1 |
On Sat, Oct 1, 2016 at 10:20 PM, Daniel Campbell <zlg@g.o> wrote: |
2 |
> On 10/01/2016 09:53 PM, Raymond Jennings wrote: |
3 |
>> |
4 |
>> |
5 |
>> On Sat, Oct 1, 2016 at 9:13 PM, Daniel Campbell <zlg@g.o> |
6 |
>> wrote: |
7 |
>>> On 09/30/2016 05:59 PM, Rich Freeman wrote: |
8 |
>>>> [snip] |
9 |
>>>> |
10 |
>>>> 1. When information is turned over to comrel who does it get |
11 |
>>>> shared |
12 |
>>>> with, and under what circumstances? |
13 |
>>> |
14 |
>>> That information should be kept mainly to the comrel member(s) who |
15 |
>>> were |
16 |
>>> reported to. Should the issue become more serious, share it with |
17 |
>>> the |
18 |
>>> rest of comrel according to case needs (one member having a |
19 |
>>> friendship |
20 |
>>> with a given developer, or a professional background in community |
21 |
>>> management, etc). |
22 |
>>> |
23 |
>>>> 2. Do any members of the community have an obligation to |
24 |
>>>> report? Can |
25 |
>>>> members of comrel/trustees/officers/council/etc be told |
26 |
>>>> information in |
27 |
>>>> private without it being shared back with comrel for the official |
28 |
>>>> record? |
29 |
>>> |
30 |
>>> An obligation to report will result in more reporting, some of |
31 |
>>> which |
32 |
>>> will end up being within CoC limits or merely a misunderstanding. |
33 |
>>> Encouragement might not be a bad idea, but forcing them to is just |
34 |
>>> an |
35 |
>>> easy way to make ComRel busy; I'm sure they're just as |
36 |
>>> understaffed as |
37 |
>>> the rest of Gentoo, however. |
38 |
>> |
39 |
>>>> 3. Specifically, what information gets shared with people named |
40 |
>>>> in a |
41 |
>>>> dispute of some kind? |
42 |
>>> |
43 |
>>> It depends on the type of dispute. If it's happenstance in a public |
44 |
>>> medium such as the forums, bugzilla, or the ML, then the |
45 |
>>> antagonists and |
46 |
>>> their actions are known and can be shared freely. |
47 |
>>> |
48 |
>>> In short I think the privacy level of a dispute should never become |
49 |
>>> lower than the occurrence of the "crime". So if it was in PMs on |
50 |
>>> IRC, it |
51 |
>>> now concerns the ComRel member who was contacted, Party A, and |
52 |
>>> Party B. |
53 |
>>> It should only expand when one ComRel member isn't enough. |
54 |
>>> |
55 |
>>> Impactful changes to Gentoo staffing are deserving of mention, but |
56 |
>>> in |
57 |
>>> general terms, like "Foobar project no longer has a lead, election |
58 |
>>> scheduled for..." |
59 |
>>> |
60 |
>>>> 4. Under what circumstances will information be shared with a |
61 |
>>>> government authority/etc? |
62 |
>>> |
63 |
>>> It's not written anywhere, but I think we owe it to our developers |
64 |
>>> to |
65 |
>>> keep private information private. Without a sufficient reasoning |
66 |
>>> and/or |
67 |
>>> legal force, imo Gentoo should not comply without overwhelming |
68 |
>>> evidence |
69 |
>>> or legitimate legal threat to its incorporation status. We should |
70 |
>>> treat |
71 |
>>> private and internal information like it's valuable and important, |
72 |
>>> because it is. If developers can't share information with the |
73 |
>>> Foundation |
74 |
>>> and/or other developers and expect it to remain at least somewhat |
75 |
>>> safe, |
76 |
>>> then it may lower morale within the Project. |
77 |
>> |
78 |
>> Would we assume that the foundation would be hiring counsel or |
79 |
>> otherwise |
80 |
>> opposing such legal threats in court? If the foundation gets a |
81 |
>> subpoena |
82 |
>> or served with a search warrant, how much effort should the |
83 |
>> foundation |
84 |
>> put into fighting it? |
85 |
>> |
86 |
> That's a good question with a possibly-messy answer. It depends; if we |
87 |
> already have a lawyer on retainer or otherwise would go to bat for us |
88 |
> and has an understanding of such law, then sure, hire counsel. But |
89 |
> anything impacting the finances imo should go past the Foundation and |
90 |
> the treasurer first. If we lack budgeting, then depending on how bad |
91 |
> this request is we may ask for people to pitch in or something. I |
92 |
> doubt |
93 |
> anything like that would happen, however, so the most likely case is |
94 |
> subpoena for logs connected to a given IP address. If they have a |
95 |
> search |
96 |
> warrant, well, not much you can do about that then, huh? |
97 |
> |
98 |
> I'm not a lawyer, however, and don't know the safest approach that |
99 |
> also |
100 |
> protects the Foundation's members. I just don't believe in handing |
101 |
> things over when they're asked for without a damn good reason. |
102 |
>>>> 5. Do subjects of comrel action generally have a "right to face |
103 |
>>>> their |
104 |
>>>> accuser?" |
105 |
>>> |
106 |
>>> If the action is impacting their developer status or |
107 |
>>> public/internal |
108 |
>>> image, I believe the accuser should be willing to attach their |
109 |
>>> name to |
110 |
>>> their accusations. |
111 |
>> |
112 |
>> +1 to this. |
113 |
>> |
114 |
>> Furthermore I believe in principle that if you aren't willing to put |
115 |
>> your ass on the line to back your accusation, then your testimony is |
116 |
>> worthless. People are put under oath in court for a reason, and |
117 |
>> there |
118 |
>> are penalties for perjury. |
119 |
> I agree up to the "penalty for perjury" part. On one hand, there |
120 |
> should |
121 |
> be something that prevents people from making stuff up and generally |
122 |
> just killing peoples' time, but on the other, punishing someone for it |
123 |
> could result in them leaving the Foundation, possibly taking down |
124 |
> important things (forums, deliberately misconfigured mailserver, etc) |
125 |
> beforehand. |
126 |
> |
127 |
> There needs to be a balance. Maybe once comrel and/or the Council have |
128 |
> decided a matter is important, the push rights of all involved parties |
129 |
> is suspended to prevent in-fighting. Could be a stupid idea, I dunno. |
130 |
>> |
131 |
>>>> 6. What should be communicated about comrel actions, both |
132 |
>>>> proactively |
133 |
>>>> and when people inquire about them? |
134 |
>>> |
135 |
>>> Proactive announcements only necessary when they impact the |
136 |
>>> functioning |
137 |
>>> of Gentoo and have reason to be made public. Inquiries are a little |
138 |
>>> trickier, as we should strive for transparency internally, but keep |
139 |
>>> sensitive things from the general public. |
140 |
>>> |
141 |
>>>> I think there are a number of pros and cons to any approach we |
142 |
>>>> take, |
143 |
>>>> and it is possible for reasonable people to hold a different |
144 |
>>>> opinion |
145 |
>>>> on this topic. |
146 |
>>>> |
147 |
>>>> [snip] |
148 |
>>>> |
149 |
>>>> So, whether you think this is great or the worst drivel you've |
150 |
>>>> ever |
151 |
>>>> read, please do speak up... |
152 |
>>>> |
153 |
>>>> -- |
154 |
>>>> Rich |
155 |
>>>> |
156 |
>>>> |
157 |
>>> I was wondering who would get around to writing something like |
158 |
>>> this up |
159 |
>>> ever since that conversation about it a while back. :) |
160 |
>>> |
161 |
>>> -- |
162 |
>>> Daniel Campbell - Gentoo Developer |
163 |
>>> OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
164 |
>>> fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |
165 |
>> |
166 |
>> I'd also like to note for the record that the last known version of |
167 |
>> the |
168 |
>> developer quiz features a question about devrel (now comrel, +todo |
169 |
>> update it), so whoever wrote the quiz obviously feels that a good |
170 |
>> grounding in comrel procedures. |
171 |
>> |
172 |
>> I would very much like this noted for the record, and in addition to |
173 |
>> keeping the quiz updated with whatever happens in this discussion, |
174 |
>> I'd |
175 |
>> also like the current devmanual policy (cited in the quiz as a |
176 |
>> reference) involved as a subject in this discussion...does that |
177 |
>> make sense? |
178 |
> What devmanual policy are you referring to? |
179 |
|
180 |
The one saying that you should follow this sequence: |
181 |
|
182 |
1. Resolve informally |
183 |
|
184 |
2. Consult project lead |
185 |
|
186 |
3. Go to devrel (now comrel) only if you can't resolve it. |
187 |
|
188 |
Go directly to step 3 if the misconduct is intentional or habitual. |
189 |
|
190 |
I was told by a past mentor that "comrel doesn't want to get dragged |
191 |
into every catfight" |
192 |
|
193 |
If you need a direct citation of the devmanual section I can do some |
194 |
digging. |
195 |
|
196 |
>> |
197 |
>> We kinda do have documentation already, that is at the least being |
198 |
>> cited |
199 |
>> as a reference in the developer quiz...which I'm presently |
200 |
>> polishing my |
201 |
>> answers to in the wake of my pending recruitment. |
202 |
>> |
203 |
>> |
204 |
> Good luck on your journey to join us. :) |
205 |
> |
206 |
> -- |
207 |
> Daniel Campbell - Gentoo Developer |
208 |
> OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
209 |
> fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |
210 |
> |