Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> writes: > So, from a purely "what are the rules?" view, the Change process says: > FESCo will vote to approve or deny a change proposal in accordance with > the FESCo ticket policy. > > ... and I won't quote all of that, but looking at > https://docs.fedoraproject.org/en-US/fesco/#_ticket_policy... > I don't see any violations, either in the letter or the spirit of what is > written. OTOH: "The motivation for the Changes process is to raise the visibility of planned changes and make coordination and planning effort easier. It is nearly impossible to follow all changes happening in a big project such as Fedora. By providing a mechanism for sharing changes, it is easier for contributors to know what is coming and to ensure that we can address impacts of changes well before the release date. Change proposals should be shared as early as possible, before the change is implemented and even in the very early state of the idea, to gather community feedback and review." One could argue that taking a change that was widely discussed and clearly rejected, then initiating a sudden revote without at least as much publicity, undercuts the "easier for contributors to know what is coming" or "gather community feedback and review" point of the whole thing. - FChE _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
