all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Noé Lopez" <noe@xn--no-cja.eu>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 74736@debbugs.gnu.org
Subject: [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process.
Date: Fri, 10 Jan 2025 14:02:25 +0100	[thread overview]
Message-ID: <87sepqkeji.fsf@gmail.com> (raw)
In-Reply-To: <87wmf3ymua.fsf@xn--no-cja.eu>

Hi Noé,

On Fri, 10 Jan 2025 at 11:39, Noé Lopez via Guix-patches via <guix-patches@gnu.org> wrote:

> Can you explain the reasoning for that name?  I don’t think I understand
> what it means.

Personally, I find ’Guix Common Document’ more self-explanatory than
Request-for-Comments.  Because once the proposal is accepted or
withdrawn there is no more request nor comment. ;-)

Well, I know RFC is the usual name for this kind of thing (I also used
RFC when discussing it).  Nonetheless, I find nicer to not follow such
“convention”, as for example Python Enhancement Proposals (PEP)
does. :-) And the term RFC is already too much overloaded in Guix
mailing list, IMHO.

In addition, I like ’Guix Common Document’ because it expresses what it
is: our shared (common) direction.  Moreover it echoes with Commons and
somehow the process tries to capture that: what we collectively want to
preserve.  Last, pun with mathematical notion of greatest common divisor
(gcd) [1].

Does it make sense?

Cheers,
simon



1: https://en.wikipedia.org/wiki/Greatest_common_divisor




  reply	other threads:[~2025-01-10 13:04 UTC|newest]

Thread overview: 51+ 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-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 [this message]
2025-01-10 16:48                         ` Noé Lopez via Guix-patches via
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

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=87sepqkeji.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=74736@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=noe@xn--no-cja.eu \
    /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.