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-project
Navigation:
Lists: gentoo-project: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-project@g.o
From: Fabian Groffen <grobian@g.o>
Subject: Re: Preparations Council meeting 2011-08-09
Date: Mon, 1 Aug 2011 21:32:37 +0200
On 01-08-2011 20:16:34 +0100, Markos Chandras wrote:
> > Would you mind summarising/drafting up the policy for who can and who
> > can't get a cloak?  This is probably going to be the GLEP that Petteri
> > refers to.  Does it make sense to vote for this topic without that GLEP
> > in place?
> > 
> Anyone can (should) get a cloak upon developer's request. Petteri
> suggested to have the council vote and transfer the responsibility to
> devrel, which in accordance will include this in a new GLEP defining the
> devrel policy just like then one for QA.

Ok, thanks.
Am I correct by summarising this point as simply a vote for transferring
the cloak responsibility to devrel?


-- 
Fabian Groffen
Gentoo on a different level


Replies:
Re: Preparations Council meeting 2011-08-09
-- Markos Chandras
References:
Preparations Council meeting 2011-08-09
-- Fabian Groffen
Re: Preparations Council meeting 2011-08-09
-- Markos Chandras
Re: Preparations Council meeting 2011-08-09
-- Fabian Groffen
Re: Preparations Council meeting 2011-08-09
-- Markos Chandras
Navigation:
Lists: gentoo-project: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Preparations Council meeting 2011-08-09
Next by thread:
Re: Preparations Council meeting 2011-08-09
Previous by date:
Re: Preparations Council meeting 2011-08-09
Next by date:
Re: [gentoo-dev] ChangeLog generation - pros and cons (council discussion request)


Updated Jun 17, 2012

Summary: Archive of the gentoo-project mailing list.

Donate to support our development efforts.

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