Skip to content

Latest commit

 

History

History
145 lines (104 loc) · 9.29 KB

CODE_OF_CONDUCT.md

File metadata and controls

145 lines (104 loc) · 9.29 KB

Code of Conduct

cert-manager uses the CNCF Community Code of Conduct, which is reproduced below from upstream commit c0d29e5e94be2ac2c1370d663ce3a08ada77921f.

The latest version of the upstream CNCF Code of Conduct is at https://github.com/cncf/foundation/blob/main/code-of-conduct.md

If the version reproduced below is out of date, the Code of Conduct which applies to the cert-manager project is the latest version upstream.

cert-manager Project Code of Conduct Committee

Given the size of the team involved with cert-manager, there is no explicitly defined separate team of people responsible for policing the code of conduct for matters which fall exclusively under the jurisdiction of the cert-manager project.

If a committee is needed to evaluate a potential violation of the Code of Conduct, that team shall be made up of both the steering committee and maintainers. All steering committee members and all maintainers are invited, and all are expected to attend if they're able to.

Any decisions made by the Code of Conduct committee should seek unanimous consent, but failing that should fall back to a majority vote.

If the alleged violator is in the steering committee or the maintainer group, that person is ineligible to sit on the committee. The same is true for anyone in the group who has a conflict of interest. Importantly, note the CNCF Transfer by Project CoC Responders section. If a majority of potential committee members have hard conflicts of interest, then the reported issue should be transferred to the CNCF CoC Committee.

To make a report which falls under the jurisdiction of the cert-manager Code of Conduct committee, a user can email cert-manager-maintainers@googlegroups.com, which is readable only by maintainers. If the user has concerns about contacting all maintainers they can reach out to an individual maintainer or steering committee member.

If the reporter doesn't feel comfortable reaching out to any individual maintainer or steering committee member, they're encouraged to reach out to the CNCF CoC Committee directly. More details are in the "Reporting" section in the copied code of conduct below.

CNCF Community Code of Conduct v1.3

Other languages available:

Community Code of Conduct

As contributors, maintainers, and participants in the CNCF community, and in the interest of fostering an open and welcoming community, we pledge to respect all people who participate or contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, attending conferences or events, or engaging in other community or project activities.

We are committed to making participation in the CNCF community a harassment-free experience for everyone, regardless of age, body size, caste, disability, ethnicity, level of experience, family status, gender, gender identity and expression, marital status, military or veteran status, nationality, personal appearance, race, religion, sexual orientation, socioeconomic status, tribe, or any other dimension of diversity.

Scope

This code of conduct applies:

  • within project and community spaces,
  • in other spaces when an individual CNCF community participant's words or actions are directed at or are about a CNCF project, the CNCF community, or another CNCF community participant.

CNCF Events

CNCF events that are produced by the Linux Foundation with professional events staff are governed by the Linux Foundation Events Code of Conduct available on the event page. This is designed to be used in conjunction with the CNCF Code of Conduct.

Our Standards

The CNCF Community is open, inclusive and respectful. Every member of our community has the right to have their identity respected.

Examples of behavior that contributes to a positive environment include but are not limited to:

  • Demonstrating empathy and kindness toward other people
  • Being respectful of differing opinions, viewpoints, and experiences
  • Giving and gracefully accepting constructive feedback
  • Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
  • Focusing on what is best not just for us as individuals, but for the overall community
  • Using welcoming and inclusive language

Examples of unacceptable behavior include but are not limited to:

  • The use of sexualized language or imagery
  • Trolling, insulting or derogatory comments, and personal or political attacks
  • Public or private harassment in any form
  • Publishing others' private information, such as a physical or email address, without their explicit permission
  • Violence, threatening violence, or encouraging others to engage in violent behavior
  • Stalking or following someone without their consent
  • Unwelcome physical contact
  • Unwelcome sexual or romantic attention or advances
  • Other conduct which could reasonably be considered inappropriate in a professional setting

The following behaviors are also prohibited:

  • Providing knowingly false or misleading information in connection with a Code of Conduct investigation or otherwise intentionally tampering with an investigation.
  • Retaliating against a person because they reported an incident or provided information about an incident as a witness.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing a CNCF project. Project maintainers who do not follow or enforce the Code of Conduct may be temporarily or permanently removed from the project team.

Reporting

For incidents occurring in the Kubernetes community, contact the Kubernetes Code of Conduct Committee via conduct@kubernetes.io. You can expect a response within three business days.

For other projects, or for incidents that are project-agnostic or impact multiple CNCF projects, please contact the CNCF Code of Conduct Committee via conduct@cncf.io. Alternatively, you can contact any of the individual members of the CNCF Code of Conduct Committee to submit your report. For more detailed instructions on how to submit a report, including how to submit a report anonymously, please see our Incident Resolution Procedures. You can expect a response within three business days.

For incidents occurring at CNCF event that is produced by the Linux Foundation, please contact eventconduct@cncf.io.

Enforcement

Upon review and investigation of a reported incident, the CoC response team that has jurisdiction will determine what action is appropriate based on this Code of Conduct and its related documentation.

For information about which Code of Conduct incidents are handled by project leadership, which incidents are handled by the CNCF Code of Conduct Committee, and which incidents are handled by the Linux Foundation (including its events team), see our Jurisdiction Policy.

Amendments

Consistent with the CNCF Charter, any substantive changes to this Code of Conduct must be approved by the Technical Oversight Committee.

Acknowledgements

This Code of Conduct is adapted from the Contributor Covenant (http://contributor-covenant.org), version 2.0 available at http://contributor-covenant.org/version/2/0/code_of_conduct/