On Wed, Sep 5, 2018 at 1:50 PM Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > We used to always have a Change submitted for the GNOME update, but that > stopped, I assume because it felt like kind of rote bureaucracy rather than > helpful, since it was basically the same every time. Maybe it's useful after > all to help keep communications open for situations like this? > It may come as no surprise given my role, but I'm in favor of continuing to submit Change proposals for GNOME updates and similar. I'd be open to a "shortcut" version of the Change process that essentially says "hey, we're doing this again". But this way we'd get visibility across teams and externally. For better or for worse, our Change list is a starting point for marketing and PR, so it's beneficial to have these sorts of things visible externally, too. -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
