Reps/Communication: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Removed draft banner + moved deprecated channels to correct section)
(Warning added)
 
(10 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{Warning |1= With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.|title= With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.}}


This page documents all communication channels the Reps program uses as well as their purpose. Additionally this documents our content strategy.
This page documents all communication channels the Reps program uses as well as their purpose. Additionally this documents our content strategy.
Line 11: Line 13:
! Channel
! Channel
! URL
! URL
! Type
! Purpose
! Purpose
|-
|-
| Discourse
| Discourse
| https://discourse.mozilla-community.org/c/reps / https://discourse.mozilla-community.org/c/mozillians/nda
| https://discourse.mozilla-community.org/c/reps<br/>https://discourse.mozilla.org/c/reps/mentors<br/>https://discourse.mozilla-community.org/c/mozillians/nda
| Asynchronous discussions
| 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.
| 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.
|-
| [[Matrix]] Chat
| https://matrix.to/#/!hHmqXvUdKMtqwwHeWu:mozilla.org?via=mozilla.org&via=matrix.org&via=flak.is
| Synchronous chat
| Chat for synchronous and informal discussions about Reps and Mozilla in general. '''This channel is not thought to have NDA'd content (please use the Discourse NDA category for this).'''
|-
| [[Matrix]] Announcement Channel
| https://matrix.to/#/!cAyasJUyKZutejteSb:mozilla.org?via=mozilla.org&via=matrix.org&via=t2bot.io
| Notifications
| Read-only announcements, new Discourse topics and important information is shared through that announcement channel. It is not possible to respond to those. '''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
| Governance
| 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. For public discussions please use the Discourse category.
|-
|-
| Newsletter
| Newsletter
| to be decided
| https://discourse.mozilla.org/tags/reps-newsletter
| 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.
| Notifications
| The [https://reps.mozilla.org/people/#/group/newsletter/ Newsletter Team] is sending out newsletters to all Reps. This includes all important information and discussions.
|-
|-
| reps-general
| reps-general
| https://lists.mozilla.org/listinfo/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 [[ReMo/Mailing list policy|mailing list policy]] carefully before writing a message on the list.'''
| Deprecated
|-
| All Reps are subscribed to the reps-general mailing list. We are posting announcements and discussions with a link to Discourse. Eventually we will decommission this. This is read-only. '''IMPORTANT: This channel is not thought to have NDA'd content (please use the Discourse NDA category for this). Please read the [[ReMo/Mailing list policy|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.
|}
|}


Line 56: Line 61:
| http://blog.mozilla.org/mozillareps/
| 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, ..)
| Announcements such as OKRs, Rep of the Month, and other program relevant pieces for a broader audience (whole Mozilla org, other interested parties, ..)
|-
| Facebook Reps page
| https://www.facebook.com/MozillaReps/
| This page is maintained by Mayur Patil, Vishal Chavan, Yofie Setiawan and Srushtika Neelakantam.
|}
|}


== Channels to be analyzed ==
= Communication Content Strategy =
Our current strategy is to identify further improvements to be done. For now, in terms of publication of information, we will continue as-is. This means the following:


* Facebook (see Experiments)
{| class="wikitable"
|-
! Topic
! Channels
|-
| Discussions
|
* Post to start discussion on Discourse
* Share link to reps-general
|-
| Rep of the Month
|
* Blog post on Mozilla Reps blog
* Discourse post
* reps-general info with Discourse post link
* send to Matrix
|-
| Goals
|
* Discourse post
* Blog post
* reps-general info with Discourse post link
* send to Matrix
|-
| Announcements about the Program
|
* Discourse post
* reps-general info with Discourse post link
* send to Matrix
|-
| Reps Weekly Meetings
|
* Discourse post
* reps-general info with Discourse post link and agenda
* make noise on Matrix
|-
| Council Weekly Meetings
|
* Discourse post with meeting notes
|-
| Infos about the program
|
* Newsletter to mail
* Discourse post with newsletter content for discussion
|}


== Deprecated ==
= Tweets by Reps =
With [https://github.com/mozillach/gh-projects-content-queue/ Content Queue] we can have a GitHub repository which holds issues that will be tweeted through @MozillaReps once the issue is approved.


* Remove old mailing lists ([https://bugzilla.mozilla.org/show_bug.cgi?id=1339437 Bug to track the progress on Mozilla's side])
'''Repository to hold the tweets, everyone can contribute:''' https://github.com/mozilla/reps-tweets/issues
** [https://lists.mozilla.org/listinfo/reps-comms reps-comms] (old list)
** [https://lists.mozilla.org/listinfo/reps-students reps-students] (old list)
** [https://lists.mozilla.org/listinfo/reps-council reps-council] (alias is being used, if we need it, we will create a new category on Discourse)
** [https://lists.mozilla.org/listinfo/reps-webdev reps-webdev]  mailing list (not been used for a long time, replaced by Discourse category)
* #remo-dev IRC channel merged with #participationsystems
* #remo IRC channel (still around, but not official used anymore)


= Communication Content Strategy =
'''Further information on how to file tweets:''' https://github.com/mozilla/reps-tweets/blob/master/CONTRIBUTE.md
To be decided.


= Experiments =
= Experiments =
== Connecting Facebook and Twitter provides us more flexibility and reach ==
Currently there are no ongoing communication experiments.
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.

Latest revision as of 20:33, 29 September 2023

Warning signWarning: With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.


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 Type Purpose
Discourse https://discourse.mozilla-community.org/c/reps
https://discourse.mozilla.org/c/reps/mentors
https://discourse.mozilla-community.org/c/mozillians/nda 		Asynchronous discussions 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.
Matrix Chat https://matrix.to/#/!hHmqXvUdKMtqwwHeWu:mozilla.org?via=mozilla.org&via=matrix.org&via=flak.is Synchronous chat Chat for synchronous and informal discussions about Reps and Mozilla in general. This channel is not thought to have NDA'd content (please use the Discourse NDA category for this).
Matrix Announcement Channel https://matrix.to/#/!cAyasJUyKZutejteSb:mozilla.org?via=mozilla.org&via=matrix.org&via=t2bot.io Notifications Read-only announcements, new Discourse topics and important information is shared through that announcement channel. It is not possible to respond to those. 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 Governance 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. For public discussions please use the Discourse category.
Newsletter https://discourse.mozilla.org/tags/reps-newsletter Notifications The Newsletter Team is sending out newsletters to all Reps. This includes all important information and discussions.
reps-general https://lists.mozilla.org/listinfo/reps-general Deprecated All Reps are subscribed to the reps-general mailing list. We are posting announcements and discussions with a link to Discourse. Eventually we will decommission this. This is read-only. 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.

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, ..)
Facebook Reps page https://www.facebook.com/MozillaReps/ This page is maintained by Mayur Patil, Vishal Chavan, Yofie Setiawan and Srushtika Neelakantam.

Communication Content Strategy

Our current strategy is to identify further improvements to be done. For now, in terms of publication of information, we will continue as-is. This means the following:

Topic Channels
Discussions
  • Post to start discussion on Discourse
  • Share link to reps-general
Rep of the Month
  • Blog post on Mozilla Reps blog
  • Discourse post
  • reps-general info with Discourse post link
  • send to Matrix
Goals
  • Discourse post
  • Blog post
  • reps-general info with Discourse post link
  • send to Matrix
Announcements about the Program
  • Discourse post
  • reps-general info with Discourse post link
  • send to Matrix
Reps Weekly Meetings
  • Discourse post
  • reps-general info with Discourse post link and agenda
  • make noise on Matrix
Council Weekly Meetings
  • Discourse post with meeting notes
Infos about the program
  • Newsletter to mail
  • Discourse post with newsletter content for discussion

Tweets by Reps

With Content Queue we can have a GitHub repository which holds issues that will be tweeted through @MozillaReps once the issue is approved.

Repository to hold the tweets, everyone can contribute: https://github.com/mozilla/reps-tweets/issues

Further information on how to file tweets: https://github.com/mozilla/reps-tweets/blob/master/CONTRIBUTE.md

Experiments

Currently there are no ongoing communication experiments.

Retrieved from "https://wiki.allizom.org/index.php?title=Reps/Communication&oldid=1248421"