<div dir="ltr"><div>Hi all --</div><div><br></div><div>See Cameron's note below re: the current draft OSGeo CoC and some options for implementation.</div><div><br></div><div>Camille Acey and I will be working on this, and if other folks are interested in joining in, it would be great to move this forward.</div><div><br></div><div>If interested, ping me off list.</div><div><br></div><div>cheers -</div><div>-kristin</div><div><br></div><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 13, 2015 at 1:55 PM, Cameron Shorter <span dir="ltr"><<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi Kristin,<br>
Thanks for your review and tweaks.<br>
The CoC as it stands does have a light weight implementation guide,
and escalation process. This hopefully should catch 95% of
scenarios.<br>
<br>
One think I liked about the Geek Feminism Wiki was their internal
guidelines for conference staff implementing an anti-harassment
policy.<br>
<a href="http://geekfeminism.wikia.com/wiki/Conference_anti-harassment_policy" target="_blank">http://geekfeminism.wikia.com/wiki/Conference_anti-harassment_policy</a><br>
<br>
If you are inspired, and think it appropriate, you might want to
customise it to fit within the FOSS4G Handbook format:<br>
<a href="http://wiki.osgeo.org/wiki/FOSS4G_Handbook" target="_blank">http://wiki.osgeo.org/wiki/FOSS4G_Handbook</a><br>
<br>
Warm regards,<br>
Cameron<div><div class="h5"><br>
<br>
<div>On 14/05/2015 4:10 am, Camille Acey
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div style="font-family:georgia,serif">Yes,
Kristin, I agree, and I am definitely on board for the (likely
more involved) question of implementation. Keep me posted! <br>
<br>
</div>
<div style="font-family:georgia,serif">Thanks
all,<br>
</div>
<div style="font-family:georgia,serif">Camille<br>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr"><span>
<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><font size="2"><span style="font-family:georgia,serif"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-weight:bold">Camille
E. Acey</span></span></font></p>
<font size="2"><span style="font-family:georgia,serif">
</span></font>
<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="font-family:georgia,serif"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent">Manager,
Customer Development and Partnerships|
Boundless</span></span></p>
<font size="2"><span style="font-family:georgia,serif">
</span></font>
<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="font-family:georgia,serif"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent"><a href="mailto:camille@boundlessgeo.com" target="_blank">camille@boundlessgeo.com</a>
<br>
</span></span></p>
<p style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="font-family:georgia,serif"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent">T:
<a href="tel:%2B1%20917.460.7197" value="+19174607197" target="_blank">+1 917.460.7197</a>|M: <a href="tel:%2B1%20347.267.2016" value="+13472672016" target="_blank">+1 347.267.2016</a>| Skype:
camilleacey</span></span></p>
<p style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="font-family:georgia,serif"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent">New
York, NY - USA<br>
</span></span></p>
<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="font-family:georgia,serif"><a href="https://twitter.com/boundlessgeo" style="text-decoration:none" target="_blank"><span style="color:rgb(0,167,141);background-color:transparent;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap"><font size="2">@boundlessgeo</font><br>
<br>
</span></a></span></p>
<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><img src="http://boundlessgeo.com/wp-content/uploads/files/boundless_sig.png"><br>
<span style="font-family:georgia,serif"><a href="https://twitter.com/boundlessgeo" style="text-decoration:none" target="_blank"><span style="color:rgb(0,167,141);background-color:transparent;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap"></span></a></span><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent"></span></p>
</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Wed, May 13, 2015 at 2:05 PM,
Kristin Bott <span dir="ltr"><<a href="mailto:bottk@reed.edu" target="_blank">bottk@reed.edu</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Cameron,
<div><br>
</div>
<div>Some minor edits to the language under "Application"
-- <a href="http://wiki.osgeo.org/wiki/Code_Of_Conduct#Application" target="_blank">http://wiki.osgeo.org/wiki/Code_Of_Conduct#Application</a></div>
<div><br>
</div>
<div>I assume that the next step in the CoC discussion,
after the CoC is approved, is how to implement the CoC.
(Methods for dealing with violations -- are those in the
hands of the project admins / event organizers, is there
an OSGeo-wide involvement, etc...) </div>
<div><br>
</div>
<div>I imagine that hashing out those types of details
will be a fairly involved process -- step one, of
course, is to get the CoC approved. Thanks again for all
your work on this.</div>
<span><font color="#888888">
<div><br>
</div>
<div>-kb</div>
<div><br>
</div>
</font></span></div>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, May 12, 2015 at 2:31
PM, Cameron Shorter <span dir="ltr"><<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Following
on from the IRC meeting today,<br>
It was agreed by all participants that the
proposed Code of Conduct should be adopted, with
the following changes:<br>
* A statement explaining how the CoC should be
applied, as suggested by Kristin Bott (below)<br>
* Remove negative words from the Diversity
Statement, as suggested by Jeff McKenna<br>
* Move to a Code of Conduct URL (instead of
Diversity URL)<br>
<br>
I've addressed each of these into <a href="http://wiki.osgeo.org/wiki/Code_Of_Conduct" target="_blank">http://wiki.osgeo.org/wiki/Code_Of_Conduct</a><br>
<br>
Kristin,<br>
Your suggested has been added as:<br>
<a href="http://wiki.osgeo.org/wiki/Code_Of_Conduct#Application" target="_blank">http://wiki.osgeo.org/wiki/Code_Of_Conduct#Application</a><br>
Can you please confirm that this addresses what
you were thinking, or suggest alternative
wording.<br>
<br>
Are there any further comments or suggestions
before we ask the board to endorse it?<br>
<br>
Warm regards,<br>
Cameron<br>
<br>
<div>On 13/05/2015 3:56 am, Kristin Bott wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi all,
<div><br>
</div>
<div>Apologies for my slow response --
Cameron, this looks good to me; thank you
for the effort and time it took to put
this together, including reaching out to a
number of different people and
incorporating their perspectives.</div>
<div><br>
</div>
<div>I won't be able to make the related
meeting, unfortunately. Thanks to all who
are contributing to this effort.</div>
<div><br>
</div>
<div>I note that there is no central /
suggested / mandated way to publicize the
CoC for a given event or group; this puts
the onus on individual organizers / LOCs /
etc to make the CoC visible and enforced.
I look forward to seeing this (or a
revision thereof) CoC featured as part of
upcoming OSGeo events.</div>
<div><br>
</div>
<div>cheers - </div>
<div>- kristin</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, May 10,
2015 at 8:07 AM, Eli Adam <span dir="ltr"><<a href="mailto:eadam@co.lincoln.or.us" target="_blank">eadam@co.lincoln.or.us</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Hi Cameron and all, </p>
<span>
<p dir="ltr">On May 10, 2015 3:44 AM,
"Cameron Shorter" <<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>>
wrote:<br>
><br>
> Members of the conference
committee,</p>
</span>
<p dir="ltr">Or anyone participating
(but yes especially conference
committee members)</p>
<span>
<p dir="ltr">> I haven't heard
anything positive or negative about
the proposed OSGeo Code of Conduct
[2], and only a couple of people
planning to attend the IRC meeting
to discuss it.<br>
><br>
> I'm hoping that is because
interested people have read it,
think it is acceptable, and don't
have anything else to add?<br>
></p>
</span>
<p dir="ltr">Yes for me but always
interested in hearing from others.</p>
<span>
<p dir="ltr">> If you have read the
Code of Conduct, and think it is
suitable to be applied to future
OSGeo projects and FOSS4G events
then please speak up with your
support or recommended suggestions
for changes.</p>
</span>
<p dir="ltr">I think the we did a good
job sorting through other comparable
codes of conduct and finding where the
best aspects came together. Cameron
also did a lot to keep the
conversation going and not getting too
distracted with minor details. Cameron
also did a lot to try and incorporate
various disparate views which is not
an easy task. Thanks for that.</p>
<p dir="ltr">Best regards, Eli<br>
<br>
</p>
<p dir="ltr"><span>><br>
> Thanks in advance, Cameron<br>
><br>
><br>
><br>
> On 2/05/2015 9:03 am, Cameron
Shorter wrote:<br>
>><br>
>> All,<br>
>> There has been a lot of
valuable discussion around the
development of an OSGeo Code of
Conduct / Diversity Statement
earlier this year, mainly on the
OSGeo Conference and OSGeo Board
email lists.<br>
>><br>
>> I've researched a number of
prior Code of Conduct and Diversity
Statements and combined with OSGeo
participant comments to build a
draft OSGeo Code of Conduct, along
with references to prior material,
comments, and a list of goals we
want to achieve from such a
document.<br>
>><br>
>> I propose that we aim to
finalise a 1.0 version of an OSGeo
Code of Conduct/Diversity Statement
and provide a recommendation for the
next OSGeo board meeting on 21 May
2015.<br>
>><br>
>> I've set up a Doodle Pole
for an IRC meeting aimed at
finalising this Code of Conduct [1]<br>
>><br>
>> If you would like to
contribute, please:<br>
>> 1. Read the draft code of
conduct [2]<br>
>> 2. Provide comments either
in the comments section on the wiki
[3] or on the conference email list
[4]<br>
>> 3. Register for [1] and
then attend the IRC meeting [5]<br>
>><br>
>> [1] <a href="http://doodle.com/k8bmu6e8kntht462" target="_blank">http://doodle.com/k8bmu6e8kntht462</a><br>
>> [2] <a href="http://wiki.osgeo.org/wiki/Diversity" target="_blank">http://wiki.osgeo.org/wiki/Diversity</a><br>
>> [3] <a href="http://wiki.osgeo.org/wiki/Diversity#Community_Comments" target="_blank">http://wiki.osgeo.org/wiki/Diversity#Community_Comments</a><br>
>> [4] <a href="http://lists.osgeo.org/mailman/listinfo/conference_dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
>> [5] <a>irc://</a><a href="http://freenode.net#osgeo" target="_blank">freenode.net#osgeo</a><br>
>><br>
>> Warm regards,<br>
><br>
><br>
> -- <br>
> Cameron Shorter,<br>
> Software and Data Solutions
Manager<br>
> LISAsoft<br>
> Suite 112, Jones Bay Wharf,<br>
> 26 - 32 Pirrama Rd, Pyrmont NSW
2009<br>
><br>
> P <a href="tel:%2B61%202%209009%205000" value="+61290095000" target="_blank">+61 2 9009 5000</a>,
W <a href="http://www.lisasoft.com" target="_blank">www.lisasoft.com</a>,
F <a href="tel:%2B61%202%209009%205099" value="+61290095099" target="_blank">+61 2 9009 5099</a><br>
><br>
><br>
</span> >
_______________________________________________<br>
> Conference_dev mailing list<br>
> <a href="mailto:Conference_dev@lists.osgeo.org" target="_blank">Conference_dev@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/conference_dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
</p>
<br>
_______________________________________________<br>
Conference_dev mailing list<br>
<a href="mailto:Conference_dev@lists.osgeo.org" target="_blank">Conference_dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/conference_dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
</blockquote>
</div>
<br>
<span><font color="#888888"> </font></span></div>
<span><font color="#888888"> </font></span></blockquote>
<span><font color="#888888"> <br>
<pre cols="72">--
Cameron Shorter,
Software and Data Solutions Manager
LISAsoft
Suite 112, Jones Bay Wharf,
26 - 32 Pirrama Rd, Pyrmont NSW 2009
P <a href="tel:%2B61%202%209009%205000" value="+61290095000" target="_blank">+61 2 9009 5000</a>, W <a href="http://www.lisasoft.com" target="_blank">www.lisasoft.com</a>, F <a href="tel:%2B61%202%209009%205099" value="+61290095099" target="_blank">+61 2 9009 5099</a></pre>
</font></span></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Conference_dev mailing list<br>
<a href="mailto:Conference_dev@lists.osgeo.org" target="_blank">Conference_dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/conference_dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre cols="72">--
Cameron Shorter,
Software and Data Solutions Manager
LISAsoft
Suite 112, Jones Bay Wharf,
26 - 32 Pirrama Rd, Pyrmont NSW 2009
P <a href="tel:%2B61%202%209009%205000" value="+61290095000" target="_blank">+61 2 9009 5000</a>, W <a href="http://www.lisasoft.com" target="_blank">www.lisasoft.com</a>, F <a href="tel:%2B61%202%209009%205099" value="+61290095099" target="_blank">+61 2 9009 5099</a></pre>
</div></div></div>
</blockquote></div><br></div></div>