From: reza via Guix-patches via <guix-patches@gnu.org>
To: 74736@debbugs.gnu.org, ludo@gnu.org
Cc: "Noé Lopez" <noe@xn--no-cja.eu>, "Noé Lopez" <noelopez@free.fr>,
"Christopher Baines" <mail@cbaines.net>,
"Simon Tournier" <zimon.toutoune@gmail.com>
Subject: [bug#74736] [PATCH v6] Add Request-for-Comments process.
Date: Wed, 8 Jan 2025 06:33:55 +0000 [thread overview]
Message-ID: <01020194449ea437-ba0e47aa-a66a-43a0-9ba8-bdad0f257714-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <87y0zn4lvi.fsf_-_@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
Thanks for pushing this forward.
As a maybe tangential comment: There is no mention of an identifier for an RFC (e.g. PEP number) or a unique string to identify or reference it?
On January 6, 2025 11:29:21 PM GMT+01:00, "Ludovic Courtès" <ludo@gnu.org> wrote:
Hello,
As proposed before, here’s a reworked version based on v5. The intent
is to keep the spirit and process unchanged compared to v5, while making
the document a bit more concise (239 lines, v5 was 322), improving
consistency for key words, hopefully improving wording, fixing
grammatical issues, and adding Markdown ornaments where appropriate.
Notable changes:
• Instead of “supporter” and “co-supporter”, I propose “author(s)” and
“supporter(s)” (there must be at least one supporter).
• Explicitly state the license of RFCs (CC-BY-SA or GFDL).
• Clarify that the deliberation period lasts exactly 14 days (was “up
to 14 days” in one place, “14 days” in another).
• Consistently name the different periods.
• Remove mention of the ‘withdrawn/’ directory: it’s redundant with
the ‘status’ header.
• Clarify what to do with “deprecated” RFCs.
• Clarify headers of this RFC.
• Clarify that this is not just for technical changes.
I can proofread and possibly propose minor tweaks the template
afterwards.
Thoughts?
Ludo’.
-- Sent from /e/OS Mail.
[-- Attachment #2: Type: text/html, Size: 1868 bytes --]
next prev parent reply other threads:[~2025-01-08 6:36 UTC|newest]
Thread overview: 32+ 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 ` [bug#74736] [PATCH v2 0/1] " Ludovic Courtès
2024-12-23 17:33 ` 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-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
[not found] ` <825F8319-4F41-4F4C-81B3-2C84A73A13CF@housseini.me>
2025-01-08 6:33 ` reza via Guix-patches via [this message]
2025-01-08 16:26 ` pukkamustard
2025-01-07 19:40 ` [bug#74736] " Ricardo Wurmus
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01020194449ea437-ba0e47aa-a66a-43a0-9ba8-bdad0f257714-000000@eu-west-1.amazonses.com \
--to=guix-patches@gnu.org \
--cc=74736@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
--cc=noe@xn--no-cja.eu \
--cc=noelopez@free.fr \
--cc=reza@housseini.me \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).