From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Christopher Baines" <mail@cbaines.net>
Cc: guix-devel@gnu.org, guix-europe-sac@gnu.org, guix-maintainers@gnu.org
Subject: RFC (was Re: Shutting down qa.guix?)
Date: Wed, 13 Dec 2023 17:43:19 +0100 [thread overview]
Message-ID: <87le9y3vfc.fsf@gmail.com> (raw)
In-Reply-To: <875y177iik.fsf@gnu.org>
Hi Ludo,
On sam., 09 déc. 2023 at 11:54, Ludovic Courtès <ludo@gnu.org> wrote:
> I know this has been discussed several times and it remains unclear to
> me why as a project we never managed to move forward—maybe the comfort
> of the status quo?
It would help if the project would have a process for such move. Why
not some Request-For-Comment?
Request-For-Comment process: concrete implementation
Simon Tournier <zimon.toutoune@gmail.com>
Tue, 31 Oct 2023 12:14:42 +0100
id:87h6m7yrfh.fsf@gmail.com
https://lists.gnu.org/archive/html/guix-devel/2023-10
https://yhetil.org/guix/87h6m7yrfh.fsf@gmail.com
Cheers,
simon
next prev parent reply other threads:[~2023-12-19 14:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 13:32 November/December update on qa.guix.gnu.org and related things Christopher Baines
2023-12-09 10:39 ` Discontinuing data.guix.gnu.org? Ludovic Courtès
2023-12-09 11:14 ` Christopher Baines
2024-01-09 18:12 ` Ludovic Courtès
2024-01-09 18:33 ` Julien Lepiller
2024-01-09 19:19 ` Gábor Boskovits
2024-01-10 0:38 ` Maxim Cournoyer
2023-12-09 10:54 ` Shutting down qa.guix? Ludovic Courtès
2023-12-09 12:16 ` Christopher Baines
2023-12-09 13:30 ` Tobias Geerinckx-Rice
2023-12-10 10:54 ` Christopher Baines
2023-12-10 16:05 ` Maxim Cournoyer
2023-12-11 13:30 ` Christopher Baines
2023-12-10 18:50 ` Simon Tournier
2023-12-13 16:43 ` Simon Tournier [this message]
2024-01-18 12:39 ` [Guix-europe-sac] " Andreas Enge
2024-01-20 12:57 ` Christopher Baines
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=87le9y3vfc.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=guix-europe-sac@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=ludo@gnu.org \
--cc=mail@cbaines.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 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).