From: Donnie Berkholz <dberkholz@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: Tue, 1 Jul 2008 00:28:07 -0700 [thread overview]
Message-ID: <20080701072807.GB430@comet> (raw)
In-Reply-To: <1212690820.2631.1@spike>
On 19:33 Thu 05 Jun , Roy Bamford wrote:
> 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.
I just got to this because I was on vacation and I've been busy getting
work done since I got back.
> 1. Please tell us how/if you plan to fix GLEP 39. (You may not consider
> it broken)
I think Rich Freeman made a good point -- having attendance requirements
without requirements about method of notification is a problem.
> 2. As one of the first priorities will be setting policy for pending
> appeals what policy do you propose ?
The one I already did propose and the council approved.
> 3. If you are not on the council already, how will you make time for
> the extra work?
N/A -- although I will say that creating the agenda (with the included
research) and chairing meetings is significantly more work than being
any other council member at this point in time.
> 4. How do you think the council and trustees can work together to make
> Gentoo better? Not just the code base but the cooperative environment
> we all work together in too. Disclosure - I have a personal interest
> in responses as a trustee.
>
> 5. Tell us a little about yourself - the skills and experience you can
> bring to the council?
- I stay calm under fire.
- I've got extensive training in problem solving and logical thought,
from programming to journalism to my in-progress biochemistry Ph.D.
- "Strong opinions, weakly held." - A borrowed description I really like
- I write clearly and concisely.
- I recently had my 5-year anniversary as a Gentoo developer, and I'm
among the most active devs.
> 6. Tell us one outstanding (in your own mind) contribution you made to
> Gentoo in the last year.
If your X is still running, you already know. =)
Thanks,
Donnie
--
gentoo-project@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-07-01 7:28 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
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 [this message]
[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=20080701072807.GB430@comet \
--to=dberkholz@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