Hi Aoife,

Thanks for raising these questions. This is a helpful way to frame the problem.

On 6/30/26 9:21 AM, Aoife Moloney wrote:
Hello everyone, actual Change Wrangler here so I thought I'd weigh in :)

Couple of questions I'd like to understand:

1. How has the current change process poorly impacted you? For example, are you a change owner who disliked X or Y? Are you a driveby contributor who doesn't like the devel/discourse split? Are you a FESCo member who needs more of A or B in the voting ticket?

2. What level of involvement do you have in processing the changes, and what parts do you find taxing? Eg are you a change owner who doesn't enjoy interfacing with the wiki? Are you FESCo member who finds the tickets less than optimal to review? Are you QA who needs better tracking of changes, etc.

As someone who has proposed Changes, I find dealing with the wiki to be really cumbersome. I'm used to editing technical documentation stored in git in markdown in my preferred text editor or using a standard word processor for other types of writing. The Wiki brings another syntax and another interface that I have to deal with.

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).
3. What would a brand new process bring the Fedora Linux distribution that our current one does not?

Ideally, to address the existing pain points and make the process smoother for the various people and roles involved.

P.S I would LOVE to not have to post to discourse and devel-announce and really like the idea of the weekly change round up post on discourse and keep main conversation to the mailing list.

+1. As I said, I don't like the split discussion between devel@ and Discourse. As a FESCo member or not a FESCo member, it makes it really hard to keep track of what's going on and adds repetition and confusion to discussions.

All the best,
Maxwell
--
_______________________________________________
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