1 |
On 11/30/2016 08:10 AM, Dirkjan Ochtman wrote: |
2 |
> On Wed, Nov 30, 2016 at 2:43 PM, Daniel Campbell <zlg@g.o> wrote: |
3 |
>> I'm not going to mince words here: why did we kick out a contributor who |
4 |
>> was helping the Gentoo cause? I've looked over logs that were shared |
5 |
>> with me and the worst thing I could find was an off-color joke. Worse |
6 |
>> things occur on these mailing lists that never see Comrel's inbox, so |
7 |
>> why this? |
8 |
> |
9 |
> This does not sound like you have the full picture of the years over |
10 |
> which Ian attempted to contribute to Gentoo. I was involved for a long |
11 |
> time, basically from the start of Ian's tenure as a developer, and I |
12 |
> fully support his being kicked out. |
13 |
|
14 |
I fully concede I don't have the full picture, and a lot of the |
15 |
reasoning for that is it's kept so hush-hush. Naturally, my first |
16 |
reaction to secrecy is to find out why it's treated so specially when a |
17 |
lot of our affairs are left to public discourse. I'm open to new |
18 |
evidence and facts; any probing I've done into this subject has been met |
19 |
with hand-waving, which imo doesn't engender trust among us. So rather |
20 |
than beat around the bush, I chose to speak directly and candidly. |
21 |
|
22 |
>> What I'm looking for is undeniable proof that Ian was irrevocably |
23 |
>> damaging and threatening to Gentoo, to justify his dismissal and |
24 |
>> accompanying ban. If such information will not or cannot be provided, |
25 |
>> then it indicates to me that there *is* no proof, and without it I will |
26 |
>> call for his reinstatement for the next council meeting. |
27 |
> |
28 |
> As I'm not a member of ComRel or Council or whatever and I haven't |
29 |
> kept any logs, I think you're being to binary about this. Even if |
30 |
> there is no single thing that shows Ian "irrevocably damaging and |
31 |
> threatening" Gentoo, there can still be a reason to prevent him from |
32 |
> participating in some of our venues. I think the problem with Ian is |
33 |
> that, as hard as he may try to contribute, I found his contributions |
34 |
> to be net negative to the distribution. As such, I do think his |
35 |
> presence is damaging to Gentoo. (And please note that I initially |
36 |
> encouraged him to join us, and, as lead of the Python team at the |
37 |
> time, spent significant time ironing out issues that arose from his |
38 |
> attempts at contribution.) |
39 |
|
40 |
I can understand a stance like that; are there bugs or a history of |
41 |
reversions that I can reference to corroborate this? At the core of it, |
42 |
there should be clear evidence that his contributions hurt or otherwise |
43 |
make maintaining the distribution difficult. I hope that if I were in |
44 |
that sort of situation, that efforts would be made to illustrate why my |
45 |
contributions were subpar and steps I could take to improve them in the |
46 |
long run. So if Ian's contributions really weren't helping us, there |
47 |
should be a history that indicates such. |
48 |
|
49 |
>> I am not alone in requesting accountability from the top of Gentoo. I |
50 |
>> will take the results of this conversation into consideration when it's |
51 |
>> time to vote next year, as Gentoo is suffering from staffing issues and |
52 |
>> practices like this actively damage Gentoo's ability to attract and |
53 |
>> retain contributors. I have personally met people who have suffered as a |
54 |
>> result of this debacle; people willing and eager to help us out that are |
55 |
>> still struggling to join our ranks. So what gives? |
56 |
>> |
57 |
>> This distribution should not turn away anyone willing (and able) to |
58 |
>> help. This is a critical flaw that could accelerate our decline. |
59 |
> |
60 |
> I respectfully but strongly disagree. Some people that are willing and |
61 |
> able to help can in the end turn out to be negative contributors. It |
62 |
> is imperative for our community that we can identify those people and |
63 |
> minimize their impact on the distribution both socially and |
64 |
> technically. |
65 |
|
66 |
I think I understand where you're coming from -- sometimes people can be |
67 |
toxic in their attitudes and make contributing a pain for other |
68 |
developers. I've not really seen any evidence of Ian being that type of |
69 |
person, however. Some off-color jokes that may have been in poor taste, |
70 |
maybe a misunderstanding or two, but that doesn't strike me as a big |
71 |
problem. We're a worldwide community, and naturally there may be |
72 |
language or cultural barriers or norms that clash. I think that's |
73 |
completely normal and expected. It's how we deal with those differences |
74 |
that gauges our social merit. |
75 |
|
76 |
If we're wanting to keep someone out -- be it Ian or someone else -- |
77 |
*some* sort of evidence or reasoning is necessary. Evidence that shows a |
78 |
given person doesn't have the distribution's best interests in mind or |
79 |
evidence that someone can't work well with (many) others. Note the |
80 |
plural; sometimes two particular people just don't get along. Rather |
81 |
than expelling one of the two, I think it's fair to expect developers to |
82 |
acknowledge each others' differences but respect each other as people. |
83 |
If they can't respect each other, then they should be able to work on |
84 |
their own projects without harassing each other. |
85 |
|
86 |
Other cases like William's departure, Diego's, Ciaran's, etc are also of |
87 |
interest to me (I will save those for some other time), because our |
88 |
ability to handle conflict will reflect on us as a distribution and |
89 |
knowing the history of the organization one is part of is important. |
90 |
It's hard to know where to go next if you don't know where you've been. |
91 |
I hope that viewpoint makes sense to someone besides me. |
92 |
> |
93 |
> Cheers, |
94 |
> |
95 |
> Dirkjan |
96 |
> |
97 |
|
98 |
(apologies if I misunderstood something; still haven't had my coffee yet) |
99 |
-- |
100 |
Daniel Campbell - Gentoo Developer |
101 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
102 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |