all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "Noé Lopez" <noe@xn--no-cja.eu>,
	74736@debbugs.gnu.org, "Christopher Baines" <mail@cbanes.net>,
	"Steve George" <steve@futurile.net>
Subject: [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process.
Date: Mon, 23 Dec 2024 18:58:14 +0100	[thread overview]
Message-ID: <8734iee0y1.fsf_-_@gmail.com> (raw)
In-Reply-To: <87v7vmo9yg.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Sat, 14 Dec 2024 11:06:15 +0100")

Hi Ludo,

I agree (more than less) with all the other comments except this
one. :-)


>>>> +** Decision making: consensus
>>>
>>> … and drop this.
>>
>> I think it makes more sense to have the Decision Making as RFC and then
>> the manual refers to it, and not the converse. ;-)
>>
>> Therefore, I would keep the section here.  And once we are done, letting
>> the manual as-is, I would link to RFC.
>>
>> What defines the Decision Making *is* RFC and not the manual. ;-)
>
> Earlier, I wrote:
>
>> I would add “General day-to-day contributions follow the regular
>> [decision-making process] and [team organization].”, with references to
>> the relevant sections of the manual.
>
> Since (1) day-to-day contributions do not follow the RFC process and (2)
> teams and consensus-based decision making are already defined (and went
> through peer review), I think it makes more sense to build on these two
> sections we already have.

I still think the RFC process must contain its own “Decision Making”
process and must not refer to external parts that could be changed
without going via this RFC process.

Somehow, from my point of view, it makes more sense to encode “Decision
Making” or “Commit Access” or “Teams” via future RFCs than via sections
in the manual.  And we need to bootstrap the “Decision Making”, no?

For sure, I agree that we do not build from nothing.  To me, this very
first RFC makes explicit the structure we already have.  Maybe I
misunderstand something, IMHO, we should avoid the temptation to say:
Hey we already have a way to collaborate thus let implicitly rely on.

Hum? 🤔 Somehow, I would find the RFC process incomplete without an
explicit self-contained “Decision Making” section.

What do you think?  What do people think?

Cheers,
simon




  reply	other threads:[~2024-12-23 18:01 UTC|newest]

Thread overview: 14+ 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 [this message]
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

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=8734iee0y1.fsf_-_@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=74736@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@cbanes.net \
    --cc=noe@xn--no-cja.eu \
    --cc=steve@futurile.net \
    /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.