unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jbranso@dismail.de
To: "Katherine Cox-Buday" <cox.katherine.e@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>
Cc: "Guix Devel" <guix-devel@gnu.org>
Subject: Re: Time for a request-for-comments process?
Date: Wed, 27 Oct 2021 23:48:53 +0000	[thread overview]
Message-ID: <9e7b2e197720a843fcca984e2380b81e@dismail.de> (raw)
In-Reply-To: <87zgqu9k75.fsf@gmail.com>

October 27, 2021 6:51 PM, "Katherine Cox-Buday" <cox.katherine.e@gmail.com> wrote:

> Ludovic Courtès <ludo@gnu.org> writes:
> 
>> 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 think it's a good idea. The only contribution I can give is that I would not have known =guix
> shell= was coming had I not been watching the patches list. So in addition to formalizing what
> you've mentioned, I suggest we also formalize a location to watch (guix-devel seems logical?).
 
That's why I didn't see guix shell coming.  I don't follow guix patches...

> --
> Katherine


  parent reply	other threads:[~2021-10-27 23:49 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
2021-10-27 23:48 ` jbranso [this message]
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=9e7b2e197720a843fcca984e2380b81e@dismail.de \
    --to=jbranso@dismail.de \
    --cc=cox.katherine.e@gmail.com \
    --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).