CommunitySupport: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
This " | ==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]. | |||
If you'd like to get more closely involved by working with a [[TeamPages|team]], you should contact them directly. For example the [[Development|Development Team]] can always use good people. If you have any questions or are not sure where you where to start you can send an email to mrcoolbp@soylentnews.org. | |||
More links: | |||
==Documentation== | ==Documentation== | ||
Line 36: | Line 44: | ||
Dependencies for this group include: | Dependencies for this group include: | ||
* | **SN Mailboxes and forwards: | ||
* | |||
***admin@SN | ***admin@SN | ||
*** | ***suggestions@SN | ||
*IRC Bot | *IRC Bot | ||
**!suggestion | **!suggestion | ||
Revision as of 21:54, 14 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. Further, you can 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. For example the Development Team can always use good people. If you have any questions or are not sure where you where to start you can send an email to mrcoolbp@soylentnews.org.
More links:
Documentation
Current responsibilities include:
- Answers support and contact emails
- Organizes volunteers
- Tracks volunteers and staff (?)
- Collecting Suggestions
Goals for the future:
- Develop a system to vote on and implement suggestions (this may require a strike-force)
- Develop a system for turning volunteers into staff (see TodoList
ToDo
- Ensure Team Pages all have some contact info
- Staff
- Get "true" @SN.org staff emails (not forwards) to all staff that want them
- mechanicjay has a working mailbox setup, we are testing/debuggin
- Migrate mailing list address to new @SN.org addresses
- These will both wait until we decide on a permanent name
- Get "true" @SN.org staff emails (not forwards) to all staff that want them
- Volunteers/Staff
- remove references to volunteer email catch-all, explain to contact teams directly
- Outline difference between volunteer VS staff
- Develop process for becoming staff (get @SN.org email, get on mailing list, privileges, orientation booklet, etc.)
- Refine Suggestions system
- Develop process to select good items, hold vote, then implement
- Automate *ways to post* suggestions that all end up in same place (suggestions@ email and IRC "!suggestions" are piped to wiki)
- This could all be done with slash
- Clarify our stance on vulgarity in comments (ALL CAPS is preventing posting in some cases (filter) swears seem to work)(FAQ page?)
- may require a story submission to main site
- Contact CmdrTaco via twitter?
(note: some of these have been duplicated from TodoList)
Depenencies
Dependencies for this group include:
- SN Mailboxes and forwards:
- admin@SN
- suggestions@SN
- SN Mailboxes and forwards:
- IRC Bot
- !suggestion