From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: "Ulrich Müller" <ulm@gentoo.org>
Subject: [gentoo-project] [PATCH 3/6] glep-0039: Replace leaving council members by next in line
Date: Fri, 25 Nov 2022 19:20:29 +0100 [thread overview]
Message-ID: <20221125182032.18483-4-ulm@gentoo.org> (raw)
In-Reply-To: <20221125182032.18483-1-ulm@gentoo.org>
Accepted in the 2007-02-08 council meeting. Wording slightly updated,
in order to clarify that even after an election the new council member
will get a reduced term.
This is already current practice and was followed by the council
several times in the past: 2007-03-08 (uberlord), 2007-06-14 (jaervosz),
2008-09-11 (cardoe), 2009-02-26 (leio), 2009-05-28 (ulm),
2011-01-11 (patrick).
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
---
glep-0039.rst | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/glep-0039.rst b/glep-0039.rst
index e2fe477..7443ae1 100644
--- a/glep-0039.rst
+++ b/glep-0039.rst
@@ -148,9 +148,15 @@ B. Global issues will be decided by an elected Gentoo council.
two consecutive meetings, they are marked as a slacker.
* If a council member who has been marked a slacker misses any further
meeting (or their appointed proxy doesn't show up), they lose their
- position and a new election is held to replace that person. The newly
- elected council member gets a 'reduced' term so that the yearly
- elections still elect a full group.
+ position.
+ * Whenever a member of the council loses their position (the reason
+ is irrelevant; e.g. they resign or they are booted for slacking),
+ then the next person in line from the previous council election
+ is offered the position. If they accept and the current council
+ unanimously accepts the new person, they get the position.
+ Otherwise, it is offered to the next person in line, and so forth.
+ The new member gets a 'reduced' term so that the yearly elections
+ still elect a full group.
* Council members who have previously been booted for excessive slacking
may stand for future elections, including the election for their
replacement. They should, however, justify their slackerness, and
--
2.38.1
next prev parent reply other threads:[~2022-11-25 18:21 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 ` Ulrich Müller [this message]
2022-11-25 19:02 ` [gentoo-project] [PATCH 3/6] glep-0039: Replace leaving council members by next in line 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 ` [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=20221125182032.18483-4-ulm@gentoo.org \
--to=ulm@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