|
|
| Line 105: |
Line 105: |
|
| |
|
| *[https://wiki.mozilla.org/One-Mozilla-Project/Documentation/Blog-Guidelines/Content-Leads Content leads here] | | *[https://wiki.mozilla.org/One-Mozilla-Project/Documentation/Blog-Guidelines/Content-Leads Content leads here] |
|
| |
| ==Why do we need blog guidelines?==
| |
|
| |
| Mozilla is growing and more projects lead to more discussions, which again lead to more threads to follow - a process that makes it harder to follow what the Mozilla project stands for with regard to a certain topic.
| |
|
| |
| In the past, journalists, our users and even Mozillians often found it hard to identify Mozilla's position on different industry developments. By offering a clear distinction between personal opinions and those of the organization overall, we aim to avoid misunderstandings regarding ongoing discussions versus finalized project announcements, particular in the press.
| |
|
| |
| The PR team is proposing the Mozilla blog guidelines to help people to hear Mozilla’s voice out there, loud and clear. Therefore, we need your help: our external communication needs to be consistent and journalists should be able to find relevant information fast, easy and trustworthy enough to be referred to in their articles.
| |
|
| |
| We want to encourage you to spread the word about Mozilla, build-up on everything we achieved and get credited for out there. Help us to tell people why Mozilla is a great organization - and one that is speaking with one voice and acting as “one Mozilla”.
| |
|
| |
| Our external communication and every Mozillian involved as a blogger or spokesperson has an impact on our reputation. Reputation is how other people think or speak about us, always based on our behavior – past, present and even future. Reputation is not about image. You cannot build up reputation artificially; it needs to develop over time.
| |
|
| |
|
| |
| About Content Leads [this will be published as a separate page on the Mozilla WIKI]
| |
|
| |
| 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*).
| |
|
| |
| Overview of Content Leads
| |
|
| |
| Table to be added / teams to add their Content Lead
| |
|
| |
| Review timings and time zone-friendly posting
| |
|
| |
| If you would like the PR team to review your blog posts, please send it to communications@mozilla.com at least three days before you plan to publish your post. This will give everyone enough time to discuss, review and do some fine-tuning on your post if you need the PR team’s wordsmithing magic or help with the Mozilla messaging. The PR team can also help you to find a good day and time to publish your post, to make sure we get the press attention we want your blog post to receive. If you would like to flag a finalized blog post with the PR team so that they are aware, please do so one day before you plan to publish.
| |
|
| |
| Time-sensitive content that requires a faster turnaround time can also be reviewed by the PR team on short notice: Feel free to drop by the PR team’s desk directly or send an email, flagging the matter’s urgency with [time sensitive] in the subject line.
| |
|
| |
| 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.
| |
|
| |
| Best days for posting news and announcements are Tuesdays and Wednesdays.
| |
| Mondays (journalists need to clear their inboxes from a lot of news and press releases) and Thursdays (press queries from Europe will have to be turned around on a Friday which is difficult on both sides, journalists and spokespeople) are still okay, but not the first choice to do global press outreach.
| |
|
| |
|
| |
| What needs to be reviewed? [this will be published as a separate page on the Mozilla WIKI]
| |
|
| |
| News and announcements we expect to receive a lot of media attention, such as:
| |
|
| |
| Major product announcements and updates
| |
| Official responses to a current industry issue
| |
| Strategic and visionary pieces posted by Mozilla Executives
| |
| Relevant numbers, figures and market share statistics
| |
| Statements on competitors, potential partners or Mozilla’s revenue streams
| |
| Major issues surrounding privacy or security
| |
|
| |
|
| |
|
| |
| What doesn’t need to be reviewed?
| |
|
| |
| Content that will not go up on a Mozilla-hosted channel, such as:
| |
| Blog or forum posts that reflect your personal opinion and go up on your personal blog or a non-Mozilla platform
| |
| Content created by the Mozilla community or content that will go up on our community channels
| |
|
| |
| Content to be posted in MDN, demos, code
| |
| Content posted to a personal blog, to be aggregated to Planet Mozilla
| |
| Anything else that we don’t expect to attract any media attention
| |