Request for Review of Flock 2026 CFP themes by 2025-11-11 #86
Labels
No labels
category
budget
category
docs
category
limesurvey
category
meta
category
physical events
category
swag
category
virtual events
good first issue
help wanted
needs
event report
needs
reporter feedback
needs
vote
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
team
advocates
team
ambassadors
team
commops
team
council
team
design
team
docs
team
g11n
team
marketing
team
mindshare
team
websites-apps
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
mindshare/tickets#86
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
Provide feedback, input, and/or approval of Flock 2026 Call for Proposals (CFP) themes by Tuesday, 11 November 2025
Background
The Flock Organizer Team is getting the party back together for 2026. One of the many things we are working on is the CFP to open before the end of this year. (Crazy, right??) As part of this process, we invite input from the various Fedora leadership bodies (Council, FESCo, Mindshare Committee, and EPEL Steering Committee) on the themes we have come up with so far.
Since we are planning to open the CFP before the end of the year, we do have a deadline for providing input, feedback, and comments. I am formally requesting any feedback on the 2026 CFP themes no later than Tuesday, 11 November 2025. This will leave enough time for the Flock Organizer Team to address feedback and open the CFP before the end of the year.
This is not a guarantee we will implement every single piece of feedback. We are asking four diverse committees for feedback, after all! However, the Flock Organizer Team respects the perspective and input of all our leadership bodies to help influence the content we want to have at Flock 2026. So, we ask for your collaborative input to help us build a community conference that we are all proud of.
Details
At the time of opening this ticket, we have come up with four themes. These themes do not necessarily correspond to tracks or how the actual schedule will be organized. However, it will be more like "tags" that a submitter can apply to their content. In an ideal world, every accepted session at Flock will clearly fit into at least one theme.
Here they are:
Outcome
Mindshare Committee discusses and reviews the themes, provides input as comments to this GitLab ticket no later than Tuesday, 11 November 2025, and the Flock Organizer Team incorporates as much thoughtful feedback as we can before opening the CFP later this year.
set status to To do
changed start date to October 23, 2025 and changed due date to November 11, 2025
assigned to @jwwheeler
Some verbiage improvements first.
The improvements should more or less cover the narrative that I am suggesting here but here's a brief rundown anyway.
I am attempting to improve the submitter's experience by making the titles more concise and impactful. Nothing wrong with yours, to be honest but if these show up as either radio buttons or dropdown elements, I would much rather if the text cuts to the chase.
I also expanded upon to the description for the "Features" section, based on the parts of the engineering fraternity in Fedora Project that I have found to be more impactful. This also ends up giving visibility to our lesser appreciated group of contributors.
"Expanding" in place of "Open" - We are not only keeping an apple on the top of @jwwheeler's head (metaphorically speaking) but we are also providing the contributors with the means to... well, you know. I wanted for our phrasing to represent that fact.
I removed the occurrence of "as a contributor conference", because that equally applies on other parts too, doesn't it? Instead, I tried filling that part with more information pertaining to that specific theme while making it contributor-focused all the same.
If we are being aspirational with collaboration and onboarding, we should be the same with mentorship too - both, in spirit and in words. Also, I have added the "maintenance" part in the Fedora Linux release process because it is equally important.
I made the phrasing a little more community-first with the words like "empowerment", "advancement" etc. I know it for a fact that it is not just me who feels little more positive with the use of these words, no matter how managerial they might end up looking.
That being said, +1 to the proposed theme (with the minor aforementioned changes).
Time escaped me on this one 😅
I like the proposed themes - it’s a nice way to make sure all talks are related. I’m happy to give a +1 to this!
Thanks for the feedback, y'all! As the deadline has passed, I am going to close this issue. Over the next few weeks, the Flock CFP team will work on integrating the feedback collected from Mindshare and the other Fedora governance bodies back into the themes before we launch the CFP in December.
Closing this issue as complete. 🌊
set status to Done
Thank you to everyone who reviewed and provided feedback on the Flock to Fedora 2026 Call for Proposals (CfP) themes. The review process is now concluded, having collated input from the Fedora Council, FESCo, the Mindshare Committee, and the EPEL Steering Committee. Our goal for the revisions was to balance technical precision with community inclusivity, ensuring that every contributor sees a "home" for their work in these tracks.
Summary of Changes
Here is the final list of themes that will go live with the CfP:
Thank you again for helping us refine the direction of the conference!