Gentoo Archives: gentoo-dev

From: Thilo Bangert <bangert@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: Training points for users interested in helping out with ebuild development
Date: Sun, 10 May 2009 08:46:48
Message-Id: 200905101045.34083.bangert@gentoo.org
In Reply to: Re: [gentoo-dev] Re: Training points for users interested in helping out with ebuild development by Ciaran McCreesh
1 Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> said:
2 > On Tue, 5 May 2009 21:19:49 +0300
3 >
4 > Markos Chandras <hwoarang@g.o> wrote:
5 > > We surely need more developers. Otherwise we ll end up maintaining
6 > > 100<x<500 each one. Just look at the numbers ( total packages/total
7 > > ACTIVE developers ). So first we need to attract more people.
8 > > Evaluation and recruitment comes next
9 >
10 > I have a better way of improving those numbers: remove two thirds of
11 > the packages from the main tree.
12
13 to me, the above two contradictory viewpoints are the essence of the
14 apparent and real decline in Gentoo activity. The two are just not
15 compatible with each other and there is no clear guidance on to which of
16 the two should be followed.
17
18 in the one corner we have the 'Daniel Robbins' corner, which stands for an
19 open and inclusive process, which favors new comers, wants fast progress
20 regardsless of the technical limitations of that process. also, being nice
21 is more important than being correct. one central repository is where all
22 development should happen - this is were we came from.
23
24 in the other corner is the gentoo leftover of the exherbo fork: the few
25 people how continue to work on Gentoo but generally prefer the direction
26 of Exherbo. technical elitism, explicitism and formal standardization are
27 their trade. being correct is more important than good intentions.
28 overlays or multiple repositories help achieve a hierarchy of not-good-to-
29 supported ebuilds. we are halfway here...
30
31
32 it would be good if we collectively could agree on some of these issues,
33 in order to move forward. as with many of the other technical discussions
34 which lead to nowhere, it's more important that there is a clear
35 direction, than into which direction we are headed.
36
37 maybe we need a debian project leader position - or a council, which is
38 sensitive to the internal devide among developers and gives clear
39 directions.
40
41 if the above offends you, please take a walk before replying. it may sound
42 inflammtory - its not meant to be.
43
44 thanks
45 Thilo

Replies