-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Net Neutrality Campaign #191
Comments
Here is the wiki for this work: https://wiki.mozilla.org/NN-Campaign Studio Mofo is updating the petition https://bugzilla.mozilla.org/show_bug.cgi?id=1121783 and the advocacy website https://bugzilla.mozilla.org/show_bug.cgi?id=1121786 Oglivy is being contracted to do the rest of the design work. |
This needs an owner and a fleshed out RACI. @DaveSteer / @OpenMatt - outline below if you want to take a stab at it. @edrushka is this on @sabrinang's plate already or do we need Webmaker design resource for this? |
removing needs dev and needs design labels, as Studio Mofo has that covered. |
@ErikaD said in IRC that there are many pieces to this ticket. "@sabrinang is designing the petition (95% done) and the updates to the advocacy site. moco hired a firm (ogilvy) to do all other graphic design" @DaveSteer are there any other design resources needed from MoFo? |
@edrushka : do we still need this ticket? Or can we close, given the more specific work is happening elsewhere? |
I don't see another meta ticket for the NN campaign in /plan so I think we should leave this open. Work is happening here: |
Needs RACI |
@edrushka : can you clean up this ticket? As I understand it, this is a meta-ticket gathering three pieces of work:
is that correct? and are you the owner / PM for this? |
I updated the RACI in the first comment. |
Updated RACI with username mentions. |
Update: |
Update: |
@edrushka any data or early metrics we can share? |
Update from @edrushka :
|
Yes, just got an update on the weekly standup: |
It's not clear to me what is left to do on this, esp. between now and the current milestone of Feb 27. |
To Do:
The Victory planning, currently being scoped, will likely result in some additional action items for this team (design, copy etc.) |
Update: The FCC voted in our favour today. A joint MoFo-MoCo team put the victory plan into action, which included: More than 9,000 people used the tool to make about 23,000 phone calls ahead of today's vote, while the petition drew in 300,000 signatures. Huge congrats to everyone that helped make this victory happen, especially @valianttry and @DaveSteer Closing this meta issue for now. Can refile individual tickets if further victory work is required. |
This has three pieces: updated web site, petition, call congress tool
RACI
Hi All -
We're ramping up a net neutrality advocacy campaign to launch on February 5th with inclusion in Snippets, social and other channels just as the FCC is likely to vote on rules late February (and the cable industry is already mounting its attack, alongside a new GOP led Congress). Mozillians have been fighting for strong net neutrality -- it's time to stand up and take net neutrality across the finish line.
Beyond the policy state change goal, this advocacy effort serves an important brand and community engagement purpose. It creates an environment in which
a) we can reinforce the value of Mozilla to the existing community (especially post EOY fundraising),
b) we can grow our community of people interested in fighting to protect the Internet and
c) we can grow adoption of our tools and programs by demonstrating our brand thought leadership.
Here is the link to the project brief: https://docs.google.com/a/mozillafoundation.org/document/d/1IOjvypPZP2FHiItwyicsH3LKgqzc7SeTGo22MSJroSU/edit#
This will be a XFN MoCo/MoFo sprint, but hoping it will be fairly lightweight by using existing templates. I'll be scheduling a kickoff shortly to include: @HPaulJohnson, Andrea Wood, @Kellijk, @edrushka, and people from MoFo Policy, Engagement and Comms. Please let me know if others should be included.
Thanks!
The text was updated successfully, but these errors were encountered: