From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] [RFC] pre-GLEP: Gentoo General Resolution
Date: Thu, 28 Jun 2018 16:42:52 -0400 [thread overview]
Message-ID: <CAGfcS_mSAiX59Uwa4LuEtA=RM-uKjtj1FeDsrui_+LSjw6Qn7A@mail.gmail.com> (raw)
In-Reply-To: <1530217973.901.19.camel@gentoo.org>
On Thu, Jun 28, 2018 at 4:32 PM Michał Górny <mgorny@gentoo.org> wrote:
>
> W dniu czw, 28.06.2018 o godzinie 13∶24 -0400, użytkownik Rich Freeman
> napisał:
> > On Thu, Jun 28, 2018 at 12:14 PM Michał Górny <mgorny@gentoo.org> wrote:
> > >
> > > a. the Council decision in question is final (i.e. a general
> > > resolution can not be used to bypass the Council),
> >
> > One question that this brings up in my mind is the duration of these
> > decisions, because Council decisions are never really final. The
> > Council can override its own decisions, or the decision of a prior
> > Council.
>
> The meaning of this is explained in the parentheses, so please stop
> trying to bend it. The only thing it means is that you can't call a GR
> to pass a motion that didn't go through the Council vote yet.
I was not suggesting that this meaning wasn't plain. I was just
saying that no Council decision is final as a way to bring up the
topic of duration/etc. I'm not proposing changing the wording of this
part of the GLEP.
> When Council makes an apparently bad decision, the developers can give
> it a yellow card. The Council is still in the game and can technically
> can do the same thing again -- however, it has been given an explicit
> warning, so I don't think we really need to consider it carelessly
> passing the same motion again.
Sure, that makes sense, and that wasn't actually what I got out of it
the first time. I just assumed this was a way to just do direct
democracy, and not merely a way to strike down an individual decision.
> No. The GLEP repeats that multiple times: GR is not a generic voting
> mechanism but a failsafe. I'd say calling for a global developer vote
> is within Council's regular powers, and it's entirely outside the scope
> of this GLEP.
Ok, that wasn't what I thought you were proposing, and I think that
makes more sense.
>
> It really seems that you didn't understand the GLEP, and instead started
> processing with your own vision of GR that's not related to my proposal.
>
Indeed.
--
Rich
next prev parent reply other threads:[~2018-06-28 20:43 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 [this message]
2018-06-28 21:20 ` M. J. Everitt
2018-06-29 5:12 ` Eray Aslan
2018-06-29 18:32 ` Michał Górny
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='CAGfcS_mSAiX59Uwa4LuEtA=RM-uKjtj1FeDsrui_+LSjw6Qn7A@mail.gmail.com' \
--to=rich0@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