CommunitySupport: Difference between revisions

From SoylentNews
Jump to navigation Jump to search
Line 20: Line 20:
*Staff
*Staff
**Get "true" @SN.org staff emails (not forwards) to all staff that want them
**Get "true" @SN.org staff emails (not forwards) to all staff that want them
***mechanicjay has a working mailbox setup, need to test a bit before distributing
**Migrate mailing list address to new @SN.org addresses
**Migrate mailing list address to new @SN.org addresses
***These will both wait until we decide on a permanent name
***These will both wait until we decide on a permanent name

Revision as of 15:44, 13 March 2014

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.

Documentation

Current responsibilities include:

  • Answers support and contact emails
  • Organizes volunteers
  • Tracks volunteers and staff (?)
  • Collects Suggestions

Future Tasks

  • 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.

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?).


ToDo

  • Staff
    • Get "true" @SN.org staff emails (not forwards) to all staff that want them
      • mechanicjay has a working mailbox setup, need to test a bit before distributing
    • Migrate mailing list address to new @SN.org addresses
      • 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?

(note: some of these have been duplicated from TodoList)

Depenencies

Dependencies for this group include:

  • Gmail (until we get staff mailboxes)
    • Mail forwards as per above
      • admin@SN
      • volunteer@SN <--not set up yet?
  • IRC Bot
    • !suggestion
    • !volunteer (to be implemented)