11.. _communications-guidelines :
22
3- ========================
4- Communication guidelines
5- ========================
3+ ===========================
4+ Community engagement guidel
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+ The Scientific Python community uses various communications platforms to stay
12+ updated on new features and projects, to contribute by telling us what is on
13+ their mind and suggest issues and bugs, and to showcase their use cases and the
14+ tools they have built.
15+
16+ Our communications strategy is foremost guided by our :ref: `mission-statement `:
17+
18+ * We demonstrate that we care about visualization as a practice
19+ * We deepen our practice and the community’s capacity to support users,
20+ facilitate exploration, produce high quality visualizations, and be
21+ understandable and extensible
22+ * We showcase advanced use of the library without adding maintenance burden to
23+ the documentation and recognize contributions that happen outside of the github
24+ workflow.
25+ * We use communications platforms to maintain relationships with contributors
26+ who may no longer be active on GitHub, build relationships with potential
27+ contributors, and connect with other projects and communities who use
28+ Matplotlib.
29+ * In prioritizing understandability and extensiblity, we recognize that people
30+ using Matplotlib, in whatever capacity, are part of our community. Doing so
31+ empowers our community members to build community with each other, for example
32+ by creating educational resources, building third party tools, and building
33+ informal mentoring networks.
1134
1235.. _communication-channels :
1336
@@ -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-------
0 commit comments