From: Torsten Veller <tove@gentoo.org>
To: gentoo-council@lists.gentoo.org
Subject: [gentoo-council] The slacker mark
Date: Fri, 26 Sep 2008 09:51:12 +0200 [thread overview]
Message-ID: <20080926091614.TA9636d.tv@veller.net> (raw)
As you know the by GLEP 39 council members are marked as slacker if they
(or their proxy) fail to show up for two consecutive meetings.
Being marked as slacker makes your council life much harder. While a
council member can miss every second meeting without consequences. A
slacker who "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."
So this might be a problem since yesterday's meeting:
lu_zero wasn't there for the second time in a row. If we follow GLPE 39
he'll get the slacker mark.
We should clearify the "new election" part in time. I think this council
started in July 2008 and there will be many meetings that can be missed
in the next 9 month.
As there is already a replacement strategy for devs leaving the council
(take the next ranked candidate if the council agrees, else elect one)
one might think to use the same for a slacker missing any further
meeting. But that doesn't work as the slacker can be elected again:
"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 should
expect to have it pointed out if they don't do so themselves."
Ideas?
next reply other threads:[~2008-09-26 7:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 7:51 Torsten Veller [this message]
2008-09-26 9:39 ` [gentoo-council] The slacker mark Peter Volkov
2008-09-26 14:50 ` Mark Loeser
[not found] ` <1222417867.6175.55.camel@media>
2008-09-26 9:53 ` Luca Barbato
2008-09-26 14:49 ` Mark Loeser
2008-09-26 22:12 ` Luca Barbato
2008-09-26 23:19 ` Ferris McCormick
2008-09-27 16:32 ` Roy Bamford
2008-09-26 15:08 ` Ned Ludd
2008-09-26 19:26 ` Mike Frysinger
2008-09-26 19:57 ` Ned Ludd
2008-09-26 20:25 ` Roy Bamford
2008-09-26 20:58 ` Ned Ludd
2008-09-27 0:26 ` Jorge Manuel B. S. Vicetto
2008-09-28 22:42 ` Mike Frysinger
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=20080926091614.TA9636d.tv@veller.net \
--to=tove@gentoo.org \
--cc=gentoo-council@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