On Fri, Mar 11, 2022 at 12:45:05PM -0800, Adam Williamson wrote: > I'm +1 to this; it makes sense for me that Council should be able to > veto/waive blocker decisions in this specific context, I just wanted > there to be a proper mechanism for it. This seems like a reasonable way > to achieve that. First, I want to (in complete non-ironic sincerity) express appreciation to all of y'all process-oriented folks who make sure this stuff stays on track. Continuing from https://pagure.io/Fedora-Council/tickets/issue/389#comment-785815... I suppose as an engineering collaboration (releng, devel, qa...) it may have been better for us to direct this at all of those teams, or maybe FESCo. FESCo has a "make this a blocker" button... I kind of feel an itch for a generalized "sometimes stuff comes up" lever that goes the _other_ direction, rather than a very specific carve-out. We wouldn't be here if I (well, the Council, but I'll go ahead and say specifically _me_) had made sure we'd done the proper followup around Cloud "de-editioning" several years ago, and I don't think there's likely to be a case where this new policy is actually ever used again — if there is, that'd signal another failure. -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-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/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
