I couldn't find any good information on the differences between the
versions so I cloned the repo and diffed between the versions. It works
pretty well, though it's a little difficult to understand the
differences at times.
I find that each new version is an improvement over the previous. The
1.4 is better than the 1.3. I find that the 2.0 version is best.
The 2.0 version changes to using "community" consistently. Formerly it
used both "project" and "community".
This line is added to expected behavior in 2.0 and I really like its
inclusion: "Accepting responsibility and apologizing to those affected
by our mistakes, and learning from the experience."
I like this addition in 2.0: "and will communicate reasons for
moderation decisions when appropriate." As one who has moderated and
been moderated in a variety of forums, communicating reasons is valuable.
This part is very nicely improved in 2.0: "All complaints will be
reviewed and investigated promptly and fairly. All community leaders are
obligated to respect the privacy and security of the reporter of any
incident." This can be extremely important when an incident occurs.
Version 2.0 adds enforcement guidelines, which are important to spell
out if there are ever any misbehaviors. Over the past few years, I've
read many cases of communities, virtual and physical, who have
encountered misbehaving individuals. Having a code of conduct has turned
out to be very valuable for them. Having some part of it include
enforcement gives the leaders and members something to refer to.
I believe the 2.0 version contains the best and latest understandings on
these issues and that we would be best to adopt it.
Jeff
On 6/12/20 3:31 PM, Tracy Miranda wrote:
+1 for proposal (1.4 version)
Tracy
On Fri, Jun 12, 2020 at 5:06 PM Oleg Nenashev <o.v.nenas...@gmail.com
<mailto:o.v.nenas...@gmail.com>> wrote:
Dear all,
As a follow-up to the previous Governance meeting, I would like to
propose updating the Jenkins Code of Conduct
<https://www.jenkins.io/project/conduct> (CoC). Currently it is
based on Contributor Covenant 1.3
<https://www.contributor-covenant.org/version/1/3/0/code-of-conduct/>
which was officially adopted on Jan 06, 2016. Contributor Covenant
is widely used in open-source projects, and this was the most
recent version at that time. Now there are versions 1.4
<https://www.contributor-covenant.org/version/1/4/code-of-conduct/>
and 2.0
<https://www.contributor-covenant.org/version/2/0/code_of_conduct/>
of Contributor Covenant.
*
*
*Why update? * New versions of Contributor Covenant extend our
version significantly, e.g. pledge and standards,
unacceptable behavior, representing the project and social media
matters, etc. These changes are pretty important IMHO. Also, we
have recently started a process of aligning the Jenkins project
with graduated project criteria defined by the Continuous Delivery
Foundation (see the proposal from Tracy Miranda here
<https://groups.google.com/forum/#!topic/jenkinsci-dev/I3sUP2SB2JI>).
One of the checklist items is adopting the CDF's Code of Conduct
<https://github.com/cdfoundation/toc/blob/master/CODE_OF_CONDUCT.md>
which is based on Contributor Covenant 1.4.
*Background.* At the last Governance Meeting on Jun 03 we had a
sync-up with Dan Lorenc who is the current CDF Technical Oversight
Committee chair. Links are here: recording
<https://youtu.be/R80Rv6G-Oww?t=1728>, meeting notes
<https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#bookmark=id.66p0d0acy2w2>.
Some clarification we have got:
* CDF does not require us to adopt the CDF Code of Conduct as
long as the Jenkins project has one and as long as they are
aligned. We interpret it as using a similar or compatible
version of Contributor Covenant.
* CDF is fine with a 2-stage escalation process. We can keep the
Jenkins Governance Board as a first stage as it is currently
documented
<https://www.jenkins.io/project/conduct/#reporting>. CDF can
act as a second level of escalation and as an entity for
mitigating cross-project Code of Conduct escalations should it
happen
* Right now there is no confirmed plan to update CDF's Code of
Conduct to version 2.0
There is also a consensus that we would like to update the code of
conduct, especially taking the terminology update discussions
<https://groups.google.com/forum/#!topic/jenkinsci-dev/CLR55wMZwZ8>
which are a sensitive topic to many Jenkins contributors. We have
3 options:
* Update to Contributor Covenant 1.4
<https://www.contributor-covenant.org/version/1/4/code-of-conduct/>
* Update to Contributor Covenant 2.0
<https://www.contributor-covenant.org/version/2/0/code_of_conduct/>.
Note that there is still no changelog for the version 2.0,
some "breaking changes" are mentioned here
<https://github.com/ContributorCovenant/contributor_covenant/issues/744>.
There is also no Git tags, so we cannot really ensure that the
version 2.0 is fixed
* Keep it as is, Contributor Covenant 1.3
<https://www.contributor-covenant.org/version/1/3/0/code-of-conduct/>
*Proposal*: I suggest updating Jenkins Code of Conduct to version
1.4. Taking the lack of changelog and Git tags for the version
2.0, I am not sure it is worth going with this version for now.
The breaking changes also seem to be pretty important, and I am
not sure we want to deviate from the CDF's CoC version and explore
the legal differences. We can update CoC again when and if CDF
goes to a higher version of Contributor Covenant.
I would appreciate any feedback, and I suggest to vote on the
update at the next Governance meeting
<https://www.jenkins.io/project/governance-meeting/> on June 17th.
Thanks for your time,
Oleg Nenashev
--
You received this message because you are subscribed to the Google
Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to jenkinsci-dev+unsubscr...@googlegroups.com
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCHDM6jEZJ%3D6t%3DWN%2BRJLiGFw%2BFTvxsjGzuKKoWHZWyW6A%40mail.gmail.com
<https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCHDM6jEZJ%3D6t%3DWN%2BRJLiGFw%2BFTvxsjGzuKKoWHZWyW6A%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-dev+unsubscr...@googlegroups.com
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6oSKm1eESf6%3DKo5%2BJ-a2Y26a17Wkd%2BjV6fpByWWhZHw-Q%40mail.gmail.com
<https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6oSKm1eESf6%3DKo5%2BJ-a2Y26a17Wkd%2BjV6fpByWWhZHw-Q%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/40298ead-f965-8f88-38d4-3d3c16cf173b%40cloudbees.com.
