public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: John Helmert III <ajak@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [PATCH 0/6] Some updates for GLEP 39
Date: Tue, 29 Nov 2022 13:37:12 -0600	[thread overview]
Message-ID: <Y4ZfaEnBf1QQo8PW@gentoo.org> (raw)
In-Reply-To: <20221125182032.18483-1-ulm@gentoo.org>

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

Could you add references to the relevant council decisions for these?

On Fri, Nov 25, 2022 at 07:20:26PM +0100, Ulrich Müller wrote:
> We recently saw a proposal by ajak for updating GLEP 39, which would
> require an all-developers vote. If we do that, we could use it to get
> some other changes in. Some of them are pending since many years;
> I have collected them from bugzilla, council meeting logs, and mailing
> list postings.
> 
> The patches in this series should be independent of each other (and of
> ajak's patch), so each of them can be discussed separately.
> 
> Ulrich Müller (6):
>   glep-0039: Update title
>   glep-0039: Updating GLEP 39 requires an all-developers vote
>   glep-0039: Replace leaving council members by next in line
>   glep-0039: Council members must be developers
>   glep-0039: A meeting must dissolve if not quorate
>   glep-0039: Projects need not have a lead
> 
>  glep-0039.rst | 30 ++++++++++++++++++++----------
>  1 file changed, 20 insertions(+), 10 deletions(-)
> 
> -- 
> 2.38.1
> 
> 

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

  parent reply	other threads:[~2022-11-29 19:37 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
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 ` John Helmert III [this message]
2022-11-29 20:12   ` [gentoo-project] [PATCH 0/6] Some updates for GLEP 39 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=Y4ZfaEnBf1QQo8PW@gentoo.org \
    --to=ajak@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