linux-coco.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Jörg Rödel" <jroedel@suse.de>
To: Claudio Carvalho <cclaudio@linux.ibm.com>
Cc: amd-sev-snp@lists.suse.com, linux-coco@lists.linux.dev
Subject: Re: [RFD] COCONUT-SVSM project governance
Date: Wed, 24 May 2023 12:49:29 +0200	[thread overview]
Message-ID: <ZG3rubI1enwgiYpN@suse.de> (raw)
In-Reply-To: <53adca2d4e8287f2189c631be611c9c76ee1b708.camel@linux.ibm.com>

On Thu, May 11, 2023 at 03:26:30PM -0400, Claudio Carvalho wrote:
> At least 3 maintainers looks good, but I think we will have a better answer once
> we know the number of maintainer candidates and their experience/interest.

Yeah, I also think that 3 is a good starting point. Having more probably
does not make sense before the community reaches a certain size or we
get to a sub-maintainer model.

> An option could be to have maintainer(s) per area. I have worked on the
> vtpm/attestation for the AMDESE/linux-svsm and I could help to maintain it (and
> other parts) in the coconut-svsm.

That definitly makes sense. There will likely also be effort to make
certain parts of the code more generic, so that the different parts are
easier to maintain.


> We may also want to discuss about release plan/model; e.g. the dynamics of new
> releases, how often they will happen and if there is any priority that we need
> to consider in the short term.

That are all interesting points. In my opinion it is too early to think
about doing a release. But we can discuss possible release models so
that we are ready when it actually happens.

Regards,

-- 
Jörg Rödel
jroedel@suse.de

SUSE Software Solutions Germany GmbH
Frankenstraße 146
90461 Nürnberg
Germany

(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman


      reply	other threads:[~2023-05-24 10:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 10:15 [RFD] COCONUT-SVSM project governance Jörg Rödel
2023-05-08 16:28 ` Dionna Amalie Glaze
2023-05-24 10:39   ` Jörg Rödel
2023-05-11 19:26 ` Claudio Carvalho
2023-05-24 10:49   ` Jörg Rödel [this message]

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=ZG3rubI1enwgiYpN@suse.de \
    --to=jroedel@suse.de \
    --cc=amd-sev-snp@lists.suse.com \
    --cc=cclaudio@linux.ibm.com \
    --cc=linux-coco@lists.linux.dev \
    /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.
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 NNTP newsgroup(s).