Over the past couple months, we have been working on a long overdue Code of Conduct for the Jenkins project (meeting minutes here and here). Following in the footsteps of other projects like the Apache Software Foundation, Go lang and countless others, we have adopted this code of conduct to help set guidelines for what behaviors are acceptable, and what behaviors are not, when acting within the Jenkins community or on behalf of the Jenkins project.
I would like to extend our gratitude to the authors of the Contributor Covenant who provided us with a very good and mostly finished Code of Conduct template. We have adapted the covenant to meet the unique needs of a multifaceted project like Jenkins.
The document itself is broken down into three sections, all of which I encourage you to read:
Similar to many other process and philisophical documents in the Jenkins
project, the document is not etched in stone and is therefore intended to be
updated. If you’re interested in participating in the discussion about this,
and other topics around how the Jenkins project operates, I invite you to the
#jenkins-community IRC channel on the Freenode
network or to our regularly scheduled
governance
meetings.
|
R. Tyler Croy
R. Tyler Croy has been part of the Jenkins project for the past seven years. While avoiding contributing any Java code, Tyler is involved in many of the other aspects of the project which keep it running, such as this website, infrastructure, governance, etc. |