<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Embracing and extending upon David's comments,<br>
<br>
Another reason for keeping a CoC committee small it is less
threatening for a victim to approach a single known person than many
people within a committee. It is a trust thing.<br>
<br>
The reporter should have full control on how far they wish their
report to go. If a reporter wishes to approach just one member of
the CoC committee and requests other committee or board members not
be notified, that should be ok.<br>
The committee member can then explain options, which typically would
include:<br>
<br>
1. A discrete mention to the perpetrator that it has been noticed
their behaviour was considered by someone as inappropriate and maybe
you'd like to think about that in future.<br>
<br>
2. Disciplinary action, which would first require a level of
discussion amongst the committee, and also provide an opportunity
for the accused to defend themselves. (I suggest follow convention
of modern legal systems which are based on assumption of innocence
until proven guilty). <br>
<br>
3. Something in between 1 and 2.<br>
<br>
--<br>
<br>
With regards to structure and running of the CoC Committee, I
suggest the committee should fit in with the official, ARTICLE VI
Project Steering Committees, from OSGeo By Laws:<br>
<a class="moz-txt-link-freetext" href="http://www.osgeo.org/content/foundation/incorporation/bylaws.html">http://www.osgeo.org/content/foundation/incorporation/bylaws.html</a><br>
<br>
(This includes OSGeo Board oversight, which I think might address
some of the points from the board that Jeff describes below? In
particular, the board would be able to appoint people onto the CoC
Committee.)<br>
<br>
Warm regards, <br>
<br>
Cameron<br>
<br>
<div class="moz-cite-prefix">On 25/07/2015 4:11 am, David William
Bitner wrote:<br>
</div>
<blockquote
cite="mid:CAEqvsZvzFVBrUdsxC9Q18cj1FSYtzBy4deH1o3DyzB5pd4HLQg@mail.gmail.com"
type="cite">
<div dir="ltr">Jeff & Board members,
<div><br>
</div>
<div>Thanks for feedback. A few of my thoughts with regards to
the clarifications from the Board.</div>
<div><br>
</div>
<div>I think that it is critical that the <i>front line</i> (ie
those who we are setting up to be on the receiving end of
potential incidents) be a very limited group of people. While
with the structure being proposed in the clarification allows
for the ultimate decision of any enforcement to be made by the
board, it does not allow for the committee to privately
collect (and potentially anonymize) any reports. We still need
to have a very small group of people who are entrusted to be
that front line. We also need to allow for the case where a
CoC committee member OR a board member may be on the receiving
end of a complaint. If we maintain a separate private (perhaps
subset or executive committee of the CoC comm) list for
reporting of incidents, then if there was ever a complaint
about a CoC comm member, someone could submit directly to the
Board-priv list, while if there was a complaint about a Board
member they could submit to the CoC-priv.</div>
<div><br>
</div>
<div>Having a coc-priv list with a very limited number of people
is absolutely critical, in my opinion, to making this work
whether any enforcement decisions are made by CoC comm or the
Board.</div>
<div><br>
</div>
<div>David</div>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
****<br>
- Board appreciates proposed CoC committee<br>
- 2 points must be clarified:<br>
1) changes needed to structure:<br>
- there should be no limitation on # of members
(as other committees)<br>
- need to name chair of committee<br>
- should propose/vote in new members<br>
2) changes needed to scope:<br>
- committee reports about CoC incidents to
privately (board-priv mailing list)<br>
- actions are only taken by the OSGeo Board<br>
****<br>
<br>
</blockquote>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Board mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Board@lists.osgeo.org">Board@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/board">http://lists.osgeo.org/mailman/listinfo/board</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter,
Software and Data Solutions Manager
LISAsoft
Suite 112, Jones Bay Wharf,
26 - 32 Pirrama Rd, Pyrmont NSW 2009
P +61 2 9009 5000, W <a class="moz-txt-link-abbreviated" href="http://www.lisasoft.com">www.lisasoft.com</a>, F +61 2 9009 5099</pre>
</body>
</html>