From: "Ludovic Courtès" <ludo@gnu.org>
To: "Noé Lopez" <noe@xn--no-cja.eu>
Cc: 74736@debbugs.gnu.org, Simon Tournier <zimon.toutoune@gmail.com>
Subject: [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process.
Date: Mon, 23 Dec 2024 15:42:24 +0100 [thread overview]
Message-ID: <87ikraea0f.fsf_-_@gnu.org> (raw)
In-Reply-To: <aa5f6bcd5ebf3ddafc6f56155a23bd0c4223db8b.1734875359.git.noelopez@free.fr> ("Noé Lopez"'s message of "Sun, 22 Dec 2024 14:56:56 +0100")
Hi Noé,
Thanks for this new version.
Noé Lopez <noe@noé.eu> skribis:
> +### Submission (up to 7 days)
> +
> +The author submits their RFC proposal as a regular patch and look for
> +co-supporter(s). See “Co-supporter” section.
> +
> +Once the RFC is co-supported, it marks the start of a discussion period.
[...]
> +### Last call (up to 14 days)
> +
> +The author publishes a final version of the RFC and a last grace period
> +of 14 days is granted. People are asked to agree or disagree by
> +commenting:
> +
> +- +1 / LGTM: I support
> +- =0 / LGTM: I will live with it
> +- -1: I disagree with this proposal
> +
> +At least half of people with commit access must express their voice with
> +the keys above during this last call. We need to be sure that the RFC
> +had been read by people committed to take care of the project, since it
> +proposes an important change.
> +
> +When a positive consensus is reached, the RFC becomes effective. If not,
> +the proposal is archived and the status quo continues.
It seems unchanged compared to v3. WDYT of my comments, suggestions,
and proposed wording:
https://issues.guix.gnu.org/74736#9
?
I think we should now make sure we reach consensus on the timeline, and
in particular:
1. on the voting process;
2. on the submission -> withdrawn transition, in case nobody supports
the RFC.
Once we have that, we can fine-tune the language and hopefully be done
within a couple of weeks.
I like the Dot graph you submitted! Here’s an updated version, with a
new submission -> withdrawn arrow (as proposed in the comment above) and
with hopefully clearer names (in particular “Voting Period” rather than
“Last call”):
--8<---------------cut here---------------start------------->8---
digraph "RFC Timeline" {
submission[label=<Submission Period<br />7 days>]
comments[label=<Discussion Period<br />30–60 days>]
last_call[label=<Voting Period<br />14 days>]
withdrawn[label=Withdrawn, shape=rectangle]
final[label=Final, shape=rectangle]
submission -> comments
submission -> withdrawn
comments -> last_call
last_call -> withdrawn
last_call -> final
withdrawn -> submission [label="New version"]
comments -> withdrawn
}
--8<---------------cut here---------------end--------------->8---
Thoughts?
Thanks for getting the ball rolling!
Ludo’.
next prev parent reply other threads:[~2024-12-23 14:43 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-08 12:29 [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process Noé Lopez via Guix-patches via
2024-12-08 12:31 ` [bug#74736] [PATCH v2 1/1] rfc: " Noé Lopez via Guix-patches via
2024-12-12 18:14 ` [bug#74736] [PATCH v2 0/1] " Ludovic Courtès
2024-12-12 19:47 ` Simon Tournier
2024-12-14 10:06 ` Ludovic Courtès
2024-12-23 17:58 ` Simon Tournier
2024-12-26 11:15 ` Ludovic Courtès
2024-12-09 20:47 ` Artyom V. Poptsov
2024-12-12 19:30 ` [bug#74736] [PATCH v3] rfc: " Simon Tournier
2024-12-14 10:47 ` Ludovic Courtès
2024-12-22 13:06 ` Noé Lopez via Guix-patches via
2024-12-22 13:56 ` [bug#74736] [PATCH v4 0/1] " Noé Lopez via Guix-patches via
2024-12-22 13:56 ` [bug#74736] [PATCH v4 1/1] " Noé Lopez via Guix-patches via
2024-12-23 14:42 ` Ludovic Courtès [this message]
2024-12-23 17:33 ` [bug#74736] [PATCH v2 0/1] " Simon Tournier
2024-12-26 11:28 ` Ludovic Courtès
2024-12-31 15:23 ` Simon Tournier
2024-12-29 18:31 ` Noé Lopez via Guix-patches via
2024-12-30 11:03 ` Ludovic Courtès
2024-12-30 11:58 ` Noé Lopez via Guix-patches via
2025-01-04 17:28 ` Ludovic Courtès
2025-01-05 12:51 ` Noé Lopez via Guix-patches via
2025-01-06 10:29 ` Simon Tournier
2025-01-06 17:40 ` Ludovic Courtès
2025-01-08 10:53 ` Ludovic Courtès
2025-01-09 13:27 ` Ludovic Courtès
2025-01-09 22:48 ` Simon Tournier
2025-01-10 10:39 ` Noé Lopez via Guix-patches via
2025-01-10 13:02 ` Simon Tournier
2025-01-10 16:48 ` Noé Lopez via Guix-patches via
2025-01-11 0:47 ` Suhail Singh
2025-01-03 18:14 ` [bug#74736] [PATCH v5] rfc: " Simon Tournier
2025-01-06 22:29 ` [bug#74736] [PATCH v6] Add Request-for-Comments process Ludovic Courtès
2025-01-07 17:06 ` Noé Lopez via Guix-patches via
2025-01-08 15:12 ` [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process Suhail Singh
2025-01-09 17:21 ` Simon Tournier
[not found] ` <825F8319-4F41-4F4C-81B3-2C84A73A13CF@housseini.me>
2025-01-08 6:33 ` [bug#74736] [PATCH v6] Add Request-for-Comments process reza via Guix-patches via
2025-01-09 23:22 ` Simon Tournier
2025-01-08 16:26 ` [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process pukkamustard
2025-01-09 17:18 ` Simon Tournier
2025-01-09 21:00 ` Ludovic Courtès
2025-01-09 21:16 ` Ludovic Courtès
2025-01-09 16:21 ` [bug#74736] [PATCH v6] Add Request-for-Comments process Simon Tournier
2025-01-09 22:32 ` [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process Ludovic Courtès
2025-01-09 23:56 ` Simon Tournier
2025-01-10 0:40 ` [bug#74736] [PATCH v6] Add Request-for-Comments process Vagrant Cascadian
2025-01-10 12:25 ` Simon Tournier
2025-01-10 7:44 ` Janneke Nieuwenhuizen
2025-01-10 12:45 ` Simon Tournier
2025-01-10 13:17 ` Janneke Nieuwenhuizen
2025-01-07 19:40 ` [bug#74736] Add Request-For-Comment process Ricardo Wurmus
2025-01-09 23:45 ` [bug#74736] [PATCH v7] Add Guix Common Document process Simon Tournier
2025-01-10 17:15 ` [bug#74736] [PATCH v8] Add Request-For-Comment process Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ikraea0f.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=74736@debbugs.gnu.org \
--cc=noe@xn--no-cja.eu \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.