Cloud Native Computing Foundation Technical Oversight Committee, 13 Jul 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: CNCF TOC Meeting 2021-07-13

Description

CNCF TOC Meeting 2021-07-13

A

All right, sandbox review is on. We are now recording, go ahead.

B

But I have, I have got a drop, but I can reply to others in slack. If that were.

A

B

Me to if that helps.

A

uh I believe you've already put in your plus ones, for um if I'm correct in here, it's crestless, crater and or as yes.

B

And it wasn't cloud yeah, why isn't cloud thank.

A

You that's what I was missing.

C

Should we do those um you know, while, while we're still thinking of those, so any other thoughts about chrislet and krator seems like they're worth discussing together.

D

um Plus one on both, we need to get it going. Yeah good.

C

All right shall we do votes for.

C

C

C

Are we missing somebody.

A

I have seven so I'm not sure who I'm.

C

Missing shang: there we go there, we go great.

A

C

You and uh that's for.

C

A

A

D

D

Is this a ibm.

D

B

C

I can see some contributors.

E

From microsoft and the person who submitted the project uh is also microsoft, um it actually might be useful information to to add um to the list of questions to ask, because I always I always try to decipher it either from email address or github orig. Maybe we can make it more explicit going forward uh alina the.

D

Tyson lori seems to be in ibm.

E

C

Maybe it's uh against the boomerang one. I think we're talking about crater at the moment.

E

Yes, it's one one row um below taylor.

E

C

Okay, great, um I think we will only have quorum for the ones that justin has voted on, because that takes us to eight. So let's cover those and then we can. We can always talk about the other ones and do a vote in a poll in slack or something so shall we talk about auras next, which.

F

C

Line six, I.

C

C

Chris, do you know anything about the sort of oci background here there seems like there might be some I don't know. Is there any.

G

No, it's it's like, I think, a typical. You know, standards body versus open source projects. The oci folks are just very resistant to major changes, at least the core maintainers, so making anything big. You know they tend to avoid. Generally, they don't want things like reference implementations outside of run c itself living living there. So oras is basically an implementation of some of the ideas in the distribution, spec and artifacts work. um You know, essentially, so it's a way basically formal way of hosting artifacts in in a registry.

G

I think rs actually uses uh docker distribution. I think under the hood I recall.

C

And I see the why you want to contribute the project being for.

A

C

Governance reasons um yeah and the the fact that it has is currently existing under open containers. Is there any don't know legal tennis or you know, or anything, no.

G

It would be like container d implements. You know, oci specs right, there's no issue absolutely so.

C

They would move that artifacts directory no.

G

Oh potentially I they'd have a discussion but or as itself um it's.

C

Got its own project yeah.

G

C

G

Have its own github, repo and so on.

D

So they have a cli, they have a go library and a spec.

C

And this spec is currently under oci. Is it.

G

Yeah, I think that's oci artifacts and distribution spec. I think those will remain in oci.

C

C

But that's okay! I mean it's clearly cloud native. You know area.

G

Yep people want to stuff other things in container registries is the end of the story here, and this is one implementation.

D

Yeah plus one yeah.

C

All right, so, let's do those four s: apologies for my messed up, capitalization.

C

C

I think that's everyone.

C

And should we skip ahead to wasn't.

C

C

It's quite a good statement here that, as a technology wasn't cloud is compatible with and enhances the lives of the clown native developers.

E

E

C

uh Any comments, any ricardo, saying they're gonna present on the tag.

C

C

Any concerns about this one anyone wants to air. I guess one question I have is: are they talking about the whole wasm cloud organization, which has a bunch of different subprojects.

G

Yeah, I assume so a lot of it looks like utilities um examples some cli was in cloud shell.

G

B

G

Ask but I'm assuming it's it's everything.

H

So wasm cloud is the name of the company looks like it's. Some kind of llc they're gonna donate this whole organization to cncf.

G

Oh yeah, I mean they're gonna have to either donate the mark or choose a new name.

D

D

So, subject to um yeah.

C

So I'll put something like subject to.

G

C

G

I'll go I'll, go shoot him a note.

C

Oh that's interesting if they want to start looking at the incubation process right after I mean if they.

G

Seems aggressive, yeah.

C

I think they're probably going to be a little bit early for incubation straight away. Just from you know what I'm seeing here.

G

F

G

It's nice to have ambition. I guess.

D

Can we check how much how many people contribute to this or like who.

C

It looks like capital one and a company called cosmonic, which I think is a spin out from capital one. But.

G

Yeah, I think it's a lot of code that came out of capital, one with wazzy and all their kind of wasm experimentation and then folks, left and spun out a company.

D

And this liam randall seems to be like a a serial entrepreneur.

G

Yep, I think, he's at some cloud he's a cloud custodian or whatever stack that now and I think.

C

Yeah, I think he was involved with cloud custodian when it came out of the capital.

G

And before he was at some kubernetes, I think startup that he sold to capital one so he's been around for a while. Okay.

F

D

Last one for me.

F

C

C

So I think now that we've been through justin's votes, we can't actually vote on others, but we could still discuss uh any concerns that people have and then maybe we can hold a vote somehow through slack separately. I feel like we all have to use the same voting mechanism. Does that?

C

Does anybody think I'm crazy to think that.

E

You only have seven minutes left yeah. I wonder if it's better to have a separate meeting.

C

E

I'm going to.

C

Say there's this one, that's struck out to me as well stuck out to me as being a strange example of a project, and that was potato head, which I think is lovely. I think it's a really cool thing, but I mean it's never going to be like product. It's a test.

B

C

Thing right so it can, I don't see how it can ever get to incubation or graduation. It's on the cnc of github.

G

Yeah, it's, it was basically part of. uh Was it app delivery? uh I think the tag put together an example application showing different cncf projects showing how app delivery would work in a modern thing. So the question is, like you know, they've kind of been playing with this. You know and I think they want to spin it as an official sandbox thing versus kind of it floating on its.

G

Own, I mean we allow, you know, working groups and tags to do like white papers and kind of example, projects right. So it's kind of one of these artifacts that they produce. I.

C

Mean I completely think it's a great thing that it exists and see how it's going to get through the yeah. You know if we put it in sandbox, where is it going to go it can't it.

G

Can't I mean the criteria.

C

G

So I mean we could just say we leave it in the cncf oregon tree as an example work. You know, example, project from the app delivery uh group and that's that's fine.

D

Chris, but then you know we have kubernetes six like so can we have something uh like cnc of tag and then move it there? We.

G

Could we could I'd be open to that exploration? There's, not many projects that would fall under that particular.

D

Right but then, if we create github.

G

D

Will get ideas and say, okay? Can we experiment there request an arg request, a repo there.

C

It is actually interesting should we have kind of guidelines on how.

C

Like if you go to this repo, I mean it's very clear that it's a demo project. You know that it's it's pretty cool really, um but like.

C

Who owns it? I don't know, there's.

D

So in in the cumulative sting we end up, saying: okay, this report is owned by the sig, so in this case it would be the tag and then the members of the tag would get added. As you know, maintainers there.

C

Yeah, actually it does say in the about thing: it says: cncf, app, delivery seek demo yeah, so yeah, I think. Maybe we should encourage some kind of way of people understand when they come up across the project where it came came from like who, who sort of owns it, but.

C

um Any of the other projects that people want to talk about or highlight any concerns about.

G

I'm excited about a metal lb, looks cool.

E

C

In fact, I think didn't we last time uh get as far as another load balancing project, but we didn't get as far as metal, lb, porter I'll be right. You have.

G

A

ah Yeah, you have reapplied.

B

A

The new name um look at line number 20.

C

D

It looks like we need another session amy.

D

We have two minutes left.

A

We will definitely be like there will be a backlog that moves towards our next meeting um and, as I get things together, I will announce when the next project meeting is. We can probably do one the end of august, but I'm a little concerned about like a bunch of people on vacation in august.

F

Yeah, there's 22 on the that we need to talk about 22 on the sheet that we haven't already.

C

Covered right now, yeah.

C

Yeah well, we've got rid of got rid of we've just voted on about four of them, and maybe maybe I think, unless anyone particularly feels strongly that we should hold a vote on um potato head. I think maybe we should tell that one.

F

They don't fear.

G

Yeah, maybe maybe maybe we'll chat about like what solution we come up with for these example projects because I mean for the white, uh you know, for the you know, papers that people are producing. It just goes into the actual tag repo, so it's very clear who is the owner, but for the code projects obviously they're, not living.

G

um You know in those repos in particular, I mean that could be the solution, but that kind of sucks from a maintainer perspective. If they have to maintain this, I.

A

Like being able to have like them specifically noted, as you are part of like the tag, you are like a demo project in there, but you don't have to be in the repo directly yeah.

C

A

So that that is a thing that we can take under advisement yeah.

G

C

Think we're up to time. We got through quite a lot today, so yeah.

G

C

Well done folks, take care, see.

F