From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: gentoo-core@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo metastructure update (GLEP 39) voting now open
Date: Tue, 25 Apr 2023 09:15:34 +0200 [thread overview]
Message-ID: <uv8hk77qh@gentoo.org> (raw)
In-Reply-To: <u354pabaq_-_@gentoo.org> (Ulrich Mueller's message of "Mon, 24 Apr 2023 11:18:05 +0200")
[-- Attachment #1: Type: text/plain, Size: 1667 bytes --]
>>>>> On Mon, 24 Apr 2023, Ulrich Mueller wrote:
> Voting for the update of the Gentoo metastructure document (GLEP 39)
> is now open. The election is named "metastructure-2023".
> Login to dev.gentoo.org and use "votify --help" to get instructions
> on how to vote, verify, and submit your ballot.
> Voting closes at 2023-05-08 00:00:00 UTC (= end of day 2023-05-07).
I received a comment that it would be hard to figure out what this vote
is about. So here is a summary of the changes, with pointers to the
respective commits (where you'll find more information about these
changes):
* Replace leaving council members by next in line
https://gitweb.gentoo.org/data/glep.git/commit/?id=c4df5974adab69d97f5118d0f7f693167a50581c
* Updating this document requires an all-developers vote
https://gitweb.gentoo.org/data/glep.git/commit/?id=f94967967abc1f7f506d3ebbe9e23b8b7c05d1b9
* Council members must be developers
https://gitweb.gentoo.org/data/glep.git/commit/?id=890b3b73a05bdbe3fdc171ab01b7428510737fe3
* An inquorate council meeting cannot take any substantive action
https://gitweb.gentoo.org/data/glep.git/commit/?id=29bfaccbe91395059dacf47dfa9759283301aed2
* Drop hard requirement of yearly project lead elections
https://gitweb.gentoo.org/data/glep.git/commit/?id=1dbe638f022c64bd29dfbe4d0a8bd55ca49d1549
https://gitweb.gentoo.org/data/glep.git/commit/?id=e9027e1d081ea5737230985110dc044fce40039d
We will also update the title:
-Title: An "old-school" metastructure proposal with "boot for being a slacker"
+Title: Gentoo metastructure
Crossposting to -core this time to reach all developers, but please
reply to -project only.
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2023-04-25 7:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 3:43 [gentoo-project] Council Meeting 2023-04-09: Call for Agenda Items John Helmert III
2023-03-29 5:14 ` Ulrich Mueller
2023-03-29 5:29 ` Ulrich Mueller
2023-03-29 14:41 ` Rich Freeman
2023-03-29 16:11 ` Ulrich Mueller
2023-04-10 17:37 ` [gentoo-project] Update of Gentoo metastructure document aka GLEP 39 (was: Re: Council Meeting 2023-04-09: Call for Agenda Items) Ulrich Mueller
2023-04-10 18:48 ` Robin H. Johnson
2023-04-10 21:28 ` [gentoo-project] Update of Gentoo metastructure document aka GLEP 39 Ulrich Mueller
2023-04-11 16:24 ` Ulrich Mueller
2023-04-15 9:33 ` Roy Bamford
2023-04-16 8:24 ` [gentoo-project] " Ulrich Mueller
2023-04-24 9:18 ` [gentoo-project] Gentoo metastructure update (GLEP 39) voting now open Ulrich Mueller
2023-04-25 7:15 ` Ulrich Mueller [this message]
2023-04-30 16:30 ` [gentoo-project] Re: [gentoo-dev-announce] Gentoo metastructure update (GLEP 39) voting now open - 7 days left Jorge Manuel B. S. Vicetto
[not found] ` <d43987ddf5371b1b883cfe0b712e683baec62379.camel@gentoo.org>
2023-05-03 6:58 ` Ulrich Mueller
2023-05-03 11:59 ` Michael Orlitzky
2023-03-31 17:02 ` [gentoo-project] Re: Council Meeting 2023-04-09: Call for Agenda Items Andreas K. Huettel
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=uv8hk77qh@gentoo.org \
--to=ulm@gentoo.org \
--cc=gentoo-core@lists.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