Gentoo Archives: gentoo-project

From: Daniel Robbins <drobbins@××××××.org>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] Resignation
Date: Mon, 18 Dec 2017 17:04:32
Message-Id: CAPDOV48Eaw1y7sk9=ozmdQYCaAc-AS09mxztfR03ysWfSo5iMg@mail.gmail.com
In Reply to: [gentoo-project] Resignation by Daniel Campbell
1 Hi Daniel,
2
3 Thanks very much for your contributions to Gentoo, and for this detailed
4 write-up of why you left. It is very informative and enlightening about
5 what the current challenges with Gentoo are. I am sure mgorny is not the
6 only senior developer who could benefit from some mentorship/professional
7 development to improve leadership needed skills related to support and
8 encouragement of more junior members. These skills often aren't a part of a
9 geek's innate repertoire but they are absolutely necessary for a successful
10 open source project.
11
12 -Daniel
13
14 On Sat, Dec 16, 2017 at 1:34 AM, Daniel Campbell <zlg@g.o> wrote:
15
16 > Effective today, December 16th, 2017 at 0800 UTC, I am resigning from my
17 > position as Gentoo Developer and Foundation Trustee. I joined Gentoo to
18 > gain experience and give back to the libre software community. In some
19 > ways, maybe I succeeded a little. I learned from this experience that
20 > I don't need to be a member of a distribution to contribute or advance
21 > my skills, and people will often act against their stated goals if it
22 > improves their appearance. It taught me how *not* to organize a libre
23 > software project. The few great experiences I had here at Gentoo sadly
24 > do not outweigh the negative experiences, and I'm no longer interested
25 > in beating my head against that brick wall.
26 >
27 > Here's a list of the "nothing" I've done in my Gentoo involvement:
28 >
29 > As proxy maintainer, I took on these packages to sort of "prove my
30 > worth":
31 >
32 > net-p2p/i2p
33 > net-p2p/imule
34 > x11-wm/fluxbox
35 >
36 > I knew nothing about Java -- and it probably showed -- but I was willing
37 > to learn what was necessary to get the ebuilds in better shape. This
38 > never changed throughout the 2.5 years I was a developer.
39 >
40 > pchrist, heroxbd, jlec, and zlogene mentored me and got me up to speed.
41 > I am grateful for their level of care and attention, and the effort they
42 > put in alongside me. My recruitment process was protracted due to real
43 > life, but we eventually pulled through.
44 >
45 > After I became a developer, maffblaster welcomed me to the wiki, and
46 > we even had a conversation over Mumble later on. I later took on more
47 > packages, enthusiastic to give back to a distro that I liked:
48 >
49 > app-cdr/bashburn
50 > dev-util/astyle
51 > media-sound/apulse
52 > media-video/smtube
53 > net-misc/toxic
54 > sys-apps/udevil
55 > www-servers/lighttpd
56 > x11-misc/alock
57 > x11-misc/ktsuss
58 > x11-misc/spacefm
59 >
60 > I dipped my hands into any bug I thought I could reasonably solve,
61 > and sought advice when I didn't know the correct way to do something.
62 > Sometimes this worked; sometimes I'd realize I didn't have the skill
63 > necessary, and left it to the more experienced people.
64 >
65 > Sometimes, mgorny would show up and tell me that my solution sucked or
66 > was "braindead", or that such-and-such solution was "common sense",
67 > with no explanation as to *why* it was "common sense". (this was on
68 > IRC, though [1] outlines where jcallen had to clarify what I hope
69 > mgorny intended to communicate) He didn't ever tell me what the correct
70 > solution was to any given problem that I might've messed up. To this
71 > end, his criticism served to do nothing but demotivate me. At a later
72 > point, when monsieurp and I were dealing with file collisions, he
73 > threatened to have us go through the developer quizzes again. [2] None
74 > of his criticism was helpful or encouraging. The key to good criticism
75 > is to be *constructive*, acknowledging the mistakes *AND* the successes.
76 > Without both, one's communication is morally destructive.
77 >
78 > [1]: https://bugs.gentoo.org/547524
79 > [2]: https://bugs.gentoo.org/603526#c6
80 >
81 > (careful, the comments might be deleted in response to this e-mail to
82 > save face)
83 >
84 > Later, I was nominated as Trustee by klondike. At first, I didn't think
85 > I could do the job. Maybe I should've listened to that feeling. But I
86 > felt it would be rude if I didn't accept a nomination. Nothing ventured,
87 > nothing gained, right? I didn't expect to be voted for. I had a feeling
88 > I would be laughed at and would walk away having spent the time on a
89 > manifesto for nothing. Reality is often stranger than fiction, and I
90 > found myself in a Trustee role. Given that he was only one rank below me
91 > in the election, I feel that klondike may have been a better fit for the
92 > role. I regret accepting the nomination.
93 >
94 > robbat2 mentored me on Treasurer duties, when he had the spare time. I
95 > felt bad that he was spread so thin between his other Gentoo duties,
96 > mentoring me, and being a parent. Nevertheless, I pushed forward, trying
97 > to fill the role as best I knew how to. Most of the time, I was afraid
98 > to touch anything because I understood that money was involved. I didn't
99 > want to make a mistake and cost us money. Because of that, I only ever
100 > logged into one account (Paypal), and only to gather the metadata we
101 > needed to update some records.
102 >
103 > mgorny again showed up; this time accusing me of being a "do-nothing
104 > politician". Thankfully, I kept an activity log of everything I did for
105 > the Foundation, and `git log --committer=zlg@g.o` will show you
106 > everything I did in the tree. Yes, I made mistakes. Some of them rookie
107 > ones. But given that I wasn't being paid for my work, and time spent
108 > on Gentoo meant time I couldn't spend on other things (like personal
109 > projects), I needed to make a value decision: was I willing to continue
110 > donating labor to an organization that didn't notice my work unless
111 > I screwed up? If I was truly as ineffectual as those who claimed it
112 > (rich0), what was the point of continuing? The cricitism I received
113 > during my time as a developer was demotivating and didn't acknowledge
114 > any of the *correct* things I did; how exactly was I going to improve?
115 >
116 > These questions led me to my answer: leave the organization. There is no
117 > point in continuing to try when I will only be berated for screwing up.
118 > My failures will be paraded to all while my victories go un-noticed and
119 > unappreciated. This is a losing proposition, leading nowhere. As such, I
120 > am terminating my involvement with Gentoo Linux and its Foundation.
121 >
122 > I'd like to thank everyone who helped me become a developer and trustee,
123 > and the two positive code reviews I received during my time as a
124 > developer, by Soap and floppym. They helped me understand not only
125 > *where* I messed up, but what the solution should've looked like and
126 > *why* their solutions were better. I don't think either of them really
127 > like me, but credit given where it's due.
128 >
129 > A developer will not progress or become more skilled unless they
130 > understand those key things (why, how, where). Drive-by insults and
131 > egotism will drive people away. Gentoo won't improve in this regard
132 > unless it cares enough to value what people contribute and acknowledge
133 > when people give constructive reviews. It takes effort from both "sides"
134 > of a mentorship in order to get any appreciable progress.
135 >
136 > When I reached out to members of the Gentoo community, I learned that
137 > there were a considerable number of users (of all skill levels) who,
138 > for whatever reason, did not want to go through the process of becoming
139 > a developer. This told me that there was an imbalance in the value
140 > proposition; that is, the effort spent to become a developer *appears*
141 > to be more work than what you get by making it through the process. I
142 > think this is the core of Gentoo's struggles. Gentoo will continue to
143 > suffer from manpower problems [3] until it figures out how to improve
144 > that value proposition. If higher quality recruits are desired, then
145 > a structured curriculum -- with smaller, focused tests along the way
146 > -- may be the best way to bring a recruit from "wet behind the ears"
147 > to "ready to commit on the toolchain". This process is important to
148 > Gentoo's longevity, and unless its leadership takes this social problem
149 > seriously, they will find themselves with more work and fewer people.
150 >
151 > [3]: Before any glib old-timer pipes up, recall that the Council (your
152 > leadership) just recently considered a mailing list split and discussed
153 > package maintenance (i.e. manpower) problems in the same meeting; I hope
154 > the irony is not lost on others.
155 >
156 > I expect to be laughed or jeered at by mgorny and other senior
157 > developers, but now it's Gentoo's problem, not mine. I've done what I
158 > thought I could do, and can walk away knowing that I tried. Nobody can
159 > reasonably ask for more than that.
160 >
161 > So long, and thanks for all the fish.
162 >
163 > (on the plus side, you can now type 'zl' and Tab in IRC to get zlogene
164 > instead of me :P)
165 >
166 > My Foundation activity follows.
167 >
168 > FOUNDATION ACTIVITY TRACKER
169 > FOR zlg@g.o
170 >
171 > 2017-10-08
172 > Worked with robbat2 to catch up the MoneyMarket account to match the
173 > missing
174 > statements from 2013-12 to 2015-12.
175 >
176 > 2017-10-22
177 > Edited the Foundation:Activity Tracker page with the new due date of
178 > the
179 > Treasurer's Annual Report with NM: 2018-11-15
180 >
181 > 2017-11-19
182 > robbat2 re-encrypted the banking passwords file, granting access to
183 > online
184 > accounts for me to begin converting Paypal transaction data and catch
185 > up on
186 > other financial activity.
187 >
188 > Paypal transaction information from 20170701-20171031 was imported and
189 > converted using `make all` in /paypal_raw/; commit pending
190 >
191 > Corrected Ruby call in paypal_raw/Makefile to ruby22
192 >
193 > Added a note in paypal_raw/README about requiring dev-ruby/tzinfo
194 >
195 > The meeting was postponed until Nov 26th, due to Meeting Chair's
196 > last-minute
197 > obligations and a shortage of trustees.
198 > * E-mail announcement was sent to -nfp@l.g.o
199 > * Wiki page for meeting updated
200 > * #gentoo-trustees /topic updated
201 >
202 > Convened with robbat2 on correcting the rubycsv code to include
203 > Subject: and
204 > Note: fields for matching accounts. He later fixed this on his own.
205 >
206 > 2017-11-26
207 > bug 605336; updated metadata for FOSDEM 2017 LiveDVD production
208 > reimbursement
209 >
210 > bug 591704; updated metadata for Perl Foundation donation in our loss
211 > of
212 > avenj
213 >
214 > wrote script to update foundation member OpenPGP key IDs to
215 > fingerprints,
216 > per ulm's request:
217 > https://archives.gentoo.org/gentoo-nfp/message/
218 > f06a3b742e06ddfcb541a822e0210e05
219 > sent to trustees@g.o for review
220 > used one-liner from robbat2 to fetch fingerprints from LDAP to x-ref
221 >
222 > bug 638036; created bug for shadowz.in request for logo/trademark
223 > licensing
224 > discussion pending
225 >
226 > 2017-11-27 to 2017-12-04
227 > worked on two more scripts to migrate and upgrade foundation list to
228 > include
229 > full fingerprints (and multiple keys)
230 > only script remaining is wikitable creator; a user indicated it
231 > would
232 > be trivial to write, using awk.
233 >
234 > EOF
235 > --
236 > Daniel Campbell
237 > OpenPGP Fingerprint: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6
238 > Found on hkp://keys.gnupg.net and other keyservers
239 >

Replies

Subject Author
Re: [gentoo-project] Resignation Raymond Jennings <shentino@×××××.com>