Kubernetes SIG Contributor Experience, 7 Jan 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes SIG Contributor Experience Weekly Upstream Marketing Team Meeting for 20220107

Description

Kubernetes SIG Contributor Experience Weekly Upstream Marketing Team Meeting for 20220107

A

Good cloud, hello, all welcome to the what day is today january, almost february january, 7th 2022 uh upstream kubernetes marketing meeting. This is the first meeting of 2022 so welcome all I don't see any new faces on the call. I think I might be a new face for this. One.

B

A

It might make you hear the new face and then maybe james, I don't know if you've been here before so I.

C

I'm going to be beautiful.

A

B

Yeah yeah, so hey folks, um I am a pm for uh hosting kubernetes solution oracle and I will be the uh the coms coordinator for 1.24 on the release team. um So that's that's the reason I'm on the call today to introduce myself and um to share that we'll be working together moving together throughout this, uh this release cycle so nice to meet. All of you awesome. Thank you for joining us really.

D

Appreciate that, um on the note, uh my name is james, uh I'm a senior solutions engineer at jet stack. um I am also the release lead for kubernetes 124 and until we started talking to mickey about uh how you need to go to this meeting, I didn't know this meeting existed. So I figured I should probably come along and say hello as well.

D

I don't know if I'll come along to every single one, but I'd at least come.

A

By and say, hi so hello, we appreciate you coming by. um We have tried to have shadows on the release team in the past, but that hasn't always worked out. Well, it has worked out. I think, until this release do we have a shadow or dab array either one of you working on this release. Nuts.

A

That's fine, no worries. uh So thank you for joining us. I should remind everybody before we even get any further. uh This is. This call is recorded. uh The cncf code of conduct applies basically, please be nice and respectful to each other. uh Don't do anything your mother would shame you for um that's how I put it because I will call your mom. I will find her and I will call her and tell her anyways um so updates big ones meet our contributors that went out. That's awesome.

C

Yeah that's out and we need to send comms regarding it, that's it, but I think we have to wait because the website is not yet live uh uh like in kw. It's like, but in qnet's website, not like.

A

Okay, we want to send it out from the key blog makes sense higher traffic yeah totally awesome. uh Do you need any help with that? Is that going okay shouldn't be? Oh.

C

Yeah, it's like I I'll draft a tweet and send it to you, so you could just wear it out after this thing is done or maybe we could do it on monday, because the dates on the blog are on january 10th. It's live today.

A

No pressure, yeah um cool, all right, the uh um great work on that by the way, so I know that took a long time to get together. I know it took longer because the holidays, so thank you for bearing with me, um I need okay, if there's a sig multi-cluster blog pr.

A

Do I need to sign off on this, because I know I reviewed it.

E

Actually, actually, I created a pr because I know um probably you had some some things going on. uh I didn't want to poke you too much. uh I yeah yeah yeah. I I shared the draft. Maybe a month ago, with yeah, I went.

C

Through it, okay, okay, so other than that, one.

E

Comment, uh I didn't find anything else, so I tried to get as much information from the audio and video and the transcripts and try to put it in the blog. I had to trim a bunch of stuff that we see like um and you know and think and um but uh glad. Finally, uh the peer is there so from now on, then it's only text to text yeah.

A

Basically, I did something different for this one and it did not work right like take a note, doing a zoom call and just recording it and getting a transcript afterwards is not the best way to do an article right. So ask your questions via email, much easier to type them and copy and paste the answers out, uh but I mean feel free if you want to do like an in-person interview and then use that transcript as text. That's fine, but it didn't really work that well for us this time right right, but all.

E

A

Yeah awesome uh anything, oh twitter, automation is or should be ready to go. uh We need something to tweet to test it. So maybe monday we could figure out what that is or after the meeting today. um But yes, it turned out that nobody on this team had the permissions needed to make the change. So that has been fixed caslin and I both have perms.

A

uh I can add others as we see fit, um but yeah you actually need to be a github like admin for that repo to actually change it from master domain, which bob thought I had, but I didn't so yeah george. Had it not helpful for us, though uh so yeah that's fixed. So let me put that down.

F

There's a new doctorship blog out today. I think that's a good.

A

F

A

Yeah totally, that would be great.

A

Especially because I contributed to that blog, so I don't want to write the tweet for it, though I will say that someone else can have that pr if they want um but yeah use. The issue template like go through the whole process make sure it works. Please.

B

And out of curiosity, how does the docker shin blog that was published today different from the previous ones,.

A

This one includes a lot of additional data around the survey we sent out. I think, okay, um let me double check real quick. I have it open in a tab somewhere, I swear, but yeah the you know it being the first post of the year and everything like the data we got back from.

A

The survey was like we're not ready like no one's ready, um so we needed to have some more of that drum beat going. So we reminded people the deprecation timelines, our next steps.

A

uh You know where the faq is. If this is the first time they heard about it, the whole nine yards right like because this is something that clearly we have to communicate more of and like, I would almost go for a weekly tweet like. Are you ready for docker shim replacement, like I'm? I'm almost to that point, because you know even internally here in aws, like there's a lot of our customers, that just aren't ready for it. So we're building some tools to figure out. Are they just emotionally not ready.

B

For it, or do they really need.

A

No like they're still using like the docker mounts and stuff like.

B

That the big one is mounted yeah.

C

E

A

Yeah yeah, so the the uh the that's. The challenge right is like getting people to understand what docker shim really is it's not just docker right like it's, this hacky piece of code that we're removing and here's the impact of that and here's what you need to do to replace it kind of deal.

A

But yeah that's kind of it was. It was more of a synopsis of the survey and kind of getting that info out there and then letting people know where to go for help.

A

So like sig, node and kubernetes slack that kind of thing um so yeah like we could. We should totally tweet that out and have it burn up the internet like it should, if.

C

A

We'll make it happen kind of deal um so yeah. I don't know if the notes up hang on.

A

um Cool so new items, hey the release team's here.

A

How best should we work together, uh especially you mickey, because I don't know what your workflow looks like, but as you're doing things, and if you want help, how do you, how do how would you like to engage us.

B

Yeah, I think that's a great question because I I don't necessarily know the answer myself. um It has been suggested that I joined this call, I think at least three times throughout the release cycle. um So um what are those three times is the question I wrote it down on my calendar.

F

I could add some background to that. Those.

B

Got this: when is the first.

F

Week of the release cycles to introduce yourself um a second time so part of the release process. Now we've added uh part of the handbook is that we're going to release a blog right after code freeze or the week of code. Freeze, that's going to say what is being deprecated.

F

What's going to be removed in this upcoming release, so I suggest meeting um probably a week a week before that you know so we could send a tweet about that blog I'll, get that ready um and also a week before the release just to highlight any future blogs or actually tweets about the release itself. That's coming up and also any future blogs, especially about deprecations and removals to be that's going to go out right after the release.

B

That answers that, so I will see you at least two more times this cycle. Yes,.

A

And you can always engage us by hitting at a contributor.coms. I I just joined the uh slack channel. So yes, but this is like a slack group- oh.

C

That's most of us so like you could be in any.

A

Channel and say, hey contributor, comms. We need help with this. Okay sounds good off. We come running. You.

D

Know is it worth asking your shadows mickey to attend this meeting kind of the ones that you don't do just kind of have them drop in yeah? Sure I'm happy to do that. I don't know if chris having a shadow kind of here, most meetings would be nice just to kind of ask her. Yeah might be.

A

Good for the shadows as well yeah, if there's anything that we can do to help during the process right like proofreading tweeting. Well, whenever.

B

Unless you're, not the right, debut you're, one of my shadows right.

C

Yeah, I was not speaking because it was not asked it wasn't.

A

Oh sorry, I didn't realize you were a shadow, so my previous statement about trying to have a shadow on the release team always is false.

B

Or already successful, even without putting any effort in there, you know yeah.

D

Great yeah apologies. Sorry! I didn't realize either.

B

D

B

Everyone, yet it's yeah, so that actually that's that's handy and that works out. So it sounds like no matter. What we'll have somebody on this call on a weekly basis. Awesome.

A

Yeah, definitely, you know how to engage us better than anybody.

A

A

Anything else release team-wise, I mean you're here any other questions about what we do or anything else.

B

No, I think, I'm I think, I'm pretty clear with it, okay, but I'm glad that we're actually going to coordinate this a little bit more in this release cycle.

A

Awesome yeah I'm looking forward to tighter integration with the release team. As we release things, you know it's a feedback loop. We need to just keep it strong.

B

A

So if you're deprecating anything serious, it's best to get out in front of it early, that's the one thing I will tell you: um don't let psp be the example that we repeat because it was funny. I was writing a blog post or I was writing the introduction to one of my newsletters uh about psp deprecation and how a customer at red hat had just finished implementing like stacks of psps hospital. It took them years to get it done. Yeah now we're deprecating it.

A

So it's like holy smokes, there's still people using it and yeah so getting in front of stuff like that early is best and we've kind of burned our fingers enough with that to know how to go about doing a little bit better. I swear there's like a career in crisis communications. For me at some point.

A

So yeah, that's my big thing. Anybody else got any tips or tricks for the release. Team, cool.

A

All right campaigns in progress check, twitter automation, anything else. I mean doctor shim things out the door any new items.

A

Let's look at the board real quick, since it is a new year.

A

I have that open. I swear.

A

It won't load there, we go all right, uh meet our contributor, vlogs and review requests. Internationalizations.

A

Refining the way we communicate deprecations wide, reaching changes to the project.

A

Yeah, I'm also milestone123, well, okay, fair enough um rewards and recognition umbrella issue. I think we can close that maybe.

A

Maybe I don't know: okay I'll check my pairs, but yeah. We got nothing in progress right now. So folks, on the call know anybody that is interested in getting involved in kubernetes doing a pacific profile is a great way to get started. Get your name out. There get some recognition, get your pr's and you know commits and such like that, so this group needs to market itself a little better.

A

Maybe you know as funny as that sounds right, like we're out here we're here to help all contributors uh of all stripes right, not necessarily your company, but if you're a contributor- and you want to get something out. This is this: is the venue or a venue.

A

Cool anybody have any ideas for the new year.

E

A

For anything, coming up any yeah like.

E

Anything we still have some time for kubecon eu right like is there anything that needs to start like way early for that.

A

Not necessarily from this group but sig controbex in general, yeah.

C

A

Already kind of are we meeting have we met yeah we've definitely met. We have the space reserved. We have um two rooms reserved at the venue. One has like some round tables kind of deal like we had. If you were in la at the contributor summit, kind of like that, just big round tables with lots of chairs and then the other room holds like 175 people ish, I think with kovalvid protocols in place.

A

So you know we don't expect a lot of people, but a contributor summit, or even just like a you, know, hangout hack on stuff. The kind of thing will happen. There will be no virtual component.

A

We know that for sure um after the contributor celebration that didn't go, that great it was just kind of a flop. To be honest with you right like so, you know, everybody's kind of especially after kubecon, I feel like everybody was burned out as it was for the folks that went and everybody that was on the celebration team when the cube kind of felt like so it was like pulling teeth to get stuff done, uh literally and figuratively, almost because you're you're dealing with the holidays you're dealing with you know all the stuff.

A

You normally deal with that time of year. Oh and let's launch a celebration and try to do bake, offs and stuff like that. It just wasn't happening so yeah and everything within coffee.

E

Protocols, yes,.

A

E

With the masks.

A

um I mean it was all virtual and we did most of it in discord and it's just kind of meh.

A

I mean yeah, our usual suspects were there, but it wasn't a lot of newbies if that makes sense where normally events like that are heavily attended at least last year, when we did it or year before the last one. We did it. It was heavily attended, but we just didn't, have a lot of participation this time, so we've got to, like you know, based off reading non-tech reading that I do we're still in this pandemic.

A

A lot of people thought that we wouldn't be here for this long and people are kind of realizing this year.

A

Three now of this stuff that we're beginning kind of deal, you know 2020 2021 2022, um so I wouldn't mind seeing a blog just going to community members and asking like how are you helping contribute during the pandemic right like, I think that that would be a great idea, given that you know a lot of people need to figure out like all the stuff they did for the pandemic, originally in 2020 like they need new stuff.

A

Now because you have some greater mobility but you're, still kind of stuck with the logistics of dealing with the pandemic, so I mean, if we needed an idea, there's one um I'll write that down.

A

Let's see new items, maybe.

A

How do you spell coke coke c-o-p-e yeah.

A

Yeah, I won't get too for both.

A

Cool all right.

A

Trying to think what anything we have from last time, we need to go back over.

A

Oh, how is the catacotta scenarios? Are those done or I forget.

C

Oh yeah, it's done. I I just like. uh Even I also forgot about it, thanks for reminding we need to send comms regarding it. Also, uh it's it's all prepared, and it's already just we uh we need to send comms. That's it like category is working fine. um I was working on like presently. I'm working on the website part like how to teach the new developers how to set up website uh on their own uh local system, because most of the folks start who are contributing to documentation and the major use of their faces.

C

You know setting up the website locally, so I'm working on that presently, but yeah. The basic part of you know uh setting up kubernetes less communities in the local system. That's done for linux users or windows. It's still like there's no scenario for windows users in category, so I'm figuring out. If we could make a customized scenario for that.

A

Wow, do you have a windows box.

C

But uh like at present, I am confused like how to implement it in a category like the scenario, there is no native scenario in catacora that supports window. Like sure yeah, we have kubernetes playground. We have ubuntu scenario, which is the linux part, uh which we just did the tutorial on. But there is no windows scenario like you know the wsl, or something like that. There is nothing present.

A

Who owns catacotta these days? Is it alright? Yes, yes, okay, let me you know what I'm an o'reilly partner. Let me reach out to my contacts over there.

C

A

The email um yeah partners, riley and then I should have your email in here. I don't okay, I'll grab it from slack. If it's in there um yeah. Let me put that down as an action item at the very least, so I could find in the browser window ahead.

A

A

Is anybody else interested in following along with that conversation I'll see you but yeah cool.

A

All right, 30 minutes anybody got anything else.

A

Wonderful all good awesome cool, so I will stop the recording. We can work on other stuff after the fact feel free to stick around, um but farewell everyone have a safe 2022. If this is the first meeting you're watching and uh we'll see you soon nice to meet you guys. Likewise,.