1 |
On Wed, 2008-07-09 at 22:49 -0700, Donnie Berkholz wrote: |
2 |
> From this month's agenda: |
3 |
> |
4 |
> User Relations authority |
5 |
> ------------------------ |
6 |
> |
7 |
> Ferris asks: Does userrel have the authority to enforce the Code of |
8 |
> Conduct on users in the same way devrel does for developers? |
9 |
> |
10 |
> Preparation: Donnie will start a thread on the -council list. Post |
11 |
> your opinion there. If everyone's posted in advance of the meeting, |
12 |
> status check at meeting to see who's ready to vote. |
13 |
> |
14 |
> Goal: Reach a decision on-list no later than July 17. |
15 |
> |
16 |
> Please respond with your thoughts. |
17 |
|
18 |
I didn't even remember that I had asked this, but here are my thoughts. |
19 |
|
20 |
1. Yes, Userrel has (or should have) that authority; |
21 |
2. But for both devrel and userrel, the Code of Conduct loses almost |
22 |
all its impact unless response is immediate --- CoC's intent, I think, |
23 |
is to help keep the mailing lists and #gentoo-dev channel on track |
24 |
pretty much in real time. I know this was the original idea behind it, |
25 |
and this was one reason we felt we needed people outside devrel to help |
26 |
enforce it (devrel is not set up for immediate responses); |
27 |
3. Thus, I think bugzilla bugs for Code of Conduct violations miss much |
28 |
of the point. |
29 |
4. That is, we (devrel, userrel, averyone else perhaps) should use Code |
30 |
of Conduct to stop elaborate flame wars before they can burn out of |
31 |
control. Whether a flame war ever merits a bug will vary from situation |
32 |
to situation, but generally if we have a flame war and wish to impose |
33 |
some sort of sanctions because of it, we really need to be hitting |
34 |
several people or none with warnings or brief "vacations." |
35 |
|
36 |
5. I am not sure where the current Code of Conduct document is, but |
37 |
I'll volunteer to help update it to bring it into line with how we wish |
38 |
to use it and to help clarify who has what authority under it, and that |
39 |
sort of thing. I have come to support it, and I'd like to help make it |
40 |
more effectively used in the rather narrow context for which it was |
41 |
designed before we consider extending its reach. |
42 |
6. For example, I think we could put some sort of limited moderation |
43 |
onto the -dev mailing list, citing the current Code of Conduct as |
44 |
authority, any time we wanted. And I do not think the Code of Conduct |
45 |
as currently envisioned has much reach into the past (one or two days, |
46 |
probably; one or two weeks, perhaps; one or two months, no; one or two |
47 |
years, certainly not). |
48 |
|
49 |
I hope you get the idea. Although I advocate brevity, I have problems |
50 |
practicing it. |
51 |
|
52 |
Regards, |
53 |
Ferris |
54 |
-- |
55 |
Ferris McCormick (P44646, MI) <fmccor@g.o> |
56 |
Developer, Gentoo Linux (Devrel, Sparc, Userrel, Trustees) |