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. 3. What would a brand new process bring the Fedora Linux distribution that our current one does not? I do for the most part agree with much of what has been suggested and am a firm supporter of reviewing process and ways of doing things periodically for improvements, (mostly Bens suggestions as a previous change wrangler), but I would ask folks to examine how much 'hands-on' involvement they have in the actual mechanics of _processing_ the changes before suggesting ways to engineer a brand new way to do it. What is it you are missing from the current process in your own individual needs? Finding a fix to _that_ might be more simpler than we think. 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. P.P.S There really is a lot of change happening - Fedora Forge, Bugzilla ....thing..., maybe we see how the changes process adapts to these bigger items first and then see what were missing and where from. On Tue, Jun 30, 2026 at 12:30 PM Kashyap Chamarthy <[email protected]> wrote: > On Tue, Jun 30, 2026 at 11:56:51AM +0200, Pierre-Yves Chibon wrote: > > On Tue, Jun 30, 2026 at 11:45:34AM +0200, Kashyap Chamarthy wrote: > > [...] > > > The change process is not just about: here is an idea + some discussions > + a > > decision. > > It's also about the implementation of that idea, tracking the work > resulting > > from this idea, ensuring that bugs introduced by that idea are > identified, > > centralized and acted on so that the person introducing the idea deals > with the > > fall-out, not someone else. > > Of course, implementation and its consequences are the core of it all. > I did consider it. If you read the other email I mentioned with an > OpenStack "spec" template, it show how implementation and the > consequences are tracked. > > Now, I realize, a change spanning an entire Linux distribution is > different than traditional upstreams. But OpenStack is a close enough > analogy -- it's an "umbrealla project" that is a collection of various > upstream projects. Their "spec" model is worth looking into (see links > in my previous email) and adapting to Fedora's needs. > > > All this to say, I think we need to be looking at the process in its > entirety > > before focusing on some part that we'd like to change in order to ensure > we do > > not in fact lose some capabilities that we had before and which, turns > out, we > > want to keep. > > Sure, that only makes sense. I asked as much in my other reply. To be > clear, I'm not implying to make any changes in isolation; that'd be > silly. > > > -- > Kashyap Chamarthy / Red Hat / RISC-V and Fedora > > -- > _______________________________________________ > 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 > -- 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
