Thanks to everyone who reviewed it! Just a reminder, today we will be
voting for approving the pull request as a new Code of Conduct version

On Wed, Jun 24, 2020, 12:27 Oleg Nenashev <[email protected]> wrote:

> Hi all,
>
> Pull request with Code of conduct is ready for update:
> https://github.com/jenkins-infra/jenkins.io/pull/3477
>
> Best regards,
> Oleg
>
> On Friday, June 19, 2020 at 2:12:07 PM UTC+2, Oleg Nenashev wrote:
>>
>> UPD: At the Jun 17 Governance meeting we discussed the Code of Conduct
>> update and agreed to go forward with updating to Contributor Covenant 2.0
>> (6 votes in favor, no against/abstains). We have NOT approved the new code
>> of Conduct yet.
>>
>> Next steps:
>>
>>    - Oleg - to propose a pull request to jenkins.io with a Code of
>>    Conduct update
>>       - Contributor Covenant Update
>>       - CDF as a second level of escalation
>>       - Aligning enforcement rules, etc.
>>    - Formally voting for a suggested code of conduct PR at the next
>>    governance meeting (July 1st)
>>
>> Meeting notes:
>> https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#bookmark=id.yr5dfh4k94u6
>> Recording of the discussion: https://youtu.be/3g0GKvVHfgI?t=501
>>
>> Best regards,
>> Oleg
>>
>> On Tuesday, June 16, 2020 at 5:51:07 PM UTC+2, Oleg Nenashev wrote:
>>>
>>> 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 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
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/e75bd80d-9e4c-485e-9470-6ff677e067a4o%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/e75bd80d-9e4c-485e-9470-6ff677e067a4o%40googlegroups.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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLD1q7FrhJXjk_B7dEHt2sYQKshLt82jHgT7U6Orgxn4tA%40mail.gmail.com.

Reply via email to