| |
@@ -0,0 +1,71 @@
|
| |
+ include::ROOT:partial$attributes.adoc[]
|
| |
+
|
| |
+ = Communications Policy
|
| |
+ Justin W. Flory, Fedora Council, Fedora community, and others
|
| |
+ v1.0.0-DRAFT, 2023-08-30
|
| |
+ :policy-impacted-teams: Specific Fedora Committees and Teams
|
| |
+
|
| |
+
|
| |
+ xref:#definitions-leadership[{policy-impacted-teams}] are required to maintain an xref:#definitions-presence[active presence] on xref:#definitions-platforms[official communications platforms].
|
| |
+
|
| |
+
|
| |
+ [[rationale]]
|
| |
+ == Rationale
|
| |
+
|
| |
+ {policy-impacted-teams} decide, plan, and execute actions that impact many parts of Fedora Linux and the community.
|
| |
+ {policy-impacted-teams} should be discoverable so that the community has clear guidance on how and where to interact with leadership groups.
|
| |
+ Since the Fedora community uses a diverse range of communication platforms and tools in our work, it is challenging to always know the right place to take a query or discussion topic.
|
| |
+ Therefore, it is important for {policy-impacted-teams} to share a common approach to where and how we communicate.
|
| |
+
|
| |
+ There are two main benefits for {policy-impacted-teams} to share a common communication platform:
|
| |
+
|
| |
+ . *Set expectations with collaborators*:
|
| |
+ Anyone who needs to engage with {policy-impacted-teams} should feel empowered on how and where to do that.
|
| |
+ Providing one common place and account for engaging with {policy-impacted-teams} makes it easier to coordinate and collaborate, for members of leadership committees but also community members.
|
| |
+ We should set expectations so that anyone in the community knows what is required in order to reach {policy-impacted-teams}.
|
| |
+ . *Set an example for the community*:
|
| |
+ {policy-impacted-teams} set the tone for the community.
|
| |
+ We model best practices and invite others in the community to join us in the future of the project.
|
| |
+ Therefore, {policy-impacted-teams} should be leaders in innovating how we communicate as a large, decentralized project.
|
| |
+ By using common platforms, we provide models that others can take and learn from, in the true Open Source Way.
|
| |
+
|
| |
+
|
| |
+ [[definitions]]
|
| |
+ == Definitions
|
| |
+
|
| |
+ This policy does not intend to provide universal definitions for all the terms used within, but some terms require clarification so this policy is clear.
|
| |
+
|
| |
+ [[definitions-teams]]
|
| |
+ === {policy-impacted-teams}
|
| |
+
|
| |
+ {policy-impacted-teams} are recognized decision-making bodies that chart the future of the project and are important for ensuring critical work happens every Fedora release.
|
| |
+ For the purpose of this policy, the following groups are considered {policy-impacted-teams}:
|
| |
+
|
| |
+ * xref:council::index.adoc[Fedora Council]
|
| |
+ * xref:diversity-inclusion::index.adoc[Fedora Diversity, Equity, & Inclusion Team]
|
| |
+ * xref:fesco::index.adoc[Fedora Engineering Steering Committee (FESCo)]
|
| |
+ * xref:mindshare-committee::index.adoc[Fedora Mindshare Committee]
|
| |
+
|
| |
+ [[definitions-platforms]]
|
| |
+ === Official communications platforms
|
| |
+
|
| |
+ Official communications platforms are first-priority platforms where Fedora community members discuss, work, and socialize with each other.
|
| |
+ These platforms are given heavier weight in terms of outages, there is a degree of uptime reliability guaranteed, and they are the _only_ communications platforms that can be considered officially used by the Fedora Project.
|
| |
+ This is contrast to other platforms that fall under the xref:council::policy/community-publishing-platforms.adoc[Community Publishing Platforms] policy.
|
| |
+
|
| |
+ For the purpose of this policy, the following platforms are considered official communications platforms:
|
| |
+
|
| |
+ * Asynchronous:
|
| |
+ *Fedora Discussion* on https://discussion.fedoraproject.org/
|
| |
+ * Synchronous:
|
| |
+ *Fedora Chat* on https://chat.fedoraproject.org/
|
| |
+
|
| |
+ [[definitions-presence]]
|
| |
+ === Active presence
|
| |
+
|
| |
+ An active presence means that there is someone or several people from the Fedora leadership group who take responsibility to handle incoming topics and feedback shared in the official communications platforms.
|
| |
+ The person(s) responsible for handling inbound discussion should be a legitimate representative of the {policy-impacted-teams}.
|
| |
+ This policy does not specify how long inbound discussion and queries should be responded to, as this is in the best interest of the Fedora leadership group to determine for themselves.
|
| |
+
|
| |
+ This policy does not intend to antagonize a Fedora leadership group if they do not respond to all and every topic in the official communications platforms.
|
| |
+ However, if it becomes habitual for topics and feedback to be routinely ignored by {policy-impacted-teams} on official communications platforms, the Fedora Council is committed to addressing this challenge on a case-by-case basis.
|
| |
mattdm commented a year ago
The rendered version you showed has this a "Fedora Leadership teams". Is this a change, or is that defined somewhere else? In any case, I think we should spell out exactly what is meant by the term near the beginning of this document somewhere -- I know it's not a long doc but it feels kind of inverted to learn the definition later.