Oh I am awful for posting inline so Im going to quote and copy-paste :) @Björns thank you for sharing your experience. This definitely helps me understand the pain points by providing concrete examples of where the process failed, or was less optimal.
@Maxwell G Björns experience addresses all of your issues in an example that we could all perhaps use to iterate any changes on. For the Wiki stuff: I don't have a good idea for here. Some potentially better ideas have already been mentioned that could replace the wiki later. I do agree it's not great to edit, but it's also not too bad either, and I think we should try keep this entry point as kind as possible for people to want to engage in the process. The wiki is just more manual (the difficult-to-read announcement that Bjorn mentioned was me not physically editing out the angle brackets before hitting send :-/ ) Assigning Glitches: Ironically, its scripting that auto-assigns change owners to bugs. Sometimes even technology seems to fail :) As we are moving from Bugzilla at some point though, I would be reluctant to make any changes on this part yet. Rather, I will resume (and be more vigilant on) reviewing each bz as they are created for the correct assignee. Same for FESCo ticket assignees, although Ive reported an issue there today with that https://forge.fedoraproject.org/fesco/tickets/issues/3630 Trackers being closed/badges being assigned: Yeah that was probably a consequence of me being absent. These tasks in particular could use more/better/any automation though. Again, the trackers are tied to Bugzilla so I would not make any changes just yet, but I appreciate this conversation happening now so we are at least thinking about what changes we could and want to make soon. Should all tracker bugs be closed by the change owner when the change is complete? Should a script mass-close them after N-amount of weeks post release? This is more policy I think than implementation, but its clearly a gap that we should cover. For conversation-split: I wonder if dropping the conversation from discourse is a good first step, and instead supplementing that space with the 'weekly roundup'. If chnage owners are finding it hard to be present in both places (because that *is* hard), then why not start with a ticket to FESCo to request reducing the conversation space from devel-list and discourse to just discourse? On Tue, Jun 30, 2026 at 5:17 PM Adam Williamson <[email protected]> wrote: > > On Tue, 2026-06-30 at 10:51 -0500, Maxwell G wrote: > > I am also under the impressions that it's difficult to properly process > > Changes from the wiki without a lot of error-prone, manual steps. I have > > seen various issues with the current process where formatting of > > Discourse posts and FESCo tickets is messed up, Change owners aren't > > CCed on FESCo tickets and Bugzilla trackers (which caused process > > delays), Changes get stuck in one of the steps of the process, etc. I > > know there were some new AI-assisted tooling introduced recently, but > > that only seemed to make problems worse. I was hoping that switching to > > a format that was easier to work with in a scripted manner would help > > with some of these issues, but maybe I'm off base (please do tell me if > > I am). > > Well, there's an important human element here: Aoife was off work for > several months and only came back recently. Allison King was covering > for her, but she was doing it in addition to her regular work and of > course Allison hasn't had the experience with the process that Aoife > has. > > So specific issues in the last several months are very likely to be > related to that. Of course, if the process had more guardrails and > automation, it would probably mean fewer things would go wrong when the > human(s) with most experience with the process are unavailable or when > we're handing off the role between humans, and that would definitely be > a benefit. > -- > Adam Williamson (he/him/his) > Fedora QA > Fedora Chat: @adamwill:fedora.im | Mastodon: @[email protected] > https://www.happyassassin.net > > > -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
