<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi David,<br>
Thanks for starting this discussion. When you opened the discussion,
you very kindly offered to help set a Code of Conduct in place. How
do you suggest we move toward concluding the discussion and getting
a Code of Conduct in place?<br>
Do you have a timeframe in mind for this? I assume we should try to
make a CoC available for FOSS4G 2015 if they wish to make use of
one?<br>
<br>
Peter, thanks for you comments on proposed text.<br>
<br>
Is there anyone else with an interest in influencing the final text?
If so, please speak up.<br>
<br>
Which is the better version of a CoC?<br>
<br>
1. Prior foss4g: <a href="https://2015.foss4g-na.org/code-conduct">https://2015.foss4g-na.org/code-conduct</a><br>
2. OReilly: <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.oreilly.com/conferences/code-of-conduct.html">http://www.oreilly.com/conferences/code-of-conduct.html</a>
(copied below)<br>
3. My revised version (copied below)<br>
4. Something else<br>
<br>
<div class="moz-cite-prefix">On 19/01/2015 9:16 am, Cameron Shorter
wrote:<br>
</div>
<blockquote cite="mid:54BC30D8.5010705@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Hi David,<br>
I'm happy to move proposed CoC text across to a wiki. If
requested, I'll copy across now (within 48 hours), or can wait
till there has been further discussion.<br>
<br>
Also happy to expand the discussion to other lists, although I
expect the conference committee is probably the logical primary
point for discussion, as a CoC is most applicable to conferences.
The board would need to sign off on a CoC and should be invited to
comment.<br>
<br>
Re identifying what should be in a code of conduct. I've attempted
to start on that in the list of items I've attempted to address,
listed below.<br>
<br>
I have presented the draft CoC (below), as I find it is often
easier to start with a "straw man" which can be picked apart,
rather than talking vaguely in conceptual levels. However, I'm not
wedded to the text, and hope to see constructive criticism of the
ideas, text and structure. <br>
<br>
<div class="moz-cite-prefix">On 19/01/2015 3:46 am, David William
Bitner wrote:<br>
</div>
<blockquote
cite="mid:CAEqvsZsK3i2Q=5w2ZfPMbkQe1A6AGY9Lq19wBhenH5aY+QGCbQ@mail.gmail.com"
type="cite">I really want to thank everyone here for engaging in
this issue. I do appreciate all the different voices that have
contributed to this conversation -- they all certainly speak to
the diversity of thoughts and experiences that we already have
in this community.
<div><br>
</div>
<div>Cameron -- thank you very much for putting forward a first
draft of a potential CoC for us to use. Before drafting and
wordsmithing a CoC I want to step back and make sure we answer
a few questions that would certainly impact how a CoC gets
written. When we get to the point of drafting, we should
certainly do so on the wiki (or other trackable collaborative
medium) rather than in an email thread.</div>
<div><br>
</div>
<div>With some of the wording in this draft as well as seeing
the discussion from the last Board Meeting, is the conference
committee the correct venue for this discussion or should this
be at the Board level so that this applies to all OSGeo
activities (mailing lists, events, etc)? I am certain that
many of the same people would remain engaged in helping draft
a Code of Conduct either for the foundation as a whole or just
for our events, but this certainly impacts the scope and
wording required in a draft.</div>
<div><br>
</div>
<div>Many of the comments that I read as against having a CoC
seem to stem from people wondering what does a CoC solve.
Sadly, having a CoC does not "solve" anything. There will
still be issues. A CoC simply provides one tool for us to help
resolve those issues when they come up as well as providing a
proactive statement that we aim to be a welcoming and diverse
community to hopefully prevent some of those issues in the
first place. A CoC is not the end point of diversity
initiatives, but it is a very low hanging fruit to start with.
Other initiatives that I know have been tried that we should
continue to look at their effectiveness include author blind
public program review, scholarship initiatives, proactively
seeking out diversity in key notes, and many more things that
we haven't tried. </div>
</blockquote>
<br>
<div class="moz-cite-prefix">On 18/01/2015 2:33 pm, Cameron
Shorter wrote:<br>
</div>
<blockquote cite="mid:54BB29A6.1070407@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Following on from this email thread, I've drafted a proposed
Code of Conduct, where I've aimed to address:<br>
* Be concise (concise words get read more)<br>
* Cover key messages<br>
* Include an escalation process for dealing with both minor and
major issues<br>
* Ensure key terms are understood (in particular reference to
definition of sexualised images)<br>
* Couch in positive language<br>
<br>
<b>Tickbox version</b>:<br>
* I agree to act respectfully toward others in line with the
OSGeo Code of Conduct.<br>
<br>
<b>OSGeo Code of Conduct</b>:<br>
<br>
This Code of Conduct collates the collective values adopted by
our OSGeo community which baselines the behaviour we do and
don’t support to ensure OSGeo is a safe and productive
environment for all.<br>
<br>
We invite everyone to be respectful to all, regardless of race,
gender, age, sexual orientation, disability, physical
appearance, national origin, ethnicity, religion, or ideas. We
do not tolerate harassment of others in any form. Examples of
harassment include offensive comments, verbal threats or
demands, sexualized images in public spaces, intimidation,
stalking, harassing photography or recording, sustained
disruption of events, and unwelcome physical contact or sexual
attention. [1]<br>
<br>
We expect all participants to follow the Code of Conduct when
involved in OSGeo activities. This includes conferences, related
social events, and online forums. Participants violating this
Code of Conduct will be asked to desist and/or make amends. For
gross or continual violations, offenders may be expelled from
the event or forum without a refund, and/or banned from future
events or other forums.<br>
<br>
Participants are encouraged to bring any concerns to the
attention of event staff, the forum, forum leader, or OSGeo
Board. We thank all for helping keep OSGeo welcoming,
respectful, and friendly for all.<br>
<br>
[1] Examples of inappropriate sexualised environments are
described here: <a class="moz-txt-link-freetext"
href="https://www.humanrights.gov.au/publications/sexual-harassment-code-practice-what-sexual-harassment">https://www.humanrights.gov.au/publications/sexual-harassment-code-practice-what-sexual-harassment</a><br>
<br>
<div class="moz-cite-prefix">On 10/01/2015 9:59 pm, Cameron
Shorter wrote:<br>
</div>
<blockquote cite="mid:54B10604.9020501@gmail.com" type="cite">
Looking around at various Conference "Codes of Conduct", I
found the O'Reilly definition to be eloquently worded, and
less threatening to potential attendees. (Although I still
can't find a clear definition of "sexual images".)<br>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.oreilly.com/conferences/code-of-conduct.html">http://www.oreilly.com/conferences/code-of-conduct.html</a><br>
<br>
<meta charset="utf-8">
<h1 style="font-weight: normal; font-size: 24px; color:
rgb(51, 51, 51); margin: 10px 0px; font-family: Arial,
Verdana, Geneva, Helvetica, sans-serif; line-height: 1.3em;
font-style: normal; font-variant: normal; letter-spacing:
normal; orphans: auto; text-align: left; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">Code of Conduct</h1>
<p style="font-size: 12px; font-family: Arial, Helvetica,
sans-serif; color: rgb(51, 51, 51); font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: auto; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255);">At O'Reilly, we assume that most people are
intelligent and well-intended, and we're not inclined to
tell people what to do. However, we want every O'Reilly
conference to be a safe and productive environment for
everyone. To that end, this code of conduct spells out the
behavior we support and don't support at conferences. The
core of our approach is this:</p>
<p style="font-size: 12px; font-family: Arial, Helvetica,
sans-serif; color: rgb(51, 51, 51); font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: auto; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255);">We don't condone harassment or offensive
behavior, at our conference venues or anywhere. It's counter
to our company values. More importantly, it's counter to our
values as human beings.</p>
<p style="font-size: 12px; font-family: Arial, Helvetica,
sans-serif; color: rgb(51, 51, 51); font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: auto; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255);">We're voicing our strong, unequivocal support of
appropriate behavior by all participants at technical
events, including all O'Reilly conferences. We invite you to
help us make each O'Reilly conference a place that is
welcoming and respectful to all participants, regardless of
race, gender, age, sexual orientation, disability, physical
appearance, national origin, ethnicity, or religion. So that
everyone can focus on the conference itself, and the great
networking and community richness that happens when we get
together in person, we will not tolerate harassment of
conference participants in any form—in person or online.</p>
<p style="font-size: 12px; font-family: Arial, Helvetica,
sans-serif; color: rgb(51, 51, 51); font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: auto; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255);">Examples of harassment include offensive
comments, verbal threats or demands, sexualized images in
public spaces, intimidation, stalking, harassing photography
or recording, sustained disruption of sessions or events,
and unwelcome physical contact or sexual attention.</p>
<p style="font-size: 12px; font-family: Arial, Helvetica,
sans-serif; color: rgb(51, 51, 51); font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: auto; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255);">We expect all participants—attendees, speakers,
sponsors, and volunteers—to follow the Code of Conduct
during the conference. This includes conference-related
social events at off-site locations, and in related online
communities and social media. Participants asked to stop any
harassing behavior are expected to comply immediately.
Conference participants violating this Code of Conduct may
be expelled from the conference without a refund, and/or
banned from future O'Reilly events, at the discretion of
O'Reilly Media.</p>
<p style="font-size: 12px; font-family: Arial, Helvetica,
sans-serif; color: rgb(51, 51, 51); font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: auto; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255);">Please bring any concerns to the immediate
attention of the event staff, or contact our VP of
Conferences, Gina Blaber at<span
class="Apple-converted-space"> </span><a
moz-do-not-send="true" href="mailto:gina@oreilly.com"
style="text-decoration: none; color: rgb(32, 124, 193);">gina@oreilly.com</a>.
We thank our participants for your help in keeping the event
welcoming, respectful, and friendly to all participants.</p>
<p style="font-size: 12px; font-family: Arial, Helvetica,
sans-serif; color: rgb(51, 51, 51); font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: auto; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255);">Read the<span class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="http://radar.oreilly.com/2011/07/sexual-harassment-at-technical.html"
style="text-decoration: none; color: rgb(32, 124, 193);">blog
post by Tim O'Reilly</a><span
class="Apple-converted-space"> </span>that is the basis of
our functional code of conduct for all O'Reilly conferences.</p>
<p style="font-size: 12px; font-family: Arial, Helvetica,
sans-serif; color: rgb(51, 51, 51); font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: auto; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255);">Thanks to the<span class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="http://2014.leanstartup.co/code-of-conduct/"
style="text-decoration: none; color: rgb(32, 124, 193);">Lean
Startup</a><span class="Apple-converted-space"> </span>folks
and the<span class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="http://jsconf.com/codeofconduct.html"
style="text-decoration: none; color: rgb(32, 124, 193);">jsconf.us</a><span
class="Apple-converted-space"> </span>folks, whose Codes
of Conduct inspired some changes to our own.</p>
</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 moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.lisasoft.com">www.lisasoft.com</a>, F +61 2 9009 5099</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 moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.lisasoft.com">www.lisasoft.com</a>, F +61 2 9009 5099</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>