linux-coco.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Jörg Rödel" <jroedel@suse.de>
To: Dionna Amalie Glaze <dionnaglaze@google.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:39:02 +0200	[thread overview]
Message-ID: <ZG3pRhRPTXl1FkGG@suse.de> (raw)
In-Reply-To: <CAAH4kHYpyeu-UFBYL5mXnS0xQh_rD039FgMz=Qfa=ruCUsVL_A@mail.gmail.com>

Hi Dionna,

On Mon, May 08, 2023 at 09:28:40AM -0700, Dionna Amalie Glaze wrote:
> I'm in favor of governance models that strongly value transparency,
> good-faith disagreement, and a set of community guidelines that both
> has enforcement power and accountability of all parties involved.

Thanks for your input, I completly agree with that baseline. One thing
to keep in mind is that any processes and rules we potentially put in
place are aligned with the size of the community. Really large
communities like for Rust or K8s certainly need different governance
than ours.

> 3 is a minimum I think, with at least 2 entities represented.

Right, we need to make sure different entities are represented.

> I think the sigstore.dev project does a good job of running regular
> community meetings and publishing meeting notes to allow for regular
> collaboration across institutions.
> I don't think we need to set that up until there's a good reason to
> take a discussion off the mailing list for higher bandwidth
> communication, since who needs more low value meetings?
> 
> [1] https://github.com/ossf/scorecard
> [2] Robert's Rules of Order
> [3] https://www.redhat.com/en/blog/understanding-open-source-governance-models
> [4] https://www.youtube.com/watch?v=m0rakUuPXFM

Thanks, that is a lot of good input. I think in general we need to find
a balance between the needed bureaucracy to ensure fairness and
inclusiveness on one side, and being able to stay productive and make
decissions as needed on the other. That balance might shift with the
size of the community, of course.

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:39 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 [this message]
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=ZG3pRhRPTXl1FkGG@suse.de \
    --to=jroedel@suse.de \
    --cc=amd-sev-snp@lists.suse.com \
    --cc=dionnaglaze@google.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).