Date   

[VOTE] - Tekton graduation in the CDF

Oleg Nenashev
 

Dear all,

As we discussed at today's public TOC meeting, the Technical Oversight Committee decided to start a public voting for the project's incubation in the Continuous Delivery Foundation. Please share your feedback, or cast your binding and non-binding votes by October 17th, 23:59 UTC. You can vote and share feedback by responding to this thread or by reviewing this pull request.

References:
Please note that some documentation updates are still pending. Also, one of the components in the scope (Tekton Operator) has not reached the OpenSSF badge and now stands at 94%. At the meeting on Oct 04 the TOC agreed that there are no blockers that would prevent Tekton from graduating, especially taking huge adoption and successful external security audits. Based on that, we start voting and open the public feedback. To graduate, the project needs to reach the supermajority of votes (6 binding +1 votes), and to have no blocking feedback/discussions until the end of the vote.

Please cast your votes!

Best regards,
Oleg Nenashev
CDF TOC Chair





3 Summits happening this fall [Open CFP and Programs] and other updates

Roxanne Joncas
 

Dear CDF folks,


Here's what's been happening in our community this month!


Highlight: We're hosting three Summits this fall! 🍂


Continuous Delivery Mini Summit 


Spinnaker Summit

  • Co-located with KubeCon + CloudNativeCon NA

  • October 23-24, Detroit, Michigan

  • Program announced!


Continuous Delivery Summit

  • Co-located with KubeCon + CloudNativeCon NA

  • October 25, Detroit, Michigan

  • Call for Papers open (free CD Summit pass included)


Full Community Events List (including, CDF Online Meetup, DevOps World, swampUP, and more)


Blog:


Wishing you a lovely weekend!


Regards,

Roxanne


Re: Reference Arch. - CDEvents Vocab. and Landscape

Robert Reeves
 

Hi, Tracy!

 

Thanks for the thoughts.

 

If we are going to share with the community the way DevOps gets done, we’re going to have to say some pretty obvious things like use a “artifact repository” to store and version your stuff. There are a lot of ways to do that, both free or commercial or you could roll your own.

 

Maybe I’m missing something, but we should absolutely be recommending a tool *type*. We would say “use a hammer -- Estwing is a CDF member that makes hammers” not “use a Estwing hammer cause they are the best”.

 

Would love to chat about this so I can understand. Pretty sure I’m missing a lot of context here.

 

Thanks!

 

Robert

 

 

Robert Reeves

CTO | Liquibase

Mobile: 5124222443

Email: r2@...

Website: www.liquibase.com

twitter

linkedin

stack-overflow

github

youtube

website

Get certified and learn at learn.liquibase.com | Get real-time status & monitoring at hub.liquibase.com

 

 

From: cdf-toc@... <cdf-toc@...> On Behalf Of TracyRagan via lists.cd.foundation
Sent: Monday, August 1, 2022 11:41 AM
To: cdf-toc <cdf-toc@...>
Subject: [cdf-toc] Reference Arch. - CDEvents Vocab. and Landscape

 

Hello distinguished TOC members,

 

I spent some time thinking through our reference architecture proposal combined with the work we have already started on other efforts. It seems to me that we should have a discussion on combining some resources.

 

My thoughts:

 

The reference architecture should not 'recommend' or 'identify' particular tools. But it could point to a 'vocabulary,' and that 'vocabulary' should align to the Landscape as well as CDEvents.

 

The CDEvents team has started working on the vocabulary for Events. It seems we could use this as the jumping-off point for all three products (reference, landscape, CDEvents).  

 

My thought is that we bring these groups together in a 'Working Group' that can build upon the vocabulary work the CDEvents team has already started. It still needs to be expanded and refined, but the basic constructs are there. The Landscape could then be updated based on these vocabulary 'buckets.' The Reference Architecture would refer to these 'buckets.'  

 

Most important is we would be forced to finally solidify how we talk about CD overall and build upon all three in a unified way. 

 

I have an all-day commitment tomorrow and cannot attend the meeting. Hoping we can think about defining a TOC Vocabulary Working Group on this very important task.  

 

--

Kind Regards,

 

Tracy Ragan

CEO and Co-Founder / DeployHub / tel: + 1.505.424.6440/ mob: +1.505.780.0558

Follow me on: Blog / Twitter Facebook / LinkedIn / YouTube / GitHub

We make microservices easy. 

 

Image removed by sender.

 


Invitation: CDF Technical Oversight Committee Meeting @ Tue 2022-08-02 18:00 - 19:00 (CEST) (cdf-toc@lists.cd.foundation)

Oleg Nenashev
 

CDF Technical Oversight Committee Meeting
Join with Google Meet – CDF Technical Oversight Committee (TOC) facilitates communication and collaboration among the Technical ProjectsVirtual event URL: https://community.cd.foundation/events/details/cd-foundation-technica
 
CDF Technical Oversight Committee (TOC) facilitates communication and collaboration among the Technical Projects

Virtual event URL: https://community.cd.foundation/events/details/cd-foundation-technical-oversight-committee-toc-presents-cdf-technical-oversight-committee-meeting-7/

Make sure to join the #toc channel on the CDF Slack too!

When

Tuesday 2022-08-02 ⋅ 18:00 – 19:00 (Central European Time - Zurich)

Location

https://community.cd.foundation/events/details/cd-foundation-technical-oversight-committee-toc-presents-cdf-technical-oversight-committee-meeting-7/
View map
Reply for cdf-toc@...

Invitation from Google Calendar

You are receiving this email because you are an attendee of the event. To stop receiving future updates for this event, decline this event.

Forwarding this invitation could allow any recipient to send a response to the organiser, be added to the guest list, invite others regardless of their own invitation status or modify your RSVP. Learn more


Reference Arch. - CDEvents Vocab. and Landscape

Tracy Ragan
 

Hello distinguished TOC members,

I spent some time thinking through our reference architecture proposal combined with the work we have already started on other efforts. It seems to me that we should have a discussion on combining some resources.

My thoughts:

The reference architecture should not 'recommend' or 'identify' particular tools. But it could point to a 'vocabulary,' and that 'vocabulary' should align to the Landscape as well as CDEvents.

The CDEvents team has started working on the vocabulary for Events. It seems we could use this as the jumping-off point for all three products (reference, landscape, CDEvents).  

My thought is that we bring these groups together in a 'Working Group' that can build upon the vocabulary work the CDEvents team has already started. It still needs to be expanded and refined, but the basic constructs are there. The Landscape could then be updated based on these vocabulary 'buckets.' The Reference Architecture would refer to these 'buckets.'  

Most important is we would be forced to finally solidify how we talk about CD overall and build upon all three in a unified way. 

I have an all-day commitment tomorrow and cannot attend the meeting. Hoping we can think about defining a TOC Vocabulary Working Group on this very important task.  

--
Kind Regards,

Tracy Ragan
CEO and Co-Founder / DeployHub / tel: + 1.505.424.6440/ mob: +1.505.780.0558
Follow me on: Blog / Twitter Facebook / LinkedIn / YouTube / GitHub
We make microservices easy. 





Re: VOTE: Accepting project Pyrsia as a CDF incubating project

Kara de la Marck
 

+1 non-binding Pyrsia
Kind regards,

Kara de la Marck 
Continuous Delivery Foundation
LinkedIn @karadelamarck   
Twitter @KaraMarck



On Wed, Jul 20, 2022 at 11:32 AM Oleg Nenashev <o.v.nenashev@...> wrote:
Dear all,

As decided by the TOC meeting yesterday, we would like to start public voting for adding Project Pyrsia to the Continuous Delivery Foundation (Project proposal). If accepted, the project would join the CDF as an incubating project. All votes and comments will be welcome! Please cast your vote by July 29th, 10PM UTC.

Persia is a Decentralized Package Network. Pyrsia aims to secure the software supply chain of open-source dependencies by creating a system that secures open-source builds and distribution. As concluded by the TOC, the project fits the scope of the CDF which targets providing solutions and best practices for all aspects of software delivery.

References:
For more information about the CDF project lifecycle and membership requirements, see this page. Thanks a lot to Steve and Melissa for driving this proposal in the TOC!

Best regards,
Oleg Nenashev
CDF TOC Chair


Re: VOTE: Accepting project Pyrsia as a CDF incubating project

Sudhindra Rao <sudhindra.r.rao@...>
 

Hi Justin, 
I think there was a similar question on the slack channel. I will respond in the same way 

As related to Pyrsia .. No there are no crypto-coins involved. Pyrsia does not intend to incentivize participation using any cryptocurrency.
We are only working with organizations that would become part of the governing board of Pyrsia to bring up trusted nodes. The trust mechanisms will be deliberately available only to these orgs. Additionally the membership also gives the org the ability to crosscheck other orgs and their security etiquette for Pyrsia.
Thus the Pyrsia governing board maintains a high bar of how the trusted nodes work together.
For regular nodes - they are pretty much open to anyone who would like to download and install pyrsia node on their machine. Since these nodes do not have the ability to commit to the network(meaning add new binaries/packages to it) and thus do not have the ability to commit to the transparency log, it is deemed safe. These nodes will still enhance the experience using decentralized P2P exchange of info/binaries and also leverage the network for better throughput by streaming from multiple nodes.

Please let me know if that was good explanation and I can elaborate more.

Thanks,
Sudhindra.


Re: VOTE: Accepting project Pyrsia as a CDF incubating project

Melissa McKay
 

+1 binding on Pyrsia


On Wed, Jul 20, 2022, 12:49 PM steve via lists.cd.foundation <steve=deployhub.com@...> wrote:
+1 binding


Re: VOTE: Accepting project Pyrsia as a CDF incubating project

steve@...
 

+1 binding


Re: VOTE: Accepting project Pyrsia as a CDF incubating project

Justin Abrahms <justin@...>
 

+1 from me.

Thanks to Sudhindra Rao who said in slack:

As related to Pyrsia .. No there are no cryptocoins involved. Pyrsia does not intend to incentivitize participation using any cryptocurrency. We are only working with organizations that would become part of the governing board of Pyrsia to bring up trusted nodes. The trust mechanisms will be deliberately available only to these orgs. Additionally the membership also gives the org the ability to crosscheck other orgs and their security etiquette for Pyrsia. Thus the Pyrsia governing board maintains a high bar of how the trusted nodes work together. For regular nodes - they are pretty much open to anyone who would like to download and install pyrsia node on their machine. Since these nodes do not have the ability to commit to the network(meaning add new binaries/packages to it) and thus do not have the ability to commit to the transparency log, it is deemed safe. These nodes will still enhance the experience using decentralized P2P exchange of info/binaries and also leverage the network for better throughput by streaming from multiple nodes.


Re: VOTE: Accepting project Pyrsia as a CDF incubating project

Mark Waite
 

+1 from me

On Wed, Jul 20, 2022 at 12:33 PM Sudhindra Rao <sudhindra.r.rao@...> wrote:
+1 non-binding on Pyrsia


Re: VOTE: Accepting project Pyrsia as a CDF incubating project

Sudhindra Rao <sudhindra.r.rao@...>
 

+1 non-binding on Pyrsia


Re: VOTE: Accepting project Pyrsia as a CDF incubating project

David Lai
 

+1 on Pyrsia

 

Thanks,

David

 

From: cdf-toc@... <cdf-toc@...> On Behalf Of TracyRagan via lists.cd.foundation
Sent: Wednesday, July 20, 2022 8:56 AM
To: Oleg Nenashev <o.v.nenashev@...>
Cc: cdf-toc <cdf-toc@...>
Subject: Re: [cdf-toc] VOTE: Accepting project Pyrsia as a CDF incubating project

 

+1 on Pyrsia

 

On Wed, Jul 20, 2022 at 9:32 AM Oleg Nenashev <o.v.nenashev@...> wrote:

Dear all,

 

As decided by the TOC meeting yesterday, we would like to start public voting for adding Project Pyrsia to the Continuous Delivery Foundation (Project proposal). If accepted, the project would join the CDF as an incubating project. All votes and comments will be welcome! Please cast your vote by July 29th, 10PM UTC.

 

Persia is a Decentralized Package Network. Pyrsia aims to secure the software supply chain of open-source dependencies by creating a system that secures open-source builds and distribution. As concluded by the TOC, the project fits the scope of the CDF which targets providing solutions and best practices for all aspects of software delivery.

 

References:

For more information about the CDF project lifecycle and membership requirements, see this page. Thanks a lot to Steve and Melissa for driving this proposal in the TOC!

 

Best regards,

Oleg Nenashev

CDF TOC Chair


 

--

Kind Regards,

 

Tracy Ragan

CEO and Co-Founder / DeployHub / tel: + 1.505.424.6440/ mob: +1.505.780.0558

Follow me on: Blog / Twitter Facebook / LinkedIn / YouTube / GitHub

We make microservices easy. 

 

 


Re: VOTE: Accepting project Pyrsia as a CDF incubating project

Justin Abrahms <justin@...>
 

I didn't see it in the document, but is there financial incentive around being one of the trusted or untrusted nodes that are reproducing builds? e.g. are they minting some sort of crypto coin?


Re: VOTE: Accepting project Pyrsia as a CDF incubating project

Andrea Frittoli
 

+1 binding

On Wed, 20 Jul 2022 at 16:32, Oleg Nenashev <o.v.nenashev@...> wrote:
Dear all,

As decided by the TOC meeting yesterday, we would like to start public voting for adding Project Pyrsia to the Continuous Delivery Foundation (Project proposal). If accepted, the project would join the CDF as an incubating project. All votes and comments will be welcome! Please cast your vote by July 29th, 10PM UTC.

Persia is a Decentralized Package Network. Pyrsia aims to secure the software supply chain of open-source dependencies by creating a system that secures open-source builds and distribution. As concluded by the TOC, the project fits the scope of the CDF which targets providing solutions and best practices for all aspects of software delivery.

References:
For more information about the CDF project lifecycle and membership requirements, see this page. Thanks a lot to Steve and Melissa for driving this proposal in the TOC!

Best regards,
Oleg Nenashev
CDF TOC Chair


Re: VOTE: Accepting project Pyrsia as a CDF incubating project

Robert Reeves
 

+1

 

Robert Reeves

CTO | Liquibase

Mobile: 5124222443

Email: r2@...

Website: www.liquibase.com

twitter

linkedin

stack-overflow

github

youtube

website

Get certified and learn at learn.liquibase.com | Get real-time status & monitoring at hub.liquibase.com

 

 

From: cdf-toc@... <cdf-toc@...> On Behalf Of Oleg Nenashev via lists.cd.foundation
Sent: Wednesday, July 20, 2022 11:02 AM
To: Tracy Ragan <tracy@...>
Cc: cdf-toc <cdf-toc@...>
Subject: Re: [cdf-toc] VOTE: Accepting project Pyrsia as a CDF incubating project

 

+1 binding from me by the way

 

On Wed, 20 Jul 2022, 17:56 Tracy Ragan, <tracy@...> wrote:

+1 on Pyrsia

 

On Wed, Jul 20, 2022 at 9:32 AM Oleg Nenashev <o.v.nenashev@...> wrote:

Dear all,

 

As decided by the TOC meeting yesterday, we would like to start public voting for adding Project Pyrsia to the Continuous Delivery Foundation (Project proposal). If accepted, the project would join the CDF as an incubating project. All votes and comments will be welcome! Please cast your vote by July 29th, 10PM UTC.

 

Persia is a Decentralized Package Network. Pyrsia aims to secure the software supply chain of open-source dependencies by creating a system that secures open-source builds and distribution. As concluded by the TOC, the project fits the scope of the CDF which targets providing solutions and best practices for all aspects of software delivery.

 

References:

For more information about the CDF project lifecycle and membership requirements, see this page. Thanks a lot to Steve and Melissa for driving this proposal in the TOC!

 

Best regards,

Oleg Nenashev

CDF TOC Chair


 

--

Kind Regards,

 

Tracy Ragan

CEO and Co-Founder / DeployHub / tel: + 1.505.424.6440/ mob: +1.505.780.0558

Follow me on: Blog / Twitter Facebook / LinkedIn / YouTube / GitHub

We make microservices easy. 

 

Image removed by sender.

 


Re: VOTE: Accepting project Pyrsia as a CDF incubating project

Oleg Nenashev
 

+1 binding from me by the way


On Wed, 20 Jul 2022, 17:56 Tracy Ragan, <tracy@...> wrote:
+1 on Pyrsia

On Wed, Jul 20, 2022 at 9:32 AM Oleg Nenashev <o.v.nenashev@...> wrote:
Dear all,

As decided by the TOC meeting yesterday, we would like to start public voting for adding Project Pyrsia to the Continuous Delivery Foundation (Project proposal). If accepted, the project would join the CDF as an incubating project. All votes and comments will be welcome! Please cast your vote by July 29th, 10PM UTC.

Persia is a Decentralized Package Network. Pyrsia aims to secure the software supply chain of open-source dependencies by creating a system that secures open-source builds and distribution. As concluded by the TOC, the project fits the scope of the CDF which targets providing solutions and best practices for all aspects of software delivery.

References:
For more information about the CDF project lifecycle and membership requirements, see this page. Thanks a lot to Steve and Melissa for driving this proposal in the TOC!

Best regards,
Oleg Nenashev
CDF TOC Chair



--
Kind Regards,

Tracy Ragan
CEO and Co-Founder / DeployHub / tel: + 1.505.424.6440/ mob: +1.505.780.0558
Follow me on: Blog / Twitter Facebook / LinkedIn / YouTube / GitHub
We make microservices easy. 





Re: VOTE: Accepting project Pyrsia as a CDF incubating project

Tracy Ragan
 

+1 on Pyrsia

On Wed, Jul 20, 2022 at 9:32 AM Oleg Nenashev <o.v.nenashev@...> wrote:
Dear all,

As decided by the TOC meeting yesterday, we would like to start public voting for adding Project Pyrsia to the Continuous Delivery Foundation (Project proposal). If accepted, the project would join the CDF as an incubating project. All votes and comments will be welcome! Please cast your vote by July 29th, 10PM UTC.

Persia is a Decentralized Package Network. Pyrsia aims to secure the software supply chain of open-source dependencies by creating a system that secures open-source builds and distribution. As concluded by the TOC, the project fits the scope of the CDF which targets providing solutions and best practices for all aspects of software delivery.

References:
For more information about the CDF project lifecycle and membership requirements, see this page. Thanks a lot to Steve and Melissa for driving this proposal in the TOC!

Best regards,
Oleg Nenashev
CDF TOC Chair



--
Kind Regards,

Tracy Ragan
CEO and Co-Founder / DeployHub / tel: + 1.505.424.6440/ mob: +1.505.780.0558
Follow me on: Blog / Twitter Facebook / LinkedIn / YouTube / GitHub
We make microservices easy. 





VOTE: Accepting project Pyrsia as a CDF incubating project

Oleg Nenashev
 

Dear all,

As decided by the TOC meeting yesterday, we would like to start public voting for adding Project Pyrsia to the Continuous Delivery Foundation (Project proposal). If accepted, the project would join the CDF as an incubating project. All votes and comments will be welcome! Please cast your vote by July 29th, 10PM UTC.

Persia is a Decentralized Package Network. Pyrsia aims to secure the software supply chain of open-source dependencies by creating a system that secures open-source builds and distribution. As concluded by the TOC, the project fits the scope of the CDF which targets providing solutions and best practices for all aspects of software delivery.

References:
For more information about the CDF project lifecycle and membership requirements, see this page. Thanks a lot to Steve and Melissa for driving this proposal in the TOC!

Best regards,
Oleg Nenashev
CDF TOC Chair


ATTENTION | The Nomination Period for The TOC Chair is Open.

Michelle Martineau
 

CDFoundation TOC,


The nomination period for The TOC Chair is open. 

Individuals interested in running for this position or individuals interested to nominate others must record the nominations under corresponding GitHub issue. Please note that only the current members of the TOC are eligible to nominate themselves or be nominated by other members of the TOC. 


Please include:

  • Name of the candidate

  • Their biography and statement of intent on why they would be a good person to hold the position.

  • Any other relevant Information

 

If you are nominating someone other than yourself, please confirm their interest privately BEFORE you nominate them publicly. It is also required that individuals nominated by others accept their nominations directly under the GitHub issue.


Election Cycle:

July 19: Present election timeline to TOC 

July 20: Start of self-nomination period for the TOC Chair 

August 3: End of self-nomination period for the TOC Chair 

August 4: Start of voting period 

August 15: End of voting period and results announced 

August 16: The new chair gets seated during TOC Meeting 

Term: 8/16/2022 - 8/16/2023

____________________________________________________________________________


Responsibilities Include:

Preside over meetings

Ensure minutes are taken

Drive the TOC agenda with input from the TOC representatives

Serve on the Governing Board as the TOC’s representative


Please see Charter for more information.


______________________________________________________________________


Please find the link to the Github issue to submit your nomination for the open position below.

Nominate Here


Please let me know if you have any questions or issues submitting your nomination.



MICHELLE MARTINEAU | PROGRAM MANAGER

mmartineau@...

LinkedIn

21 - 40 of 867