unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>, 74736@debbugs.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: Thu, 09 Jan 2025 16:40:43 -0800	[thread overview]
Message-ID: <878qrjh56c.fsf@wireframe> (raw)
In-Reply-To: <87y0zn4lvi.fsf_-_@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2844 bytes --]

Overall, this seems quite good, nice work all!

I do have one specific comment... though I am a latecomer to this
discussion!

On 2025-01-06, Ludovic Courtès wrote:
> ### Deliberation Period (14 days)
>
> All members of any team of the Guix project can participate in
> deliberation and are encouraged to do so.
>
> Once the final version is published, team members have 14 days to send
> one of the following replies on the patch-tracking entry of the RFC:
>
> - “I support”, meaning that one supports the proposal);
> - “I accept”, meaning that one consents to the implementation of the
>   proposal;
> - “I disapprove”, meaning that one opposes the implementation of the
>   proposal.  A team member sending this reply must have actively
>   proposed alternative solutions during the discussion period.
>
> The RFC is *accepted* if (1) at least 25% of all team members send a
> reply, and (2) no one disagrees.  In other cases, the RFC is
> *withdrawn*.

Is 'no one disagrees' == 'no one replies with "I disapprove"'? It would
be nicer if there were more explicit alignment in the words used to make
that clearer, if that is, in fact, the intended case. Perhaps
literally... e.g. ... (2) if no one declares "I disapprove".

... Well, two points, apparently, now that I got the simple one out of
the way... :)

In other consensus settings I have on occasion declared something that
is effectively "I accept, but I disapprove" or maybe more descriptively
"I accept, with reservations" e.g. not agreeing with the decision but
not severely enough that it should not move forward. You might not
expect to get much help with implementation from such a person, though!

I guess again, it comes to word alignment ... "I disapprove" sounds
rather soft, compared to the effects (e.g. blocking further progress or
sending it back to the proverbial drawing board). "I accept" sounds
rather positive, despite the possibility of some potential discomfort
with the decision...

Obviously, one can and should declare their reservations as part of the
discussion that lead up to that point! Although maybe "I accept" should
come with the option to declare formal outstanding concerns?

Similarly "I disaprove" should not come out of nowhere; it should be
clear why, and perhaps worth having an option to note that in the call
for consensus at the end of the Deliberation Period?


Eeesh. Three points!

I also wonder if there is a supermajority of "I accept" over "I support"
this maybe should raise some sort of red flag calling into question the
proposal... as that is a very weak consensus and perhaps cause for
concern.


All that said, I am a latecomer to this process... so take it however is
most helpful! Overall, it looks quite good to my eyes.


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2025-01-10  0:41 UTC|newest]

Thread overview: 97+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r04uljlj.fsf@gmail.com>
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
2025-01-10 16:48                           ` Noé Lopez via Guix-patches via
2025-01-11  0:47                           ` Suhail Singh
2025-01-15 18:44                             ` Simon Tournier
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
     [not found]             ` <87ed1163j5.fsf@housseini.me>
2025-01-17 12:15               ` reza via Guix-patches via
2025-01-17 15:39                 ` 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       ` Vagrant Cascadian [this message]
2025-01-10 12:25         ` [bug#74736] [PATCH v6] Add Request-for-Comments process Simon Tournier
2025-01-13  1:45           ` Vagrant Cascadian
2025-01-15 18:58             ` 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-15 19:12             ` Simon Tournier
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
2025-01-10 17:15     ` [bug#74736] [PATCH v8] Add Request-For-Comment process Ludovic Courtès
2025-01-15 22:40       ` Simon Tournier
2025-01-16  9:00         ` Ludovic Courtès
2025-01-16  9:50           ` Simon Tournier
2025-01-12 15:57   ` [bug#74736] Re v8 of " Hartmut Goebel
2025-01-13 21:17     ` [bug#74736] [PATCH v2 0/1] " Ludovic Courtès
2025-01-16 19:43       ` Hartmut Goebel
2025-01-16 20:41         ` Hartmut Goebel
2025-01-16 23:51           ` Simon Tournier
2025-01-16 23:50         ` Simon Tournier
2025-01-16 17:43     ` [bug#74736] Re v8 of " Simon Tournier
2025-01-16 19:50       ` Hartmut Goebel
2025-01-17  0:20         ` Simon Tournier
2025-01-16 17:55   ` [bug#74736] [PATCH v9] Add Guix Consensus Document process Simon Tournier
2025-01-16 23:13     ` [bug#74736] Do you read it? (was: [bug#74736] [PATCH v9] Add Guix Consensus Document process) Simon Tournier
2025-01-17  0:43   ` [bug#74736] [PATCH v10] Add Guix Consensus Document process Simon Tournier
2025-01-20  2:50     ` [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process Maxim Cournoyer
2025-01-20 22:21       ` Ludovic Courtès
2025-01-20 23:47         ` Maxim Cournoyer
2025-01-22 19:18           ` Simon Tournier
2025-01-22 19:15       ` Simon Tournier
2025-01-17  0:53   ` [bug#74736] [PATCH v10] Add Guix Consensus Document process Simon Tournier
2025-01-17 10:15     ` [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process Ludovic Courtès
2025-01-22 19:49   ` [bug#74736] [FWD] Guix Consensus Document process – deliberation Simon Tournier
2025-01-23  7:44     ` Hilton Chain
2025-01-23  8:30     ` [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process Ludovic Courtès
2025-01-23  9:19   ` [bug#74736] Guix Consensus Document process Tobias Geerinckx-Rice via Guix-patches via
2025-01-23  9:55   ` [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process Sharlatan Hellseher
2025-01-24  7:12   ` [bug#74736] Guix Consensus Document process – deliberation Nicolas Goaziou via Guix-patches via
2025-01-24  8:30   ` Ricardo Wurmus
2025-01-24 15:18   ` [bug#74736] Guix Consensus Document process Gabriel Wicki
2025-01-22 20:15 ` [bug#74736] Guix Consensus Document process – deliberation Liliana Marie Prikler
2025-01-22 20:56 ` Ekaitz Zarraga
2025-01-23  1:16   ` [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process jgart via Guix-patches via
2025-01-23  8:16 ` [bug#74736] Guix Consensus Document process – deliberation Tanguy LE CARROUR
2025-01-23  9:01 ` Janneke Nieuwenhuizen
2025-01-23  9:10 ` Zheng Junjie
2025-01-23 11:09 ` Maxim Cournoyer
2025-01-24 10:45   ` 宋文武 via Guix-patches via

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=878qrjh56c.fsf@wireframe \
    --to=vagrant@debian.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=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).