New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adopt Code of Conduct #3

Merged
merged 7 commits into from Feb 12, 2018

Conversation

Projects
None yet
3 participants
@GeorgLink
Member

GeorgLink commented Jan 17, 2018

IMPORTANT: Do not merge, until the CHAOSS Governance Board has formally adopted the Code of Conduct for the CHAOSS community.

The Code of Conduct workgroup is finalizing the text of a Code of Conduct that will be proposed to the CHAOSS community.

The Contributor Covenant has most of our desired features and is the basis of our own Code of Conduct.

We added a paragraph from Geek Feminism about the reporting and consequences. (paragraph starting with "We will respect confidentiality")

We added a paragraph about reporting yearly incidence report numbers and reviewing the CoC. (paragraph starting with "The CHAOSS Governance Board will")

@GeorgLink

This comment has been minimized.

Member

GeorgLink commented Jan 17, 2018

@GeorgLink

This comment has been minimized.

Member

GeorgLink commented Jan 27, 2018

The CHAOSS Working Group for a Code of Conduct recommends to the CHAOSS Governing Board to adopt for the CHAOSS Community the Code of Conduct in this pull-request. The working group further proposes that the Governing Board shall review the effectiveness of the Code of Conduct every year when the Code of Conduct Team provides the yearly statistic of reports.

In adopting this Code of Conduct, two things need to occur:

  1. The community needs to elect a Code of Conduct Team with 4 members.
  2. An email address needs to be created -- e.g. inclusion@chaoss.community -- that gets forwarded to only the four elected Code of Conduct Team members and can be used for incidence reports.
@germonprez

This comment has been minimized.

Contributor

germonprez commented Jan 28, 2018

Should we solicit nominations at the next board meeting?

@GeorgLink

This comment has been minimized.

Member

GeorgLink commented Jan 30, 2018

Yes, please discuss and vote on this proposal at the next Governing Board meeting.

@GeorgLink

This comment has been minimized.

Member

GeorgLink commented Feb 4, 2018

NOTE: Please add the date of the GB vote before squash-merging.

I added a version history to the document and it includes the date of the GB vote for completeness.

@germonprez

This comment has been minimized.

Contributor

germonprez commented Feb 4, 2018

Is the question, when is the board voting? If so, Feb 12th.

@GeorgLink

This comment has been minimized.

Member

GeorgLink commented Feb 4, 2018

No question, just a note that we need to update before merging. Thanks for the update though.

@jgbarah

jgbarah approved these changes Feb 5, 2018

LGTM (Nice how you look at the details!!)

@GeorgLink

This comment has been minimized.

Member

GeorgLink commented Feb 5, 2018

Thanks @jgbarah

@GeorgLink

This comment has been minimized.

Member

GeorgLink commented Feb 12, 2018

Document of the working group including the evaluation results of code of conducts: https://docs.google.com/document/d/12NVJnFccSapPKK_f5a7HjwgQ4VP2ws9Sn1IG2t8ha4g/edit?usp=sharing

@GeorgLink

This comment has been minimized.

Member

GeorgLink commented Feb 12, 2018

The GB approved this Code of Conduct today.

@GeorgLink GeorgLink merged commit b47ce3e into chaoss:master Feb 12, 2018

@GouravSardana GouravSardana referenced this pull request Mar 23, 2018

Closed

Talk to the mentors #23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment