#74736 - [PATCH v2 0/1] Add Request-For-Comment process.

Package	Source(s)		Maintainer(s)
guix-patches		PTS Buildd Popcon

Message #30 received at 74736@debbugs.gnu.org (full text, mbox, reply):

Received: (at 74736) by debbugs.gnu.org; 14 Dec 2024 10:47:32 +0000
From debbugs-submit-bounces@debbugs.gnu.org Sat Dec 14 05:47:32 2024
Received: from localhost ([127.0.0.1]:45673 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces@debbugs.gnu.org>)
	id 1tMPgK-0001ux-02
	for submit@debbugs.gnu.org; Sat, 14 Dec 2024 05:47:32 -0500
Received: from eggs.gnu.org ([209.51.188.92]:46864)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <ludo@gnu.org>) id 1tMPgH-0001ue-92
 for 74736@debbugs.gnu.org; Sat, 14 Dec 2024 05:47:30 -0500
Received: from fencepost.gnu.org ([2001:470:142:3::e])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <ludo@gnu.org>)
 id 1tMPgA-00059y-CT; Sat, 14 Dec 2024 05:47:22 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To:
 From; bh=79hXUh1B/ZE2cQAsAxdwbHrbE/hUF8mOMCLBynUYE/c=; b=nLGym1jrEM/WDv1pPCsX
 8HK5X2WjhrkwuM2LDTHumNfTcL+WOEqkyg7aSJSO6CU5pv07qQxwnNb3n8IylEbvhIjlE76YxBuWK
 eYbUSK4VXpm6qV2wYiCVZ3JSc3NOkCLUDTvTqNirHUUsv3lZxcMQJatMzIDOoCQ2RJUvqrawy5U/g
 OBjcNQZ8czNiPMUAaRrdjAloz9Lv3FSU3r9g2DU5/jnC/bQPJl1T1bVMz/HHY8jpJ9kbD6BZ1g42G
 4s/2l0gq5Er3hQ9tgJPbfcEAAWNRZp0Wir/smCVsL9oWf8ndfvlzZ0Zw/UtJk+bhvmlcCkCc9biQF
 d9aUZTsytkHz3A==;
From: Ludovic Courtès <ludo@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Subject: Re: [bug#74736] [PATCH v3] rfc: Add Request-For-Comment process.
In-Reply-To: <493bcc076f206ec134959268f55a9358b4886b88.1734031781.git.zimon.toutoune@gmail.com>
 (Simon Tournier's message of "Thu, 12 Dec 2024 20:30:56 +0100")
References: <cover.1733614983.git.noelopez@free.fr>
 <493bcc076f206ec134959268f55a9358b4886b88.1734031781.git.zimon.toutoune@gmail.com>
Date: Sat, 14 Dec 2024 11:47:19 +0100
Message-ID: <87h676mthk.fsf@gnu.org>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -2.3 (--)
X-Debbugs-Envelope-To: 74736
Cc: Noé Lopez <noe@xn--no-cja.eu>,
 Noé Lopez <noelopez@free.fr>, 74736@debbugs.gnu.org,
 Christopher Baines <mail@cbanes.net>
X-BeenThere: debbugs-submit@debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request@debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit@debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request@debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request@debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces@debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
X-Spam-Score: -3.3 (---)

Thanks for v3!

Some of my more superficial comments earlier this week remain
unaddressed:

  • I think it should be Markdown, and in a separate repo.

  • There are too many explicit references to Debbugs, which I think is
    not future-proof.

I think the text itself needs more work to address and remove remaining
comments that appear in the body, to improve grammar and wording, and to
make it shorter (it’s way too long IMO).  But that can come in a second
phase.

Questions/comments about the process that I overlooked before:

> +The lifetime of an RFC is structured into the following recommended periods:
> +
> +  submission (7d) ⟶ comments (30–60d) ⟶ last call (14d) ⟶ withdrawn OR final

This diagram doesn’t show everything I think; for example…

> +*** Submission (up to 7 days)
> +
> +The author submits their RFC proposal as a regular patch and look for
> +co-supporter(s). See 'Co-supporter' section.
> +
> +Once the RFC is co-supported, it marks the start of a discussion period.

… what happens when the submitter doesn’t find supporters in that
period? I’m guessing the RFC goes in “withdrawn” state?

The diagram should reflect that, and we can render it with Dot.

> +*** Last call (up to 14 days)
> +
> +The author publishes a final version of the RFC and a last grace period of 14
> +days is granted.  People are asked to agree or disagree by commenting:
> +
> + - +1 / LGTM: I support
> + - =0 / LGTM: I will live with it
> + - -1: I disagree with this proposal
> +
> +At least half of people with commit acces must express their voice with the
> +keys above during this last call.  We need to be sure that the RFC had been
> +read by people committed to take care of the project, since it proposes an
> +important change.

I think committers here are mentioned as a simple way to express
membership and avoid infiltration, but it has the downside of ignoring
many members and giving committers a special privilege.

I propose this definition: anyone who is on a team (in ‘teams.scm’) is a
voting member*.

We can keep a quorum, but I think 50% of the voters is too ambitious;
maybe 25%?

This would become¹:

  Once the final version is published, team members have 14 days to cast
  one of the following votes about the RFC:

    - Support (+1);
    - Accept (0);
    - Reject (-2).

  Votes are cast by replying on the patch-tracking entry of the RFC.

  The RFC is accepted if (1) at least 25% of the voting members cast a
  vote, and (2) the sum of votes is non-negative.  In other cases, the
  RFC is withdrawn.

Thoughts?

Ludo’.


* We’ll have to create new teams and update them so we don’t forget
  anyone, notably translators, sysadmins, graphics designers, and so on.

¹ Inspired by
  <https://codeberg.org/mergiraf/mergiraf/src/branch/main/GOVERNANCE.md>.

Display info messages

Send a report that this bug log contains spam.

debbugs.gnu.org maintainers <help-debbugs@gnu.org>. Last modified: Sun Dec 22 16:25:11 2024; Machine Name: wallace-server

GNU bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

#74736 [PATCH v2 0/1] Add Request-For-Comment process.