--
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-de...@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.
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
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.
I agree that Contributor Covenant 2.0 is generally better, especially for a large community like Jenkins. This version basically includes statements of the Community Covenant which covers wider areas. I am fine with exploring this option more.
I have contacted the Contributor Covenant author in the GitHub Issue referenced above. Maybe we could have an official changelog for this version. Once ready I will submit a question to CDF TOC about using this version, it is important to have explicit sign-off so that we comply with Graduated Project requirements.
Let's discuss both 1.4 and 2.0 options at the next governance meeting.
Best regards,
Oleg
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/u0T56f9MSZY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e75bd80d-9e4c-485e-9470-6ff677e067a4o%40googlegroups.com.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.