Gentoo Archives: gentoo-dev

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: Gentoo World Domination. a 10 step guide
Date: Thu, 05 Oct 2006 04:13:20
Message-Id: eg20ig$n0p$3@sea.gmane.org
1 "Thomas Cort" <linuxgeek@×××××.com> posted
2 3b09e8e90610040844y400d744bpb3c4e4b41b56fdeb@××××××××××.com, excerpted
3 below, on Wed, 04 Oct 2006 11:44:07 -0400:
4
5 > My view is that currently we cannot offer the same level of support
6 > for the minority arches as the majority arches because we don't have
7 > enough people involved. I think that spreading the developers too thin
8 > leads to conflict and burnout. Look at NetBSD and debian. They are
9 > trying to be everything for everyone. How is that working for them,
10 > how is it working for us? I think we should be more focused, but
11 > that's just my opinion.
12
13 There are two separate problems with simply removing them, however.
14
15 One, it has already been mentioned that the minority archs don't tend to
16 be the bottleneck, so removing them isn't likely to help. In addition,
17 the minority archs don't bother anyone not on them, except for maintainers
18 looking to dump old versions, and that could arguably be better and more
19 directly addressed with a policy of time-limitting the holdup effect -- if
20 there has been no updates on a keyword bug in (say) 90 days, dropping the
21 last arch or ~arch keyworded version is allowed.
22
23 As it's related, it should be pointed out that simply forcing every dev
24 onto at least one arch team isn't going to help much either -- as long as
25 Gentoo is staffed by volunteers, you aren't going to be able to force them
26 to do anything substancial on a team they aren't voluntarily on anyway,
27 and all the inactive arch-team devs will only hide the problem.
28 Additionally, that was the de facto situation with x86 previously, and it
29 simply didn't work.
30
31 Two and potentially far worse, you have the demotivation problem. Picking
32 on a rather active dev as a prime example, Flameeyes' Gentoo/alt-freebsd
33 is certainly a minority arch, one that he spends a decent amount of time
34 on that could arguably be spent on more mainline projects. Yet he remains
35 very active in other areas as well, and simply telling him to packup his
36 Gentoo/fbsd project as it's not wanted would be incredibly demotivating,
37 and could eventually cause us to lose him and all the stuff he does for
38 the /rest/ of the tree (a quite a lot, from where I sit as a user, and
39 I'm very likely missing the largest share of it). That's not even
40 counting how his work on Gentoo/FBSD has improved the quality of the tree
41 for everyone, including those like me who have no direct interest in FBSD
42 at all. Flameeyes isn't the only one. If you shut down all the minority
43 archs and projects, you demotivate some of our best and brightest, and
44 will very likely eventually lose them.
45
46 --
47 Duncan - List replies preferred. No HTML msgs.
48 "Every nonfree program has a lord, a master --
49 and if you use the program, he is your master." Richard Stallman
50
51 --
52 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] Re: Gentoo World Domination. a 10 step guide Chris Gianelloni <wolf31o2@g.o>