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.

 

Join cdf-toc@lists.cd.foundation to automatically receive all group messages.