MozillaWiki

Websites/Mozilla.org/One Mozilla/Documentation/Blog-Guidelines/Content-Leads: Difference between revisions

Page Discussion

Websites/Mozilla.org/One Mozilla/Documentation/Blog-Guidelines/Content-Leads (view source)

Revision as of 19:40, 10 September 2015

1,210 bytes added ,  10 September 2015
m
→‎Overview of Content Leads
 
(17 intermediate revisions by 6 users not shown)
Line 1: Line 1:
=About Content Leads=
=About Content Leads - DRAFT PLAN * still in progress *=


Every team who runs a multi-author, Mozilla-hosted blog appoints a Content Lead.  The Content Lead is accountable for the content that is published on the team’s blog. It is up to the Content Lead to decide whether or not a draft blog post needs to be reviewed by or flagged with the PR team. Any posts needing review should be provided in draft form to the PR team three days ahead of time (*more on review timings below*).
Every team who runs a multi-author, Mozilla-hosted blog appoints a Content Lead.  The Content Lead is accountable for the content that is published on the team’s blog. It is up to the Content Lead to decide whether or not a draft blog post needs to be reviewed by or flagged with the PR team. Any posts needing review should be provided in draft form to the PR team three days ahead of time (*more on review timings below*). Key stakeholders should also be involved in the approval process for announcements that shape our strategy. A list of key stakeholders for each product area can be found below.


==Overview of Content Leads==
==Overview of Content Leads==
Line 13: Line 13:
| Your Team Here
| Your Team Here
| Blog URL here
| Blog URL here
| Content Lead Name & Email Here
| Content Lead Name & Email Here (feel free to update for your blog)
|-
|-
| PR
| Mozilla Main Blog
| [http://blog.mozilla.com main blog.mozilla.com]
| [http://blog.mozilla.com blog.mozilla.com]
| Valerie Ponell vponell@mozilla.com
| Mozilla Communications Team
|-
| Mozilla Privacy
| [http://blog.mozilla.com/privacy blog.mozilla.com/privacy]
| Alex Fowler
|-
| Firefox Add-ons
| [http://blog.mozilla.com/addons blog.mozilla.com/addons]
| Justin Scott "Fligtar"
|-
|-
| Mozilla Security
| Mozilla Security
| Michael Coates
| [http://blog.mozilla.com/security blog.mozilla.com/security]
| Updates on Security at Mozilla
| Dan Veditz and Richard Barnes
| see links to the right
|-
|
| Future of Firefox
* Questions, comments, concerns - [mailto:security@mozilla.org security@mozilla.org]
| [http://blog.mozilla.com/futureoffirefox blog.mozilla.com/futureoffirefox]
* [https://wiki.mozilla.org/Security Security Wiki]
| Laura Mesa / Grace Jimenez
* [https://wiki.mozilla.org/Security/Radar Security Radar]
* [https://wiki.mozilla.org/SecurityEngineering Security Engineering Page]
* [https://wiki.mozilla.org/Security/Roadmap Security Roadmap]
* [https://wiki.mozilla.org/Privacy/Roadmap Privacy Roadmap]
|-
|-
| Firefox Metrics
| [http://blog.mozilla.com/metrics blog.mozilla.com/metrics]
| Gil Fitzgerald
|-
| Mozilla Beyond the Code
| [http://blog.mozilla.com/beyond-the-code blog.mozilla.com/beyond-the-code]
| Tristan Nitot
|-
| Market Insights
| [http://blog.mozilla.com/market-insights blog.mozilla.com/market-insights]
| Irina Sandu
|-
| User Research (to be merged with UX)
|[https://blog.mozilla.com/userresearch blog.mozilla.com/userresearch]
| Diane Loviglio
|-
| L10N
| [http://blog.mozilla.com/l10n blog.mozilla.com/l10n]
| Jeff B.
|-
| Apps
| [http://blog.mozilla.com/apps blog.mozilla.com/apps]
| Scott DeVaney
|-
| Research
| [http://blog.mozilla.com/research blog.mozilla.com/research]
| DHerman
|}
==Product Stakeholders==


{| class="fullwidth-table"
|-
!  Product
!  Stakeholder
|-
| Firefox Desktop
| (to be added)
|-
| Firefox Mobile
| (to be added)
|-
| Add-ons
| (to be added)
|-
| Boot to Gecko
| (to be added)
|-
| Marketplace
| (to be added)
|-
| Identity
| (to be added)
|-
| Privacy
| (to be added)
|-
| Security
| (to be added)
|-
| (to be added)
| (to be added)
|-
| (to be added)
| (to be added)
|-
| (to be added)
| (to be added)
|}
|}


Line 41: Line 112:


For globally relevant announcements, keep in mind that Europe (and thus half of the PR team, six PR agencies, and a significant base of journalists and users) is 9 hours ahead of Pacific Time. If you are based on the West Coast, this means that the best time to post something is early Pacific Time, ideally between 6 and 8 am, if not earlier. Everything posted later than that will cause us to lose the opportunity to be part of the day’s news cycle in Europe, or to do any active press outreach at all.
For globally relevant announcements, keep in mind that Europe (and thus half of the PR team, six PR agencies, and a significant base of journalists and users) is 9 hours ahead of Pacific Time. If you are based on the West Coast, this means that the best time to post something is early Pacific Time, ideally between 6 and 8 am, if not earlier. Everything posted later than that will cause us to lose the opportunity to be part of the day’s news cycle in Europe, or to do any active press outreach at all.
    US-based PR team (PT) [link to Engagement Wiki for contact details]
    EU-based PR team (CET) [link to Engagement Wiki for contact details]


Friday is not a good day for announcements at all, as the EU press team will not be able to do outreach until the following Monday.
Friday is not a good day for announcements at all, as the EU press team will not be able to do outreach until the following Monday.
Dveditz
canmove, Confirmed users
640

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/404763...1094701"