Kubernetes SIG Contributor Experience, 23 Sep 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: ContribEx: APAC Topics Biweekly Meeting for 20200923

Description

ContribEx: APAC Topics Biweekly Meeting for 20200923

A

Cool. Thank you.

A

uh I think recording is on uh so yeah.

B

A

uh Today is september 24th effect by weekly meeting. uh First and foremost, uh this meeting is bound by the community score of conduct, and please be mindful of what you say in this meeting, because this is being recorded and will be posted on youtube uh viewable to the public.

A

uh So with that said and done, uh I want everyone to put in your name in the attendees list and uh and we it would be really helpful if I can have a uh not taker for this meeting thanks. uh So first business is: uh is there any new contributor in this meeting right now? Can they introduce themselves.

C

uh Hey hi, I'm marvin and uh I I used to join this meeting several months ago, but due to work I was not able to join but then now I want to. I look forward to attend more of these meetings, uh but I'm not a new contributor or something yeah.

A

D

A

um Cool, uh so I think we have a pretty light agenda today, uh thanks for uh getting the tweet out about the meeting, it was really great. We will have more visibility now.

D

Yeah- let's, let's hope so uh there.

C

D

uh But I guess it would correct it.

A

Yeah yeah yeah, that's fine, but it was corrected. um So I think uh right now our focus is on the meet our contributors, blog series that we've been talking on for some months now. uh So the last meeting we found an agenda of actually milestone and time boxing things, uh so I saw that there was already an issue created by yang uh about the whole document and tracking uh this very meteor contributors thing that we are doing uh so.

A

I just wanted to discuss uh the timeline uh before even going ahead and putting the thoughts in that issue. So I found out that there are three major milestones that we need to take care of. One is collection of responses. The second is, after you get all the responses. We want to collate the responses and then write the blogs or structure out the blogs at least, and then once we have the blog structured out, we have to publish them.

A

So I was thinking about collection, let's say two weeks so until the next bi-weekly meeting and then possibly milestone that in between the bike meetings, so that this also becomes like a cadence for us, and I believe it's like a comfortable junction like one week, maybe do less for people to respond back to one with maybe two, because people have different bandwidths.

A

So what do you all think about this?.

D

Oh just uh one thing: collection of responses from everybody, or I mean whoever you want to reach out.

A

uh The people who have been like highlighted in that list, so we have the region specific.

B

A

B

A

D

That makes sense to me.

B

A

Thoughts questions concerns.

A

B

A

I assume, like everyone, is okay with that I'll just uh jot down the thoughts in that uh issue itself, uh thanks for pasting it on the meeting doc. Whoever did that, uh so we don't have anything else on the agenda, um so we usually don't have an open discussion point, but please feel free uh to put in your points and discuss. uh Let's say we will wait for two three more minutes and then, if there are no agenda items, we can end the meeting and give back 20 minutes of everyone's day.

C

So uh I I have a question like: uh when are we planning to do this? uh You know the timeline. Are we are we looking to do it in a specific time for this block series.

A

um So we really don't have a deadline to it. We are right now trying to figure out the milestones by basically we're trying to figure out the deadline by match turning the tasks.

A

So once we at least get the data in and have a structure to the blocks, then we can have a deadline for possibly we will publish more than one blocks, because we have responses from many people and we want to collate all the thoughts that people have regarding contribution.

C

A

Thanks thanks for the question that was really.

A

D

D

Okay, uh just just because we don't have any other topic, I just want to float around the idea for uh hacktoberfest as well: uh full disclosure, I work with digitalocean right and they managed to buffer. So I just wanted to know communities thoughts as well. I know uh sam. uh We are doing the community repo and uh navarro negative speaking at the event, but uh do you think we can do something more, at least from the apec point of view.

C

Yeah I'm trying uh so that our event is listed now, so I'm trying to have the word out. I have some tweets uh lined up and uh some contributors are already there who are creating the prs and uh optito also is happy to provide the platform so that people can. You know.

E

C

The challenges solved so ramiro itself himself is creating around 12 to 15 challenges.

C

I am creating and you are creating, so we'll be having good amount of challenges before october and though we'll be keep on continuing and uh but having few challenges will be good so that other people can start contributing as soon as they uh see the repo, and I think it will be fun so uh something different but it'll be fun.

D

Right- and I was thinking probably we can do something for you know kubernetes and apex kind of a thing, but I don't know I mean uh the thing with kubernetes is I mean hacktoberfest is mostly aimed at you know, getting started uh with open source and would be. ha Would we have enough issues within kubernetes that that would be good for newcomers right? I don't think they would remain even if they are like they won't remain for too long.

D

That might be a blocker.

A

Yeah so uh like on that point, that's like a really great point. uh I saw it's some places that people were thinking about putting hacktoberfest labels on the kubernetes uh broad arc issues, but I think the consensus was that usually they are like very few and they're taken very early yeah. So unless we create something, uh I think there will be very like big dearth of things. The other thing that we can do. I was thinking uh since you mentioned a pack right.

A

We can send out a tweet from the contributor account that hey uh epic folks, if you want people, would be uh hanging around in the epic specific country, dev channels, uh for example, in-depth. There may be other deaf channels too they'll be hanging around. You can just come in and ask uh questions if you have any doubts regarding kubernetes upstream. That can be an engagement scenario.

A

uh Just thinking of thinking about it allowed here.

D

Yeah yeah, I mean that sounds good. You can do that we can we can.

D

But again I mean that has to be some some action item related to that, like the the problem with kubernetes.

E

D

You won't find that many issues that you can just take a look and start working on that right. It needs a lot of preparation and to understand how exactly that could be written.

A

Yeah that that's one thing.

A

So I have been trying to figure out something on the python client, where things are a bit trivial uh on some issues that people can like. New contributors can really take up because uh clients function in a biphasic way like there is a base, repo which has a specific language language, specific stuff, and then there is the client root repo which is basically generated from the upstream. So there are, there is scope of like new contributor engagement there, but then I'm trying, uh we still don't have anything figured out on that front.

A

I'm going to discuss it in the next meeting got it.

A

uh Also uh one shout out, uh so we have an upstream event uh coming up tomorrow uh evening: 8 30 ist, uh it's like 3 utc, uh so the kubernetes release webinar, so every release cycle. We have a webinar of talking about the features, so there I taylor and max would be going through a overview of the release and the enhancements which were pushed out in the release do attend that. I posted the link on the meeting notes.

D

Awesome yeah. That would be great. Thank you.

C

So uh one question number one is like these meetings at uh the release meeting or the announcement is shared by the k8s handle the main handle.

A

uh I'm sorry uh I did not did that.

C

So I was just asking so uh the meeting that you told about which walks through the release, changes etc. Is it uh announced, or you know or through the kubernetes twitter handle the main handle.

A

um I think they are done. uh I don't know if there was a tweet already done, uh but I would try to get another tweet if it was uh not really prominent.

C

A

C

A

C

Yeah the reason for uh this question is like I see some some people uh in the community. Maybe uh uh you know like I, I see sometimes uh about the release like 1.18 and the meeting etc. I followed that, but I have never seen the meeting live happening uh in. Maybe it was happening and I don't know properly, even though being in the community. So I was thinking that, where is the right place, you know as a outside in look so to one to understand. Probably that would be an improvement.

A

Oh okay, I think I got your question a bit wrong. I think you're talking about the recurring release team meeting. Is it uh the weekly meeting that we have for the release cycle.

F

A

Okay, so I think for that you can join the sigrid's mailing list and ping on uh sig release slack channel, so, if you're being there and if you are not invited to the meeting, if you want to join the meeting, anyone is welcome to join the meeting. You can just ask anyone for an invite and you will get the invite okay, okay, okay or it should be on the sick release calendar. Although I have to confirm that, but it is open, you can anytime come in uh for indian time zones.

A

uh It happens at 10, 30 p.m. On monday, every monday yeah.

C

Some time back, maybe I joined it anyway, I'll I'll look into it. Thank you so much.

A

Yeah also, we are trying to uh create an epic specific meeting uh because we have people from eu epec on the team. There are 11 folks uh that we want to get a good uh meeting time for them, uh not for if, like not, everyone would be comfortable joining at like 10 30 during the night, so we're trying to do some kind of stuff. Regarding that.

C

Yeah, maybe we could do alternative uh time zones like once in eu us and then once in eu kind of thing.

A

Yeah better, yet I think we will do both meetings every week as of now. I think that's the.

A

A

Cool, uh I think we don't have any more points. Shall we call it a day, then.

A

Going once twice.

F

uh Just one point uh for the for the blog posts or any other um important um issue, we are tracking. uh I suggest that we uh collaborate on slack uh after this meeting.

A

Great idea, yes, I also agree with that. Thanks ann for the suggestion sure.

A

So, let's end the meeting uh thanks everyone for joining in uh for giving your time to this meeting and discussing their back topics. Thank you. Everyone again uh good, uh like have a nice day or evening, depending on your time zone, bye. Everyone.

F

D

See you in two weeks, bye.

F

Have a nice day.