From: Matthias Maier <tamiko@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2018-04-08
Date: Mon, 02 Apr 2018 19:40:04 -0500 [thread overview]
Message-ID: <87a7ulktqz.fsf@gentoo.org> (raw)
In-Reply-To: <87muyt9njh.fsf@gentoo.org> (Matthias Maier's message of "Tue, 27 Mar 2018 17:11:30 -0500")
On Tue, Mar 27, 2018, at 17:11 CDT, Matthias Maier <tamiko@gentoo.org> wrote:
> [...]
I have the feeling that quite a bit of the current heated discussion
(about whatever) stems from a perceived lack of "democracy" in our
processes.
Therefore, I suggest as meeting agenda that the council discusses the
introduction of a "general resolution" similarly to the one that Debian
has [1]. Debian's version would have to be adapted to Gentoo specifics
but in short a possible version could include
- overruling council (and comrel?) decisions with a 2:1 majority
- a vote of no confidence forcing council reelections
- accepting/withdrawing/... GLEPs with a 2:1 majority
A vote could be initiated by
- the council itself
- a sufficient number of developers seconding the motion
Eligible voters would be Gentoo developers.
I am happy to author a first draft proposal GLEP. If this idea finds
enough supporters on the developer side and on the council, I suggest to
proceed as follows:
- let council accept the GLEP
- initiate a "general resolution" (or however we end up naming the
child) asking to support the GLEP formally.
I am tired of hearing that my decisions and that of my colleagues on the
council would be due to some agenda, sinister behavior or
whatever. A "general resolution" would introduce a nice mechanism that
would deter loud single voices ("the majority of developers is against
this and that") and let just speak the body of developers itself. I
suggest we make the bar of initiating such a vote relatively high (but
by no means impossible) so that we don't get swamped with too much
stuff, though.
Best,
Matthias
[1] https://www.debian.org/devel/constitution#item-4
next prev parent reply other threads:[~2018-04-03 0:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 22:11 [gentoo-project] Call for agenda items - Council meeting 2018-04-08 Matthias Maier
2018-03-28 14:33 ` R0b0t1
2018-03-29 21:55 ` Andreas K. Huettel
2018-03-29 9:52 ` Michał Górny
2018-03-29 11:39 ` Ulrich Mueller
2018-03-31 9:04 ` Ulrich Mueller
2018-03-29 10:13 ` Michał Górny
2018-03-29 11:24 ` Ulrich Mueller
2018-03-29 13:34 ` Michał Górny
2018-03-29 13:55 ` Ulrich Mueller
2018-03-29 22:00 ` Andreas K. Huettel
2018-03-29 11:46 ` Francisco Blas Izquierdo Riera (klondike)
2018-03-29 11:53 ` Rich Freeman
2018-03-29 13:09 ` Ulrich Mueller
2018-03-29 14:28 ` Francisco Blas Izquierdo Riera (klondike)
2018-03-29 22:02 ` Andreas K. Huettel
2018-03-29 20:26 ` Michał Górny
2018-03-29 22:39 ` Andreas K. Huettel
2018-03-30 5:18 ` Robin H. Johnson
2018-03-30 11:46 ` Rich Freeman
2018-04-02 10:00 ` Michał Górny
2018-04-02 15:43 ` Daniel Robbins
2018-04-02 15:46 ` Matthias Maier
2018-04-02 15:51 ` Daniel Robbins
2018-04-02 16:05 ` Ulrich Mueller
2018-04-02 16:07 ` Daniel Robbins
2018-04-03 3:22 ` R0b0t1
2018-04-04 3:57 ` Gregory Woodbury
2018-04-03 0:40 ` Matthias Maier [this message]
2018-04-03 1:01 ` Rich Freeman
2018-04-03 1:14 ` M. J. Everitt
2018-04-03 1:38 ` Matthias Maier
2018-04-03 1:46 ` Rich Freeman
2018-04-06 3:20 ` Robin H. Johnson
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=87a7ulktqz.fsf@gentoo.org \
--to=tamiko@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