1 |
On 11/06/2016 05:42 PM, Rich Freeman wrote: |
2 |
> [snip] |
3 |
> |
4 |
> I wouldn't say that operating in confidentiality in these matters is |
5 |
> ideal, but it seems like the least worst alternative. The rest just |
6 |
> seem like a good idea until you think through what would happen if you |
7 |
> actually tried them out. |
8 |
> |
9 |
|
10 |
(somewhat long, skip to tldr at the bottom if desired) |
11 |
|
12 |
I'm not convinced of that. I understand and appreciate the angle |
13 |
you're coming from. I think Gentoo owes (some) transparency to its |
14 |
developer and user community _IF_ it's going to try mediating or solving |
15 |
interpersonal problems. I'd rather us expect people to be adults and, if |
16 |
they can't sort things out on their own, simply leave each other alone. |
17 |
|
18 |
Gentoo is ultimately better off if it takes its stance of |
19 |
non-involvement more seriously and butts out of any disputes until |
20 |
they affect Gentoo itself, i.e. commit wars, spam or harassment in |
21 |
IRC/forums, etc. If the status quo is so favored, why do we entertain |
22 |
the idea of Gentoo handling disputes in the first place? We already have |
23 |
the CoC to refer to, and effective means of handling things without |
24 |
being secretive or having a specialized team for it. I mean, ultimately |
25 |
the trustees and infra have complete practical and legal control over |
26 |
Gentoo. |
27 |
|
28 |
Why is comrel necessary? Do we not have policy documents outlining the |
29 |
consequences of violating the CoC? If not, we should. IIRC, agreeing |
30 |
to abide by the CoC is a requirement of becoming a developer. The |
31 |
same people who monitor or maintain our various media can handle the |
32 |
real issues when they become a real problem. We have IRC ops, forum |
33 |
moderators and admins, wiki staff, and so on. In a sense, they already |
34 |
_are_ the CoC enforcers. |
35 |
|
36 |
Removing comrel can reduce legal liability in that there _is_ no |
37 |
investigative team involved, no slander or libel to worry about. Then |
38 |
there's the added bonus of those devs gaining free time to do things |
39 |
that they enjoy rather than listen to greivances and being expected to |
40 |
please two or more parties. |
41 |
|
42 |
Of course, this could be viewed as pushing it off on ops and mods, etc. |
43 |
This wouldn't really increase their workload, because they already have |
44 |
SOP (standard operating procedures). Large problems can be pushed to the |
45 |
council, as they are already elected officials who are expected to make |
46 |
impactful decisions on Gentoo. This creates an agenda point and a log |
47 |
of discussion. It's flexible enough to give the council discretion if |
48 |
something is potentially litigous, and provides a record for those who |
49 |
may want to research the history. If an issue is not big or impactful |
50 |
enough to bring to the council, then the parties involved need to |
51 |
solve their conflict in other, hopefully more constructive ways. Third |
52 |
party platforms already have their own guidelines, so if someone is |
53 |
dissatisfied with Gentoo's action (or inaction), they can go to the |
54 |
platform moderators and we (Gentoo) don't need to be involved. |
55 |
|
56 |
We are all (I hope?) adults, and are expected to act as such, without a |
57 |
secretive group of babysitters. It would be less social overhead and to |
58 |
the betterment of Gentoo in general if we did away with the babysitting |
59 |
project, imo. |
60 |
|
61 |
tldr: we should treat social disputes the same way we treat upstream |
62 |
software: modify it only when Gentoo functionality depends on it. |
63 |
|
64 |
Just my 2¢. |
65 |
-- |
66 |
Daniel Campbell - Gentoo Developer |
67 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
68 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |