From 0c7a9f521b5a6335420e8e7a913b3da4ee8873a0 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Aug 17 2023 18:24:11 +0000 Subject: index: break text with "semantic line breaks" This is just reformatting at the source level, no visible changes. I want to use that in the new parts, so I'm reformatting the parts that will not be changed separately for clarity. See https://sembr.org. --- diff --git a/fesco/modules/ROOT/pages/index.adoc b/fesco/modules/ROOT/pages/index.adoc index 67d5851..abaaf15 100644 --- a/fesco/modules/ROOT/pages/index.adoc +++ b/fesco/modules/ROOT/pages/index.adoc @@ -25,11 +25,15 @@ Issues FESCo handles include: * Responsible for what software is offered to end users under what conditions. * Oversight and approval of new spins and other media that doesn't fit under a working group. -FESCo has empowered the FPC (Fedora Packaging Comittee) to handle management of packaging guidelines, so those items are usually deferred to them with occasional FESCo oversight. +FESCo has empowered the FPC (Fedora Packaging Comittee) to handle management of packaging guidelines, +so those items are usually deferred to them with occasional FESCo oversight. -Candidates for FESCo should be people who have a wide breadth of knowledge about the Fedora Project as a whole and who understand how the many different pieces fit together. Ideal candidates should also have a history of fostering inter-team coordination. +Candidates for FESCo should be people who have a wide breadth of knowledge about the Fedora Project as a whole +and who understand how the many different pieces fit together. +Ideal candidates should also have a history of fostering inter-team coordination. -FESCo has a designate for each Working Group that coordinates with that Group and communicates back to FESCo any issues or concerns. Currently there are: Workstation, Server and Atomic Working groups. +FESCo has a designate for each Working Group that coordinates with that Group and communicates back to FESCo any issues or concerns. +Currently there are: Workstation, Server and Atomic Working groups. [[fesco-members]] == Members @@ -52,8 +56,13 @@ The xref:Previous_Fedora_Engineering_Steering_Committee_Members.adoc[Previous co The xref:Updating_Fedora_Engineering_Steering_Committee_Members.adoc[Updating FESCo members] page outlines the necessary steps to update FESCo members after an election. == Ticket Policy +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. -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. Once a ticket has a formal proposal offered, FESCo members have one week to either vote for or against it or else propose the ticket for the next weekly meeting agenda. At the end of that one week, if the proposal has gained at least three "for" votes and no "against" votes, it is approved. Any "against" votes mean that it goes onto the next meeting agenda, unless there are at least 7 negative votes and no positive ones, see below. If the week passes and the required number of votes have not been met, the proposal is extended by one further week and the minimum requirement becomes a single positive "for" vote. This is intended to ensure that proposals do not languish. @@ -79,13 +88,22 @@ Meetings require a majority of FESCo to be present; if fewer than five of the ni [[agenda]] === Agenda -You can find FESCO's weekly agenda in the link:https://pagure.io/fesco[FESCo Ticketing System] with this link:https://pagure.io/fesco/report/meeting_agenda[report]. +You can find FESCO's weekly agenda in the link:https://pagure.io/fesco[FESCo Ticketing System] +with this link:https://pagure.io/fesco/report/meeting_agenda[report]. === Meeting Minutes -You can find FESCO's meeting minutes at link:https://meetbot.fedoraproject.org/sresults/?group_id=fesco&type=team[the fedora meetbot site] as well as posted to the link:devel@lists.fedoraproject.org list after each meeting. Note that meetings prior to the 2010-10-20 meeting were on Tuesdays. +You can find FESCO's meeting minutes at +link:https://meetbot.fedoraproject.org/sresults/?group_id=fesco&type=team[the fedora meetbot site] +as well as posted to the +link:devel@lists.fedoraproject.org +list after each meeting. +Note that meetings prior to the 2010-10-20 meeting were on Tuesdays. == Mailing List -FESCo has a private mailing list for sensitive matters. This list will have as subscribers only the current FESCo members and the Fedora Project Leader. -This list should only be used in very rare situations with private information. The FESCo chair will make sure any discussion on this list that doesn't need to be private will be resent to a public forum (FESCo issue tracker, devel list, etc). +FESCo has a private mailing list for sensitive matters. +This list will have as subscribers only the current FESCo members and the Fedora Project Leader. +This list should only be used in very rare situations with private information. +The FESCo chair will make sure any discussion on this list that doesn't need to be private +will be resent to a public forum (FESCo issue tracker, devel list, etc).