From: "Ludovic Courtès" <ludo@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>,
Efraim Flashner <efraim@flashner.co.il>,
Ricardo Wurmus <rekado@elephly.net>,
Christopher Baines <mail@cbaines.net>,
GNU Guix maintainers <guix-maintainers@gnu.org>
Subject: Re: Request-For-Comment process: concrete implementation (v5)
Date: Tue, 07 Jan 2025 11:40:11 +0100 [thread overview]
Message-ID: <87zfk229h0.fsf@gnu.org> (raw)
In-Reply-To: <87ttafn3p2.fsf@gmail.com> (Simon Tournier's message of "Fri, 03 Jan 2025 19:38:01 +0100")
Hello Guix!
Simon Tournier <zimon.toutoune@gmail.com> skribis:
> Below the updated version (v5) of the RFC introducing the RFC process.
>
> The submission is: <https://issues.guix.gnu.org/74736#22>.
And now v6! https://issues.guix.gnu.org/74736#27
> Well, a very good lesson is: Co-supporter is very important! It helps
> in crossing the final line. :-) In other words, the Timeline had not
> been respected at all because the lack of an initial Co-supporter.
Yes, would be nice if some of you reading this could offer to become
“supporters”.
> Almost two months ago, Noé resumed the proposal [1]. It appears to me
> that now we are close to the end of the Comment period.
>
> Yeah any comment is very welcome. :-)
>
> Then, I propose to start the Last Call the 17th (January) and finalize
> (or withdraw) for the end of the month (January, 31th) – in both cases,
> a good opportunity to share a drink at Guix Days in Brussels. :-)
Even better if we can finalize before Guix Days so:
discussion period ending on Jan. 14th
deliberation period ending on Jan. 28th
How does that sound?
Everyone: this may sound like boring administrative stuff, but in fact,
it’s pretty crucial for the well-being of the project (meaning: the
people!) going forward. It’s a fairly simple process that ensures
important decisions are properly discussed and decided on, and that
everyone gets a chance to weigh in.
Without such a process, it’s either authoritarianism or stagnation.
Please take a look, comment, offer your name as a “supporter”, and then
make your voice heard during the deliberation period!
Ludo’.
next prev parent reply other threads:[~2025-01-07 10:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 11:14 Request-For-Comment process: concrete implementation Simon Tournier
2023-11-16 15:03 ` Ludovic Courtès
2023-11-20 9:42 ` Simon Tournier
2023-11-22 18:17 ` Ludovic Courtès
2023-11-23 7:04 ` Efraim Flashner
2023-11-28 13:34 ` Simon Tournier
2023-12-19 12:33 ` Simon Tournier
2023-12-20 11:49 ` Ricardo Wurmus
2024-02-03 10:09 ` Simon Tournier
2024-02-03 10:34 ` [post Guix Days] Guix Common Document (was: Request-For-Comment process) Simon Tournier
2024-02-07 8:27 ` Efraim Flashner
2025-01-03 18:38 ` Request-For-Comment process: concrete implementation (v5) Simon Tournier
2025-01-07 10:40 ` Ludovic Courtès [this message]
2025-01-08 15:15 ` Suhail Singh
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zfk229h0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=mail@cbaines.net \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.