unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
	"Thiago Jung Bauermann" <bauermann@kolabnow.com>
Cc: Guix Devel <guix-devel@gnu.org>,
	Katherine Cox-Buday <cox.katherine.e@gmail.com>
Subject: Re: Time for a request-for-comments process?
Date: Sat, 30 Oct 2021 17:57:27 +0200	[thread overview]
Message-ID: <86sfwijyjc.fsf@gmail.com> (raw)
In-Reply-To: <878rybzx62.fsf@gnu.org>

Hi Ludo,

On Fri, 29 Oct 2021 at 17:08, Ludovic Courtès <ludo@gnu.org> wrote:

> As zimoun wrote, a big question is formalization.  I haven’t yet taken
> the time to look at those other project RFC processes I mentioned, but
> we should do that.  Important questions are: how do we determine whether
> a change is important enough to be RFC-worthy?  How do we determine
> whether it’s accepted or withdrawn?  Perhaps that will unfold broader
> questions about structuring and decision-making.
>
> If anyone feels like giving a hand of this formalization effort, please
> feel empowered to do so!

I could volunteer for being part of the formalization effort.  However,
as I said elsewhere, this effort should start be collecting what do we
consider as changes requiring formal process?

For example, “guix shell” is one instance.  The recent “input label” is
another one.  Authentication another.  Without such list – even rough –
it seems hard to think about a process grounded on our past practises
for improving them and becoming applicable by our community – for what
my opinion is worth. :-)


Cheers,
simon


  reply	other threads:[~2021-10-30 16:01 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 [this message]
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=86sfwijyjc.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=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).