|
|
| Line 10: |
Line 10: |
|
| |
|
| Currently, you can find a collection of basic guidelines and tutorials for the different kinds of communication you might engage in. But ultimately our goal is to create frameworks and processes that enable you, amazing Mozillian, to see, hear and participate in Mozilla’s marketing communications. In other words, we want Open Comms to be more than a program, but to become the natural way we do things around here. | | Currently, you can find a collection of basic guidelines and tutorials for the different kinds of communication you might engage in. But ultimately our goal is to create frameworks and processes that enable you, amazing Mozillian, to see, hear and participate in Mozilla’s marketing communications. In other words, we want Open Comms to be more than a program, but to become the natural way we do things around here. |
|
| |
| == Communication Guidelines ==
| |
|
| |
| Image you are making your way through the airport, super excited to attend the International Red Panda Summit.
| |
|
| |
| At the airport, you have some sense of how to get around, but there are also helpful signs along the way pointing you in the right direction. This section is like the airport signage. Here you’ll find messages, FAQs, guidelines and tips to effectively talk about Mozilla and our products. You’ll also find help for the more complicated topics and the people you can turn to for help (hint: it’s the people writing this page).
| |
|
| |
| These guidelines will be helpful if you’d like to talk (or write) to the world about Mozilla '''as a Mozilla representative''', whether proactively or reactively.
| |
|
| |
| If you write for a blog or publication regularly, make sure to include the link in your Mozillian profile and please give the PR team a heads-up at communications@moz...a.com. We won’t ask you to send us every blog post, but we’re always here to help, especially with the tricky ones :)
| |
| '''Communicating as a Mozillian'''
| |
| Feel free to use the tips and messaging found on this page and email the comms team if you need any help. All we ask is you complete [https://docs.google.com/a/mozilla.com/forms/d/16vXnTx7WdtbhUNsNgdVZVQTYbb4qFE72A7965lyie_Q/edit this coverage form] for your blog and any other blogs or media outlets who covered your post. We’d love to include it in our coverage reports and show how loud the Mozilla megaphone can be! The areas below are generally great ways you can tell the Mozilla story freely - the “fast-track” lane in our airport analogy.
| |
|
| |
| '''Fast-track topics''':
| |
| * Announced products, features and initiatives <br>
| |
| * Mission and history of Mozilla, its relationship to the open-source community, etc. <br>
| |
| * Community activities <br>
| |
| * Profiles of community members, etc.
| |
|
| |
| The next few topics are a little more complicated and suitable for “frequent flyers only”. If you are part of the CommSquared program or an experienced spokesperson you likely have the tools and nuanced messaging to tell Mozilla’s POV. Otherwise, please contact the PR team for guidance. Some of these may be sensitive, or there may be a chance for you to make a bigger impact by coordinating timing of your story with the team!
| |
|
| |
| '''Frequent Flyer-only topics''':
| |
|
| |
| * Upcoming (not yet released/announced) projects, product features, etc. <br>
| |
| * Public policy / political statements (beyond what’s on the wiki) <br>
| |
| * Data/statistics on product usage, market share, etc.
| |
|
| |
| But what happens if, for instance, you’re approached by a journalist who is asking your opinion on a sensitive issue? You can feel the situation veering off-course and --Oh noes! you’re entering the difficult, “restricted” section. But you’re a Mozillian, you want to be nice and have some sort of reply. Below you’ll find some statements you may find helpful for each situation:
| |
|
| |
| '''Restricted topics''':
| |
| * Sensitive information/speculation relative to our current and former partners <br>
| |
| ** Sample responses: <br>
| |
| *** “That’s a question for [partner].” <br>
| |
| *** “I can’t speak to [partner]’s strategy regarding [xyz]. What I can do is connect you to our PR team to make sure you get Mozilla’s perspective on xyz subject.” (If you are 100% sure of Mozilla’s view on the topic, feel free to state it here, but *not* in comparison or contrast to the partner) <br>
| |
| * Rumors/speculation about Mozilla staff, internal strategy, etc. (really, rumors of any kind) <br>
| |
| ** Sample responses: <br>
| |
| *** “I don’t really have all the details, and speculation won’t be helpful.” <br>
| |
| *** (With regards to staff departures, in addition to above): “What I can say is that Mozilla is very different from other organizations, and many who depart choose to keep contributing to the project as volunteers. Once a Mozillian, always a Mozillian!” :) <br>
| |
| * Information labeled as and/or understood to be private or confidential <br>
| |
| ** Sample responses: <br>
| |
| *** “I believe that is confidential information, so I’m afraid I cannot discuss it.” <br>
| |
| *** “I’m really not the right person to ask. I can connect you to our PR team who can help.” <br>
| |
|
| |
| Beyond the above, we can’t stop you from expressing your individual opinions and thoughts, but we also can’t be help you at that point. Depending on the issue, we may have think twice before trusting you with certain information again. Sad PR team :(
| |
|
| |
|
| == Media Relations Guidelines == | | == Media Relations Guidelines == |