Cloud Native Computing Foundation TAG App Delivery / Bi-Weekly, 2 Aug 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: 2023-08-02 TAG Meeting

Description

TAG web site: https://tag-app-delivery.cncf.io/
TAG Slack channel: https://cloud-native.slack.com/archives/CL3SL0CP5
TAG git repo: https://github.com/cncf/tag-app-delivery
TAG meeting notes: https://docs.google.com/document/d/1OykvqvhSG4AxEdmDMXilrupsX2n1qCSJUWwTc3I7AOs/edit

A

A

Ers of the KCl project, I come from and group from China I come from one group in China I view you slides to introduce the queso project in the next meeting happy to meet everyone here. Thank you.

A

Hello, everyone, I'm piffy, one of the maintenance of the Casey object. I come from our group in China I, will use slides to introduce the queso project in the next meeting happy to meet everyone here. Thank you.

A

A

B

B

A

Project I come from and group in China I will use slides to introduce the KCl project in the next meeting happy to meet everyone here. Thank you.

A

C

B

D

C

Hi Eloise, how are you.

D

Good I just have to drop a bit earlier today, because I have a doctor's appointment that I have to get to, but yeah I would just depreciate if you start with devoting uh peace today. If that's okay with you.

C

C

You want to talk about it now.

D

uh Let's see where a couple of people join I mean after the uh later today, I will send out obviously information to the mailing lists uh as well put it on Twitter and so forth.

C

Is it like? Do you want like who votes always I've been wondering if.

D

You see work so more or less. The issue on the candidates are.

C

D

D

Yeah I think that's, maybe something we have to discuss in the Gs meeting.

B

D

I was considering I want to contribute um going forward. I have to just balance it with all my other open source commitments right now, so I'm in between going from culture to Tech, lead or supporting on it and the co-chair side. But this is something I'm currently.

C

Figuring out, maybe maybe we should have an advisor role or something like something like that.

C

E

C

C

Okay, or should we get started.

D

Yeah, uh just in the chat, uh please, everybody find um the agenda doc.

D

And also for the people only recording uh he will also, as it find our agenda doc on our GitHub or on our website. um Okay, let's have a look at the edge and what yeah yeah.

C

D

The links so uh introduction of newcomers is, and then we have no wrong one.

C

That's right, usually, we've been asking folks that are new to just uh maybe tell us who they are and what their interest is and and we're trying to solicit folks to tell short stories. So.

D

Somebody deleted my issue by the way.

B

C

We have to put it back in.

D

Yeah yeah, just uh maybe you can start with the newcomers and I'll put the voting in.

C

Yeah, so if anyone here is uh yeah, please introduce yourself, we just want to know what uh what you work on, and you know what we could. uh We should ask you to help us with see.

B

A couple new faces.

E

I'm not a new face, but I can hop in um because I have to leave and go attend. Another meeting but I wanted to check in and then hopefully, I can come back, um but I Karina and I'm interested in revisiting the API discussion before um I know. Alois. You mentioned like a working group or something and you know reaching back out to the AIP guys and then you know others but I thought that would be beneficial for the tag.

E

If there are Cycles um because I know, everybody's got a lot of work um and looking forward to kubecon and seeing you all there so.

B

C

Just shared they are working on that proposal um in that group, so you could take a look at it. They haven't told us about it yet, but if you want a heads up.

E

That's fantastic.

E

D

All right anybody else: okay, um hello,.

A

Hello, can you hear me yes,.

D

We can hear.

A

You uh I'm from one of the maintenance of the KCl project. I come from and groove in China I will introduce the KCl project in the next meeting uh happy to meet everyone here. Thank you.

C

Nice, thank you looking forward to that all.

B

C

D

Yeah, so uh there is an issue that has actually been open for a while, but uh now moving forward with the process. um So this is the co-chair voting. This is an issue if you want to either nominate yourself or nominate somebody else for a co-chair of the tech, because we have models which the next level voting uh put yourself in there.

D

A couple of people are already in there as well also keep in mind that if you nominate somebody else uh that we also need there, okay, so if you know when you nominate somebody, let them know, uh or at least give us a chance to uh reach out to those people, because otherwise we can't obviously take the nomination, because we would not know whether they're going to accept it. um I kept the nomination open for a bit more than two weeks, um also taking vacation season into account.

D

So that's the Friday in two weeks from now should be fine. I will be sharing it uh also on our other channel mailing list, uh slack and so forth, and a couple of candidates are already in there. We are free to put yourself in there as well, if you're, really interested in that role. I also, as part of the issue shared uh the responsibilities of the co-chairs.

D

So this is a obviously Beyond, some some technical expertise more a or it's an organizational role like taking care of meeting agendas, uh uh thriving discussions, scheduling discussions, driving proposals, uh also work helping with working groups partnering with the tech, leads on road maps and other topics, and also going forward being more involved in the sandbox projects uh as well. So I just found actually one issue in the this submission.

D

uh I think the issue that I'm just fixing as we speak.

D

um The timing- we just move this one actually a bit further uh yeah, if you want to be there, um just be aware that obviously everybody is welcome, uh only share your name uh affiliation um short TV. Why you want to have that role and please also indicate how much time you're willing to to spend so tax really heavily depend on uh uh how much time you can actually put in into the tag work because tags require a lot of work.

D

Josh knows I know that it is it's really how much work you can put in there. uh If you think you want to still contribute, but can't find the time everybody's welcome, but yeah I think Josh. We put it in like in yours as well. I think, like one day a week is what you should consider.

D

The effort to be not every week is the same, obviously, but uh depending on what we're working on this is the time we should have available, uh because there will only be- or there will be, three uh co-chairs that have to share their workloads. That's why we want to find a good balance between the three people to distribute work.

D

Yeah, that's it I'll share it also with, uh as mentioned on our other channels and then wait two weeks and then submit it to uh that. You see.

D

That's it for the voting so now that we have this one in let's move to the fun Parts Josh.

C

Yes, okay, so this next one is just kind of short I just wanted to mention it like. We still want to get a pre-day project meeting for kubecon Chicago and we want to get a booth, um I'm gonna write to the uh to.

E

The planners today.

C

um Let me write that down actually Josh to write to Cody Lusk and see if that might be the best way to do it because I haven't heard anything. Did you hear anything always.

D

No, usually we get, and even we get the meet the notification of the mailing list, but also they're mailing. This sometimes is weird right now, because you have to approve all of those messages, so they might have gotten lost as well.

C

D

Could turn off.

C

Those messages, by the way, the ones that are coming to the leads Channel. Yes, that's a preference somewhere in the zoom. It has been getting annoying okay, but we haven't otherwise heard about it. Okay,.

D

Well, we're here, let me.

C

Know I'll write to that guy.

D

I think it's also still a bit early I think it's usually two months-ish in advance of kubecon that they're working on this.

D

But I think it's good. I can get a bit more details here.

C

um Next item: uh Ouija artifacts, we have two people that are dominated. The group has pretty much unanimously said. They're good um I think it's on the tag leads to approve, so uh take a look at those things. If you have any issues, tell us there's a PR to merge them in.

D

Yeah I think we also have to talk to the QC, so we can't just create the well. We have the working group, uh which is just yeah. uh Let's send it also to the TUC.

C

On the mailing list, at least we've shared, it is that.

D

Okay, did we share it with the vote in the hair in the subject, because otherwise you won't get votes from the TLC.

C

um No do we need votes. That was what wasn't clear. We didn't get votes for the last Ouija chairs. We added because we determined we didn't need them.

D

Yeah, let me double check with Amy, but it wasn't needed for working group chairs I mean for TUC chairs. We need it for tech leads. We need them. Yeah I can talk to Amy, I'm I. Think as procedures are changing I'm, not always 100 certain myself. To be honest,.

C

Yeah exactly okay. So let's try to finish that out, so we could just finalize that um those folks are acting as the leads right now.

C

um The biggest thing for today, really that I wanted to share is that the the technical oversight committee wants to delegate more of the at least starting with the sandbox stuff to the tags.

C

um One of the first things that they're pursuing is the annual reviews, because there's a huge backlog right now, um and so there are four that are tags for Tag app delivery. um They we now have some official guidance I've posted in the chat. Sorry, not the chat, the uh the notes, but I'll post it in the chat right now.

C

um What I would propose is if there are folks here that are passionate or willing to take on a couple hours and review um choose one of those four create an issue in our repo in our issue tracker. So we can uh see what's going on um and then follow those instructions in this. In that guidance that I just posted um yeah I mean I, don't it's?

C

We really could use support there, uh I, don't know what else to say.

D

So that people know who to talk to I'm happy to take like one else, I haven't worked with the new Sandbox uh review process. I have to look into it myself. To be honest,.

C

Yeah, so this isn't the ACT. This isn't sandbox submissions, which we should also keep an eye on um and KCl will be coming to present to us next week and there are a couple other ones that have come in which we need to consider uh which are Silver. Surfer came in like a couple days ago and um Kraken krkn, which is a test framework.

C

Those are other couple but.

D

This is separate.

C

This is annual reviews.

D

Okay, that's the animal reviews. Okay, sorry I got that wrong. Okay,.

F

Is it the same four that are on there for, like the 2022 reviews,.

C

Yep, okay, Landing ones, oh wrath and Porter. Really we should ask the artifacts folks come to think of it because they're both pretty heavy on Packaging.

C

C

Yeah I guess we can discuss. Does anybody here want to take any of those on I'm being really forward as much as I ever am I'm.

F

Interested in what's involved, I, don't know, I've never done one of those. So that's tough to say.

B

D

We're doing this the first time that uh let me pick one go over it together and then we uh fan out for the other ones. I think we might have some questions. Let's just take pictures the first one on the list and maybe calling Josh and I we collaborate on like getting the first one done. If it's really straightforward, I think we can move on to the other ones.

D

They're not like super critical for the projects anyways, but I think we can all learn as we were collaborating on this one and then it should be easier. Ideally, we can also assign two people going forward. It might also make it more manageable.

F

From our team too, to try to expand the footprint a little bit.

C

Yeah, that would be awesome. If you have someone call it in mind, they could just open an issue and say I'm working on the oras tag. Us in and you know, we'll all get on it together.

F

Sounds good I'll, look at the uh I'll look at the four.

C

Yeah choose one that that fits well cdk. That's my well! It might be pretty interesting.

F

See the the link you posted there and chat is the it's that big guideline. That's.

C

The instructions- okay.

F

That's the instructions, and then there is a markdown there's a dock. That I found is that this is still relevant to this link.

C

Up to some degree, yeah, that's the high level, but then the one that I posted is where Emily and some of the other folks have been putting together the exact process. Okay, they kind of want us to try to follow that I guess and give feedback I.

F

See and there's a Google doc in there too.

C

Okay, yeah. Ultimately, that issue is copied from other threads.

D

I have worked with the project already. I was like, as part of uh um help me out, um Potato Head background in the project as well.

C

Okay, um next item on the list is Marcelo grabois, but he's not here so we'll skip that one um I'll move it to the next week. If he wants to present and that's it there's upcoming meetings I put down, there is a uh a deep dive on the platform's maturity model, which is scheduled for next week. I think next Wednesday and the platforms meeting is on Tuesday platforms, project meeting uh and then Friday next Friday I think is the artifact next artifact meeting.

F

And then we have a meeting uh between um platforms, working group and cartographers to kind of compare and share notes on the maturity models to synchronize there. Trying to remember in that meeting is.

B

C

Couple of weeks from now I think I think it's next week also yeah on Wednesday or Thursday.

C

B

F

That's Thursday yep.

C

So if that's all, then maybe we don't have anything else to discuss right now.

D

uh Any help you would need charge for uh kubecon.

C

um Yeah I mean in terms of planning the assuming we can get a pre-day meeting. Then we need to plan out what that will be if we want to do like what we did last time was sometime for the working groups and the tags and then sometime for some projects to come and talk. That was pretty popular um same thing with the Boost. If we want to get, you know some time for projects to come and talk about themselves,.

D

Regarding three-day meetings, assume we don't get one on the venue. Do you know whether Red Hat has some space in Chicago that we could probably use.

C

um That's interesting for a if it's a small scale thing then maybe yeah I might be able to get us a space. We have a sales office here. Red hat is actually running in a pre-day event, also openshift Commons. They call.

D

C

There's a lot of there's a lot of pre-day things which.

D

Is that's why I think we might have more displays issued than like getting a set of people together? If you can keep it to a reasonable number? uh I know that we don't have one that I could offer.

D

Yeah ABC, who wants to join for a pre-day event, maybe create an issue of people who want to join and even we might find a space to run it anyways.

C

Okay, yeah I mean there's been it's not we don't. We haven't, run a Colo because this is like non-profit like this is not you know, vendors or anything, so they did have like with all the previous coupons. There have been numerous project meetings, so I'm, hoping that you know they'll facilitate it this time.

C

um But let me find the issue.

C

I think we have an open issue for kubecon.

D

There is one of our Cube complaining.

C

Yeah here number 408. Let me tag it into the notes too.

B

C

Yeah, so that's the thread: um I did start. I did have a slack thread at the same time, and a few more people chimed in um yeah I'm just going based on you know in Detroit and in Amsterdam it was a pretty positive experience.

C

um You know we got about 20 30 maintainer types in the in the room um and discovered some synergies. You know ironed out some of our strategies like the way we approach prototypes. I would say we kind of figured out their um and we're pursuing that now gradually and slowly in the website.

D

B

D

Think we should at least try to get all uh working group league chairs and the chairs and the TC together.

C

D

Impossible I mean there's a lot going on. It's always a challenge with kubecon.

C

So yeah we should definitely get a room um if we can hopefully see in Seattle, I mean McCormick. Place is a huge place. I live in Chicago, so I have an advantage. It's a it's a really big place. So hopefully they'll get us a room like they did in Amsterdam in Detroit and if not then see what we can figure out.

D

C

um Maybe we'll open up like a cfp kind of thing like we did last time just to solicit. You know 10 or 15 lightning talks to distribute.

D

C

D

We could just have some dedicated time with the working group chairs, um because it's one of the few chances we might see most people in real life and have some interaction.

C

Yeah exactly there is, there are a few conflicting Colo events which I honestly I'm debating like should I submit for these cfps there's backstage con, there's an app developer con and there's a git Ops or whatever kind of con argocon I guess, um which is a multi-tenancy con. That saeem has been talking about so yeah.

C

I, don't know what.

B

C

I'm sharing that I personally am conflicted like do I submit to those, but then you know if I won't be able openshift.

E

C

The same day, I'm sure I could support there. It's it's hard.

D

Yeah, let's put it out there here in the mailing list and see what we can get together, I think it shouldn't all be. Maybe we can distribute also the load of running the events. Obviously,.

C

Yeah, that would be. That would be amazing, so yeah.

E

C

On that issue, um we'll keep letting people know I guess if we do secure a room, then we'll post it on the slack and maybe more people will chime in there.

D

Okay, correct yeah, I think then that's all on the agenda.

A

B

C

So I guess we'll see you on a couple weeks and see you online.

D

The whole thing.

C

Oh yeah, thank you always see you all soon.

B

C