| |
@@ -63,6 +63,9 @@
|
| |
Tagging the issue for the meeting agenda is understood to disqualify the proposal for fast-track status.
|
| |
Proposals that receive a unanimous vote are immediately considered approved or rejected as appropriate, independent of fast-track status.
|
| |
|
| |
+ Proposals that are rejected may be submitted by reconsideration, but they must go through whatever process was originally required before FESCo begins voting.
|
| |
+ For example, this means a rejected Change proposal must be resubmitted to the Change Wrangler as outlined in the xref:program_management::changes_policy.adoc[Changes process].
|
| |
+
|
| |
== Meetings
|
| |
|
| |
FESCo meets usually on a weekly basis, check the link:https://fedoraproject.org/wiki/FESCo_meeting_process[FESCo meeting process]. You should verify the meeting date and time from the link:https://admin.fedoraproject.org/mailman/listinfo/devel[devel] mail "_Plan for tomorrow's FESCo meeting_" being sent in advance.
|
| |
Process note: I am opening this for comment before creating an associated ticket in order to get feedback from the community first.
Explicitly require that any rejected proposal has to go through the
process it originally required.
I intentionally left this vague in order to account for things apart
from Change proposals, even though that's what highlighted the need for
this policy change/clarification.