From: John Kehayias <john.kehayias@protonmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.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: Thu, 23 Nov 2023 06:50:11 +0000 [thread overview]
Message-ID: <87jzq9yndx.fsf@protonmail.com> (raw)
In-Reply-To: <8734wxk616.fsf@gnu.org>
Hi Ludo’ and everyone else,
On Wed, Nov 22, 2023 at 07:16 PM, Ludovic Courtès wrote:
> Hello,
>
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
>> On Fri, Nov 17, 2023 at 11:31:41PM -0500, Maxim Cournoyer wrote:
>
> [...]
>
>>> > If maintainers agree (Cc’d), I invite you to add your name and a
>>> > termination date to the security page, remove my name, and subscribe to
>>> > guix-security. We should add a term for other people on the team too.
>>> >
>>> > How does that sound?
>>>
>>> Sounds good to me!
>>
>> Sounds good to me too.
>
> I added John and removed myself from the security page in guix-artwork
> commit 1bd9d383cc1de4cf0eb220129c065a98332b798b.
>
Thanks and happy to be a part of the team!
> I’ve also unsubscribed Andreas and myself from the list; there are now 4
> people subscribed (we should check whether the 4th person wants to be
> officially involved).
>
> 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.
>
Seeing as how I'm often away from any Guix computers for a few weeks
at a time over the summer, let me say roughly 6 months, ending on May
15th.
As you say, likely I would be happy to continue, though parts of
summer I tend to be away so it would be good to not have us
shorthanded then. Or maybe staggering when people join/leave with some
overlap is a good plan.
> Thanks again for volunteering, John!
>
> Ludo’.
Welcome and hoping to serve the Guix community well!
John
next prev parent reply other threads:[~2023-11-23 6:50 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jzq9yndx.fsf@protonmail.com \
--to=john.kehayias@protonmail.com \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--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.