public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] Re: [gentoo-dev] Nominations open for the Gentoo Council 2008/2009
Date: Thu, 05 Jun 2008 23:10:15 +0200	[thread overview]
Message-ID: <48485637.4020006@gentoo.org> (raw)
In-Reply-To: <1212690820.2631.1@spike>

Roy Bamford wrote:
> On 2008.06.05 01:00, Aukasz Damentko wrote:
>> Hi guys,
> 
>> Nominations for the Gentoo Council 2008/2009 are open now and will be
>> open for the next two weeks (until 23:59 UTC, 18/06/2008).
> 
> Team,
> 
> I don't want to nominate anyone who hasn't been nominated already.
> I would like to address all the candidates who have or will accept 
> council nominations.
> 
> 1. Please tell us how/if you plan to fix GLEP 39. (You may not consider 
> it broken)

Alone you cannot do anything. Still I found that there are some parts 
unspecified like how many meetings and how a meeting has to be announced 
to be considered official that should be clarified.

> 2. As one of the first priorities will be setting policy for pending 
> appeals what policy do you propose ?

No changes are required in my opinion.

> 4. How do you think the council and trustees can work together to make 
> Gentoo better?

Trustees manage a local entity located in the USA, the council should 
manage Gentoo as whole. Can they work together to improve Gentoo? Well 
EVERY developer and to a minor degree every member of the Gentoo 
community should work together to improve Gentoo, usually do what's 
within their role. The foundation has to make sure our intellectual 
property won't get abused in the USA, has to defend our trademark and 
cope with the bureaucracy related. The Council has to forster activities 
within Gentoo, to solve deadlocks in discussions by having the last say.

My old manifesto is still valid =)

lu

-- 

Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero

-- 
gentoo-project@lists.gentoo.org mailing list



  reply	other threads:[~2008-06-05 21:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05  0:00 [gentoo-project] Nominations open for the Gentoo Council 2008/2009 Łukasz Damentko
2008-06-05 18:33 ` [gentoo-project] Re: [gentoo-dev] " Roy Bamford
2008-06-05 21:10   ` Luca Barbato [this message]
2008-06-06  1:37   ` Ferris McCormick
2008-06-06 13:32     ` Ferris McCormick
2008-06-06 19:12       ` Donnie Berkholz
2008-06-07  7:45   ` Tiziano Müller
2008-06-09 18:18   ` Tiziano Müller
2008-06-21 10:03   ` Marijn Schouten (hkBst)
2008-07-01  7:28   ` Donnie Berkholz
     [not found] ` <4847B354.6090800@gentoo.org>
     [not found]   ` <df1735a20806051748v6fd7ac47xcd026831ec1b35ad@mail.gmail.com>
2008-06-06  1:22     ` Richard Freeman
2008-06-06  6:00       ` Donnie Berkholz
2008-06-06  8:43         ` Graham Murray
2008-06-07  7:47           ` [gentoo-project] " Tiziano Müller
2008-06-08 14:28       ` [gentoo-project] " George
2008-06-06  8:20 ` [gentoo-project] Cross posting to multiple mailing lists Petteri Räty

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=48485637.4020006@gentoo.org \
    --to=lu_zero@gentoo.org \
    --cc=gentoo-dev@lists.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