From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [GLEP 39 overhaul] Does the council need a lead?
Date: Sun, 18 Apr 2010 12:06:57 +0300 [thread overview]
Message-ID: <201004181206.57856.hwoarang@gentoo.org> (raw)
In-Reply-To: <u2l7c612fc61004171649n7670d040jcdd1f5663703169@mail.gmail.com>
On Sunday 18 April 2010 02:49:26 Denis Dupeyron wrote:
> Does the council need a lead? All top-level projects have a lead
> except the council. Should we maintain this exception?
>
> How do we elect a lead? Do the developers do it or should it be left
> to the newly elected council members?
Well, my opinion is well-known but I will post it here as well.
Definitely YES. Each project requires a lead who coordinates, defines a clear
path to follow and inspire the rest of the members.
Council should have one too
--
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
next prev parent reply other threads:[~2010-04-18 9:07 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 [this message]
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
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=201004181206.57856.hwoarang@gentoo.org \
--to=hwoarang@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