Kubernetes SIG Contributor Experience, 15 Apr 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220415

Description

[SIG ContribEx] Weekly Marketing Meeting for 20220415

A

All right, hello and welcome everyone to the uh april 15th 2022 edition of the contributor coms upstream marketing sub project meeting. We are a part of the kubernetes project which is present cncf, which is part of the linux foundation.

A

So we have a code of conduct that we follow, which essentially says be respectful to your fellow participants and speakers and generally be excellent to each other.

A

So today we have our regular action items table as well as our usual notes. um I want to start off by going through the notes and then we'll move to open action items.

A

uh If you haven't added yourself, I think I've added everyone. Oh no, there's more people.

A

um If you haven't added yourself to the notes, thank you for putting in the uh notes document.

A

I'll actually end folks, because it looks like we have a couple of new folks today, exciting.

A

um So usually, at the beginning, we'll have a little bit of time for if anyone is new and would like to introduce themselves, we welcome you to do that now.

A

um If you would tell us a little bit about yourself and why you're here.

B

Yeah, like um I'm harsh, I'm a undergraduate in india in third year so like I'm contributing to elephants also, I have created a category scenario recently and I have added a pr today so like can you please check it once like if any other suggestions, which I can add in that? So that's what I'm hearing like this is that the scenario.

B

Scenario um with my account like with my profile and then today I have updated the scenario which is already present.

A

Could you give us any links where you would like us to review that yeah sure? Once again sure um I know we had someone in here was that debba who worked on katakada stuff anyone else in here work on katakura, stuff.

B

Yeah like he, he was kidding me please. If any suggestions are there, let me know like I have shared the I'll smell you this this one.

A

A

I need to sign up to be able to see it which I'm not going to do right this second, but um how would you like to receive review on it uh if we review it?

A

Is there a tool in.

B

This internship, like any changes which can help new contributors like to make it better to make them understand right.

A

But how would you like us to give you that feedback like.

C

Is there a tool.

A

Inside of this link, where we can make comments on the scenario or do we need to ping you directly on slack or is there an email address, you can.

B

Thank me directly on the slack okay like yeah, because the scenarios just work like directly. So there is no option to make comments so yeah.

C

B

A

And what is your slack username? Is it the same harshita.

B

How should that yeah, okay.

A

Okay, thank you for that. I guess that's a new item. I will put that under new items I feel like. We should move our items in the notes. Maybe um okay and I thought I saw another new name. Anyone else want to introduce themselves.

A

I think the other new name dropped off. Maybe they were intimidated by being asked to introduce themselves. um It's also totally optional, don't have to uh uh anyway.

A

So this new katakura review request does anyone feel particularly inclined to want to do that or want to put their name on that or just kind of do it? Ad hoc.

A

A

Okay, so I will put it in our action items table and not assign anyone. Just if you have time to do this, it would be much appreciated if we don't get it done this week, then we'll come back to it next week.

A

um Let me insert a new row into our action items and go ahead and put that in there.

A

A

Thank you very much rashida and welcome.

A

B

Okay, I would like to thank you, like humanity's team, to give me such a good opportunity to explore myself as a student. Like I'm meeting you all developers, it's a really good thing for me. It's.

A

A wonderful thing to hear I'm so excited about our.

B

Intern programs.

A

And helping folks out we've got several other students in this group. I think so.

A

So, let's move on to our next item, which I suppose would be updates and big wins. Are there any particular updates and big wins that we want to shout out?

A

I guess I have one so I can start which is uh well an update. First chris has some personal stuff going on, so he may be out for a little bit at least for this week. I don't know if he'll be back next week, but so he was doing uh comms and marketing leadership for the contributor summit. That's happening in person at cubecon eu in valencia, so I'm taking over that for him. For the time being uh so this week I sent out both a tweet and an email.

A

If I remember correctly, to kdev well, the email to kdev would have gone out this morning. I hope it actually did. It should have gone out 14 minutes ago, because I scheduled it. um So I am excited that we got a couple of things out on the contributor summit.

A

That's my update and big win.

A

One update and one thing.

A

And by the way that was my first time sending an email to kdev.

A

So, that's why it's a big win.

A

The contributor summit tweet any other updates and big ones before we moved into um we'll, do new items first and then do open ai's. I think.

A

D

So paris created a contributor ladder, mentoring group. She wanted to create one and uh she finally decided on two teams. I am part of the team and atawa is also the part of the team, along with carlos and aishwarya, and the next meeting she has kept on the coming wednesday.

D

A

Awesome so prince moir and atarva you're. Both part of this effort is that right.

A

Yes, was there anyone else just.

D

D

A

In this group, we don't care about their achievements.

A

uh I don't know how just about their names, though, so I'm not gonna notice, but congratulations.

D

For taking on this new role, you can just.

A

What were you saying, sorry.

E

I'm not nothing I I just said it is more like the best thing contributor experience thing.

A

That's okay, we're excited about.

E

The achievements.

F

Of our members.

A

And it's a contrib x thing in general, because uh the mentoring thing that paris is doing is part of the larger sig contrabex. So it's still relevant to us.

A

uh You said the paris created two mentoring groups. Could you tell me a little bit more about what she's doing there? I know she's been really excited.

D

A

This mentoring, stuff going.

D

uh Oh yes, but basically the okay one, no.

E

D

uh So basically, the contributor ladder thing is uh like not bringing new contributors into kubernetes, but the existing contributors uh she wants to like uh gel them up and uh let them know about the whole environment in the process and uh we basically act as peer mentors and we'll we can pay peer program or just uh if there is any questions we can handle it uh like with each other and uh basically the whole thing is a group effort um along, like everyone learns everything since no one knows the system completely.

D

So it's kind of a peer learning thing and uh it's a like. I don't know about the details, so much so paris would be taking through it uh in the next wednesday meet. So she wanted. I guess two people, but since more people uh came up for the thing, so she created two groups and the next details would be in the next meet. I guess, uh if you want, I can just drop some links to.

D

What's there sure.

A

D

Great in the in-depth mail.

A

D

A

A kw email on it, um you said there was another group: are they both working on this contributor ladder project or is there another one.

D

Basically, since there are four people so since there are four people in the group like me, carlos and aishwarya, I guess there will be two groups of 2h okay.

A

Do you know what the other group is doing.

D

But I know we haven't started yet, but maybe the first meeting will be handed over some rules.

E

Yeah the wednesday upcoming wednesday, there would be a meeting. um Paris would uh tell us what exactly we are going to do in much more detail.

A

Awesome, I'm excited for you all. I hope that you'll enjoy that experience. Paris is, of course, awesome to work with and an excellent mentor. I've heard about this contributor ladder idea before there was a talk at kubecon la where josh burkus and someone else. I don't remember who the other person was, um did a talk about helping contributors become maintainers, and this contributor ladder concept was a topic in that talk. Maybe I should see if I can find that recording for you. Maybe a good resource.

D

Yes, that's exactly what the thing is like uh the rise of the since most of the new contributors they just come into the environment remain for some time and since they find it hard to sustain here, they basically live the project so yeah. We help each other to grow up in the project. Yeah.

A

D

At this moment we have a lot of new contributors, but there are a few few maintainers only and we need new maintenance for the projects and.

F

D

As a matter of fact, uh hashida is here who is doing this katakura thing and if she remains in the project, she can maintain the project also.

C

B

Sure I'll love it if it is possible like if you guys support me, definitely yeah.

A

Open source contribution is a tricky thing, especially at the scale of kubernetes. We've gotta develop processes to make it easier for people to move forward. So I'm excited about this effort thanks so much for sharing it with us.

D

I've dropped the link in the chat and check the issue off perfect.

A

Thank you, member reviewer to her sub project lead, I'm not sure what that was with regard to bob, but.

G

That's just our standard letter. Oh.

A

G

Moving from member to reviewer to approver to some project lead and then eventually, uh like potentially into sick leadership,.

A

A

So I'm linking this issue in here and I'll also make a note of this.

G

For anyone, that's interested, it's actually outlined in the cake community, repo and the communitymembership.mdoc.

A

In the contrib x, repo did you say or.

G

A

A

In wichita again.

G

uh Community membership community.

A

Membership talk good to know.

A

That might be useful for these folks who are learning about this concept.

A

Okay, uh any other updates or big wins before we move into new items and then we'll go over our open action items updates big wins.

A

Anybody got a long weekend aside from hina.

F

All right, well, I likes me sad. You all can come participate in my long weekend, though, with me.

A

We will in our hearts there you go um so we'll move on to new items. I know ray you've got a couple of new. Yes,.

H

For us, some requests two tweets uh the april community meeting is next thursday. I'm the host of it's yeah. Also, the release team, the 125 release team shadow application will be open, uh hoping today we're still trying to target um our confirmed dates with for the 125 release.

H

Since 124 releases is delayed, um I'm actually tempted to open the application process today, anyway, just just and just put the dates uh right now I have the data uh it's approximate and subject to change uh currently, so I really really want to get this out today, um so be great if you could tweet that, because the application is only open for two weeks or about a little bit over two weeks. If I said that today,.

A

H

I'll create those issues with those um if the application is out today, I'll also create the issue.

A

Do you have the um the contributor tweets repo handy? Do I need to find that, for you um tweets.

H

Issues, I've got it.

A

um There you go so if you create those issues yourself, you can go ahead and put your tweet draft in there. I usually check it in twitter first because it will do the check on the length after you submitted it. So I usually check it in twitter just to make sure I won't have to fix that part.

A

So, are you planning to go ahead and create a tweet draft with the issue or okay or just.

H

Need help um I will today for the shout out application: okay,.

A

I'll be on the lookout for that.

H

A

It up so that I get notifications on my phone. So, okay, let's see it. I.

H

Might ping on slack too because I'll be that.

A

Might be a good idea.

H

I'll be away from the keyboard for a few hours in the middle of the day, so I want to get that out.

A

Yes, because we want to make sure that we get that out in a timely fashion, sounds good and then on the community meeting front um avinesh, if I'm not mistaken, has been our go-to yeah our community meeting interface role person. uh Are you doing anything with this community meeting.

I

Well, actually, I was about to mess in dora about the same if she needs any help so yeah I've got a task to do tweets, cool.

A

um So I should add a note about that and it sounds like you'll be working with ray this time on making sure the blog gets done and everything, so it should be a pretty smooth process for you for you, both, hopefully um I'll finish, to message more about community meetings.

A

Side question that I don't want to go into too much detail on, but whatever happened to that blog post from the last. Did it ever end up happening.

H

There should be two nigel's. I saw.

A

The draft for nigel.

H

And I put it in the in the contrabex slack channel I made I made one additional comment when I I think I did that put it in the slack channel last week. uh I think.

A

You did, I remember asking this question before yeah.

H

And don't didn't see one from from uh the last meeting, but.

A

Okay, was there another one between nigel and now I don't know, yeah.

H

Josh in one.

I

I think laura I asked laura if, if we are going to have a blog for the last last time meet, but she tell she told that there are some changes going to happen in the community thing, so we won't be having a vlog for last time.

E

A

No blog for josh's, but the nigel blog still exists out there and probably is not out yet.

H

Yeah, I'm gonna find it I'll put in the the agenda.

A

We reviewed it and everything, but.

H

I think maybe just a formality is just creating the pull requests.

A

Yeah, I think that's what's holding this up, which is a pretty common issue. Definitely that I've experienced and my work contributing with kubernetes is the the github process can be a blocker a lot of the time, um which is why we usually try to shepherd along these things and let them know how to do it, but there's only so much you can do, and sometimes these things still get blocked. So it's good for us to know that it might need some help. If we see it, we might want to poke on it.

A

The squeaky pr gets the approve.

A

So true, if I don't hear about it 10 times, it probably won't happen.

G

It doesn't help that github notifications are a tire fire.

A

Yeah really like what it's taken me years to get to a point where I'm as good as I am now, and that's not saying much. It's not a high bar.

A

There are some improvements to be made um all right, any other new items that we want to add in here. Before we go into open action items we can of course add them as we go through, but there's nothing else. Pressing bob isn't here to give us a ton, more work.

A

We'll move into open action items uh and we'll start with you hina. I know you've been dying to give us your update.

F

uh Yeah, I just feel bad because I things still look like sweet squiggles unless I hold the computer directly to my face so still paused and my apologies, my eyesight's fluctuating.

H

F

Hopefully I can see you soon for the greater.

A

Good no worries take care of yourself. First thanks. This is volunteer work, so gotta do it when you can and what is the status of that. I know apprentice wire got added to the org right. So that's a big win that we should have mentioned.

A

Congratulations right! Didn't that go through. I think it did. I think I saw that merged.

A

Pretty sure it did, I'm gonna add it as a big win.

G

Oh, actually, um I have a couple upcoming things: new items to you sure that we should probably um so the with the delays of 124 and the 125 cycle planning. um I think it was right now enhancements freeze is for 125 is only going to be a couple weeks after kubecon.

G

A

The start of 125 is going to be a couple weeks after kubecon or.

G

uh Let's see uh the enhancements freeze.

A

Yeah, that does make sense all right.

G

Let me open up this pr real, quick.

A

And also another update, big win, I guess is that we did do a tweet on uh the release, 1.24 release being delayed.

C

Happy that we got that out there.

G

So enhancements freeze is going to be june, 3rd, okay um and so yeah. That's two weeks after kubecon eu, um it's gonna.

F

G

Yeah, so most people will probably want to try and get like, especially with this extra set of downtime between since, like uh code freeze is still in effect, their thaw has not happened yet um to start working on their enhancements for 125.

A

There's not gonna be a lot of time to get those in.

G

And that can be, um you know, tweet um honestly, uh talking to you uh cc um to you about some getting more comms going, for that would probably be be good. um She's. The 125 uh release lead.

A

Okay, talk with cece 1.25. Let me see oh.

H

Just chatting about this as well yeah.

A

You're the emeritus lead.

H

This time right, yeah and uh we're gonna ask for a a minute. I'm joined the contributor summit for folks who are there over there. I'm not gonna be there, but uh if we just announce and somewhere enough but yeah something someone, someone will reach out. Yeah.

G

So what got it on? My radar was james, reaching out to me and she's like hey. How do I get a minute during the contribution? I was just talking ping james at the start,.

H

Of the meeting yeah.

G

About this so yeah the the other um potential work item that might be good for people, since it's a new group and they're trying to get more community members would be to do a profile on the batch working group. I might have brought this up before, but I don't remember. Oh.

A

Exciting, I think furnace wire, you were working on a new sig spotlight. Have you already chosen your sig reached out to them.

A

Sorry, we'll come back to that: okay.

H

A

But create a new spotlight on the batch working group.

G

Yep, um because one of the big things that has been a pain point has been um getting direct engagement from, like I, I've been in the batch research world for a while and and and trying to get feedback from act like end users has been a pain point, um so any sort of uh marketing support. We can get that group to potentially pull in extra extra people and and people to provide more info on. That would be very useful.

A

We need greater public awareness and is there some way for end users to provide some feedback right now, like a survey that we could add into this spotlight.

G

Not not a survey, um it's mostly like the there's a couple like open proposals out um like a design for a um in fact they just had their like dot o. Oh really, uh a one really really sounds.

A

Like q spelled, is it spelled with a k.

G

K? Yes, of course,.

A

E

G

But yeah there it be any sort of promotion we can give to them to try and get more they'll they'll also have a um there's going to be a colo at kubecon eu.

G

That's focused on on this um so like. I know there isn't a whole lot of time before kubecon but like if we could get something out like a week or two before uh with a highlight of the group to potentially get more people engaged there. um That would be super awesome.

I

A

The batch focused cola, okay,.

A

Cool so release news enhancement. Freeze, it's gonna happen on june 3rd talk with cece the release lead rey is also emeritus. Lead they'll make an announcement during the contributor summit, but we'll also need some tweets awareness there. One thing I wanted to ask there is: do we need to do like a slack bot message? Do we need to ping sigs about this.

G

um It would, it would probably be good to. It should be mentioned the community meeting and probably like when I would say when the schedule is merged, though they schedule the ray. Do you know when they're targeting to have it merged.

H

G

H

Soon as possible, but okay, I know there's some discussion about the dates still going on and who knows um hopefully that'll.

G

Be resolved pretty quickly, so um I think once that is merged, we that's when we should uh use the slackbot and send because um well, okay, actually until.

A

The schedule is merged. What is that exactly? It's gonna be the.

G

Release schedule: okay,.

A

G

So um once the schedule is merged and we update the website keats.dev release, um because that will be okay yeah. uh What.

H

We want to point people to what we want to point people to.

A

Okay, so once the release schedule's merged and the website is updated, then we'll want to do probably a slack bot message and probably tweet.

A

um Do we need to do anything like a blog post, something bigger here? um Slackbot tweet is probably enough for now. Yeah.

G

That's that's probably going to be enough for for this. It's mostly just um yeah, I think, usually usually there's an email that goes out to cada from the current release team with the schedule. Okay,.

A

So we probably don't need to be involved with that, though yeah.

G

So yeah either pointing people towards the website pointing them towards the email that I go to kdev, um just to get more awareness about enhancements, freeze and the timeline changes for 1.25.

A

Okay sounds good and uh that'll be a good note for avinesh on. We want that mentioned in the community meeting and ray because you're, actually, the person who's going to be doing the community.

F

A

I guess I should assign you to that.

A

Oh no, what did I do? Oh.

A

No, I did not need to do that. Sorry, typing is hard for me to mention so I'm taking down these action items in our notes for now, depending on time, I'll get them into the um table, but they're at least here and I'll move them into the table after this meeting. If I need to okay, uh if that's all, you can think of right now, we'll move back into the open action items.

G

Yes, sorry to like just drop the last no.

A

That's how these things go as long as we get to them as long as we mention them, it's better than not mentioning them.

A

Cool hina's pr uh for the github list, so that will get notifications of issues is on hold. uh You've got that update the next one is virgila's action item about the auto generation of blog tweets. I know that this was blocked, because the um the tool that we were looking at using for auto generating tweets about blogs uh has an issue and can't be used directly.

A

uh Any updates on that from anyone.

A

I think it's been a couple of weeks. You.

F

All have been meaning to.

E

A

Still nothing yet.

E

Yeah nothing yet: okay,.

A

Are you liz busy busy? Have you all been able to chat with him at all, though see he's still thinking about it?.

E

He was working on it. I just need to pick him back just to see what what he has done. What's the progress.

A

And this is why we need more maintainers.

E

A

I really appreciate you all working with uh rajoula on that to try to figure it out.

A

Those kinds of things can be quite tricky, uh so the next item in our action items list is check in with matt about the twitter together issue. Chris was going to check on that avinash noticed a thread in the slack saying that was in progress, then last time we actually checked. I don't think we updated this. That matt said that he wasn't going to be able to get to it until may in the github issue.

A

um Are there any other updates? I was just in github from a while ago, so I'm not sure if it was relevant, you haven't seen anything. Have you bob on the twitter together thing.

G

It's been a little bit since I've. I've looked at it.

G

I know so there was an open. uh Let me check real quick.

A

I just need some requests.

G

Oh um so the the current maintainer for it says that they are essentially blocked until the beginning of may yeah. So there are open prs to address some of our needs, but likely won't happen for like another month. Okay,.

A

That's what we noticed last time so is what it is.

A

I hope we can get that in though the scheduling will make a really big difference. I think in our workflows um so we'll check in on that later.

E

He uh matt has written on the pull request thread that he is not sure whether he would be handling the scheduling thing. Okay, I I'm, I might be uh far behind the update, but as far as this thing on the twitter, uh the github thread is concerned. He has written here that he won't he's not sure about handling the scheduling thing. Let me grab the link in.

A

E

But there was there was something in this lag, but maybe a thread or something I might better.

A

Handle through automation on github, rather than relying on twitter, so this is like debating um whether this should be implemented as part of twitter, together or as external, like a github action.

E

A

Okay, that is good to note. Thank you for pointing that out just to tackle this as part of spr separate discussion issue. Pr.

A

All right: well, I want to move on to other action items, but let's keep that in mind that we may need to look at a separate scheduling solution.

A

We keep saying like it should be doable with actions, but we haven't spent the time to actually evaluate what would be needed there or what that might look like um so separate solutions indicated.

E

I've posted the slack thread here.

A

Yeah, it's also mentioned in the the pull request, that's linked in the action item, I'll grab that link. Thank you. Tarva.

A

You have that direct comment as well.

A

Okay link that here.

A

Thank you and I'm going to move on to the next action item. We can come back to that if we have time and discuss it more um avinash world description for community meeting interface role, we wanted to get a few more of those um done first to see what it would look like. That's still the status.

I

um Yep, I believe, for after this meet we'll have some great idea about what exactly the description would be about the room, uh yeah.

A

So you'll probably have an idea and be able to get started on some description there. After april's meeting.

A

Started after april's meeting.

A

And okay is that next week or the week after.

A

Next week, okay, so the next time we meet we'll have something to talk about there. Probably um next one release webinar just keeping an eye on 1.24 release stuff. You know the release has been delayed by two weeks. um Do we know if they're planning to do a webinar? If there's one scheduled, if we need to tweet about it,.

H

um I believe there will be a webinar. I don't have a schedule currently, um okay,.

A

Not scheduled our note on that currently is. This could be months after the release, so.

H

It can be, and usually is a month about after the release. So okay.

A

It's good to keep in mind because otherwise, we'll probably miss it unless someone brings it up um but will be a while before we have to deal with that uh tweet about feature blogs that come out after the release and will be released by the end of this week. So we were supposed to be able to talk about it this week, but since it got delayed by two weeks, I'm guessing those are delayed or are they not.

H

Yes, if they will be delayed, that is actually a really good point. We should adjust some of the dates that we.

A

H

A

Delayed by two weeks, so not next meeting but the meeting after we'll want to talk about that which is the 29th.

A

Yes, let's discuss on the 29th.

H

Yeah, um actually, we could discuss next tuesday because well I actually no no you're right. The 29th, I'm getting my dates. Yeah, so we'll discuss on the 29th and the featured vlogs will start on may 4th. um Well.

F

H

Release blog will go out on may 3, and so will a special history of dr shim blog will also go out as well. um That is a little bit different. We normally don't release two blogs on release day, but really so. This is a special release. We are releasing two blogs so um then starting on may 4 will be the feature box.

H

A

History of docker, shim blog on day of release and then the regular just release blog. I guess.

H

Yeah, yes, and.

A

So we have two vlogs to tweet on the day of release which is may 3rd may 3rd.

A

May 3rd I'll probably break that out into a separate action item after this I'm going to leave it there for now. um So we have a couple of weeks and we'll want to mention that on that same meeting, so maybe I'll actually just leave it there, because this is stuff to discuss on the 29th um sounds good uh review, repo look into role descriptions.

A

We had quite a bit of discussion last time about what we think roles should look like for our group um chris wanted to look into starting to figure that out, but, like I said, chris is unavailable at the moment, so no updates there. For now um I had big action item which I was not able to get to this week since I was taking up some other things uh which I need to get done, though, which is the um tweet spreadsheet for kubecon eu 2022..

A

I usually have a bit more time on fridays than I do during the week, though. I have a couple things to do today, but if I can get this done before our next meeting I'll mention it on slack, probably and add everyone um or something like that, just try to let you all know before the meeting. So we can get started with that because we're a month out from kubecon.

A

I usually like to have a good amount of time to get these done. The example.

A

Tweet document, where I'll be putting it is already linked there in the comments. um If I get it done today I'll, let you all know sorry that I don't have that done yet.

A

A

Next, one furnace wire, you decided to do a spotlight on sig docs.

D

Yes, I decided yeah, uh I decided, but uh I guess I'll be busy this month with some of my college work and stuff.

F

D

So I was planning to start it by the end of this month. If that will be okay.

A

Whenever, on six spotlights generally, we do have that new request. uh I don't know if you heard earlier bob asked for a spotlight on the batch working group, um so we would follow a similar uh process that we do with the regular sig spotlights on that.

A

um But if you can't work on one until the end of the month, don't worry about it now, but if anyone else wants to take up writing a sig spotlight blog or in this case working group, spotlight blog, let me know- and I will get you set up with all the resources and guide you through that process.

A

um That sounds good on hold till the end of the month for whatever's big sig spotlight. You would like to make if we don't get the batch one done by the end of the month. I might ask you to do that, one if you, if you haven't, started your other one yet, which sounds like you haven't right.

A

So I'm going to put on hold until the end of the month.

A

Sounds good and whenever you do get started on that, like I said reach out to me, I'm happy to help guide you through the process. If you have any questions or anything along the.

A

Way, uh atarva need a new tweet on contributor summit. That was from last time. So I guess we decided on the sig docs thing last time, but oh yeah, that's right because we were talking with ray and ray was like I'm part of sigdoc, so we can do that.

A

It is a good idea. We should do that, but anyway tarva new tweet on contributor summit. I know that I pushed one at least so. Was there another one? Yeah.

E

Yeah, it's done. We we've been just going to give a detail to it, but it's out today.

A

Awesome so I'll count that as done um and I went ahead and added the new action item on catacota review into our action items list to make sure that we check on that next time. I also have a few other action items in the notes that I'm going to add into our action item uh table row: okay, um and so that is it for our open action items, and now we have only seven minutes left. Are there any topics that folks wanted to talk about for the last few minutes?

A

I knew there was something we were talking about that I was like we could come back to if we have time um or any other questions or anything.

I

Well, actually, I had a question.

I

Can you I mean: why is the these 1.24 release delayed?

I

I'm missing that point.

H

Yeah, so I could take this, um it's delayed of a of an issue would go 118., and so there was a fix with that. So they had to wait for until go, one was released and they also not only had a way to go when 181 was released, but also have to make sure that the fixed x is actually fixed um and so and also they had to also uh postponed some release.

H

Candidate cuts as well just to make sure to get that go 118.1 uh in there um and it's due to this actually have the chat. I actually have the issue, let's break csr validation um and that's put it on the zoom chat.

H

It's a kk issue and that's pretty much the reason why it was delayed, go 118 breaks, the csr validation fix pending and go 118.1, which was recently released so.

A

Thanks rick and thanks for asking avanesh, I was also actually wondering about that when I was working on how we were going to communicate that the release was delayed. I ended up deciding not to directly mention that it was a go 1.18 thing, but I wondered if I should have any preferences on public communication about why the release is delayed.

H

I think it's fine to leave it off um and also.

A

Fine to leave it in yeah.

H

I don't plan on leaving it well, I feel like if you leave, if you leave it in it's kind of it,.

A

Poses more questions, yeah yeah, that's how I kind of felt about it. Yeah it's a little worried. It would feel that way to people. So I didn't do that. Thank you for the validation um but good to know. That is why the release is delayed.

A

um I'm gonna put that into our notes as well uh info on release to release delay.

A

Okay, any other questions or things people want to talk about follow-up questions to them.

E

Can you please uh explain why exactly this spotlight thing is.

A

uh The spotlight! Oh yes, of course, um so this six spotlight series of blog posts is a concept that we came up with like two years ago or something it used to be an umbrella issue that we would track on our um board, which I should really get better about actually walking through um all of our different tools. They make things complicated anyway, so there used to be an umbrella issue there on our board.

A

That was for this sig spotlight series and it had a list of the different cigs on it that we wanted to create blog posts about the reason that we don't have that issue anymore is because uh the initial issue had that list, but then, as people took cigs to create blog posts on that would just be in the comments.

A

So it wasn't keeping very good track of what sigs had actually gotten spotlight blogs. So, that's why we don't have the issue anymore, but the concept still remains, and it's still something that we like as as a task so there's some information in our repo which I'll have to go grab the link to somewhere um about this, and the idea is to create a blog post. Where you interview the co-chairs generally of a special interest group within the kubernetes project.

A

I did one on sig windows, for example, so I pinged the sig windows group and I said: hey I'm from the contributor comms group. I would like to do a blog post spotlighting, your special interest group, who would you like me to talk to they pointed me to the co-chairs.

A

I created a document of questions to ask them about their group. What does sig windows do? What are particular features that you're working on that you're excited about? uh How do you know what users actually need from your sig, and how do you prioritize work?

A

What types of expertise do you need right now that you're missing, um so it included like a a call to action for anyone reading it? Who is interested in that to become a contributor as part of that group, which is something that's valuable to the sick um and just kind of talked about what the sig did and why they were important? So that's the idea of these blog posts, um so we've got some resources in our repo around example.

A

Questions that you could ask if you want to do one of these interviews and there are several examples of blog posts that we've created that do this spotlight thing like the sick windows spotlight. I can find that one really easily, but there's also a sig networking one that we did a long time ago, and it's been so long since we've done one of these that honestly, if we wanted to do literally any sig, it would still be relevant.

A

um So that's the idea. Does that help.

E

Oh absolutely thank you.

A

Yeah, so I've helped to guide a few people through this process of creating these sig spotlights um most of them kind of dropped off on it. It takes a while because of the interview component, as well as the process of getting a blog post, approved.

A

So when I did it, I did my interview of the sig co-chairs async. I just gave them a doc and asked them to fill it out, and I had to ping them several times to do that. There was another one that got done. The most recent one um chris actually did a live interview with the people and recorded it over zoom, and then chris ended up not having time to write the blog post. So he passed it off to someone else. I think that was oh gosh.

A

uh I can't remember names right now, it's like in my head, but I can't anyway, so we got one other one done that way. So there's a several different ways that you can get the information and then you turn it into a blog post and go through the process. But if you want to do one, I am here to help you you're welcome to ping me directly.

E

Yeah I'll, be you.

A

Sounds good if you want to do this batch one I'll also give you some information on that, but you can also pick whatever you want honestly, because these are very useful things to do and we're at time.

A

So, thank you so much everyone for coming today and I'm.

F

A

Go ahead and stop the recording.