[Office-commits] r9961 - trunk/campaigns/pipeline

[sysadmin]

Author: www-data
Date: Fri Oct  2 14:37:10 2009
New Revision: 9961

Log:
web commit by holmes

Modified:
   trunk/campaigns/pipeline/rapidresponseteam.mdwn

Modified: trunk/campaigns/pipeline/rapidresponseteam.mdwn
==============================================================================
--- trunk/campaigns/pipeline/rapidresponseteam.mdwn     Fri Oct  2 14:16:35 
2009        (r9960)
+++ trunk/campaigns/pipeline/rapidresponseteam.mdwn     Fri Oct  2 14:37:10 
2009        (r9961)
@@ -12,7 +12,18 @@
 
 On schedule?  (according to timeline)
 
-Further action?  Or tie off / drop
+##Further action?  Or tie off / drop
+
+## Follow up: 
+
+### Involving volunteers in RT (our email to the volunteer list):
+
+* You get an RT account. 
+* You pick a focus
+* We'll assign stuff to the volunteers queue
+* You assign stuff to your name from the queue, do it, and mark it done.
+* Send a monthly update to the list about your RT work.
+
 
 Lessons learned / Action to implement lesson
 
@@ -42,19 +53,25 @@
 * Volunteers follow a list of sites, write FSF responses to news relevant to 
articles touching on FSF issues software freedom, DRM, war on sharing, etc. (15 
per week)
 * Volunteers are on-message.
 * Volunteers keep campaigns team up to date on developing stories that we 
should pay attention to.
-* Volunteers help *generate* stories on these sites that express FSF ideas (by 
submitting our actions, or suggesting angles of approach to campaigns team / 
RMS).  5 new FSF-generated stories per month.   
+* Volunteers help *generate* stories on these sites that express FSF ideas (by 
submitting our actions, or suggesting angles of approach to campaigns team / 
RMS).  5 new FSF-generated stories per month.
+* Volunteers help us respond to emails to address@hidden in RT.   
 
 Steps:
 
 * Make a mailing list.   This is where volunteers can report successes, track 
their work, discuss with each other, ask campaigns team for guidance on 
message.  At least one person on campaigns joins list.  
 * Compose email to the following lists: ????????? address@hidden, 
defectivebydesign?? to get volunteers and compose blog post.  These point 
people to join the list. 
+* Look up volunteers page in the wiki and write to them too (a different 
email, acknowledging they've already volunteered).
+* Look through RT for existing volunteers (search for "volunteer" or look at 
people on volunteer queue).  Send to them too.
 * When at least 10 people on the list, continue, otherwise get more.
+* Adapt email send to lists and set it as the welcome email to the volunteers 
mailing list (so that any future subscribers get it, and that's the primer they 
get when they come in.  Invite them to introduce themselves, ask the list if 
they have questions).
 * Create a list of sites that are central to tech and politics information / 
debate in Libreplanet wiki (in a public space, right?).  Start with BoingBoing, 
Slashdot, Engadget, Gizmodo, Consumerist.
 * On same page, create list of important philosphy / position documents that 
volunteers should read (start with "confusing words to avoid")
 * Send wiki link to RMS, campaigns-nonrt@, new list of volunteers and invite 
input.
-* Send email to volunteer team asking them to read philosophy/position 
articles and divide up the list of sites according to who will work on what.  
Goal is to check twice daily (so it's okay if two people get the same site).  
+* Send email to volunteer team asking them to read philosophy/position 
articles and divide up the list of sites according to who will work on what.  
Goal is to check twice daily (so it's okay if two people get the same site).  
Sites can be divided thematically, so somebody is FSF's press coordinator for 
tech blogs, political blogs, mainstream press, etc.  Don't just divide up, make 
roles that feel solid.  
 * Ask volunteers to share with the list: the text of their comments and a 
link, any questions about FSF's position or message, stories campaigns team 
should pay attention to, a weekly update.
 * Campaigns team monitors list and gives feedback (we agree that comments 
don't have to be confirmed beforehand... FSF staff can give feedback which 
volunteers can implement *next time* unless there's a convenient way to edit a 
comment and the volunteer wants to do that).
+* If there is energy here + 2 weeks, invite members of volunteer team to join 
RT and help us respond to articles there.  See "involving volunteers in RT" 
follow up.
+
 
 Timeline: