Difference between revisions of "TodoList"

From SoylentNews
Jump to: navigation, search
(Undefined Group: staff/volunteers section organization)
Line 2: Line 2:
  
 
==Undefined Group==
 
==Undefined Group==
*Develop process for volunteer-> staff (get email/ on mailiing list etc)
+
*Formulate Plan/vision/bylaws
 
*Develop task-list of ongoing duties from each "group"
 
*Develop task-list of ongoing duties from each "group"
*Solicit volunteers on specific tasks as indicated below
+
*Staff
*Create volunteer@soylentnews.org and link in various places
+
*Get "true" @SN.org staff emails (not forwards) to all staff that want them
*Develop system for recruiting/organizing volunteers (currently just mrcoolbp *attempting* to collect and send in the right direction)
+
**Migrate mailing list address to new @SN.org addresses
*SN Story Submission: Volunteers Needed (after determining which skills we need most)
+
*Volunteers
*Coordinate tasks with new volunteers
+
**Identify difference between volunteer VS staff
*IRC log links need updating in various places
+
**Develop process for becoming staff (get @SN.org email, get on mailing list, privileges etc)
*revisit the legal (copyright?) implications of cross-posting (reposting stories posted elsewhere)
+
**Create volunteer@soylentnews.org and link in various places
*Summarize staff meeting (or not ???)
+
**Develop system for recruiting/organizing volunteers (currently just mrcoolbp *attempting* to collect and send in the right direction)
*Formulate Plan/vision/bylaws
+
**SN Story Submission: Volunteers Needed (after determining which skills we need most i.e. perl)
*Get ALL staff @SN.org emails and migrate mailing list to new addresses (this should be optional, not automatic) (mechanicjay can help add people)
+
*IRC log links need updating in various places '''<-'''
 +
*Summarize staff meeting (or not?)
 
*New Name contest (final one, we hope)
 
*New Name contest (final one, we hope)
 
*Regular status updates with key leaders
 
*Regular status updates with key leaders
 
*Organize staff, don't do everything yourself, delegate to appropriate people
 
*Organize staff, don't do everything yourself, delegate to appropriate people
 
*Fire people when it isn't working out sooner rather than later (this should go in ongoing duties task-list)
 
*Fire people when it isn't working out sooner rather than later (this should go in ongoing duties task-list)
 
  
 
==Sys/Dev==
 
==Sys/Dev==

Revision as of 23:07, 7 March 2014

This is a list of tasks or projects that should be tackled as soon as possible. Please remove anything you know to be completed already. Also, consider visiting the similar Open Projects or the Suggestions pages.

Undefined Group

  • Formulate Plan/vision/bylaws
  • Develop task-list of ongoing duties from each "group"
  • Staff
  • Get "true" @SN.org staff emails (not forwards) to all staff that want them
    • Migrate mailing list address to new @SN.org addresses
  • Volunteers
    • Identify difference between volunteer VS staff
    • Develop process for becoming staff (get @SN.org email, get on mailing list, privileges etc)
    • Create volunteer@soylentnews.org and link in various places
    • Develop system for recruiting/organizing volunteers (currently just mrcoolbp *attempting* to collect and send in the right direction)
    • SN Story Submission: Volunteers Needed (after determining which skills we need most i.e. perl)
  • IRC log links need updating in various places <-
  • Summarize staff meeting (or not?)
  • New Name contest (final one, we hope)
  • Regular status updates with key leaders
  • Organize staff, don't do everything yourself, delegate to appropriate people
  • Fire people when it isn't working out sooner rather than later (this should go in ongoing duties task-list)

Sys/Dev

  • Ensure staff have privileges in all platforms we use
  • Implement Fire-hose of some kind
  • Single sign on to all services (register once, central administration)
  • Add markdown support, example: http://dillinger.io/ (this is also in the Suggestions que, could be removed from this list for now as is non-essential IMO mrcoolbp (talk) 22:54, 7 March 2014 (UTC))
  • Make it easy for people to submit bugs (bugs@ email? also a suggestion for doing it via slash)
  • need to update bug links (now on github) from various places
  • System for keeping old UIDs (may be impossible without changing everyone's UIDs, move to scrap idea remove info in FAQ and Migration of users page mrcoolbp (talk) 22:54, 7 March 2014 (UTC))
  • Make sure the SSL login page Pots to an SSL page, the cookie needs HTTPS headers set (this should be a bug?)(collected via Suggestions)

Communications

  • Determine better communication Forum (or keep mailing list) (suggestions: redmine, slash), get concensus, cut the dead weight (i.e. forums)
  • Change wording on wiki to specifically solicit volunteers (done?)
  • Consolidated ways to post suggestions (single repository, easy to add to, possibly via multiple means that all end up in one spot)(will be wiki, mrcoolbp collecting currently via email and !suggestions irc)
  • Refine Suggestions system (develop process to select good items, pose for vote, then implement)
  • incorporate !suggestions for any user (post directly to wiki)
  • Contact CmdrTaco via twitter?

Editors

  • Press release (at some point)
  • Develop editorial process, informed by Poll results
  • Documentation pages (FAQ, "Authors" page) <- LaminatorX is working on FAQ

Business

  • pick incorporation model, then do it
  • Swag? (sync with art)
  • Marketing - Do we do it? how do we do it?
  • Ads?
  • Donations? (these all Depend on incorporation model)
  • social media, do we want to pursue it? who? How?
  • Solicit legal advice on keeping logs of user activity. What is required?
  • How to respond to DMCA takedown requests
  • Investigate legals issues like these

Paulej72

  • change "Read More" to button.
  • Kill D2
  • fix all buttons to have proper case
  • bug 48 fix log in screen ul list
  • fix bug #68 some links are worn color in comment details trace JS loads to fix JS re-size of certain elements on mobile devices.
  • style blockquote and see what is up with quote
  • add hyperlink to article story title to story page per bug 106
  • style input boxes to have better border contrast per bug 107
  • add night mode skin per 112
  • make sure site displays “Log In” and “Log Out” per bug 116
  • fix journal template to fix broken link title tex per bug 118
  • fix preference pages per many bugs
  • fix relationships ui as per bug 37
  • migrate bugs to GitHub (curretnly in progress)