<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Interesting, MapZen will only sponsor events which have a strong COC in place:<div class=""><br class=""></div><div class=""><a href="https://mapzen.com/blog/mapzen-code-of-conduct" class="">https://mapzen.com/blog/mapzen-code-of-conduct</a></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 25 Jan 2015, at 22:10, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" class="">cameron.shorter@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div 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 place. (Add it to our cookbook [1] and bid process)<br class="">** Make it easy to apply a CoC by referencing an existing document. (Complete this discussion and provide a best practice document that 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 easy (by providing generic text), then we should add having a CoC a requirement for OSGeo graduation. I've added a placemarker into the proposed text for the next OSGeo Project Graduation Checklist. [2]<br class=""><br class="">[1] <a href="http://wiki.osgeo.org/wiki/FOSS4G_Handbook" class="">http://wiki.osgeo.org/wiki/FOSS4G_Handbook</a><br class="">[2] <a href="http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#processes.4" 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 type="cite" class="">Code of Conduct specific wording is less important than these 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 href="http://qgis.org/en/site/getinvolved/governance/codeofconduct/codeofconduct.html" 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 href="http://2015.foss4g.org/about/codeofconduct/" 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 href="mailto:cameron.shorter@gmail.com" class="">cameron.shorter@gmail.com</a>> wrote:<br class=""><blockquote type="cite" class="">Hi David,<br class="">Thanks for starting this discussion. When you opened the 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 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 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 href="https://2015.foss4g-na.org/code-conduct" class="">https://2015.foss4g-na.org/code-conduct</a><br class="">2. OReilly: <a href="http://www.oreilly.com/conferences/code-of-conduct.html" class="">http://www.oreilly.com/conferences/code-of-conduct.html</a> (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, I'll<br class="">copy across now (within 48 hours), or can wait till there has been further<br class="">discussion.<br class=""><br class="">Also happy to expand the discussion to other lists, although I expect the<br class="">conference committee is probably the logical primary point for discussion,<br class="">as a CoC is most applicable to conferences. The board would need to 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 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, 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 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 I want<br class="">to step back and make sure we answer a few questions that would 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 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 discussion from<br class="">the last Board Meeting, is the conference committee the correct venue for<br class="">this discussion or should this be at the Board level so that this applies to<br class="">all OSGeo activities (mailing lists, events, etc)? I am certain 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 stem from<br class="">people wondering what does a CoC solve. Sadly, having a CoC does not "solve"<br class="">anything. There will still be issues. A CoC simply provides one 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 community to<br class="">hopefully prevent some of those issues in the first place. A CoC is not the<br class="">end point of diversity initiatives, but it is a very low hanging fruit to<br class="">start with. Other initiatives that I know have been tried that we should<br class="">continue to look at their effectiveness include author blind public program<br class="">review, scholarship initiatives, proactively seeking out diversity 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 major issues<br class="">* Ensure key terms are understood (in particular reference to 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 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 OSGeo<br class="">community which baselines the behaviour we do and don’t support to 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, gender, age,<br class="">sexual orientation, disability, physical appearance, national origin,<br class="">ethnicity, religion, or ideas. We do not tolerate harassment of others in<br class="">any form. Examples of harassment include offensive comments, verbal 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 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 asked to<br class="">desist and/or make amends. For gross or continual violations, offenders may<br class="">be expelled from the event or forum without a refund, and/or banned from<br class="">future events or other forums.<br class=""><br class="">Participants are encouraged to bring any concerns to the attention of event<br class="">staff, the forum, forum leader, or OSGeo Board. We thank all for helping<br class="">keep OSGeo welcoming, respectful, and friendly for all.<br class=""><br class="">[1] Examples of inappropriate sexualised environments are described here:<br class=""><a href="https://www.humanrights.gov.au/publications/sexual-harassment-code-practice-what-sexual-harassment" 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="">http://www.oreilly.com/conferences/code-of-conduct.html<br class=""><br class="">Code of Conduct<br class=""><br class="">At O'Reilly, we assume that most people are intelligent and well-intended,<br class="">and we're not inclined to tell people what to do. However, we want every<br class="">O'Reilly conference to be a safe and productive environment for everyone. To<br class="">that end, this code of conduct spells out the behavior we support 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 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 behavior by all<br class="">participants at technical events, including all O'Reilly 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, gender,<br class="">age, sexual orientation, disability, physical appearance, national origin,<br class="">ethnicity, or religion. So that everyone can focus on the conference itself,<br class="">and the great networking and community richness that happens when 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 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 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 staff, or<br class="">contact our VP of Conferences, Gina Blaber at gina@oreilly.com. We thank our<br class="">participants for your help in keeping the event welcoming, 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 functional code<br class="">of conduct for all O'Reilly conferences.<br class=""><br class="">Thanks to the Lean Startup folks and the jsconf.us folks, whose 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 +61 2 9009 5000, W www.lisasoft.com, F +61 2 9009 5099<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 +61 2 9009 5000, W www.lisasoft.com, F +61 2 9009 5099<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 +61 2 9009 5000, W www.lisasoft.com, F +61 2 9009 5099<br class=""><br class=""><br class="">_______________________________________________<br class="">Conference_dev mailing list<br class="">Conference_dev@lists.osgeo.org<br class="">http://lists.osgeo.org/mailman/listinfo/conference_dev<br class=""></blockquote></blockquote><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 +61 2 9009 5000, W <a href="http://www.lisasoft.com" class="">www.lisasoft.com</a>, F +61 2 9009 5099<br class=""><br class="">_______________________________________________<br class="">Conference_dev mailing list<br class=""><a href="mailto:Conference_dev@lists.osgeo.org" class="">Conference_dev@lists.osgeo.org</a><br class="">http://lists.osgeo.org/mailman/listinfo/conference_dev</div></blockquote></div><br class=""></div></body></html>