Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev-announce
Navigation:
Lists: gentoo-dev-announce: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev-announce@g.o
From: Denis Dupeyron <calchan@g.o>
Subject: Resolve unfinished GLEP 39 business
Date: Thu, 10 Sep 2009 23:38:16 +0000
I would like to add an item for the next council meeting. Since GLEP
39 was modified in the past, and since discussion material for
modifications will be coming sooner rather than later, we need to have
an official way to amend it.

During our first meeting we voted that the council was not competent
to decide on a way to amend GLEP 39. There was previously no formal
process to do this and now the situation is locked up at the council
level since we can't decide. Some council members have said or assumed
that the natural fallback to that was that any amendment would need to
be voted by the developer community. There are two big and distinct
problems with that.

As soon as the council declares itself incompetent to decide on a way
to amend GLEP 39, it can't anymore choose or assume a process. Because
this is exactly deciding of a way to go forward which we voted we
couldn't do. How logical is it to tell the community "We can't tell
you how but here is how we will do it!" ?

Also, an all-developer vote may not be the right solution. Some devs
do want to vote on GLEP 39 amendments. Some say they have voted for a
council and delegated their voice to them and want them to do the job.
Some don't really have an opinion. Many haven't even read GLEP 39 and
couldn't care less. From the results of my informal poll, I'm truly
amazed (and worried) by the number of devs who will not want to
participate to a vote on GLEP 39 amendments. Not counting those who
say they will but won't. I'm hoping I'm wrong but in case I'm not I'm
afraid votes on amendments will be like jumping off a cliff, i.e. an
exciting trip to nowhere.

Let's face it: the only way to know what developers want is to ask
them. Formally. And let's not pretend there are no changes coming for
GLEP 39. I have some in the pipeline and I know others have too. If we
don't have a framework for this we're preventing ourselves to do
adjustments on our structure and condemning it to only evolving in big
chaotic steps. It's like not being able to write a patch and having to
wait for release 2.0 which may never come. So, for the next meeting I
would like the council to discuss and initiate an all-developer vote
on a process to amend GLEP 39.

Denis.



Navigation:
Lists: gentoo-dev-announce: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Last rites for dev-python/ssl-py26
Next by thread:
Lastrite: x70talk, bluez-bluefw, =tellico-1*
Previous by date:
Last rites for dev-python/ssl-py26
Next by date:
Lastrite: x70talk, bluez-bluefw, =tellico-1*


Updated Jul 14, 2012

Summary: Archive of the gentoo-dev-announce mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.