unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>,
	Efraim Flashner <efraim@flashner.co.il>,
	Ricardo Wurmus <rekado@elephly.net>,
	Christopher Baines <mail@cbaines.net>,
	GNU Guix maintainers <guix-maintainers@gnu.org>
Subject: Re: Request-For-Comment process: concrete implementation (v5)
Date: Thu, 09 Jan 2025 18:33:16 +0100	[thread overview]
Message-ID: <87frlr51ur.fsf@gmail.com> (raw)
In-Reply-To: <87zfk229h0.fsf@gnu.org>

Hi,

On Tue, 07 Jan 2025 at 11:40, Ludovic Courtès <ludo@gnu.org> wrote:

> Yes, would be nice if some of you reading this could offer to become
> “supporters”.

[...]

> Please take a look, comment, offer your name as a “supporter”, and then
> make your voice heard during the deliberation period!

I think we need to clarify what means “supporter”.  In my mind, a
Supporter is a person that commits to help the Author in crossing the
final line.

During the Discussion Period, we discuss, all.  The aim of Supporter is
to keep the RFC on track.  Especially, to let space and time to all to
express their voice.  Nix names this Role: Shepherd.  Maybe it captures
better the idea.

Then during the Deliberation Period, team members reply “I support”.

WDYT?

BTW, I like “Guix Common Document“ [1] instead of Request-For-Comment as
suggested by pukkamustard.


Cheers,
simon

1: [post Guix Days] Guix Common Document (was: Request-For-Comment process)
Simon Tournier <zimon.toutoune@gmail.com>
Sat, 03 Feb 2024 11:34:13 +0100
id:87y1c1kfa2.fsf@gmail.com
https://lists.gnu.org/archive/html/guix-devel/2024-02
https://yhetil.org/guix/87y1c1kfa2.fsf@gmail.com


  parent reply	other threads:[~2025-01-09 17:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 11:14 Request-For-Comment process: concrete implementation Simon Tournier
2023-11-16 15:03 ` Ludovic Courtès
2023-11-20  9:42   ` Simon Tournier
2023-11-22 18:17     ` Ludovic Courtès
2023-11-23  7:04 ` Efraim Flashner
2023-11-28 13:34   ` Simon Tournier
2023-12-19 12:33 ` Simon Tournier
2023-12-20 11:49   ` Ricardo Wurmus
2024-02-03 10:09     ` Simon Tournier
2024-02-03 10:34 ` [post Guix Days] Guix Common Document (was: Request-For-Comment process) Simon Tournier
2024-02-07  8:27   ` Efraim Flashner
2025-01-03 18:38 ` Request-For-Comment process: concrete implementation (v5) Simon Tournier
2025-01-07 10:40   ` Ludovic Courtès
2025-01-08 15:15     ` Suhail Singh
2025-01-09 17:33     ` Simon Tournier [this message]
2025-01-09 23:49       ` bokr
2025-01-10  6:26       ` Suhail Singh

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=87frlr51ur.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@cbaines.net \
    --cc=rekado@elephly.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 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).