Create a communications handbook for Fedora Council #536
Labels
No labels
category
budget
category
code-of-conduct
category
docs
category
elections
category
events
category
initiatives
category
mindshare
category
policies
category
spending-request
category
Strategy Summit
category
trademarks
Next Meeting
state
resolved
good first issue
help wanted
needs
changes
needs
reporter feedback
needs
triage
needs
vote
role
engineering
role
fca
role
foa
role
fpl
role
initiative lead
role
mindshare
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
council/tickets#536
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
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.
See linked Fedora Discussion topic for Ticket #536
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.
Metadata Update from @jflory7: