On Fri, Apr 3, 2020 at 10:08 AM Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > > On Thu, Apr 02, 2020 at 09:54:30PM +0100, Ankur Sinha wrote: > > Maybe we shouldn't overthink this and go looking for a new "perfect" > > process. Let's just adapt the current change process, which we know > > works, and then tweak it later? Nothing in Fedora is written in stone. :) > > This all sounds good to me. :) > As Jean-Baptiste pointed out, we can already use the Changes process. So maybe let's just start there. Like I said, creating a new process, even one that is very close to the existing Changes process, is more complicated than it looks on the surface. I think what may be needed here is policy (well really guidance), not process. I'm going to try really hard to come up with something specific to discuss that may address the concerns without requiring me to develop and manage a new process. -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ council-discuss mailing list -- council-discuss@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to council-discuss-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/council-discuss@xxxxxxxxxxxxxxxxxxxxxxx
