From: "Marijn Schouten (hkBst)" <hkBst@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev] Nominations open for the Gentoo Council 2008/2009
Date: Sat, 21 Jun 2008 12:03:24 +0200 [thread overview]
Message-ID: <485CD1EC.2070102@gentoo.org> (raw)
In-Reply-To: <1212690820.2631.1@spike>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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.
Gentoo and me
=============
I have been a developer since January 2007. I became involved to learn
and to help make sure that all things Lisp are easily available on
Gentoo. I have been Lisp Project lead since January 2008. Besides Lisp I
maintain some software that I feel should be available even though I do
not use it (much yet), such as SML implementations and lilypond. Guile
is one of the Scheme implementations I maintain.
Roy Bamford's questions
=======================
1. Please tell us how/if you plan to fix GLEP 39. (You may not consider
it broken)
I don't think it is broken.
2. As one of the first priorities will be setting policy for pending
appeals what policy do you propose ?
I do not like the way developers were expelled recently. For me at least
it came out of the blue and seemingly without any prior warning or
corrective action. I would like the whole process to be more careful.
Devrel should give one or maybe even two formal public warnings before
asking the council to expel a developer. The council should hold a
public hearing after examining the evidence and decide. I'd like all
recent 3 expulsions to be turned into first formal warnings. Any future
council could decide to reinstate an expelled developer. I don't think a
separate appeals process is necessary to handle this.
3. If you are not on the council already, how will you make time for
the extra work?
I will slack less.
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.
I think it is the council's role to be the glue that binds us all
together. The council should also take responsibility for projects that
affect or represent all of Gentoo, such as PMS and releng. The council
should make sure that things are moving forward and that developers (and
users too) are not left wondering what is going on.
5. Tell us a little about yourself - the skills and experience you can
bring to the council?
I have the brains to quickly comprehend problems and to evaluate and
create solutions. I am not afraid to make mistakes or to admit that I am
wrong. I do not mind interacting with people that some find difficult.
With this skill I will try to bridge any fissures that divide us.
6. Tell us one outstanding (in your own mind) contribution you made to
Gentoo in the last year.
I have helped to build a small community of Gentoo Lispers by
encouraging and helping users in their studies and enabling them to
easily contribute through our git overlay and with their help I have
significantly increased the number of available recent versions of
Scheme implementations and related software. I have recently recruited
one of those users to become a developer.
- --
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkhc0esACgkQp/VmCx0OL2yk/ACggILwAT9KjoQCkgGxR+hR5fBe
W40AnjxzlnLf7HBiG5/1R6SdZwhpQ6/J
=nso7
-----END PGP SIGNATURE-----
--
gentoo-project@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-06-21 10:10 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) [this message]
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=485CD1EC.2070102@gentoo.org \
--to=hkbst@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