Create a communications handbook for Fedora Council #536

Open
opened 2025-06-16 15:50:36 +00:00 by jflory7 · 3 comments
Owner

Summary

This ticket proposes the creation of a communications handbook to establish a consistent strategy and clear guidelines for how the Fedora Council communicates with the community and other project bodies.

Background

This proposal originates from a face-to-face meeting between Fedora Council and FESCo delegates, where a lack of consistent communication strategy from the Council was identified as a key challenge. Unlike FESCo, which has well-established communication methods, the Council's approach has been inconsistent. This perception was reinforced during the Flock conference, where community members expressed that the Council can feel "invisible and not very approachable." Adopting a more deliberate and consistent communication practice is essential for improving the Council's visibility, effectiveness, and connection to the community.

Details

The goal is to collaboratively create a communications handbook, not to prescribe a solution upfront. As Fedora Community Architect (FCA), I am self-assigning myself to facilitate this process, which will follow these steps:

  1. Discuss this ticket at the next Fedora Council meeting. The goal for the meeting discussion is to reflect on our current communication methods, their effectiveness, and the value of different channels.
  2. Using the feedback from this discussion, I will create a first draft of the communications handbook.
  3. The first draft will be shared with other Fedora governance bodies—including FESCo, the Mindshare Committee, and the EPEL Steering Committee—for a review and feedback period.
  4. The draft will also be shared publicly with the wider Fedora community. We encourage participation from anyone who has constructive ideas on how the Fedora Council can better communicate.
  5. The FCA will incorporate the collected feedback to finalize the handbook for formal approval by the Council.

Outcome

The result will be a Council-approved communications handbook that, through its consistent use, makes Council activities more visible, transparent, and approachable to the entire Fedora community.

# Summary This ticket proposes the creation of a communications handbook to establish a consistent strategy and clear guidelines for how the Fedora Council communicates with the community and other project bodies. # Background This proposal originates from a face-to-face meeting between Fedora Council and FESCo delegates, where a lack of consistent communication strategy from the Council was identified as a key challenge. Unlike FESCo, which has well-established communication methods, the Council's approach has been inconsistent. This perception was reinforced during the Flock conference, where community members expressed that the Council can feel "invisible and not very approachable." Adopting a more deliberate and consistent communication practice is essential for improving the Council's visibility, effectiveness, and connection to the community. # Details The goal is to collaboratively create a communications handbook, not to prescribe a solution upfront. As Fedora Community Architect (FCA), I am self-assigning myself to facilitate this process, which will follow these steps: 1. Discuss this ticket at the next Fedora Council meeting. The goal for the meeting discussion is to reflect on our current communication methods, their effectiveness, and the value of different channels. 2. Using the feedback from this discussion, I will create a first draft of the communications handbook. 3. The first draft will be shared with other Fedora governance bodies—including FESCo, the Mindshare Committee, and the EPEL Steering Committee—for a review and feedback period. 4. The draft will also be shared publicly with the wider Fedora community. We encourage participation from anyone who has constructive ideas on how the Fedora Council can better communicate. 5. The FCA will incorporate the collected feedback to finalize the handbook for formal approval by the Council. # Outcome The result will be a Council-approved communications handbook that, through its consistent use, makes Council activities more visible, transparent, and approachable to the entire Fedora community.
Author
Owner
## [_See linked Fedora Discussion topic for Ticket #536_](https://discussion.fedoraproject.org/t/fedora-council-tickets-ticket-536-create-a-communications-handbook-for-fedora-council/155885)
Owner

We unfortunately didnt get to this in this weeks meeting, but perhaps we can discuss it on discourse instead and ideate there? I have some questions that would be good to get feedback on that likely feed into this overall comms plan.

We unfortunately didnt get to this in this weeks meeting, but perhaps we can discuss it on discourse instead and ideate there? I have some questions that would be good to get feedback on that likely feed into this overall comms plan.
Author
Owner

Metadata Update from @jflory7:

  • Assignee reset
  • Issue untagged with: Next Meeting
**Metadata Update from @jflory7**: - Assignee reset - Issue **un**tagged with: Next Meeting
jflory7 added this to the Fedora Linux 45 milestone 2026-02-18 23:49:36 +00:00
Sign in to join this conversation.
No milestone
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
council/tickets#536
No description provided.