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.
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.
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:
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.
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.
Log in to comment on this ticket.