OSGeo - User contributions [en]

CodeOfConduct Committee

2015-09-07T19:51:05Z

Wiki-Camilleacey: adding name and dealing with violations sections

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 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 Documents

2015-08-05T22:39:56Z

Wiki-Camilleacey: improving formatting

== Discussions ==

==== 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-05T22:37:16Z

Wiki-Camilleacey: moving documents and resources section to separate page

CodeofConduct Documents

2015-08-05T22:32:01Z

Wiki-Camilleacey: Creating the page

== 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:25:45Z

Wiki-Camilleacey: /* Membership */ add discuss mailing list

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@) but will maintain a smaller voting committee (which can be contacted on their private mailing list at coc-private@) to handle CoC incidents and violations. This smaller 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:24:21Z

Wiki-Camilleacey: /* Membership */ adding that the committee is open and voting members

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 but will maintain a smaller voting committee (which can be contacted on their private mailing list at coc-private@) to handle CoC incidents and violations. This smaller 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-07-04T12:28:44Z

Wiki-Camilleacey: /* Membership */ removing the word continue

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 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-04T12:26:57Z

Wiki-Camilleacey: /* Membership */ simplifying statement

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 continue to 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 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:57:48Z

Wiki-Camilleacey: /* Communication */ updating mailing list and meeting info

''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 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-06-21T21:10:25Z

Wiki-Camilleacey: Updating the page with notes from the SOTMUS session and trying to figure out exactly what the committee will be.

''Note: this committee is currently in formation...''

The Code Of Conduct Committee (describe purpose here)...This 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 (http://wiki.osgeo.org/wiki/Code_Of_Conduct).

== Membership ==
* The committee will consist of X members. NEED TO FILL IN. Would like to emphasize both experience and diversity. So maybe a mix of community members and people who have experience organizing FOSS4G events??

== 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 banned individuals 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

== Responsibilities ==
The group maintains a mailing list at codeofconduct@osgeo.org, and meet in the IRC channel AT SOME REGULAR INTERVAL??

== 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]]

Code Of Conduct

2015-06-21T21:00:40Z

Wiki-Camilleacey: Moving CoC committee notes over to new page and updating this page accordingly

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

== PROPOSED Code of Conduct Committee - Meeting Notes, Proposal, and Resources ==

http://wiki.osgeo.org/wiki/CodeOfConduct_Committee

[[Category: Board]]
[[Category:Conference Committee]]

Diversity

2015-03-30T16:01:23Z

Wiki-Camilleacey: /* Question: Title? */

''*** This page is structured to show a number of options for building a Code of Conduct / Diversity statement, in order to help the OSGeo community agree on the best version. It is currently [March 2015] a work in progress.***''

== Goals for Code of Conduct / Diversity Statement ==
* 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 others)
* 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)

== Questions ==
===Question: Title?===
Should this statement be called a "Diversity Statement" or a "Code of Conduct" or should we create two documents? A Diversity Statement and Code of Conduct could have different purposes. Having one document makes it easier to reference from OSGeo projects or events.

;Votes:
"Diversity Statement"
#

"Code of Conduct"
# Cameron Shorter: While I like the concept of the word "Diversity", I think it is currently confusing in "Diversity Statement" as a heading. "Diversity" is broad in meaning, and can mean Diversity in software choice, food selection, processes followed, etc, etc. We should select a heading relevant to what is being described - which is an expectation of "behaviour" or "conduct". "Code of Conduct", "Principles of Conduct" better describe what should be covered. I feel it is better to have just one document (which has a brief introduction, which expands in content, as it is easier to reference one document from external projects and events.
# Eli Adam: To me this is more about behavior or conduct so I vote for "Code of Conduct". Separating into two different documents with two different aims and names might be cleaner and make what to call it irrelevant.
# Camille Acey: I am in favor of the Code of Conduct being a separate doc that outlines expectations, behaviours, and also NEXT STEPS (such as incident reporting, decision making, possible consequences, etc.). I do, however, like the acknowledgement at the start that the community is diverse across many different spectrums.

Two documents: "Diversity Statement" as well as a "Code of Conduct"
#

===Question: Identify discriminated groups?===
Many versions of the Code of Conduct identify a range of discriminated groups: race, gender, age, sexual orientation, disability, physical appearance, national origin, ethnicity, religion. The QGIS Diversity statement simplifies to: "The QGIS Project welcomes and encourages participation by everyone.
No matter how you identify yourself or how others perceive you: we welcome you." Which is better?
;Votes:
"List discriminated groups"
#

"QGIS version - "No matter how you identify yourself or how others perceive you: we welcome you"
# Cameron Shorter

===Question: Do we note need to support non-native language speakers?===
The OGC Principles of Conduct acknowledges that we should speak clearly and avoid slang to make it easier for non-native (English) speakers. Should this be included?

;Votes:
Include language statement
# Cameron Shorter

Don't include language statement
#

== Exemplar Sources ==

=== Draft OSGeo Board Diversity Statement ===

: '''Diversity and the OSGeo Foundation'''

: The Open Source Geospatial Foundation (OSGeo) supports diversity in the community: OSGeo community members can safely interact, contribute, share, learn, and be respected for who they are. OSGeo is a large, international organisation made up of members with different cultural, historical, and linguistic backgrounds. Diversity involves acceptance and respect for these differences and more, including ethnicity, race, cultural traditions, religious expressions, age, gender, socio‐economic status, mental or physical ability, and sexual orientation. OSGeo strives to foster growth and innovation in the geospatial industry, and diversity must be respected to reach this goal.

: '''Where Diversity Applies in OSGeo'''

: Diversity and its acceptance applies to everything that OSGeo does including mailing lists, projects, documentation, language in code comments, code sprints, and events.

: '''Feedback and Concerns'''

: OSGeo is a worldwide organization. People converging in the organization have different cultures and background. In some cultures, some behaviors are considered normal, whereas in other cultures might result as disrespectful and offensive. Before getting offended from other people's behavior, consider that there could be a misunderstanding in the communication. Ask yourself if you really think that the other person meant to be disrespectful towards you. Translation is also a common cause of misunderstanding.

: Most people in the organization speak English as a second language, and it is possible that they do not always use the language with accuracy or in the way you would.

: If you are in an unpleasant situation where one person's behaviour is causing discomfort to you or someone else, consider one or more of these options:

:* Raise a direct protest against the person who is causing your discomfort: talk to each other.
:* Ask friends or others there directly for help - you are never alone, others will always help you.
:* Contact event staff, members of the local organizing committee (LOC), or volunteers.
:* Contact anybody from the OSGeo Board of Directors either personally or by email, private and in confidence, at board-priv(at)osgeo(dot)org.
:* You may also contact the President of OSGeo directly at president(at)osgeo(dot)org.
:* If you think it is appropriate, contact event security staff or local law enforcement.

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

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

Tickbox version:
* I agree to act respectfully toward others in line with the OSGeo Code of Conduct.

OSGeo Code of Conduct:

: This Code of Conduct collates the collective values adopted by our OSGeo community which baselines the behaviour we do and don’t support to ensure OSGeo is a safe and productive environment for all.

: We invite everyone to be respectful to all, regardless of race, gender, age, sexual orientation, disability, physical appearance, national origin, ethnicity, religion, or ideas. We do not tolerate harassment of others in any form. Examples of harassment include offensive comments, verbal threats or demands, sexualized images in public spaces, intimidation, stalking, harassing photography or recording, sustained disruption of events, and unwelcome physical contact or sexual attention.

: We expect all participants to follow the Code of Conduct when involved in OSGeo activities. This includes conferences, related social events, and online forums. Participants violating this Code of Conduct will be asked to desist and/or make amends. For gross or continual violations, offenders may be expelled from the event or forum without a refund, and/or banned from future events or other forums.

: Participants are encouraged to bring any concerns to the attention of event staff, the forum, forum leader, or OSGeo Board. We thank all for helping keep OSGeo welcoming, respectful, and friendly for all.

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

=== QGIS Diversity Statement ===
: The QGIS Project welcomes and encourages participation by everyone.
: No matter how you identify yourself or how others perceive you: we welcome you. We welcome contributions from everyone as long as they interact constructively with our community.
: While much of the work for our project is technical in nature, we value and encourage contributions from those with expertise in other areas, and welcome them into our community.

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

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

=== QGIS Code of Conduct ===
:Like the technical community as a whole, the QGIS team and community is made up of a mixture of professionals and volunteers from all over the world, working on every aspect of the mission - including mentorship, teaching, and connecting people.

:Diversity is one of our huge strengths, but it can also lead to communication issues and unhappiness. To that end, we have a few ground rules that we ask people to adhere to when they’re participating within this community and project. These rules apply equally to founders, mentors and those seeking help and guidance.

:This isn’t an exhaustive list of things that you can’t do. Rather, take it in the spirit in which it’s intended - a guide to make it easier to enrich all of us and the technical communities in which we participate.

:This code of conduct applies to all spaces managed by the QGIS project. This includes IRC, the mailing lists, the issue tracker, DSF events, and any other forums created by the project team which the community uses for communication.

:If you believe someone is violating the code of conduct, we ask that you report it by emailing psc @ qgis org.

: '''Be welcoming, friendly, and patient'''

: '''Be considerate'''

: Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account when making decisions. Remember that we’re a world-wide community, so you might not be communicating in someone else’s primary language.

: '''Be respectful'''

: Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one. Members of the QGIS community should be respectful when dealing with other members as well as with people outside the QGIS community.

: '''Be careful in the words that you choose'''

: We are a community of professionals, and we conduct ourselves professionally. Be kind to others. Do not insult or put down other participants. Harassment and other exclusionary behavior aren’t acceptable. This includes, but is not limited to:
: Violent threats or language directed against another person.
: Sexist, racist, or otherwise discriminatory jokes and language.
: Posting sexually explicit or violent material.
: Posting (or threatening to post) other people’s personally identifying information (“doxing”).
: Personal insults, especially those using racist or sexist terms.
: Unwelcome sexual attention.
: Advocating for, or encouraging, any of the above behavior.
: Repeated harassment of others. In general, if someone asks you to stop, then stop.

: '''When we disagree, try to understand why'''

: Disagreements, both social and technical, happen all the time and QGIS is no exception. It is important that we resolve disagreements and differing views constructively. Remember that we’re different. The strength of QGIS comes from its varied community, people from a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. Don’t forget that it is human to err and blaming each other doesn’t get us anywhere, rather offer to help resolving issues and to help learn from mistakes.

:Original text courtesy of the Speak Up! project, and Django Code of conduct

:If you have questions, feel free to contact us: psc qgis org

;Source: http://qgis.org/en/site/getinvolved/governance/codeofconduct/codeofconduct.html

; Comments
* PRO: Written in positive language
* CON: Too verbose

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

: At O'Reilly, we assume that most people are intelligent and well-intended, and we're not inclined to tell people what to do. However, we want every O'Reilly conference to be a safe and productive environment for everyone. To that end, this code of conduct spells out the behavior we support and don't support at conferences. The core of our approach is this:

: We don't condone harassment or offensive behavior, at our conference venues or anywhere. It's counter to our company values. More importantly, it's counter to our values as human beings.

: We're voicing our strong, unequivocal support of appropriate behavior by all participants at technical events, including all O'Reilly conferences. We invite you to help us make each O'Reilly conference a place that is welcoming and respectful to all participants, regardless of race, gender, age, sexual orientation, disability, physical appearance, national origin, ethnicity, or religion. So that everyone can focus on the conference itself, and the great networking and community richness that happens when we get together in person, we will not tolerate harassment of conference participants in any form—in person or online.

: Examples of harassment include offensive comments, verbal threats or demands, sexualized images in public spaces, intimidation, stalking, harassing photography or recording, sustained disruption of sessions or events, and unwelcome physical contact or sexual attention.

: We expect all participants—attendees, speakers, sponsors, and volunteers—to follow the Code of Conduct during the conference. This includes conference-related social events at off-site locations, and in related online communities and social media. Participants asked to stop any harassing behavior are expected to comply immediately. Conference participants violating this Code of Conduct may be expelled from the conference without a refund, and/or banned from future O'Reilly events, at the discretion of O'Reilly Media.

: Please bring any concerns to the immediate attention of the event staff, or contact our VP of Conferences, <name and email address>. We thank our participants for your help in keeping the event welcoming, respectful, and friendly to all participants.

: Read the blog post by Tim O'Reilly that is the basis of our functional code of conduct for all O'Reilly conferences.

: Thanks to the Lean Startup folks and the jsconf.us folks, whose Codes of Conduct inspired some changes to our own.

;Source: http://www.oreilly.com/conferences/code-of-conduct.html, downloaded 24 March 2015
;Comments
* CON: This is missing a description of graduated escalation process, and how a report would be handled.
* PRO: It makes good use of positive language

===OGC Principles of Conduct===
: 1. Abstract

: This document outlines the Principles of Conduct that shall govern personal and public interactions in any OGC activity The Principles recognize the diversity of OGC process participants, emphasize the value of mutual respect, and stress the broad applicability of our work. A separate section of the Policies and Procedures details consequences that may occur if the Principles of Conduct are violated.

: 2. Introduction

: The work of the OGC relies on cooperation among a broad cultural diversity of peoples, ideas, and communication styles. The Principles for Conduct guide our interactions as we work together to develop multiple, interoperable technologies, solutions, and interface specifications that support data, application, and services interoperability in the geospatial domain. All OGC process participants aim to abide by these Principles as we build consensus in person, at OGC meetings, in teleconferences, and in e-mail. If conflicts arise, we resolve them according to the procedures outlined in the OGC TC and IP Policies and Procedures.

: 3. OGC Principles of Conduct:

: a. OGC process participants extend respect and courtesy to their colleagues at all times.

: OGC process participants come from diverse origins and backgrounds and are equipped with multiple capabilities and ideals. Regardless of these individual differences, participants treat their colleagues with respect as persons--especially when it is difficult to agree with them. Seeing from another's point of view is often revealing, even when it fails to be compelling.

: English is the de facto language used for all OGC processes, communication, and documentation. However, English is not the native language of many OGC process participants. Native English speakers will attempt to speak clearly and a bit slowly and to limit the use of slang in order to accommodate the needs of all listeners.

: b. OGC process participants develop and test ideas impartially, without finding fault with the colleague proposing the idea.

: We dispute ideas by using reasoned argument, rather than through intimidation or ad hominem attack. Or, said in a somewhat more consensus-like way:

: "Reduce the heat and increase the light"

: c. OGC process participants think globally, devising solutions that meet the needs of diverse technical and operational environments.

: The goal of the OGC is to maintain and enhance a working, viable, scalable, global set of interfaces and protocols that provide a framework for interoperability in the geospatial domain. Many of the problems we encounter are genuinely very difficult. OGC participants use their best engineering judgment to find the best solution for the whole domain of geospatial interoperability, not just the best solution for any particular network, technology, vendor, or user. We follow the Intellectual Property Principles outlined in http://portal.opengeospatial.org/files/?artifact_id=23145.

: d. Individuals who attend OGC facilitated meetings are prepared to contribute to the ongoing work of the membership and the organization.

: OGC participants who attend OGC meetings will make their best effort to read the relevant Pending Documents, RFCs, and e-mail archives beforehand, in order to familiarize themselves with the technology under discussion. This may represent a challenge for newcomers, as e-mail archives can be difficult to locate and search, and it may not be easy to trace the history of longstanding Domain Working Group, Standards Working Group, Sub-committees, or Initiative debates. With that in mind, newcomers who attend OGC meetings are encouraged to observe and absorb whatever material they can, but should not interfere with the ongoing process of the group. OGC meetings run on a very limited time schedule, and are not intended for the education of individuals. The work of the group will continue on the mailing list, and many questions would be better expressed on the list in the months that follow.

: 4. Acknowledgements

: OGC wishes to acknowledge the work done by the IETF on a code of conduct (specifically RFC 3184). The OGC principles of conduct are modeled on their work.

;Source: http://www.opengeospatial.org/ogc/policies/conduct
;Comments
* PRO: Recognises the need to be inclusive, by making allowances for people who are not speaking in their native language.
* PRO: Encourages people to debate and potentially disagree on ideas, without attacking people personally.
* CON: Too verbose.

===FOSS4G 2015 NA and FOSS4G 2015 Code of Conduct===
: All attendees, speakers, sponsors and volunteers at our conference are required to agree with the following code of conduct. Organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensure a safe environment for everybody.

:'''The Quick Version'''

:Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.

:'''The Less Quick Version'''

:Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.

:Participants asked to stop any harassing behavior are expected to comply immediately.

:Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.

:If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.

:If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately. A member of the conference staff will be at the registration desk during conference hours.

:Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.

:We expect participants to follow these rules at conference and workshop venues and conference-related social events.

;Source: https://2015.foss4g-na.org/code-conduct, downloaded 24 March 2015, derived from others, like: http://jsconf.com/codeofconduct.html.
;Similar Source: http://2015.foss4g.org/about/codeofconduct/ FOSS4G-NA 2015 and the main international FOSS4G are using very similar CoCs. Text copied from NA.
;Comments:
:* PRO: Starts with a tick-box version which can be used during registration of an event.
:* CON: Language has interpreted by some as confrontational, and could be interpreted as implying assumption of guilt.
:* CON: It would be better if this statement could be made shorter.
===Debian diversity statement and code of conduct===
Debian has both a diversity statement and a code of conduct:
;https://www.debian.org/code_of_conduct
https://www.debian.org/intro/diversity
:(johanvdw) I added these 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).;
:I also think the second item '''"assume good faith"''' is a very important one, which is missing from the current proposal.

== Further References ==

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

==Draft OSGeo Code of Conduct==

:'''Tickbox version:'''
:* I agree to act respectfully toward others in line with the OSGeo Code of Conduct.

:'''OSGeo Code of Conduct'''
:The Open Source Geospatial Foundation (OSGeo) embraces the diversity, ideals and capabilities of our community. No matter how you identify yourself or how others perceive you: we welcome you and your constructive input into our community.

:We are regularly debating and refining ideas. We don't always agree. When we disagree we treat each other with respect as people.

:We have a multi-lingual community and are considerate toward non-native speakers, such as by speaking clearly and avoiding slang.

:Within our events and online forums, we do not accept harassment such as offensive comments, verbal threats or demands, sexualized images in public spaces, intimidation, stalking, harassing photography or recording, sustained disruption of events, and unwelcome physical contact or sexual attention. People breaking this Code of Conduct will be asked to desist and/or make amends. For gross or continual violations, offenders may be expelled from the event or forum by event organisors, or forum leaders.

:Participants are encouraged to bring any concerns to the attention of event staff, the forum, forum leader, or OSGeo Board to be addressed. We thank all for helping keep OSGeo welcoming, respectful, and friendly for all.

; Comments
* <add comments here>
* PRO:
* CON:

[[Category: Board]]