[bug#74736,v9] Add Guix Consensus Document process
Commit Message
Hi,
Please find attach the v9; I hope it addresses the comments.
Attached the diff and the document. The minor changes are:
• Point alone “1. Clone …”
• Replace remaining RFC with GCD.
• Add a sentence about “Sponsor” role.
• Add the role of “Contributor”.
• Tweak the artist view of the Timeline
• Explicit mention that everyone can participate to the “Discussion
Period”. And mention that the main concerns and/or opposition are
collected to the final document.
• Move upfront the aim of “Deliberation Period”. Remove a redundant
sentence.
• Explicit mention the state ‘deprecated’.
WDYT?
Cheers,
simon
--
--
@@ -73,7 +73,7 @@
## How the Process Works
1. Clone
- https://git.savannah.gnu.org/git/guix/guix-consensus-documents.git .
+ https://git.savannah.gnu.org/git/guix/guix-consensus-documents.git
2. Copy `000-template.md` to `XYZ-short-name.md` where `short-name`
is a short descriptive name and `XYZ` is the sequence number.
3. Write your GCD following the template’s structure. The GCD must not
@@ -92,15 +92,16 @@
## Roles
- - An *author* is the person or one of the persons submitting the RFC.
+ - An *author* is the person or one of the persons submitting the GCD.
Authors bear the responsibility to carry out the process to its
conclusion.
- A *sponsor* is a contributor who, during the submission period (see
below), informs the author(s) that they would like to support the
- RFC by participating in discussions, providing constructive comments
+ GCD by participating in discussions, providing constructive comments
to help the author(s), soliciting opinions, and acting as
- timekeepers.
+ timekeepers. As a sponsor, please make sure that all have the time
+ and space for expressing their comments.
Sponsors should be contributors who consider being sufficiently
familiar with the project’s practices; hence it is recommended, but
@@ -111,6 +112,10 @@
members is maintained in the file `etc/teams.scm` in the Guix
repository.
+ - A *contributor* is a person contributing to Guix either with code,
+ translation, reviewing, etc. and more broadly any person feeling part
+ of the Guix community.
+
## Timeline
A GCD must follow the process illustrated by the diagram below,
@@ -118,21 +123,20 @@
```
- +-----------+
- +- - - - - - ->| Withdrawn |<----------------------+
- : +-----------+ |
- : ^ |
- : : |
-+--------------------+ +---------------------+ +---------------------+
-| Submission Period | | Discussion Period | | Deliberation Period |
-| (up to 7 days) |-->| (30–60 days) |-->| (14 days) |
-+--------------------+ +---------------------+ +---------------------+
- |
- |
++--------------------+ +---------------------+ +---------------------+
+| Submission Period | | Discussion Period | | Deliberation Period |
+| (up to 7 days) |-X->| (30–60 days) |-->| (14 days) |
++--------------------+ : +---------------------+ +---------------------+
+ : : : |
+ : v : |
+ : declined v |
+ : o-----------o |
+ +- - - - - - - - ->| Withdrawn |<----------------- X
+ o-----------o |
V
- +----------+
- | Accepted |
- +----------+
+ o----------o
+ | Accepted |
+ o----------o
```
The subsections below detail the various periods and their duration.
@@ -150,8 +154,11 @@
### Discussion Period (at least 30 days, up to 60 days)
-Once submitted, the GCD is publicly discussed; authors are encouraged to
-publish updated versions incorporating feedback during the discussion.
+Once submitted, the GCD is publicly discussed by all the members of the
+community. Authors are encouraged to publish updated versions
+incorporating feedback during the discussion; members are encouraged to
+share a summary of their main concerns or opposition, if any, for being
+included under section “Open Issues” in the document.
When deemed appropriate, between 30 days and 60 days after the start
of the discussion period, the author(s) may publish a final version and
@@ -159,8 +166,11 @@
### Deliberation Period (14 days)
-All team members can participate in deliberation and are encouraged to
-do so.
+Deliberation aims at consolidating consensus; see “Decision Making”
+below.
+
+Anyone who is a team member is a deliberating member and is encouraged
+to contribute to the deliberation.
Once the final version is published, team members have 14 days to send
one of the following replies on the patch-tracking entry of the GCD:
@@ -176,13 +186,6 @@
reply, and (2) no one disapproves. In other cases, the GCD is
*withdrawn*.
-Deliberation aims at consolidating consensus; see “Decision Making”
-below.
-
-Anyone who is a team member is a deliberating member and is encouraged
-to contribute to the deliberation. Team members are defined by the
-file etc/teams.scm (see “Teams” in the manual).
-
GCD acceptance is not a rubber stamp; in particular, it does not mean
the proposal will effectively be implemented, but it does mean that all
the participants consent to its implementation.
@@ -215,7 +218,7 @@
`status` to `accepted` or `withdrawn`; adding the URL of the
discussion in the `discussion` header; updating the `date` header; if
previously-accepted GCDs are deprecated by this new GCD, change the
- `status` header accordingly);
+ `status` header accordingly with `deprecated`);
2. committing everything;
3. announcing the publication of the GCD.