1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Donnie Berkholz wrote: |
5 |
| From this month's agenda: |
6 |
| |
7 |
| User Relations authority |
8 |
| ------------------------ |
9 |
| |
10 |
| Ferris asks: Does userrel have the authority to enforce the Code of |
11 |
| Conduct on users in the same way devrel does for developers? |
12 |
|
13 |
Yes, it does and it always had. If people want to invoke history, I'll |
14 |
notice that imo, it was an option not to exercise that power. |
15 |
|
16 |
| Preparation: Donnie will start a thread on the -council list. Post |
17 |
| your opinion there. If everyone's posted in advance of the meeting, |
18 |
| status check at meeting to see who's ready to vote. |
19 |
| |
20 |
| Goal: Reach a decision on-list no later than July 17. |
21 |
| |
22 |
| Please respond with your thoughts. |
23 |
| |
24 |
|
25 |
Ferris McCormick wrote: |
26 |
| On Wed, 2008-07-09 at 01:40 -0700, Donnie Berkholz wrote: |
27 |
|> On 05:30 Tue 01 Jul , Mike Frysinger wrote: |
28 |
|> Here's the proposed agenda. Please respond if I forgot something, it's |
29 |
|> unclear, or you have another suggestion. As before, since we have an |
30 |
|> agenda in advance we won't be holding an open floor. |
31 |
| |
32 |
| I'll try to clarify my second agenda item on an absolute ban. Also I |
33 |
| might edit my private request to make it pure vanilla and send it out, |
34 |
| too, so that people may cross check my summary if they wish. If people |
35 |
| want that, please respond saying so. |
36 |
| |
37 |
| 1. Your summary in the agenda is a fair reading of my request. |
38 |
| However, I don't think it's realistic to expect a decision within a week |
39 |
| because I think instituting a policy and procedure allowing a complete |
40 |
| ban forever from Gentoo requires at the least a change to the Code of |
41 |
| Conduct and a review cycle for that. |
42 |
|
43 |
Ferris, I know we disagree on this point, but my view is that this isn't |
44 |
a new CoC, but instead a discussion on how to finally enforce the CoC in |
45 |
extreme cases. |
46 |
However, I agree with you that before we start doing it, we should have |
47 |
clear rules and define procedures. |
48 |
|
49 |
| 2. I can't spell out exactly what people are thinking of when |
50 |
| discussing absolute bans, because I get the sense that different people |
51 |
| have different ideas about just what we would mean by that. So I think |
52 |
| the first step is for someone who advocates such a procedure needs to |
53 |
| spell out exactly what it would be and why we would do it and under |
54 |
| whose authority, etc. As probably everyone knows, I am absolutely |
55 |
| opposed to any such thing, so I am not the person to do this. |
56 |
|
57 |
Then let me present my old proposal about this issue. The two relevant |
58 |
posts at the time were: |
59 |
|
60 |
http://article.gmane.org/gmane.linux.gentoo.devel/46846 |
61 |
http://article.gmane.org/gmane.linux.gentoo.devel/46897 |
62 |
|
63 |
To summarize, my proposal was that we should have a method to "keep |
64 |
away" people that do nothing but cause continuous issues - this is about |
65 |
the "poisonous people" that are long-time and repeated offenders. |
66 |
As I've stated back then "I believe that the greatest reward anyone can |
67 |
have to participate in Gentoo is getting credit for work done on Gentoo. |
68 |
As such, as a last measure, we must be ready to deny such contribution |
69 |
from banned users." |
70 |
As I've stated, that doesn't mean we don't accept the work someone does |
71 |
upstream. Also, to avoid any doubts, I'm not suggesting we use someone's |
72 |
work without giving him/her the credit - quite the opposite. Exactly |
73 |
because of that, we must be ready to have additional work and not accept |
74 |
their work and find an internal solution. About the security patches, if |
75 |
they're provided by upstream or to upstream, there's no issue with them. |
76 |
If they're provided directly to us, are we really that "bad" that in |
77 |
such cases we're unable to find another contributor or to patch |
78 |
ourselves the security flaw? |
79 |
|
80 |
Let others present different proposals. |
81 |
|
82 |
| 3. So, I don't think we can reach a decision on anything until we are |
83 |
| all clear on what we are deciding on. |
84 |
| |
85 |
| 4. Here's what I think is meant by a complete ban. *These are only my |
86 |
| own inferences from reading between the lines and trying to put |
87 |
| different comments together in some coherent fashion.* |
88 |
| Under some rather unclear conditions, some combination of |
89 |
| devrel/userrel/trustees/infra could decide to impose a complete, |
90 |
| permanent ban on a member (user or, I suppose developer) of our |
91 |
| community. This would have the following effects: |
92 |
|
93 |
Some people seem to support that userrel can make such decisions on its |
94 |
own. As I've stated, as an userrel member, I was willing to involve |
95 |
other teams. We also need to agree to which body should appeals be sent. |
96 |
|
97 |
| a. The person could post to no gentoo mailing list; |
98 |
| b. The person could not post to gentoo bugzilla; |
99 |
|
100 |
check |
101 |
|
102 |
| c. The person could not participate in #gentoo- IRC |
103 |
| channels (although this runs into conflict with individual |
104 |
| channel policy); |
105 |
|
106 |
I think the proposal was more along #gentoo-dev, #gentoo and a few other |
107 |
channels. This point was to prevent people from abusing irc channels and |
108 |
in the case of #gentoo-dev to prevent other devs from giving +v on |
109 |
moderated channels to people that keep abusing them. |
110 |
|
111 |
| d. The person could not contribute to gentoo (hence my corner |
112 |
| case of a security fix) except perhaps through a proxy; |
113 |
|
114 |
See the above reasoning for my proposal |
115 |
|
116 |
| e. (Perhaps any upstream projects in which the person banned |
117 |
| would be notified of the ban??? --- I'm not sure). |
118 |
|
119 |
My comment about this has always been that in extreme cases and if we |
120 |
have a close partnership with upstream, we might want to share with them |
121 |
our decision and let them judge for themselves if the actions that made |
122 |
such person be banned on Gentoo are relevant to them or not. |
123 |
|
124 |
| 5. I am told that nothing is forever, and that if whatever problems |
125 |
| triggered such a ban were corrected, the ban might be lifted. I note, |
126 |
| however, that since the banned person could not participate in Gentoo |
127 |
| things, as a practical matter we'd never know if anything was corrected |
128 |
| or not. (Except through 3rd parties.) |
129 |
|
130 |
The point here is that such a decision is not terminal. If people feel |
131 |
more comfortable about it, don't call it permanent bans, but call it a |
132 |
ban until further notice. |
133 |
|
134 |
| 6. Presumably, all of this would be done in secret and whoever is being |
135 |
| hit by such a ban would have no opportunity to respond before the ban's |
136 |
| imposition. I suppose there would be a right to appeal to council, |
137 |
| assuming council took no part in deciding on the ban. |
138 |
|
139 |
I assume what you mean here is that there would be no attempt of |
140 |
mediation with said person. As my proposal states this is an *extreme* |
141 |
decision meant only for *long-time* and *repeated* offenders. When we |
142 |
get there, there's no possibility for mediation - that's something that |
143 |
would have been tried a long time before we get there. |
144 |
|
145 |
| 7. [Argument] I view this as a pretty major change in how Gentoo |
146 |
| operates. So someone needs to clarify my inferences in paragraph 4, and |
147 |
| then we should think very carefully about it before allowing for any |
148 |
| such practice. |
149 |
|
150 |
I've replied above. |
151 |
|
152 |
| 8. [Argument] I note that we are likely to institute some form of |
153 |
| possible moderation for the gentoo-dev mailing list (presumably based on |
154 |
| Code of Conduct violations), and if we do that, it effectively satisfies |
155 |
| the intent of any absolute ban, but is not nearly so traumatic to the |
156 |
| system. I note that this is a minority view among those who have |
157 |
| discussed this. |
158 |
|
159 |
Ferris, I do hope the moderation will prevent so many abuses on the mls, |
160 |
but it alone won't change people's mindsets and actions. Although posts |
161 |
can be moderated, it doesn't mean that people will stop trying to send |
162 |
abusive mails and that a few might even get to the lists. Also, it |
163 |
doesn't address irc, bugzilla and other mediums abuse. |
164 |
|
165 |
| Donnie, |
166 |
| I don't know if that clarifies anything or just makes things more |
167 |
| confusing. It's the best I can come up with. |
168 |
| |
169 |
| Regards, |
170 |
| Ferris |
171 |
|
172 |
- -- |
173 |
Regards, |
174 |
|
175 |
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
176 |
Gentoo- forums / Userrel / SPARC / KDE |
177 |
-----BEGIN PGP SIGNATURE----- |
178 |
Version: GnuPG v2.0.9 (GNU/Linux) |
179 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
180 |
|
181 |
iEYEARECAAYFAkh19z8ACgkQcAWygvVEyAJYbACgnAIEcXC1xyR3ZffRkCtLqyVJ |
182 |
/w0AnA3u+58ui3/Ih/aLvjXoL2bZwn/v |
183 |
=M4kk |
184 |
-----END PGP SIGNATURE----- |
185 |
-- |
186 |
gentoo-council@l.g.o mailing list |