unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: John Kehayias <john.kehayias@protonmail.com>,
	Guix Devel <guix-devel@gnu.org>,
	guix-maintainers@gnu.org
Subject: Re: Upgrading Guix's security team
Date: Thu, 16 Nov 2023 16:15:32 +0100	[thread overview]
Message-ID: <ZVYyFLKmJnS8AgCy@jurong> (raw)
In-Reply-To: <8734x5ydzh.fsf@gnu.org>

Hello,

Am Thu, Nov 16, 2023 at 03:22:42PM +0100 schrieb Ludovic Courtès:
> Yes, we definitely need a rotation here!  I for one have my name there
> but regardless of my interest, I have to admit that I’ve been unable to
> be sufficiently responsive.  It’s time to let new folks take
> responsibility.
> I think we should make this a fixed-term position, to make it easier for
> people to commit to actually being active when needed, with the
> understanding that it’s not a commitment for life.

all this sounds good. Maybe we should also clean up the mailing list.
I am on the list, but not mentioned on the security team site, and will
be happy to be removed. (My being here probably comes from a mismatch
between being interested in "security" and knowing things about "crypto-
graphy", and my inability to act upon concrete situations of security
problems in packages.)

Andreas



  reply	other threads:[~2023-11-16 15:16 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 [this message]
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
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

  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=ZVYyFLKmJnS8AgCy@jurong \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=john.kehayias@protonmail.com \
    --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).