public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [RFC] pre-GLEP: Gentoo General Resolution
Date: Fri, 29 Jun 2018 20:32:25 +0200	[thread overview]
Message-ID: <1530297145.737.44.camel@gentoo.org> (raw)
In-Reply-To: <20180629051228.GC3190@angelfall.a21an.org>

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

W dniu pią, 29.06.2018 o godzinie 08∶12 +0300, użytkownik Eray Aslan
napisał:
> On Thu, Jun 28, 2018 at 06:14:15PM +0200, Michał Górny wrote:
> > The text of a new GLEP proposal follows.  The GLEP implements a General
> > Resolution mechanism based on the one in Debian; the idea was initially
> > proposed by Matthias Maier [1]; however, he didn't manage to find time
> > to write the GLEP.
> > 
> > Please review the proposed text and let me know what you think.  Please
> > note that the numbers presented have been chosen arbitrarily and are up
> > for discussion.
> > 
> > [1]:https://archives.gentoo.org/gentoo-project/message/973be0a662b3cc74aa118a1128dcac9e
> 
> Thanks for the write up.
> 
> The numbers set too high a threshold to make it almost impossible to use
> GR.  Debian defaults seems sane.  Is there any particular reason we are
> changing them?
> 

The main difference is that Debian's GR is a generic voting mechanism
that's supposed to be used ocassionally.  Our GR is a fail-safe for
Council behaving silly or going rogue.  It's not supposed to be used
under normal circumstances.

I've chosen our numbers to be high enough to discourage attempted abuse
while making it possible to actually use GR when necessary.  Which
numbers are you specifically talking about?

If it's about N1 and N2, they may seem like many but I should point out
that after all we're talking about majority of the developers
disagreeing with the Council.

N1 being around 30 developers may seem large but it's certainly smaller
than the number of Gentoo developers actively contributing to Gentoo
every day.  I get that getting them all to sign off is cumbersome but if
there's a real reason to use GR, I'm pretty sure they'll find
the motivation to do that.

N2 being 25% developers is really small.  We're talking about all-dev
vote, so really expecting at least 25% to actively take part is a must. 
It's larger than N1 but we're talking of a vote that's handled via
voting mechanism all devs are supposed to notice.

The 2:1 majority is what Debian uses for overriding decisions of TC.
So it's certainly not larger.  In some cases Debian uses 3:1.

-- 
Best regards,
Michał Górny

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

  reply	other threads:[~2018-06-29 18:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 16:14 [gentoo-project] [RFC] pre-GLEP: Gentoo General Resolution Michał Górny
2018-06-28 17:24 ` Rich Freeman
2018-06-28 19:03   ` Aaron Bauman
2018-06-28 19:33     ` Rich Freeman
2018-06-28 20:08       ` Aaron Bauman
2018-06-28 20:39         ` Rich Freeman
2018-06-28 20:32   ` Michał Górny
2018-06-28 20:42     ` Rich Freeman
2018-06-28 21:20   ` M. J. Everitt
2018-06-29  5:12 ` Eray Aslan
2018-06-29 18:32   ` Michał Górny [this message]
2018-07-02  8:21     ` Eray Aslan
2018-07-02 13:42       ` Michał Górny

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=1530297145.737.44.camel@gentoo.org \
    --to=mgorny@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