|
|
|
|
Formation of End User Counsel Working Group
Jacque Salinas
Hello!
As a result of the most recent GB meeting we saw there was a need to form an End User Counsel for our members. Currently, GB member from Capital One, John Mark, has volunteered to lead the charge on this working group.
We invite our members who are interested in helping define the End User Counsel to join us on June 11, 2020 @ 3pm PST. The goal is to have the program defined and launched in July of 2020.
If you have any questions, please let me know! Thanks!
-- Jacqueline Salinas Continuous Delivery Foundation Director of Ecosystem & Community408 218 0667
|
|
|
CDF Webinar On Demand & PDF: Evolving Your Pipeline for Microservices w/DeployHub
Jacque Salinas
Hi everyone,
Thank you for joining the CDF on our 1st webinar on May 26, 2020: Evolving Your Pipeline for Microservices with DeployHub.
We had 142 registrations! Wohoo! Thank you to all who attended.
We have made the webinar on demand and you can watch the entire video on the CDF Youtube channel. We have also attached the PDF for your reference. We hope you will join us for our upcoming one on June 2nd.
Stay up to date on webinar updates on our website. Thank you!
-- Jacqueline Salinas Continuous Delivery Foundation Director of Ecosystem & Community408 218 0667
 |
|
|
|
The Pipeline: All things CI/CD & DevOps Podcast by the CDF - 1st month performance
Jacque Salinas
Hello everyone,
We want to thank all of our guests for signing up to be the first speakers for The Pipeline Podcast. I am sharing some metrics with you about performance in the first month since launching this program to help establish a baseline for KPIs. To be honest, I didn't expect this much traction but we are excited to wrap the first month with: - 4 episodes published and...
- 613 total downloads and still counting!
|
Episode Title
|
Guest
|
Publish Date
|
Publish Status
|
All Time Plays
|
|
Configuration Management - Needed Now More Than Ever!
|
Tracy Ragan
|
April 27, 2020 00:00
|
Live
|
316
|
|
The Power of Open Source Community
|
Marky Jackson
|
May 11, 2020 21:00
|
Live
|
112
|
|
CDF SIG Interoperability Chair, Cloudbees & Puppet Discuss Interoperability
|
Fatih Dermagenci, Kara de la Marck & Deepak G.
|
May 15, 2020 17:00
|
Live
|
93
|
|
Continuous Delivery, Defined
|
Dan Lorenc, Christie Wilson & Jason Hall
|
May 22, 2020 07:00
|
Live
|
92
|
|
Total downloads
|
|
613
|
If you are interested in contributing here is how: We are going to gamify this for speakers. Each quarter we will review who has had the most downloads and send them a t-shirt from our swag store. Thanks and keep on listening! -- Jacqueline Salinas Continuous Delivery Foundation Director of Ecosystem & Community408 218 0667
|
|
|
Hi,
In the TOC call, the topic came up where conduct@... is connected to. I found out that it goes to Dan, Chris, and the rest of CDF operations folks in the LF.
IOW, the alias goes to responsible adults :-)
-- Kohsuke Kawaguchi
|
|
|
Tara Hernandez
Reminder that tomorrow's meeting is on the new APAC friendly 6pm time, so we can have our Chinese language SIG contributor join us.
On Mon, May 18, 2020 at 6:19 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
I've added this to tomorrow's TOC agenda. Thanks Oleg!
Dan Lorenc
Hi Dan and all,
One thing to keep in mind is that there is already a 2.0 version of Contributor Covenant. There are some differences. Just in case, are there any plans to upgrade the Code of Conduct on the CDF side?
Once I know the target version for CDF, I will start the discussion about aligning the Contributor Covenant version in Jenkins. Our version is old, and there are some statements in newer versions which would be a good addition.
Best regards, Oleg
On Thu, May 7, 2020, 02:16 Michael Galloway via lists.cd.foundation <mgalloway=netflix.com@...> wrote:
On Wed, May 6, 2020 at 2:26 PM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Great points. I think we should encourage the CDF Code of Conduct by default, but allow others with good reason after a review. Project-level escalation sounds great as well. The CDF could be used as a second level of escalation if necessary.
Any thoughts from others here?
Dan Lorenc
Hi all,
I have another question about the current graduation requirements. Currently projects are expected to adopt the CDF Code of Conduct to graduate. In the case of the Jenkins project we have our own code of conduct which is an adopted version of Contributor Covenant 1.3 widely used in open-source projects. CDF Code of Conduct uses version 1.4 and there are some differences.
What does "Code of Conduct adoption" mean in practice? - Would it be enough to ensure that we use the same Contributor Covenant version in our project? Or would CDF TOC expect wider changes, e.g. replacing CoC completely by the CDF one?
- Would we be expected to switch the escalation/enforcement process to conduct@...? Currently the Jenkins project has its own escalation and enforcement process, managed by the Jenkins Governance Board.
Best regards, Oleg
On Mon, Apr 27, 2020 at 4:07 PM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Thanks Oleg!
I think we'll need to quickly get a plan together for security audits at the CDF level.
Dan Lorenc
Hi all,
I also have a question about a 3rd-party security audit defined by Dan Lopez in
https://github.com/cdfoundation/toc/pull/76. It may cost a lot for a big project like Jenkins if we want to have a formal security audit by a 3rd party. Just in case, does CDF have budget allocated for such audit in CDF projects? If not, such criteria may become a major obstacle.
Thanks in advance, Oleg
On Fri, Apr 24, 2020 at 5:29 PM Tracy Miranda < tmiranda@...> wrote: +1 good to have clarity then dog-food our own processes.
While it might be strange for some to see Jenkins 'graduate' think it will be good due-diligence and a good example for rest of the projects (not to mention more reasons to celebrate!)
Tracy
On Fri, Apr 24, 2020 at 11:27 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,
There's been some confusion around CDF project graduation/incubation statuses and I want to try to clear that up. If I remember correctly, when the initial projects came into the CDF we decided to keep them all at incubation status, even though some were likely to graduate quickly.
The plan was to firm up the graduation criteria, then move the more mature projects through this process as a trial run.
Does that still make sense to everyone? If so, I'd like to take a pass at the graduation criteria, then start to move Jenkins through to make sure the process makes sense and works.
Dan Lorenc
--
Michael Galloway | Delivery Engineering
mgalloway@... | m: 408.234.5205 
-- Tara Hernandez Engineering Manager Google Cloud
|
|
|
I've added this to tomorrow's TOC agenda. Thanks Oleg!
Dan Lorenc
Hi Dan and all,
One thing to keep in mind is that there is already a 2.0 version of Contributor Covenant. There are some differences. Just in case, are there any plans to upgrade the Code of Conduct on the CDF side?
Once I know the target version for CDF, I will start the discussion about aligning the Contributor Covenant version in Jenkins. Our version is old, and there are some statements in newer versions which would be a good addition.
Best regards, Oleg
On Thu, May 7, 2020, 02:16 Michael Galloway via lists.cd.foundation <mgalloway=netflix.com@...> wrote:
On Wed, May 6, 2020 at 2:26 PM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Great points. I think we should encourage the CDF Code of Conduct by default, but allow others with good reason after a review. Project-level escalation sounds great as well. The CDF could be used as a second level of escalation if necessary.
Any thoughts from others here?
Dan Lorenc
Hi all,
I have another question about the current graduation requirements. Currently projects are expected to adopt the CDF Code of Conduct to graduate. In the case of the Jenkins project we have our own code of conduct which is an adopted version of Contributor Covenant 1.3 widely used in open-source projects. CDF Code of Conduct uses version 1.4 and there are some differences.
What does "Code of Conduct adoption" mean in practice? - Would it be enough to ensure that we use the same Contributor Covenant version in our project? Or would CDF TOC expect wider changes, e.g. replacing CoC completely by the CDF one?
- Would we be expected to switch the escalation/enforcement process to conduct@...? Currently the Jenkins project has its own escalation and enforcement process, managed by the Jenkins Governance Board.
Best regards, Oleg
On Mon, Apr 27, 2020 at 4:07 PM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Thanks Oleg!
I think we'll need to quickly get a plan together for security audits at the CDF level.
Dan Lorenc
Hi all,
I also have a question about a 3rd-party security audit defined by Dan Lopez in
https://github.com/cdfoundation/toc/pull/76. It may cost a lot for a big project like Jenkins if we want to have a formal security audit by a 3rd party. Just in case, does CDF have budget allocated for such audit in CDF projects? If not, such criteria may become a major obstacle.
Thanks in advance, Oleg
On Fri, Apr 24, 2020 at 5:29 PM Tracy Miranda < tmiranda@...> wrote: +1 good to have clarity then dog-food our own processes.
While it might be strange for some to see Jenkins 'graduate' think it will be good due-diligence and a good example for rest of the projects (not to mention more reasons to celebrate!)
Tracy
On Fri, Apr 24, 2020 at 11:27 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,
There's been some confusion around CDF project graduation/incubation statuses and I want to try to clear that up. If I remember correctly, when the initial projects came into the CDF we decided to keep them all at incubation status, even though some were likely to graduate quickly.
The plan was to firm up the graduation criteria, then move the more mature projects through this process as a trial run.
Does that still make sense to everyone? If so, I'd like to take a pass at the graduation criteria, then start to move Jenkins through to make sure the process makes sense and works.
Dan Lorenc
--
Michael Galloway | Delivery Engineering
mgalloway@... | m: 408.234.5205
|
|
|
Reminder: APAC-Friendly TOC Meeting Tomorrow - 5/19
Our TOC meeting will be at 6PM Pacific tomorrow, May 19th. Going forward we will alternate meeting times.
Dan Lorenc
|
|
|
Hi Dan and all,
One thing to keep in mind is that there is already a 2.0 version of Contributor Covenant. There are some differences. Just in case, are there any plans to upgrade the Code of Conduct on the CDF side?
Once I know the target version for CDF, I will start the discussion about aligning the Contributor Covenant version in Jenkins. Our version is old, and there are some statements in newer versions which would be a good addition.
Best regards, Oleg
On Thu, May 7, 2020, 02:16 Michael Galloway via lists.cd.foundation <mgalloway=netflix.com@...> wrote:
On Wed, May 6, 2020 at 2:26 PM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Great points. I think we should encourage the CDF Code of Conduct by default, but allow others with good reason after a review. Project-level escalation sounds great as well. The CDF could be used as a second level of escalation if necessary.
Any thoughts from others here?
Dan Lorenc
Hi all,
I have another question about the current graduation requirements. Currently projects are expected to adopt the CDF Code of Conduct to graduate. In the case of the Jenkins project we have our own code of conduct which is an adopted version of Contributor Covenant 1.3 widely used in open-source projects. CDF Code of Conduct uses version 1.4 and there are some differences.
What does "Code of Conduct adoption" mean in practice? - Would it be enough to ensure that we use the same Contributor Covenant version in our project? Or would CDF TOC expect wider changes, e.g. replacing CoC completely by the CDF one?
- Would we be expected to switch the escalation/enforcement process to conduct@...? Currently the Jenkins project has its own escalation and enforcement process, managed by the Jenkins Governance Board.
Best regards, Oleg
On Mon, Apr 27, 2020 at 4:07 PM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Thanks Oleg!
I think we'll need to quickly get a plan together for security audits at the CDF level.
Dan Lorenc
Hi all,
I also have a question about a 3rd-party security audit defined by Dan Lopez in
https://github.com/cdfoundation/toc/pull/76. It may cost a lot for a big project like Jenkins if we want to have a formal security audit by a 3rd party. Just in case, does CDF have budget allocated for such audit in CDF projects? If not, such criteria may become a major obstacle.
Thanks in advance, Oleg
On Fri, Apr 24, 2020 at 5:29 PM Tracy Miranda < tmiranda@...> wrote: +1 good to have clarity then dog-food our own processes.
While it might be strange for some to see Jenkins 'graduate' think it will be good due-diligence and a good example for rest of the projects (not to mention more reasons to celebrate!)
Tracy
On Fri, Apr 24, 2020 at 11:27 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,
There's been some confusion around CDF project graduation/incubation statuses and I want to try to clear that up. If I remember correctly, when the initial projects came into the CDF we decided to keep them all at incubation status, even though some were likely to graduate quickly.
The plan was to firm up the graduation criteria, then move the more mature projects through this process as a trial run.
Does that still make sense to everyone? If so, I'd like to take a pass at the graduation criteria, then start to move Jenkins through to make sure the process makes sense and works.
Dan Lorenc
--
Michael Galloway | Delivery Engineering
mgalloway@... | m: 408.234.5205
|
|
|
Re: [MEMBER BENEFIT OPPTY] Call for volunteers & content for CDF booth @ SKILup Day
Jacque Salinas
Hi all,
IF you are still interested in providing content about one of the projects or your company - please submit your content here! I've extended the deadline to the end of day (May 14, 2020 @ 11:59PM MTN time).
We also do not have enough representation for the following projects: Spinnaker, Tekton, Jenkins X, and Screwdriver. This is a FREE opportunity to represent your member company and open source project at the CDF's virtual booth. We welcome all, feel free to pass this onto other community members. Thanks!
https://docs.google.com/spreadsheets/d/1DyBw6KhBV_3na84YhaufH9TCX_pCCV4P6r-MPVcaUtU/edit?usp=sharing
 | Jacqueline Salinas Continuous Delivery Foundation Director of Ecosystem & Community408 218 0667
|
|
|
Re: CDF Pop Up Mindshare Cocktail Hr - Cinco de Mayo theme!
Jacque Salinas
Hi Alex,
We had some tech difficulties initially but we made it work! This is a recap of what you may have missed....  | Jacqueline Salinas Continuous Delivery Foundation Director of Ecosystem & Community408 218 0667
|
|
|
Re: CDF Pop Up Mindshare Cocktail Hr - Cinco de Mayo theme!
Hi all --- How was the cocktail party? Sorry I could not make it. Hope you have another one -- looks like fun.
Thanks, Alex  ᐧ
On Tue, May 5, 2020 at 3:27 PM Jacque Salinas < jsalinas@...> wrote: Hi all - we had tech difficulties but we are on! CDF Pop Up Mindshare Cocktail Hr - Cinco de Mayo theme!
Jacqueline Salinas is inviting you to a scheduled Zoom meeting.
Join Zoom Meeting
https://us02web.zoom.us/j/81007299585?pwd=bjd2aHlEOU9JYWxrc2FiNlJJVkxRUT09
Meeting ID: 810 0729 9585
Password: 074847
One tap mobile
+12532158782,,81007299585# US (Tacoma)
+13462487799,,81007299585# US (Houston)
Dial by your location
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 669 900 9128 US (San Jose)
+1 301 715 8592 US (Germantown)
+1 312 626 6799 US (Chicago)
+1 646 558 8656 US (New York)
Meeting ID: 810 0729 9585
Find your local number: https://us02web.zoom.us/u/kbWId5z9ke |
|
|
|
Michael Galloway <mgalloway@...>
toggle quoted messageShow quoted text
On Wed, May 6, 2020 at 2:26 PM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Great points. I think we should encourage the CDF Code of Conduct by default, but allow others with good reason after a review. Project-level escalation sounds great as well. The CDF could be used as a second level of escalation if necessary.
Any thoughts from others here?
Dan Lorenc
Hi all,
I have another question about the current graduation requirements. Currently projects are expected to adopt the CDF Code of Conduct to graduate. In the case of the Jenkins project we have our own code of conduct which is an adopted version of Contributor Covenant 1.3 widely used in open-source projects. CDF Code of Conduct uses version 1.4 and there are some differences.
What does "Code of Conduct adoption" mean in practice? - Would it be enough to ensure that we use the same Contributor Covenant version in our project? Or would CDF TOC expect wider changes, e.g. replacing CoC completely by the CDF one?
- Would we be expected to switch the escalation/enforcement process to conduct@...? Currently the Jenkins project has its own escalation and enforcement process, managed by the Jenkins Governance Board.
Best regards, Oleg
On Mon, Apr 27, 2020 at 4:07 PM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Thanks Oleg!
I think we'll need to quickly get a plan together for security audits at the CDF level.
Dan Lorenc
Hi all,
I also have a question about a 3rd-party security audit defined by Dan Lopez in
https://github.com/cdfoundation/toc/pull/76. It may cost a lot for a big project like Jenkins if we want to have a formal security audit by a 3rd party. Just in case, does CDF have budget allocated for such audit in CDF projects? If not, such criteria may become a major obstacle.
Thanks in advance, Oleg
On Fri, Apr 24, 2020 at 5:29 PM Tracy Miranda < tmiranda@...> wrote: +1 good to have clarity then dog-food our own processes.
While it might be strange for some to see Jenkins 'graduate' think it will be good due-diligence and a good example for rest of the projects (not to mention more reasons to celebrate!)
Tracy
On Fri, Apr 24, 2020 at 11:27 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,
There's been some confusion around CDF project graduation/incubation statuses and I want to try to clear that up. If I remember correctly, when the initial projects came into the CDF we decided to keep them all at incubation status, even though some were likely to graduate quickly.
The plan was to firm up the graduation criteria, then move the more mature projects through this process as a trial run.
Does that still make sense to everyone? If so, I'd like to take a pass at the graduation criteria, then start to move Jenkins through to make sure the process makes sense and works.
Dan Lorenc
-- Michael Galloway | Delivery Engineering
mgalloway@... | m: 408.234.5205
|
|
|
Great points. I think we should encourage the CDF Code of Conduct by default, but allow others with good reason after a review. Project-level escalation sounds great as well. The CDF could be used as a second level of escalation if necessary.
Any thoughts from others here?
Dan Lorenc
Hi all,
I have another question about the current graduation requirements. Currently projects are expected to adopt the CDF Code of Conduct to graduate. In the case of the Jenkins project we have our own code of conduct which is an adopted version of Contributor Covenant 1.3 widely used in open-source projects. CDF Code of Conduct uses version 1.4 and there are some differences.
What does "Code of Conduct adoption" mean in practice? - Would it be enough to ensure that we use the same Contributor Covenant version in our project? Or would CDF TOC expect wider changes, e.g. replacing CoC completely by the CDF one?
- Would we be expected to switch the escalation/enforcement process to conduct@...? Currently the Jenkins project has its own escalation and enforcement process, managed by the Jenkins Governance Board.
Best regards, Oleg
On Mon, Apr 27, 2020 at 4:07 PM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Thanks Oleg!
I think we'll need to quickly get a plan together for security audits at the CDF level.
Dan Lorenc
Hi all,
I also have a question about a 3rd-party security audit defined by Dan Lopez in
https://github.com/cdfoundation/toc/pull/76. It may cost a lot for a big project like Jenkins if we want to have a formal security audit by a 3rd party. Just in case, does CDF have budget allocated for such audit in CDF projects? If not, such criteria may become a major obstacle.
Thanks in advance, Oleg
On Fri, Apr 24, 2020 at 5:29 PM Tracy Miranda < tmiranda@...> wrote: +1 good to have clarity then dog-food our own processes.
While it might be strange for some to see Jenkins 'graduate' think it will be good due-diligence and a good example for rest of the projects (not to mention more reasons to celebrate!)
Tracy
On Fri, Apr 24, 2020 at 11:27 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,
There's been some confusion around CDF project graduation/incubation statuses and I want to try to clear that up. If I remember correctly, when the initial projects came into the CDF we decided to keep them all at incubation status, even though some were likely to graduate quickly.
The plan was to firm up the graduation criteria, then move the more mature projects through this process as a trial run.
Does that still make sense to everyone? If so, I'd like to take a pass at the graduation criteria, then start to move Jenkins through to make sure the process makes sense and works.
Dan Lorenc
|
|
|
Re: Virtual Cinco de Mayo party Open Source discussion
Tracy Ragan
That may be it. Very likely.
On Wed, May 6, 2020 at 11:51 AM Tara Hernandez via lists.cd.foundation <tarahernandez=google.com@...> wrote:
Ha! I was looking at my notes this morning and wondering the same thing...
On Wed, May 6, 2020 at 9:19 AM Michael Winser via lists.cd.foundation <michaelwinser=google.com@...> wrote:
Was KBT actually kpt? Pronounced kept.
On Wed, May 6, 2020 at 11:59 AM TracyRagan < tracy@...> wrote: Hello TOC members...
Yesterday we had a virtual CincUp for Cinco de Mayo. While we only had about 10 people in total, we did have a good discussion about everyone's favorite open source tools. So I thought I would send you the list of what the group thought the TOC should be looking at:
1) Triage Party 2) kaniko 3) Keptn 4) KBT??? Not sure what this one is and could not find it in GitHub.
Tara indicated that you may have looked at some of these, but I figured I should send the list over anyway.
And yes, we had a horse join the event.
-- Kind Regards,
Tracy Ragan We make microservices easy.
--
Tara Hernandez Engineering Manager Google Cloud
-- Kind Regards,
Tracy Ragan CEO and Co-Founder / DeployHub / tel: + 1.505.424.6440/ mob: +1.505.780.0558 We make microservices easy.
|
|
|
Re: Virtual Cinco de Mayo party Open Source discussion
Tara Hernandez
Ha! I was looking at my notes this morning and wondering the same thing...
On Wed, May 6, 2020 at 9:19 AM Michael Winser via lists.cd.foundation <michaelwinser=google.com@...> wrote:
Was KBT actually kpt? Pronounced kept.
On Wed, May 6, 2020 at 11:59 AM TracyRagan < tracy@...> wrote: Hello TOC members...
Yesterday we had a virtual CincUp for Cinco de Mayo. While we only had about 10 people in total, we did have a good discussion about everyone's favorite open source tools. So I thought I would send you the list of what the group thought the TOC should be looking at:
1) Triage Party 2) kaniko 3) Keptn 4) KBT??? Not sure what this one is and could not find it in GitHub.
Tara indicated that you may have looked at some of these, but I figured I should send the list over anyway.
And yes, we had a horse join the event.
-- Kind Regards,
Tracy Ragan We make microservices easy.
-- Tara Hernandez Engineering Manager Google Cloud
|
|
|
[MEMBER BENEFIT OPPTY] Call for volunteers & content for CDF booth @ SKILup Day
Jacque Salinas
Hello CDF Members, Ambassadors, et Community,
We are seeking volunteers to help virtually staff the CDF booth. The minimum requirement is 1 hour of your time. If you are interested in helping please sign up here! (DEADLINE: May 13, 2020)
Any CDF members (all tiers) that volunteer, we are also asking them to provide the following marketing collateral from their companies. This is an opportunity to speak about your company's technology and represent the CDF & its projects all in one place. The collateral will be available for attendees who stop by the booth to download. Please provide in PDF format by DEADLINE: May 13, 2020 & send to jsalinas@.... - Case studies
- White papers
- Data sheets
- Infographics
- Swag
We are seeking technical folks who can speak about the following projects: - Spinnaker
- Tekton
- Screwdriver
- Jenkins
- Jenkins X
We are also seeking volunteers from the Governing Board, TOC, and Ambassador program to help represent the CDF and speak to its initiatives. If you have any questions, feel free to reach out to me. Thanks!
-- Jacqueline Salinas Continuous Delivery Foundation Director of Ecosystem & Community408 218 0667
 |
|
|
|
Hi all,
I have another question about the current graduation requirements. Currently projects are expected to adopt the CDF Code of Conduct to graduate. In the case of the Jenkins project we have our own code of conduct which is an adopted version of Contributor Covenant 1.3 widely used in open-source projects. CDF Code of Conduct uses version 1.4 and there are some differences.
What does "Code of Conduct adoption" mean in practice? - Would it be enough to ensure that we use the same Contributor Covenant version in our project? Or would CDF TOC expect wider changes, e.g. replacing CoC completely by the CDF one?
- Would we be expected to switch the escalation/enforcement process to conduct@...? Currently the Jenkins project has its own escalation and enforcement process, managed by the Jenkins Governance Board.
Best regards, Oleg
On Mon, Apr 27, 2020 at 4:07 PM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Thanks Oleg!
I think we'll need to quickly get a plan together for security audits at the CDF level.
Dan Lorenc
Hi all,
I also have a question about a 3rd-party security audit defined by Dan Lopez in
https://github.com/cdfoundation/toc/pull/76. It may cost a lot for a big project like Jenkins if we want to have a formal security audit by a 3rd party. Just in case, does CDF have budget allocated for such audit in CDF projects? If not, such criteria may become a major obstacle.
Thanks in advance, Oleg
On Fri, Apr 24, 2020 at 5:29 PM Tracy Miranda < tmiranda@...> wrote: +1 good to have clarity then dog-food our own processes.
While it might be strange for some to see Jenkins 'graduate' think it will be good due-diligence and a good example for rest of the projects (not to mention more reasons to celebrate!)
Tracy
On Fri, Apr 24, 2020 at 11:27 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,
There's been some confusion around CDF project graduation/incubation statuses and I want to try to clear that up. If I remember correctly, when the initial projects came into the CDF we decided to keep them all at incubation status, even though some were likely to graduate quickly.
The plan was to firm up the graduation criteria, then move the more mature projects through this process as a trial run.
Does that still make sense to everyone? If so, I'd like to take a pass at the graduation criteria, then start to move Jenkins through to make sure the process makes sense and works.
Dan Lorenc
|
|
|
Re: Virtual Cinco de Mayo party Open Source discussion
Was KBT actually kpt? Pronounced kept.
On Wed, May 6, 2020 at 11:59 AM TracyRagan < tracy@...> wrote: Hello TOC members...
Yesterday we had a virtual CincUp for Cinco de Mayo. While we only had about 10 people in total, we did have a good discussion about everyone's favorite open source tools. So I thought I would send you the list of what the group thought the TOC should be looking at:
1) Triage Party 2) kaniko 3) Keptn 4) KBT??? Not sure what this one is and could not find it in GitHub.
Tara indicated that you may have looked at some of these, but I figured I should send the list over anyway.
And yes, we had a horse join the event.
-- Kind Regards,
Tracy Ragan We make microservices easy.
|
|
|
Virtual Cinco de Mayo party Open Source discussion
Tracy Ragan
Hello TOC members...
Yesterday we had a virtual CincUp for Cinco de Mayo. While we only had about 10 people in total, we did have a good discussion about everyone's favorite open source tools. So I thought I would send you the list of what the group thought the TOC should be looking at:
1) Triage Party 2) kaniko 3) Keptn 4) KBT??? Not sure what this one is and could not find it in GitHub.
Tara indicated that you may have looked at some of these, but I figured I should send the list over anyway.
And yes, we had a horse join the event.
-- Kind Regards,
Tracy Ragan CEO and Co-Founder / DeployHub / tel: + 1.505.424.6440/ mob: +1.505.780.0558 We make microservices easy.
|
|
|
