public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Roy Bamford <neddyseagoon@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo: growing pains & the future.
Date: Tue, 18 Jun 2013 13:12:00 +0100	[thread overview]
Message-ID: <1371557523.2541.0@bluebottle> (raw)
In-Reply-To: <CAM3Znqo5JZF+fGsqz2iSyPjyLBqB1vzm+N-p36_Vq4eP+WJnZw@mail.gmail.com> (from djdunn.safety@gmail.com on Mon Jun 17 21:54:08 2013)

On 06/17/13 21:54:08, Douglas Dunn wrote:
> > GLEP 39 was originally voted in by all devs. The council has
> previously
> > decided it does not have the authority to change it. It might not 
> be
> a
> > bad idea to poll developers in connection to our yearly elections 
> on
> if
> > they still think GLEP 39 is current.
> >
> > Regards,
> > Petteri
> >
> 
> A good idea i think, but if we can come up with an
> amendment/replacement
> for glep 39 before then, it would be a perfect time to use the
> opportunity
> just to piggyback that vote for that change in with the yearly 
> council
> election and kill 2 birds with one stone
> 

A GLEP is a GLEP.  A GLEP that obsoletes GLEP 39 can be proposed by 
anyone at any time.  When/if it reaches council, they can determine 
that it needs a dev wide vote.

There is no need to do anything in a hurry.

-- 
Regards,

Roy Bamford
(Neddyseagoon) an member of
gentoo-ops
forum-mods
trustees


  parent reply	other threads:[~2013-06-18 12:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-16 21:21 [gentoo-project] Gentoo: growing pains & the future Robin H. Johnson
2013-06-16 22:13 ` Ciaran McCreesh
2013-06-17  8:36 ` Markos Chandras
2013-06-17 19:15   ` Petteri Räty
2013-06-17 20:54     ` Douglas Dunn
2013-06-17 21:17       ` Petteri Räty
2013-06-18 12:12       ` Roy Bamford [this message]
2013-06-18 12:53         ` Rich Freeman
2013-06-18 12:55 ` hasufell
2013-06-18 13:15   ` Ciaran McCreesh
2013-06-18 13:47     ` Anthony G. Basile
2013-06-18 13:59       ` hasufell
2013-06-18 14:11         ` Petteri Räty
2013-06-18 13:59       ` Rich Freeman

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=1371557523.2541.0@bluebottle \
    --to=neddyseagoon@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