toggle quoted messageShow quoted text
Yes, although I think that operators themselves will probably also be discussed in most of the SIG’s, as they’re a general-purpose automation mechanism, and may be applied anywhere.
So operators for Vitess, Cassandra, etcd will likely be discussed under SIG-Storage, etc
Here’s a list of some example operators, for those who may not be familiar:
The Operator Framework, API etc will probably be discussed in App Dev, Ops & Testing.
Diane, were you referring to the Operator Framework, or the operators themselves?
Diane Mueller-Klingspor <dmueller@...
Monday, February 4, 2019 at 10:13
Quinton Hoole <quinton.hoole@...
Brian Grant <briangrant@...
Erin Boyd <eboyd@...
>, Sarah Allen <sarahallen@...
>, Bryan Cantrill <bryan@...
>, Chris Aniszczyk <caniszczyk@...
Matt Farina <matt.farina@...
>, Alex Chircop <alex.chircop@...
>, Alexis Richardson <alexis@...
Re: [cncf-toc] CNCF SIGs Proposal
Quinton et al,
Would it be acceptable to add"Operators" to list of areas covered in the App Dev, Ops & Testing - "Area" column? As we get asked a lot which Kubernetes SIG this topic falls into. I know it's not a CNCF project, but it would be good to point people to the SIG
where the conversations are happening.
Thanks for all the work on this. It's much improved. I think the proposed governance model should address concerns with earlier proposals.
What is meant by "high level roadmap of projects within this space"? Usually I associate "roadmap" with a timeline. Landscape? Trailmap? How they fit into a reference architecture?
Quinton> I didn’t write those words, but my own thinking is that it is intended to encompass all of the above, including the timeline angle. i.e. what this space looks like today (including projects, ref arch, landscape, common
trail maps etc) and also how these are changing over time (trends), and how we would like to influence all of this (filling gaps, better integrations, timelines for this), etc.
Nit: I'd put Buildpacks under App Dev, Ops & Testing.
Quinton> Yes, some of the project allocations were a bit strained, with non-perfect fits. I agree regarding Buildpacks and have moved it.
Greetings to the new TOC
Late last year Alexis kicked off a public discussion regarding forming CNCF SIG’s (initially referred to as Categories). Since then a few of us have collaborated on soliciting further input, addressing all the comments, and producing a finalish proposal
for consideration by the TOC.
Please give it a read and we can decide how to proceed at the next meeting this Tue, Feb 5
can you put this link into the main doc as a comment?
Following our initial discussion in Seattle, Quinton and I had a discussion on this. I captured the notes and applied them to the operating model. I decided to make a copy of the doc and apply the changes to operating
model section only - the current doc is hard to process due to the number of comments.
Here is the amended operating model content: https://docs.google.com/document/d/1ySri5jVrPaJjTJ_tZnDzcc4Xmcm4uKoUrHT6lVO6Pcw/edit#heading=h.6cl6hmsbz9fv
From: Alexis Richardson <alexis@...>
Sent: 09 January 2019 19:36
To: Erin Boyd; Sarah Allen
Cc: Bryan Cantrill; Chris Aniszczyk; Quinton Hoole; Alex Chircop; Matt Farina
Subject: CNCF TOC SIGs Doc
how's this doc looking? I daren't look. can we show the toc an update next week?
On Mon, Dec 10, 2018 at 5:35 AM Alexis Richardson <alexis@...
On Fri, 7 Dec 2018, 13:35 Erin Boyd, <eboyd@...
Please feel free to catch me on Slack.
On Wed, Dec 5, 2018 at 11:18 PM Alexis Richardson <alexis@...
Thank you Erin. Let's try and sync 1-1 during the week
On Thu, 6 Dec 2018, 00:42 Erin Boyd, <eboyd@...
I think I am speaking on a panel at this time.
I can collaborate in the document.
Sorry about that.
On Tue, Dec 4, 2018 at 11:46 AM Alexis Richardson <alexis@...
CNCF TOC meeting re SIGs Doc
meeting to discuss the Categories and SIGs doc
identify and divide up work tasks to clean up draft doc.
eg: we agree a new section plan and each take one section? or something
Mon Dec 10, 2018 3:30pm – 4:10pm Mountain Time - Denver
lobby of the Sheraton Grand Seattle (map)
Or dial: +1 929-299-3513 PIN: 706587657#
Going (eboyd@...)? Yes
- No more
You are receiving this email at the account
eboyd@... because you are subscribed for invitations on calendar
To stop receiving these emails, please log in to
https://www.google.com/calendar/ and change your notification settings for this calendar.
Forwarding this invitation could allow any recipient to modify your RSVP response.
Director, Community Development
Red Hat OpenShift