INFO: Present Justin Wheeler Jef Spaleta @nimbinatus Peter Boy (ServerWG, Docs) Akashdeep Dhar Petr Bokoc ffmancera (@nimbinatus:matrix.org, 15:12:59)
TOPIC:Ticket 555 Council Strategy Summit https://pagure.io/Fedora-Council/tickets/issue/555(@jspaleta:fedora.im, 15:14:14)
INFO: This is the final week for feedback on the Fedora Council Strategy Summit in February 2026. On Friday, Jef and Justin will shape up the agenda into a final form that we can all keep in mind as we head off into the year-end holidays. (@jflory7:fedora.im, 15:21:14)
INFO: The intent is that we will NOT make huge shifts in the agenda in January, and the only changes will be refinements to the existing topics on the agenda. This addresses feedback received from a few years of having a firm agenda prepared in the weeks before we arrive together, instead of the days before we arrive together. (@jflory7:fedora.im, 15:22:08)
HALP: If you feel like a topic is missing from the agenda that you care about or the community cares about and urgently needs Council attention, this is the last week to bring it up! (@jflory7:fedora.im, 15:22:50)
INFO: Additionally, while we do have a Council-private mailing list thread, we can continue using the older, longer Council-private thread or the public Fedora Discussion topic, which has received some engagement. (@jflory7:fedora.im, 15:23:29)
INFO: Fervent discussion ensued on the draft. Opinions were given, feedback was sought, and we ended up running out of time! However, clearly there is some actionable feedback on this as we move forward. (@jflory7:fedora.im, 15:56:58)
INFO: There is doubt on whether a long, detailed document is something that should be maintained at the top-level of project docs. It is unclear to some whether the impact we want this document to have could be achieved. Feedback was given that making it shorter and more concise would be useful, so it doesn't get overlooked so easily. (@jflory7:fedora.im, 15:58:03)
IDEA: An idea was raised about having automation in issues/PRs that adds a note about slow review/response time and tries to explain the dynamics of our community. This might be better than total radio silence when someone raises feedback. However, this feature does not exist today and would have to be built out. (@jflory7:fedora.im, 15:58:54)
IDEA: We may be able to offload the content generation piece to other communities who have faced the same challenges. This is not a uniquely Fedora problem. We can try and interpret what has already been written elsewhere into a Fedora context. (@jflory7:fedora.im, 16:00:10)
INFO: We ran out of time to fully get to a closing position on this ticket, but anticipate that feedback will continue in the new year. (@jflory7:fedora.im, 16:00:35)
ACTION: @council Leave feedback on specifics in the Google Doc, and for high-level points about where the document should live and who it is being written for, use the Fedora Discussion topic. (@jflory7:fedora.im, 16:01:07)
HALP: If possible, get your feedback in before the year-end holiday season, as we all know there is a collective, social amnesia for anything in December that is not explicitly written down! (@jflory7:fedora.im, 16:01:40)
Meeting ended at 16:03:08 UTC
Action items
@council Leave feedback on specifics in the Google Doc, and for high-level points about where the document should live and who it is being written for, use the Fedora Discussion topic.