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



-- 
_______________________________________________
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

Reply via email to