all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
	"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Cc: John Kehayias <john.kehayias@protonmail.com>,
	Guix Devel <guix-devel@gnu.org>,
	guix-maintainers@gnu.org, Leo Famulari <leo@famulari.name>,
	Tobias Geerinckx-Rice <me@tobias.gr>,
	Andreas Enge <andreas@enge.fr>
Subject: Re: Upgrading Guix's security team
Date: Wed, 29 Nov 2023 17:15:59 +0100	[thread overview]
Message-ID: <87v89kr0w0.fsf@gmail.com> (raw)
In-Reply-To: <8734wxk616.fsf@gnu.org>

Hi,

On mer., 22 nov. 2023 at 19:16, Ludovic Courtès <ludo@gnu.org> wrote:

> Leo, Tobias, and John: What would be a good end-of-term date for each
> one of you?  As I see it, it wouldn’t mean you cannot do an additional
> term but rather that you’ll have an opportunity to leave and that you’ll
> do your best to be around by then.

I think all this should be encoded in some RFC as proposed in:

        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

Well, this RFC proposal appears to me a good opportunity for clarifying
the scope. role. end-of-term, etc. about the Security Team.

Cheers,
simon


  parent reply	other threads:[~2023-11-29 19:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 15:41 Upgrading Guix's security team John Kehayias
2023-11-16 14:22 ` Ludovic Courtès
2023-11-16 15:15   ` Andreas Enge
2023-11-18  4:31   ` Maxim Cournoyer
2023-11-18 19:18     ` Efraim Flashner
2023-11-22 18:16       ` Ludovic Courtès
2023-11-22 18:39         ` Leo Famulari
2023-11-22 19:02           ` Tobias Geerinckx-Rice
2023-12-09 10:55             ` Ludovic Courtès
2023-11-23  6:50         ` John Kehayias
2023-11-29 16:15         ` Simon Tournier [this message]
2024-02-05 19:34   ` Hartmut Goebel

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=87v89kr0w0.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=john.kehayias@protonmail.com \
    --cc=leo@famulari.name \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=me@tobias.gr \
    /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.