unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
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, 30 Dec 2024 12:03:29 +0100	[thread overview]
Message-ID: <87seq5tou6.fsf_-_@gnu.org> (raw)
In-Reply-To: <87wmfifii5.fsf@xn--no-cja.eu> ("Noé Lopez"'s message of "Sun, 29 Dec 2024 19:31:46 +0100")

Hi Noé,

Noé Lopez <noe@noé.eu> skribis:

>> It seems unchanged compared to v3.  WDYT of my comments, suggestions,
.> and proposed wording:
>>
>>   https://issues.guix.gnu.org/74736#9
>>
>> ?
>
> As Simon said, I think a vote goes against the principle of
> consensus.

OK.  As I wrote in my reply to Simon, my thought here was that “voting”*
would give a clear and unambiguous way, not subject to interpretation,
to decide whether the RFC is withdrawn: it’s easier to add numbers than
to determine whether “a positive consensus is reached” (current
wording).

But I don’t know, I guess that’s an “I will live with it” from me on
this one.  :-)

Two other issue I raised was the quorum: Simon proposed half of the
committers; I propose 25% of team members.  Thoughts?

* Maybe “voting” is misleading; “deliberation” might be clearer.

>>   2. on the submission -> withdrawn transition, in case nobody supports
>>      the RFC.

[...]

> I agree with that timeline, but I would have just “forgotten” an RFC
> that doesn’t pass the submission period, since that would mean it is not
> good enough to be discussed.  It can just be kept in the mail archives
> like any other unfinished idea.
>
> A withdrawn RFC would mean keeping it in the rfc/withdrawn directory.

Oh right, forgotten/dismissed seems more appropriate than withdrawn
here.

Anyway, I think we should aim for finalization of v1 of the RFC process
by, say, Jan. 15th.  I will dedicate some time to tweak the wording, and
then we can call it a thing.

(A bit sad that it’s just the three of us talking, we wouldn’t have the
quorum here…)

Ludo’.




  reply	other threads:[~2024-12-30 11:06 UTC|newest]

Thread overview: 21+ 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 [this message]
2024-12-30 11:58           ` Noé Lopez via Guix-patches via
2025-01-03 18:14 ` [bug#74736] [PATCH v5] rfc: " 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

  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=87seq5tou6.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 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).