Kevin Kofler via devel wrote:
> Still, it gives an extremely bad impression of rushing this through
> without giving anybody the chance to object.
>
> I also do not see why this needed to be approved for F38 on such a short
> notice and could not wait for F39.
PS: The impression I get is that everything was deliberately rigged so that
the vote would end up the way it did:
1. A new ticket was filed, in order to exclude the participants of the
previous discussion.
2. The people watching the old ticket were NOT notified.
3. The Tools Team was NOT notified.
4. The proponents of the Change, on the other hand, WERE notified.
So, with all of the above, the discussion participants were preselected to
only include people in favor of the change.
5. The ticket was filed in the middle of the holiday season. Many people in
Europe are on vacation until today.
6. There was NO thread about the reopening of the discussion on the mailing
list. The first message that mentioned the issue on the mailing list was
"Schedule for Tuesday's FESCo Meeting (2023-01-03)" from 2023-01-03 09:39
UTC, only 7 hours 21 minutes before the meeting. This is in contrast to the
Change policy requiring at least a week between the mailing list
announcement and opening the FESCo ticket.
7. Only 4 days had elapsed between the (unannounced) opening of the ticket
and the vote. This is clearly insufficient. The one week in the Change
policy that I cited above is designed as a minimum time for discussion.
8. The change was approved only 2 weeks before the mass rebuild, leaving
little to no time to revert it in the contigency case.
So, this ensured that whoever was deliberately NOT invited had no chance to
find out by themselves and intervene before it was too late.
This strikes me as extremely intransparent and undemocratic.
Therefore, I hereby request that the vote be annulled as having happened in
violation of the Change policy.
Kevin Kofler
_______________________________________________
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
