linux-coco.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Jörg Rödel" <jroedel@suse.de>
To: amd-sev-snp@lists.suse.com
Cc: linux-coco@lists.linux.dev
Subject: [RFD] COCONUT-SVSM project governance
Date: Mon, 8 May 2023 12:15:46 +0200	[thread overview]
Message-ID: <ZFjL0oXu6NjYKCXl@suse.de> (raw)

Hi,

As discussed before[1] I'd like to start a discussion about the future
governance of COCONUT-SVSM. Bottom line is that the project should move
from a single-maintainer, SUSE-driven project to a multi-maintainer
model driven by the community.

[1] https://lore.kernel.org/linux-coco/ZFJTDtMK0QqXK5+E@suse.de/

Some of the things to discuss:

	* How many maintainers? (3 or more?)

	* How to select them (by contributions and trust in the
	  community? elections? If elections, who can vote?)

	* Regular changes to the maintainer group?

	* How the group makes decisions on merging contributions and
	  the general direction of the project.

And certainly more questions which I have not yet thought of. So I'd
like to invite everyone to share their thoughts and opinions in this
thread so that we can develop a way to an open project governance :)

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-08 10:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 10:15 Jörg Rödel [this message]
2023-05-08 16:28 ` [RFD] COCONUT-SVSM project governance 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

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=ZFjL0oXu6NjYKCXl@suse.de \
    --to=jroedel@suse.de \
    --cc=amd-sev-snp@lists.suse.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).