[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Office-commits] r9858 - trunk/campaigns/pipeline
From: |
sysadmin |
Subject: |
[Office-commits] r9858 - trunk/campaigns/pipeline |
Date: |
Wed, 30 Sep 2009 15:50:21 -0400 |
Author: www-data
Date: Wed Sep 30 15:50:21 2009
New Revision: 9858
Log:
web commit by holmes
Added:
trunk/campaigns/pipeline/rapidresponseteam.mdwn
Added: trunk/campaigns/pipeline/rapidresponseteam.mdwn
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ trunk/campaigns/pipeline/rapidresponseteam.mdwn Wed Sep 30 15:50:21
2009 (r9858)
@@ -0,0 +1,65 @@
+
+
+
+
+##Evaluation
+
+Objectives were:
+
+Objectives met:
+
+Goals met:
+
+On schedule? (according to timeline)
+
+Further action? Or tie off / drop
+
+Lessons learned / Action to implement lesson
+
+## Launched
+
+* Emails
+* Blog post
+* Wiki page
+* Email list
+
+## Draft
+
+Materials:
+
+* Emails
+* Blog post
+* Wiki page
+* Email list
+
+## Proposal: Volunteer team for news rapid response
+
+Goal: People see FSF positions and overall philosophy when they read top
tech/politics sites, while FSF staff spend minimal time at this effort.
+
+Objectives:
+
+* We have a group of volunteers making a regular commitment (10-20, at least 5
solid commitment)
+* 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.
+
+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.
+* When at least 10 people on the list, continue, otherwise get more.
+* 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).
+* 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).
+
+Timeline:
+
+* Week 1: All emails listed above sent, volunteers in place, document
built/divied up, volunteers mobilized. Report back on number of volunteers.
+
+* Week 2: Second round of search for volunteers if necessary. Send an
encouraging email to the list, keep people focused, ask for feedback. Report
back: does it seem like it will be self-sustaining? If not, what needs to
change?
+
+* Week 3: Evaluate / report back: does it seem like it will be
self-sustaining? Will it meet objectives? If not, what needs to change? Big
changes? Little changes?
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Office-commits] r9858 - trunk/campaigns/pipeline,
sysadmin <=