<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I'm happy to contribute toward developing an OSGeo Code of Conduct
or Diversity Statement if the board would welcome and accept
community involvement in developing such a document.<br>
<br>
I admit that I've felt disenfranchised and that input from the
conference committee into an OSGeo policy would not be welcomed,
based on the OSGeo board pushing toward developing a 2nd Diversity
Statement, and encouraging the conference committee to develop their
own.<br>
<br>
I'd be happy to build from Jeff's Diversity Statement, if the board
would welcome input (once the OSGeo wiki page is working again - it
seems I can't log in and edit).<br>
If the board is set on breaking away from the conference committee,
and want to develop their diversity statement in isolation, then
please say so, and I'll spend my time elsewhere.<br>
<br>
Regards, Cameron<br>
<br>
<div class="moz-cite-prefix">On 5/03/2015 9:50 pm, Bart van den
Eijnden wrote:<br>
</div>
<blockquote cite="mid:96F4F089-9FA4-4317-951E-C9F07F1B9C70@osgis.nl"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
I can understand the confusion on the conference committee to be
honest.
<div class=""><br class="">
</div>
<div class="">They draft up something, the board “takes” over with
their own diversity statement, and then the whole process stops.
We need to decide who is in charge here. I’d personally like to
see the conference committee take charge but I know this is
probably not the consensus.</div>
<div class=""><br class="">
</div>
<div class="">Best regards,</div>
<div class="">Bart</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 05 Mar 2015, at 11:26, Jachym Cepicky <<a
moz-do-not-send="true"
href="mailto:jachym.cepicky@gmail.com" class="">jachym.cepicky@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">Jeff is right. "Waiting and
seeing" does not move things a lot, it's just by "doing"
(doocracy)<br class="">
<br class="">
<div class="">Thanks for your contribution<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">J</div>
</div>
<br class="">
<div class="gmail_quote">čt 5. 3. 2015 v 4:22 odesílatel
David William Bitner <<a moz-do-not-send="true"
href="mailto:bitner@dbspatial.com" class="">bitner@dbspatial.com</a>>
napsal:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr" class="">+10000000000</p>
<div class="gmail_quote">On Mar 4, 2015 8:45 PM,
"David Percy" <<a moz-do-not-send="true"
href="mailto:percyd@pdx.edu" target="_blank"
class="">percyd@pdx.edu</a>> wrote:<br
type="attribution" class="">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr" class="">Now that I'm a charter
member I can happily nominate and vote for Eli
for the board, he would make great
contributions, in addition to what he already
does! <br class="">
Thanks for the suggestion, Jeff!<br class="">
:-)</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Wed, Mar 4, 2015 at
5:29 PM, Jeff McKenna <span dir="ltr"
class=""><<a moz-do-not-send="true"
href="mailto:jmckenna@gatewaygeomatics.com"
target="_blank" class="">jmckenna@gatewaygeomatics.com</a>></span>
wrote:<br class="">
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">Eli,<br
class="">
<br class="">
I am not sure of the purpose of this
message. If you decide to 'wait and see' in
this world, well nothing will ever get done.<br
class="">
<br class="">
Everyone is working hard and doing their
best. My last message to the Conference
Committee was to yes put the proposed text
in a wiki and bring it to the Board, or, as
I said in my message that if you cannot do
that, then you can edit the wiki directly
that I proposed to the Board[1];
Unfortunately since I said that nothing has
happened (the ball was left on the floor).<br
class="">
<br class="">
So I agree, if nothing else happens, the
OSGeo Board will move forward with the
proposed text in the wiki.<br class="">
<br class="">
Again, yes, please do put your ideas in the
wiki and propose it to the Board.<br
class="">
<br class="">
In terms of tomorrow's meeting, we have some
huge topics to decide as a Board, so that
should give you time to lead the changes on
the wiki. And please next time start the
discussions a little earlier than the night
before the Board meeting.<br class="">
<br class="">
If I can leave you tonight with a final
thought, it would be: maybe you should
consider joining the OSGeo Board, in the
next election.<br class="">
<br class="">
Thanks,<br class="">
<br class="">
-jeff
<div class="">
<div class=""><br class="">
<br class="">
<br class="">
<br class="">
On 2015-03-04 9:00 PM, Eli Adam wrote:<br
class="">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
Hi Camille and all,<br class="">
<br class="">
Thanks to everyone for contributing to
what could become an OSGeo Code<br
class="">
of Conduct. I appreciate that
knowledgeable people with relevant<br
class="">
backgrounds and experiences have been
helping; thanks.<br class="">
<br class="">
Here is a short recap of what I know
of OSGeo CoC and my opinions of<br
class="">
the conversation moving forward.<br
class="">
<br class="">
The OSGeo Board deferred CoC to the
conference committee over four<br
class="">
years ago in 2010 [0], where it was
discussed and not pursued for<br
class="">
development or adoption [1].<br
class="">
<br class="">
Despite no formal OSGeo policy, over
the past several years FOSS4G<br
class="">
LOCs of both the main international
conference and some regional<br
class="">
conferences have used CoCs and seem to
recognize it as worthwhile.<br
class="">
Some OSGeo Projects (QGIS) have
adopted CoCs too.<br class="">
<br class="">
In October 2014, the OSGeo Board votes
to develop a CoC [2].<br class="">
<br class="">
January 2015, lots of CoC debate and
drafting here on the conference<br
class="">
list. Thanks to Cameron for trying to
coordinate various ideas into a<br
class="">
coherent manner, including many
participants and accessing available<br
class="">
resources relevant to CoCs. Cameron's
work helps distill everything<br
class="">
into something appropriate for voting
in a Board meeting. Thanks to<br
class="">
everyone for participating and
contributing.<br class="">
<br class="">
February, the OSGeo board takes up a
Diversity Statement [3] and on<br
class="">
the wiki [4]. Some aspects of it are
similar to a CoC.<br class="">
<br class="">
My opinion of moving the conversation
forward is to "wait and see"<br
class="">
what the OSGeo Board does. The item
has fallen into the "Items from<br
class="">
past meetings" section [5], which is
rarely reached due to lack of<br
class="">
time. Depending on what the Board
does (or doesn't do), it makes<br
class="">
sense for the conference committee to
take up the issue again in an<br
class="">
appropriate scope (whole foundation or
international FOSS4G), perhaps<br
class="">
putting something like the proposed
text Cameron put together on a<br
class="">
Board agenda for a vote. My opinion
is that the conversation has<br
class="">
stopped. Tomorrow's Board meeting [5]
should give some indication of<br
class="">
that.<br class="">
<br class="">
[0] <a moz-do-not-send="true"
href="http://lists.osgeo.org/pipermail/board/2010-November/008511.html"
target="_blank" class="">http://lists.osgeo.org/pipermail/board/2010-November/008511.html</a><br
class="">
[1] <a moz-do-not-send="true"
href="http://lists.osgeo.org/pipermail/conference_dev/2010-November/001235.html"
target="_blank" class="">http://lists.osgeo.org/pipermail/conference_dev/2010-November/001235.html</a><br
class="">
[2] <a moz-do-not-send="true"
href="http://wiki.osgeo.org/wiki/Board_Meeting_2014-10-16"
target="_blank" class="">http://wiki.osgeo.org/wiki/Board_Meeting_2014-10-16</a><br
class="">
[3] <a moz-do-not-send="true"
href="http://lists.osgeo.org/pipermail/board/2015-February/012456.html"
target="_blank" class="">http://lists.osgeo.org/pipermail/board/2015-February/012456.html</a><br
class="">
[4] <a moz-do-not-send="true"
href="http://wiki.osgeo.org/wiki/Diversity"
target="_blank" class="">http://wiki.osgeo.org/wiki/Diversity</a><br
class="">
[5] <a moz-do-not-send="true"
href="http://wiki.osgeo.org/wiki/Board_Meeting_2015-03-05"
target="_blank" class="">http://wiki.osgeo.org/wiki/Board_Meeting_2015-03-05</a><br
class="">
<br class="">
Thanks for everyone contributing and
best regards, Eli<br class="">
<br class="">
<br class="">
<br class="">
On Mon, Feb 9, 2015 at 6:02 AM,
Camille Acey <<a
moz-do-not-send="true"
href="mailto:camille@boundlessgeo.com"
target="_blank" class="">camille@boundlessgeo.com</a>>
wrote:<br class="">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<br class="">
I agree with this statement and
would be interested to hear how this
conversation is moving forward.<br
class="">
<br class="">
Thanks,<br class="">
Camille<br class="">
<br class="">
Camille E. Acey<br class="">
<br class="">
Manager, Customer Development and
Partnerships| Boundless<br class="">
<br class="">
<a moz-do-not-send="true"
href="mailto:camille@boundlessgeo.com"
target="_blank" class="">camille@boundlessgeo.com</a><br
class="">
<br class="">
T: <a moz-do-not-send="true"
href="tel:%2B1%20917.460.7197"
value="+19174607197"
target="_blank" class="">+1
917.460.7197</a>|M: <a
moz-do-not-send="true"
href="tel:%2B1%20347.267.2016"
value="+13472672016"
target="_blank" class="">+1
347.267.2016</a>| Skype:
camilleacey<br class="">
<br class="">
New York, NY - USA<br class="">
<br class="">
@boundlessgeo<br class="">
<br class="">
<br class="">
<br class="">
On Wed, Feb 4, 2015 at 3:31 PM,
Cameron Shorter <<a
moz-do-not-send="true"
href="mailto:cameron.shorter@gmail.com"
target="_blank" class="">cameron.shorter@gmail.com</a>>
wrote:<br class="">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<br class="">
Hi Jeff, all,<br class="">
<br class="">
Thanks for invitation to the board
meeting [1] to discuss a code of
conduct. Unfortunately I can't
make it, my enthusiasm for OSGeo
wains at 2am (which is the
timeslot for me). Maybe there are
others who have been involved in
the conference email list discuss
who will join in.<br class="">
<br class="">
So I'll add my comments in
advance:<br class="">
<br class="">
1. I strongly believe there should
be ONLY ONE OSGeo endorsed and
recommended Code of Conduct /
Diversity Statement. It makes it
simpler and hence easier to apply.<br
class="">
<br class="">
2. Following on from 1), other
OSGeo communities should be
invited to contribute to the Code
of Conduct / Diversity Statement.
In particular, the conference
committee should be invited to
contribute.<br class="">
<br class="">
4. I suggest building on prior
best practice documentation rather
than writing our own from scratch.
Many of these prior documents have
already gone through multiple
review cycles and it makes sense
to build upon that expertise.
There have been a number of
referenced best practice documents
referenced. Carl has just
suggested an OGC reference which
is good (and built upon prior
material).<br class="">
<br class="">
6. There has been valuable and
insightful suggestions on this
topic already on the conference
thread. I suggest building upon
those comments as well.<br
class="">
<br class="">
5. David William Bitner valuably
suggested documenting what we want
to achieve, then use that as a
basis for writing. (see comment
below). I suggest what we want
such a document to cover:<br
class="">
<br class="">
* Recognise that OSGeo has a
DIVERSE community<br class="">
* Set expectation that people
should act RESPECTFULLY toward
each other<br class="">
* Outline a process for
RECOGNISING, REPORTING and
ADDRESSING incidents which can be
referenced by those dealing with
incidents. (Dealing with incidents
is often a hostile situation, and
having a process to reference can
greatly help the people doing the
hard job of mediating.)<br
class="">
<br class="">
6. While I like the concept of the
word "Diversity", I think it is
currently confusing in "Diversity
Statement" as a heading.
"Diversity" is broad in meaning,
and can mean Diversity in software
choice, food selection, processes
followed, etc, etc. We should
select a heading relevant to what
is being described - which is an
expectation of "behaviour" or
"conduct". "Code of Conduct",
Principles of Conduct" better
describe what should be covered.<br
class="">
<br class="">
[1] <a moz-do-not-send="true"
href="http://wiki.osgeo.org/wiki/Board_Meeting_2015-02-05"
target="_blank" class="">http://wiki.osgeo.org/wiki/Board_Meeting_2015-02-05</a><br
class="">
<br class="">
On 5/02/2015 3:51 am, Carl Reed
wrote:<br class="">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<br class="">
Venka et. al.<br class="">
<br class="">
You might be interested in the
OGC Principals of Conduct which
is itself based on the IETF Code
of Conduct.<br class="">
<br class="">
<a moz-do-not-send="true"
href="http://www.opengeospatial.org/ogc/policies/conduct"
target="_blank" class="">http://www.opengeospatial.org/ogc/policies/conduct</a><br
class="">
<br class="">
Perhaps this might be helpful.<br
class="">
<br class="">
Regards<br class="">
<br class="">
Carl Reed<br class="">
<br class="">
<br class="">
-----Original Message----- From:
Venkatesh Raghavan<br class="">
Sent: Wednesday, February 04,
2015 6:03 AM<br class="">
To: <a moz-do-not-send="true"
href="mailto:board@lists.osgeo.org"
target="_blank" class="">board@lists.osgeo.org</a><br
class="">
Subject: Re: [Board] Proposed
text for an OSGeo Code of
Conduct<br class="">
<br class="">
On 2015/02/04 21:45, Jeff
McKenna wrote:<br class="">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<br class="">
Yes I agree, which is why I
believe the OSGeo Foundation
needs a very simple Diversity
statement, that says everyone
can expect an open and
respectful environment (see my
original draft at <a
moz-do-not-send="true"
href="http://wiki.osgeo.org/index.php?title=Diversity&oldid=81445"
target="_blank" class="">http://wiki.osgeo.org/index.php?title=Diversity&oldid=81445</a>).
Notice how there is no mention
of policing etc in that
version. Your discussions on a
Code of Conduct for FOSS4G are
very separate in my opinion.
In any case, the OSGeo Board
will discuss this in
tomorrow's meeting if you
would like to attend and share
your thoughts, all are welcome
(<a moz-do-not-send="true"
href="http://wiki.osgeo.org/wiki/Board_Meeting_2015-02-05"
target="_blank" class="">http://wiki.osgeo.org/wiki/Board_Meeting_2015-02-05</a>).<br
class="">
</blockquote>
<br class="">
<br class="">
I agree that any statement by
OSGeo foundation in general and<br
class="">
statements pertaining to events
produced/hosted/presented by<br
class="">
OSGeo Foundation should be kept
separate.<br class="">
<br class="">
Venka<br class="">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<br class="">
<br class="">
-jeff<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
On 2015-02-04 6:28 AM, Cameron
Shorter wrote:<br class="">
<blockquote
class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<br class="">
I'm expanding this Code of
Conduct thread to include
the OSGeo Board,<br class="">
who are proposing an
alternative Code of Conduct:<br
class="">
<a moz-do-not-send="true"
href="http://wiki.osgeo.org/wiki/Diversity"
target="_blank" class="">http://wiki.osgeo.org/wiki/Diversity</a><br
class="">
<br class="">
I strongly suggest that we
should try to have only one
OSGeo Code of<br class="">
Conduct / Diversity
Statement as it reduces
confusion and is easier to<br
class="">
implement. There is beauty
in simplicity. Jeff are you
suggesting that<br class="">
we have two? (One for
conferences, and another for
OSGeo?)<br class="">
<br class="">
On 3/02/2015 7:09 am, Jeff
McKenna wrote:<br class="">
<blockquote
class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<br class="">
I would like Board members
to edit that wiki page
directly over the<br
class="">
next few days, and then we
can discuss this at the
Board meeting on<br
class="">
Thursday. My goal is to
have a new "/diversity"
page linked from the<br
class="">
main <a
moz-do-not-send="true"
href="http://osgeo.org/"
target="_blank" class="">osgeo.org</a>
site.<br class="">
</blockquote>
<br class="">
<br class="">
Jeff, I assume that since
you have proposed an
alternative text, that<br
class="">
you have issue with the
prior proposed text? (as in
the bottom of this<br
class="">
email thread). What do you
see to be the limitations of
the prior<br class="">
proposed text?<br class="">
<br class="">
Also, in your email, are you
requesting that only board
members edit the<br class="">
Diversity statement, or is
it open to other community
members to edit as<br
class="">
well?<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
On 4/02/2015 7:16 am, Bart
van den Eijnden wrote:<br
class="">
<blockquote
class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<br class="">
Interesting, MapZen will
only sponsor events which
have a strong COC<br
class="">
in place:<br class="">
<br class="">
<a moz-do-not-send="true"
href="https://mapzen.com/blog/mapzen-code-of-conduct" target="_blank"
class="">https://mapzen.com/blog/mapzen-code-of-conduct</a><br
class="">
<br class="">
Best regards,<br class="">
Bart<br class="">
<br class="">
<blockquote
class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px
#ccc
solid;padding-left:1ex">
On 25 Jan 2015, at
22:10, Cameron Shorter
<<a
moz-do-not-send="true"
href="mailto:cameron.shorter@gmail.com" target="_blank" class="">cameron.shorter@gmail.com</a><br
class="">
<mailto:<a
moz-do-not-send="true"
href="mailto:cameron.shorter@gmail.com" target="_blank" class="">cameron.shorter@gmail.com</a>>>
wrote:<br class="">
<br class="">
Thanks Eli,<br class="">
I like your list of
characteristics. I'd
add:<br class="">
<br class="">
* Have a CoC in the
first place, which
breaks down to:<br
class="">
** Ensure conferences
remember / realise that
a CoC should be in<br
class="">
place. (Add it to our
cookbook [1] and bid
process)<br class="">
** Make it easy to apply
a CoC by referencing an
existing document.<br
class="">
(Complete this
discussion and provide a
best practice document
that<br class="">
can be referenced).<br
class="">
<br class="">
I acknowledge your point
re over-doing sexualized
images discussion.<br
class="">
<br class="">
I like the qgis CoC, and
suggest that if we can
make adding a CoC<br
class="">
easy (by providing
generic text), then we
should add having a CoC
a<br class="">
requirement for OSGeo
graduation. I've added a
placemarker into the<br
class="">
proposed text for the
next OSGeo Project
Graduation Checklist.
[2]<br class="">
<br class="">
[1] <a
moz-do-not-send="true"
href="http://wiki.osgeo.org/wiki/FOSS4G_Handbook" target="_blank"
class="">http://wiki.osgeo.org/wiki/FOSS4G_Handbook</a><br
class="">
[2] <a
moz-do-not-send="true"
href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#processes.4"
target="_blank"
class="">http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#processes.4</a><br
class="">
<br class="">
On 26/01/2015 5:53 am,
Eli Adam wrote:<br
class="">
<blockquote
class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px
#ccc
solid;padding-left:1ex">
<br class="">
Code of Conduct
specific wording is
less important than
these<br class="">
characteristics:<br
class="">
* Being present (i.e.
not implied but
clearly stated)<br
class="">
* Appearing sincere<br
class="">
* Being sincere<br
class="">
* Having reasonable
people implementing it<br
class="">
<br class="">
In that regard, the
similar texts you
listed were all fine.<br
class="">
<br class="">
Generally, I think
that we are spending
too much time and
emphasis on<br
class="">
sexualized images. We
are in the open source
geospatial software,<br
class="">
geospatial standards,
open data, education,
and related fields;
95%+<br class="">
of all presentations
and other content can
be done entirely<br
class="">
successfully without
images of people at
all. For the 5% of
cases<br class="">
that images of people
substantively
contribute to the
presentation,<br
class="">
err on the side of
caution, "If in doubt,
leave it out".<br
class="">
<br class="">
I like the idea of the
conference committee
starting with a CoC
for<br class="">
conferences and the
Board possibly
modifying and
expanding it to other<br
class="">
areas of OSGeo or
projects establishing
their own (see QGIS,<br
class="">
<a
moz-do-not-send="true"
href="http://qgis.org/en/site/getinvolved/governance/codeofconduct/codeofconduct.html"
target="_blank"
class="">http://qgis.org/en/site/getinvolved/governance/codeofconduct/codeofconduct.html</a>)<br
class="">
<br class="">
I don't think that
2015 FOSS4G needs any
input, they already
seem to<br class="">
have it under control,
<a
moz-do-not-send="true"
href="http://2015.foss4g.org/about/codeofconduct/" target="_blank"
class="">http://2015.foss4g.org/about/codeofconduct/</a>,<br
class="">
and there was nothing
about a CoC in the
bid. We should be
focusing<br class="">
2016 and beyond.<br
class="">
<br class="">
Thanks for working on
guiding this process
Cameron.<br class="">
<br class="">
Best regards, Eli<br
class="">
<br class="">
<br class="">
On Sat, Jan 24, 2015
at 3:12 AM, Cameron
Shorter<br class="">
<<a
moz-do-not-send="true"
href="mailto:cameron.shorter@gmail.com" target="_blank" class="">cameron.shorter@gmail.com</a>
<mailto:<a
moz-do-not-send="true"
href="mailto:cameron.shorter@gmail.com" target="_blank" class="">cameron.shorter@gmail.com</a>>>
wrote:<br class="">
<blockquote
class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px
#ccc
solid;padding-left:1ex">
<br class="">
Hi David,<br
class="">
Thanks for starting
this discussion.
When you opened the<br
class="">
discussion, you<br
class="">
very kindly offered
to help set a Code
of Conduct in place.
How do you<br
class="">
suggest we move
toward concluding
the discussion and
getting a Code of<br
class="">
Conduct in place?<br
class="">
Do you have a
timeframe in mind
for this? I assume
we should try to<br
class="">
make a<br class="">
CoC available for
FOSS4G 2015 if they
wish to make use of
one?<br class="">
<br class="">
Peter, thanks for
you comments on
proposed text.<br
class="">
<br class="">
Is there anyone else
with an interest in
influencing the
final<br class="">
text? If so,<br
class="">
please speak up.<br
class="">
<br class="">
Which is the better
version of a CoC?<br
class="">
<br class="">
1. Prior foss4g: <a
moz-do-not-send="true" href="https://2015.foss4g-na.org/code-conduct"
target="_blank"
class="">https://2015.foss4g-na.org/code-conduct</a><br
class="">
2. OReilly: <a
moz-do-not-send="true"
href="http://www.oreilly.com/conferences/code-of-conduct.html"
target="_blank"
class="">http://www.oreilly.com/conferences/code-of-conduct.html</a><br
class="">
(copied<br class="">
below)<br class="">
3. My revised
version (copied
below)<br class="">
4. Something else<br
class="">
<br class="">
<br class="">
On 19/01/2015 9:16
am, Cameron Shorter
wrote:<br class="">
<br class="">
Hi David,<br
class="">
I'm happy to move
proposed CoC text
across to a wiki. If
requested,<br
class="">
I'll<br class="">
copy across now
(within 48 hours),
or can wait till
there has been<br
class="">
further<br class="">
discussion.<br
class="">
<br class="">
Also happy to expand
the discussion to
other lists,
although I<br
class="">
expect the<br
class="">
conference committee
is probably the
logical primary
point for<br
class="">
discussion,<br
class="">
as a CoC is most
applicable to
conferences. The
board would need to<br
class="">
sign off<br class="">
on a CoC and should
be invited to
comment.<br class="">
<br class="">
Re identifying what
should be in a code
of conduct. I've
attempted<br
class="">
to start<br class="">
on that in the list
of items I've
attempted to
address, listed
below.<br class="">
<br class="">
I have presented the
draft CoC (below),
as I find it is
often easier to<br
class="">
start with a "straw
man" which can be
picked apart, rather
than talking<br
class="">
vaguely in
conceptual levels.
However, I'm not
wedded to the text,<br
class="">
and hope<br class="">
to see constructive
criticism of the
ideas, text and
structure.<br
class="">
<br class="">
On 19/01/2015 3:46
am, David William
Bitner wrote:<br
class="">
<br class="">
I really want to
thank everyone here
for engaging in this
issue. I do<br
class="">
appreciate all the
different voices
that have
contributed to this<br
class="">
conversation -- they
all certainly speak
to the diversity of<br
class="">
thoughts and<br
class="">
experiences that we
already have in this
community.<br
class="">
<br class="">
Cameron -- thank you
very much for
putting forward a
first draft of a<br
class="">
potential CoC for us
to use. Before
drafting and
wordsmithing a CoC<br
class="">
I want<br class="">
to step back and
make sure we answer
a few questions that
would<br class="">
certainly<br
class="">
impact how a CoC
gets written. When
we get to the point
of drafting, we<br
class="">
should certainly do
so on the wiki (or
other trackable<br
class="">
collaborative
medium)<br class="">
rather than in an
email thread.<br
class="">
<br class="">
With some of the
wording in this
draft as well as
seeing the<br
class="">
discussion from<br
class="">
the last Board
Meeting, is the
conference committee
the correct<br
class="">
venue for<br
class="">
this discussion or
should this be at
the Board level so
that this<br
class="">
applies to<br
class="">
all OSGeo activities
(mailing lists,
events, etc)? I am
certain<br class="">
that many of<br
class="">
the same people
would remain engaged
in helping draft a
Code of Conduct<br
class="">
either for the
foundation as a
whole or just for
our events, but this<br
class="">
certainly impacts
the scope and
wording required in
a draft.<br class="">
<br class="">
Many of the comments
that I read as
against having a CoC
seem to<br class="">
stem from<br
class="">
people wondering
what does a CoC
solve. Sadly, having
a CoC does<br
class="">
not "solve"<br
class="">
anything. There will
still be issues. A
CoC simply provides
one<br class="">
tool for us<br
class="">
to help resolve
those issues when
they come up as well
as providing a<br
class="">
proactive statement
that we aim to be a
welcoming and
diverse<br class="">
community to<br
class="">
hopefully prevent
some of those issues
in the first place.
A CoC is<br class="">
not the<br class="">
end point of
diversity
initiatives, but it
is a very low
hanging<br class="">
fruit to<br class="">
start with. Other
initiatives that I
know have been tried
that we<br class="">
should<br class="">
continue to look at
their effectiveness
include author blind
public<br class="">
program<br class="">
review, scholarship
initiatives,
proactively seeking
out diversity<br
class="">
in key<br class="">
notes, and many more
things that we
haven't tried.<br
class="">
<br class="">
<br class="">
On 18/01/2015 2:33
pm, Cameron Shorter
wrote:<br class="">
<br class="">
Following on from
this email thread,
I've drafted a
proposed Code of<br
class="">
Conduct, where I've
aimed to address:<br
class="">
* Be concise
(concise words get
read more)<br
class="">
* Cover key messages<br
class="">
* Include an
escalation process
for dealing with
both minor and<br
class="">
major issues<br
class="">
* Ensure key terms
are understood (in
particular reference
to<br class="">
definition of<br
class="">
sexualised images)<br
class="">
* Couch in positive
language<br class="">
<br class="">
Tickbox version:<br
class="">
* I agree to act
respectfully toward
others in line with
the OSGeo<br
class="">
Code of<br class="">
Conduct.<br class="">
<br class="">
OSGeo Code of
Conduct:<br class="">
<br class="">
This Code of Conduct
collates the
collective values
adopted by our<br
class="">
OSGeo<br class="">
community which
baselines the
behaviour we do and
don’t support to<br
class="">
ensure<br class="">
OSGeo is a safe and
productive
environment for all.<br
class="">
<br class="">
We invite everyone
to be respectful to
all, regardless of
race,<br class="">
gender, age,<br
class="">
sexual orientation,
disability, physical
appearance, national
origin,<br class="">
ethnicity, religion,
or ideas. We do not
tolerate harassment
of<br class="">
others in<br
class="">
any form. Examples
of harassment
include offensive
comments, verbal<br
class="">
threats<br class="">
or demands,
sexualized images in
public spaces,
intimidation,
stalking,<br
class="">
harassing
photography or
recording, sustained
disruption of
events, and<br
class="">
unwelcome physical
contact or sexual
attention. [1]<br
class="">
<br class="">
We expect all
participants to
follow the Code of
Conduct when<br
class="">
involved in<br
class="">
OSGeo activities.
This includes
conferences, related
social events, and<br
class="">
online forums.
Participants
violating this Code
of Conduct will be<br
class="">
asked to<br class="">
desist and/or make
amends. For gross or
continual
violations,<br
class="">
offenders may<br
class="">
be expelled from the
event or forum
without a refund,
and/or banned<br
class="">
from<br class="">
future events or
other forums.<br
class="">
<br class="">
Participants are
encouraged to bring
any concerns to the
attention<br
class="">
of event<br class="">
staff, the forum,
forum leader, or
OSGeo Board. We
thank all for<br
class="">
helping<br class="">
keep OSGeo
welcoming,
respectful, and
friendly for all.<br
class="">
<br class="">
[1] Examples of
inappropriate
sexualised
environments are
described<br
class="">
here:<br class="">
<a
moz-do-not-send="true"
href="https://www.humanrights.gov.au/publications/sexual-harassment-code-practice-what-sexual-harassment"
target="_blank"
class="">https://www.humanrights.gov.au/publications/sexual-harassment-code-practice-what-sexual-harassment</a><br
class="">
<br class="">
<br class="">
On 10/01/2015 9:59
pm, Cameron Shorter
wrote:<br class="">
<br class="">
Looking around at
various Conference
"Codes of Conduct",
I found the<br
class="">
O'Reilly definition
to be eloquently
worded, and less
threatening to<br
class="">
potential attendees.
(Although I still
can't find a clear
definition of<br
class="">
"sexual images".)<br
class="">
<br class="">
<a
moz-do-not-send="true"
href="http://www.oreilly.com/conferences/code-of-conduct.html"
target="_blank"
class="">http://www.oreilly.com/conferences/code-of-conduct.html</a><br
class="">
<br class="">
Code of Conduct<br
class="">
<br class="">
At O'Reilly, we
assume that most
people are
intelligent and<br
class="">
well-intended,<br
class="">
and we're not
inclined to tell
people what to do.
However, we want<br
class="">
every<br class="">
O'Reilly conference
to be a safe and
productive
environment for<br
class="">
everyone. To<br
class="">
that end, this code
of conduct spells
out the behavior we
support<br class="">
and don't<br
class="">
support at
conferences. The
core of our approach
is this:<br class="">
<br class="">
We don't condone
harassment or
offensive behavior,
at our<br class="">
conference venues<br
class="">
or anywhere. It's
counter to our
company values. More
importantly, it's<br
class="">
counter to our
values as human
beings.<br class="">
<br class="">
We're voicing our
strong, unequivocal
support of
appropriate<br
class="">
behavior by all<br
class="">
participants at
technical events,
including all
O'Reilly<br class="">
conferences. We<br
class="">
invite you to help
us make each
O'Reilly conference
a place that is<br
class="">
welcoming and
respectful to all
participants,
regardless of race,<br
class="">
gender,<br class="">
age, sexual
orientation,
disability, physical
appearance, national<br
class="">
origin,<br class="">
ethnicity, or
religion. So that
everyone can focus
on the<br class="">
conference itself,<br
class="">
and the great
networking and
community richness
that happens when<br
class="">
we get<br class="">
together in person,
we will not tolerate
harassment of
conference<br
class="">
participants in any
form—in person or
online.<br class="">
<br class="">
Examples of
harassment include
offensive comments,
verbal threats or<br
class="">
demands, sexualized
images in public
spaces,
intimidation,
stalking,<br
class="">
harassing
photography or
recording, sustained
disruption of
sessions or<br
class="">
events, and
unwelcome physical
contact or sexual
attention.<br
class="">
<br class="">
We expect all
participants—attendees,
speakers, sponsors,
and<br class="">
volunteers—to<br
class="">
follow the Code of
Conduct during the
conference. This
includes<br class="">
conference-related
social events at
off-site locations,
and in related<br
class="">
online communities
and social media.
Participants asked
to stop any<br
class="">
harassing behavior
are expected to
comply immediately.
Conference<br
class="">
participants
violating this Code
of Conduct may be
expelled from the<br
class="">
conference without a
refund, and/or
banned from future
O'Reilly<br class="">
events, at<br
class="">
the discretion of
O'Reilly Media.<br
class="">
<br class="">
Please bring any
concerns to the
immediate attention
of the event<br
class="">
staff, or<br
class="">
contact our VP of
Conferences, Gina
Blaber at <a
moz-do-not-send="true"
href="mailto:gina@oreilly.com" target="_blank" class="">gina@oreilly.com</a>.
We<br class="">
thank our<br
class="">
participants for
your help in keeping
the event welcoming,<br
class="">
respectful, and<br
class="">
friendly to all
participants.<br
class="">
<br class="">
Read the blog post
by Tim O'Reilly that
is the basis of our<br
class="">
functional code<br
class="">
of conduct for all
O'Reilly
conferences.<br
class="">
<br class="">
Thanks to the Lean
Startup folks and
the <a
moz-do-not-send="true"
href="http://jsconf.us/" target="_blank" class="">jsconf.us</a> folks,
whose<br class="">
Codes of<br class="">
Conduct inspired
some changes to our
own.<br class="">
<br class="">
<br class="">
--<br class="">
Cameron Shorter,<br
class="">
Software and Data
Solutions Manager<br
class="">
LISAsoft<br class="">
Suite 112, Jones Bay
Wharf,<br class="">
26 - 32 Pirrama Rd,
Pyrmont NSW 2009<br
class="">
<br class="">
P <a
moz-do-not-send="true"
href="tel:%2B61%202%209009%205000" value="+61290095000" target="_blank"
class="">+61 2
9009 5000</a>, W
<a
moz-do-not-send="true"
href="http://www.lisasoft.com/" target="_blank" class="">www.lisasoft.com</a>,
F <a
moz-do-not-send="true"
href="tel:%2B61%202%209009%205099" value="+61290095099" target="_blank"
class="">+61 2
9009 5099</a><br
class="">
<br class="">
<br class="">
--<br class="">
Cameron Shorter,<br
class="">
Software and Data
Solutions Manager<br
class="">
LISAsoft<br class="">
Suite 112, Jones Bay
Wharf,<br class="">
26 - 32 Pirrama Rd,
Pyrmont NSW 2009<br
class="">
<br class="">
P <a
moz-do-not-send="true"
href="tel:%2B61%202%209009%205000" value="+61290095000" target="_blank"
class="">+61 2
9009 5000</a>, W
<a
moz-do-not-send="true"
href="http://www.lisasoft.com/" target="_blank" class="">www.lisasoft.com</a>,
F <a
moz-do-not-send="true"
href="tel:%2B61%202%209009%205099" value="+61290095099" target="_blank"
class="">+61 2
9009 5099</a><br
class="">
<br class="">
<br class="">
--<br class="">
Cameron Shorter,<br
class="">
Software and Data
Solutions Manager<br
class="">
LISAsoft<br class="">
Suite 112, Jones Bay
Wharf,<br class="">
26 - 32 Pirrama Rd,
Pyrmont NSW 2009<br
class="">
<br class="">
P <a
moz-do-not-send="true"
href="tel:%2B61%202%209009%205000" value="+61290095000" target="_blank"
class="">+61 2
9009 5000</a>, W
<a
moz-do-not-send="true"
href="http://www.lisasoft.com/" target="_blank" class="">www.lisasoft.com</a>,
F <a
moz-do-not-send="true"
href="tel:%2B61%202%209009%205099" value="+61290095099" target="_blank"
class="">+61 2
9009 5099</a><br
class="">
<br class="">
<br class="">
_______________________________________________<br class="">
Conference_dev
mailing list<br
class="">
<a
moz-do-not-send="true"
href="mailto:Conference_dev@lists.osgeo.org" target="_blank" class="">Conference_dev@lists.osgeo.org</a><br
class="">
<a
moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/conference_dev"
target="_blank"
class="">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br
class="">
</blockquote>
</blockquote>
<br class="">
<br class="">
--<br class="">
Cameron Shorter,<br
class="">
Software and Data
Solutions Manager<br
class="">
LISAsoft<br class="">
Suite 112, Jones Bay
Wharf,<br class="">
26 - 32 Pirrama Rd,
Pyrmont NSW 2009<br
class="">
<br class="">
P <a
moz-do-not-send="true"
href="tel:%2B61%202%209009%205000" value="+61290095000" target="_blank"
class="">+61 2 9009
5000</a>, W <a
moz-do-not-send="true"
href="http://www.lisasoft.com/" target="_blank" class="">www.lisasoft.com</a>
<<a
moz-do-not-send="true"
href="http://www.lisasoft.com/" target="_blank" class="">http://www.lisasoft.com</a>>,
F<br class="">
<a
moz-do-not-send="true"
href="tel:%2B61%202%209009%205099" value="+61290095099" target="_blank"
class="">+61 2 9009
5099</a><br class="">
<br class="">
_______________________________________________<br class="">
Conference_dev mailing
list<br class="">
<a
moz-do-not-send="true"
href="mailto:Conference_dev@lists.osgeo.org" target="_blank" class="">Conference_dev@lists.osgeo.org</a>
<mailto:<a
moz-do-not-send="true"
href="mailto:Conference_dev@lists.osgeo.org" target="_blank" class="">Conference_dev@lists.osgeo.org</a>><br
class="">
<a
moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/conference_dev"
target="_blank"
class="">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br
class="">
</blockquote>
<br class="">
<br class="">
</blockquote>
<br class="">
<br class="">
</blockquote>
_______________________________________________<br
class="">
Board mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:Board@lists.osgeo.org"
target="_blank" class="">Board@lists.osgeo.org</a><br
class="">
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/board"
target="_blank" class="">http://lists.osgeo.org/mailman/listinfo/board</a><br
class="">
<br class="">
<br class="">
</blockquote>
<br class="">
_______________________________________________<br
class="">
Board mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:Board@lists.osgeo.org"
target="_blank" class="">Board@lists.osgeo.org</a><br
class="">
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/board"
target="_blank" class="">http://lists.osgeo.org/mailman/listinfo/board</a><br
class="">
_______________________________________________<br
class="">
Board mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:Board@lists.osgeo.org"
target="_blank" class="">Board@lists.osgeo.org</a><br
class="">
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/board"
target="_blank" class="">http://lists.osgeo.org/mailman/listinfo/board</a><br
class="">
</blockquote>
<br class="">
<br class="">
--<br class="">
Cameron Shorter,<br class="">
Software and Data Solutions
Manager<br class="">
LISAsoft<br class="">
Suite 112, Jones Bay Wharf,<br
class="">
26 - 32 Pirrama Rd, Pyrmont NSW
2009<br class="">
<br class="">
P <a moz-do-not-send="true"
href="tel:%2B61%202%209009%205000"
value="+61290095000"
target="_blank" class="">+61 2
9009 5000</a>, W <a
moz-do-not-send="true"
href="http://www.lisasoft.com/"
target="_blank" class="">www.lisasoft.com</a>,
F <a moz-do-not-send="true"
href="tel:%2B61%202%209009%205099"
value="+61290095099"
target="_blank" class="">+61 2
9009 5099</a><br class="">
<br class="">
_______________________________________________<br
class="">
Conference_dev mailing list<br
class="">
<a moz-do-not-send="true"
href="mailto:Conference_dev@lists.osgeo.org"
target="_blank" class="">Conference_dev@lists.osgeo.org</a><br
class="">
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/conference_dev"
target="_blank" class="">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br
class="">
</blockquote>
<br class="">
<br class="">
</blockquote>
</blockquote>
_______________________________________________<br
class="">
Conference_dev mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:Conference_dev@lists.osgeo.org"
target="_blank" class="">Conference_dev@lists.osgeo.org</a><br
class="">
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/conference_dev"
target="_blank" class="">http://lists.osgeo.org/mailman/listinfo/conference_dev</a></div>
</div>
</blockquote>
</div>
<br class="">
<br class="" clear="all">
<br class="">
-- <br class="">
<div class="">David Percy ("Percy")<br class="">
-Geospatial Data Manager<br class="">
-Web Map Wrangler<br class="">
-GIS Instructor<br class="">
Portland State University<br class="">
-<a moz-do-not-send="true"
href="http://gisgeek.pdx.edu/"
target="_blank" class="">gisgeek.pdx.edu</a><br
class="">
-<a moz-do-not-send="true"
href="http://geology.pdx.edu/"
target="_blank" class="">geology.pdx.edu</a><br
class="">
</div>
</div>
<br class="">
_______________________________________________<br
class="">
Conference_dev mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:Conference_dev@lists.osgeo.org"
target="_blank" class="">Conference_dev@lists.osgeo.org</a><br
class="">
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/conference_dev"
target="_blank" class="">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br
class="">
</blockquote>
</div>
_______________________________________________<br
class="">
Conference_dev mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:Conference_dev@lists.osgeo.org"
target="_blank" class="">Conference_dev@lists.osgeo.org</a><br
class="">
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/conference_dev"
target="_blank" class="">http://lists.osgeo.org/mailman/listinfo/conference_dev</a></blockquote>
</div>
_______________________________________________<br
class="">
Conference_dev mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:Conference_dev@lists.osgeo.org" class="">Conference_dev@lists.osgeo.org</a><br
class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a></div>
</blockquote>
</div>
<br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Conference_dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</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>