public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Denis Dupeyron <calchan@gentoo.org>
To: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Resolve unfinished GLEP 39 business
Date: Fri, 11 Sep 2009 18:38:55 -0600	[thread overview]
Message-ID: <7c612fc60909111738u799458fp9f4266bf00fb7856@mail.gmail.com> (raw)
In-Reply-To: <200909120600.14217.vapier@gentoo.org>

On Sat, Sep 12, 2009 at 4:00 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> i still dont see what is wrong with the amendment process that has been used
> multiple times in the past
[...]
> council members are *voted in* because the community *trusts them to make the
> important decisions*.  if the decision made really pisses off the community,
> again you will hear about it and you can take the response into consideration.
> plus, if you do something really stupid, it isnt like your ass will remain in
> power.

I totally agree with you. However a majority of council members and
many devs seem to think that since GLEP 39 was originally voted by all
devs then every amendment to it needs to also be voted by all devs. As
I saw that coming I asked the council to vote on whether it could
decide on a process and the outcome was no. The only sensible way to
go forward now is thus to ask developers what they want us to do. The
other alternatives are not amending GLEP 39 or asking all devs to vote
on each amendments. The former is obviously silly and I'm convinced
the latter, although logical, isn't a good practical solution and may
not be what a majority of devs want.

Denis.



  reply	other threads:[~2009-09-12  0:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 20:37 [gentoo-council] Resolve unfinished GLEP 39 business Denis Dupeyron
2009-09-12 10:00 ` Mike Frysinger
2009-09-12  0:38   ` Denis Dupeyron [this message]
2009-09-12 12:26     ` Mike Frysinger
2009-09-12  5:21   ` Andrew D Kirch
2009-09-21  9:46 ` [gentoo-council] " Torsten Veller

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=7c612fc60909111738u799458fp9f4266bf00fb7856@mail.gmail.com \
    --to=calchan@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