As community members, contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we commit to respect all people who participate in the community through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
This document defines the Code of Conduct along with reporting and handling guidelines for the Jenkins community. For more details about our cultural values, goals, philosophies, and structure, please consult our Governance Document.
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
Examples of behavior that contributes to a positive environment for our community include:
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
Examples of unacceptable behavior include:
The use of sexualized language or imagery, and sexual attention or advances of any kind
Trolling, insulting or derogatory comments, and personal or political attacks
Public or private harassment
Publishing others' private information, such as a physical or email address, without their explicit permission
Other conduct which could reasonably be considered inappropriate in a professional setting
Jenkins Board members are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
Community leaders (Jenkins Board members, service administrators, plugin and other 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, and will communicate reasons for moderation decisions when appropriate.
This Code of Conduct applies within all Community Spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
All resources and conversations within the Jenkins GitHub organizations are subject to the code of conduct. It includes but not limited to:
Organizations
Commits
Pull requests
Issues
Wikis
Technical criticism is always appreciated. Keep it positive and constructive. Don’t merely decry the current state of affairs. Offer and solicit suggestions as to how things may be improved. (courtesy of the Go Lang Code of Conduct)
Everything hosted under jenkins.io, jenkins-ci.org and their sub-domains such as:
All mailing lists hosted on Google Groups and other platforms.
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the Jenkins board.
If you feel somebody has breached this code, please send an email with the
relevant information (links, etc) to jenkinsci-board@googlegroups.com.
This email list is only readable by the Governance Board members.
The board may not have all of the necessary context and history,
so it’s better to describe the issue thoroughly.
All complaints will be reviewed
and investigated and will result in a response that is deemed necessary and
appropriate to the circumstances.
If you believe one of the board members has violated the code of conduct above, please email one of the other members of the Governance Board with the details (their emails are visible on the Governance Board page).
If the desired resolution cannot be reached on the Jenkins community level,
an issue can be escalated to the Continuous Delivery Foundation (CDF) by contacting the project team at conduct@cd.foundation.
See the CDF Code of Conduct for more information about reporting and enforcement in this case.
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct.
Depending on the severity of the violations the board may elect to take one of the following paths. Handling of violations will be done in private and the affected people will be notified. In the majority of cases there will not be a public announcement of the resolution, unless the Governance Board deems it necessary to announce the resolution in public.
If the severity of the violation is mild enough, the board will notify the community member that their conduct is not acceptable and needs to change.
Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
If the severity of the violation is serious enough, the board will issue an official warning to the community member.
Community Impact: A violation through a single incident or series of actions.
Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a Probation or Ban.
If the severity of the violation is serious or reprimands are not effective, the board will ask the community member to "take a break" and to step away from the community for a period of time. The intent of this is to send a clear signal to the community member that their conduct is unacceptable, de-escalate the situation for everyone who are affected, and ask the community member to reflect on their behaviors.
Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time (chats, mailing lists, pull requests, issues, events, etc.). No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a ban.
Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
Consequence: A permanent ban from any sort of public interaction within the community. The individual will be expelled from the Jenkins community. After 12 months they may appeal to the board for the ban to be lifted.
The ban will include but is not limited to:
Bans from Jenkins community chats
Deletion of their LDAP account
Blocking their GitHub username from the Jenkins GitHub organizations
Banning their email address from Jenkins mailing lists
Banning them from social media and meetup groups
Banning them from participating in Community-organized events
This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.
Jul 02, 2020 - Major update of the Code of Conduct. It was approved the project governance meeting on Jul 01 (meeting notes, developer mailing list discussion). Notable changes:
Code of Conduct is updated to Contributor Covenant, version 2.0
Align Handling of Violations with Contributor Covenant 2.0 Enforcement Guidelines
Refresh the Community Spaces section
Reference Continuous Delivery Foundation (CDF) as a second escalation level
Jan 06, 2016 - First version of Code of Conduct is introduced. It is adapted from the Contributor Covenant, version 1.3.0. The Code of Conduct was approved by the project governance meeting on 2016-01-06