From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [GLEP 39 overhaul] Does the council need a lead?
Date: Thu, 22 Apr 2010 00:10:24 +0000 [thread overview]
Message-ID: <4BCF93F0.6080700@gentoo.org> (raw)
In-Reply-To: <u2l7c612fc61004171649n7670d040jcdd1f5663703169@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17-04-2010 23:49, Denis Dupeyron wrote:
> Does the council need a lead? All top-level projects have a lead
> except the council. Should we maintain this exception?
What do we mean by a council lead? If we're talking about someone to
oversee their meetings, then I see no problem with it. If we're talking
about a Gentoo Lead, then I'm against that as I don't want to ever see
the council reduced to a single person body - there are some advantages
to collective bodies. One of them is the requirement for people to talk
and to be able to generate a consensus.
> How do we elect a lead? Do the developers do it or should it be left
> to the newly elected council members?
As stated above, I think we should have a collective body. Therefore to
choose someone to oversee meetings should be a council decision -
including the choice to not have someone overseeing the meetings.
- --
Regards,
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / KDE / Elections
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJLz5PwAAoJEC8ZTXQF1qEPrzoQANTPg3ikbVUgImkEdWgI+VLO
g+3wyDkozv+BpEV20NJPwZFxbuq+795eG74mV6nQudxGw29w7CZP0co/MfeQCBFy
5W74DyF06fuN+E2OPrFEAYYc5N5UJt0FE9G1mXV6aMczxX8qQgTOZnU8OFdX0w/f
MVDvRDzLv6zAyt46/Fw25y2ft4DVNLh0gAHT0NFfTno9iAFUmTnUmOBLweayalRO
fNlBRTON90K3BqqN6Rk2hMTPslaYzkgPN1ifSC9Na3v0BtrwAlv548eoNkv7PO++
ZtAt7y78taJERvrTs8sZwaXEafIkrnBEGfFOBndxszJZbYiRuHPdDIejQ7WV8K6g
shw2mXhdV8VCkgRgF+9CuBP5BdiEleFGRxLPV3xnty0q5hZee0WyOX76oG72mWsF
xGgz5C7uhLMB4G4eHDaeuHDHTSBzcjbuVsYLLYTpnM4j2UmmF5WCpvqyWk/oTpTS
1UfKoHcQX3dcFhrKSxcwK4+FlNwbn+9zJ9QRTBiw/lDHVIpbINwr7ybUKLsrP1vZ
LDVaFw1KLmv0PNBT9G9Y86fLaTFoOSKY3awPc5i40FNkdxqNDI5i74jrQc8pw25M
LeT/44oYeJ4BoD+I964yZzW/sJWaoUSB1DtctX/uLWh+ltSdzxPcL5UclnbenUa7
+8U4gW2hqSOJxfckZT+Y
=DLb0
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-04-22 1:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 23:49 [gentoo-project] [GLEP 39 overhaul] Does the council need a lead? Denis Dupeyron
2010-04-18 9:06 ` Markos Chandras
2010-04-18 9:23 ` Nirbheek Chauhan
2010-04-18 10:54 ` Markos Chandras
2010-04-18 21:26 ` Richard Freeman
2010-04-18 23:09 ` Denis Dupeyron
2010-04-19 1:36 ` Richard Freeman
2010-04-18 12:06 ` Petteri Räty
2010-04-18 12:45 ` Nirbheek Chauhan
2010-04-18 12:48 ` Petteri Räty
2010-04-18 13:07 ` Nirbheek Chauhan
2010-04-20 17:59 ` Roy Bamford
2010-04-20 19:18 ` Thomas Anderson
2010-04-22 0:10 ` Jorge Manuel B. S. Vicetto [this message]
2010-05-14 22:45 ` [gentoo-project] " Denis Dupeyron
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=4BCF93F0.6080700@gentoo.org \
--to=jmbsvicetto@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