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
