1 |
I think privacy from the wider community would be a good thing in the |
2 |
first instance for two reasons. |
3 |
a) it allows people to come forward in confidence that they wont be |
4 |
targeted by the accused for what ever reason. |
5 |
b) it allows the accused to deal with the issue quietly, and resolve |
6 |
the issue without it becoming a bigger issue than it needs to (an |
7 |
misunderstand blows out to much more, or false allegations tarnish |
8 |
their reputation. |
9 |
|
10 |
I agree with Rich, I haven't seen an organisation make all complaints |
11 |
handling a completely transparent and open processes it has too much |
12 |
risk of abuse. |
13 |
|
14 |
What I think is important though is that both parties involved have |
15 |
information about the events/complaints/examples. If you cant give |
16 |
this, then how are they to discuss the issue, or defend themselves |
17 |
against COMREL/Complainant. |
18 |
|
19 |
I realize I am not a dev, but for awhile I was actively pursuing this |
20 |
and the situation with Idella4 (who was my mentor) has made me have |
21 |
second thoughts, from the information I have been able glean about |
22 |
what occurred, and also the way his retirement was handled cause |
23 |
confusion and disillusionment with the whole process for me at least |
24 |
and I think a few non-devs from Proxy-Maint IRC channel feel the same. |
25 |
|
26 |
Just me 2cents |
27 |
|
28 |
Craig |
29 |
|
30 |
On Fri, Dec 2, 2016 at 11:59 AM, Rich Freeman <rich0@g.o> wrote: |
31 |
> On Fri, Dec 2, 2016 at 1:13 AM, Raymond Jennings <shentino@×××××.com> wrote: |
32 |
>> |
33 |
>> Whose privacy, exactly, is at stake if comrel were to breach confidentiality |
34 |
>> on this issue? I'd rather ask for a full list. |
35 |
>> |
36 |
> |
37 |
> I wouldn't advocate opening this up even if nobody's privacy were at |
38 |
> stake, as I believe the issue goes beyond privacy. (It tends to pit |
39 |
> people against each other, if accusations are false (or true) they can |
40 |
> become damaging to reputations, and so on. Almost no organization I'm |
41 |
> aware of publishes this kind of stuff, and counterexamples are |
42 |
> welcome.) |
43 |
> |
44 |
> However, opening up comrel evidence affects the privacy of the person |
45 |
> who is the subject of a comrel action, and those who told that the |
46 |
> information would be kept private when they submitted their |
47 |
> complaints/etc. |
48 |
> |
49 |
> And this is a big part of why the Council decided not to open up this |
50 |
> evidence. People had already been told that information would be kept |
51 |
> private. And that is in my email WAY back at the beginning when I |
52 |
> opened this up for discussion I phrased the question in terms of what |
53 |
> kinds of expectations of privacy should we allow. IMO we can't tell |
54 |
> people that information will be kept private, and then later change |
55 |
> our minds. Now, we could have a policy that all submitted information |
56 |
> is public, and when somebody says, "could I tell you something in |
57 |
> private" Comrel could respond with, "sorry, but any information that |
58 |
> you give me that concerns another member of the community will be |
59 |
> published and I cannot promise that information will be kept private." |
60 |
> |
61 |
> I still tend to favor allowing information to be submitted in private |
62 |
> for reasons I've already stated back in those 100+ post threads. |
63 |
> However, it is a debate I don't mind having. |
64 |
> |
65 |
> What I don't think we can do is publish information without the |
66 |
> permission of those who provided it, without obtaining that |
67 |
> permission, which I suspect is unlikely to be forthcoming anyway. |
68 |
> |
69 |
> -- |
70 |
> Rich |
71 |
> |