From: "Tony \"Chainsaw\" Vroon" <chainsaw@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Manifesto for council election
Date: Sat, 19 Jun 2010 22:06:59 +0100 [thread overview]
Message-ID: <1276981619.425.35.camel@localhost> (raw)
In-Reply-To: <1276977363.2635.0@NeddySeagoon>
[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]
As you've seen, Chainsaw is on the list as a council candidate.
I use Gentoo in a professional capacity, as a UNIX systems administrator
for one of the largest internet exchanges in the world [1]. Right now, I
administer 42 machines running non-multilib hardened AMD64.
The topic of "Gentoo in the enterprise" surfaces from time to time on
the mailing lists, but the current direction that Gentoo is taking seems
to steer away from it.
Should you elect me to the council, I will do my best to discourage the
frequent usage of overlays. Not only can overlay ebuilds slip through
the QA net that is frequently trawled through the main tree (and they
often do), the ownership is not always clear. There is no central
location to report bugs in overlay ebuilds.
Last but not least, moving ebuilds out into overlays means that larger
deployments like mine are unable to use them.
One other problem that has appeared on my radar more then once lately.
When developers lose motivation and stop committing to a package for
which they are the sole maintainer it can take a considerable amount of
time before this is dealt with in the form of a retirement bug or "last
rites" e-mail.
With a business dependency on some packages, that can be too long. I
believe we should actively seek out such packages and see if another
developer can be motivated to take the package over.
Failing that, I believe no ebuild is a fairer situation then an
outdated/stagnant ebuild with open bugs that are not looked at. Some
automated QA processes like the tinderbox already help with this but
without official recognition of these bugs as QA matters the full
potential of it goes untapped.
In writing this, I realise that some or all of what I have just written
may be controversial to you. Can I ask that you speak with your vote and
not in this mailing list.
Regards,
Tony "Chainsaw" Vroon
1: https://www.linx.net/about/index.html
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-19 21:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 19:56 [gentoo-dev] Gentoo Council 2010/2011 - Voting Roy Bamford
2010-06-19 21:06 ` Tony "Chainsaw" Vroon [this message]
2010-06-20 11:19 ` [gentoo-dev] My Council manifest Petteri Räty
2010-06-20 13:47 ` [gentoo-dev] Re: Gentoo Council 2010/2011 - Voting Roy Bamford
2010-06-21 16:33 ` [gentoo-dev] Council manifesto of sping Sebastian Pipping
2010-06-21 18:20 ` Petteri Räty
2010-06-21 21:07 ` Sebastian Pipping
2010-06-21 19:25 ` Arun Raghavan
2010-06-21 21:36 ` Sebastian Pipping
2010-06-22 1:46 ` Brian Harring
2010-06-22 2:37 ` Sebastian Pipping
2010-06-22 5:13 ` Arun Raghavan
2010-06-22 10:02 ` [gentoo-dev] " Duncan
2010-06-22 10:24 ` Arun Raghavan
2010-06-30 0:45 ` [gentoo-dev] " Sebastian Pipping
2010-07-02 14:23 ` Arun Raghavan
2010-07-02 15:50 ` Sebastian Pipping
2010-07-02 17:30 ` Nirbheek Chauhan
2010-06-22 5:15 ` Arun Raghavan
2010-06-22 2:37 ` Alec Warner
2010-06-21 19:10 ` [gentoo-dev] My council manifesto Mark Loeser
2010-06-21 19:15 ` Arun Raghavan
2010-06-21 19:27 ` Mark Loeser
2010-06-21 19:30 ` Arun Raghavan
2010-06-21 21:19 ` [gentoo-dev] Gentoo Council 2010/2011 - Voting Mike Frysinger
2010-07-02 22:32 ` [gentoo-dev] Re: Gentoo Council 2010/2011 - Voting - Reminder Roy Bamford
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=1276981619.425.35.camel@localhost \
--to=chainsaw@gentoo.org \
--cc=gentoo-dev@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