Kubernetes SIG Docs, 27 Sep 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: [SIG Docs] Monthly APAC Community Meeting for 20230927

Description

[SIG Docs] Monthly APAC Community Meeting for 20230927

A

A

This is the APAC friendly version of the kubernetes fake talks meeting and um typically folks from the Asian side of the world um and the Asia pack ANZ side of the world join in on this. uh The though the others are welcome too. uh So in this meeting we speak about um various issues, PR's related to um sick dogs or if there are any release or deliverables that are being blocked by um sick dogs, approvals, reviewers or Etc, uh but before I go ahead.

A

um I want to sort of um um you know announce that this is under the kubernetes code of conduct. uh Every meeting, every interaction that you have here and on slack and on GitHub, is governed by uh the code of conduct as laid down um in the kubernetes repository, and uh it basically boils down to uh be excellent to one another and refrain from the usage of any harmful or abusive language.

A

So, um if you see any instance of um that, uh please, you know uh feel free uh to file a report um uh with the kubernetes code of conduct. Committee.

A

um I shall just sort of uh paste the agenda documentation here so that you all can um have the link to what I'm gonna share right now. Also, all the people who are attending the call um and haven't contributed thus far. um You all can enter your name under the new contributors section for the current um meeting.

A

um I do see a few familiar faces, so um I, don't think anyone's brand new here, but nevertheless um yeah. That's uh that's like the PSA before we start the meeting.

A

uh So that being said, I'm gonna share the agenda documentation uh for the meeting and uh if we fairly fairly light on the agenda, uh not much to actually, you know go through.

A

um As always, we will be going through the updates or reminders for this um week, which uh basically, you know, uh serves as uh an FYI for those who are new. uh We have um uh you know formal, approvers and reviewers within C, uh within six docs, taking on the responsibility of approving and reviewing PR's, um and uh we termed the term them as PR Wranglers.

A

uh These are week-long shifts taken on by the formal, approvers and reviewers today, uh not today this week, um especially um uh we have not especially, but this week we have Taylor um and uh who's the pr Wrangler who will be looking after all the approvals and reviews for the PRS um that are there. Currently.

A

uh This does not mean that another reviewer or approval can't step in, but um the this person will be your primary point of contact UM to reach out to um and we'd request that, instead of publicly dming I mean sorry privately dming them.

A

You publicly actually ask for an approval or review on the channels that it gives other folks also the opportunity um to sort of share the load with the pr Wrangler because, as you all might have seen, we have quite a few PRS um in our repository and the workload can get a little bit intimidating.

A

um But we also have uh FICA Ansari, who is shadowing uh Taylor this time around and uh what a PR Wrangler Shadow essentially does is learn the ropes on the job um of how to you know, Wrangle PR's, and what are the integrities of approving and reviewing a PR? What should we, you know, look out for when you're um you know reviewing a PR uh from a dog's perspective and from a technical perspective.

A

So FICA is a shadowing Taylor this time around um next week's PR WR Wrangler is Tim um and for uh the week after that, coming is um the pr angler. Now, uh if you want to be a shadow like FICA, um you just need to let um myself or one of the other uh tech leads or the co-chairs know that uh you know you want to become a PR Wrangler um Shadow and we would be happy to approve you.

A

uh What this entails is working alongside the pr Wrangler for the week and learning from them how uh the whole process works, uh but I'm gonna stop there for a bit and see if anybody has any questions around what I spoke so far,.

A

All right, um if you all have any questions and if you're not able to you, know um unmute yourself uh for any reason whatsoever. Please make sure you enter them on the chat. I'll try getting to them towards the end of the meeting, all right, um so that's the basic sanity check, slash health check that we go through um with respect to updates and reminders every meeting.

A

uh The second um part is that of the agenda. Now, since uh really, uh as you all know, release 1.29 is RW and I. Believe SRI Ram is on the uh you know, release team um this time around and um uh there are various verticals. So we seek updates from the docks and the comms verticals, uh since this is an APAC friendly meeting and typically people um who are in the release team are based out of the Americas and EU.

A

uh We currently don't have any update, but um we've requested them to post their updates a sink on the dock. After uh the meeting it gets done because obviously they're not able to actually stay up for this. So um that's uh that's one of the updates that we seek out.

A

um You know during the release cycle um and uh if there are any blockers in terms of uh you know, approvals or reviews, we sort of um can get our efforts uh to that and get it expedited if necessary.

A

So we don't have the status right now, but uh we should have it by EOD if us um so yeah. uh The next one is issues in PR some, since uh nobody has entered any issues or PR's currently under the section um that need any attention- or you know you all- have any questions about I'm gonna assume that there are none but I. All so would like to take a pause to see.

A

If um you know there are any issues specifically that are, uh you know, requiring attention from like the tech lead or chair, or you know, from an approval perspective or from a review perspective.

A

um You all can either you know unmute yourself and speak or you all can. You know enter it on the chat and I can read that out as well. So I'll pause for a bit here. uh Please flag your issues or PRS. If any.

A

uh So anach had a question about the pr Wrangler Shadow program, which we uh spoke about previously and I'm gonna. um Answer that the question was: is there any eligibility to become um to Shadow a PR WR Wrangler? So no there is. No, um you know eligibility criteria as such the shadowing process is basically you trying to learn how the whole uh approval and review process works within.

A

um You know sick talks, uh so if that is something of interest, um please let any of the tech leads, orge or coaches know by posting on the channel, and we shall get you added as a shadow.

A

um So this is on a weekly basis, so you'll be tagging alongside uh the weeks PR Wrangler to learn more about the process. um Hopefully that answered your question or not.

A

Okay, um if there are any, um you know further concerns, you can enter them on the chat and I'll get to them or you can unmute yourself and speak, uh but uh since there have been no questions or concerns coming in other than the one I just spoke about I'm gonna move on to the next agenda item, which is uh discussion, points or questions uh that you know we probably might not have gotten to um earlier on.

A

So the first uh thing is: uh we are looking at and cooperating generative AI, or at least there has been a suggestion from uh Lennox Foundation to see if uh generative AI is a feasible.

A

um You know thing to incorporate within the dogs in an attempt to make it uh more accessible and more user friendly, and um uh you know for better user experience in Angel. uh So if you haven't had the chance to go through the discussion um item, yet it's up on, you know GitHub on this link. That is there on the agenda.

A

um So please, you know if you have any specific um things that you want, um or you know specific things that you want to convey. Or you know you have these suggestions or opinion uh about generative AI. Being incorporated into the kubernetes talks- or you know, you have some solutions that you want to suggest.

A

uh Please feel free to chime in on that, um it's open uh to everyone to comment, uh so you do not need to worry that you do not you're not eligible, or you know you need a specific amount of privilege to do that. Anybody is welcome to contribute to that discussion. So that's the first one and uh the second one is uh localization contribution, update I'm, just gonna scroll down um all right. So uh this one is also closed, um but we have.

A

um uh The whole thing was that we are. uh We were looking to update the contribution, uh not contribution localization docs in the contribution guide, and um uh we wanted to sort of see, consensus um and understand if there were any more items um within the dock that needed an update. um There were a few things that we could think of from our experience uh from the top of our head. So uh this is basically um these are the things that were discussed and um we are moving the work into an issue.

A

um Four three one. One six uh I will link that here as well, so y'all can go through that um and see if this is something that you all want to actually uh pick up, because this is basically improving the content um around localization contributions and you'll probably have to work alongside um Abby and a bunch of others who are already.

A

um You know taking initiative on this because it's a huge piece of work. So this is something that, if it's not a good first issue, I can definitely uh not recommend this to a new contributor. But if this is something that you're already sort of the air insect dogs and you're, aware of what needs to be done, you all can like tag team with uh another experienced contributor, and uh you know contribute to this uh issue. So this is just gonna issue.

A

Right, so, if there is, um you know any sort of require, uh if there's any sort of um you know up uh suggestion that you have around how we could better improve our documentation around localization contributions. Please uh feel free to suggest that as well over and about what Abby has mentioned um so I'm going to take a pause here again uh so that you know I I want to let it uh sink in and see. If you all have any thoughts about this or if you all have any questions or something like that.

B

Yeah, so, uh regarding the generative discussion, uh you know: I came across a peer uh which was a POC of using generative AI to write documentation like I, actually I think it is I, think the localized version uh and uh the author has used gpt4 to translate the English text to Spanish and this particular pair. One thing that I found interesting was the question regarding CLA was unclear and Tim had commented that we are still unclear uh how the CLA needs to be set up when the content.

A

B

A

Yeah, because contributor license agreement essentially boils down to the fact that uh you know a contributor is the person who's? Actually um writing the contributing to the repository or writing the content? That's there in the repository. So essentially uh that is um it's not a bone of contention really, but it is a matter around which we have had several discussions, um not just from the perspective of chat GPT but uh or any other AI.

A

um You know uh tool, but in general uh you cannot just have machine translations um copied and pasted, because um AI or even your Google Translate can throughout other rubbish, sometimes and my not be comprehensible to a user. So you need to sort of um look at it as a reader or as a consumer of the documentation and uh see. If that is actually the right one um I don't think uh I mean I am not uh dissing the whole Trend, but I.

A

Don't think uh models are just as intelligent enough to start writing documentation on their own. They can probably be a supplementary sort of a tool, uh but I don't think we're there yet with respect to something being written all by itself, which is sort of what we're trying to uh do here um and LF is uh LF, as in Linux. Foundation is sort of um happy to chip in with any help that we require um for tooling from very specific vendors.

A

um So that is the um that is the tldr um but I completely I.

A

Think I've I've had this discussion in different forums um about you, know, translation and how it is not uh possible for just Google, translate or just a tool to be integrated and write the whole documentation, but maybe, as like a supplementary sort of a thing, you could use it, uh but uh if there are any other like if, if this is an opinion, you feel strongly about I'd recommend you sort of put it in here and I think it's already linking to it. But um you you, you can feel free to put it in here.

B

Yep yeah I guess I'll go through the entire discussion first and then this is.

A

All right, sorry about that um Okay, so um yeah so other than that uh uh are. Are there any thoughts? Anybody else has around generative AI for uh kubernetes documentation or about the other uh localization contribution thing that we were just discussing.

C

A

C

Hi I'm gaurav I'm, just I'm sort of new to the sick dogs thing and it has been. It has been a month since I'm cultivating but I have been uh I've been meeting, so many good people. So far so around this generative AI uh thing, I I, think uh in the beginning we can. uh We can sort of implement this as a workaround of dogs.

C

uh If I can post an example of IV, uh there's a website called Ivy and they just use the generative air to uh as a roadmap to your Docs. If that sounds uh any insightful.

A

I would I would recommend that you chime in on that discussion like I um uh the discussion item that is there on the agenda documentation right like just me. Just let me post the link again.

A

um I would recommend that you post uh the discussion item like this as a discussion reply to the discussion item uh for generative AI, so that um others are also aware because, uh as uh as there are only four people on the call, we never make consensus over calls um and that's why I'd recommend that you know you have that out, like um your opinion uh and no opinion is uh foolish stupid or whatever, like I, used to think that when I joined that oh, it is uh dumb of me to have an opinion her.

A

But it's not uh so please do not. You know, feel scared or intimidated to actually post your opinion there, um and um you know uh you can provide the example that you were talking about and say that this is what is the suggestion that you are trying to put forth and from there onwards we can sort of have like a discussion around that publicly. Instead of just ask for you know discussing amongst ourselves like we're in some school school group or.

C

Something thank you so much yeah.

A

No, not a problem at all. Thank you for bringing it up um anything else. Folks, before we move on to the next topic,.

B

A

From myself, okay, cool uh yeah, so the next one is that um this is I mean there's already, probably you are aware, but the cfp for uh cubecon, you 2024, uh that's gonna, be held in Paris. It's not now open. So if there are any, uh uh you know, talk ideas that you have please uh put for those now, um and you know you may never know you might get selected.

A

So the link is there on the docs here um or the agenda talk here, sorry and um in the same bin, um at the upcoming kubecon, which is to be held in Chicago in November. uh We have a contributor Summit for all kubernetes contributors and um add that contributor Summit. uh We have a doc Sprint.

A

um So unfortunately, we have not extended it to a virtual platform yet um uh and it's in person. But if there is an interest in um uh you know the in-person doc Sprint and if any of you all are actually attending, uh please uh you know feel free to register.

A

um This will also um mean that you've already registered for keep Khan any so that Amendment will be made, and this registration is also pending approval uh from uh the contributor Summit team.

A

uh So those are the updates that I have. Are there any questions around these two points? Please.

A

Okay, great, um are there any other questions or discussion points or any issues or PRS that you all want to bring up before we close the call um I um I mean I, want to open the discussion up to everyone on the call to you know, sort of bring up anything that they might want to actually add to the agenda, documentation or speak um with respect to contribution to kubernetes talks, or you know any of the issues or PR's that y'all are working on.

B

Can I know what we think what is happening.

A

Yeah sure so uh the document there are a few nits in the documentation that were that was proposed by Harry Priya, um more or less. It looks pretty okay to me uh once that documentation is in place, we will be sending out a call um phenominations on the Google group. So please make sure uh that you have joined our mailing list um and once we send out a call for nominations, we uh expect that to run for around maybe 15 to 20 days, and then you know we will be selecting the issue rank loss.

A

um There are also potential plans to sort of have a shadow program, but that's again in like the distant future, not immediately but um yeah. That's that's the update that I have for you. We've finished reviewing the docs more or less. It looks good. We just have a few units that we want haripria to address and once that's done, we will merge the dock and issue. A call for nominations.

A

Did that sort of make sense and.

B

Did I ask you a question: okay,.

A

Any other questions- beers issues, okay, I, see a chart item.

A

um So contribute to Summit sessions will be available on YouTube no as far as I know, um but I can ask if that is something that we plan to do, maybe starting next. So this is just very specific to kubernetes contributors. uh So we have a variety of unconference sessions wherein you know all the respective uh sex breakout into their own uh sort of uh unconference uh sessions. And you know we talk about the major issues in PRS that we're targeting and the goals that we have for our sake.

A

And then we move on to like these uh talks that we have, for which you know again. Cfps are open and uh last but not the least. We have like uh things like Doc Sprint and uh where you know, contributors can actually be onboarded um and uh we plan to sort of like do a live. um You know contribution thing at the dock stream, so yeah. It's not recorded, unfortunately, because of like the breadth and scope with respect to recording uh so I'm. Sorry about that.

A

But it's something we can probably look at um I mean we can suggest it, but I don't know if there is something that's possible in that case, because there are multiple unconference sessions going on at the same time. So I don't think it's possible, but we can definitely suggest it for the next contributor Summit. uh Did that answer your question or not.

A

A

A

That's answered um any other questions. I'll just write this down here so that I don't forget.

C

uh Divya I had a question uh so regarding the pr angler uh should I message. My uh Wrangler of the week on kubernetes, like.

A

No, no, so uh you want to become a shadow or are you looking at? uh You know for a very particular uh approval on a set of PRS. What is it that you're looking out, for that is what I'm trying to understand yeah.

C

I'm looking out for becoming a shadow, PR Angler.

A

Okay, so when you want to become a shadow or even if you want approvals, what I'd recommend is that you post it on the sick, docs channel, uh one of the tech leads or the coaches will take a look at it and confirm it on the thread itself that um you have been added, um so you can go through the list of PR Wranglers I believe the list is also there on the agenda documentation and um you can sort of go through that and figure out uh which, who you want to shadow, um and uh you know, specify who specify that on the sick, dog slack channel.

A

Does that make sense.

C

A

A

A

Okay, so if there's nothing else, I think uh you know we can plant this call for today and I'll give you back 30 minutes of your time um so yeah. If there's anything, please feel free to voice out on the sick talks Channel and we'll take a look for you um other than that I hope to see you around in the sick talks and the kubernetes slack channels, other kubernetes slack channels and hope you have a nice day, bye. Folks.

C

Bye. Thank you. Bye.

B

Thank you. Thank you.