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: Sat, 04 Jan 2025 18:28:05 +0100	[thread overview]
Message-ID: <87ttaeqyje.fsf@gnu.org> (raw)
In-Reply-To: <875xn14c21.fsf@xn--no-cja.eu> ("Noé Lopez"'s message of "Mon, 30 Dec 2024 12:58:46 +0100")

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

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> 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).
>>
>
> This is why an ACK/NACK system works great in my opinion: you send “ACK”
> or “NACK” litteraly so your opinion is clear.  And you can just count
> the number of each, without implying a vote.

OK, got it, we agree on this.

>> 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?

[...]

> Half of the committers is 25 people (based on .guix-authorizations), and
> a quarter of the team members is 10.  Personnally, I have trouble
> imagining that this amount of people will come to send a mail to the
> RFC.

So are you saying you’d want no quorum at all?  (Your revision still
reads “50% committers”.)

>> 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.
>>
>
> Good idea!  I’ll be waiting for your v5 then.  And then I can bring
> back the RFC template.

OK, will do in the coming days.

>> (A bit sad that it’s just the three of us talking, we wouldn’t have the
>> quorum here…)
>>
>
> Agreed.
>
> Lastly, do we want to move the RFCs to a separate git repository?

I think so.  I’ll ask for it on Savannah.

Thanks,
Ludo’.




  reply	other threads:[~2025-01-04 17:29 UTC|newest]

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

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