|
Re: [VOTE] - Tekton graduation in the CDF
Oleg Nenashev
Thanks to all who voted in this thread or in the pull request! Based on the positive feedback, I merged the proposal and happy to announce that Tekton is now a graduated project in the CDF. Kudos to Andrea Frittoli and all the contributors for making it happe
On Mon, Oct 17, 2022 at 10:34 AM Robert Reeves <r2@...> wrote:
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
Re: [VOTE] - Tekton graduation in the CDF
Robert Reeves
Wonderful news. Thank you, Oleg.
I’ll be at DOES in Vegas this week. Would love see Tekton community members, users and contributors, and celebrate this achievement with you.
Robert
On Oct 17, 2022, at 3:16 AM, Oleg Nenashev via lists.cd.foundation <o.v.nenashev=gmail.com@...> wrote:
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
Re: [VOTE] - Tekton graduation in the CDF
Oleg Nenashev
Hi all, FYI we have the required binding votes. I'm also happy to cast my +1 binding vote. Unless there is blocking negative feedback until the deadline this evening (23:59 UTC), the vote will be concluded tonight. Best regards, Oleg
On Mon, Oct 17, 2022 at 9:30 AM Jithin Emmanuel <jithin1987@...> wrote:
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
Re: [VOTE] - Tekton graduation in the CDF
Jithin Emanuel
+1 -- Jithin
On Tue, Oct 11, 2022 at 11:16 AM Oleg Nenashev <o.v.nenashev@...> wrote:
-- Thanks Jithin Emmanuel
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
Re: [VOTE] - Tekton graduation in the CDF
Brad McCoy
+1 non-binding, Go Tekton!
On Fri, Oct 14, 2022 at 1:27 AM Lori Lorusso (JFrog) via lists.cd.foundation <loril=jfrog.com@...> wrote: +1
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
Re: [VOTE] - Tekton graduation in the CDF
Lori Lorusso (JFrog) <loril@...>
+1
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
Re: [VOTE] - Tekton graduation in the CDF
Tracy Miranda
+1
On Tue, Oct 11, 2022 at 6:45 PM <tequilarista@...> wrote: +1 non-binding
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
Re: [VOTE] - Tekton graduation in the CDF
tequilarista@...
+1 non-binding
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
Re: [VOTE] - Tekton graduation in the CDF
+1
On Tue, Oct 11, 2022, 12:16 PM Oleg Nenashev <o.v.nenashev@...> wrote:
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
Re: [VOTE] - Tekton graduation in the CDF
David Lai
+1
From: cdf-toc@... <cdf-toc@...>
On Behalf Of Tracy Ragan via lists.cd.foundation
+1
On Tue, Oct 11, 2022 at 12:16 PM Oleg Nenashev <o.v.nenashev@...> wrote:
-- Kind Regards,
Tracy Ragan CEO and Co-Founder / DeployHub / tel: + 1.505.424.6440/ mob: +1.505.780.0558 Continuous Delivery Foundation Board Member We make microservices easy.
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
Re: [VOTE] - Tekton graduation in the CDF
+1
On Tue, Oct 11, 2022 at 12:16 PM Oleg Nenashev <o.v.nenashev@...> wrote:
--
Kind Regards, Tracy Ragan CEO and Co-Founder / DeployHub / tel: + 1.505.424.6440/ mob: +1.505.780.0558 Continuous Delivery Foundation Board Member We make microservices easy. 
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
[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
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
Continuous Delivery Summit
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
From: cdf-toc@... <cdf-toc@...>
On Behalf Of TracyRagan via lists.cd.foundation
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 Continuous Delivery Foundation Board Member We make microservices easy.
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
Invitation: CDF Technical Oversight Committee Meeting @ Tue 2022-08-02 18:00 - 19:00 (CEST) (cdf-toc@lists.cd.foundation)
Oleg Nenashev
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
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 Continuous Delivery Foundation Board Member We make microservices easy.
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
Re: VOTE: Accepting project Pyrsia as a CDF incubating project
+1 non-binding Pyrsia Kind regards, Kara de la Marck Continuous Delivery Foundation
On Wed, Jul 20, 2022 at 11:32 AM Oleg Nenashev <o.v.nenashev@...> wrote:
|
|||||||||||||||||||
|
|
|||||||||||||||||||
|
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
+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
|
|||||||||||||||||||
|
|
