44Communication guidelines
55========================
66
7+ The Scientific Python community uses various communications platforms to stay
8+ updated on new features and projects, to contribute by telling us what is on
9+ their mind and suggest issues and bugs, and to showcase their use cases and the
10+ tools they have built.
11+
12+ Our communications strategy is foremost guided by our :ref: `mission-statement `:
13+
14+ * We demonstrate that we care about visualization as a practice
15+ * We deepen our practice and the community’s capacity to support users,
16+ facilitate exploration, produce high quality viz, and be understandable and
17+ extensible
18+ * We showcase advanced use of the library without adding maintenance burden to
19+ the documentation and show recognition for work that may not be in the
20+ “what’s new” section.
21+ * We use communications platforms to maintain relationships with contributors
22+ who may no longer be active on GitHub, build relationships with potential
23+ contributors, and connect with other projects and communities who use
24+ Matplotlib.
25+ * In prioritizing understandability and extensiblity, we empower people working
26+ with Matplotlib to feel like they are a part of our community and that they are
27+ doing valuable community building labor.
28+
729These guidelines are applicable when acting as a representative of Matplotlib,
830for example at sprints or when giving official talks or tutorials, and in any
931community venue managed by Matplotlib.
1032
11-
1233.. _communication-channels :
1334
1435Official communication channels
@@ -148,12 +169,32 @@ Visual media in communications should be made as accessible as possible:
148169 * Do not make bright, strobing images.
149170 * More guidelines at https://webaim.org/techniques/images/.
150171
172+ .. _social-media-brand :
151173
152174Social media
153175============
154176
155- Please follow these guidelines to maintain a consistent brand identity across
156- platforms.
177+ Matplotlib aims for a single voice across all social media platforms to build and
178+ maintain a consistent brand identity for Matplotlib as an organization. This
179+ depersonalization is the norm on social media platforms because it enables
180+ constructive and productive conversations; People generally feel more comfortable
181+ giving negative and constructive feedback to a brand then to specific contributors.
182+
183+ The current Matplotlib voice and persona aims to be kind, patient, supportive and
184+ educational. This is so that it can de-escalate tensions and facilitate
185+ constructive conversations; being perceived as negative or
186+ argumentative can escalate very fast into long-lasting brand damage, being
187+ perceived as personal leads to aggression and accusations faster than an
188+ impersonal account, and being perceived as friendly and approachable leads to
189+ higher engagement. Instead of speaking with a directive authority, which can be
190+ intimidating and lead to negative engagement, it speaks as a peer or educator to
191+ empower participation. The current voice encourages more input from folks we
192+ engage with, and also makes it possible for folks who are not in the core team
193+ to participate in managing the account.
194+
195+ While the :ref: `brand identity <social-media-brand >` is casual, the showcased
196+ content is high quality, peer-led resource building. Please follow these
197+ guidelines to maintain a consistent brand identity across platforms.
157198
158199Persona
159200-------
0 commit comments