CommunitySupport: Difference between revisions

From SoylentNews
Jump to navigation Jump to search
m (obfuscated links to @soylentnews to hide from spammers)
 
(38 intermediate revisions by 7 users not shown)
Line 1: Line 1:
This "Team" is currently just myself, mrcoolbp. I can see this team growing in responsibilities, but until then, I have no need for additional personnel.
==Welcome==
 
This site is made possible by (and for) the insightful community of users. This team supports that community in various, ever-changing ways.
 
There are many ways to participate in this project. 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 ideas for new projects in [[Suggestions]], or bugs 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 perl experience, and the [[Editors]] team are looking to expand their time zone coverage. If you have any questions or are not sure where to start you can send an email to '''suggestions (at) soylentnews.org'''.
 
==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[CommunitySupport|Community Support Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| [[User:mrcoolbp|mrcoolbp]]
| Leader
| UTC-4 (EST/EDT)
|-
|}
<section end=whoarewe />
 
==Retired Members==
Former members of the Community Support team that have lost their roles due to inactivity or retirement
{| class="wikitable" width="100%"
!colspan="3"|'''[[CommunitySupport|Former members]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| [[User:xlefay|xlefay]]
| Co-team leader
| UTC+2 (CEST)
|-
|}


==Documentation==
==Documentation==
Current responsibilities include:
 
This team:
*Answers support and contact emails
*Answers support and contact emails
*Organizes volunteers
*Tracks and logs bugs and feature requests
*Tracks volunteers and staff (?)
*Helps write static pages
*Maintains the wiki and keeps general information up-to-date
*Tracks volunteers and staff
*Collects [[Suggestions]]
*Collects [[Suggestions]]
*Administers [[SocialMedia|social media sites]]
Goals for the future:
*Utilize community feedback selecting suggestions for implementation
*Investigate staff and community '''[[CommunicationSystems|Communication Systems]]'''


Future Tasks
==Dependencies==
*Develop a system to vote on and implement suggestions (this will require a strike-force)
*Develop a system for turning volunteers into staff (see [[TodoList]]


Ideally, I see volunteers contacting Team leaders directly, especially when they already know where they want to be. This is obviously less work for me and Team Leaders will be subject matter experts where I may not be (i.e. I have BG in art/css/html/editorial etc., but no dev). To elaborate: I don't want to liaise for every team, not out of laziness, but efficiency. For more general tasks I can troll the team pages and collect general volunteers via email and IRC and coordinate from there. This will be much easier when we have an idea of which teams need what kind of help.
Dependencies for this group include:
 
*SN Mailboxes and forwards:
Another idea I'd like to work on is how someone would become staff. A thought I had is that Team leaders could grant "staff" status after a volunteer proves their self (no privs until?).
**admin@SN
**suggestions@SN
**social-media@SN
**mail is hosted on [[Soylent-services|beryllium]]
*IRC Bot
**!suggestion (currently de-activated)


==Projects==


==ToDo==
*Organize staff meetings
*Staff
*Migrate mailing list addresses to new @SN.org addresses
**Get "true" @SN.org staff emails (not forwards) to all staff that want them
*Develop [[NewStaff|process for becoming staff]] (get @SN.org email, get on mailing list, privileges, orientation booklet, etc.)
**Migrate mailing list address to new @SN.org addresses
* [[Suggestions#IRC]]
***These will both wait until we decide on a permanent name
*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 !suggestions irc are forwarded to an email and are manually added)
***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?
*Contact CmdrTaco via twitter?


(note: some of these have been duplicated from [[TodoList]])
==Depenencies==


Dependencies for this group include:
[[Category:Teams]]
*Gmail (until we get staff mailboxes)
[[Category:Community support]]
**Mail forwards as per above
***admin@SN
***volunteer@SN <--not set up yet?
*IRC Bot
**!suggestion
**!volunteer (to be implemented)

Latest revision as of 13:46, 22 January 2019

Welcome

This site is made possible by (and for) the insightful community of users. This team supports that community in various, ever-changing ways.

There are many ways to participate in this project. Of course, submitting stories or commenting on them is the most obvious way to get involved. You can also submit ideas for new projects in Suggestions, or bugs 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 perl experience, and the Editors team are looking to expand their time zone coverage. If you have any questions or are not sure where to start you can send an email to suggestions (at) soylentnews.org.

Who we are

Community Support Team Main Page

nick

position

timezone

mrcoolbp Leader UTC-4 (EST/EDT)


Retired Members

Former members of the Community Support team that have lost their roles due to inactivity or retirement

Former members

nick

position

timezone

xlefay Co-team leader UTC+2 (CEST)

Documentation

This team:

  • Answers support and contact emails
  • Tracks and logs bugs and feature requests
  • Helps write static pages
  • Maintains the wiki and keeps general information up-to-date
  • Tracks volunteers and staff
  • Collects Suggestions
  • Administers social media sites

Goals for the future:

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

Dependencies

Dependencies for this group include:

  • SN Mailboxes and forwards:
    • admin@SN
    • suggestions@SN
    • social-media@SN
    • mail is hosted on beryllium
  • IRC Bot
    • !suggestion (currently de-activated)

Projects

  • Organize staff meetings
  • 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.)
  • Suggestions#IRC
  • Contact CmdrTaco via twitter?
Retrieved from "https://wiki.soylentnews.org/index.php?title=CommunitySupport&oldid=29816"