From: jbranso@dismail.de
To: "Ludovic Courtès" <ludo@gnu.org>, "Guix Devel" <guix-devel@gnu.org>
Subject: Re: Time for a request-for-comments process?
Date: Wed, 27 Oct 2021 23:47:59 +0000 [thread overview]
Message-ID: <dc74f8b97792d10a48aed71712935b15@dismail.de> (raw)
In-Reply-To: <87cznqb1sl.fsf@inria.fr>
October 27, 2021 5:23 PM, "Ludovic Courtès" <ludo@gnu.org> wrote:
> 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?
I absolutely love the new guix shell! "-ad-hoc" was a bit confusing to
understand. I know more about guix shell in 5 minutes than I did with
a few years of guix environment!
> 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.
I'm all for a RFC! Somehow I missed any communication about this new
guix shell, and I normally follow the mailing lists like a 11th grade
stalker (not that I have any experience with stalking...I can't really
discuss it until the lawsuit is over...).
But then again my comments are perhaps not as weighty as others? I have
only really been the occasional guix documentation writer.
> Thoughts? Anyone with experience with such a process?
>
> Ludo’.
next prev parent reply other threads:[~2021-10-27 23:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 21:22 Time for a request-for-comments process? Ludovic Courtès
2021-10-27 22:28 ` 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 [this message]
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=dc74f8b97792d10a48aed71712935b15@dismail.de \
--to=jbranso@dismail.de \
--cc=guix-devel@gnu.org \
--cc=ludo@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).