Gentoo Archives: gentoo-dev

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: Abuse by gentoo developer
Date: Wed, 20 Jul 2005 09:57:33
Message-Id: pan.2005.07.20.09.54.16.156104@cox.net
In Reply to: [gentoo-dev] Abuse by gentoo developer by Casey Allen Shobe
1 Casey Allen Shobe posted <200507200132.30745.lists@×××××××××××××.com>,
2 excerpted below, on Wed, 20 Jul 2005 01:32:30 +0000:
3
4 > Hello all, I'm sorry to bring this here, but I don't know where else to
5 > take it, and feel that I was treated really unfairly.
6 >
7 > As you know, I recently inquired about ebuild development on this list,
8 > and mentioned vpopmail. <developer> answered my mail and suggested that
9 > I submit a patch.
10 >
11 > I then spent some time working on the ebuild, and in doing so,
12 > discovered that the postgres support in vpopmail was not very good at
13 > all, so I wrote back to <developer>, and said that I was going to hold
14 > off working on the ebuild since I am currently working with the vpopmail
15 > team to improve vpopmail itself. <developer> wrote this rather rude
16 > reply:
17 >
18 > -------------------
19 > Casey Allen Shobe wrote:
20 >> Well I patched the ebuild and got it working, but I'm so terribly
21 >> disappointed with vpopmail's horrible postgresql support that I don't
22 >> think I'll be using it at all until I rewrite it. :P
23 >>
24 >> Ah well, thanks anyways. I'll let you know when/if they let me fix
25 >> vpopmail (already posted about it on the list).
26 >
27 > The will not allow it and I will not allow someone to go fooling in an
28 > ebuild I maintain. Not trying to be an ass here but we have something
29 > called respect for others when it comes to the tree and what they
30 > maintain.
31
32 snip/snip..
33
34 The following could be considered philosophical ramblings by some. Those
35 who don't like that sort of thing.. skip on to the next message.
36
37 So as not to get too personal, I replaced the name with <developer>. I
38 really wish this had been done in the original. After all, for those
39 needing to know, it's not difficult to trace who <developer> might be,
40 especially since this was posted to a public list with the (ostensible)
41 goal of finding where to take it next, NOT to specifically point fingers,
42 and leaving names out of it can sometimes help ease tensions.
43
44 As others have stated, devrel is the place to take it. However, there was
45 the question of what remark may have been taken wrongly. I think I see
46 that, above.
47
48 <developer> likely took the "horrible ... support ... I won't be using at
49 all until I rewrite it" as a threat to his maintainership of the package,
50 not seeing that you meant working with upstream. Else, perhaps he was
51 instrumental in creating the original upstream support you just called
52 "horrible", saying you were going to "rewrite" it, in which case yeah, I
53 can see someone getting a bit offended over that.
54
55 Yes, folks need to develop a rather thicker skin and take offense less
56 easily. However, the FLOSS community is unfortunately all too rich with
57 stories of rivalries and enemies made, for no reason other than offense
58 was taken where no offense was originally intended.
59
60 I've come to believe, due to a large degree to my own often humbling
61 experiences, that a good portion of the problem is that FLOSS community
62 developers often tend to be far better at what they do than most of their
63 real life peers, and are used to being considered /the/ reference
64 authority on their interests and often on computers or technology in
65 general. In meatspace, they are usually 90th percentile and above, and so
66 used to "explaining" things in "normal people" terms that they do it as a
67 matter of course, simply assuming (usually correctly, in meatspace) they
68 have a better understanding of the topic than anyone else around.
69
70 Now, take this 90th plus percentile person, and change their peer group
71 from one of the general population to one where they are co-equal or even
72 at the LOW end of understanding of the tech involved, and it can be a VERY
73 humbling experience. NO LONGER are they always right, or at least "right
74 enough" that no one else has the knowledge to question them! Getting
75 used to being at the LOW end, having folks talk down to YOU, as you've
76 been used to talking down (not in a mean way, but just at a level that can
77 be understood) to others, NOT being the unquestioned authority on the
78 subject because no one else knows enough about it to question you, takes a
79 *LOT* of getting used to.
80
81 It is my belief that many of the misunderstandings in the community are
82 based on this problem. Someone has a huge ego, because they are used to
83 being right, 99% of the time, and never having to say "I'm sorry", or "I
84 was wrong". Get that someone interfacing with another someone with the
85 same problem, and there can be and often are fireworks! Most in the
86 community eventually learn to deal with the problem, becoming rather more
87 humble in the process, but some never do. One of the amazing things about
88 Linus, if you've watched him in action, is how well he seems to have
89 learned this lesson -- how incredibly well he defuses the situation (in
90 most cases, the bitkeeper thing was exceptional in that it was the
91 exception proving the general point) with his self deprecating humor.
92
93 So... I'd just consider this the growing pains of a developer, faced with
94 dealing with an environment where he is surrounded by mostly equals (or
95 better) for the first time, thus, STRONGLY reacting as if his legitimacy
96 was challenged, at the slightest suggestion that there might be a
97 different and possibly better solution to the issue. That words like
98 "horrible" and "rewrite" were included only strengthened what was in his
99 view a serious challenge to his maintainership, and therefore, to his
100 legitimacy as a Gentoo developer.
101
102 I'd suggest apologies would be in order from both sides. Unfortunately,
103 when one side has resorted to kill filing the other, it's very difficult
104 to get an apology through, and yes, then it's time to involve a third
105 party, the reason devrelations is there. Ideally, both sides ultimately
106 learn from the situation, making the one less likely to take offense and
107 more "professional" in his reactions even when he /does/ take /personal/
108 offense, and the other more aware of the sensitivity of words such as
109 "horrible" and "rewrite", particularly for those somewhat insecure in
110 their position in the first place.
111
112 --
113 Duncan - List replies preferred. No HTML msgs.
114 "Every nonfree program has a lord, a master --
115 and if you use the program, he is your master." Richard Stallman in
116 http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
117
118
119 --
120 gentoo-dev@g.o mailing list