[OSGeo-Conf] OSGeo Code of Conduct, version 1.0rc1
Cameron Shorter
cameron.shorter at gmail.com
Wed May 13 13:55:51 PDT 2015
Hi Kristin,
Thanks for your review and tweaks.
The CoC as it stands does have a light weight implementation guide, and
escalation process. This hopefully should catch 95% of scenarios.
One think I liked about the Geek Feminism Wiki was their internal
guidelines for conference staff implementing an anti-harassment policy.
http://geekfeminism.wikia.com/wiki/Conference_anti-harassment_policy
If you are inspired, and think it appropriate, you might want to
customise it to fit within the FOSS4G Handbook format:
http://wiki.osgeo.org/wiki/FOSS4G_Handbook
Warm regards,
Cameron
On 14/05/2015 4:10 am, Camille Acey wrote:
> Yes, Kristin, I agree, and I am definitely on board for the (likely
> more involved) question of implementation. Keep me posted!
>
> Thanks all,
> Camille
>
> Camille E. Acey
>
> Manager, Customer Development and Partnerships| Boundless
>
> camille at boundlessgeo.com <mailto:camille at boundlessgeo.com>
>
> T: +1 917.460.7197|M: +1 347.267.2016| Skype: camilleacey
>
> New York, NY - USA
>
> @boundlessgeo
>
> <https://twitter.com/boundlessgeo>
>
>
> <https://twitter.com/boundlessgeo>
>
>
> On Wed, May 13, 2015 at 2:05 PM, Kristin Bott <bottk at reed.edu
> <mailto:bottk at reed.edu>> wrote:
>
> Cameron,
>
> Some minor edits to the language under "Application" --
> http://wiki.osgeo.org/wiki/Code_Of_Conduct#Application
>
> 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...)
>
> 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.
>
> -kb
>
>
> On Tue, May 12, 2015 at 2:31 PM, Cameron Shorter
> <cameron.shorter at gmail.com <mailto:cameron.shorter at gmail.com>> wrote:
>
> Following on from the IRC meeting today,
> It was agreed by all participants that the proposed Code of
> Conduct should be adopted, with the following changes:
> * A statement explaining how the CoC should be applied, as
> suggested by Kristin Bott (below)
> * Remove negative words from the Diversity Statement, as
> suggested by Jeff McKenna
> * Move to a Code of Conduct URL (instead of Diversity URL)
>
> I've addressed each of these into
> http://wiki.osgeo.org/wiki/Code_Of_Conduct
>
> Kristin,
> Your suggested has been added as:
> http://wiki.osgeo.org/wiki/Code_Of_Conduct#Application
> Can you please confirm that this addresses what you were
> thinking, or suggest alternative wording.
>
> Are there any further comments or suggestions before we ask
> the board to endorse it?
>
> Warm regards,
> Cameron
>
> On 13/05/2015 3:56 am, Kristin Bott wrote:
>> Hi all,
>>
>> 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.
>>
>> I won't be able to make the related meeting, unfortunately.
>> Thanks to all who are contributing to this effort.
>>
>> 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.
>>
>> cheers -
>> - kristin
>>
>> On Sun, May 10, 2015 at 8:07 AM, Eli Adam
>> <eadam at co.lincoln.or.us <mailto:eadam at co.lincoln.or.us>> wrote:
>>
>> Hi Cameron and all,
>>
>> On May 10, 2015 3:44 AM, "Cameron Shorter"
>> <cameron.shorter at gmail.com
>> <mailto:cameron.shorter at gmail.com>> wrote:
>> >
>> > Members of the conference committee,
>>
>> Or anyone participating (but yes especially conference
>> committee members)
>>
>> > 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.
>> >
>> > I'm hoping that is because interested people have read
>> it, think it is acceptable, and don't have anything else
>> to add?
>> >
>>
>> Yes for me but always interested in hearing from others.
>>
>> > 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.
>>
>> 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.
>>
>> Best regards, Eli
>>
>> >
>> > Thanks in advance, Cameron
>> >
>> >
>> >
>> > On 2/05/2015 9:03 am, Cameron Shorter wrote:
>> >>
>> >> All,
>> >> 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.
>> >>
>> >> 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.
>> >>
>> >> 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.
>> >>
>> >> I've set up a Doodle Pole for an IRC meeting aimed at
>> finalising this Code of Conduct [1]
>> >>
>> >> If you would like to contribute, please:
>> >> 1. Read the draft code of conduct [2]
>> >> 2. Provide comments either in the comments section on
>> the wiki [3] or on the conference email list [4]
>> >> 3. Register for [1] and then attend the IRC meeting [5]
>> >>
>> >> [1] http://doodle.com/k8bmu6e8kntht462
>> >> [2] http://wiki.osgeo.org/wiki/Diversity
>> >> [3]
>> http://wiki.osgeo.org/wiki/Diversity#Community_Comments
>> >> [4] http://lists.osgeo.org/mailman/listinfo/conference_dev
>> >> [5] irc://freenode.net#osgeo <http://freenode.net#osgeo>
>> >>
>> >> Warm regards,
>> >
>> >
>> > --
>> > 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 <tel:%2B61%202%209009%205000>, W
>> www.lisasoft.com <http://www.lisasoft.com>, F +61 2 9009
>> 5099 <tel:%2B61%202%209009%205099>
>> >
>> >
>> > _______________________________________________
>> > Conference_dev mailing list
>> > Conference_dev at lists.osgeo.org
>> <mailto:Conference_dev at lists.osgeo.org>
>> > http://lists.osgeo.org/mailman/listinfo/conference_dev
>>
>>
>> _______________________________________________
>> Conference_dev mailing list
>> Conference_dev at lists.osgeo.org
>> <mailto:Conference_dev at lists.osgeo.org>
>> http://lists.osgeo.org/mailman/listinfo/conference_dev
>>
>>
>
> --
> 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 <tel:%2B61%202%209009%205000>, Wwww.lisasoft.com <http://www.lisasoft.com>, F+61 2 9009 5099 <tel:%2B61%202%209009%205099>
>
>
>
> _______________________________________________
> Conference_dev mailing list
> Conference_dev at lists.osgeo.org <mailto:Conference_dev at lists.osgeo.org>
> http://lists.osgeo.org/mailman/listinfo/conference_dev
>
>
--
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 www.lisasoft.com, F +61 2 9009 5099
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/conference_dev/attachments/20150514/652b3528/attachment-0001.html>
More information about the Conference_dev
mailing list