On Mon, 2018-02-19 at 14:14 -0500, Matthew Miller wrote: > On Sun, Feb 18, 2018 at 05:35:12PM -0600, Dennis Gilmore wrote: > > I would like to have us look at not only the processes for how we build > > and ship the distribution. I have some ideas for how we can keep the > > important pieces of how we build and ship things today, but give us the > > flexibility to have the peices be more independent and controlled. > > Okay, I'm a believer. :) > > > than in the past, there is a long way to go. We may even need to take a > > time out in order to focus on making fundamental changes to how we > > manufacture Fedora. > > We should make a plan for this. It's been almost five years (!) since > we took the year for F20, and maybe it's time soon to do it again. A big +1 to Dennis here. To be clear, I'm not saying everything is fine and we shouldn't change anything. I was just a bit worried about the way the initial proposal appeared to be based on a belief that basically no-one cared about composes right now (as this would be a mistaken starting point that might lead to the loss or unnecessary laborious recreation of existing knowledge and practices). I entirely agree with Dennis that another flaw in the initial proposal is that it's based on trying to smooth out the operation of the existing process, whereas it would be much better to focus on making the process better. So long as we're starting from an accurate assessment of how the current process works (including the fact that several people follow it quite closely and attempt to remove the grit in the gears, and have quite a lot of domain-specific knowledge about doing that), and we don't just think about how to smooth out that process but think about making it better, I think we'll get somewhere useful. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
