Code of Conduct Update

[tnabtaf]

Hi All,

The conda Code of Conduct Finalization Committee would like the conda Organization Steering Council to consider several updates to our current Code of Conduct.

Summary of updates:

• Added a section about behavior outside of conda Organization spaces.
• Restructured and expanded text related to live events.
• Implemented reporting forms and email addresses.
• Added a voting section, and specified types of votes throughout the document
• Nominated an initial Code of Conduct Committee. All nominees were on the finalization committee.
• Added an external ombudsperson to the committee.
• Defined committee member term length, and how committee members leave and join.
• Added an Eligibility section for committee membership. This includes limits on what percentage of the committee can also be on the Steering Council.
• Inverted the community notification policy: Now notifying the community of incidents and actions (in general terms) is the default policy.
• Now explicitly accept anonymous reports.
• Expanded the conflicts of interest section. We no longer rely on self-recusal.
• Added section on what types of behavior we may not act on.
• Typo fixes

What remains to be done

• Fill the external ombudsperson spot. We are in negotiations with another organization.
• Move this code of conduct from the conda-incubator to the conda organization in GitHub. This will be done once CoC updates are approved. The CoC in conda-incubator will be updated to point to the one in conda.
• Fill in individual contact information for several committee members.

Odds and Ends

• This CoC contains a "future reference" to a Steering Council membership model (see the eligibility section) that may or may not get approved. This can be taken out if that model is not approved.

Thanks

Many, many thanks to the Code of Conduct Finalization Committee:

• Bianca Henderson
• Crystal Soja
• Dave Clements
• Eric Dill
• Filipe Pires Alvarenga Fernandes
• Katherine Kinnaman
• Ken Odegard
• Noa Tamir
• Mahe Iram Khan

This was a team effort, and the result reflects guidance and work from every member.

[tnabtaf]

Hi All,

Just a ping. Please provide any feedback you have.

[jezdez]

@tnabtaf BTW, the title of the pull request is a bit misleading, I think your intention is to first get feedback before you call on the Steering Council to vote on the CoC update. I'd suggest to simply remove the "Steering Council Vote needed" suffix from the title since the vote will be called later via a PR comment like with https://github.com/conda-incubator/ceps/pull/19#issuecomment-1150096980.

[tnabtaf]

Hi @jezdez,

Thanks for taking a careful look. I have responded to each point, and will update the document in a few places, as indicated.

Just left a few notes, I think the most concerning thing to me is the reporting form, I'd prefer an email address since it provides a free form and easily maps to a mailing list that the conda organization can maintain, instead of using a 3rd party form system.

The Jotform goes to a shared GMail address (see comments on suggestions) and then out to committee members.

Hmm. I like having a form because it gets people to think about details. However, we do want to make reporting easy. So, I will update the document to include an email option wherever we link to the form.

It would be worthwhile to have an external Code of Conduct experienced person to review this as well.

Ja! We did have @ocefpaf, @noatamir, and me on the finalization committee. All 3 of have previous CoC experience. The Ombudsperson will also be very helpful, once they are on board.

Is that enough?

@tnabtaf BTW, the title of the pull request is a bit misleading, I think your intention is to first get feedback before you call on the Steering Council to vote on the CoC update. I'd suggest to simply remove the "Steering Council Vote needed" suffix from the title since the vote will be called later via a PR comment like with https://github.com/conda-incubator/ceps/pull/19#issuecomment-1150096980.

But, but, but, I want a vote, right now! OK, I will change the title. My enthusiasm got ahead of me. (And thanks again.)

[jezdez]

Hi @jezdez,

Thanks for taking a careful look. I have responded to each point, and will update the document in a few places, as indicated.

Just left a few notes, I think the most concerning thing to me is the reporting form, I'd prefer an email address since it provides a free form and easily maps to a mailing list that the conda organization can maintain, instead of using a 3rd party form system.

The Jotform goes to a shared GMail address (see comments on suggestions) and then out to committee members.

Hmm. I like having a form because it gets people to think about details. However, we do want to make reporting easy. So, I will update the document to include an email option wherever we link to the form.

Thank you, I think this will go a long way to make reporting lower barrier, even at the cost of a slight increase in needed effort to review the reports.

It would be worthwhile to have an external Code of Conduct experienced person to review this as well.

Ja! We did have @ocefpaf, @noatamir, and me on the finalization committee. All 3 of have previous CoC experience. The Ombudsperson will also be very helpful, once they are on board.

Is that enough?

Yes, plenty! Thanks for noting this :)

@tnabtaf BTW, the title of the pull request is a bit misleading, I think your intention is to first get feedback before you call on the Steering Council to vote on the CoC update. I'd suggest to simply remove the "Steering Council Vote needed" suffix from the title since the vote will be called later via a PR comment like with conda-incubator/ceps#19 (comment).

But, but, but, I want a vote, right now! OK, I will change the title. My enthusiasm got ahead of me. (And thanks again.)

I hear you :) I'm wondering, do you think it'd be okay to formally call for the vote on the day of the next conda community meeting (22/6)? I'd be happy to help with the voting process.

[tnabtaf]

@jezdez I think the most recent commit addresses the issues you raised.

I'm wondering, do you think it'd be okay to formally call for the vote on the day of the next conda community meeting (22/6)? I'd be happy to help with the voting process.

Yes please!

[jezdez]

@conda-incubator/steering

This PR falls under the "Modifying the governance document" policy of the conda governance policy, please vote and/or comment on this PR.

This PR needs 75% of the Steering Council to vote yea to pass.

To vote, please leave Approve (yea) or Request Changes (nay) pull request reviews.

If you would like changes to the current language, please leave a comment (in the PR) or push to this branch.

This vote will end on 2022-06-30.

[beckermr]

Thanks for this hard work! As a practical matter, it will be easier to leave the CoC document here until the entire governance repo is moved. cc @tnabtaf

[jezdez]

Thanks for this hard work! As a practical matter, it will be easier to leave the CoC document here until the entire governance repo is moved. cc @tnabtaf

Agreed!

[tnabtaf]

As a practical matter, it will be easier to leave the CoC document here until the entire governance repo is moved.

Will do.

[jezdez]

@conda-incubator/steering A gentle reminder, there is an active vote running to update conda's Code of Conduct, please vote at your earliest opportunity, it ends 2022-06-30 (this Thursday)!

[beckermr]

@conda-incubator/steering please vote!

[beckermr]

@conda-incubator/steering

After chatting with @jezdez, I am extending this vote until 2022-07-13.

Please vote!

[beckermr]

@conda-incubator/steering please vote!

[beckermr]

@conda-incubator/steering Today is the last day to vote on this governance change!

[beckermr]

This vote is over. It needed a 75% threshold for quorum and passing. 21 people voted with 20 yes and 1 no. Thus the vote has passed! Merging!

[tnabtaf]

Thank you to everyone who helped create this update, and to everyone who reviewed and provided feedback on this. We will get the reporting infrastructure fully implemented within a week.