Flock 2023

Fedora Project has always relied on changemakers who work with the CommOps team. Historically, this team would go and bridge gaps between ideation, planning and execution by uniting one or multiple teams together. In the recent past, we have had a lot of changes in the community and many of them couldn't get facilitated due to inactivity on the part of the CommOps team. This is to bring about the change and revive the CommOps as CommOps 2.0. As a part of this process, we would like the workshop to focus on community members and ask them a few key questions

How do Fedora change-makers make changes in Fedora? What avenues exist?
What SOP will they follow before bringing a funding/spending request to the Mindshare Committee? Do they follow a SOP or common process?
Should we keep the Ambassador rep roles, or should they evolve into something else? Changeset wranglers?
What duties and responsibilities should a community change wrangler have?
What balance is there between a team supporting on community ops, and an individual or individuals who are change wranglers?
Team vs. committee, volunteer vs. appointed. What is the balance?

We will be using various strategies to take out as much as information we can which will help us to shape:

1. CommOps 2.0 initiative as a part of the council
2. To write and finish SOPs which will help the community propose change (aka like a changes process)
3. Have a change wrangler who can help bridge the gap between the engineering and community side of things by announcing and helping both parties.