ReMo/Communication

From MozillaWiki
Jump to: navigation, search
Draft-template-image.png THIS PAGE IS A WORKING DRAFT Pencil-emoji U270F-gray.png
The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly.
If you have any questions or ideas, please add them as a new topic on the discussion page.

This page documents all communication channels the Reps program uses as well as their purpose. Additionally this documents our content strategy.

Communication Channels

Currently used channels

These are the current channels we are using for announcements and discussion:

Internally facing:

Channel URL Purpose
Discourse https://discourse.mozilla-community.org/c/reps / https://discourse.mozilla-community.org/c/mozillians/nda Main forum for discussions about the Reps program. We create a discussion here for all announcements and other program related discussions we need to have. These links are cross-posted to reps-general. The ultimate goal is to just use Discourse for all discussions while still providing several interfaces to interact with (email is completely possible with Discourse as well). The NDA category is used for sensitive information discussion.
Newsletter to be decided Starting in early 2017 there will be also a Newsletter sent at least monthly to all Reps. This will include all important information and discussions.
reps-general https://lists.mozilla.org/listinfo/reps-general All Reps are subscribed to the reps-general mailing list. We are posting announcements and discussions with a link to Discourse. The ultimate goal is to have this synchronized with Discourse so it is possible to discuss through both. IMPORTANT: This channel is not thought to have NDA'd content (please use the Discourse NDA category for this). Please read the mailing list policy carefully before writing a message on the list.
reps-mentors https://lists.mozilla.org/listinfo/reps-mentors Discussions on a mailing list among Reps Mentors. The ultimate goal is to have this synchronized with Discourse so it is possible to discuss through both. This channel is not thought to have NDA'd content (please use the Discourse NDA category for this).
Telegram Group request invite from your mentor or another Rep Informal discussions about Reps and Mozilla in general. All new announcements and discussions from Discourse are pinned here for broader visibility. This channel is not thought to have NDA'd content (please use the Discourse NDA category for this).
Telegram Announcement Channel request invite from your mentor or another Rep Read-only announcements, tweets, and important information is shared through that announcement channel. It is not possible to respond to those within Telegram. This channel is not thought to have NDA'd content (please use the Discourse NDA category for this).
Reps Council Alias reps-council@mozilla.com Used by the Reps Council for their coordination and discussions. This is automatically posted to a private inbox on Discourse to allow an archive for future Council members. This is the preferred way of reaching out to the Council for private matters.

Externally facing:

Channel URL Purpose
Reps Twitter Account https://twitter.com/mozillareps Communications about the Reps program and Mozilla in general. This is thought to be internally as well as externally facing. This is one of our main channels towards the broader organization.
Reps Blog http://blog.mozilla.org/mozillareps/ Announcements such as OKRs, Rep of the Month, and other program relevant pieces for a broader audience (whole Mozilla org, other interested parties, ..)

Channels to be analyzed

  • Facebook (see Experiments)

Channels to be deprecated very soon

Deprecated

  • #remo IRC channel (still around, but not official used anymore)

Communication Content Strategy

To be decided.

Experiments

Connecting Facebook and Twitter provides us more flexibility and reach

As of now we mostly use the Facebook Group for meeting announcements cross-posts. Given the fact that a lot of Reps are also on Facebook, we suspect that we are not using Facebook as good as we could to. As a first step, we are evaluating to cross-post automatically from Twitter. Konstantina is responsible for this exploration.