public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [PATCH 6/6] glep-0039: Projects need not have a lead
Date: Sun, 27 Nov 2022 05:43:08 +0000	[thread overview]
Message-ID: <robbat2-20221127T053531-135816966Z@orbis-terrarum.net> (raw)
In-Reply-To: <20221125182032.18483-7-ulm@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]

On Fri, Nov 25, 2022 at 07:20:32PM +0100, Ulrich Müller wrote:
> -   *  It may have one or many leads, and the leads are
> -      selected by the members of the project.  This selection must
> -      occur at least once every 12 months, and may occur at any
> -      time.
> +   *  It should have at least one lead, and the leads are selected by
> +      the members of the project.  This selection must occur at least
> +      once every 12 months, and may occur at any time.

The subject line buries the lede here ;-).

If the GLEPs are trying to follow RFC 2119 language semantics.

"SHOULD" is "recommended"
"MAY" is "truly optional"

How about this, again in line with RFC 2119 (formatted for ease of discussion):
==
It is recommended that projects have at least one lead. 
It is recommended that leads are selected by members of the project.
Lead selection may occur at any time.
Lead selection is required to occur least once every 12 months.
==

-- 
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Treasurer
E-Mail   : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1113 bytes --]

  reply	other threads:[~2022-11-27  5:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 18:20 [gentoo-project] [PATCH 0/6] Some updates for GLEP 39 Ulrich Müller
2022-11-25 18:20 ` [gentoo-project] [PATCH 1/6] glep-0039: Update title Ulrich Müller
2022-11-25 18:20 ` [gentoo-project] [PATCH 2/6] glep-0039: Updating GLEP 39 requires an all-developers vote Ulrich Müller
2022-11-25 18:20 ` [gentoo-project] [PATCH 3/6] glep-0039: Replace leaving council members by next in line Ulrich Müller
2022-11-25 19:02   ` Ulrich Mueller
2022-11-25 18:20 ` [gentoo-project] [PATCH 4/6] glep-0039: Council members must be developers Ulrich Müller
2022-11-25 18:20 ` [gentoo-project] [PATCH 5/6] glep-0039: A meeting must dissolve if not quorate Ulrich Müller
2022-11-27  9:04   ` Ulrich Mueller
2022-11-25 18:20 ` [gentoo-project] [PATCH 6/6] glep-0039: Projects need not have a lead Ulrich Müller
2022-11-27  5:43   ` Robin H. Johnson [this message]
2022-11-27  8:44     ` Ulrich Mueller
2022-11-25 18:25 ` [gentoo-project] [PATCH 7/6] glep-0039: Update Post-History Ulrich Müller
2022-11-29 19:37 ` [gentoo-project] [PATCH 0/6] Some updates for GLEP 39 John Helmert III
2022-11-29 20:12   ` Ulrich Mueller
2022-11-29 20:23     ` John Helmert III

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=robbat2-20221127T053531-135816966Z@orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --cc=gentoo-project@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox