From b9b0c81f8d2724b3450b48d42b26aa5fa3066ed1 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Feb 26 2024 11:16:31 +0000 Subject: voting policy: clarify/change voting policy for Non-resp. maintainers In the description of the general voting rules, mention that NRM ticket have their own policy and the usual voting policy does not apply to them. In the description of the NRM voting, mention that the policy is different. Also change the text to say that the ticket will be added to meeting agenda only if there's a disagreement. Previous text implied that the ticket would be handled in a meeting if no votes were made. The new text matches the actual practice that was being followed. Fixes https://pagure.io/fesco/issue/3166. --- diff --git a/fesco/modules/ROOT/pages/Policy_for_nonresponsive_package_maintainers.adoc b/fesco/modules/ROOT/pages/Policy_for_nonresponsive_package_maintainers.adoc index 724426f..3b26ece 100644 --- a/fesco/modules/ROOT/pages/Policy_for_nonresponsive_package_maintainers.adoc +++ b/fesco/modules/ROOT/pages/Policy_for_nonresponsive_package_maintainers.adoc @@ -47,8 +47,9 @@ link:https://src.fedoraproject.org[src.fedoraproject.org] pull requests, emails, 4. After 7 days, submit a link:https://pagure.io/fesco/new_issue/?template=nonresponsive-maintainer&title=Nonresponsive%20maintainer:%20%3Cname%3E%20%3Cfas-id%3E[FESCo issue] with the bug link and mailing list post link. State if you are a packager and want to take over the package. The non-responsive maintainer and all existing maintainers must be @-mentioned in the ticket. -5. If at least one FESCo member votes +1 and no one votes differently, the ticket is approved after three days. - Otherwise, FESCo will discuss the issue during a meeting. +5. If at least one FESCo member votes `+1` and no one votes differently, the ticket is approved after three days. + If any `-1` or `0` votes are made, FESCo will discuss the issue during a meeting. + This voting policy is intentionally simpler than the usual xref:index.adoc[voting policy#ticket-votes]. 6. If approved, and the reporter is a current Fedora packager in good standing, interested in comaintaining the package, FESCo will default to adding the reporter as the package admin. If the existing co-maintainers of the package do not want the package to be reassigned to the reporter, they should state so in the ticket. If assigned ownership, the reporter can now perform any required package maintenance. diff --git a/fesco/modules/ROOT/pages/index.adoc b/fesco/modules/ROOT/pages/index.adoc index 940fc1d..3b5388b 100644 --- a/fesco/modules/ROOT/pages/index.adoc +++ b/fesco/modules/ROOT/pages/index.adoc @@ -59,11 +59,17 @@ The xref:Updating_Fedora_Engineering_Steering_Committee_Members.adoc[Updating FE == Ticket Votes (Preferred) FESCo tracks all ongoing decisions using the link:https://pagure.io/fesco[FESCo Ticketing System]. -Generally, tickets are of two types: -tickets asking for FESCo's advice or tickets asking for a specific policy or technical change to occur. -When FESCo's opinion is sought, a ticket is opened -and then FESCo will reply to that ticket with either a proposal -or by adding it to the next weekly meeting agenda for discussion. +Generally, tickets are of three types: +tickets asking for FESCo's advice, +tickets asking for a specific policy or technical change to occur, +and tickets for xref:Policy_for_nonresponsive_package_maintainers.adoc[non-responsive maintainers]. +Tickets for non-resposive maintainers have their own +xref:Policy_for_nonresponsive_package_maintainers.adoc[voting policy#steps] +and the rest of this section does not apply to them. + +When FESCo's opinion is sought and a ticket has been opened, +FESCo will either reply to that ticket with a proposal +or add it to the agenda of the next weekly meeting for discussion. Once a formal proposal is made in a ticket, voting will proceed. A Change ticket is assumed to be a a formal proposal upon creation.