From: Richard Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Requiring two sets of eyes for all eclass commits
Date: Sun, 25 Apr 2010 08:04:15 -0400 [thread overview]
Message-ID: <4BD42FBF.7010901@gentoo.org> (raw)
In-Reply-To: <20100425053625.6a72ee87@gentoo.org>
On 04/25/2010 07:36 AM, Ryan Hill wrote:
> People make mistakes.
Agreed - at work I've often found a quality mindset that is 100% focused
on preventing mistakes, and I've found that these kinds of systems are
almost equally as focused on preventing them from being fixed (three
minutes to fix a bug, three weeks to document and release the fix - then
we wonder why the system has hundreds of trivial open bugs with no ROI
for fixing them).
A good quality system isn't just about preventing mistakes - it needs to
be about fixing them too. The system that prevents typos from getting
into the tree shouldn't get in the way of those typos being fixed.
There needs to be a balance.
Scripts running on repository servers don't have a sense of balance, so
they aren't the answer. Nor is cutting off hands any time a dev messes
up unless it becomes a pattern or there is malicious intent.
However, a systematic review process is probably a good thing most of
the time, and published policies supporting this are a good thing.
Rich
next prev parent reply other threads:[~2010-04-25 12:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 17:40 [gentoo-dev] Requiring two sets of eyes for all eclass commits Petteri Räty
2010-04-24 18:10 ` Arun Raghavan
2010-04-24 18:14 ` Alexis Ballier
2010-04-25 10:14 ` Petteri Räty
2010-04-25 22:42 ` Alistair Bush
2010-04-25 13:10 ` Petteri Räty
2010-04-25 15:22 ` Jorge Manuel B. S. Vicetto
2010-04-26 17:58 ` Steev Klimaszewski
2010-04-25 10:06 ` [gentoo-dev] " Ryan Hill
2010-04-25 10:11 ` Petteri Räty
2010-04-25 11:36 ` Ryan Hill
2010-04-25 12:01 ` Alec Warner
2010-04-25 21:06 ` Ryan Hill
2010-04-25 12:04 ` Richard Freeman [this message]
2010-04-26 16:19 ` Paul Varner
2010-04-25 10:54 ` [gentoo-dev] " Roy Bamford
2010-04-27 19:11 ` Rémi Cardona
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=4BD42FBF.7010901@gentoo.org \
--to=rich0@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