Sub-team Proposal: Code of Conduct Finalization

[tnabtaf]

Name:

Code of Conduct Finalization Committee, to be replaced by the
Code of Conduct Committee, once a proposal is adopted by the Steering Council.

Role and Responsibility:

The Code of Conduct Finalization Committee will be responsible for

• Finalizing our current code of conduct
  • Implement supporting infrastructure for the committee, such as reporting forms and email addresses.
  • Update existing policies and add other content.
• Nominating the initial members of the Code of Conduct Committee. These will be listed in the pull request submitted to the Steering Council for approval.

The Code of Conduct Committee will be responsible for

• Maintaining a welcoming and safe culture in the conda ecosystem
  • via the mechanisms described in the CoC document.
• Nominating replacement members as committee members depart.
  • This process will be described in the proposal.

The driving goal of the CoC Committee is:

Maintaining a welcoming and safe culture in the conda ecosystem

This will drive numerous subgoals in the Code of Conduct, including promoting a welcoming and safe culture across the ecosystem, having clear mechanisms for reporting, and taking prompt action on any reported or observed incidents, and, whenever possible, informing the community when incidents happen, and what actions were taken.

We will strive to incorporate current best practices from other projects.

Charter:

We are seeking a Dynamic Charter. We believe that the Code of Conduct committee should be as independent as possible from the Steering Council. Unfortunately, there are well known examples of leadership in open source projects being the source of Code of Conduct violations. Therefore we believe the Code of Conduct Committee should be able to select its own members, and also have minimal overlap with the Steering Council membership.

Initial Members:

The Finalizing committee will finalize the Code of Conduct, and will include in that document nominations for the Code of Conduct Committee that will take over once the Code of Conduct is approved. We expect some overlap between the finalizing committee and the first actual committee.

Initial Finalizing Committee members:

• Crystal Soja (@csoja), Anaconda
• Eric Dill (@ericdill), Voltron Data and conda-forge
• Ken Odegard (@kenodegard), Anaconda
• Mahe Khan (@ForgottenProgramme), Anaconda
• Filipe Fernandes (@ocefpaf), IOOS/NOAA
• Dave Clements (@tnabtaf), Anaconda

Note:

• This initial membership is Anaconda and North America heavy. However, we are an open committee and hope to add more interested people as we go.
• When finalizing the Code of Conduct, we are likely to add restrictions on what percentage of that committee's members can come from one organization. Thus any skew in the finalizing committee will not be perpetuated in the actual CoC committee.

[tnabtaf]

Hi All,

PR #49 was submitted yesterday. If you are on the Steering Council, please let us know what, if anything, needs clarification and correction. We think it's ready to go, but we have been looking at it for a while...

[tnabtaf]

PR #49 was approved and merged today. We have an updated code of conduct. I will work on finalizing the reporting infrastructure this week (most email wrangling) within a week, and then close this issue.

Thanks to everyone who helped with this update!

[tnabtaf]

The updated Code of Conduct is now a thing, and it includes the members of the our COC Committee. The CoC Committee is now a dynamic subteam.