Gentoo Archives: gentoo-project

From: Dale <rdalek1967@×××××.com>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] Re: Trying to become a Gentoo Developer again spanning 8 years...
Date: Wed, 12 Oct 2016 20:36:38
Message-Id: 57FE9ED3.2070404@gmail.com
In Reply to: Re: [gentoo-project] Re: Trying to become a Gentoo Developer again spanning 8 years... by Rich Freeman
1 Rich Freeman wrote:
2 > On Wed, Oct 12, 2016 at 1:40 AM, Dale <rdalek1967@×××××.com> wrote:
3 >> It seems to me that William posted something that someone else didn't
4 >> like.
5 > That seems like a pretty big assumption. How do you know that it has
6 > something to do with something he posted?
7
8 OK. Are you saying he did nothing wrong and was banned from a mailing
9 list, resigned as trustee and retired as a developer for doing nothing
10 at all? If that is the case, then Gentoo and ComRel has much larger
11 problems than it seems. While I said "posted", I basically meant he
12 said or did something that was not to someone's liking. I'm basing that
13 on what William wrote himself. I seem to recall he said he was banned
14 from a mailing list in one of the many posts here or in a link he
15 posted. It would seem to me that he posted something on that mailing
16 list that someone felt shouldn't be posted. My email is not a legal
17 document where I must include each and every single thing that may or
18 may not need to be listed. My email was my take on the topic based on
19 what I read. I might add, I was here when this happened. I do have a
20 very vague recollection of it. I suspect that I saw some spill over
21 threads and not the original cause of it tho. I'm certainly not basing
22 my replies on what I recall about it. That's way to long ago.
23
24 >
25 >> I mentioned I help admin a website. If someone violates the rules, I
26 >> contact them on it and they chose to delete their account instead of
27 >> dealing with the matter, it doesn't mean they can never rejoin the
28 >> site. It does mean that if they do and I know it, then they would have
29 >> to address the previous problem.
30 > That is basically the same as Gentoo. I've yet to see an appeal where
31 > the person appealing wasn't told in writing exactly what the concern
32 > was. If they weren't that would certainly be something I'd be
33 > concerned about in an appeal.
34
35 I agree. No one should have action taken on them without the person
36 first being warned.
37
38 >
39 > Personally, I care far more about whether somebody is likely to follow
40 > the CoC TODAY than the exact circumstances of how they may have
41 > violated it 8+ years ago. ANY new recruit has to demonstrate that
42 > they are likely to follow the CoC and ones who may have violated it in
43 > the past are subject to more scrutiny.
44
45 I think the question here is this. Was the ban from the mailing list
46 all of it punishment wise or was there some secret discussion later that
47 lead to William being effectively blacklisted? If what William did was
48 that bad, shouldn't he be told, whether he left Gentoo or not? On the
49 site I help with, when I ban someone, they are notified of why they are
50 banned. They are also given a email address to email to appeal the
51 ban. On that site, it is done automatically by the software. In this
52 situation tho, it seems that William has not been advised of that
53 decision, if one was made at all. Again, this is happening in what
54 others call a black box.
55
56 >
57 > Something that keeps coming up in this discussion is reference to
58 > process and procedure within Comrel. The concern is nobody
59 > understands how they made the decision, or what rules they were
60 > supposed to follow. When appeals are discussed they're in terms of
61 > whether Comrel followed the rules when it did its job. I get that
62 > courts often work this way.
63 >
64 > However, I think we should be far more concerned about outcome. Is
65 > somebody willing to follow the CoC, or not? Are they able to follow
66 > the CoC, or not? Perhaps the way the black box works can be improved,
67 > and maybe we can expose more of the gears inside, but what matters the
68 > most is that it comes up with the right decision.
69 >
70 > So, if you don't like the results of a decision by all means appeal
71 > it. I can't promise that Council will follow the same rules Comrel
72 > followed. As far as I'm aware the Council hasn't really set any rules
73 > as to how it judges appeals. Ultimately what you'll get is an
74 > independent evaluation of whatever concerns Comrel raises (or which
75 > were originally raised to Comrel), and any subsequent behavior of the
76 > parties involved, and a judgement as to how the situation should be
77 > handled.
78
79 I agree mostly here as well. I also believe that William needs to
80 appeal the decision, whatever that was or if one was ever made beyond
81 the email ban. Personally, based on William's posts here, it doesn't
82 seem that a official decision was made. Again, black box that we can't
83 see into.
84
85
86 >
87 > And this brings me back to a concern I mentioned a long time ago in
88 > this thread: appeal on the basis that you've proven that you're a good
89 > member of the community. If the basis of your appeal is that your
90 > behavior shouldn't matter, well, don't be surprised if it is defeated.
91 > If the basis of your appeal is that Comrel is out to get you, well,
92 > I'm sure it will get considered and maybe some reforms may come out of
93 > it if there is something to it, but whether you stay or go is a
94 > separate matter. If the basis of your appeal is that Comrel didn't
95 > complete step 2.3.1 of the Comrel rules of procedure then maybe we'll
96 > ask Comrel to try to follow the rules better or fix them after sending
97 > you on your way. If the basis of your appeal is that Comrel shouldn't
98 > exist in the first place, well, hopefully that isn't all there is to
99 > it. Ultimately we're going to be more concerned with whether the CoC
100 > is being followed and is likely to be followed.
101
102 I can see this point as well. As I mentioned before, I was here when
103 the mailing lists were a disaster. It was a long time ago but I recall
104 it being bad. Even tho today no one actually seems to read every post,
105 people do know that there is a policing body that can deal with the
106 occasional problem. It's sort of like driving by a police car that is
107 very visible. It's natural to make sure you are within the law as you
108 drive by. We do have the occasional spammer or something that pops up
109 and then disappears. I recall seeing someone post that a good while
110 back. Just knowing that the mailing lists are being policed helps keep
111 it within reason. I wouldn't want that gone either. I wouldn't want
112 the mailing lists to go back to what they used to be years ago. If the
113 goal William has is to get rid of ComRel, that likely won't end well.
114 Changes to ComRel if needed, sure. End it, I hope not.
115
116 >
117 > So, if you appeal a Comrel decision there aren't any magic words to
118 > say. Hiring a better lawyer isn't likely to impress anybody. You
119 > really just need to show that you have changed or are likely to
120 > change. And if you want to be a dev and aren't one yet, just interact
121 > positively with the community and nobody is going to have something to
122 > object to. You don't need to agree with every policy or be afraid of
123 > speaking up when you disagree. However, you do need to try to
124 > maintain a semi-professional attitude and treat people with respect,
125 > and you do need to follow the rules. There are cases where I disagree
126 > with most of the devs and probably the entire Council, and I've voiced
127 > those publicly. However, that doesn't stop me from working
128 > productively with anybody and it isn't personal and I follow the rules
129 > as they've been agreed upon, so I've yet to see anything come of it.
130 > There are devs who are fairly antisocial and they just sit in their
131 > corner doing commits all day, and nobody bothers them either as long
132 > as they follow QA policy. The people who get dragged into the Comrel
133 > process seem to be creating trouble in IRC (on channels, PMs, etc), or
134 > somethings on the mailing lists. Often it is just an
135 > argument/banter/etc that gets out of hand, but instead of just
136 > apologizing and changing they double down and dig in. That is a very
137 > broad generalization and a somewhat ignorant one since I only hear
138 > about cases that are appealed or which become so big that they become
139 > more public knowledge.
140
141 I have to do the same thing on the site I help with. There are rules I
142 don't agree with but I still have to enforce them. If I don't, then I
143 need to either step down on my own or will be forced to leave. As you
144 say, if William has a problem with something, speak up and explain what
145 is wrong but do it within the current rules.
146
147 >
148 > I'm not saying the way that Comrel operates doesn't matter. I'm
149 > certainly not saying that there isn't room for improvement. However,
150 > any changes that get made, and any criticism of how it works, need to
151 > be rooted in the ultimate goal: having a community that follows the
152 > CoC. If the concern is with the CoC itself that is also something
153 > that can be changed, and anybody is free to argue that it isn't right.
154 > However, there isn't going to be some loophole where with the right
155 > argument you can basically mistreat others in the community and get
156 > away with it. Nor is the bar going to be set unreasonably high for
157 > Comrel to deal with people who do so.
158 >
159
160 I think part of the problem may be the "black box" method currently is
161 use. I know on the site I help on, staff knows and sees things that
162 members can't see. As a example, someone posts a reply that clearly
163 violates the rules and then immediately deletes the post. We as staff
164 can see that deleted post. Regular members can't see it tho. If staff
165 takes action on that post, then the members have no idea what happened
166 to cause the action. Members are running around complaining that we
167 restricted/banned someone for nothing because they can't see the post we
168 see. Thing is, we know we did the right thing. Just like with ComRel
169 tho, we can't post a screenshot or anything that shows why the action
170 was taken. Members remain clueless and sometimes angry. This is
171 basically where we are, and maybe William too. We don't know what
172 happened in the black box. Until William appeals it, he may not know
173 either.
174
175 This is likely my last reply. While I would like to see Gentoo improved
176 and all, I have to much going on in the real world to spend time
177 debating it. I just felt the need to make my post in case it would
178 help. If it doesn't, Gentoo is still Gentoo.
179
180 Dale
181
182 :-) :-)

Replies