11.. _communications-guidelines :
22
3- ========================
4- Communication guidelines
5- ========================
3+ ==========================
4+ Community management guide
5+ ==========================
66
7- These guidelines are applicable when acting as a representative of Matplotlib,
7+ These guidelines are applicable when ** acting as a representative ** of Matplotlib,
88for example at sprints or when giving official talks or tutorials, and in any
99community venue managed by Matplotlib.
1010
11+ Our approach to community engagement is foremost guided by our :ref: `mission-statement `:
12+
13+ * We demonstrate that we care about visualization as a practice
14+ * We deepen our practice and the community’s capacity to support users,
15+ facilitate exploration, produce high quality visualizations, and be
16+ understandable and extensible
17+ * We showcase advanced use of the library without adding maintenance burden to
18+ the documentation and recognize contributions that happen outside of the github
19+ workflow.
20+ * We use communications platforms to maintain relationships with contributors
21+ who may no longer be active on GitHub, build relationships with potential
22+ contributors, and connect with other projects and communities who use
23+ Matplotlib.
24+ * In prioritizing understandability and extensiblity, we recognize that people
25+ using Matplotlib, in whatever capacity, are part of our community. Doing so
26+ empowers our community members to build community with each other, for example
27+ by creating educational resources, building third party tools, and building
28+ informal mentoring networks.
1129
1230.. _communication-channels :
1331
1432Official communication channels
1533===============================
34+ The Scientific Python community uses various communications platforms to stay
35+ updated on new features and projects, to contribute by telling us what is on
36+ their mind and suggest issues and bugs, and to showcase their use cases and the
37+ tools they have built.
38+
1639The following venues are managed by Matplotlib maintainers and contributors:
1740
1841* library and docs: https://github.com/matplotlib/matplotlib
@@ -148,12 +171,32 @@ Visual media in communications should be made as accessible as possible:
148171 * Do not make bright, strobing images.
149172 * More guidelines at https://webaim.org/techniques/images/.
150173
174+ .. _social-media-brand :
151175
152176Social media
153177============
154178
155- Please follow these guidelines to maintain a consistent brand identity across
156- platforms.
179+ Matplotlib aims for a single voice across all social media platforms to build and
180+ maintain a consistent brand identity for Matplotlib as an organization. This
181+ depersonalization is the norm on social media platforms because it enables
182+ constructive and productive conversations; People generally feel more comfortable
183+ giving negative and constructive feedback to a brand than to specific contributors.
184+
185+ The current Matplotlib voice and persona aims to be kind, patient, supportive and
186+ educational. This is so that it can de-escalate tensions and facilitate
187+ constructive conversations; being perceived as negative or
188+ argumentative can escalate very fast into long-lasting brand damage, being
189+ perceived as personal leads to aggression and accusations faster than an
190+ impersonal account, and being perceived as friendly and approachable leads to
191+ higher engagement. Instead of speaking with a directive authority, which can be
192+ intimidating and lead to negative engagement, it speaks as a peer or educator to
193+ empower participation. The current voice encourages more input from folks we
194+ engage with, and also makes it possible for folks who are not in the core team
195+ to participate in managing the account.
196+
197+ While the :ref: `brand identity <social-media-brand >` is casual, the showcased
198+ content is high quality, peer-led resource building. Please follow these
199+ guidelines to maintain a consistent brand identity across platforms.
157200
158201Persona
159202-------
@@ -213,11 +256,10 @@ Retired campaigns
213256Changing the guidelines
214257=======================
215258
216- As the person tasked with implementing communications, the `community-manager `_
217- should be alerted to proposed changes to the communications guidelines. Similarly,
218- specific platform guidelines (e.g. twitter, instagram) should be reviewed by the
219- person responsible for that platform, when different from the community manager.
220- If there is no consensus, decisions about communications guidelines revert to
221- the community manager.
259+ As the person tasked with implementing these guidelines, the `community-manager `_
260+ should be alerted to proposed changes. Similarly, specific platform guidelines
261+ (e.g. twitter, instagram) should be reviewed by the person responsible for that
262+ platform, when different from the community manager. If there is no consensus,
263+ decisions about guidelines revert to the community manager.
222264
223265.. _community-manager : https://matplotlib.org/governance/people.html#deputy-project-leads
0 commit comments