Kubernetes SIG Contributor Experience, 18 Jun 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: ContribEx: Weekly Update for 20200618

Description

ContribEx: Weekly Update for 20200618

A

It's okay office hours days are just a cluster for me, so I've been I've been discombobulated all day. All right welcome everybody. It's june 17th. um This is the kubernetes contributor experience weekly meeting. I am george castro, I'm one of your co-chairs and host and um bob will be the note taker real, quick. Let's do some introductions, I know jenny's new and then everybody else, let's just let's take two minutes to like tell jenny who we are so we could just introduce ourselves. So you wanna go first or last your your choice.

A

I can go first, then all right.

B

Okay, hi, I'm jenny. um I work together with laurie and she was really making that really nice, it's my first tip into open source. So please excuse all the newbie failures. I will do um I'm head of engineering for one and a half years now, um so I'm not really looking into contributing code wise but contributing um with coaching more with helping organizing and I hope, to learn also more about different leadership. Styles and yeah, I'm an introvert!

B

So at the moment I'm more reading and observing- um and I hope I can get an opportunity to work with you.

A

Awesome welcome definitely love to have that skill set. Thank you uh who's next bob and then whoever introduces just pick the next person to yeah.

C

Okay, uh I'm bob killen uh one of the other co-chairs uh with george I'm mr bobby tables uh in well across everything.

C

um I typically work for the the university of michigan, um but I spend- and I spend a lot of my uh time here- uh just helping well helping contributor experience with a whole wide variety of things, and I will kick it off to marky, since he is directly left of me on my my screen.

D

Hello jenny, my name is marky. I am one of the contributor experience peeps. uh I also do release stuff and I am the newly found director of open source at opsomex and I work in other communities as well. Welcome if you ever have any questions, if you don't, if you want to don't feel comfortable asking you you're more than welcome to ping me uh if I don't know the answer, I'll find it but welcome, and I will go to who is next to me, which is george.

A

George castro, I work at vmware uh as one of the community managers and that's it. I am.

E

A

I'm just coming off a holiday and uh daycare just started for my kids, so I've been working half time for a long time, uh so I'm kind of getting back.

A

I'm very disorganized right now. That's I'll just go with that yeah! So I'm getting.

F

A

The saddle here, uh paris, why don't you go next.

F

Hey hi, uh I do community stuff for kubernetes and cncf. I also sit on the steering committee, so nice seeing you here.

F

A

You have the pic who's next, oh.

F

G

uh So I'm don foster. um Like george, I also work at vmware. I do open source community strategy within our open source program office.

G

um I was doing kubernetes strategy when, when I worked at pivotal before we got acquired, so I actually don't do a lot of kubernetes stuff right now, but you all are so much fun and I really liked being in the contributor experience thing, so I just still like come and lurk and hang out and if I can help out in any way, I I will that's kind of what I kind of what I do. I've been doing the open source thing for a really long time.

H

A

You pick the next person.

G

Josh on his bicycle goes next.

H

Yep um on the bike, I figuring that I can use self-isolation to do something about my pillsbury doughboy physique.

H

I work at red hat um on pardon me, cloud native community things um so kubernetes prometheus, uh etcd, whole bunch of other projects, um and I've done various things for contributor experience right now. I'm working on the new contributor workshop with alison, who is not.

F

H

Because she lives in new zealand- and it's like three in the morning where she cool.

A

And that leaves the.

I

Oh yeah, um I'm a developmental cncf and I'm doing a lot of community since here.

A

All right, okay, so here's the agenda I'll go ahead and paste it again in chat, so let's just get started and be efficient, uh quick office hours, so today's office hours um these happen. The third wednesday of every month uh had a record session this morning, 188 uniques participating. So that's like really good.

A

Unfortunately, due to some uh panelist cancellations for the west coast and jeff and my schedules not being able to back each other up, we had to cancel the west coast session, but overall the traffic continues to get better and I'm pretty happy with um what we're doing there challenges moving up is um representation on our panels is still not awesome and it's something that um we need help on and I'm actively working on any questions for office hours.

A

You are muted josh. If you're asking a question, you are still muted and zoom your muted, not your pc, that helps got.

H

A

H

um uh For the west coast edition, have we considered moving it even later to a more apac friendly time.

A

So initially we did and that's when the traffic really started to drop, but I would be willing to try again like I'll, try everything if.

H

I can get obs working, you know see the thread for that discussion.

A

H

I'd be willing to try hosting an.

A

H

Friendly one right because for me that's four in the afternoon: it's not really painful.

A

Right right, okay, yeah! We can definitely do that. Oh and the last bit we are going to do a special edition with sig network on ingress that we were going to do, but with what was going on in the world, we felt we cancelled it. uh So I don't know next week I'll sync with the chairs and sort that out: okay, uh anything else, office hours, I'm seeing nodding generally uh paris, community meeting you have one in.

F

I just wanted to um say that I'm submitting a pr for steering for syncgovernance.md, uh which will hopefully reduce the requirement from four sessions a year that you have to give updates from a community group perspective to two plus the annual report which we just introduced right now. We don't have any groups really that meets the requirements, so we just have policy policy laying out there that nobody meets which isn't good. So I'm going to submit a pr for that.

F

That could essentially affect how the meeting is laid out, probably in a positive way, because it would be less less things to jam in, um but that's it. There.

A

Okay, yeah! Sorry, I don't in hindsight I don't know four times a year. I don't know what I was thinking with like 46, but thanks for that um and tomorrow the host is going to be lori uh and she's, giving us some hoe, so we're actually set for hosts until october. So that's really good um any questions on community meeting. That's just tomorrow. Normal time I feel like the monthly cadence has been good. Attendance has been good, so uh no problems there. As far as I can tell contributor summits, bob.

C

uh No updates on the contributor summit at the moment, sweet steering committee election bob. uh We currently have two confirmed um election officers uh jace and josh uh ihor. uh I poked him literally just before the meeting start is a if needed, or you know shrug um it was not shrug.

I

It was like I'm happy to do it, but any other candidates who have never been the election officers and you'd like to be so happy to step down and take my place. Please yeah.

A

However, bob you wouldn't be in an actual officer right, you're, not on this list.

C

uh I am not at the moment right.

A

C

I'm uh waiting for like the next two weeks to play out. Okay, because I.

A

C

Better idea of how how my my schedule should be lining up for.

A

C

Later half of this year.

A

The reason I bring that up is neither josh nor jace have done an election, but you've done two right, so we, I think yeah yeah, just.

G

Kind of do like.

A

The shadow do the release thing where you're just kind of like I think, we've documented it enough or it's fine and I see josh nodding. I don't think this will be a problem.

I

uh Actually, as far as I remember, we, uh we have even agreed that at least two two individuals have to be election officers from the past. If I can find it link meet it well, but anyway,.

H

I looked over the docks um when uh george brought it up this time and that's what it says.

I

A

Right now we have zero confirmed.

I

A

I

A

I

A

Okay and then bob.

I

And I will decide.

A

We need two, then bob, and I will do they buying grant that everyone ask brian grant if he wanted to come back just curious, not yet. Okay, all right anything other election election based things like that um is there a next step here is the is: is the election in steering's core, or do we have to do something? We.

C

Need to propose the election officers.

A

Thank you. Okay. It's.

C

A

C

Okay, uh do we have a deadline for that? um I don't know an official deadline.

C

Okay, so end of the month.

A

Okay, got you all right.

A

Sorry, I'm just taking a personal item to check on that.

A

Okay, good! All right! That's your run, smooth! I think starting early was a good idea. um Paris, any comments here, all right. Moving on to mentoring with paris.

F

Hey y'all, um no real major updates for meet our contributors, I'm still lagging on, creating that apac second edition, but for next month for july. I think I have two folks already confirmed. I just need to double back with them from our reschedule from june, but I would also love to see some folks from sync testing. Sig scalers take off just going back to see when some of those folks have come on last and haven't seen any of those folks in a minute. So I'm going to reach out to that crew.

F

But if anybody here is on the line and a part of those three groups and would like to volunteer to be on the panel I'd love to have you and that's it for meet our contributors.

F

Good to know, isn't the keto on yet.

C

I think I think she's in a meeting right now.

F

Outreachy, no new updates uh g sucky, or do you want to give? Do you want to say anything about gsoc? I think it's just in progress.

I

Right right, the same is coming into bridge.

F

Okay, yeah so yeah we're chugging along on uh g-suck. um I know a couple of students have been pinging me and they're still excited, so they haven't been scared off yet, which is great uh but yeah. That's pretty much it for mentoring. Right now,.

A

uh Let's see community management, we don't have a person for this, but bob needs to know chairs, tl's, email.

C

Oh um just uh we have several items on the list already and I checked it this morning. There's a couple that we should toss on there: a the release, timeline, change and then paris, you toss two items on there, uh one regarding the working group, annual report and then the steering committee. uh Can you group a liaisons role.

F

So just context because I know I haven't been here in a few weeks in steering- we've created uh this concept of an annual report, it's very similar to what apache does for their projects and their pmc's reported each year, unlike the project health. But this is a little bit granular because we're going to be doing it for our community groups, so it'll happen once a year and they have to report in on certain questions and things that we are asking them since this year is kind of not great um we're going to be punting.

F

A lot of this to 2021, except for the working group session uh and since working groups uh are sort of supposed to be temporary in nature anyway, and some of them have been hanging out for a while we're going to do a deep dive first into the working groups and then also potentially iterate on the annual report process period from what we learned with the working groups.

F

So if any folks here are in working groups, we're coming for you, we want to collaborate and talk and have open lines of communication. And when I say we I mean steering and that's pretty much it so. We also introduced the concept of steering committee liaisons, so every community group, which is sig working group user group, et cetera committees as well, will have a steering committee liaison assigned to them.

F

So if there's any issues or things that you need to bubble up to, steering not that you know, even if accolades things like that, not you know not even necessarily negative, um then everybody will have someone assigned and then they don't have to come to like the principal's office. Aka, a public steering committee meeting, but those things need to get out to the chairs and tech leads. So we can start to water that information down but, like I said if anybody in here is a part of a working group, give folks a heads up.

F

This is coming and steering will most likely visit one of their public meetings. So they don't have to come to us we'll be going to them. Is.

C

There a list breakdown of who's, taking ownership, of which community group.

F

Yep, uh I think kristoff is gonna pr that in either today or sometime this week, um but yeah it's done. We just we just completed the exercise.

A

So, what's the tl dr on the annual report? Is it like a slide deck similar to like the community meeting status, or is it like a blog post or is it.

F

Hold up, it is a it's going to be a word, uh not a word. I hate saying word: google, like some kind of google doc hack md, whatever the community next um some kind of text exactly but then you'll you'll send it to private scariness for at first, because it gives the community group an opportunity to say private things like if you're having a major issue um stuff like that, but I'm getting out some of the the documentation um yeah.

A

I'm just wondering if, like over the course of the year, you'll get different sig and working group. Annual reports like to the mailing list kind of thing.

F

Well then, the idea everybody's gonna do it together. So um it's not gonna necessarily.

C

It's not necessarily.

F

Gonna stagger it's going to be an actual report, annual.

C

F

And then um hold on don't move.

C

Do you have a link to the questions already yeah.

F

That's what I'm getting right now so.

C

Sorry to stomp you with all these questions.

F

C

Could uh go ahead, go ahead and toss it into the uh notes. I have a big thing like insert link here.

F

Yep cool all right uh here it is um and then yeah. If you want to share your screen, you can see it um and all the questions are there.

A

Okay, sweet. I just wanted to see where I can find out more info cool anything else about annual reports. Anyone questions.

F

I think most of it could get automated honestly. I've been talking to laurie about it to see if lucas could build a specialized dashboard so that sig, chairs and tech leads aren't manually collecting their data like, for instance, one of the questions is send us a link to your last uh youtube community meeting.

A

F

And we could just automate that um I mean we could get youtube to figure that out. You know what I mean so yeah.

G

There's a lot of stuff.

F

That can be automated uh about. I think that's. My next step right now is identifying what those areas are and yeah.

G

F

Getting a dashboard built so then there's not a lot of work or burden rather on the chair technically to get this done.

A

Yeah, because if you were to ask, when was the last time, sig food did a status update or something I'd have to go in the spreadsheet like manually, you know like the only way I know sig apps has to go next week is because they canceled, and I left myself a note, a future note to myself so it'd be awesome. If we.

F

And that that wouldn't be on contrib x, that would be on sig apps.

A

Right, yeah, yeah yeah, but what I'm.

F

H

A

Automation where we know it's like uh oh, they need help. That would be really awesome. All right, awesome.

J

I sort of tabled the dev stats work for a bit because I was hunkered down in prioritization session work with the release team, but uh paris and you were also between jobs, but I have some notes that I've collected and need to revisit. Just uh I looked, I did a little deep dive scenic route, a tour of the dev stats, dashboards and nice looking for ways to consolidate and ways to make them more effective and more attractive for the signatures and leads to use.

J

So maybe we just um you had actually seen it, and you said oh thanks, so maybe we should just maybe we can look at that together and we find out like what we can do next yeah.

C

We actually, uh we haven't really talked too much about like we haven't, had a line item in our agenda for dev stats, but it might be time to actually put that back on there again for sure, thanks for sort of vidal, like really leading the charge and and taking ownership and running with.

I

J

I just like looking at grafana dashboard, it's a really pretty.

J

H

We need to talk about the consolidation thing, though, because lucas brought up some problems with consolidating grass yeah.

J

So they were just suggestions like I have no idea what's possible or not so we could dive. Maybe the three of us, you, paris and I would take a look at those notes and see like okay, what's possible, it could be like a half hour, 45 minute, walk through and be like. Technically, this is too challenging from a user experience perspective. This is a good idea. We should like overcome the friction.

J

The technical friction to actually make it look like this. We could get aligned and then bring him in and he can make the changes.

A

All right anything else before we move on to marketing all right. Nikita left to note that the uh no new updates from the apac coordinator, as that bi-weekly meeting was canceled next meeting is tomorrow uh marketing team there's not a person here, but paris, that's yeah! I was.

C

A

Yeah well, it says that you're going emeritus. So this is like your.

I

C

A

Will be your last report and then we could like do it yeah yeah.

F

All right, um yeah, I'm officially going to be emeritus because matt and the crew is almost up and running. That was my goal here- is to get them up and running uh and matt broberg is awesome. Matt is going to take the lead of editor role for the marketing team uh and I believe matt might be looking for a shadow, but matt was also doing some direct recruitment on his own. For that. So I'm not too sure where he is but gotcha. uh The major announcement is, we need more help.

F

I mean we've got a team of at least six uh six that are coming weekly and producing weekly and we probably need a team of twelve uh to be totally honest um and I'd love to have more storytellers there. The storytellers are the people that are doing the sig profiling and the.

G

F

Profiling and making it less about a technical blog, but more about us and humans and the the pathways to contributorship here um so yeah, if you're, interested and or if you know other people who are interested in telling stories like doing kinds of like interviews and stuff like that, that's the kind of stuff, the kind of work we're looking for.

F

There's an issue template now in kubernetes community for us to engage with us you'll see the issue. Template uh talk about tweets talk about events, talk about like pretty much anything that you would contact your marketing department for at your work. These people would do but remember that their scope is upstream contributors, and that is in the reason. Why is there's already enough work there, that we don't want to blow their scope? So right? um That's that and then also please follow kate's contributors. We plan to launch soon.

F

uh We've been like in this long in this, like noodly launch state for like a week now, but that's just because society and unrest and like wanting to make sure we don't look like jerks and it's just been kind of taking a day by day, to be quite honest and we're just wanting to make sure that we don't. You know, start off on a bad foot, uh because you know how twitter can get so.

F

um That's it and a kdev email will be sent soon and that cadeb email is to talk about how how to interact with us. Why to interact with us uh and everything like that, and then we'll also explain that the release team still has a has a communication person so that they still got that and we'll just explain a couple more things. But um that's the marketing update.

A

So you had mentioned that kids contributors hasn't gone live yet so like like. What am I telling people at work? If you work at kubernetes, follow this now or am I waiting for your email.

F

You can just say, follow it now: it's not going live yet, and you know we we're trying to go live. I think today, according to my group, a group message right uh kind of like no time like the present, in my opinion at this point, so okay, um we're also fumbling around with tooling right now, because the api like got rejected and approved and rejected, or something from twitter.

F

So right now we're just doing manual which is really going to suck. Does.

A

It have a little, it doesn't have a confirmed. Oh, it does not. Okay, just yeah.

F

Yeah, no, we don't. We don't have a check mark or anything like that. I doubt we'll even get a check mark, but it's fine.

A

It's a badge of honor not to have one um is, is matt, then the sub project who's the sub project owner. Then, if you're emirate, I'm not, I don't I'm not looking at the owners. I'm.

F

Emeritus out of the team, not the folder.

A

F

I'll still be in the folder and still help them out with their approvals. But matt is going to take the team.

A

F

And matt is also now in the owner's file as a reviewer perfect, and I will most likely be promoting him to approve her shortly, so we're making our way down the community membership guidelines. A.

A

Sweet emeritus life all right.

J

Is there like a tweet that is just already in use that I could retweet with the idea of recruiting more contributors to the marketing team like um no, would we get that.

F

J

Yeah, I think that would be good, and then we could just all share.

I

A

J

And the second thing was that I was just coming from the hallway session that stormy peters is setting up and the topic. There was diversity, inclusion and ava who I've not met before until that session. uh But it's, I think, on the kubernete yeah. So um we were talking about uh what we could do and I think that this could be a good opportunity to bring the dni language, given that it's like focusing on the human focusing on different perspectives.

J

Different, uh you know we're we're a community of many different uh people and that could be worked into the messaging somehow, because we get this marketing team off the ground like we're finding stories for the different things. But we can also find stories about maybe like um human interest stories, personal profiles, people who might be um facing different challenges uh and but still contributing to kubernetes, like many people are facing uh different types of challenges right now, uh regardless of what country they're in so.

D

J

Could be an angle that we might want to explore in the marketing contents, in the blog posts and elevating contributors like their profile.

A

J

A

Also, when we launch this and we kind of have like the preset tweets, like I'm thinking my brain, we should definitely call out every favor, like every famous person who's ever like tweeted about kubernetes.

A

You know like ask them like the one thing be like you know like. I feel like whenever we launch, if all of us tweet on that same day, it'll be like. Oh.

J

A

Yeah it'll be clear, like everybody and then we'll line people up.

C

That actually might.

A

C

J

Yep: oh: go ahead. Bob.

C

um We might want to actually just bring that up directly in the marketing meeting or put on the agenda for.

A

That, on friday,.

C

F

A

F

Sorry there you go since I included, I just included in the chat, the marketing team's uh notes and, if you scroll to pay at the end of page two and then three and four, this is our launch schedule for twitter.

A

uh Perfect perfect, thank you.

F

So we've got our first tweet. Our first tweet will be um like a hello, contributors.yaml joke for sure, and then the next is gonna be uh like meetings meetings. We have so many meetings and then clicking like uh clicking the calendar link and we'll do that once a week every week on sunday or monday. So it's like your meetings ahead of you this week kind of thing um and then we're also going to talk about.

F

Obviously the community meeting when that comes up and then talk about uh one tweet will be the sig scalability blog the next day the it'll be the blog for the kate's info working group, the next day after that um it'll be aspiring contributors thursday. So post your good first issues here and then friday will be shout out fridays and we'll be looking at the shout outs from the slack channel and shouting people out on twitter.

F

So that's kind of the the schedule, but obviously things are going to pop up in between there. But it's the the idea there for them is that every day they have at least one tweet, that's already been curated uh and scheduled. So.

G

Like thursdays.

F

Will always be aspiring contributor thursdays? Fridays will always be shout out friday. It builds the. It builds the audience expectations for what they're going to expect from the account and then like sunday and monday again, you can always expect to see a calendar of like what's sake meetings or this week.

A

Github management, bob or nikita.

C

uh One big thing: so the github org cleanup we punted um just because it it didn't, seem like a good time to send an email to kdf. Hey we're gonna, be booting people out of the org um at this point in time, thinking probably the first week of july to send that notice out and update the community membership doc.

C

Does anyone have any other thoughts or opinions on this.

E

A

Okay, hey all right.

C

A

All right and then.

C

A

E

Yeah um just that we have a new slap channel uh for github management discussions, so you could join. It um announced this down in the uh open my discussion below as well, uh so we talking a little bit about uh renaming the master branch name, uh the default branch in general. So, if you're interested in those discussions, that would be the right channel too.

A

All right anything else on github management, slack infra I'll, be fast. Before I went on holiday, we had a meeting, it's really hard to have a meeting when we purposely spread everyone out over the world so that we could get slack coverage. So that was really difficult. So I was only able to get a certain amount of moderators, but we did update the contact information we were able to uh like retired, and we have some due outs that we need to do.

A

My biggest concern was code ownership of like the things that katherine was working on and marky has been working with pierre, on, like on ramping them and stuff is happening. I'll have a better update next week. Any questions on slack.

A

All right, contributor, documentation, bob.

C

Okay, a couple quick things: I've been going through the contributor guide and could release some help just going through it and like commenting on which things are really outdated and should be removed. I found a couple things that were like still referencing all our stuff. As maintainers and saying we had a two-day turnaround time on prs.

C

A

Reading that, that's for sure, yeah.

C

um So ideally, we at least remove that stuff, either immediately or note that you know it should be removed, um and then we also have a lot of like duplicate information scattered around the docs. um So this is sort of the lead up to an eventual reorganization, rewrite of the contributor guide.

F

C

And just getting all you know, sort of mapping out where the documentation like which section all has a little the different documentation will help with that where, where the dupes can be removed, um the no news on developer guide, contributor site, uh we have a few launch list items and one of those items is actually uh the contributor guide update item of going through and and printing that stuff. So we can uh get it nice and good before going live and- and that's that's pretty much it all right next- is reviewing the project board.

C

A

Let's, let's skip that yeah. Do you all mind if we go to the just the open mic, because there's a lot of important issues, I think we need to turn through here and the the board is. You know.

C

That's the next week problem.

A

Yeah uh laurie you've got your the first two items.

J

ah Thanks so I'll try to be quick. um Basically, uh we've been talking about triaging a lot as a tool for cigs to improve their workflow and improve pr velocity.

J

So stephen and I have been just chatting- I don't know if I'm going too early on this, but basically a working group that would be focused on triage, so we're going to have a triage party demo tomorrow with community meeting uh triage party, has a kanban board function now, so that is really helpful for uh sigs to use those camo boards to move work forward and it helps with their flow.

J

But I just wanted to bring the topic here to this group. Basically, we just want to think about how we can more officially offer coaching and support to sigs to set up triaging processes or improve their existing processes and then continue with a community of community of practice. Efforts to help sigs share their insights and advice about triaging and the channel that uh the terrorists and leads channel, um and then uh my suggestion was to like, uh or one of the suggestions I had was about dev stats was to like.

J

Could we use the dev stats in this capacity to show the pattern and trend data over time so say a sig starts doing triage dev stats can help them potentially measure the impact of that you know they can see their workload go down.

J

So this is very early, but I just kind of wanted to bring it to all of you, because this is a topic that we've been talking about for some time and then, uh unless there are questions I can go to the next topic.

E

um I have one question um sure what so, why does this need to be a working group and I feel like when I think of triage, I think, of uh helping and coaching six around triage. I see that as a responsibility for a secret contributor experience.

E

So in my mind I see this as a subproject for country banks, so I think I'm losing context around why this needs to be a working group instead of a sub project.

J

Yeah, so that's a good point and I think paris is plus winning your point. Am I right paris.

F

Yeah, I think they make sense of the sub project as well. Okay, just because then there's real ownership to it and it's not going to go away like the working group purpose is really for it to just do a thing produce a thing and be done with the thing and then the thing goes to a cig, but I feel like if we're going to take triage seriously and we want to make it forever, we should make it some project.

J

I think the idea with the working group was that we wanted to have some metrics and goals clearly to find around it, um but there's no reason that that can't be addressed in a sub project. um The second concern is just like making sure that people don't think this is sig pm brought back, but I think that messaging, like my suggestion, for that, was that, because it would be time boxed and also because the um way we would handle this would be like embedded in the existing cigs.

J

It wouldn't be like a siloed effort that you would just have maybe an evangelist in bed with this egg or even there's a member in this egg who is really pro-triaging and then it um it can that can answer the question of oh, it's a pm again but yeah. If it's. If it's a sick project, sub project of this sick, then again that that question will be answered.

C

Yeah, that was a tough time we.

A

Trust you to keep stephen a in line.

F

My comment was just going to be right: go ahead and write a proposal for the working group, so we can see where your thoughts were um and then we can work from there, because that would be next steps regardless.

F

um So just I would just say you and steven just write up something and then nikita and kristoff and others will take a look at it and determine if it should be a sub project or a working group.

J

Yeah I've already written a few lines. I kept it really short because I don't want to make a lot of documentation for people, so I could just send that to where. Where do you suggest? I just share that.

F

Share it with the contributor experience mailing list: okay,.

J

I'll clear it with him as well just to make sure that him being steven just make sure he's. Okay with that, and then I can do that.

C

The thing, too, is that you can, um you know well talk to him about it, but because you know you've reached out to like the release team and everything can potentially cc them and and get some of the the other groups involved there to uh give it a look over.

A

Yeah or at least give your feedback.

H

E

um I just want to say that I love the idea about using dev stats and actually using that to drive change uh for triage. So that's awesome.

J

Thank you I'll put that as well as a note.

A

Also lori we're trusting you to keep stephen focused.

J

He is recruiting me for all sorts of things today and I was like. Why would I just like to get something if he.

A

Gets if he gets to six pm, he could just like poke him. A little bit cool.

J

Well, yeah, I think, he's quite conscious of bringing that back so he's.

A

J

No, I'm bringing it back that.

A

Is a three-year conversation? I've been having with.

J

Yeah, let's not start it again,.

A

All right uh any anything else, then do you want to talk about this enhancements, cuddle, cuddle.

J

Oh yeah, well, I was just. um I just also wanted to give up the update on the release team uh breakouts, so I concluded the breakout sessions and these were basically for the release team members to have very small groups, a very small group setting, so they could discuss all the many items that I found related to process improvements.

J

So you know github issues existing documentation, whatever was like triggering process for the release team related to the release cycle, and the idea is being. How can we clear the happy path for the release cycle to make it as frictionless as possible? So, whatever your status, if you're a new member or shadow, you come to the release team? What are the friction points that make it hard for you to like figure out? What's going on, so we talked a lot about those issues in these breakouts. So a lot of discussion around simplifying documentation.

J

uh Then there was um the work that jeremy's doing on this tool to make the enhancements component less manual, bringing transparency to and the enhancement process overall, so yeah. I guess I've just assumed that I kept control or kept cto. We're not sure what the canonical use is yet uh bringing that into this conversation, so uh the discussion sessions were really fun like. I was amazed.

J

We finished them and usually with 10 minutes early and if you're talking about 90 items of discussion, that's that's pretty impressive and people were using these sessions as opportunities to kind of gain. Clarity on existing issues, long-standing issues raise concerns that they'd seen in this cycle and over the past cycles that they'd been a part of um so it felt really gooey. You know.

C

I can say, as as being you know, some of them, they were definitely appreciated and people did get a lot out of them.

J

Yeah and for me, as a facilitator, was super fun to just have everybody come and be like full of ideas and good will and and get down to the business, and so the next step is that I need to review the content of the spreadsheet.

J

If you don't I'll, share the link with all of you so that you just know what I'm talking about. You probably already do.

C

Can you link it in the doc itself, see josh.

J

Oh yeah sure, um but basically here I'll put prioritization breakout sessions so basically yeah. The next step is to summarize those notes and try to understand some of the patterns. The points of consolidation, because we had a lot of overlapping items and then simplify all of that content into uh themes of work that will then kind of be like you could think of them as products and then like.

J

How would we break down this product work into user stories so that we can actually get things done in shorter periods of time than maybe you know, some of these items uh would have suggested or only enabled in the past, because some of them are big. Some of them are not so big, some of them. We could just template.

A

How many I'm cognizant of time here, so I don't want to take up too much. How uh generous sized is this like like? Is this something you could copy and paste to another sig who's like hey, I like what you did for sig release. We kind of need some of this.

J

Some of this is so what we didn't actually do, but tim pepper had wanted us to do. I think we need to sit down and what are the items that release team members actually have to do, and then what are the items that other cigs need to?

J

Do that step um kind of got a side stepped, uh but it would really help kind of focus the workload for release team members and then um I one of the columns, if you go into the spreadsheet, you'll notice that the uh the first column is like what is the area of release team work, and so those are basically like. I created a little scroll down, so the the items are thematized and obviously some of these items span a couple themes. But what is the intent behind the item?

J

Is it to improve documentation on behalf on behalf of enhancements? uh How intrinsic is it to the actual enhancements process? I tried to do a good read on the items, spirit and intent, but those can obviously be shifted, uh but then you know they're already kind of um categorized.

J

So that means that, like ci signal can just go off and take their few items and decide like well. How do we want to improve our process and then the caps? That's a big topic and we have a caps meeting, that's being scheduled uh or doodle told at the moment.

F

J

You can triage that topic into that meeting.

A

Okay, all right any last questions we have 12 minutes and three more topics. We can do this. We good okay, nikita.

E

Yeah I'll keep this quick, um so just an fyi si contributor experience is sponsoring the request for creating a new working group around inclusive naming you've. Probably already heard of this um stephen augustus, zach and celeste would be leading this. uh The kubernetes dev mailing list uh thread is linked in the dark. You can find out all the details there. There is a sig architecture meeting tomorrow uh that will be covering discussion on some of these topics.

E

You can join that if you're interested- and uh there is some discussion around renaming the master, the default master branch for our reapers- that's happening in the github management sac on saks, so you can check that out. um That's it.

C

One actually a quick comment on that. um The github itself is very aware of of alderman of this and there's a lot of stuff going on there. That will likely be bubbling up soon and a lot of people are sort of all over. The oss community is sort of discovering different edge cases.

C

um If we can gather all those things just that we have, you know we have knowledge of that ourselves, that'd be great dumping them in slack, and then she was going to, I think, create an issue later um in k community to sort of get this thing. So if you see anything, please please put that stuff. There yep.

E

um Quick question bob: do you know if, like your sins, are in touch with github folks? Is there something formal uh an issue internally between.

C

um So there's one in the os maintainers group, the the one that I think the entire github admin team has access to. um There isn't one in the the cohort. That's just uh ihorn and I at least to my knowledge, but.

E

um Moving on um the next issue, uh it's kind of solved, but I'll just go about it. um The issue is about moving the sick leads mailing list. uh I think right now, it's pretty manual and someone needs to add folks manually to the yep. I don't know what it is like a google group, but we want to move it to g suite, so we'll move all of the accounts to a yammer file and the kf dot.

E

Io repo paris sent me everything on slack and paris I'll take out the next steps on this and I'll create the pr.

C

And yeah that's about it, am I assigned on that issue.

C

Let me I need to grab the notes again. I am not, but.

A

If you need help.

C

Yeah, I think if you could assign both uh george and I that would be great.

E

I'll do that.

E

Here, like the pr hasn't been created, yet I just felt that yeah.

C

Sorry, no, I was thinking the the issue to create the pr.

E

Yeah, I was just gonna, go ahead and create it here. Okay, you mean oh.

F

E

Issue that's linked and the meeting notes.

A

C

A

C

Yeah, oh my god, I'm I complete sorry, my bad brain fart looked over it and.

A

Yeah, it's okay! Worse.

E

But yeah that's about it.

A

All right and last is gonna be paris. This is probably you contributor strategy.

F

Yeah, something that's not necessarily relevant to this group, but I'm going to plug selfishly anyway. It is it's a.

A

Same audience, kind of kind of.

F

It's kind of the same audience, but if y'all have other friends, family or co-workers that work on cncf projects, we formed this group called contributor strategy to help the toc with evaluating projects that are going through their project life cycle with contributor related matters. So we're talking about governance, um diversity of maintainers, et cetera, et cetera, all the above, and we're also helping out and being consultative with the projects as well, and then we're also going to be forming a maintainer circle and the maintainer circle is just a space where cncf maintainers can hang out.

F

That's really it, um but we're definitely looking for help. Looking for more folks to join us um and that's it.

A

All right cool all right. We have seven minutes left, but we can break early of course. Oh my god, I just will pop all over my desk um any any last items before we go just a reminder. Community meeting is tomorrow, so lori break a leg.

A

Everything is looking good thanks, good updates. um Anybody else have anything.

A

All right and with that we'll see everyone, hopefully tomorrow and if not next week, um thanks I'll give you uh six minutes back thanks. Everyone hi everybody.

C

A