OSGeo - User contributions [en]

User:RhoBott

2017-09-08T17:23:41Z

Wiki-RhoBott:

{{OSGeo Member
|Name=Kristin Bott
|JobTitle=Associate Director, Instructional Technology
|Company=Reed College
|Country=USA
|State=Oregon
|City=Portland
|Coordinate=45.480978, -122.630372
|LocalChapter=Cascadia
|Email=kbott@reed.edu
|Website=http://www.reed.edu/data-at-reed/
|Info=Kristin is very interested in building a stronger and more diverse community by making OSGeo events, discussions, and products more accessible to a wider group of people. She has worked with a number of conferences (FOSS4G, FOSS4G-NA, SOTM, SOTM-US) to help design and/or execute travel grants and/or scholarships to help people attend events that otherwise may have been out of reach. She served on the LOC for FOSS4G 2014 and has been involved in the Code of Conduct committee since its inception in 2015.

Kristin works with faculty and students at Reed College on all-things-analytical, focusing on statistical + computational software, research design, and data management and presentation. She is also the main geospatial + mapping resource on campus, where she works to integrate different types of geo/spatial work across the curriculum. She is an active member of PDXOSGeo and does her best to keep track of the folks to north (CUGOS, Seattle).
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=No
|Translate=No
|PSC=No
|ExBoard=No
|Charter=Yes
|Chair=No
|SolKatz=No
|Committer=No
}}
== Kristin Bott ==

'''title''' Associate Director, Instructional Technology, Reed College

'''location''' Portland, Oregon, USA

'''OSGeo experience'''
* Co-Chair of Code of Conduct Committee, 2015 (with Camille Acey)
* Chair of Code of Conduct Committee, 11/2015-present (ongoing)
* FOSS4G 2014 Local Organizing Committee
* co-designer of 2014 FOSS4G travel grant program (with Darrell Fuhriman)
* OSGeo Charter Member (2014)
[[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]]

Twitter: [https://twitter.com/rhobott @RhoBott ]

User:RhoBott

2017-09-08T17:22:11Z

Wiki-RhoBott:

{{OSGeo Member
|Name=Kristin Bott
|JobTitle=Associate Director, Instructional Technology
|Company=Reed College
|Country=USA
|State=Oregon
|City=Portland
|Coordinate=45.480978, -122.630372
|LocalChapter=Cascadia
|Email=kbott@reed.edu
|SocialMedia=[https://twitter.com/rhobott @RhoBott ];
|Website=http://www.reed.edu/data-at-reed/
|Info=Kristin is very interested in building a stronger and more diverse community by making OSGeo events, discussions, and products more accessible to a wider group of people. She has worked with a number of conferences (FOSS4G, FOSS4G-NA, SOTM, SOTM-US) to help design and/or execute travel grants and/or scholarships to help people attend events that otherwise may have been out of reach. She served on the LOC for FOSS4G 2014 and has been involved in the Code of Conduct committee since its inception in 2015.

Kristin works with faculty and students at Reed College on all-things-analytical, focusing on statistical + computational software, research design, and data management and presentation. She is also the main geospatial + mapping resource on campus, where she works to integrate different types of geo/spatial work across the curriculum.
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=No
|Translate=No
|PSC=No
|ExBoard=No
|Charter=Yes
|Chair=No
|SolKatz=No
|Committer=No
}}
== Kristin Bott ==

'''title''' Associate Director, Instructional Technology, Reed College

'''location''' Portland, Oregon, USA

'''OSGeo experience'''
* Co-Chair of Code of Conduct Committee, 2015 (with Camille Acey)
* Chair of Code of Conduct Committee, 11/2015-present (ongoing)
* FOSS4G 2014 Local Organizing Committee
* co-designer of 2014 FOSS4G travel grant program (with Darrell Fuhriman)
* OSGeo Charter Member (2014)
[[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]]

Twitter: [https://twitter.com/rhobott @RhoBott ]

User:RhoBott

2017-09-08T17:11:24Z

Wiki-RhoBott:

== Kristin Bott ==

'''title''' Associate Director, Instructional Technology, Reed College

'''location''' Portland, Oregon, USA

'''OSGeo experience'''
* Co-Chair of Code of Conduct Committee, 2015 (with Camille Acey)
* Chair of Code of Conduct Committee, 11/2015-present (ongoing)
* FOSS4G 2014 Local Organizing Committee
* co-designer of 2014 FOSS4G travel grant program (with Darrell Fuhriman)
* OSGeo Charter Member (2014)
[[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]]

'''background and interests'''

Within OSGeo, Kristin is very interested in building a stronger and more diverse community by making OSGeo events, discussions, and products more accessible to a wider group of people. She has worked with a number of conferences (FOSS4G, FOSS4G-NA, SOTM, SOTM-US) to help design and/or execute travel grants and/or scholarships to help people attend events that otherwise may have been out of reach.

Kristin works with faculty and students at Reed College on all-things-analytical, focusing on statistical + computational software, research design, and data management and presentation. She is also the main geospatial + mapping resource on campus, where she works to integrate different types of geo/spatial work across the curriculum. Kristin is particularly interested in the intersection of GIS and teaching/education and increasing access to all-things-geospatial across a wide group of users. She holds a M.Sc. in Fisheries & Wildlife (EEBB track) from Michigan State University, a B.A. in Biology/Ecology from the University of Montana, and a graduate certificate in GIS from Portland State University. Outside of work, you can probably find her rowing a boat, riding her bike, growing/making good food, brewing beer, reading something interesting, or running around outside.

'''contact'''

kbott /at/ reed /dot/ edu

Twitter: [https://twitter.com/rhobott @RhoBott ]

[http://reed.edu/data-at-reed/ Data @ Reed collaboration]

[http://blogs.reed.edu/ed-tech/ Instructional Technology Services blog]

User:RhoBott

2017-09-08T17:10:15Z

Wiki-RhoBott: /* Kristin Bott */

CodeOfConduct Committee

2015-12-02T00:33:41Z

Wiki-RhoBott: /* Membership */

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, implementation, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015. (For more on the committee scope, see below.)

== Membership ==
The inaugural co-chairs (serving for a term of one year) will be Kristin Bott and Camille Acey. (Note: [https://lists.osgeo.org/pipermail/coc-discuss/2015-November/000027.html Camille stepped down] 2015/11/18.)The committee will be open and maintain an open mailing list (coc-discuss@osgeo.org) but will maintain a smaller voting committee (which can be contacted on their private mailing list at coc-private@osgeo.org) to handle CoC incidents and violations. This smaller committee will consist of a total of 5 members also serving one year terms. The additional 3 members will be appointed by the co-chairs.

== Mission ==
Our mission is to assist in making sure that OSGeo continues to be an inclusive and welcoming organization; we will accomplish this by (1) guiding policy around the CoC and other initiatives to increase diversity and (2) dealing with reports of violations of the CoC. The CoC committee will continue to iterate on the CoC, its implementation, and committee membership in order to ensure that they represent, nurture, and encourage diversity in our community.

== Name ==
We believe that an explicitly-named committee evidences OSGeo’s commitment to the CoC. As such we wish to retain the name of “Code of Conduct Committee”.

=== Scope ===
* The committee will be responsible for developing and receiving board approval for Code of Conduct (CoC) implementation policy. Once approved, this policy and associated documentation will be circulated amongst the community.
* In support of the OSGeo Code of Conduct, the committee will work with all community members, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings and events (including FOSS4G), as well as those who steer existing OSGeo projects and/or incubate new projects.
* The committee will review and respond to reports of violations of the CoC from participants in OSGeo projects, gatherings, events, and IRC channels. “Violations” refers to any acts by individuals or groups who repeatedly act in a way that is contrary to the stated priorities of OSGeo as an organization (i.e. the board-approved CoC).
* The committee will maintain an archive/repository of such violations as well as any organizational decisions around individuals’ conduct/participation (e.g. names of banned individuals); the OSGeo LOCs, moderators, and/or board will absolutely continue to determine whether/not individuals are welcome to participate in OSGeo events / projects / forums.
* The committee will serve as a resource to Local Organizing Committees (LOC's), moderators, and other individuals and groups leading OSGeo activities, projects, and events.

== Dealing With Code of Conduct Violations/ Reports of Violations ==
The CoC committee has no desire to blacklist individuals or provide a heavy-handed "police-like" role. Instead, we aim to serve as a resource to LOCs, moderators and the board, and to continue to iterate towards more inclusive practice/policy, as well as to help to maintain institutional knowledge about CoC violations and the decisions the LOCs, moderators, and/or board make with regard to those violations. “Violations” refers to any acts by individuals or groups who repeatedly act in a way that is contrary to the stated priorities of OSGeo as an organization (i.e. the board-approved CoC).

We intend to maintain an archive/repository of such incidents as well as any organizational (e.g. board or LOC) decisions around individuals’ conduct/participation (e.g. official warnings issues, any official investigations, and names of banned individuals). The OSGeo LOCs, moderators, and/or board will continue to determine whether/not individuals are welcome to participate in OSGeo events / projects / forums.

== Communication ==
The group will maintain a public mailing list at [https://lists.osgeo.org/mailman/listinfo/coc-discuss coc-discuss@osgeo.org] ([https://lists.osgeo.org/pipermail/coc-discuss/ list archives]) and a private committee-only mailing list at coc-private@osgeo.org. Confidential and sensitive information will be discussed only on the private mailing list. The CoC Committee will have a monthly private meeting (in their venue of choice). The committee is available to hold public meetings upon request (e.g. in IRC).

== Documents/Resources ==

Additional committee documents and resources can be found at [[CodeofConduct_Documents]]

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-11-19T23:39:15Z

Wiki-RhoBott: /* Communication */

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, implementation, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015. (For more on the committee scope, see below.)

== Membership ==
The inaugural co-chairs (serving for a term of one year) will be Kristin Bott and Camille Acey. The committee will be open and maintain an open mailing list (coc-discuss@osgeo.org) but will maintain a smaller voting committee (which can be contacted on their private mailing list at coc-private@osgeo.org) to handle CoC incidents and violations. This smaller committee will consist of a total of 5 members also serving one year terms. The additional 3 members will be appointed by the co-chairs.

== Mission ==
Our mission is to assist in making sure that OSGeo continues to be an inclusive and welcoming organization; we will accomplish this by (1) guiding policy around the CoC and other initiatives to increase diversity and (2) dealing with reports of violations of the CoC. The CoC committee will continue to iterate on the CoC, its implementation, and committee membership in order to ensure that they represent, nurture, and encourage diversity in our community.

== Name ==
We believe that an explicitly-named committee evidences OSGeo’s commitment to the CoC. As such we wish to retain the name of “Code of Conduct Committee”.

=== Scope ===
* The committee will be responsible for developing and receiving board approval for Code of Conduct (CoC) implementation policy. Once approved, this policy and associated documentation will be circulated amongst the community.
* In support of the OSGeo Code of Conduct, the committee will work with all community members, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings and events (including FOSS4G), as well as those who steer existing OSGeo projects and/or incubate new projects.
* The committee will review and respond to reports of violations of the CoC from participants in OSGeo projects, gatherings, events, and IRC channels. “Violations” refers to any acts by individuals or groups who repeatedly act in a way that is contrary to the stated priorities of OSGeo as an organization (i.e. the board-approved CoC).
* The committee will maintain an archive/repository of such violations as well as any organizational decisions around individuals’ conduct/participation (e.g. names of banned individuals); the OSGeo LOCs, moderators, and/or board will absolutely continue to determine whether/not individuals are welcome to participate in OSGeo events / projects / forums.
* The committee will serve as a resource to Local Organizing Committees (LOC's), moderators, and other individuals and groups leading OSGeo activities, projects, and events.

== Dealing With Code of Conduct Violations/ Reports of Violations ==
The CoC committee has no desire to blacklist individuals or provide a heavy-handed "police-like" role. Instead, we aim to serve as a resource to LOCs, moderators and the board, and to continue to iterate towards more inclusive practice/policy, as well as to help to maintain institutional knowledge about CoC violations and the decisions the LOCs, moderators, and/or board make with regard to those violations. “Violations” refers to any acts by individuals or groups who repeatedly act in a way that is contrary to the stated priorities of OSGeo as an organization (i.e. the board-approved CoC).

We intend to maintain an archive/repository of such incidents as well as any organizational (e.g. board or LOC) decisions around individuals’ conduct/participation (e.g. official warnings issues, any official investigations, and names of banned individuals). The OSGeo LOCs, moderators, and/or board will continue to determine whether/not individuals are welcome to participate in OSGeo events / projects / forums.

== Communication ==
The group will maintain a public mailing list at [https://lists.osgeo.org/mailman/listinfo/coc-discuss coc-discuss@osgeo.org] ([https://lists.osgeo.org/pipermail/coc-discuss/ list archives]) and a private committee-only mailing list at coc-private@osgeo.org. Confidential and sensitive information will be discussed only on the private mailing list. The CoC Committee will have a monthly private meeting (in their venue of choice). The committee is available to hold public meetings upon request (e.g. in IRC).

== Documents/Resources ==

Additional committee documents and resources can be found at [[CodeofConduct_Documents]]

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-11-19T22:54:00Z

Wiki-RhoBott: /* Communication */

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, implementation, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015. (For more on the committee scope, see below.)

== Membership ==
The inaugural co-chairs (serving for a term of one year) will be Kristin Bott and Camille Acey. The committee will be open and maintain an open mailing list (coc-discuss@osgeo.org) but will maintain a smaller voting committee (which can be contacted on their private mailing list at coc-private@osgeo.org) to handle CoC incidents and violations. This smaller committee will consist of a total of 5 members also serving one year terms. The additional 3 members will be appointed by the co-chairs.

== Mission ==
Our mission is to assist in making sure that OSGeo continues to be an inclusive and welcoming organization; we will accomplish this by (1) guiding policy around the CoC and other initiatives to increase diversity and (2) dealing with reports of violations of the CoC. The CoC committee will continue to iterate on the CoC, its implementation, and committee membership in order to ensure that they represent, nurture, and encourage diversity in our community.

== Name ==
We believe that an explicitly-named committee evidences OSGeo’s commitment to the CoC. As such we wish to retain the name of “Code of Conduct Committee”.

=== Scope ===
* The committee will be responsible for developing and receiving board approval for Code of Conduct (CoC) implementation policy. Once approved, this policy and associated documentation will be circulated amongst the community.
* In support of the OSGeo Code of Conduct, the committee will work with all community members, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings and events (including FOSS4G), as well as those who steer existing OSGeo projects and/or incubate new projects.
* The committee will review and respond to reports of violations of the CoC from participants in OSGeo projects, gatherings, events, and IRC channels. “Violations” refers to any acts by individuals or groups who repeatedly act in a way that is contrary to the stated priorities of OSGeo as an organization (i.e. the board-approved CoC).
* The committee will maintain an archive/repository of such violations as well as any organizational decisions around individuals’ conduct/participation (e.g. names of banned individuals); the OSGeo LOCs, moderators, and/or board will absolutely continue to determine whether/not individuals are welcome to participate in OSGeo events / projects / forums.
* The committee will serve as a resource to Local Organizing Committees (LOC's), moderators, and other individuals and groups leading OSGeo activities, projects, and events.

== Dealing With Code of Conduct Violations/ Reports of Violations ==
The CoC committee has no desire to blacklist individuals or provide a heavy-handed "police-like" role. Instead, we aim to serve as a resource to LOCs, moderators and the board, and to continue to iterate towards more inclusive practice/policy, as well as to help to maintain institutional knowledge about CoC violations and the decisions the LOCs, moderators, and/or board make with regard to those violations. “Violations” refers to any acts by individuals or groups who repeatedly act in a way that is contrary to the stated priorities of OSGeo as an organization (i.e. the board-approved CoC).

We intend to maintain an archive/repository of such incidents as well as any organizational (e.g. board or LOC) decisions around individuals’ conduct/participation (e.g. official warnings issues, any official investigations, and names of banned individuals). The OSGeo LOCs, moderators, and/or board will continue to determine whether/not individuals are welcome to participate in OSGeo events / projects / forums.

== Communication ==
The group will maintain a public mailing list at [https://lists.osgeo.org/mailman/listinfo/coc-discuss coc-discuss@osgeo.org] and a private committee-only mailing list at coc-private@osgeo.org. Confidential and sensitive information will be discussed only on the private mailing list. The CoC Committee will have a monthly private meeting (in their venue of choice). The committee is available to hold public meetings upon request (e.g. in IRC).

== Documents/Resources ==

Additional committee documents and resources can be found at [[CodeofConduct_Documents]]

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-08-06T18:52:59Z

Wiki-RhoBott: /* Communication */

CodeOfConduct Committee

2015-08-06T18:52:35Z

Wiki-RhoBott: /* Scope */

CodeOfConduct Committee

2015-08-06T18:44:57Z

Wiki-RhoBott: /* Mission */

CodeOfConduct Committee

2015-08-06T18:42:35Z

Wiki-RhoBott: /* Membership */

CodeOfConduct Committee

2015-08-04T18:23:50Z

Wiki-RhoBott: /* Communication */

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, implementation, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015. (For more on the committee scope, see below.)

== Membership ==
The inaugural co-chairs (serving for a term of one year) will be Kristin Bott and Camille Acey. The committee will consist of a total of 5 members also serving one year terms. The additional three members will be appointed by the co-chairs.

== Mission ==
Our mission is to assist in making sure that OSGeo continues to be an inclusive and welcoming organization, as such the committee will continue to iterate on the CoC, its implementation, and committee membership in order to ensure that they represent, nurture, and encourage diversity in our community.

=== Scope ===
* The committee will be responsible for developing and receiving board approval for Code of Conduct implementation policy. Once approved, this policy and associated documentation will be circulated amongst the community.
* In support of the OSGeo Code of Conduct, this committee will work with all community members, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings and events (including FOSS4G), as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will review and respond to incident reports from participants in OSGeo projects, gatherings, events, and IRC channels.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will serve as a resource to Local Organizing Committees (LOC's) and other groups leading OSGeo activities and events.

== Communication ==
The group maintains a public mailing list at COC-discuss@osgeo.org and a private committee-only mailing list at COC-private@osgeo.org. Confidential and sensitive information will be discussed only on the private mailing list. The CoC Committee will have a monthly private meeting (in their venue of choice). The committee is available to hold public meetings upon request (e.g. in IRC).

== Documents/Resources ==

==== Code of Conduct Workflow Discussions ====

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events

-- not sure how to deal w/ this retroactively / for ongoing projects

- Would it be possible to codify/package CoC implementation ideas/methods

- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds

- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations

- OSM/F as an example of a place where support might be needed; consider joining to support this type of work in that venue, perhaps...

- Not going to come up with the full process today but going to organize “To-Dos”, focus on OSGeo

- Different groups deal with enforcement in different ways.

- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)

- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGeo; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement

- Checklists to create: (1) reporting guidelines (2) incident reports

-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)

- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)

- Process of projects joining OSGeo be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

=== Resources ===

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/

Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/

Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports

Source: http://docs.puppetlabs.com/community/community_guidelines.html

Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 (note: value in tracking, but concerns about having history be public-facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/

Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-08-04T18:23:25Z

Wiki-RhoBott: /* Communication */

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, implementation, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015. (For more on the committee scope, see below.)

== Membership ==
The inaugural co-chairs (serving for a term of one year) will be Kristin Bott and Camille Acey. The committee will consist of a total of 5 members also serving one year terms. The additional three members will be appointed by the co-chairs.

== Mission ==
Our mission is to assist in making sure that OSGeo continues to be an inclusive and welcoming organization, as such the committee will continue to iterate on the CoC, its implementation, and committee membership in order to ensure that they represent, nurture, and encourage diversity in our community.

=== Scope ===
* The committee will be responsible for developing and receiving board approval for Code of Conduct implementation policy. Once approved, this policy and associated documentation will be circulated amongst the community.
* In support of the OSGeo Code of Conduct, this committee will work with all community members, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings and events (including FOSS4G), as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will review and respond to incident reports from participants in OSGeo projects, gatherings, events, and IRC channels.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will serve as a resource to Local Organizing Committees (LOC's) and other groups leading OSGeo activities and events.

== Communication ==
The group maintains a public mailing list at coc-discuss@osgeo.org and a private committee-only mailing list at coc-private@osgeo.org. Confidential and sensitive information will be discussed only on the private mailing list. The CoC Committee will have a monthly private meeting (in their venue of choice). The committee is available to hold public meetings upon request (e.g. in IRC).

== Documents/Resources ==

==== Code of Conduct Workflow Discussions ====

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events

-- not sure how to deal w/ this retroactively / for ongoing projects

- Would it be possible to codify/package CoC implementation ideas/methods

- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds

- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations

- OSM/F as an example of a place where support might be needed; consider joining to support this type of work in that venue, perhaps...

- Not going to come up with the full process today but going to organize “To-Dos”, focus on OSGeo

- Different groups deal with enforcement in different ways.

- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)

- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGeo; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement

- Checklists to create: (1) reporting guidelines (2) incident reports

-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)

- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)

- Process of projects joining OSGeo be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

=== Resources ===

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/

Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/

Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports

Source: http://docs.puppetlabs.com/community/community_guidelines.html

Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 (note: value in tracking, but concerns about having history be public-facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/

Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-08-04T18:23:13Z

Wiki-RhoBott: /* Communication */

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, implementation, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015. (For more on the committee scope, see below.)

== Membership ==
The inaugural co-chairs (serving for a term of one year) will be Kristin Bott and Camille Acey. The committee will consist of a total of 5 members also serving one year terms. The additional three members will be appointed by the co-chairs.

== Mission ==
Our mission is to assist in making sure that OSGeo continues to be an inclusive and welcoming organization, as such the committee will continue to iterate on the CoC, its implementation, and committee membership in order to ensure that they represent, nurture, and encourage diversity in our community.

=== Scope ===
* The committee will be responsible for developing and receiving board approval for Code of Conduct implementation policy. Once approved, this policy and associated documentation will be circulated amongst the community.
* In support of the OSGeo Code of Conduct, this committee will work with all community members, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings and events (including FOSS4G), as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will review and respond to incident reports from participants in OSGeo projects, gatherings, events, and IRC channels.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will serve as a resource to Local Organizing Committees (LOC's) and other groups leading OSGeo activities and events.

== Communication ==
The group maintains a public mailing list at coc-discuss@osgeo.org and a private committee-only mailing list at codeofconduct-private@osgeo.org. Confidential and sensitive information will be discussed only on the private mailing list. The CoC Committee will have a monthly private meeting (in their venue of choice). The committee is available to hold public meetings upon request (e.g. in IRC).

== Documents/Resources ==

==== Code of Conduct Workflow Discussions ====

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events

-- not sure how to deal w/ this retroactively / for ongoing projects

- Would it be possible to codify/package CoC implementation ideas/methods

- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds

- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations

- OSM/F as an example of a place where support might be needed; consider joining to support this type of work in that venue, perhaps...

- Not going to come up with the full process today but going to organize “To-Dos”, focus on OSGeo

- Different groups deal with enforcement in different ways.

- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)

- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGeo; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement

- Checklists to create: (1) reporting guidelines (2) incident reports

-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)

- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)

- Process of projects joining OSGeo be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

=== Resources ===

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/

Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/

Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports

Source: http://docs.puppetlabs.com/community/community_guidelines.html

Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 (note: value in tracking, but concerns about having history be public-facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/

Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-07-06T21:55:04Z

Wiki-RhoBott: /* Communication */

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, enforcement, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015. (For more on the committee scope, see below.)

== Membership ==
The inaugural co-chairs (serving for a term of one year) will be Kristin Bott and Camille Acey. The committee will consist of a total of 5 members also serving one year terms. The additional three members will be appointed by the co-chairs.

Our mission is to assist in making OSGeo a more inclusive and welcoming organization, as such the committee will continue to iterate on the CoC, its enforcement, and committee membership in order to ensure that they represent, nurture, and encourage diversity in our community.

== Scope ==
* The committee will be responsible for developing and receiving board approval for Code of Conduct enforcement policy. Once approved, this policy and associated documentation will be circulated amongst the community.
* In support of the OSGeo Code of Conduct, this committee will work with all community members, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings and events (including FOSS4G), as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will review and respond to incident reports from participants in OSGeo projects, gatherings, events, and IRC channels.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will serve as a resource to Local Organizing Committees (LOC's) and other groups leading OSGeo activities and events.

== Communication ==
The group maintains a public mailing list at codeofconduct@osgeo.org and a private committee-only mailing list at codeofconduct-private@osgeo.org. Confidential and sensitive information will be discussed only on the private mailing list. The CoC Committee will have a monthly private meeting (in their venue of choice). The committee is available to hold public meetings upon request (e.g. in IRC).

== Documents/Resources ==

==== Code of Conduct Workflow Discussions ====

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events

-- not sure how to deal w/ this retroactively / for ongoing projects

- Would it be possible to codify/package CoC implementation ideas/methods

- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds

- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations

- OSM/F as an example of a place where support might be needed; consider joining to support this type of work in that venue, perhaps...

- Not going to come up with the full process today but going to organize “To-Dos”, focus on OSGEO

- Different groups deal with enforcement in different ways.

- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)

- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement

- Checklists to create: (1) reporting guidelines (2) incident reports

-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)

- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)

- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

=== Resources ===

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/

Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/

Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports

Source: http://docs.puppetlabs.com/community/community_guidelines.html

Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 (note: value in tracking, but concerns about having history be public-facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/

Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-07-03T22:40:21Z

Wiki-RhoBott:

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, enforcement, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015. (For more on the committee scope, see below.)

== Membership ==
* The committee will consist of [number to be determined] members. In order to capture the diverse nature of the OSGeo community, members will come from [would like to capture geographic diversity -- how to divide?]. The committee should also represent a mix of OSGeo community members and those who have experience organizing FOSS4G events. While we realize that gender parity may be difficult in a community that does not tend to have equal representation of men and women, ideally the CoC Committee would be a mix of men and women. [rewrite; awkward language]

== Scope ==
* The committee will be responsible for developing and receiving board approval for Code of Conduct enforcement policy. Once approved, this policy and associated documentation will be circulated amongst the community.
* In support of the OSGeo Code of Conduct, this committee will work with all community members, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings and events (including FOSS4G), as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will review and respond to incident reports from participants in OSGeo projects, gatherings, events, and IRC channels.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will serve as a resource to Local Organizing Committees (LOC's) and other groups leading OSGeo activities and events.

== Communication ==
The group maintains a public mailing list at codeofconduct@osgeo.org and a private committee-only mailing list at codeofconduct-private@osgeo.org. Confidential and sensitive information will be discussed only on the private mailing list. The CoC Committee will have a monthly private meeting (in their venue of choice). The committee is available to hold public meetings upon request in IRC.

== Documents/Resources ==

==== Code of Conduct Workflow Discussions ====

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events

-- not sure how to deal w/ this retroactively / for ongoing projects

- Would it be possible to codify/package CoC implementation ideas/methods

- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds

- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations

- OSM/F as an example of a place where support might be needed; consider joining to support this type of work in that venue, perhaps...

- Not going to come up with the full process today but going to organize “To-Dos”, focus on OSGEO

- Different groups deal with enforcement in different ways.

- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)

- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement

- Checklists to create: (1) reporting guidelines (2) incident reports

-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)

- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)

- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

=== Resources ===

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/

Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/

Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports

Source: http://docs.puppetlabs.com/community/community_guidelines.html

Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 (note: value in tracking, but concerns about having history be public-facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/

Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-07-03T22:39:01Z

Wiki-RhoBott: /* Scope */

''Note: this committee is currently in formation and this page is a work in progress. When materials are finalized, updates will be posted to the OSGeo-Discuss list. -k.bott 6/24/15''

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, enforcement, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015.

== Membership ==
* The committee will consist of [number to be determined] members. In order to capture the diverse nature of the OSGeo community, members will come from [would like to capture geographic diversity -- how to divide?]. The committee should also represent a mix of OSGeo community members and those who have experience organizing FOSS4G events. While we realize that gender parity may be difficult in a community that does not tend to have equal representation of men and women, ideally the CoC Committee would be a mix of men and women. [rewrite; awkward language]

== Scope ==
* The committee will be responsible for developing and receiving board approval for Code of Conduct enforcement policy. Once approved, this policy and associated documentation will be circulated amongst the community.
* In support of the OSGeo Code of Conduct, this committee will work with all community members, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings and events (including FOSS4G), as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will review and respond to incident reports from participants in OSGeo projects, gatherings, events, and IRC channels.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will serve as a resource to Local Organizing Committees (LOC's) and other groups leading OSGeo activities and events.

== Communication ==
The group maintains a public mailing list at codeofconduct@osgeo.org and a private committee-only mailing list at codeofconduct-private@osgeo.org. Confidential and sensitive information will be discussed only on the private mailing list. The CoC Committee will have a monthly private meeting (in their venue of choice). The committee is available to hold public meetings upon request in IRC.

== Documents/Resources ==

==== Code of Conduct Workflow Discussions ====

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events

-- not sure how to deal w/ this retroactively / for ongoing projects

- Would it be possible to codify/package CoC implementation ideas/methods

- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds

- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations

- OSM/F as an example of a place where support might be needed; consider joining to support this type of work in that venue, perhaps...

- Not going to come up with the full process today but going to organize “To-Dos”, focus on OSGEO

- Different groups deal with enforcement in different ways.

- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)

- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement

- Checklists to create: (1) reporting guidelines (2) incident reports

-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)

- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)

- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

=== Resources ===

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/

Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/

Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports

Source: http://docs.puppetlabs.com/community/community_guidelines.html

Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 (note: value in tracking, but concerns about having history be public-facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/

Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-07-03T19:01:06Z

Wiki-RhoBott: /* Scope */

''Note: this committee is currently in formation and this page is a work in progress. When materials are finalized, updates will be posted to the OSGeo-Discuss list. -k.bott 6/24/15''

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, enforcement, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015.

== Membership ==
* The committee will consist of [number to be determined] members. In order to capture the diverse nature of the OSGeo community, members will come from [would like to capture geographic diversity -- how to divide?]. The committee should also represent a mix of OSGeo community members and those who have experience organizing FOSS4G events. While we realize that gender parity may be difficult in a community that does not tend to have equal representation of men and women, ideally the CoC Committee would be a mix of men and women. [rewrite; awkward language]

== Scope ==
* The committee will be responsible for developing and receiving board approval for Code of Conduct enforcement policy. Once approved, this policy (and associated documentation) will be circulate amongst the community, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings and events (including FOSS4G), as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will review and respond to online incident reports.
* The committee will serve as a resource to Local Organizing Committees [LOC's] and other groups leading OSGeo activities and events.

== Communication ==
The group maintains a public mailing list at codeofconduct@osgeo.org and a private committee-only mailing list at codeofconduct-private@osgeo.org. Confidential and sensitive information will be discussed only on the private mailing list. The CoC Committee will have a monthly private meeting (in their venue of choice). The committee is available to hold public meetings upon request in IRC.

== Documents/Resources ==

==== Code of Conduct Workflow Discussions ====

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events

-- not sure how to deal w/ this retroactively / for ongoing projects

- Would it be possible to codify/package CoC implementation ideas/methods

- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds

- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations

- OSM/F as an example of a place where support might be needed; consider joining to support this type of work in that venue, perhaps...

- Not going to come up with the full process today but going to organize “To-Dos”, focus on OSGEO

- Different groups deal with enforcement in different ways.

- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)

- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement

- Checklists to create: (1) reporting guidelines (2) incident reports

-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)

- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)

- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

=== Resources ===

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/

Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/

Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports

Source: http://docs.puppetlabs.com/community/community_guidelines.html

Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 (note: value in tracking, but concerns about having history be public-facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/

Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-07-03T18:58:09Z

Wiki-RhoBott: /* Code of Conduct Workflow Discussions */

''Note: this committee is currently in formation and this page is a work in progress. When materials are finalized, updates will be posted to the OSGeo-Discuss list. -k.bott 6/24/15''

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, enforcement, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015.

== Membership ==
* The committee will consist of [number to be determined] members. In order to capture the diverse nature of the OSGeo community, members will come from [would like to capture geographic diversity -- how to divide?]. The committee should also represent a mix of OSGeo community members and those who have experience organizing FOSS4G events. While we realize that gender parity may be difficult in a community that does not tend to have equal representation of men and women, ideally the CoC Committee would be a mix of men and women. [rewrite; awkward language]

== Scope ==
* The committee will be responsible for developing and receiving board approval for Code of Conduct enforcement policy. Once approved, this policy (and associated documentation) will be circulate amongst the community, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings and events (e.g. LOC's), as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will review and respond to online incident reports.
* The committee will serve as a resource to Local Organizing Committees [LOC's] and other groups leading OSGeo activities and events.

== Communication ==
The group maintains a public mailing list at codeofconduct@osgeo.org and a private committee-only mailing list at codeofconduct-private@osgeo.org. Confidential and sensitive information will be discussed only on the private mailing list. The CoC Committee will have a monthly private meeting (in their venue of choice). The committee is available to hold public meetings upon request in IRC.

== Documents/Resources ==

==== Code of Conduct Workflow Discussions ====

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events

-- not sure how to deal w/ this retroactively / for ongoing projects

- Would it be possible to codify/package CoC implementation ideas/methods

- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds

- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations

- OSM/F as an example of a place where support might be needed; consider joining to support this type of work in that venue, perhaps...

- Not going to come up with the full process today but going to organize “To-Dos”, focus on OSGEO

- Different groups deal with enforcement in different ways.

- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)

- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement

- Checklists to create: (1) reporting guidelines (2) incident reports

-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)

- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)

- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

=== Resources ===

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/

Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/

Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports

Source: http://docs.puppetlabs.com/community/community_guidelines.html

Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 (note: value in tracking, but concerns about having history be public-facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/

Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-07-03T18:54:25Z

Wiki-RhoBott: /* Scope */

''Note: this committee is currently in formation and this page is a work in progress. When materials are finalized, updates will be posted to the OSGeo-Discuss list. -k.bott 6/24/15''

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, enforcement, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015.

== Membership ==
* The committee will consist of [number to be determined] members. In order to capture the diverse nature of the OSGeo community, members will come from [would like to capture geographic diversity -- how to divide?]. The committee should also represent a mix of OSGeo community members and those who have experience organizing FOSS4G events. While we realize that gender parity may be difficult in a community that does not tend to have equal representation of men and women, ideally the CoC Committee would be a mix of men and women. [rewrite; awkward language]

== Scope ==
* The committee will be responsible for developing and receiving board approval for Code of Conduct enforcement policy. Once approved, this policy (and associated documentation) will be circulate amongst the community, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings and events (e.g. LOC's), as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will review and respond to online incident reports.
* The committee will serve as a resource to Local Organizing Committees [LOC's] and other groups leading OSGeo activities and events.

== Communication ==
The group maintains a mailing list at codeofconduct@osgeo.org. Because the CoC Committee deals with confidential and sensitive information, this mailing list will be private to members of the committee. The CoC Committee will also meet in the IRC channel monthly [proposed].

== Documents/Resources ==

=== Code of Conduct Workflow Discussions ===

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events?

-- not sure how to deal w/ this retroactively / for ongoing projects

- Would it be possibly to codify/package CoC implementation ideas/methods?

- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds

- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations

- OSM/F as an example of a place where support might be needed; consider joining, perhaps...

- Not going to come up with the full process today but going to organize “To-Dos”

- Focus on OSGEO

- Different groups deal with enforcement in different ways.

- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)

- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement

- Checklists to create: (1) reporting guidelines (2) incident reports

-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)

- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)

- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

=== Resources ===

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/

Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/

Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports

Source: http://docs.puppetlabs.com/community/community_guidelines.html

Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 (note: value in tracking, but concerns about having history be public-facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/

Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-07-01T05:16:03Z

Wiki-RhoBott: /* Documents/Resources */

''Note: this committee is currently in formation and this page is a work in progress. When materials are finalized, updates will be posted to the OSGeo-Discuss list. -k.bott 6/24/15''

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, enforcement, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015.

== Membership ==
* The committee will consist of [number to be determined] members. In order to capture the diverse nature of the OSGeo community, members will come from [would like to capture geographic diversity -- how to divide?]. The committee should also represent a mix of OSGeo community members and those who have experience organizing FOSS4G events. While we realize that gender parity may be difficult in a community that does not tend to have equal representation of men and women, ideally the CoC Committee would be a mix of men and women. [rewrite; awkward language]

== Scope ==
* The committee will be responsible for developing and receiving board approval for Code of Conduct enforcement policy. Once approved, this policy (and associated documentation) will be circulate amongst the community, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings, as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will review and respond to online incident reports.
* The committee will serve as a resource to LOCs and other groups leading OSGeo activities.

== Communication ==
The group maintains a mailing list at codeofconduct@osgeo.org. Because the CoC Committee deals with confidential and sensitive information, this mailing list will be private to members of the committee. The CoC Committee will also meet in the IRC channel monthly [proposed].

== Documents/Resources ==

=== Code of Conduct Workflow Discussions ===

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events?

-- not sure how to deal w/ this retroactively / for ongoing projects

- Would it be possibly to codify/package CoC implementation ideas/methods?

- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds

- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations

- OSM/F as an example of a place where support might be needed; consider joining, perhaps...

- Not going to come up with the full process today but going to organize “To-Dos”

- Focus on OSGEO

- Different groups deal with enforcement in different ways.

- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)

- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement

- Checklists to create: (1) reporting guidelines (2) incident reports

-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)

- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)

- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

=== Resources ===

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/

Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/

Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports

Source: http://docs.puppetlabs.com/community/community_guidelines.html

Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 (note: value in tracking, but concerns about having history be public-facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/

Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-07-01T05:15:16Z

Wiki-RhoBott: /* Resources */

''Note: this committee is currently in formation and this page is a work in progress. When materials are finalized, updates will be posted to the OSGeo-Discuss list. -k.bott 6/24/15''

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, enforcement, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015.

== Membership ==
* The committee will consist of [number to be determined] members. In order to capture the diverse nature of the OSGeo community, members will come from [would like to capture geographic diversity -- how to divide?]. The committee should also represent a mix of OSGeo community members and those who have experience organizing FOSS4G events. While we realize that gender parity may be difficult in a community that does not tend to have equal representation of men and women, ideally the CoC Committee would be a mix of men and women. [rewrite; awkward language]

== Scope ==
* The committee will be responsible for developing and receiving board approval for Code of Conduct enforcement policy. Once approved, this policy (and associated documentation) will be circulate amongst the community, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings, as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will review and respond to online incident reports.
* The committee will serve as a resource to LOCs and other groups leading OSGeo activities.

== Communication ==
The group maintains a mailing list at codeofconduct@osgeo.org. Because the CoC Committee deals with confidential and sensitive information, this mailing list will be private to members of the committee. The CoC Committee will also meet in the IRC channel monthly [proposed].

== Documents/Resources ==

=== Code of Conduct Workflow Discussions ===

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events?
-- not sure how to deal w/ this retroactively / for ongoing projects
- Would it be possibly to codify/package CoC implementation ideas/methods?
- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds
- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations
- OSM/F as an example of a place where support might be needed; consider joining, perhaps...
- Not going to come up with the full process today but going to organize “To-Dos”
- Focus on OSGEO
- Different groups deal with enforcement in different ways.
- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)
- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement
- Checklists to create: (1) reporting guidelines (2) incident reports
-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)
- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)
- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

=== Resources ===

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/

Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/

Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports

Source: http://docs.puppetlabs.com/community/community_guidelines.html

Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 (note: value in tracking, but concerns about having history be public-facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/

Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-07-01T05:14:22Z

Wiki-RhoBott: /* Documents/Resources */

''Note: this committee is currently in formation and this page is a work in progress. When materials are finalized, updates will be posted to the OSGeo-Discuss list. -k.bott 6/24/15''

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, enforcement, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015.

== Membership ==
* The committee will consist of [number to be determined] members. In order to capture the diverse nature of the OSGeo community, members will come from [would like to capture geographic diversity -- how to divide?]. The committee should also represent a mix of OSGeo community members and those who have experience organizing FOSS4G events. While we realize that gender parity may be difficult in a community that does not tend to have equal representation of men and women, ideally the CoC Committee would be a mix of men and women. [rewrite; awkward language]

== Scope ==
* The committee will be responsible for developing and receiving board approval for Code of Conduct enforcement policy. Once approved, this policy (and associated documentation) will be circulate amongst the community, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings, as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will review and respond to online incident reports.
* The committee will serve as a resource to LOCs and other groups leading OSGeo activities.

== Communication ==
The group maintains a mailing list at codeofconduct@osgeo.org. Because the CoC Committee deals with confidential and sensitive information, this mailing list will be private to members of the committee. The CoC Committee will also meet in the IRC channel monthly [proposed].

== Documents/Resources ==

=== Code of Conduct Workflow Discussions ===

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events?
-- not sure how to deal w/ this retroactively / for ongoing projects
- Would it be possibly to codify/package CoC implementation ideas/methods?
- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds
- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations
- OSM/F as an example of a place where support might be needed; consider joining, perhaps...
- Not going to come up with the full process today but going to organize “To-Dos”
- Focus on OSGEO
- Different groups deal with enforcement in different ways.
- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)
- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement
- Checklists to create: (1) reporting guidelines (2) incident reports
-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)
- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)
- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

=== Resources ===

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/

Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/

Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports

Source: http://docs.puppetlabs.com/community/community_guidelines.html

Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 ( I think it should be tracked but I am worried about it being public facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/
Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-07-01T05:12:44Z

Wiki-RhoBott: /* Responsibilities */

''Note: this committee is currently in formation and this page is a work in progress. When materials are finalized, updates will be posted to the OSGeo-Discuss list. -k.bott 6/24/15''

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, enforcement, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015.

== Membership ==
* The committee will consist of [number to be determined] members. In order to capture the diverse nature of the OSGeo community, members will come from [would like to capture geographic diversity -- how to divide?]. The committee should also represent a mix of OSGeo community members and those who have experience organizing FOSS4G events. While we realize that gender parity may be difficult in a community that does not tend to have equal representation of men and women, ideally the CoC Committee would be a mix of men and women. [rewrite; awkward language]

== Scope ==
* The committee will be responsible for developing and receiving board approval for Code of Conduct enforcement policy. Once approved, this policy (and associated documentation) will be circulate amongst the community, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings, as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will review and respond to online incident reports.
* The committee will serve as a resource to LOCs and other groups leading OSGeo activities.

== Communication ==
The group maintains a mailing list at codeofconduct@osgeo.org. Because the CoC Committee deals with confidential and sensitive information, this mailing list will be private to members of the committee. The CoC Committee will also meet in the IRC channel monthly [proposed].

== Documents/Resources ==

=== Code of Conduct Workflow Discussions ===

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events?
-- not sure how to deal w/ this retroactively / for ongoing projects
- Would it be possibly to codify/package CoC implementation ideas/methods?
- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds
- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations
- OSM/F as an example of a place where support might be needed; consider joining, perhaps...
- Not going to come up with the full process today but going to organize “To-Dos”
- Focus on OSGEO
- Different groups deal with enforcement in different ways.
- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)
- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement
- Checklists to create: (1) reporting guidelines (2) incident reports
-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)
- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)
- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

Resources from other groups:

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/
Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/
Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports
Source: http://docs.puppetlabs.com/community/community_guidelines.html
Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 ( I think it should be tracked but I am worried about it being public facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/
Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-07-01T05:12:20Z

Wiki-RhoBott: /* Responsibilities */

''Note: this committee is currently in formation and this page is a work in progress. When materials are finalized, updates will be posted to the OSGeo-Discuss list. -k.bott 6/24/15''

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, enforcement, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015.

== Membership ==
* The committee will consist of [number to be determined] members. In order to capture the diverse nature of the OSGeo community, members will come from [would like to capture geographic diversity -- how to divide?]. The committee should also represent a mix of OSGeo community members and those who have experience organizing FOSS4G events. While we realize that gender parity may be difficult in a community that does not tend to have equal representation of men and women, ideally the CoC Committee would be a mix of men and women. [rewrite; awkward language]

== Scope ==
* The committee will be responsible for developing and receiving board approval for Code of Conduct enforcement policy. Once approved, this policy (and associated documentation) will be circulate amongst the community, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings, as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will review and respond to online incident reports.
* The committee will serve as a resource to LOCs and other groups leading OSGeo activities.

== Responsibilities ==
The group maintains a mailing list at codeofconduct@osgeo.org. Because the CoC Committee deals with confidential and sensitive information, this mailing list will be private to members of the committee. The CoC Committee will also meet in the IRC channel monthly [proposed].

== Documents/Resources ==

=== Code of Conduct Workflow Discussions ===

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events?
-- not sure how to deal w/ this retroactively / for ongoing projects
- Would it be possibly to codify/package CoC implementation ideas/methods?
- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds
- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations
- OSM/F as an example of a place where support might be needed; consider joining, perhaps...
- Not going to come up with the full process today but going to organize “To-Dos”
- Focus on OSGEO
- Different groups deal with enforcement in different ways.
- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)
- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement
- Checklists to create: (1) reporting guidelines (2) incident reports
-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)
- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)
- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

Resources from other groups:

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/
Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/
Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports
Source: http://docs.puppetlabs.com/community/community_guidelines.html
Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 ( I think it should be tracked but I am worried about it being public facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/
Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

CodeOfConduct Committee

2015-06-25T05:20:59Z

Wiki-RhoBott: continuing to develop CoC cmte

''Note: this committee is currently in formation and this page is a work in progress. When materials are finalized, updates will be posted to the OSGeo-Discuss list. -k.bott 6/24/15''

The Code Of Conduct Committee is responsible for defining internal workflows and sharing organization knowledge related to the maintenance, enforcement, and continued improvement of the OSGeo Code of Conduct ([[Code_Of_Conduct | background-wiki]], [http://www.osgeo.org/code_of_conduct Official OSGeo Code of Conduct]) which was approved by the OSGeo Board in 2015.

== Membership ==
* The committee will consist of [number to be determined] members. In order to capture the diverse nature of the OSGeo community, members will come from [would like to capture geographic diversity -- how to divide?]. The committee should also represent a mix of OSGeo community members and those who have experience organizing FOSS4G events. While we realize that gender parity may be difficult in a community that does not tend to have equal representation of men and women, ideally the CoC Committee would be a mix of men and women. [rewrite; awkward language]

== Responsibilities ==
* The committee will be responsible for developing and receiving board approval for Code of Conduct enforcement policy. Once approved, this policy (and associated documentation) will be circulate amongst the community, with a strong focus on those who moderate OSGeo IRC channels, organize OSGeo gatherings, as well as those who steer existing OSGeo projects and/or incubate potential new ones.
* The committee will maintain the list of individuals restricted from OSGeo activities and retain a copy of all incident reports.
* The committee will review and respond to online incident reports.
* The committee will serve as a resource to LOCs and other groups leading OSGeo activities.

== Responsibilities ==
The group maintains a mailing list at codeofconduct@osgeo.org. Because the CoC Committee deals with confidential and sensitive information, this mailing list will be private to members of the committee. The CoC Committee will also meet in the IRC channel monthly [proposed].

== Documents/Resources ==

=== Code of Conduct Workflow Discussions ===

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events?
-- not sure how to deal w/ this retroactively / for ongoing projects
- Would it be possibly to codify/package CoC implementation ideas/methods?
- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds
- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations
- OSM/F as an example of a place where support might be needed; consider joining, perhaps...
- Not going to come up with the full process today but going to organize “To-Dos”
- Focus on OSGEO
- Different groups deal with enforcement in different ways.
- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)
- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement
- Checklists to create: (1) reporting guidelines (2) incident reports
-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)
- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)
- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

Resources from other groups:

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/
Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/
Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports
Source: http://docs.puppetlabs.com/community/community_guidelines.html
Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 ( I think it should be tracked but I am worried about it being public facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/
Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
*

[[Category:Committees]]
[[Category:Board Approval Pending]]

Conference Committee

2015-06-25T00:01:36Z

Wiki-RhoBott: /* Current Members */

The Conference Committee is the official committee of OSGeo responsible for operating the annual [[FOSS4G]] conferences.

= Noteworthy Documents =

* [http://www.osgeo.org/conference OSGeo Conference Committee main page] (includes RFP, proposals, and archived files from past conferences)
* http://lists.osgeo.org/mailman/listinfo/conference_dev - Conference Committee email list
* [[Motion to form Conference Committee]]
* [[Conference website management]]

= Goals =

* facilitate the hosting application/decision process
* assist the conference local organizing committees in planning
* make sure OSGeo foundation principles exist in all conferences
* possibly support other affiliated conferences

== Other Responsibilities ==

* [[Sol Katz Award]]

= Current Members =

* [[User:EliL | Eli Adam]]
* Thierry Badard
* Peter Batty
* David Bitner
* Jachym Cepicky
* Vasile Craciunescu
* David Fawcett
* [[User:Stevenfeldman | Steven Feldman]]
* Gavin Fleming
* Darrell Fuhriman
* Dave McIlhagga
* Helena Mitasova
* Claude Philipona
* Venkatesh Raghavan
* Paul Ramsey
* Cameron Shorter
* Jeroen Ticheler

= Past Members =

* Lorenzo Becchi
* Allan Doyle
* Olivier Ertz
* Alain Grignon
* Luc Maurer
* Daniel Rappo
* Dave Patton
* Rafael Medeiros Sperb
* [[Jeff McKenna]]
* Arnulf Christl
* [[Markus Neteler]]
* Steve Lime
* Frank Warmerdam

= Meetings =

* Meetings occur in IRC in the #foss4g channel (on irc.freenode.net)
* See the [[Conference_Committee_Meetings | Conference Committee Meetings]] page for information about the committee's meetings.

= 2017 Pages =

* [[FOSS4G_2017_Bid_Process | 2017 RFP schedule]]

= 2016 Pages =

* [http://www.osgeo.org/conference/rfp/ 2016 RFP schedule]

= 2015 Pages =

* [[FOSS4G 2015 Bid Process]]

= 2014 Pages =

* [[FOSS4G 2014 Bid Process]]
* [[FOSS4G 2014]]
* [[FOSS4G Europe 2014]]
* [[FOSS4G Handbook]] (provides guidance to future FOSS4G and FOSS4G related events, based upon the collective wisdom gained during prior events)

= 2013 Pages =

* Main page: [[FOSS4G_2013]]
* [http://svn.osgeo.org/osgeo/foss4g/2013/documents/FOSS4G_2013_UK_Proposal-Final_version.pdf 2013 Proposal]
* Reflections on the event by the LOC (includes lessons learnt and supersedes the old Lessons Learned page): [[FOSS4G2013_Reflections_by_the_LOC]]

= 2012 Pages =
Main page: [[FOSS4G 2012]]
* RFP ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-2012-request-for-proposal.odt OpenOffice], [http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-2012-request-for-proposal.pdf pdf])
* budget template ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-budget-template.ods OpenOffice])
* Important dates:
** Letters of Intent (Stage 1) due: 2011-06-30 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=06&day=30&hour=23&min=0&sec=0 23:00 UTC])
** Stage 1 question period: 2011-06-30 to 2011-07-07
** Stage 1 decision: 2011-07-07
** Proposals (Stage 2) due: 2011-08-01 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=08&day=01&hour=23&min=0&sec=0 23:00 UTC])
** Stage 2 question period: 2011-08-01 to 2011-08-05
** Final decision: 2011-08-05

= 2011 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Letters of Intent]
* [[FOSS4G_2011_Bid_Process | 2011 Bid Process]]
* [[FOSS4G Reboot 2011 | Initial thoughts on 2011 required changes]]

= 2010 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Proposals]
* [[Conference_Committee_2010_Bid_Questions | Bid Questions]]
* [[Conference_Committee_2010_Voting_Process | Voting Process]]

= 2009 Pages =

* [[FOSS4G 2009 Governance]]
* All [http://wiki.osgeo.org/wiki/Category:FOSS4G2009 FOSS4G 2009] pages.

= 2008 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Proposals]
* [http://lists.osgeo.org/pipermail/conference_dev/2007-July/000355.html Voting Process]
* [[FOSS4G 2008 Governance]]
* [[FOSS4GLOC matters]]
* [http://spreadsheets.google.com/pub?key=p6mc38S7PA8lHWRQuIgExDA Workshop and lab evaluations]

= 2007 Pages =

* [http://wiki.osgeo.org/index.php/Category:FOSS4G2007 Pages in category "FOSS4G2007"]
* [[FOSS4G2007]] - wiki page
* http://www.foss4g2007.org/ - Conference Site
* [http://www.osgeo.org/conference/rfp Proposals and RFP]
* [[OSGeo_Conference_RFP_2007#RFP_Response_Requirements | requirements Wiki page]]
* [[OSGeo_Conference_Naming_Results | Naming results]]
* [http://www.foss4g2007.org/bid_site/ Victoria 2007 Proposal]
* [[FOSS4G 2007 Governance]]
* [[FOSS4G2007 Lessons Learned]]

= 2006 Pages =

* [http://wiki.osgeo.org/index.php/Category:FOSS4G2006 Pages in category "FOSS4G2006"]
* http://www.foss4g2006.org/ - Conference Site
* [[FOSS4G2006]] information

= Event Policy Pages =

* [[Official_OSGeo_Event_Policy | OSGeo Event policy]] (in review)
* [[OSGeo_Conference_Policy | Board notes]] regarding event policy
* [http://www.osgeo.org/code_of_conduct OSGeo Code of Conduct]
[[Category:FOSS4G]]
[[Category:Committees]]
[[Category:Conference Committee]]

Code Of Conduct

2015-06-06T20:44:54Z

Wiki-RhoBott: /* Code of Conduct Workflow Discussions */

Please refer to the official version of this wiki page at: http://www.osgeo.org/code_of_conduct .

This page includes reference to prior material and comments applied during the development. (For history, refer to the [[Diversity]] page).
The official version 1.0 of the Code of Conduct was taken from: http://wiki.osgeo.org/index.php?title=Code_Of_Conduct&diff=84231&oldid=84214

==OSGeo Code of Conduct==

Version: 1.0

Date: May 2015

===Introduction===

This code of conduct governs how we behave in any OSGeo forum or event and whenever we will be judged by our actions. We expect it to be honored by everyone who participates in the OSGeo community formally or informally, or claims any affiliation with the OSGeo Foundation.

It applies to in-person events (such as conferences and related social events), IRC, public and private mailing lists, the issue tracker, the wiki, blogs, Twitter, and any other forums which the community uses for communication and interactions.

This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in the letter, so that it can enrich all of us and the technical communities in which we participate.

===Diversity Statement===

OSGeo welcomes and encourages participation by everyone. We are committed to being a community that everyone feels good about joining, and we will always work to treat everyone well. No matter how you identify yourself or how others perceive you: we welcome you.

===Specific Guidelines===

We strive to:

;Be open.
: We invite anyone to participate in our community. We preferably use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also makes sure that any inadvertent mistakes made by people answering will be more easily detected and corrected.

;Be empathetic, welcoming, friendly, and patient.
:We work together to resolve conflict, assume good intentions, and do our best to act in an empathetic fashion. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one. Note that we have a multi-cultural, multi-lingual community and some of us are non-native speakers. We should be respectful when dealing with other community members as well as with people outside our community.

;Be collaborative. : Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of OSGeo, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.

;Be inquisitive. : Nobody knows everything! Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful, within the context of our shared goal of improving OSGeo.

;Be careful in the words that we choose. : Whether we are participating as professionals or volunteers, we value professionalism in all interactions, and take responsibility for our own speech. Be kind to others. Do not insult or put down other participants.

;Be concise. : Keep in mind that what you write once will be read by hundreds of persons. Writing a short email means people can understand the conversation as efficiently as possible. Short emails should always strive to be empathetic, welcoming, friendly and patient. When a long explanation is necessary, consider adding a summary.

: Try to bring new ideas to a conversation so that each mail adds something unique to the thread, keeping in mind that the rest of the thread still contains the other messages with arguments that have already been made.

: Try to stay on topic, especially in discussions that are already fairly large.

; Step down considerately.
: Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project's goals or achievements. Likewise, community members should respect any individual's choice to leave the project.

===Anti-Harassment===

Harassment and other exclusionary behaviour are not acceptable. This includes, but is not limited to:

* Personal insults or discriminatory jokes and language, especially those using racist or sexist terms.
* Offensive comments, excessive or unnecessary profanity.
* Intimidation, violent threats or demands.
* Sustained disruption of sessions or events.
* Stalking, harassing photography or recording.
* Unwelcome physical contact or sexual attention.
* Repeated harassment of others. In general, if someone asks you to stop, then stop.
* Posting (or threatening to post) other people's personally identifying information ("doxing").
* Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history.
* Advocating for, or encouraging, any of the above behaviour.

===Reporting Guidelines===

If you believe someone is breaking this code of conduct, you may reply to them, and point to this code of conduct. Such messages may be in public or in private, whatever is most appropriate. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your concerns to event staff, a forum leader or the OSGeo Board. Serious or persistent offenders may be expelled from the event or forum by event organizers or forum leaders.

===Application===
All OSGeo projects and events should reference this Code of Conduct using text similar to:

Participants at <event> are expected to act respectfully toward others in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

or

Contributors to <project> are expected to act respectfully toward others in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

----

<End of the OSGeo Code of Conduct>

----

== Goals for Code of Conduct / Diversity Statement ==
This list has been generated to help authors of this document to agree on what we aim to achieve from this Code of Conduct / Diversity Statement. It should:
* Be applicable for: In person events such as CONFERENCES, code sprints, and related social events; as well as VIRTUAL FORUMS, such as email, IRC, wikis, etc.
* Recognise that OSGeo has a DIVERSE community. (From Draft OSGeo Diversity Statement, and others)
* Set expectation that people should act RESPECTFULLY toward each other. It is ok to respectfully disagree with people's technical ideas without attacking them personally. (From Draft OSGeo Diversity Statement, and others)
* Make it clear that we don't condone HARASSMENT or offensive behaviour, and make it clear what that is. (From O'Reilly Code of Conduct and GeekGirls Anti-Harrassment Policy)
* Outline a process for IDENTIFYING, 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. (Derived from Tweaking the Moral UI)
* Identify the ROLE of the person, or group of people responsible for ensuring the process will be followed.
* Include an escalation process for dealing with both minor and major issues. (From Draft OSGeo Conference Committee Code of Conduct)
* Couch in positive, non-threatening language. (See QGIS Diversity Statement and Code of Conduct)
* Recognise that not all participants will be native (English?) speakers and native speakers should adjust language chosen to make it easier for all participants to contribute. Eg: Try to avoid using slang. (From OGC Principles of Conduct)
* Be concise. Concise words get read more. (See QGIS Diversity Statement)

== Exemplar Sources ==

The OSGeo Code of Conduct is derived from numerous prior examples. On reading the prior material, you can see how the documents have been improving over time.

===OGC Principles of Conduct===

;Source: http://www.opengeospatial.org/ogc/policies/conduct
;Vintage: 2007
;Derived from: https://tools.ietf.org/html/rfc3184 , Vintage: 2001

;Comments
* PRO: (cameronshorter) Recognises the need to be inclusive, by making allowances for people who are not speaking in their native language.
* PRO: (cameronshorter) Encourages people to debate and potentially disagree on ideas, without attacking people personally.
* CON: (cameronshorter) Too verbose.

===Geek Feminism Template Anti Harassment Policy===

;Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment_policy

;Vintage: 2010

;Comments:
* PRO: (cameronshorter) Provides customisable version.
* PRO: (cameronshorter) Provides short/medium/long version
* PRO: (cameronshorter) Contains internal guidance for conference staff on how to handle harassment reports
* CON: (cameronshorter) Focuses only on sexual harassment, doesn't cover other topics such non-native speakers, be respectful (in general, to all).
* CON: (cameronshorter) Language of some later CoC statements are less confrontational

===FOSS4G 2015 NA and FOSS4G 2015 Code of Conduct===

;Source: https://2015.foss4g-na.org/code-conduct, downloaded 24 March 2015, derived from others, like: http://jsconf.com/codeofconduct.html and http://confcodeofconduct.com/
;Similar Source: http://2015.foss4g.org/about/codeofconduct

;Vintage: 2012

;Comments:
:* PRO: (cameronshorter) Starts with a tick-box version which can be used during registration of an event.
:* CON: (cameronshorter) Language has interpreted by some as confrontational, and could be interpreted as implying assumption of guilt.
:* CON: (cameronshorter) It would be better if this statement could be made shorter.

=== O'Reilly Code of Conduct ===

;Source: http://www.oreilly.com/conferences/code-of-conduct.html, downloaded 24 March 2015

;Vintage: 2012

;Comments
* PRO: (cameronshorter) It makes good use of positive language
* CON: (cameronshorter) This is missing a description of graduated escalation process, and how a report would be handled.
* CON: (cameronshorter) Focuses on conference venues. Later documents cover on-line communication better.

=== QGIS Diversity Statement ===

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/diversitystatement.html
;Second Source: https://qgis2015.wordpress.com

; Comments:
* PRO: (cameronshorter) States acceptance of diversity without singling out all the possible variants of diversity (race, religion, gender, ...)
* PRO: (cameronshorter) Concise.
* CON: (cameronshorter) Doesn't cover other Code of Conduct items, such as what is/is not acceptable.

=== QGIS Code of Conduct ===

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/codeofconduct.html
;Derived from: [https://www.djangoproject.com/conduct/ Django Code of Conduct] and Speak Up Code of Conduct.
;Based on [http://web.archive.org/web/20121204215836/http://speakup.io/coc.html SpeakUp CoC] and https://www.djangoproject.com/conduct/
;Vintage: 2012/2013
; Comments
* PRO: (cameronshorter) Written in positive language
* CON: (cameronshorter) Too verbose

===Debian diversity statement===

; Source: https://www.debian.org/intro/diversity

; Vintage: April 2014

;Comments
*

===Debian Code of Conduct===

; Vintage: April 2014
;Source: https://www.debian.org/code_of_conduct
;Comments:
* PRO: (johanvdw) I added these Debian references because I like the style which is used in the code of conduct for Debian: short bold bullet point with some more information afterwards (like the qgis version).;
* PRO (johanvdw) I also think the second item '''"assume good faith"''' is a very important one, which is missing from the current proposal.
* PRO (cameronshorter) I like the "try to be concise" - which is a form of respect to others.
* PRO (cameronshorter) This contains a graduated escalation process providing guidance on dealing with both minor and major issues.
* PRO (cameronshorter) This contains a version number, such which can be referenced as a point in time, and such that we can identify when to upgrade to a newer version of a Code Of Conduct.
* CON (cameronshorter) This focuses on online communications and doesn't address issues at face-to-face events as well.

=== Apache Code of Conduct ===

; Source: https://www.apache.org/foundation/policies/conduct.html, retrieved April 2015

Apache contains a separate Anti Harassment Policy, derived from the Geek Feminism Anti Harassment Policy.

; Source: https://www.apache.org/foundation/policies/anti-harassment.html

;Vintage: December 2014
; Comments:
* PRO: This addresses a few more use cases not covered by Debian, such as Don't share private emails in a public forum.
* CON: This CoC is missing a version number, such that is can be referenced by version.
* CON: States that English is the primary language - OSGeo has forums in other languages.
* CON: In places, text repeats itself (in particular, under the "Reporting Guidelines" section).

=== Draft OSGeo Board Diversity Statement ===

;Source: http://wiki.osgeo.org/index.php?title=Diversity&oldid=82976
;Original Briefer Source: http://wiki.osgeo.org/index.php?title=Diversity&oldid=81445

=== Draft OSGeo Conference Committee Code of Conduct ===

; Source: http://lists.osgeo.org/pipermail/conference_dev/2015-January/002851.html, 16 January 2015

== Further References ==

* Tweaking the Moral UI by CHRISTINA WODTKE, http://alistapart.com/article/tweaking-the-moral-ui, downloaded 24 March 2015

== Code of Conduct Workflow Discussions ==

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''

Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events?
-- not sure how to deal w/ this retroactively / for ongoing projects
- Would it be possibly to codify/package CoC implementation ideas/methods?
- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds
- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations
- OSM/F as an example of a place where support might be needed; consider joining, perhaps...
- Not going to come up with the full process today but going to organize “To-Dos”
- Focus on OSGEO
- Different groups deal with enforcement in different ways.
- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)
- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement
- Checklists to create: (1) reporting guidelines (2) incident reports
-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)
- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)
- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

Resources from other groups:

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/
Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/
Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports
Source: http://docs.puppetlabs.com/community/community_guidelines.html
Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 ( I think it should be tracked but I am worried about it being public facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/
Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
[[Category: Board]]
[[Category:Conference Committee]]

Code Of Conduct

2015-06-06T20:44:18Z

Wiki-RhoBott: /* Code of Conduct Workflow Discussions */

Please refer to the official version of this wiki page at: http://www.osgeo.org/code_of_conduct .

This page includes reference to prior material and comments applied during the development. (For history, refer to the [[Diversity]] page).
The official version 1.0 of the Code of Conduct was taken from: http://wiki.osgeo.org/index.php?title=Code_Of_Conduct&diff=84231&oldid=84214

==OSGeo Code of Conduct==

Version: 1.0

Date: May 2015

===Introduction===

This code of conduct governs how we behave in any OSGeo forum or event and whenever we will be judged by our actions. We expect it to be honored by everyone who participates in the OSGeo community formally or informally, or claims any affiliation with the OSGeo Foundation.

It applies to in-person events (such as conferences and related social events), IRC, public and private mailing lists, the issue tracker, the wiki, blogs, Twitter, and any other forums which the community uses for communication and interactions.

This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in the letter, so that it can enrich all of us and the technical communities in which we participate.

===Diversity Statement===

OSGeo welcomes and encourages participation by everyone. We are committed to being a community that everyone feels good about joining, and we will always work to treat everyone well. No matter how you identify yourself or how others perceive you: we welcome you.

===Specific Guidelines===

We strive to:

;Be open.
: We invite anyone to participate in our community. We preferably use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also makes sure that any inadvertent mistakes made by people answering will be more easily detected and corrected.

;Be empathetic, welcoming, friendly, and patient.
:We work together to resolve conflict, assume good intentions, and do our best to act in an empathetic fashion. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one. Note that we have a multi-cultural, multi-lingual community and some of us are non-native speakers. We should be respectful when dealing with other community members as well as with people outside our community.

;Be collaborative. : Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of OSGeo, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.

;Be inquisitive. : Nobody knows everything! Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful, within the context of our shared goal of improving OSGeo.

;Be careful in the words that we choose. : Whether we are participating as professionals or volunteers, we value professionalism in all interactions, and take responsibility for our own speech. Be kind to others. Do not insult or put down other participants.

;Be concise. : Keep in mind that what you write once will be read by hundreds of persons. Writing a short email means people can understand the conversation as efficiently as possible. Short emails should always strive to be empathetic, welcoming, friendly and patient. When a long explanation is necessary, consider adding a summary.

: Try to bring new ideas to a conversation so that each mail adds something unique to the thread, keeping in mind that the rest of the thread still contains the other messages with arguments that have already been made.

: Try to stay on topic, especially in discussions that are already fairly large.

; Step down considerately.
: Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project's goals or achievements. Likewise, community members should respect any individual's choice to leave the project.

===Anti-Harassment===

Harassment and other exclusionary behaviour are not acceptable. This includes, but is not limited to:

* Personal insults or discriminatory jokes and language, especially those using racist or sexist terms.
* Offensive comments, excessive or unnecessary profanity.
* Intimidation, violent threats or demands.
* Sustained disruption of sessions or events.
* Stalking, harassing photography or recording.
* Unwelcome physical contact or sexual attention.
* Repeated harassment of others. In general, if someone asks you to stop, then stop.
* Posting (or threatening to post) other people's personally identifying information ("doxing").
* Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history.
* Advocating for, or encouraging, any of the above behaviour.

===Reporting Guidelines===

If you believe someone is breaking this code of conduct, you may reply to them, and point to this code of conduct. Such messages may be in public or in private, whatever is most appropriate. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your concerns to event staff, a forum leader or the OSGeo Board. Serious or persistent offenders may be expelled from the event or forum by event organizers or forum leaders.

===Application===
All OSGeo projects and events should reference this Code of Conduct using text similar to:

Participants at <event> are expected to act respectfully toward others in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

or

Contributors to <project> are expected to act respectfully toward others in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

----

<End of the OSGeo Code of Conduct>

----

== Goals for Code of Conduct / Diversity Statement ==
This list has been generated to help authors of this document to agree on what we aim to achieve from this Code of Conduct / Diversity Statement. It should:
* Be applicable for: In person events such as CONFERENCES, code sprints, and related social events; as well as VIRTUAL FORUMS, such as email, IRC, wikis, etc.
* Recognise that OSGeo has a DIVERSE community. (From Draft OSGeo Diversity Statement, and others)
* Set expectation that people should act RESPECTFULLY toward each other. It is ok to respectfully disagree with people's technical ideas without attacking them personally. (From Draft OSGeo Diversity Statement, and others)
* Make it clear that we don't condone HARASSMENT or offensive behaviour, and make it clear what that is. (From O'Reilly Code of Conduct and GeekGirls Anti-Harrassment Policy)
* Outline a process for IDENTIFYING, 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. (Derived from Tweaking the Moral UI)
* Identify the ROLE of the person, or group of people responsible for ensuring the process will be followed.
* Include an escalation process for dealing with both minor and major issues. (From Draft OSGeo Conference Committee Code of Conduct)
* Couch in positive, non-threatening language. (See QGIS Diversity Statement and Code of Conduct)
* Recognise that not all participants will be native (English?) speakers and native speakers should adjust language chosen to make it easier for all participants to contribute. Eg: Try to avoid using slang. (From OGC Principles of Conduct)
* Be concise. Concise words get read more. (See QGIS Diversity Statement)

== Exemplar Sources ==

The OSGeo Code of Conduct is derived from numerous prior examples. On reading the prior material, you can see how the documents have been improving over time.

===OGC Principles of Conduct===

;Source: http://www.opengeospatial.org/ogc/policies/conduct
;Vintage: 2007
;Derived from: https://tools.ietf.org/html/rfc3184 , Vintage: 2001

;Comments
* PRO: (cameronshorter) Recognises the need to be inclusive, by making allowances for people who are not speaking in their native language.
* PRO: (cameronshorter) Encourages people to debate and potentially disagree on ideas, without attacking people personally.
* CON: (cameronshorter) Too verbose.

===Geek Feminism Template Anti Harassment Policy===

;Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment_policy

;Vintage: 2010

;Comments:
* PRO: (cameronshorter) Provides customisable version.
* PRO: (cameronshorter) Provides short/medium/long version
* PRO: (cameronshorter) Contains internal guidance for conference staff on how to handle harassment reports
* CON: (cameronshorter) Focuses only on sexual harassment, doesn't cover other topics such non-native speakers, be respectful (in general, to all).
* CON: (cameronshorter) Language of some later CoC statements are less confrontational

===FOSS4G 2015 NA and FOSS4G 2015 Code of Conduct===

;Source: https://2015.foss4g-na.org/code-conduct, downloaded 24 March 2015, derived from others, like: http://jsconf.com/codeofconduct.html and http://confcodeofconduct.com/
;Similar Source: http://2015.foss4g.org/about/codeofconduct

;Vintage: 2012

;Comments:
:* PRO: (cameronshorter) Starts with a tick-box version which can be used during registration of an event.
:* CON: (cameronshorter) Language has interpreted by some as confrontational, and could be interpreted as implying assumption of guilt.
:* CON: (cameronshorter) It would be better if this statement could be made shorter.

=== O'Reilly Code of Conduct ===

;Source: http://www.oreilly.com/conferences/code-of-conduct.html, downloaded 24 March 2015

;Vintage: 2012

;Comments
* PRO: (cameronshorter) It makes good use of positive language
* CON: (cameronshorter) This is missing a description of graduated escalation process, and how a report would be handled.
* CON: (cameronshorter) Focuses on conference venues. Later documents cover on-line communication better.

=== QGIS Diversity Statement ===

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/diversitystatement.html
;Second Source: https://qgis2015.wordpress.com

; Comments:
* PRO: (cameronshorter) States acceptance of diversity without singling out all the possible variants of diversity (race, religion, gender, ...)
* PRO: (cameronshorter) Concise.
* CON: (cameronshorter) Doesn't cover other Code of Conduct items, such as what is/is not acceptable.

=== QGIS Code of Conduct ===

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/codeofconduct.html
;Derived from: [https://www.djangoproject.com/conduct/ Django Code of Conduct] and Speak Up Code of Conduct.
;Based on [http://web.archive.org/web/20121204215836/http://speakup.io/coc.html SpeakUp CoC] and https://www.djangoproject.com/conduct/
;Vintage: 2012/2013
; Comments
* PRO: (cameronshorter) Written in positive language
* CON: (cameronshorter) Too verbose

===Debian diversity statement===

; Source: https://www.debian.org/intro/diversity

; Vintage: April 2014

;Comments
*

===Debian Code of Conduct===

; Vintage: April 2014
;Source: https://www.debian.org/code_of_conduct
;Comments:
* PRO: (johanvdw) I added these Debian references because I like the style which is used in the code of conduct for Debian: short bold bullet point with some more information afterwards (like the qgis version).;
* PRO (johanvdw) I also think the second item '''"assume good faith"''' is a very important one, which is missing from the current proposal.
* PRO (cameronshorter) I like the "try to be concise" - which is a form of respect to others.
* PRO (cameronshorter) This contains a graduated escalation process providing guidance on dealing with both minor and major issues.
* PRO (cameronshorter) This contains a version number, such which can be referenced as a point in time, and such that we can identify when to upgrade to a newer version of a Code Of Conduct.
* CON (cameronshorter) This focuses on online communications and doesn't address issues at face-to-face events as well.

=== Apache Code of Conduct ===

; Source: https://www.apache.org/foundation/policies/conduct.html, retrieved April 2015

Apache contains a separate Anti Harassment Policy, derived from the Geek Feminism Anti Harassment Policy.

; Source: https://www.apache.org/foundation/policies/anti-harassment.html

;Vintage: December 2014
; Comments:
* PRO: This addresses a few more use cases not covered by Debian, such as Don't share private emails in a public forum.
* CON: This CoC is missing a version number, such that is can be referenced by version.
* CON: States that English is the primary language - OSGeo has forums in other languages.
* CON: In places, text repeats itself (in particular, under the "Reporting Guidelines" section).

=== Draft OSGeo Board Diversity Statement ===

;Source: http://wiki.osgeo.org/index.php?title=Diversity&oldid=82976
;Original Briefer Source: http://wiki.osgeo.org/index.php?title=Diversity&oldid=81445

=== Draft OSGeo Conference Committee Code of Conduct ===

; Source: http://lists.osgeo.org/pipermail/conference_dev/2015-January/002851.html, 16 January 2015

== Further References ==

* Tweaking the Moral UI by CHRISTINA WODTKE, http://alistapart.com/article/tweaking-the-moral-ui, downloaded 24 March 2015

== Code of Conduct Workflow Discussions ==

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events?
-- not sure how to deal w/ this retroactively / for ongoing projects
- Would it be possibly to codify/package CoC implementation ideas/methods?
- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds
- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations
- OSM/F as an example of a place where support might be needed; consider joining, perhaps...
- Not going to come up with the full process today but going to organize “To-Dos”
- Focus on OSGEO
- Different groups deal with enforcement in different ways.
- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)
- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement
- Checklists to create: (1) reporting guidelines (2) incident reports
-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)
- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)
- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

Resources from other groups:

''' Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/
Source: https://www.drupal.org/governance/community-working-group/incident-report

'''Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/
Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports
Source: http://docs.puppetlabs.com/community/community_guidelines.html
Source: https://github.com/python/pycon-code-of-conduct?files=1

'''Language/Actions for Dealing with Banned Person
'''

''Sample Language When Banned Person Attempts to Register
''
''
Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 ( I think it should be tracked but I am worried about it being public facing)

''' When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/
Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
[[Category: Board]]
[[Category:Conference Committee]]

Code Of Conduct

2015-06-06T20:42:34Z

Wiki-RhoBott: /* Code of Conduct Workflow Discussions */

Please refer to the official version of this wiki page at: http://www.osgeo.org/code_of_conduct .

This page includes reference to prior material and comments applied during the development. (For history, refer to the [[Diversity]] page).
The official version 1.0 of the Code of Conduct was taken from: http://wiki.osgeo.org/index.php?title=Code_Of_Conduct&diff=84231&oldid=84214

==OSGeo Code of Conduct==

Version: 1.0

Date: May 2015

===Introduction===

This code of conduct governs how we behave in any OSGeo forum or event and whenever we will be judged by our actions. We expect it to be honored by everyone who participates in the OSGeo community formally or informally, or claims any affiliation with the OSGeo Foundation.

It applies to in-person events (such as conferences and related social events), IRC, public and private mailing lists, the issue tracker, the wiki, blogs, Twitter, and any other forums which the community uses for communication and interactions.

This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in the letter, so that it can enrich all of us and the technical communities in which we participate.

===Diversity Statement===

OSGeo welcomes and encourages participation by everyone. We are committed to being a community that everyone feels good about joining, and we will always work to treat everyone well. No matter how you identify yourself or how others perceive you: we welcome you.

===Specific Guidelines===

We strive to:

;Be open.
: We invite anyone to participate in our community. We preferably use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also makes sure that any inadvertent mistakes made by people answering will be more easily detected and corrected.

;Be empathetic, welcoming, friendly, and patient.
:We work together to resolve conflict, assume good intentions, and do our best to act in an empathetic fashion. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one. Note that we have a multi-cultural, multi-lingual community and some of us are non-native speakers. We should be respectful when dealing with other community members as well as with people outside our community.

;Be collaborative. : Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of OSGeo, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.

;Be inquisitive. : Nobody knows everything! Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful, within the context of our shared goal of improving OSGeo.

;Be careful in the words that we choose. : Whether we are participating as professionals or volunteers, we value professionalism in all interactions, and take responsibility for our own speech. Be kind to others. Do not insult or put down other participants.

;Be concise. : Keep in mind that what you write once will be read by hundreds of persons. Writing a short email means people can understand the conversation as efficiently as possible. Short emails should always strive to be empathetic, welcoming, friendly and patient. When a long explanation is necessary, consider adding a summary.

: Try to bring new ideas to a conversation so that each mail adds something unique to the thread, keeping in mind that the rest of the thread still contains the other messages with arguments that have already been made.

: Try to stay on topic, especially in discussions that are already fairly large.

; Step down considerately.
: Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project's goals or achievements. Likewise, community members should respect any individual's choice to leave the project.

===Anti-Harassment===

Harassment and other exclusionary behaviour are not acceptable. This includes, but is not limited to:

* Personal insults or discriminatory jokes and language, especially those using racist or sexist terms.
* Offensive comments, excessive or unnecessary profanity.
* Intimidation, violent threats or demands.
* Sustained disruption of sessions or events.
* Stalking, harassing photography or recording.
* Unwelcome physical contact or sexual attention.
* Repeated harassment of others. In general, if someone asks you to stop, then stop.
* Posting (or threatening to post) other people's personally identifying information ("doxing").
* Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history.
* Advocating for, or encouraging, any of the above behaviour.

===Reporting Guidelines===

If you believe someone is breaking this code of conduct, you may reply to them, and point to this code of conduct. Such messages may be in public or in private, whatever is most appropriate. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your concerns to event staff, a forum leader or the OSGeo Board. Serious or persistent offenders may be expelled from the event or forum by event organizers or forum leaders.

===Application===
All OSGeo projects and events should reference this Code of Conduct using text similar to:

Participants at <event> are expected to act respectfully toward others in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

or

Contributors to <project> are expected to act respectfully toward others in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

----

<End of the OSGeo Code of Conduct>

----

== Goals for Code of Conduct / Diversity Statement ==
This list has been generated to help authors of this document to agree on what we aim to achieve from this Code of Conduct / Diversity Statement. It should:
* Be applicable for: In person events such as CONFERENCES, code sprints, and related social events; as well as VIRTUAL FORUMS, such as email, IRC, wikis, etc.
* Recognise that OSGeo has a DIVERSE community. (From Draft OSGeo Diversity Statement, and others)
* Set expectation that people should act RESPECTFULLY toward each other. It is ok to respectfully disagree with people's technical ideas without attacking them personally. (From Draft OSGeo Diversity Statement, and others)
* Make it clear that we don't condone HARASSMENT or offensive behaviour, and make it clear what that is. (From O'Reilly Code of Conduct and GeekGirls Anti-Harrassment Policy)
* Outline a process for IDENTIFYING, 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. (Derived from Tweaking the Moral UI)
* Identify the ROLE of the person, or group of people responsible for ensuring the process will be followed.
* Include an escalation process for dealing with both minor and major issues. (From Draft OSGeo Conference Committee Code of Conduct)
* Couch in positive, non-threatening language. (See QGIS Diversity Statement and Code of Conduct)
* Recognise that not all participants will be native (English?) speakers and native speakers should adjust language chosen to make it easier for all participants to contribute. Eg: Try to avoid using slang. (From OGC Principles of Conduct)
* Be concise. Concise words get read more. (See QGIS Diversity Statement)

== Exemplar Sources ==

The OSGeo Code of Conduct is derived from numerous prior examples. On reading the prior material, you can see how the documents have been improving over time.

===OGC Principles of Conduct===

;Source: http://www.opengeospatial.org/ogc/policies/conduct
;Vintage: 2007
;Derived from: https://tools.ietf.org/html/rfc3184 , Vintage: 2001

;Comments
* PRO: (cameronshorter) Recognises the need to be inclusive, by making allowances for people who are not speaking in their native language.
* PRO: (cameronshorter) Encourages people to debate and potentially disagree on ideas, without attacking people personally.
* CON: (cameronshorter) Too verbose.

===Geek Feminism Template Anti Harassment Policy===

;Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment_policy

;Vintage: 2010

;Comments:
* PRO: (cameronshorter) Provides customisable version.
* PRO: (cameronshorter) Provides short/medium/long version
* PRO: (cameronshorter) Contains internal guidance for conference staff on how to handle harassment reports
* CON: (cameronshorter) Focuses only on sexual harassment, doesn't cover other topics such non-native speakers, be respectful (in general, to all).
* CON: (cameronshorter) Language of some later CoC statements are less confrontational

===FOSS4G 2015 NA and FOSS4G 2015 Code of Conduct===

;Source: https://2015.foss4g-na.org/code-conduct, downloaded 24 March 2015, derived from others, like: http://jsconf.com/codeofconduct.html and http://confcodeofconduct.com/
;Similar Source: http://2015.foss4g.org/about/codeofconduct

;Vintage: 2012

;Comments:
:* PRO: (cameronshorter) Starts with a tick-box version which can be used during registration of an event.
:* CON: (cameronshorter) Language has interpreted by some as confrontational, and could be interpreted as implying assumption of guilt.
:* CON: (cameronshorter) It would be better if this statement could be made shorter.

=== O'Reilly Code of Conduct ===

;Source: http://www.oreilly.com/conferences/code-of-conduct.html, downloaded 24 March 2015

;Vintage: 2012

;Comments
* PRO: (cameronshorter) It makes good use of positive language
* CON: (cameronshorter) This is missing a description of graduated escalation process, and how a report would be handled.
* CON: (cameronshorter) Focuses on conference venues. Later documents cover on-line communication better.

=== QGIS Diversity Statement ===

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/diversitystatement.html
;Second Source: https://qgis2015.wordpress.com

; Comments:
* PRO: (cameronshorter) States acceptance of diversity without singling out all the possible variants of diversity (race, religion, gender, ...)
* PRO: (cameronshorter) Concise.
* CON: (cameronshorter) Doesn't cover other Code of Conduct items, such as what is/is not acceptable.

=== QGIS Code of Conduct ===

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/codeofconduct.html
;Derived from: [https://www.djangoproject.com/conduct/ Django Code of Conduct] and Speak Up Code of Conduct.
;Based on [http://web.archive.org/web/20121204215836/http://speakup.io/coc.html SpeakUp CoC] and https://www.djangoproject.com/conduct/
;Vintage: 2012/2013
; Comments
* PRO: (cameronshorter) Written in positive language
* CON: (cameronshorter) Too verbose

===Debian diversity statement===

; Source: https://www.debian.org/intro/diversity

; Vintage: April 2014

;Comments
*

===Debian Code of Conduct===

; Vintage: April 2014
;Source: https://www.debian.org/code_of_conduct
;Comments:
* PRO: (johanvdw) I added these Debian references because I like the style which is used in the code of conduct for Debian: short bold bullet point with some more information afterwards (like the qgis version).;
* PRO (johanvdw) I also think the second item '''"assume good faith"''' is a very important one, which is missing from the current proposal.
* PRO (cameronshorter) I like the "try to be concise" - which is a form of respect to others.
* PRO (cameronshorter) This contains a graduated escalation process providing guidance on dealing with both minor and major issues.
* PRO (cameronshorter) This contains a version number, such which can be referenced as a point in time, and such that we can identify when to upgrade to a newer version of a Code Of Conduct.
* CON (cameronshorter) This focuses on online communications and doesn't address issues at face-to-face events as well.

=== Apache Code of Conduct ===

; Source: https://www.apache.org/foundation/policies/conduct.html, retrieved April 2015

Apache contains a separate Anti Harassment Policy, derived from the Geek Feminism Anti Harassment Policy.

; Source: https://www.apache.org/foundation/policies/anti-harassment.html

;Vintage: December 2014
; Comments:
* PRO: This addresses a few more use cases not covered by Debian, such as Don't share private emails in a public forum.
* CON: This CoC is missing a version number, such that is can be referenced by version.
* CON: States that English is the primary language - OSGeo has forums in other languages.
* CON: In places, text repeats itself (in particular, under the "Reporting Guidelines" section).

=== Draft OSGeo Board Diversity Statement ===

;Source: http://wiki.osgeo.org/index.php?title=Diversity&oldid=82976
;Original Briefer Source: http://wiki.osgeo.org/index.php?title=Diversity&oldid=81445

=== Draft OSGeo Conference Committee Code of Conduct ===

; Source: http://lists.osgeo.org/pipermail/conference_dev/2015-January/002851.html, 16 January 2015

== Further References ==

* Tweaking the Moral UI by CHRISTINA WODTKE, http://alistapart.com/article/tweaking-the-moral-ui, downloaded 24 March 2015

== Code of Conduct Workflow Discussions ==

'''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015
'''
''Some notes from our discussion
''
- Consider adding CoC to RFP for all upcoming OSGeo events?
-- not sure how to deal w/ this retroactively / for ongoing projects
- Would it be possibly to codify/package CoC implementation ideas/methods?
- Need to make sure that we engage a variety of people in these discussions; different cultural contexts/backgrounds
- Remember that moderators (for listservs, of etc) need support and resources for dealing w/ difficult situations
- OSM/F as an example of a place where support might be needed; consider joining, perhaps...
- Not going to come up with the full process today but going to organize “To-Dos”
- Focus on OSGEO
- Different groups deal with enforcement in different ways.
- OSM has a mailing list policy buried in the wiki somewhere (so buried I couldn’t find it)
- open forum enforces the status quo

to do's
- Form a code of conduct committee in OSGEO; purpose is (1) Knowledge transfer year to year (2) Deal with enforcement
- Checklists to create: (1) reporting guidelines (2) incident reports
-The code of conduct should be part of the RFP template for the FOSS4G conference process; (1) have suggestions/guidelines (2) part of the application will state how the organizers will implement the code of conduct (part of RFP scoring)
- Split up the pieces -- figure out how to trickle CoC into all aspects of the organization (Conferences, mailing lists, IRC, etc.)
- Process of projects joining OSGEO be comply with CoC

Proposed MAJOR next step:

Consider creating a formal Code of Conduct committee to formally handle creating reporting guidelines, responding to incidents, enforcing the CoC (including creating language and identifying actions for dealing with the perpetrators of incidents, tracking warned or suspended individuals over time (institutional knowledge), deciding when to allow suspended individuals back to OSGeo spaces (events, listservs, etc).

Resources from other groups:

'''- Reporting Guidelines
'''

Source: https://www.djangoproject.com/conduct/reporting/
Source: https://www.drupal.org/governance/community-working-group/incident-report

'''- Responding/Enforcement
''
'Source: https://www.djangoproject.com/conduct/enforcement-manual/
Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports
Source: http://docs.puppetlabs.com/community/community_guidelines.html
Source: https://github.com/python/pycon-code-of-conduct?files=1

'''- Language/Actions for Dealing with Banned Person
'''

'''Sample Language When Banned Person Attempts to Register
'''

Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

'''

'''Keeping Track of Banned Individuals'''
'''
Source: https://www.noisebridge.net/wiki/86 ( I think it should be tracked but I am worried about it being public facing)

'''- When/How to Let Banned People Come Back
Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/
Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
[[Category: Board]]
[[Category:Conference Committee]]

Code Of Conduct

2015-06-06T15:49:00Z

Wiki-RhoBott: /* Code of Conduct Workflow Discussions */

Please refer to the official version of this wiki page at: http://www.osgeo.org/code_of_conduct .

This page includes reference to prior material and comments applied during the development. (For history, refer to the [[Diversity]] page).
The official version 1.0 of the Code of Conduct was taken from: http://wiki.osgeo.org/index.php?title=Code_Of_Conduct&diff=84231&oldid=84214

==OSGeo Code of Conduct==

Version: 1.0

Date: May 2015

===Introduction===

This code of conduct governs how we behave in any OSGeo forum or event and whenever we will be judged by our actions. We expect it to be honored by everyone who participates in the OSGeo community formally or informally, or claims any affiliation with the OSGeo Foundation.

It applies to in-person events (such as conferences and related social events), IRC, public and private mailing lists, the issue tracker, the wiki, blogs, Twitter, and any other forums which the community uses for communication and interactions.

This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in the letter, so that it can enrich all of us and the technical communities in which we participate.

===Diversity Statement===

OSGeo welcomes and encourages participation by everyone. We are committed to being a community that everyone feels good about joining, and we will always work to treat everyone well. No matter how you identify yourself or how others perceive you: we welcome you.

===Specific Guidelines===

We strive to:

;Be open.
: We invite anyone to participate in our community. We preferably use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also makes sure that any inadvertent mistakes made by people answering will be more easily detected and corrected.

;Be empathetic, welcoming, friendly, and patient.
:We work together to resolve conflict, assume good intentions, and do our best to act in an empathetic fashion. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one. Note that we have a multi-cultural, multi-lingual community and some of us are non-native speakers. We should be respectful when dealing with other community members as well as with people outside our community.

;Be collaborative. : Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of OSGeo, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.

;Be inquisitive. : Nobody knows everything! Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful, within the context of our shared goal of improving OSGeo.

;Be careful in the words that we choose. : Whether we are participating as professionals or volunteers, we value professionalism in all interactions, and take responsibility for our own speech. Be kind to others. Do not insult or put down other participants.

;Be concise. : Keep in mind that what you write once will be read by hundreds of persons. Writing a short email means people can understand the conversation as efficiently as possible. Short emails should always strive to be empathetic, welcoming, friendly and patient. When a long explanation is necessary, consider adding a summary.

: Try to bring new ideas to a conversation so that each mail adds something unique to the thread, keeping in mind that the rest of the thread still contains the other messages with arguments that have already been made.

: Try to stay on topic, especially in discussions that are already fairly large.

; Step down considerately.
: Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project's goals or achievements. Likewise, community members should respect any individual's choice to leave the project.

===Anti-Harassment===

Harassment and other exclusionary behaviour are not acceptable. This includes, but is not limited to:

* Personal insults or discriminatory jokes and language, especially those using racist or sexist terms.
* Offensive comments, excessive or unnecessary profanity.
* Intimidation, violent threats or demands.
* Sustained disruption of sessions or events.
* Stalking, harassing photography or recording.
* Unwelcome physical contact or sexual attention.
* Repeated harassment of others. In general, if someone asks you to stop, then stop.
* Posting (or threatening to post) other people's personally identifying information ("doxing").
* Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history.
* Advocating for, or encouraging, any of the above behaviour.

===Reporting Guidelines===

If you believe someone is breaking this code of conduct, you may reply to them, and point to this code of conduct. Such messages may be in public or in private, whatever is most appropriate. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your concerns to event staff, a forum leader or the OSGeo Board. Serious or persistent offenders may be expelled from the event or forum by event organizers or forum leaders.

===Application===
All OSGeo projects and events should reference this Code of Conduct using text similar to:

Participants at <event> are expected to act respectfully toward others in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

or

Contributors to <project> are expected to act respectfully toward others in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

----

<End of the OSGeo Code of Conduct>

----

== Goals for Code of Conduct / Diversity Statement ==
This list has been generated to help authors of this document to agree on what we aim to achieve from this Code of Conduct / Diversity Statement. It should:
* Be applicable for: In person events such as CONFERENCES, code sprints, and related social events; as well as VIRTUAL FORUMS, such as email, IRC, wikis, etc.
* Recognise that OSGeo has a DIVERSE community. (From Draft OSGeo Diversity Statement, and others)
* Set expectation that people should act RESPECTFULLY toward each other. It is ok to respectfully disagree with people's technical ideas without attacking them personally. (From Draft OSGeo Diversity Statement, and others)
* Make it clear that we don't condone HARASSMENT or offensive behaviour, and make it clear what that is. (From O'Reilly Code of Conduct and GeekGirls Anti-Harrassment Policy)
* Outline a process for IDENTIFYING, 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. (Derived from Tweaking the Moral UI)
* Identify the ROLE of the person, or group of people responsible for ensuring the process will be followed.
* Include an escalation process for dealing with both minor and major issues. (From Draft OSGeo Conference Committee Code of Conduct)
* Couch in positive, non-threatening language. (See QGIS Diversity Statement and Code of Conduct)
* Recognise that not all participants will be native (English?) speakers and native speakers should adjust language chosen to make it easier for all participants to contribute. Eg: Try to avoid using slang. (From OGC Principles of Conduct)
* Be concise. Concise words get read more. (See QGIS Diversity Statement)

== Exemplar Sources ==

The OSGeo Code of Conduct is derived from numerous prior examples. On reading the prior material, you can see how the documents have been improving over time.

===OGC Principles of Conduct===

;Source: http://www.opengeospatial.org/ogc/policies/conduct
;Vintage: 2007
;Derived from: https://tools.ietf.org/html/rfc3184 , Vintage: 2001

;Comments
* PRO: (cameronshorter) Recognises the need to be inclusive, by making allowances for people who are not speaking in their native language.
* PRO: (cameronshorter) Encourages people to debate and potentially disagree on ideas, without attacking people personally.
* CON: (cameronshorter) Too verbose.

===Geek Feminism Template Anti Harassment Policy===

;Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment_policy

;Vintage: 2010

;Comments:
* PRO: (cameronshorter) Provides customisable version.
* PRO: (cameronshorter) Provides short/medium/long version
* PRO: (cameronshorter) Contains internal guidance for conference staff on how to handle harassment reports
* CON: (cameronshorter) Focuses only on sexual harassment, doesn't cover other topics such non-native speakers, be respectful (in general, to all).
* CON: (cameronshorter) Language of some later CoC statements are less confrontational

===FOSS4G 2015 NA and FOSS4G 2015 Code of Conduct===

;Source: https://2015.foss4g-na.org/code-conduct, downloaded 24 March 2015, derived from others, like: http://jsconf.com/codeofconduct.html and http://confcodeofconduct.com/
;Similar Source: http://2015.foss4g.org/about/codeofconduct

;Vintage: 2012

;Comments:
:* PRO: (cameronshorter) Starts with a tick-box version which can be used during registration of an event.
:* CON: (cameronshorter) Language has interpreted by some as confrontational, and could be interpreted as implying assumption of guilt.
:* CON: (cameronshorter) It would be better if this statement could be made shorter.

=== O'Reilly Code of Conduct ===

;Source: http://www.oreilly.com/conferences/code-of-conduct.html, downloaded 24 March 2015

;Vintage: 2012

;Comments
* PRO: (cameronshorter) It makes good use of positive language
* CON: (cameronshorter) This is missing a description of graduated escalation process, and how a report would be handled.
* CON: (cameronshorter) Focuses on conference venues. Later documents cover on-line communication better.

=== QGIS Diversity Statement ===

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/diversitystatement.html
;Second Source: https://qgis2015.wordpress.com

; Comments:
* PRO: (cameronshorter) States acceptance of diversity without singling out all the possible variants of diversity (race, religion, gender, ...)
* PRO: (cameronshorter) Concise.
* CON: (cameronshorter) Doesn't cover other Code of Conduct items, such as what is/is not acceptable.

=== QGIS Code of Conduct ===

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/codeofconduct.html
;Derived from: [https://www.djangoproject.com/conduct/ Django Code of Conduct] and Speak Up Code of Conduct.
;Based on [http://web.archive.org/web/20121204215836/http://speakup.io/coc.html SpeakUp CoC] and https://www.djangoproject.com/conduct/
;Vintage: 2012/2013
; Comments
* PRO: (cameronshorter) Written in positive language
* CON: (cameronshorter) Too verbose

===Debian diversity statement===

; Source: https://www.debian.org/intro/diversity

; Vintage: April 2014

;Comments
*

===Debian Code of Conduct===

; Vintage: April 2014
;Source: https://www.debian.org/code_of_conduct
;Comments:
* PRO: (johanvdw) I added these Debian references because I like the style which is used in the code of conduct for Debian: short bold bullet point with some more information afterwards (like the qgis version).;
* PRO (johanvdw) I also think the second item '''"assume good faith"''' is a very important one, which is missing from the current proposal.
* PRO (cameronshorter) I like the "try to be concise" - which is a form of respect to others.
* PRO (cameronshorter) This contains a graduated escalation process providing guidance on dealing with both minor and major issues.
* PRO (cameronshorter) This contains a version number, such which can be referenced as a point in time, and such that we can identify when to upgrade to a newer version of a Code Of Conduct.
* CON (cameronshorter) This focuses on online communications and doesn't address issues at face-to-face events as well.

=== Apache Code of Conduct ===

; Source: https://www.apache.org/foundation/policies/conduct.html, retrieved April 2015

Apache contains a separate Anti Harassment Policy, derived from the Geek Feminism Anti Harassment Policy.

; Source: https://www.apache.org/foundation/policies/anti-harassment.html

;Vintage: December 2014
; Comments:
* PRO: This addresses a few more use cases not covered by Debian, such as Don't share private emails in a public forum.
* CON: This CoC is missing a version number, such that is can be referenced by version.
* CON: States that English is the primary language - OSGeo has forums in other languages.
* CON: In places, text repeats itself (in particular, under the "Reporting Guidelines" section).

=== Draft OSGeo Board Diversity Statement ===

;Source: http://wiki.osgeo.org/index.php?title=Diversity&oldid=82976
;Original Briefer Source: http://wiki.osgeo.org/index.php?title=Diversity&oldid=81445

=== Draft OSGeo Conference Committee Code of Conduct ===

; Source: http://lists.osgeo.org/pipermail/conference_dev/2015-January/002851.html, 16 January 2015

== Further References ==

* Tweaking the Moral UI by CHRISTINA WODTKE, http://alistapart.com/article/tweaking-the-moral-ui, downloaded 24 March 2015

== Code of Conduct Workflow Discussions ==

SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015

NEXT STEPS To Discuss:

1 - Code of Conduct formal committee (do we need one? if so, how do we formalize it?)
could be a joint committee covering both OSM and OSGeo foundations
formalized by approval from each Board

2 - Reporting Guidelines

;Source: https://www.djangoproject.com/conduct/reporting/
;Source: https://www.drupal.org/governance/community-working-group/incident-report

3 - Responding/Enforcement
;Source: https://www.djangoproject.com/conduct/enforcement-manual/
;Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports
;Source: http://docs.puppetlabs.com/community/community_guidelines.html
;Source: https://github.com/python/pycon-code-of-conduct?files=1

4 - Language/Actions for Dealing with Banned Person

'''Sample Language When Banned Person Attempts to Register
'''

Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

5 - Keeping Track of Banned Individuals
;Source: https://www.noisebridge.net/wiki/86 ( I think it should be tracked but I am worried about it being public facing)

6 - When/How to Let Banned People Come Back
;Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/
;Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
[[Category: Board]]
[[Category:Conference Committee]]

Code Of Conduct

2015-06-06T15:05:47Z

Wiki-RhoBott: /* Code of Conduct Workflow Discussions */

Please refer to the official version of this wiki page at: http://www.osgeo.org/code_of_conduct .

This page includes reference to prior material and comments applied during the development. (For history, refer to the [[Diversity]] page).
The official version 1.0 of the Code of Conduct was taken from: http://wiki.osgeo.org/index.php?title=Code_Of_Conduct&diff=84231&oldid=84214

==OSGeo Code of Conduct==

Version: 1.0

Date: May 2015

===Introduction===

This code of conduct governs how we behave in any OSGeo forum or event and whenever we will be judged by our actions. We expect it to be honored by everyone who participates in the OSGeo community formally or informally, or claims any affiliation with the OSGeo Foundation.

It applies to in-person events (such as conferences and related social events), IRC, public and private mailing lists, the issue tracker, the wiki, blogs, Twitter, and any other forums which the community uses for communication and interactions.

This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in the letter, so that it can enrich all of us and the technical communities in which we participate.

===Diversity Statement===

OSGeo welcomes and encourages participation by everyone. We are committed to being a community that everyone feels good about joining, and we will always work to treat everyone well. No matter how you identify yourself or how others perceive you: we welcome you.

===Specific Guidelines===

We strive to:

;Be open.
: We invite anyone to participate in our community. We preferably use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also makes sure that any inadvertent mistakes made by people answering will be more easily detected and corrected.

;Be empathetic, welcoming, friendly, and patient.
:We work together to resolve conflict, assume good intentions, and do our best to act in an empathetic fashion. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one. Note that we have a multi-cultural, multi-lingual community and some of us are non-native speakers. We should be respectful when dealing with other community members as well as with people outside our community.

;Be collaborative. : Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of OSGeo, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.

;Be inquisitive. : Nobody knows everything! Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful, within the context of our shared goal of improving OSGeo.

;Be careful in the words that we choose. : Whether we are participating as professionals or volunteers, we value professionalism in all interactions, and take responsibility for our own speech. Be kind to others. Do not insult or put down other participants.

;Be concise. : Keep in mind that what you write once will be read by hundreds of persons. Writing a short email means people can understand the conversation as efficiently as possible. Short emails should always strive to be empathetic, welcoming, friendly and patient. When a long explanation is necessary, consider adding a summary.

: Try to bring new ideas to a conversation so that each mail adds something unique to the thread, keeping in mind that the rest of the thread still contains the other messages with arguments that have already been made.

: Try to stay on topic, especially in discussions that are already fairly large.

; Step down considerately.
: Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project's goals or achievements. Likewise, community members should respect any individual's choice to leave the project.

===Anti-Harassment===

Harassment and other exclusionary behaviour are not acceptable. This includes, but is not limited to:

* Personal insults or discriminatory jokes and language, especially those using racist or sexist terms.
* Offensive comments, excessive or unnecessary profanity.
* Intimidation, violent threats or demands.
* Sustained disruption of sessions or events.
* Stalking, harassing photography or recording.
* Unwelcome physical contact or sexual attention.
* Repeated harassment of others. In general, if someone asks you to stop, then stop.
* Posting (or threatening to post) other people's personally identifying information ("doxing").
* Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history.
* Advocating for, or encouraging, any of the above behaviour.

===Reporting Guidelines===

If you believe someone is breaking this code of conduct, you may reply to them, and point to this code of conduct. Such messages may be in public or in private, whatever is most appropriate. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your concerns to event staff, a forum leader or the OSGeo Board. Serious or persistent offenders may be expelled from the event or forum by event organizers or forum leaders.

===Application===
All OSGeo projects and events should reference this Code of Conduct using text similar to:

Participants at <event> are expected to act respectfully toward others in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

or

Contributors to <project> are expected to act respectfully toward others in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

----

<End of the OSGeo Code of Conduct>

----

== Goals for Code of Conduct / Diversity Statement ==
This list has been generated to help authors of this document to agree on what we aim to achieve from this Code of Conduct / Diversity Statement. It should:
* Be applicable for: In person events such as CONFERENCES, code sprints, and related social events; as well as VIRTUAL FORUMS, such as email, IRC, wikis, etc.
* Recognise that OSGeo has a DIVERSE community. (From Draft OSGeo Diversity Statement, and others)
* Set expectation that people should act RESPECTFULLY toward each other. It is ok to respectfully disagree with people's technical ideas without attacking them personally. (From Draft OSGeo Diversity Statement, and others)
* Make it clear that we don't condone HARASSMENT or offensive behaviour, and make it clear what that is. (From O'Reilly Code of Conduct and GeekGirls Anti-Harrassment Policy)
* Outline a process for IDENTIFYING, 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. (Derived from Tweaking the Moral UI)
* Identify the ROLE of the person, or group of people responsible for ensuring the process will be followed.
* Include an escalation process for dealing with both minor and major issues. (From Draft OSGeo Conference Committee Code of Conduct)
* Couch in positive, non-threatening language. (See QGIS Diversity Statement and Code of Conduct)
* Recognise that not all participants will be native (English?) speakers and native speakers should adjust language chosen to make it easier for all participants to contribute. Eg: Try to avoid using slang. (From OGC Principles of Conduct)
* Be concise. Concise words get read more. (See QGIS Diversity Statement)

== Exemplar Sources ==

The OSGeo Code of Conduct is derived from numerous prior examples. On reading the prior material, you can see how the documents have been improving over time.

===OGC Principles of Conduct===

;Source: http://www.opengeospatial.org/ogc/policies/conduct
;Vintage: 2007
;Derived from: https://tools.ietf.org/html/rfc3184 , Vintage: 2001

;Comments
* PRO: (cameronshorter) Recognises the need to be inclusive, by making allowances for people who are not speaking in their native language.
* PRO: (cameronshorter) Encourages people to debate and potentially disagree on ideas, without attacking people personally.
* CON: (cameronshorter) Too verbose.

===Geek Feminism Template Anti Harassment Policy===

;Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment_policy

;Vintage: 2010

;Comments:
* PRO: (cameronshorter) Provides customisable version.
* PRO: (cameronshorter) Provides short/medium/long version
* PRO: (cameronshorter) Contains internal guidance for conference staff on how to handle harassment reports
* CON: (cameronshorter) Focuses only on sexual harassment, doesn't cover other topics such non-native speakers, be respectful (in general, to all).
* CON: (cameronshorter) Language of some later CoC statements are less confrontational

===FOSS4G 2015 NA and FOSS4G 2015 Code of Conduct===

;Source: https://2015.foss4g-na.org/code-conduct, downloaded 24 March 2015, derived from others, like: http://jsconf.com/codeofconduct.html and http://confcodeofconduct.com/
;Similar Source: http://2015.foss4g.org/about/codeofconduct

;Vintage: 2012

;Comments:
:* PRO: (cameronshorter) Starts with a tick-box version which can be used during registration of an event.
:* CON: (cameronshorter) Language has interpreted by some as confrontational, and could be interpreted as implying assumption of guilt.
:* CON: (cameronshorter) It would be better if this statement could be made shorter.

=== O'Reilly Code of Conduct ===

;Source: http://www.oreilly.com/conferences/code-of-conduct.html, downloaded 24 March 2015

;Vintage: 2012

;Comments
* PRO: (cameronshorter) It makes good use of positive language
* CON: (cameronshorter) This is missing a description of graduated escalation process, and how a report would be handled.
* CON: (cameronshorter) Focuses on conference venues. Later documents cover on-line communication better.

=== QGIS Diversity Statement ===

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/diversitystatement.html
;Second Source: https://qgis2015.wordpress.com

; Comments:
* PRO: (cameronshorter) States acceptance of diversity without singling out all the possible variants of diversity (race, religion, gender, ...)
* PRO: (cameronshorter) Concise.
* CON: (cameronshorter) Doesn't cover other Code of Conduct items, such as what is/is not acceptable.

=== QGIS Code of Conduct ===

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/codeofconduct.html
;Derived from: [https://www.djangoproject.com/conduct/ Django Code of Conduct] and Speak Up Code of Conduct.
;Based on [http://web.archive.org/web/20121204215836/http://speakup.io/coc.html SpeakUp CoC] and https://www.djangoproject.com/conduct/
;Vintage: 2012/2013
; Comments
* PRO: (cameronshorter) Written in positive language
* CON: (cameronshorter) Too verbose

===Debian diversity statement===

; Source: https://www.debian.org/intro/diversity

; Vintage: April 2014

;Comments
*

===Debian Code of Conduct===

; Vintage: April 2014
;Source: https://www.debian.org/code_of_conduct
;Comments:
* PRO: (johanvdw) I added these Debian references because I like the style which is used in the code of conduct for Debian: short bold bullet point with some more information afterwards (like the qgis version).;
* PRO (johanvdw) I also think the second item '''"assume good faith"''' is a very important one, which is missing from the current proposal.
* PRO (cameronshorter) I like the "try to be concise" - which is a form of respect to others.
* PRO (cameronshorter) This contains a graduated escalation process providing guidance on dealing with both minor and major issues.
* PRO (cameronshorter) This contains a version number, such which can be referenced as a point in time, and such that we can identify when to upgrade to a newer version of a Code Of Conduct.
* CON (cameronshorter) This focuses on online communications and doesn't address issues at face-to-face events as well.

=== Apache Code of Conduct ===

; Source: https://www.apache.org/foundation/policies/conduct.html, retrieved April 2015

Apache contains a separate Anti Harassment Policy, derived from the Geek Feminism Anti Harassment Policy.

; Source: https://www.apache.org/foundation/policies/anti-harassment.html

;Vintage: December 2014
; Comments:
* PRO: This addresses a few more use cases not covered by Debian, such as Don't share private emails in a public forum.
* CON: This CoC is missing a version number, such that is can be referenced by version.
* CON: States that English is the primary language - OSGeo has forums in other languages.
* CON: In places, text repeats itself (in particular, under the "Reporting Guidelines" section).

=== Draft OSGeo Board Diversity Statement ===

;Source: http://wiki.osgeo.org/index.php?title=Diversity&oldid=82976
;Original Briefer Source: http://wiki.osgeo.org/index.php?title=Diversity&oldid=81445

=== Draft OSGeo Conference Committee Code of Conduct ===

; Source: http://lists.osgeo.org/pipermail/conference_dev/2015-January/002851.html, 16 January 2015

== Further References ==

* Tweaking the Moral UI by CHRISTINA WODTKE, http://alistapart.com/article/tweaking-the-moral-ui, downloaded 24 March 2015

== Code of Conduct Workflow Discussions ==

SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015

NEXT STEPS To Discuss:

1 - Code of Conduct formal committee (do we need one? if so, how do we formalize it?)
could be a joint committee covering both OSM and OSGeo foundations
formalized by approval from each Board

2 - Reporting Guidelines

;Source: https://www.djangoproject.com/conduct/reporting/
;Source: https://www.drupal.org/governance/community-working-group/incident-report

3 - Responding/Enforcement
;Source: https://www.djangoproject.com/conduct/enforcement-manual/
;Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports
;Source: http://docs.puppetlabs.com/community/community_guidelines.html

4 - Language/Actions for Dealing with Banned Person

'''Sample Language When Banned Person Attempts to Register
'''

Dear Name

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks

Event Organizer

5 - Keeping Track of Banned Individuals
;Source: https://www.noisebridge.net/wiki/86 ( I think it should be tracked but I am worried about it being public facing)

6 - When/How to Let Banned People Come Back
;Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/
;Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
[[Category: Board]]
[[Category:Conference Committee]]

Code Of Conduct

2015-06-06T15:01:51Z

Wiki-RhoBott: /* Code of Conduct Workflow Discussions */ italicizing sample language

Please refer to the official version of this wiki page at: http://www.osgeo.org/code_of_conduct .

This page includes reference to prior material and comments applied during the development. (For history, refer to the [[Diversity]] page).
The official version 1.0 of the Code of Conduct was taken from: http://wiki.osgeo.org/index.php?title=Code_Of_Conduct&diff=84231&oldid=84214

==OSGeo Code of Conduct==

Version: 1.0

Date: May 2015

===Introduction===

This code of conduct governs how we behave in any OSGeo forum or event and whenever we will be judged by our actions. We expect it to be honored by everyone who participates in the OSGeo community formally or informally, or claims any affiliation with the OSGeo Foundation.

It applies to in-person events (such as conferences and related social events), IRC, public and private mailing lists, the issue tracker, the wiki, blogs, Twitter, and any other forums which the community uses for communication and interactions.

This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in the letter, so that it can enrich all of us and the technical communities in which we participate.

===Diversity Statement===

OSGeo welcomes and encourages participation by everyone. We are committed to being a community that everyone feels good about joining, and we will always work to treat everyone well. No matter how you identify yourself or how others perceive you: we welcome you.

===Specific Guidelines===

We strive to:

;Be open.
: We invite anyone to participate in our community. We preferably use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also makes sure that any inadvertent mistakes made by people answering will be more easily detected and corrected.

;Be empathetic, welcoming, friendly, and patient.
:We work together to resolve conflict, assume good intentions, and do our best to act in an empathetic fashion. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one. Note that we have a multi-cultural, multi-lingual community and some of us are non-native speakers. We should be respectful when dealing with other community members as well as with people outside our community.

;Be collaborative. : Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of OSGeo, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.

;Be inquisitive. : Nobody knows everything! Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful, within the context of our shared goal of improving OSGeo.

;Be careful in the words that we choose. : Whether we are participating as professionals or volunteers, we value professionalism in all interactions, and take responsibility for our own speech. Be kind to others. Do not insult or put down other participants.

;Be concise. : Keep in mind that what you write once will be read by hundreds of persons. Writing a short email means people can understand the conversation as efficiently as possible. Short emails should always strive to be empathetic, welcoming, friendly and patient. When a long explanation is necessary, consider adding a summary.

: Try to bring new ideas to a conversation so that each mail adds something unique to the thread, keeping in mind that the rest of the thread still contains the other messages with arguments that have already been made.

: Try to stay on topic, especially in discussions that are already fairly large.

; Step down considerately.
: Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project's goals or achievements. Likewise, community members should respect any individual's choice to leave the project.

===Anti-Harassment===

Harassment and other exclusionary behaviour are not acceptable. This includes, but is not limited to:

* Personal insults or discriminatory jokes and language, especially those using racist or sexist terms.
* Offensive comments, excessive or unnecessary profanity.
* Intimidation, violent threats or demands.
* Sustained disruption of sessions or events.
* Stalking, harassing photography or recording.
* Unwelcome physical contact or sexual attention.
* Repeated harassment of others. In general, if someone asks you to stop, then stop.
* Posting (or threatening to post) other people's personally identifying information ("doxing").
* Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history.
* Advocating for, or encouraging, any of the above behaviour.

===Reporting Guidelines===

If you believe someone is breaking this code of conduct, you may reply to them, and point to this code of conduct. Such messages may be in public or in private, whatever is most appropriate. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your concerns to event staff, a forum leader or the OSGeo Board. Serious or persistent offenders may be expelled from the event or forum by event organizers or forum leaders.

===Application===
All OSGeo projects and events should reference this Code of Conduct using text similar to:

Participants at <event> are expected to act respectfully toward others in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

or

Contributors to <project> are expected to act respectfully toward others in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

----

<End of the OSGeo Code of Conduct>

----

== Goals for Code of Conduct / Diversity Statement ==
This list has been generated to help authors of this document to agree on what we aim to achieve from this Code of Conduct / Diversity Statement. It should:
* Be applicable for: In person events such as CONFERENCES, code sprints, and related social events; as well as VIRTUAL FORUMS, such as email, IRC, wikis, etc.
* Recognise that OSGeo has a DIVERSE community. (From Draft OSGeo Diversity Statement, and others)
* Set expectation that people should act RESPECTFULLY toward each other. It is ok to respectfully disagree with people's technical ideas without attacking them personally. (From Draft OSGeo Diversity Statement, and others)
* Make it clear that we don't condone HARASSMENT or offensive behaviour, and make it clear what that is. (From O'Reilly Code of Conduct and GeekGirls Anti-Harrassment Policy)
* Outline a process for IDENTIFYING, 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. (Derived from Tweaking the Moral UI)
* Identify the ROLE of the person, or group of people responsible for ensuring the process will be followed.
* Include an escalation process for dealing with both minor and major issues. (From Draft OSGeo Conference Committee Code of Conduct)
* Couch in positive, non-threatening language. (See QGIS Diversity Statement and Code of Conduct)
* Recognise that not all participants will be native (English?) speakers and native speakers should adjust language chosen to make it easier for all participants to contribute. Eg: Try to avoid using slang. (From OGC Principles of Conduct)
* Be concise. Concise words get read more. (See QGIS Diversity Statement)

== Exemplar Sources ==

The OSGeo Code of Conduct is derived from numerous prior examples. On reading the prior material, you can see how the documents have been improving over time.

===OGC Principles of Conduct===

;Source: http://www.opengeospatial.org/ogc/policies/conduct
;Vintage: 2007
;Derived from: https://tools.ietf.org/html/rfc3184 , Vintage: 2001

;Comments
* PRO: (cameronshorter) Recognises the need to be inclusive, by making allowances for people who are not speaking in their native language.
* PRO: (cameronshorter) Encourages people to debate and potentially disagree on ideas, without attacking people personally.
* CON: (cameronshorter) Too verbose.

===Geek Feminism Template Anti Harassment Policy===

;Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment_policy

;Vintage: 2010

;Comments:
* PRO: (cameronshorter) Provides customisable version.
* PRO: (cameronshorter) Provides short/medium/long version
* PRO: (cameronshorter) Contains internal guidance for conference staff on how to handle harassment reports
* CON: (cameronshorter) Focuses only on sexual harassment, doesn't cover other topics such non-native speakers, be respectful (in general, to all).
* CON: (cameronshorter) Language of some later CoC statements are less confrontational

===FOSS4G 2015 NA and FOSS4G 2015 Code of Conduct===

;Source: https://2015.foss4g-na.org/code-conduct, downloaded 24 March 2015, derived from others, like: http://jsconf.com/codeofconduct.html and http://confcodeofconduct.com/
;Similar Source: http://2015.foss4g.org/about/codeofconduct

;Vintage: 2012

;Comments:
:* PRO: (cameronshorter) Starts with a tick-box version which can be used during registration of an event.
:* CON: (cameronshorter) Language has interpreted by some as confrontational, and could be interpreted as implying assumption of guilt.
:* CON: (cameronshorter) It would be better if this statement could be made shorter.

=== O'Reilly Code of Conduct ===

;Source: http://www.oreilly.com/conferences/code-of-conduct.html, downloaded 24 March 2015

;Vintage: 2012

;Comments
* PRO: (cameronshorter) It makes good use of positive language
* CON: (cameronshorter) This is missing a description of graduated escalation process, and how a report would be handled.
* CON: (cameronshorter) Focuses on conference venues. Later documents cover on-line communication better.

=== QGIS Diversity Statement ===

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/diversitystatement.html
;Second Source: https://qgis2015.wordpress.com

; Comments:
* PRO: (cameronshorter) States acceptance of diversity without singling out all the possible variants of diversity (race, religion, gender, ...)
* PRO: (cameronshorter) Concise.
* CON: (cameronshorter) Doesn't cover other Code of Conduct items, such as what is/is not acceptable.

=== QGIS Code of Conduct ===

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/codeofconduct.html
;Derived from: [https://www.djangoproject.com/conduct/ Django Code of Conduct] and Speak Up Code of Conduct.
;Based on [http://web.archive.org/web/20121204215836/http://speakup.io/coc.html SpeakUp CoC] and https://www.djangoproject.com/conduct/
;Vintage: 2012/2013
; Comments
* PRO: (cameronshorter) Written in positive language
* CON: (cameronshorter) Too verbose

===Debian diversity statement===

; Source: https://www.debian.org/intro/diversity

; Vintage: April 2014

;Comments
*

===Debian Code of Conduct===

; Vintage: April 2014
;Source: https://www.debian.org/code_of_conduct
;Comments:
* PRO: (johanvdw) I added these Debian references because I like the style which is used in the code of conduct for Debian: short bold bullet point with some more information afterwards (like the qgis version).;
* PRO (johanvdw) I also think the second item '''"assume good faith"''' is a very important one, which is missing from the current proposal.
* PRO (cameronshorter) I like the "try to be concise" - which is a form of respect to others.
* PRO (cameronshorter) This contains a graduated escalation process providing guidance on dealing with both minor and major issues.
* PRO (cameronshorter) This contains a version number, such which can be referenced as a point in time, and such that we can identify when to upgrade to a newer version of a Code Of Conduct.
* CON (cameronshorter) This focuses on online communications and doesn't address issues at face-to-face events as well.

=== Apache Code of Conduct ===

; Source: https://www.apache.org/foundation/policies/conduct.html, retrieved April 2015

Apache contains a separate Anti Harassment Policy, derived from the Geek Feminism Anti Harassment Policy.

; Source: https://www.apache.org/foundation/policies/anti-harassment.html

;Vintage: December 2014
; Comments:
* PRO: This addresses a few more use cases not covered by Debian, such as Don't share private emails in a public forum.
* CON: This CoC is missing a version number, such that is can be referenced by version.
* CON: States that English is the primary language - OSGeo has forums in other languages.
* CON: In places, text repeats itself (in particular, under the "Reporting Guidelines" section).

=== Draft OSGeo Board Diversity Statement ===

;Source: http://wiki.osgeo.org/index.php?title=Diversity&oldid=82976
;Original Briefer Source: http://wiki.osgeo.org/index.php?title=Diversity&oldid=81445

=== Draft OSGeo Conference Committee Code of Conduct ===

; Source: http://lists.osgeo.org/pipermail/conference_dev/2015-January/002851.html, 16 January 2015

== Further References ==

* Tweaking the Moral UI by CHRISTINA WODTKE, http://alistapart.com/article/tweaking-the-moral-ui, downloaded 24 March 2015

== Code of Conduct Workflow Discussions ==

SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015

NEXT STEPS To Discuss:

1 - Code of Conduct formal committee (do we need one? if so, how do we formalize it?)
could be a joint committee covering both OSM and OSGeo foundations
formalized by approval from each Board

2 - Reporting Guidelines

;Source: https://www.djangoproject.com/conduct/reporting/
;Source: https://www.drupal.org/governance/community-working-group/incident-report

3 - Responding/Enforcement
;Source: https://www.djangoproject.com/conduct/enforcement-manual/
;Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports
;Source: http://docs.puppetlabs.com/community/community_guidelines.html

4 - Language/Actions for Dealing with Banned Person

**Sample Language When Banned Person Attempts to Register**

''Dear Name,

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks,

Event Organizer''

5 - Keeping Track of Banned Individuals
;Source: https://www.noisebridge.net/wiki/86 ( I think it should be tracked but I am worried about it being public facing)

6 - When/How to Let Banned People Come Back
;Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/
;Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
[[Category: Board]]
[[Category:Conference Committee]]

Code Of Conduct

2015-06-06T14:54:19Z

Wiki-RhoBott: Adding references and notes from the CoC Next Steps session - held at State of the Map US - 6 June 2015

Please refer to the official version of this wiki page at: http://www.osgeo.org/code_of_conduct .

This page includes reference to prior material and comments applied during the development. (For history, refer to the [[Diversity]] page).
The official version 1.0 of the Code of Conduct was taken from: http://wiki.osgeo.org/index.php?title=Code_Of_Conduct&diff=84231&oldid=84214

==OSGeo Code of Conduct==

Version: 1.0

Date: May 2015

===Introduction===

This code of conduct governs how we behave in any OSGeo forum or event and whenever we will be judged by our actions. We expect it to be honored by everyone who participates in the OSGeo community formally or informally, or claims any affiliation with the OSGeo Foundation.

It applies to in-person events (such as conferences and related social events), IRC, public and private mailing lists, the issue tracker, the wiki, blogs, Twitter, and any other forums which the community uses for communication and interactions.

This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in the letter, so that it can enrich all of us and the technical communities in which we participate.

===Diversity Statement===

OSGeo welcomes and encourages participation by everyone. We are committed to being a community that everyone feels good about joining, and we will always work to treat everyone well. No matter how you identify yourself or how others perceive you: we welcome you.

===Specific Guidelines===

We strive to:

;Be open.
: We invite anyone to participate in our community. We preferably use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also makes sure that any inadvertent mistakes made by people answering will be more easily detected and corrected.

;Be empathetic, welcoming, friendly, and patient.
:We work together to resolve conflict, assume good intentions, and do our best to act in an empathetic fashion. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one. Note that we have a multi-cultural, multi-lingual community and some of us are non-native speakers. We should be respectful when dealing with other community members as well as with people outside our community.

;Be collaborative. : Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of OSGeo, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.

;Be inquisitive. : Nobody knows everything! Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful, within the context of our shared goal of improving OSGeo.

;Be careful in the words that we choose. : Whether we are participating as professionals or volunteers, we value professionalism in all interactions, and take responsibility for our own speech. Be kind to others. Do not insult or put down other participants.

;Be concise. : Keep in mind that what you write once will be read by hundreds of persons. Writing a short email means people can understand the conversation as efficiently as possible. Short emails should always strive to be empathetic, welcoming, friendly and patient. When a long explanation is necessary, consider adding a summary.

: Try to bring new ideas to a conversation so that each mail adds something unique to the thread, keeping in mind that the rest of the thread still contains the other messages with arguments that have already been made.

: Try to stay on topic, especially in discussions that are already fairly large.

; Step down considerately.
: Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project's goals or achievements. Likewise, community members should respect any individual's choice to leave the project.

===Anti-Harassment===

Harassment and other exclusionary behaviour are not acceptable. This includes, but is not limited to:

* Personal insults or discriminatory jokes and language, especially those using racist or sexist terms.
* Offensive comments, excessive or unnecessary profanity.
* Intimidation, violent threats or demands.
* Sustained disruption of sessions or events.
* Stalking, harassing photography or recording.
* Unwelcome physical contact or sexual attention.
* Repeated harassment of others. In general, if someone asks you to stop, then stop.
* Posting (or threatening to post) other people's personally identifying information ("doxing").
* Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history.
* Advocating for, or encouraging, any of the above behaviour.

===Reporting Guidelines===

If you believe someone is breaking this code of conduct, you may reply to them, and point to this code of conduct. Such messages may be in public or in private, whatever is most appropriate. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your concerns to event staff, a forum leader or the OSGeo Board. Serious or persistent offenders may be expelled from the event or forum by event organizers or forum leaders.

===Application===
All OSGeo projects and events should reference this Code of Conduct using text similar to:

Participants at <event> are expected to act respectfully toward others in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

or

Contributors to <project> are expected to act respectfully toward others in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

----

<End of the OSGeo Code of Conduct>

----

== Goals for Code of Conduct / Diversity Statement ==
This list has been generated to help authors of this document to agree on what we aim to achieve from this Code of Conduct / Diversity Statement. It should:
* Be applicable for: In person events such as CONFERENCES, code sprints, and related social events; as well as VIRTUAL FORUMS, such as email, IRC, wikis, etc.
* Recognise that OSGeo has a DIVERSE community. (From Draft OSGeo Diversity Statement, and others)
* Set expectation that people should act RESPECTFULLY toward each other. It is ok to respectfully disagree with people's technical ideas without attacking them personally. (From Draft OSGeo Diversity Statement, and others)
* Make it clear that we don't condone HARASSMENT or offensive behaviour, and make it clear what that is. (From O'Reilly Code of Conduct and GeekGirls Anti-Harrassment Policy)
* Outline a process for IDENTIFYING, 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. (Derived from Tweaking the Moral UI)
* Identify the ROLE of the person, or group of people responsible for ensuring the process will be followed.
* Include an escalation process for dealing with both minor and major issues. (From Draft OSGeo Conference Committee Code of Conduct)
* Couch in positive, non-threatening language. (See QGIS Diversity Statement and Code of Conduct)
* Recognise that not all participants will be native (English?) speakers and native speakers should adjust language chosen to make it easier for all participants to contribute. Eg: Try to avoid using slang. (From OGC Principles of Conduct)
* Be concise. Concise words get read more. (See QGIS Diversity Statement)

== Exemplar Sources ==

The OSGeo Code of Conduct is derived from numerous prior examples. On reading the prior material, you can see how the documents have been improving over time.

===OGC Principles of Conduct===

;Source: http://www.opengeospatial.org/ogc/policies/conduct
;Vintage: 2007
;Derived from: https://tools.ietf.org/html/rfc3184 , Vintage: 2001

;Comments
* PRO: (cameronshorter) Recognises the need to be inclusive, by making allowances for people who are not speaking in their native language.
* PRO: (cameronshorter) Encourages people to debate and potentially disagree on ideas, without attacking people personally.
* CON: (cameronshorter) Too verbose.

===Geek Feminism Template Anti Harassment Policy===

;Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment_policy

;Vintage: 2010

;Comments:
* PRO: (cameronshorter) Provides customisable version.
* PRO: (cameronshorter) Provides short/medium/long version
* PRO: (cameronshorter) Contains internal guidance for conference staff on how to handle harassment reports
* CON: (cameronshorter) Focuses only on sexual harassment, doesn't cover other topics such non-native speakers, be respectful (in general, to all).
* CON: (cameronshorter) Language of some later CoC statements are less confrontational

===FOSS4G 2015 NA and FOSS4G 2015 Code of Conduct===

;Source: https://2015.foss4g-na.org/code-conduct, downloaded 24 March 2015, derived from others, like: http://jsconf.com/codeofconduct.html and http://confcodeofconduct.com/
;Similar Source: http://2015.foss4g.org/about/codeofconduct

;Vintage: 2012

;Comments:
:* PRO: (cameronshorter) Starts with a tick-box version which can be used during registration of an event.
:* CON: (cameronshorter) Language has interpreted by some as confrontational, and could be interpreted as implying assumption of guilt.
:* CON: (cameronshorter) It would be better if this statement could be made shorter.

=== O'Reilly Code of Conduct ===

;Source: http://www.oreilly.com/conferences/code-of-conduct.html, downloaded 24 March 2015

;Vintage: 2012

;Comments
* PRO: (cameronshorter) It makes good use of positive language
* CON: (cameronshorter) This is missing a description of graduated escalation process, and how a report would be handled.
* CON: (cameronshorter) Focuses on conference venues. Later documents cover on-line communication better.

=== QGIS Diversity Statement ===

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/diversitystatement.html
;Second Source: https://qgis2015.wordpress.com

; Comments:
* PRO: (cameronshorter) States acceptance of diversity without singling out all the possible variants of diversity (race, religion, gender, ...)
* PRO: (cameronshorter) Concise.
* CON: (cameronshorter) Doesn't cover other Code of Conduct items, such as what is/is not acceptable.

=== QGIS Code of Conduct ===

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/codeofconduct.html
;Derived from: [https://www.djangoproject.com/conduct/ Django Code of Conduct] and Speak Up Code of Conduct.
;Based on [http://web.archive.org/web/20121204215836/http://speakup.io/coc.html SpeakUp CoC] and https://www.djangoproject.com/conduct/
;Vintage: 2012/2013
; Comments
* PRO: (cameronshorter) Written in positive language
* CON: (cameronshorter) Too verbose

===Debian diversity statement===

; Source: https://www.debian.org/intro/diversity

; Vintage: April 2014

;Comments
*

===Debian Code of Conduct===

; Vintage: April 2014
;Source: https://www.debian.org/code_of_conduct
;Comments:
* PRO: (johanvdw) I added these Debian references because I like the style which is used in the code of conduct for Debian: short bold bullet point with some more information afterwards (like the qgis version).;
* PRO (johanvdw) I also think the second item '''"assume good faith"''' is a very important one, which is missing from the current proposal.
* PRO (cameronshorter) I like the "try to be concise" - which is a form of respect to others.
* PRO (cameronshorter) This contains a graduated escalation process providing guidance on dealing with both minor and major issues.
* PRO (cameronshorter) This contains a version number, such which can be referenced as a point in time, and such that we can identify when to upgrade to a newer version of a Code Of Conduct.
* CON (cameronshorter) This focuses on online communications and doesn't address issues at face-to-face events as well.

=== Apache Code of Conduct ===

; Source: https://www.apache.org/foundation/policies/conduct.html, retrieved April 2015

Apache contains a separate Anti Harassment Policy, derived from the Geek Feminism Anti Harassment Policy.

; Source: https://www.apache.org/foundation/policies/anti-harassment.html

;Vintage: December 2014
; Comments:
* PRO: This addresses a few more use cases not covered by Debian, such as Don't share private emails in a public forum.
* CON: This CoC is missing a version number, such that is can be referenced by version.
* CON: States that English is the primary language - OSGeo has forums in other languages.
* CON: In places, text repeats itself (in particular, under the "Reporting Guidelines" section).

=== Draft OSGeo Board Diversity Statement ===

;Source: http://wiki.osgeo.org/index.php?title=Diversity&oldid=82976
;Original Briefer Source: http://wiki.osgeo.org/index.php?title=Diversity&oldid=81445

=== Draft OSGeo Conference Committee Code of Conduct ===

; Source: http://lists.osgeo.org/pipermail/conference_dev/2015-January/002851.html, 16 January 2015

== Further References ==

* Tweaking the Moral UI by CHRISTINA WODTKE, http://alistapart.com/article/tweaking-the-moral-ui, downloaded 24 March 2015

== Code of Conduct Workflow Discussions ==

SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015

NEXT STEPS To Discuss:

1 - Code of Conduct formal committee (do we need one? if so, how do we formalize it?)
could be a joint committee covering both OSM and OSGeo foundations
formalized by approval from each Board

2 - Reporting Guidelines

;Source: https://www.djangoproject.com/conduct/reporting/
;Source: https://www.drupal.org/governance/community-working-group/incident-report

3 - Responding/Enforcement
;Source: https://www.djangoproject.com/conduct/enforcement-manual/
;Source: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports
;Source: http://docs.puppetlabs.com/community/community_guidelines.html

4 - Language/Actions for Dealing with Banned Person

**Sample Language When Banned Person Attempts to Register**

Dear Name,

Thank you for your interest in attending This Event. Unfortunately, we
are not able to accommodate your attendance at this event. We
apologize for the inconvenience, and have issued a full refund to your
credit card.

Many thanks,

Event Organizer

5 - Keeping Track of Banned Individuals
;Source: https://www.noisebridge.net/wiki/86 ( I think it should be tracked but I am worried about it being public facing)

6 - When/How to Let Banned People Come Back
;Source: https://adainitiative.org/2014/07/guest-post-harassment-isnt-an-interpersonal-issue-its-a-health-and-safety-issue/
;Source: https://adainitiative.org/2014/07/guest-post-deciding-if-or-when-a-harasser-may-return-to-an-event/
[[Category: Board]]
[[Category:Conference Committee]]

Code Of Conduct

2015-05-13T18:01:15Z

Wiki-RhoBott: /* Application */ wordsmithing on implementation language

==OSGeo Code of Conduct==

Version: 1.0

Date: May 2015

===Introduction===

This code of conduct governs how we behave in any OSGeo forum or event and whenever we will be judged by our actions. We expect it to be honored by everyone who participates in the OSGeo community formally or informally, or claims any affiliation with the OSGeo Foundation.

It applies to in-person events (such as conferences and related social events), IRC, public and private mailing lists, the issue tracker, the wiki, blogs, Twitter, and any other forums which the community uses for communication and interactions.

This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in the letter, so that it can enrich all of us and the technical communities in which we participate.

===Diversity Statement===

OSGeo welcomes and encourages participation by everyone. We are committed to being a community that everyone feels good about joining, and we will always work to treat everyone well. No matter how you identify yourself or how others perceive you: we welcome you.

===Specific Guidelines===

We strive to:

;Be open.
: We invite anyone to participate in our community. We preferably use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also makes sure that any inadvertent mistakes made by people answering will be more easily detected and corrected.

;Be empathetic, welcoming, friendly, and patient.
:We work together to resolve conflict, assume good intentions, and do our best to act in an empathetic fashion. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one. Note that we have a multi-cultural, multi-lingual community and some of us are non-native speakers. We should be respectful when dealing with other community members as well as with people outside our community.

;Be collaborative. : Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of OSGeo, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.

;Be inquisitive. : Nobody knows everything! Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful, within the context of our shared goal of improving OSGeo.

;Be careful in the words that we choose. : Whether we are participating as professionals or volunteers, we value professionalism in all interactions, and take responsibility for our own speech. Be kind to others. Do not insult or put down other participants.

;Be concise. : Keep in mind that what you write once will be read by hundreds of persons. Writing a short email means people can understand the conversation as efficiently as possible. Short emails should always strive to be empathetic, welcoming, friendly and patient. When a long explanation is necessary, consider adding a summary.

: Try to bring new ideas to a conversation so that each mail adds something unique to the thread, keeping in mind that the rest of the thread still contains the other messages with arguments that have already been made.

: Try to stay on topic, especially in discussions that are already fairly large.

; Step down considerately.
: Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project's goals or achievements. Likewise, community members should respect any individual's choice to leave the project.

===Anti-Harassment===

Harassment and other exclusionary behaviour are not acceptable. This includes, but is not limited to:

* Personal insults or discriminatory jokes and language, especially those using racist or sexist terms.
* Offensive comments, excessive or unnecessary profanity.
* Intimidation, violent threats or demands.
* Sustained disruption of sessions or events.
* Stalking, harassing photography or recording.
* Unwelcome physical contact or sexual attention.
* Repeated harassment of others. In general, if someone asks you to stop, then stop.
* Posting (or threatening to post) other people's personally identifying information ("doxing").
* Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history.
* Advocating for, or encouraging, any of the above behaviour.

===Reporting Guidelines===

If you believe someone is breaking this code of conduct, you may reply to them, and point to this code of conduct. Such messages may be in public or in private, whatever is most appropriate. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your concerns to event staff, a forum leader or the OSGeo Board. Serious or persistent offenders may be expelled from the event or forum by event organizers or forum leaders.

===Application===
All OSGeo projects and events should reference this Code of Conduct using text similar to:

Participants at <event> are expected to act respectfully in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

or

Contributors to <project> are expected to act respectfully in accordance with the [http://wiki.osgeo.org/wiki/Code_Of_Conduct OSGeo Code of Conduct].

User:RhoBott

2014-09-02T04:29:57Z

Wiki-RhoBott:

== Kristin Bott ==

'''title''' Instructional Technologist for Quantitative Applications, Reed College

'''location''' Portland, Oregon, USA

'''OSGeo experience'''
* FOSS4G 2014 Local Organizing Committee
* co-designer of 2014 FOSS4G travel grant program (with Darrell Fuhriman)
* OSGeo Charter Member (2014)
[[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]]

'''background and interests'''

Kristin works with faculty and students at Reed College on all-things-analytical, focusing on statistical + computational software, research design, and data management and presentation. She is also the main geospatial + mapping resource on campus, where she works to integrate different types of geo/spatial work across the curriculum. Kristin is particularly interested in the intersection of GIS and teaching/education and increasing access to all-things-geospatial across a wide group of users. She holds a M.Sc. in Fisheries & Wildlife (EEBB track) from Michigan State University, a B.A. in Biology/Ecology from the University of Montana, and will complete Portland State's Graduate Certificate program in GIS in December 2014. Outside of work, you can probably find her growing or making good food, brewing beer, reading something interesting, or running around outside.

'''contact'''

kbott /at/ reed /dot/ edu

Twitter: [https://twitter.com/rhobott @RhoBott ]

[http://reed.edu/data-at-reed/ Data @ Reed collaboration] (under construction fall 2014)

[http://blogs.reed.edu/ed-tech Instructional Technology Services blog] (debuting fall 2014)

User:RhoBott

2014-08-29T16:34:38Z

Wiki-RhoBott:

== Kristin Bott ==

'''title''' Instructional Technologist for Quantitative Applications, Reed College

'''location''' Portland, Oregon, USA

'''OSGeo experience'''
* FOSS4G 2014 Local Organizing Committee
* co-designer of 2014 FOSS4G travel grant program (with Darrell Fuhriman)
* OSGeo Charter Member (2014)

'''background and interests'''

Kristin works with faculty and students at Reed College on all-things-analytical, focusing on statistical + computational software, research design, and data management and presentation. She is also the main geospatial + mapping resource on campus, where she works to integrate different types of geo/spatial work across the curriculum. Kristin is particularly interested in the intersection of GIS and teaching/education and increasing access to all-things-geospatial across a wide group of users. She holds a M.Sc. in Fisheries & Wildlife (EEBB track) from Michigan State University, a B.A. in Biology/Ecology from the University of Montana, and will complete Portland State's Graduate Certificate program in GIS in December 2014. Outside of work, you can probably find her growing or making good food, brewing beer, reading something interesting, or running/riding around outside.

'''contact'''

kbott /at/ reed /dot/ edu

Twitter: @RhoBott [ https://twitter.com/rhobott]

Data @ Reed collaboration (under construction fall 2014) [ http://reed.edu/data-at-reed/]

Instructional Technology Services blog (debuting fall 2014) [ http://blogs.reed.edu/ed-tech]

User:RhoBott

2014-08-29T16:16:50Z

Wiki-RhoBott: Created page with "== Kristin Bott == '''title''' Instructional Technologist for Quantitative Applications, Reed College '''location''' Portland, Oregon, USA '''OSGeo experience''' * FOSS4G 201..."

== Kristin Bott ==

'''title''' Instructional Technologist for Quantitative Applications, Reed College

'''location''' Portland, Oregon, USA

'''OSGeo experience'''
* FOSS4G 2014 Local Organizing Committee
* co-designer of 2014 FOSS4G travel grant program (with Darrell Fuhriman)
* OSGeo Charter Member (2014)

'''background and interests'''

Kristin works with faculty and students at Reed College on all-things-analytical, focusing on statistical + computational software, research design, and data management and presentation. She is also the main geospatial + mapping resource on campus, where she works to integrate different types of geo/spatial work across the curriculum. Kristin is particularly interested in the intersection of GIS and teaching/education and increasing access to all-things-geospatial across a wide group of users. She holds a M.Sc. in Fisheries & Wildlife (EEBB track) from Michigan State University, a B.A. in Biology/Ecology from the University of Montana, and will complete Portland State's Graduate Certificate program in GIS in December 2014.

'''contact'''

kbott /at/ reed /dot/ edu

Twitter: @RhoBott [ https://twitter.com/rhobott]

Data @ Reed collaboration (under construction fall 2014) [ http://reed.edu/data-at-reed/]

Instructional Technology Services blog (debuting fall 2014) [ http://blogs.reed.edu/ed-tech]

FOSS4G 2014 Planning Meeting 19th August

2014-08-19T21:07:55Z

Wiki-RhoBott:

FOSS4G LOC Meeting, August 19th, 2014

Renewable Funding, 5:45-7:30 pm

current as of 2:05pm 8/19. Notes/changes happen in the related Google Doc

'''Agenda'''

'''''I - Money'''''
Budget overview (Darrell)

Additional budget items:

Gala Facilities/Additional Expenses? Tents, DJ, etc?

Adding workshops lunch (Darrell) (http://www.campusdish.com/NR/rdonlyres/7E648CBA-A79F-45A7-A621-9B91A1F0769E/0/PSUMod_Everyday.pdf)

Final commitment for funds on opening night party? Lets Figure out how to pay for some food (Tanya / Ryan)

Trimet Tickets Purchase (Neil)

T-Shirt orders (Tanya)

More Stickers?

Lanyards (VTM)

Name badges (VTM)

Proposing 5 badge types, all double side in full color:

Attendee (approx. 500)

Sponsor (approx. 75)

Volunteer (approx. 75)

Presenter (approx. 200)

Press (approx. ?)

1 hr of design time and printing = ~$600.00 from Alphagraphics for either vertical (?”x?”) or horizontal (4” x 5”)

Need to buy name badge holders-- approx. $0.30 a holder ($300)

Other money stuff

Keynote transportation

'''''II- Deadlines'''''

Final Assignment of Rooms for Workshops and Tracks

Catering counts: what are our final deadlines?

Schedule changes.

Workshops, sessions, academic, other.

Impact to attendees, organizers, funds, program design, program printing, etc. (Eli wrote this, but Amy and Monica and EVH know everything)

scheduling repeat workshops? Relationship to waitlists

Printed Program Deadlines

missing logos or ads?

Fill in options

revision process

draft review

edit process

print schedule

post printing cancellations, time changes, speaker changes, etc -- errata page

Lodging (Doubletree / Staybridge)

Sponsor Booth locations

Signage DEADLINE: Wednesday, 8/20 for design -- Will go to print on Monday

General Session:

VTM recommends a 4’x10’ ($178 + hanging fees + design work) or 4’x12” ($213+hanging fees + design work) banner that will hang behind the speaker in between the screens

Exhibit Hall:
(2) Vertical signs just inside doors.

All sponsor logos?

If yes, half on one side, half on the other side?

Little tabletop A-frame signs on tables:

100 qty = $297.50 includes full color logos

All sponsor logos?

Registration Counters:

(2) Vertical signs on either side of registration desk..

All sponsor logos?

If yes, half on one side, half on the other side?

Registration counters will have FOSS4G logo on bottom, headers on top:

Alphabet split into 6 lines (3 counters)

On-site registration (1 counter)

Speaker (1 counter)

Sponsors (1 counter)

Breakout rooms:

Podium placards (10? 9 tracks + general session)

FOSS4G logo only?

Any additional directionals needed? 24”x36” foamcore on easel.

'''''III- Communication'''''

Need another blast ASAP. These do make a difference in registration #’s.

Content is ready to go. Tanya to train KB on how to MailChimp

Need to send update to Presenters (who will do this?)

include timeslot

assuming your own laptop, otherwise slides on thumb drive

Could use some clarification from OCC on podium connections (Neill and/or VTM?)

Volunteers (Tanya)

draft schedule is available

task list is online https://docs.google.com/a/reed.edu/spreadsheets/d/127w-nt_DZgCHsmJ5IS_CwXxKlEc5IItPGLAcBOnsGyI/edit?usp=sharing (please add your needs for volunteers here and we will match someone to the tasks)

we have X volunteers confirmed and registered, Y more expected

Did someone follow up with and resolve USACE finance paperwork requests?

Need to add one or more pages to the website for venue info.

''
'''IV - Other'''
''
Sponsor updates (specifically has additional booth space been added and assigned?). Appears yes. (VTM - Eli requested)

Map Gallery Update and Vendor Hall space discussion

Rules on food for OCC (Alyssa asked about bringing donuts and maybe beer to her talk. Any rules on that?)

Review last week’s todo’s

FOSS4G 2014 Planning Meeting 19th August

2014-08-19T21:03:34Z

Wiki-RhoBott: Created page with "FOSS4G LOC Meeting, August 19th, 2014 Renewable Funding, 5:45-7:30 pm Agenda I- Money Budget overview (Darrell) Additional budget items: Gala Facilities/Additional Expenses?..."

FOSS4G LOC Meeting,
August 19th, 2014
Renewable Funding, 5:45-7:30 pm

Agenda

I- Money
Budget overview (Darrell)

Additional budget items:

Gala Facilities/Additional Expenses? Tents, DJ, etc?

Adding workshops lunch (Darrell) (http://www.campusdish.com/NR/rdonlyres/7E648CBA-A79F-45A7-A621-9B91A1F0769E/0/PSUMod_Everyday.pdf)

Final commitment for funds on opening night party? Lets Figure out how to pay for some food (Tanya / Ryan)

Trimet Tickets Purchase (Neil)

T-Shirt orders (Tanya)

More Stickers?

Lanyards (VTM)

Name badges (VTM)

Proposing 5 badge types, all double side in full color:

Attendee (approx. 500)

Sponsor (approx. 75)

Volunteer (approx. 75)

Presenter (approx. 200)

Press (approx. ?)

1 hr of design time and printing = ~$600.00 from Alphagraphics for either vertical (?”x?”) or horizontal (4” x 5”)

Need to buy name badge holders-- approx. $0.30 a holder ($300)

Other money stuff

Keynote transportation

II- Deadlines

Final Assignment of Rooms for Workshops and Tracks

Catering counts: what are our final deadlines?

Schedule changes.

Workshops, sessions, academic, other.

Impact to attendees, organizers, funds, program design, program printing, etc. (Eli wrote this, but Amy and Monica and EVH know everything)

scheduling repeat workshops? Relationship to waitlists

Printed Program Deadlines

missing logos or ads?

Fill in options

revision process

draft review

edit process

print schedule

post printing cancellations, time changes, speaker changes, etc -- errata page

Lodging (Doubletree / Staybridge)

Sponsor Booth locations

Signage DEADLINE: Wednesday, 8/20 for design -- Will go to print on Monday

General Session:

VTM recommends a 4’x10’ ($178 + hanging fees + design work) or 4’x12” ($213+hanging fees + design work) banner that will hang behind the speaker in between the screens

Exhibit Hall:
(2) Vertical signs just inside doors.

All sponsor logos?

If yes, half on one side, half on the other side?

Little tabletop A-frame signs on tables:

100 qty = $297.50 includes full color logos

All sponsor logos?

Registration Counters:

(2) Vertical signs on either side of registration desk..

All sponsor logos?

If yes, half on one side, half on the other side?

Registration counters will have FOSS4G logo on bottom, headers on top:

Alphabet split into 6 lines (3 counters)

On-site registration (1 counter)

Speaker (1 counter)

Sponsors (1 counter)

Breakout rooms:

Podium placards (10? 9 tracks + general session)

FOSS4G logo only?

Any additional directionals needed? 24”x36” foamcore on easel.

III- Communication

Need another blast ASAP. These do make a difference in registration #’s.

Content is ready to go. Tanya to train KB on how to MailChimp

Need to send update to Presenters (who will do this?)

include timeslot

assuming your own laptop, otherwise slides on thumb drive

Could use some clarification from OCC on podium connections (Neill and/or VTM?)

Volunteers (Tanya)

draft schedule is available

task list is online https://docs.google.com/a/reed.edu/spreadsheets/d/127w-nt_DZgCHsmJ5IS_CwXxKlEc5IItPGLAcBOnsGyI/edit?usp=sharing (please add your needs for volunteers here and we will match someone to the tasks)

we have X volunteers confirmed and registered, Y more expected

Did someone follow up with and resolve USACE finance paperwork requests?

Need to add one or more pages to the website for venue info.

IV - Other

Sponsor updates (specifically has additional booth space been added and assigned?). Appears yes. (VTM - Eli requested)

Map Gallery Update and Vendor Hall space discussion

Rules on food for OCC (Alyssa asked about bringing donuts and maybe beer to her talk. Any rules on that?)

Review last week’s todo’s

FOSS4G 2014

2014-08-19T20:57:37Z

Wiki-RhoBott:

'''FOSS4G 2014 will take place September 8th-13th, 2014 in Portland, Oregon, USA'''

== Category ==
Instead of updating links on this page, it might be easier to just click on the [[:Category:FOSS4G2014 | FOSS4G2014 Category]]

== Planning Meetings ==

* [[FOSS4G 2014 Planning Meeting 7th April]]
* [[FOSS4G 2014 Planning Meeting 25th March]]
* [[FOSS4G 2014 Planning Meeting 11th March]]
* [[FOSS4G 2014 Planning Meeting 25th February]]
* [[FOSS4G 2014 Planning Meeting 11th February]]
* [[FOSS4G 2014 Planning Meeting 28th January]]
* [[FOSS4G 2014 Planning Meeting 14th January]]
* [[FOSS4G 2014 Planning Meeting 17th December]]
* [[FOSS4G 2014 Planning Meeting 3rd December]]
* [[FOSS4G 2014 Planning Meeting 18th November]]
* [[FOSS4G 2014 Planning Meeting 12th November]]
* [[FOSS4G 2014 Planning Meeting 12th August]]
* [[FOSS4G 2014 Planning Meeting 19th August]]

=== Promotional Material Meetings ===
* [[FOSS4G 2014 20131202 | December 2nd Meeting ]]

== Lessons Learned ==
* [[FOSS4G 2014 Lessons Learned]] (to be filled in as we go along)

== Other ==
* [[FOSS4G 2014 Code Sprint]]

[[Category:FOSS4G2014]]
[[Category:FOSS4G]]
[[Category:Events]]