Gentoo Archives: gentoo-dev

From: Donnie Berkholz <dberkholz@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-tv/mythtv: ChangeLog mythtv-0.20.2_p14668.ebuild mythtv-0.21_pre14666.ebuild mythtv-0.21_pre14480-r1.ebuild
Date: Mon, 15 Oct 2007 22:25:23
Message-Id: 20071015220943.GK23990@supernova
In Reply to: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-tv/mythtv: ChangeLog mythtv-0.20.2_p14668.ebuild mythtv-0.21_pre14666.ebuild mythtv-0.21_pre14480-r1.ebuild by Doug Goldstein
1 On 16:57 Mon 15 Oct , Doug Goldstein wrote:
2 > I still stand by my original feeling that we'd better the community NOT
3 > only the developers doing the commits by updating the devmanual, which
4 > is accessible to all developers and all users in the Gentoo community.
5 > In addition to updating and cleaning up repoman checks, which is a tool
6 > that everyone in the community can use. This is versus individual
7 > examples in random ebuilds in random e-mails that all have almost an
8 > identical subject on the mailing list.
9 >
10 > The commits review is flawed because if we're not documenting this stuff
11 > in one central place, then when new developers join. The same lessons
12 > have to be learned over and over again.
13
14 Doing the review helps us figure out what the common issues are, so we
15 actually know what's worth documenting. I've had in mind all along
16 getting common issues into docs and into repoman, which is why I wrote
17 the original quoting patch.
18
19 Also, just because something is documented doesn't mean people do it.
20 Furthermore, just because a doc says "write code without bugs" doesn't
21 mean people are physically capable of doing so. More eyes on the code
22 can never hurt.
23
24 Thanks,
25 Donnie
26 --
27 gentoo-dev@g.o mailing list