From: Simon Tournier <zimon.toutoune@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: efraim@flashner.co.il, guix-devel@gnu.org,
guix-maintainers@gnu.org, ludo@gnu.org, mail@cbaines.net,
rekado@elephly.net
Subject: Re: Guix Common Document process (v7) (was: Request-For-Comment, RFC)
Date: Wed, 15 Jan 2025 20:18:50 +0100 [thread overview]
Message-ID: <87o7073mxx.fsf@gmail.com> (raw)
In-Reply-To: <87tta4nk21.fsf@systemreboot.net>
Hi,
On Sun, 12 Jan 2025 at 15:11, Arun Isaac <arunisaac@systemreboot.net> wrote:
> On the matter of communication channels for the RFC process, can we have
> a separate mailing list for RFC announcements?
An announce to info-guix@gnu.org, does it appear to you enough?
Well, the RFC will be low traffic, I guess. And info-guix seems a good
start.
WDYT?
Please note that this was part of submission v7. :-)
Cheers,
simon
next prev parent reply other threads:[~2025-01-15 22:42 UTC|newest]
Thread overview: 36+ 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
2025-01-08 15:15 ` Suhail Singh
2025-01-09 17:33 ` Simon Tournier
2025-01-09 23:49 ` bokr
2025-01-10 6:26 ` Suhail Singh
2025-01-15 18:42 ` Simon Tournier
2025-01-10 0:07 ` Guix Common Document process (v7) (was: Request-For-Comment, RFC) Simon Tournier
2025-01-12 15:11 ` Arun Isaac
2025-01-15 15:34 ` Andreas Enge
2025-01-15 21:50 ` Guix Common Document process (v7) indieterminacy
2025-01-15 22:32 ` Guix Common Document process (v7) (was: Request-For-Comment, RFC) Simon Tournier
2025-01-15 22:32 ` [bug#74736] " Simon Tournier
2025-01-15 23:28 ` Vagrant Cascadian
2025-01-16 9:23 ` [bug#74736] " Andreas Enge
2025-01-16 12:04 ` Guix Common Document process (v7) Suhail Singh
2025-01-16 16:10 ` bug#74736: [PATCH v2 0/1] Add Request-For-Comment process Ludovic Courtès
2025-01-16 18:01 ` Simon Tournier
2025-01-17 9:37 ` Ludovic Courtès
2025-01-15 19:18 ` Simon Tournier [this message]
2025-01-16 13:21 ` Guix Common Document process (v7) (was: Request-For-Comment, RFC) Arun Isaac
2025-01-14 18:28 ` bokr
2025-01-15 19:22 ` Simon Tournier
2025-01-17 1:06 ` Guix Consensus Document process (v10) Simon Tournier
2025-01-19 21:52 ` Ludovic Courtès
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=87o7073mxx.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=arunisaac@systemreboot.net \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
--cc=rekado@elephly.net \
/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.