Update w.r.t the code of conduct update options: - We got a response from Dan Lorenc (CDF TOC chair) about going with 2.0:* "I think from the TOC perspective, we're fine with anything above Contributor Covenant 1.3. We'd prefer projects upgrade over time, but don't want to be prescriptive about when or how." * https://lists.cd.foundation/g/cdf-toc/message/442. I interpret is as that we could go with 2.0 - I submitted a pull request to Contributor Covenant which summarizes the changes between 1.4 and 2.0: https://github.com/ContributorCovenant/contributor_covenant/pull/800 . It is pending review, but it provides some insights Based on feedback, I have added 2 votes to the Governance meeting:
- Vote: Update from Contributor Covenant 1.3 to 1.4 - Vote: Update from Contributor Covenant 1.3 to 2.0 Best regards, Oleg On Saturday, June 13, 2020 at 8:49:58 PM UTC+2, Oleg Nenashev wrote: > > HiJeff, > > 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 the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5624143c-918e-414a-8626-057deb76cc01o%40googlegroups.com.
