public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: Denis Dupeyron <calchan@gentoo.org>
Cc: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Council meeting summary of July 20th 2009
Date: Sun, 26 Jul 2009 19:06:02 -0700	[thread overview]
Message-ID: <20090727020602.GA14197@comet> (raw)
In-Reply-To: <7c612fc60907242254h34edf498n9b672358f5bf59ee@mail.gmail.com>

On 23:54 Fri 24 Jul     , Denis Dupeyron wrote:
> The log and summary of Monday's council meeting (July 20th 2009) are
> now available on the council project page at:
> http://www.gentoo.org/proj/en/council/

3. GLEP 39

  3.1. Can the council decide on the process of voting amendments to GLEP 39
  without an all-developers vote?
  > No: betelgeuse, dertobi123, solar, ulm.
  > Yes: calchan, leio.


I'd like some clarification here. GLEP 39 has already been amended by 
the council [1]. Are you declaring those modifications illegal and thus 
reverted? If so, this is retroactive because it changes the past and 
removes powers that were assumed by previous councils. Are you voting to 
remove powers the council previously had? If so, isn't that in itself an 
amendment of GLEP 39?

1. http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/glep/glep-0039.html?r1=1.2&r2=1.3

-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com



  reply	other threads:[~2009-07-27  2:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-25  5:54 [gentoo-council] Council meeting summary of July 20th 2009 Denis Dupeyron
2009-07-27  2:06 ` Donnie Berkholz [this message]
2009-07-27 14:46   ` Ned Ludd
2009-07-27 18:56     ` Petteri Räty
2009-07-29  1:32     ` Donnie Berkholz

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=20090727020602.GA14197@comet \
    --to=dberkholz@gentoo.org \
    --cc=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