1 |
Ferris McCormick <fmccor@g.o> said: |
2 |
> |
3 |
> On Wed, 2008-07-09 at 22:49 -0700, Donnie Berkholz wrote: |
4 |
> > From this month's agenda: |
5 |
> > |
6 |
> > User Relations authority |
7 |
> > ------------------------ |
8 |
> > |
9 |
> > Ferris asks: Does userrel have the authority to enforce the Code of |
10 |
> > Conduct on users in the same way devrel does for developers? |
11 |
> > |
12 |
> > Preparation: Donnie will start a thread on the -council list. Post |
13 |
> > your opinion there. If everyone's posted in advance of the meeting, |
14 |
> > status check at meeting to see who's ready to vote. |
15 |
> > |
16 |
> > Goal: Reach a decision on-list no later than July 17. |
17 |
> > |
18 |
> > Please respond with your thoughts. |
19 |
> |
20 |
> I didn't even remember that I had asked this, but here are my thoughts. |
21 |
> |
22 |
> 1. Yes, Userrel has (or should have) that authority; |
23 |
|
24 |
Cool, we agree that userrel has this authority. |
25 |
|
26 |
> 2. But for both devrel and userrel, the Code of Conduct loses almost |
27 |
> all its impact unless response is immediate --- CoC's intent, I think, |
28 |
> is to help keep the mailing lists and #gentoo-dev channel on track |
29 |
> pretty much in real time. I know this was the original idea behind it, |
30 |
> and this was one reason we felt we needed people outside devrel to help |
31 |
> enforce it (devrel is not set up for immediate responses); |
32 |
|
33 |
I think we should then make it so that userrel and devrel have the |
34 |
authority and/or power to respond immediately to problems in real time. |
35 |
Why isn't devrel set up to respond to problems "real time"? |
36 |
|
37 |
> 3. Thus, I think bugzilla bugs for Code of Conduct violations miss much |
38 |
> of the point. |
39 |
|
40 |
If someone is abusing bugzilla to berate people, they should be |
41 |
punished. |
42 |
|
43 |
> 5. I am not sure where the current Code of Conduct document is, but |
44 |
> I'll volunteer to help update it to bring it into line with how we wish |
45 |
> to use it and to help clarify who has what authority under it, and that |
46 |
> sort of thing. I have come to support it, and I'd like to help make it |
47 |
> more effectively used in the rather narrow context for which it was |
48 |
> designed before we consider extending its reach. |
49 |
|
50 |
I'm not sure exactly what these statements mean. Could you please |
51 |
elaborate on how you support it currently? And what sort of changes you |
52 |
would like to avoid before you support the CoC further? |
53 |
|
54 |
> 6. For example, I think we could put some sort of limited moderation |
55 |
> onto the -dev mailing list, citing the current Code of Conduct as |
56 |
> authority, any time we wanted. And I do not think the Code of Conduct |
57 |
> as currently envisioned has much reach into the past (one or two days, |
58 |
> probably; one or two weeks, perhaps; one or two months, no; one or two |
59 |
> years, certainly not). |
60 |
|
61 |
So you wish to limit the reach of its timeframe? Could you please |
62 |
elaborate on what you mean here? I'm not sure what you are trying to |
63 |
express. |
64 |
|
65 |
Thanks, |
66 |
|
67 |
-- |
68 |
Mark Loeser |
69 |
email - halcy0n AT gentoo DOT org |
70 |
email - mark AT halcy0n DOT com |
71 |
web - http://www.halcy0n.com |