Hi all,

Based on the discussion at the previous Governance board meeting and 
further reviews, we have initiated the review by the CDF Technical 
Oversight Committee. Email thread on the CDF TOC side: 
https://lists.cd.foundation/g/cdf-toc/message/471. Review of our 
application has been added to the Jul 21st CDF TOC meeting agenda, anybody 
is welcome to join the meeting. See the links here 
<https://github.com/cdfoundation/toc#communication>.  

Thanks to all contributors for the reviews, suggestions and documentation 
patches!

Best regards,
Oleg Nenashev

On Friday, July 10, 2020 at 9:33:28 AM UTC+2, Olblak wrote:
>
> Well done Oleg, you did a really great work to have crystal clear and 
> well-summarized answers to the various questions asked here and I am really 
> happy that based on the questions asked you identified lack of 
> documentation and addressed them.
>
> On Thursday, 9 July 2020 at 23:07:38 UTC+2 Mark Waite wrote:
>
>> I've reviewed the security checklist document and am ready to be a member 
>> of the Jenkins bug triage team.
>>
>> As a Jenkins developer, I agree that we're read to send the official 
>> graduation request to the CDF TOC.
>>
>> Mark Waite
>>
>> On Thursday, July 9, 2020 at 10:50:17 AM UTC-6 Oleg Nenashev wrote:
>>
>>> Hi all,
>>>
>>> Status update: We have completed the CDF Graduation checklist 
>>> <https://docs.google.com/document/d/1Ldmtny6OfEtQlCqdFWqq9Z25cxkZFX6yNiRqOOxo77c/edit?usp=sharing>.IMHO
>>>  
>>> we are ready to proceed and initiate the graduation process on the 
>>> Continuous Delivery Foundation side. 
>>>
>>> Status details:
>>>
>>>    - Jenkins Code of Conduct was updated, and now it is compliant with 
>>>    CDF requirements: https://www.jenkins.io/project/conduct/
>>>    - A new listing of Jenkins adopters was introduced on jenkins.io:  
>>>    https://www.jenkins.io/project/adopters/
>>>       - Please do not hesitate to submit pull requests and to add your 
>>>       companies there!
>>>    - Jenkins Weekly Release line is now documented on jenkins.io:  
>>>    https://www.jenkins.io/download/weekly/
>>>    - Jenkins Main repository was updated to include references to all 
>>>    the pages above:  
>>>    https://github.com/jenkinsci/jenkins/blob/master/README.md
>>>    - The default Jenkins contributing template was updated by Tim 
>>>    Jacomb:  
>>>    https://github.com/jenkinsci/.github/blob/master/CONTRIBUTING.md. 
>>>    More contributions are always welcome!
>>>    - Core infrastructure Initiative checklist is in progress, but it is 
>>>    not a blocker for graduation
>>>       - A Security Checklist has been submitted for review today. 
>>>       Reviewers: Jenkins Security Team, Jenkins Infrastructure and 
>>> Documentation 
>>>       officers
>>>       - We have an initial agreement about creating a Jenkins Bug 
>>>       Triage Team, I will proceed with the implementation next week 
>>>    
>>> If the Jenkins developers and board members agree, I will send an 
>>> official request to CDF TOC on behalf of the Jenkins project. I would 
>>> appreciate any feedback!
>>>
>>> Thanks in advance,
>>> Oleg Nenashev
>>>
>>>
>>> On Tue, Jun 16, 2020 at 11:17 PM Vlad Silverman <[email protected]> 
>>> wrote:
>>>
>>>> +1 from me on achieving CDF Graduation by July 28 based on listed 
>>>> Criteria Checklist
>>>>
>>>> Thx, Vlad
>>>>
>>>> On Jun 12, 2020, at 6:43 AM, Oleg Nenashev <[email protected]> wrote:
>>>>
>>>> I have started a Google Doc with a checklist: 
>>>> https://docs.google.com/document/d/1Ldmtny6OfEtQlCqdFWqq9Z25cxkZFX6yNiRqOOxo77c/edit?usp=sharing
>>>> Please feel free to contribute and suggest changes!
>>>>
>>>> Best regards,
>>>> Oleg
>>>>
>>>> On Friday, June 12, 2020 at 12:16:35 AM UTC+2, Marky Jackson wrote:
>>>>>
>>>>> +1 from me
>>>>>
>>>>> On Jun 11, 2020, at 2:39 PM, Tracy Miranda <[email protected]> 
>>>>> wrote:
>>>>>
>>>>> All,
>>>>>
>>>>> Last year Jenkins became a CD.Foundation <https://cd.foundation/> 
>>>>> project. The Technical Oversight Committee (TOC) of CDF set out a 
>>>>> project lifecycle 
>>>>> <https://github.com/cdfoundation/toc/blob/master/PROJECT_LIFECYCLE.md#graduated-stage>
>>>>>  
>>>>> for projects as part of the governance model. CDF is proposing Jenkins be 
>>>>> the first project to go through the process and "graduate" i.e. 
>>>>> demonstrate 
>>>>> it has met the acceptance criteria 
>>>>> <https://github.com/cdfoundation/toc/blob/master/PROJECT_LIFECYCLE.md#graduated-stage>
>>>>> .
>>>>>
>>>>> Dan Lorenc, the current TOC Chair, joined the Jenkins Governance 
>>>>> meeting <https://youtu.be/R80Rv6G-Oww> this month for an overview of 
>>>>> the process and we had a discussion around the criteria. In short, there 
>>>>> are a few housekeeping things to do for Jenkins to graduate, and the 
>>>>> process has already been beneficial to the project health (e.g. helping 
>>>>> identify that we need to strengthen the triage team, update 
>>>>> Code-of-Conduct, etc). Project graduation will also be an opportunity to 
>>>>> promote the Jenkins project via CDF channels and highlight how the 
>>>>> project 
>>>>> goes from strength to strength. 
>>>>>
>>>>> I would like to propose that the Jenkins Community commit to 
>>>>> graduating by the end of July, i.e. on July 28th 2020 at the CDF TOC 
>>>>> meeting, we show how we've met the criteria and ask for a vote. 
>>>>>
>>>>> (Note: this schedule allows CDF to graduate Jenkins as the first 
>>>>> project but also in a timely way so other CDF projects may also graduate 
>>>>> in 
>>>>> 2020.)
>>>>>
>>>>> Please go ahead and vote/comment on this proposal.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Tracy
>>>>>
>>>>>
>>>>> -- 
>>>>> 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/CACTaz6q74FSexfzGqa1BVRXVP-R%2BD161LXALOxL-bd2BrrO7Dg%40mail.gmail.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6q74FSexfzGqa1BVRXVP-R%2BD161LXALOxL-bd2BrrO7Dg%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 [email protected].
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/e483e68c-08de-4843-af21-0c00b0a5d574o%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/e483e68c-08de-4843-af21-0c00b0a5d574o%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>>
>>>> -- 
>>>>
>>> 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/I3sUP2SB2JI/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/B76A4C6D-32CA-43A6-91BD-70C6B2CA548C%40gmail.com
>>>>  
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/B76A4C6D-32CA-43A6-91BD-70C6B2CA548C%40gmail.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/8f30dd81-a4f7-4f16-9641-5b72cc1bd96bo%40googlegroups.com.

Reply via email to