1 |
TL;DR: A screed about the infighting and politics that limits, IMO, the reach |
2 |
and acceptance of Gentoo in the Open Source community. |
3 |
|
4 |
I would like to suggest that, perhaps, Gentoo has a problem with the |
5 |
high barriers |
6 |
required to become a "developer" (and thus a "member") of the project. |
7 |
|
8 |
I understand the concerns that Gentoo wants to guarantee that the project |
9 |
provides high-quality software. However, quite a number of people I know have |
10 |
taken a look at the requirements documents and decided that the hoops are |
11 |
too messy and unnecessary for them to show that they are competent. Many of them |
12 |
are already familiar with the methods and tools, and it is insulting |
13 |
that they would |
14 |
have to go through an "apprenticeship" before they are allowed to even |
15 |
submit patches. |
16 |
|
17 |
I wonder if there are any of the current developers that would go |
18 |
through the whole |
19 |
process if it was required to renew their membership in the project. |
20 |
|
21 |
Andreas himself said: |
22 |
| And, yes I freely admit I stopped looking at github notifications some time |
23 |
| ago. Right now I have 193 unread notifications from gentoo/gentoo. |
24 |
|
25 |
Michal said in the opening post: |
26 |
| We have maybe a dozen developers who are actually looking through their |
27 |
| own pull requests. Everything else is usually reviewed by the few active |
28 |
| proxy-maint team members who are simply overwhelmed with work. What's |
29 |
| even worse, they are regularly attacked by other developers which |
30 |
| doesn't really encourage further work. |
31 |
|
32 |
These "attacks" (strong complaints and abusive language) do not improve |
33 |
the reputation of Gentoo out in the world. The other week I did a brief report |
34 |
on the Gentoo project and an update on the status of the repositories with |
35 |
regards to the latest software packages. The 'lightning talk' was appreciated |
36 |
but a few comments were made that several folks used and liked Gentoo, |
37 |
but were discouraged about the future of the project due to the politics. |
38 |
|
39 |
I discovered Gentoo about 2009, and have moved all my use of Linux |
40 |
to the Gentoo platform. I quit another project (think of a rouge chappeau) |
41 |
because I didn't agree with the direction they were taking, and have been |
42 |
filing bug reports and reading lots of mailing lists ever since. I tried |
43 |
hanging out on the IRC channels, but found it not worth the effort because |
44 |
of some hostility over giving answers that were not "proper procedure" |
45 |
and other piddling put-downs. |
46 |
|
47 |
I have actually been programming since 1958, after learning FORTRAN |
48 |
by keypunching programs for my Father on weekends and evenings. In |
49 |
High School (circa 1970) i elected to go for a B.S. in Computer Science |
50 |
with a strong elective set in genetics. Working at Duke in 1978, I was |
51 |
somewhat involved in the development and administration of a system |
52 |
that was in the same room and the CS machine that was used to develop |
53 |
NetNews/USENET. A null modem and serial cables allowed for testing |
54 |
much of the development without needing to use slow modem connections. |
55 |
The systems were, of course, running UNIX. In 1980, I tried my hand |
56 |
at being a 'consultant' in the NYC Metro area, mostly at Bell Labs and |
57 |
NY Telephone. When I had to take a short gig on Wall Street, I couldn't |
58 |
deal any longer with the commercial scene, and went back to Duke, and |
59 |
spent another 25 years working as a system admin, programmer, and |
60 |
on-campus consultant, jumping on the Linux bandwagon very early. |
61 |
With such a background, I find the "required" hoops of the Gentoo |
62 |
developer admission process very insulting, especially in light of the |
63 |
politics I have observed; and I have no patience or inclination to deal |
64 |
with it just to become a member of the "inner circle" and get a chance |
65 |
to obtain commit access and to vote for the inbred council. |
66 |
|
67 |
After 59 years of programming, admining (excuse me - DevOps), testing, |
68 |
on a wide variety of platforms, I can be cranky and fussy. The thing is: |
69 |
I do care about Gentoo. |
70 |
|
71 |
I can see the politics (which is the art of dealing with groups of people), |
72 |
and even occasionally contribute to it; and I can ignore it when necessary. |
73 |
I will continue to use Gentoo, and make bug reports, submit patches |
74 |
via bugzilla and just carry on until my body no longer can function. I would |
75 |
like to see Gentoo become more open and much less political. But I won't |
76 |
bet the farm on that happening. |
77 |
|
78 |
|
79 |
P.S: Just a thought: make every developer an automatic member of a |
80 |
QA project, with a goal of getting proposed patches reviewed within |
81 |
90 days of being submitted. A kit of patches will be one or few lines that |
82 |
make updates of minor corrections, and some may take a lot |
83 |
of effort to review. Any developer can review any patch, and then commit |
84 |
good minor ones,and make a recommendation on good major patches |
85 |
to the maintainer. Rejected patches get sent back to the submitter with |
86 |
a note about why it was rejected [such as 'unnecessary feature', |
87 |
'moot with new version', 'please revise in light of _____', etc.] Web tools |
88 |
to support this workflow should not be too hard to make. (I am actually |
89 |
surprised that there is not more automations to support development, but I |
90 |
suspect each developer would prefer to use the toolsets they are most |
91 |
comfortable with when working.) The possessiveness of (some/many/most) |
92 |
developers is one of the wort aspects of Open Source programming these |
93 |
days, and Gentoo is rife with it (but not as bad as some other well-known |
94 |
Linux projects.) |
95 |
|
96 |
Please think about this, and thanks for reading this far. |
97 |
|
98 |
-- |
99 |
G.Wolfe Woodbury, aka Redwolfe |
100 |
et cetera.... |