unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thiago Jung Bauermann <bauermann@kolabnow.com>
To: Guix Devel <guix-devel@gnu.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Katherine Cox-Buday" <cox.katherine.e@gmail.com>
Subject: Re: Time for a request-for-comments process?
Date: Wed, 27 Oct 2021 21:07:06 -0300	[thread overview]
Message-ID: <3347007.yCl91LDo8C@popigai> (raw)
In-Reply-To: <87zgqu9k75.fsf@gmail.com>

Hello,

Em quarta-feira, 27 de outubro de 2021, às 19:28:14 -03, Katherine Cox-
Buday escreveu:
> 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.

Me too.

> 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?).

I agree that guix-devel is a good place to announce new RFCs, probably 
using an eye-catching subject prefix so that we can more easily see and 
filter them.

For RFCs where users are also stakeholders, we should also announce in 
places where users are likely to see them, such as the info-guix and help-
guix mailing lists, and possibly even the Guix blog (how far out do we want 
to spread the word?).

“guix shell” would have been an RFC with users as stakeholders, but I can 
imagine others where that isn’t the case, such as some significant but 
internal code reorganization.
-- 
Thanks,
Thiago




  reply	other threads:[~2021-10-28  0:07 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 [this message]
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=3347007.yCl91LDo8C@popigai \
    --to=bauermann@kolabnow.com \
    --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).