unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Guix Devel <guix-devel@gnu.org>
Subject: Time for a request-for-comments process?
Date: Wed, 27 Oct 2021 23:22:50 +0200	[thread overview]
Message-ID: <87cznqb1sl.fsf@inria.fr> (raw)

Hello Guix!

The recent ‘guix shell’ addition is almost anecdotal technically yet
important for the project because users interact with Guix primarily
through the CLI.  Adding a new command is a commitment (our users must
trust it won’t change overnight), and getting the details wrong could
make us fail to honor that commitment.

For ‘guix shell’ I left time for comments and repeatedly asked people to
comment; yet pushing it was a bit stressful: Did I make a mistake?  Did
everyone with a stake in this really have a chance to comment?

That makes me think it’s perhaps time for a formalized
request-for-comments (RFC) kind of process for such “major changes”.  We
could draw inspiration from one of the many existing processes: Python’s
PEPs, Scheme’s SRFIs, Nix’s RFCs, Rust’s MCPs, etc.  I think a major
goal of the process would be to formalize a minimum and a maximum
duration under which an RFC is under evaluation, and a mechanism to
determine whether it’s accepted or withdrawn.

Thoughts?  Anyone with experience with such a process?

Ludo’.


             reply	other threads:[~2021-10-27 21:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 21:22 Ludovic Courtès [this message]
2021-10-27 22:28 ` Time for a request-for-comments process? Katherine Cox-Buday
2021-10-28  0:07   ` Thiago Jung Bauermann
2021-10-29 15:08     ` Ludovic Courtès
2021-10-30 15:57       ` zimoun
2021-11-09 16:52         ` Ludovic Courtès
2021-11-09 18:01           ` zimoun
2021-11-09 21:10             ` Julien Lepiller
2021-10-27 23:47 ` jbranso
2021-10-27 23:48 ` jbranso
2021-10-28  8:42 ` zimoun
2021-10-28 10:33   ` Bengt Richter
2021-10-28 17:06     ` Tobias Platen

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=87cznqb1sl.fsf@inria.fr \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    /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).