Hey all, this far I've been an observer and I'm looking forward to participating in meetings going forward. Just want to confirm the date for Tue the 17th, as I had 2nd and 4th Tuesdays in my

Hi Aaron, Thanks for the question. This is an extra "working" meeting specifically to focus on the whitepaper *content*. The regularly scheduled meeting couldn't go that deep on hot topics and seeking

Hi folks - we'll be reviewing hot topics related to the whitepaper's content and seeking owners for section reviews in a meeting this Tuesday Jan. 17 @ 1600 UTC. Here's the meeting event page to add

this is actually a really nice validation of the initial assumptions of CNCF, that an industry platform could emerge from collections of loosely coupled cloud native tools.

Hi TAG and happy new year! WG Platforms finished 2022 by building the whitepaper described in https://github.com/cncf/tag-app-delivery/issues/246 to define what a cloud-native platform is, why it's

Hi everyone! You may have heard the news: GitOpsCon is joining forces with CdCon and moving from KubeCon + CloudNativeCon to Open Source Summit starting in 2023! Check out this blog post which

Thanks Niklas, Niki, and everyone involved in this subgroup 🌎 -- Scott Rigby Developer Experience, Weaveworks

Hey everyone, for the first GitOps & Environmental Sustainability Subgroup 🌱 meeting Niki created an issue in the project's repository. We want to meet Tuesday 15th November at 6pm CET/12pm ET/9am

Hello everyone! Please see this PR which updates OpenGitOps governance to Move top level power to maintainers #123. While there are overlapping members, once that PR is merged, the OpenGitOps project

Who is planning to join the meeting today? If you have a agenda item, feel to add it for today. // AloisThis email may contain confidential information. If it appears this message was sent to you

For transparency, New Maintainers have been nominated for the OpenGitOps Working Group https://github.com/open-gitops/project/pull/107 Christian Hernandez (626) 502-8310 Developer Experience and

BTW, on GUIs being necessary: A GUI isn't strictly necessary, but this makes it Possible. It also makes other types of automation possible. It eliminates the requirement of manual editing of

Will watch video for sure. To be clear, you don't have to use git, any object store that's versioned will do. If git is in the way, use something that works and is versioned. Also, I think it was Dan

I tried to respond to this message yesterday, but the reply didn't go through. The similar twitter thread is here: https://twitter.com/joshugav/status/1529208719594110979 There are a number of other

The Backstage plugin is in its early stages. The review/approval flow needs to have at least diffs added. Some of that functionality can be seen in our earlier

Thank you for bringing this to the group. I legit wish I had this when I was working in the Duke Health system. Would've made our lives much easier. I can see extensive use of this being made in

Flux can write back to Git, but only for container image update automation. Flux image-reflector-controller scans container registries to find new versions, then Flux image-automation-controller

Thanks for sharing Brian. The most significant bit to consider IMO is that kpt enables syncing back to the git repo, whereas the likes of Flux and ArgoCD are one-way only (AFAIK) - the ArgoCD and Flux

Hi. It was suggested to me that this topic may be of interest to the GitOps WG. I'd be happy to come discuss it during a meeting, or on the mailing list. We created a WYSIWYG GUI experience layered

Hi everyone! This is a follow-up to "[gitops-wg] Co-Chair voting" on this list. Chris Short has been voted in as GitOps WG co-chair, along with Dan Garfield and myself. 🎉 See CHAIRS.md for the list