CommunitySupport: Difference between revisions

From SoylentNews
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
==Welcome==
==Welcome==
This site is made possible by, and for, the insightful community of users. There are many ways to participate. Of course, [http://soylentnews.org/submit.pl submitting stories] or commenting on them is the most obvious way to get involved. Further, you can submit [[Suggestions]] or even bugs you find and "feature requests" on the [https://github.com/SoylentNews/slashcode/issues bug tracker on github].
This site is made possible by, and for, the insightful community of users. There are many ways to participate. Of course, [http://soylentnews.org/submit.pl submitting stories] or commenting on them is the most obvious way to get involved. You can also submit [[Suggestions]] or even bugs you find and "feature requests" on the [https://github.com/SoylentNews/slashcode/issues bug tracker on github].


If you'd like to get more closely involved by working with a team, you should contact them directly. Start at the [[WhosWho]] or [[TeamPages|Team Pages]]. For example the [[Development|Development Team]] can always use good people. If you have any questions or are not sure where to start you can send an email to '''suggestions@soylentnews.org'''.
If you'd like to get more closely involved by working with a team, you should contact them directly. Start at the [[WhosWho]] or [[TeamPages|Team Pages]]. For example the [[Development|Development Team]] can always use good people. If you have any questions or are not sure where to start you can send an email to '''suggestions@soylentnews.org'''.


==Documentation==
==Documentation==
Current responsibilities include:
 
This team:
*Answers support and contact emails
*Answers support and contact emails
*Tracks volunteers and staff
*Tracks volunteers and staff
*Collects [[Suggestions]]
*Collects [[Suggestions]]
Goals for the future:
Goals for the future:
*Utilize community feedback selecting suggestions for implementation
*Utilize community feedback selecting suggestions for implementation
*Develop a system for turning volunteers into staff (see [[TodoList]])
*Investigate staff and community '''[[CommunicationSystems|Communication Systems]]'''
 
==ToDo==
*Get mailboxes for all staff (that want them)
**mechanicjay has a working mailbox setup, we are testing and debugging
**Migrate mailing list addresses to new @SN.org addresses
***(after we decide on a permanent name)
*Develop process for becoming staff (get @SN.org email, get on mailing list, privileges, orientation booklet, etc.)
*Get email and IRC "!suggestions" piped directly to wiki)
*Clarify filter parameters (vulgarity, all caps,)(add to FAQ page?)
*Contact CmdrTaco via twitter?


==Depenencies==
==Depenencies==
Line 33: Line 23:
*IRC Bot
*IRC Bot
**!suggestion (currently de-activated)
**!suggestion (currently de-activated)
==Projects==
*New (final) Name Vote (mrcoolbp, audioguy, MrBluze)
**New Names Shortlist '''(will be revised)'''
***soylentnews
***port119.net
***baconnews.org baconnews.net (baconnews.'''net''' was suggested as it can be "BNN")
***nerdcard.net
***geekcard.org
***dailybacon.org
***ionews.org
*Migrate mailing list addresses to new @SN.org addresses
*Develop process for becoming staff (get @SN.org email, get on mailing list, privileges, orientation booklet, etc.)
*Get email and IRC "!suggestions" piped directly to wiki)
*Clarify lameness filter paramaters (This has been partially fixed with upcoming slash updates that are in the testing phases.  Lameness filter will be able to show its error codes) <-remove
*Contact CmdrTaco via twitter?


[[Category:Teams]]
[[Category:Teams]]
[[Category:Community support]]
[[Category:Community support]]

Revision as of 05:42, 24 March 2014

Welcome

This site is made possible by, and for, the insightful community of users. There are many ways to participate. Of course, submitting stories or commenting on them is the most obvious way to get involved. You can also submit Suggestions or even bugs you find and "feature requests" on the bug tracker on github.

If you'd like to get more closely involved by working with a team, you should contact them directly. Start at the WhosWho or Team Pages. For example the Development Team can always use good people. If you have any questions or are not sure where to start you can send an email to suggestions@soylentnews.org.

Documentation

This team:

  • Answers support and contact emails
  • Tracks volunteers and staff
  • Collects Suggestions

Goals for the future:

  • Utilize community feedback selecting suggestions for implementation
  • Investigate staff and community Communication Systems

Depenencies

Dependencies for this group include:

  • SN Mailboxes and forwards:
  • IRC Bot
    • !suggestion (currently de-activated)


Projects

  • New (final) Name Vote (mrcoolbp, audioguy, MrBluze)
    • New Names Shortlist (will be revised)
      • soylentnews
      • port119.net
      • baconnews.org baconnews.net (baconnews.net was suggested as it can be "BNN")
      • nerdcard.net
      • geekcard.org
      • dailybacon.org
      • ionews.org


  • Migrate mailing list addresses to new @SN.org addresses
  • Develop process for becoming staff (get @SN.org email, get on mailing list, privileges, orientation booklet, etc.)
  • Get email and IRC "!suggestions" piped directly to wiki)
  • Clarify lameness filter paramaters (This has been partially fixed with upcoming slash updates that are in the testing phases. Lameness filter will be able to show its error codes) <-remove
  • Contact CmdrTaco via twitter?