Kubernetes SIG Docs, 27 Nov 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Sig Docs 20181127

Description

Meeting notes: https://docs.google.com/document/d/1Ds87eRiNZeXwRBEbFr6Z7ukjbTow5RQcNZLaSvWWQsE/

The Kubernetes special interest group for documentation (SIG Docs) meets weekly to discuss improving Kubernetes documentation. This video is the meeting for 27 November 2018.

https://github.com/kubernetes/website

Chat transcript:

19:06:25 From Yang Li : https://docs.google.com/document/d/1Ds87eRiNZeXwRBEbFr6Z7ukjbTow5RQcNZLaSvWWQsE/edit
19:09:19 From Zhang Qixiang : https://github.com/kubernetes/website/blob/master/OWNERS_ALIASES
19:10:36 From Zach Corleissen : https://github.com/kubernetes/website/blob/release-1.12/OWNERS_ALIASES
19:10:54 From rchen : cool, :+1
19:11:09 From Brad Topol : do they need us to merge those updates?
19:13:55 From Julia Han : https://github.com/k8smeetup/website-tasks/issues
19:14:21 From Julia Han : The zh translation task is in the above link now
19:20:45 From qiming : @bradtop and all, this is the PR I closed. https://github.com/kubernetes/website/pull/11101
19:22:21 From Brad Topol : @zach So the person in the closed PR was Wang Bing. Was this person at the Shanghai meeting?
19:22:36 From Julia Han : Wang Bing, we know him
19:22:56 From June Yi : https://gist.github.com/gochist/8654460717b4bbb4ac490dda79a547fa
19:23:24 From rchen : thanks, :+1
19:23:43 From Brad Topol : @qiming can you reopen the PR?
19:23:51 From qiming : Sure.
19:23:55 From Brad Topol : Thanks
19:24:17 From qiming : oh, looks like the branch has been deleted
19:24:24 From qiming : cannot reopen
19:25:10 From Brad Topol : @Julia can you ask Wang Bing to submit a new PR and assign me and I will approve it
19:25:26 From rchen : just quick question for the dec 3 release, going to be frozen sometime before that?
19:26:30 From Julia Han : @Brad sure, I will let him know
19:26:36 From Brad Topol : Thanks

A

Okay, all right, we should be live now. So this is the weekly meeting of kubernetes sig docs, and this is our monthly meeting for to make it easier for contributors from the asia-pacific region to join so welcome everyone.

A

Let us start with the agenda. So usually we begin by asking if there are new contributors, if there are folks joining this meeting for the first time. So if there are folks who are new, if you would please introduce yourself in the chat for this meeting, that would be wonderful, but Julia.

A

Would you like to introduce members of your team I.

B

Think we have some familiar teammate here. I thought she's down here and also Shalom, but I do see some new friends here. So maybe they can introduce themselves, they will do it yeah and the young yeah cuz, the other I. Remember he just joined out here. Maybe last week, wonderful.

B

Can you hear us no way? Do you mind if you introduce yourself to all the team here.

A

C

A

Good to see you again.

D

C

Networking stare continuously good.

A

A

B

He's in our clients place, so that's why he probably just joined at the audio, not video and.

A

The young hello, it was good to meet you in Shanghai yeah.

B

A

So good to see everyone yeah.

B

It looks like everybody's here, so maybe we can just um get started to the agenda. Let's.

A

Do so for PR Wrangler this week, I think Jennifer Rondo is well. Jennifer is the one who is scheduled to wrangle PRS, but we have swapped roles many times due to holidays, and things like that. So I that may be an open question. I have put out a son Jennifer a message to confirm whether or not she is the one who is wrangling PRS this week.

A

So if she confirms or if that information changes, we'll send a message to slack and let folks know but Jennifer I think is regulating pull requests this week.

A

Let's see any updates on 1.13 I, don't see Tim with us. I think that we are almost done. I think there was one outstanding call request for cube, ATM documentation for 1.3 tea, so hopefully, hopefully, all of the documentation, wrangling for the 1.13 release is finished and wrapped up.

A

Let's see so cube con cloud native con in seattle, is coming up quickly. Just in two weeks out of curiosity, I know it's very soon after after Q Khan in Shanghai, but there's anyone planning is anyone from East Asia planning to join us in Seattle in two weeks. I.

C

Probably too close.

C

Looking at some of my left, the tasks gotcha yeah well.

A

The invitation stands and hopefully, hopefully you'll- be able to join us. Maybe next year.

B

Unison is that the cube town shanghai will be coming back very soon in another six months: actory yeah. Yes, so it's really coming soon.

B

It's gonna be in june in 2019, so it's coming very soon.

B

A

All right so Roy I know that you had requested build / PR be turned on for released on 1.12. That should be enabled now. So if you, if you are not seeing mattify, builds her pull request for localization PRS to 1.12, please let me know, because that should be. That should be active. Now. Yeah.

C

This morning, I think he's working now: okay,.

A

Yeah, unfortunately, won't build for existing PRS, but if he's like, if you a new, commit to an existing PR, it should trigger it should trigger trigger a preview, build I.

C

Think I think we wasn't used to remove released one touch one for a trail from the the existing configuration, because this seems like the URL still pointing to the master stage until notified Appa I replies to your message.

C

A

But in general so have you had any difficulty being able to review and approve pull requests for 1.12.

B

Thank You general. We are doing pretty well yeah, yeah, okay,.

A

B

Encounter any problem, wonderful.

A

Yeah so I think that I think that all of the new membership requests following Shanghai coupon in Shanghai I, think those should all have gone through at this point so Julia, if you and your team would like to to update the list of reviewers and approvers for Chinese documentation in the owners file. Let me let me find out really quick and I'll drop, a link to it in chat.

A

Sorry I'm just trying to get to the chat window.

A

I, don't want to take too much time trying to figure out a chat and why I'm, having difficulty with it Brad. Do you mind finding or Steve, with one of you mind, grabbing a link to the owners, sub aliases file in a website and dropping that dropping a link to that in chat.

C

A

C

Put into The Witcher.

E

Okay looks like it's already in there.

A

Thank You Sean, so that is the that is the file to update with changes to reviewers and approvers for for Chinese review.

A

And if you update this file in master, make sure to update it in release 1.12 every branch that you're working on so like if you're, if you're working on 1.12, make sure to update the make sure to update this file in the release, align that 12 branch as well, because it's not the the review permissions are by branch, so it'll have to be you'll have to open two separate PRS one for master and one for release 1 by 12.

C

A

That make sense. Oh.

C

You mean the owners, that's cool, aliases per branch. Yes,.

A

C

A

There's this one, and so that's the link to the version and master and I mean.

A

And you'll have to update this one as well. The same file I mean you can copy and paste really. You just have to open a separate pull request, because it's on a different branch.

A

A

So, let's see, let's go back to the agenda.

A

I noticed that we've got so I'd like to get localization updates from the various teams.

A

So Julia, would you like to give an.

B

Update on how long on that part, basically yeah, because we talked about the kind of architecture change during cube count- and we talked about like to switch the task load from the Google Doc to github issues. And for that part, we've already finished on that which is really really helpful and good.

B

So that's the first thing. The other thing is the net nathie. We just talked about the preview of the release, 1.12 that I think we've already done got to ya, and the third part is the multi version. Support is already active now.

A

B

Yeah, so that's the major stuff that we've finished and completed after the Shanghai. Okay.

D

A

So glad to hear it yeah.

B

Like resti issues, for example, how to make the translation team more active to faster to cycle up the translation, but that's we talked about that to within a team. That's something we need you like to figure out more internally.

B

A

Brad so I see Brad has a question do do localization teams need us to merge those updates? No that's the beautiful thing about having updates to that owners. Sebelius's file is that localization teams can review and approve their own PRS.

E

And I remember: there was a bootstrapping issue where they were at the top level or something and certain files were at the top level. Yes,.

A

Oh, that's a good point, so yes, unfortunately, so for the for the pull requests to update the reviewers, the Chinese, reviewers and approvers those pull requests we will have to approve because they are in the top level of the repository and they specify not just Chinese approvers but also like English and other localization teams as well. So that means that one of the one of the one of the maintainer x' will have to approve it as well. But you can open the PRS.

A

We just need to you'll need to get a review from outside the team for the actual to get them merged.

A

B

Switch to github to host order translation task.

A

Do you have there? Is there anyone who still needs to have a membership request approved.

F

There's a there will be our members request from our Korean team. Okay, do you have do have a link to the poll requests to you? We didn't make the prettiest two yet, ah but I really don't attend soon. Okay,.

A

If you need a sponsor for whatever reason, I'm happy to help but I think you couldn't I think between you and Claudia I think that you can probably sponsor sponsor members on your own. At this point, I'm.

E

Happy to help as well, if needed, thank.

F

G

A

G

Jimmy we're gonna be of member requests. I closed the pr last week, because you know I was the pr regular. During the past week, I saw critic contributions for Chinese education. This the team is a very, very odd field, but in that PR I saw a name. I never saw before the person has never submitted any.

G

A

Oh no I think cheating. You froze right.

E

So III didn't notice. He he closed the PR, but I think it was one of the people we were trying to get in which makes.

G

The game put the conversion to the pier was.

E

The name of the person do we have the link to the PR. You close, because I thought it was one of the people we had plus one via email, uh-huh.

G

Okay, I got offended Inc, okay, okay,.

A

I think your caution was warranted to me. I think that was probably like the I think your decision made sense, but that was someone who had attended coop con Shanghai and we wanted to. We were adding the reviewer based on a discussion that happened at the convention and, of course, that wasn't apparent through any like github mechanism, so I think you did I think it made the right choice and I think that we do still want to add the person as a reviewer.

G

Okay, just for clarification, so people doesn't have to be listed in own an ad file to leave. Look good to me comment right. You can still do rebuild.

A

Yes, that is true. Anyone who's a kubernetes organization member, can review of any pull request, so I think the I guess that's a good question Julia. So for the Oh, the owners and owners underscore aliases file.

A

The reviewers section specifically is for people it. It specifies a list of people who are automatically assigned as reviewers to pull requests so well. Anyone can review any pull requests that reviewers block in that file is specifically like, like a randomized pool of people who are always assigned to Chinese pull requests. So that's like people, don't need to be in that file in order to review it's just if you want make sure that someone from that pool is always assigned to a poor request for a review. That's the the reason to add them.

A

So just something to keep in mind. Achieving is absolutely right.

A

Any further updates from from you, Julia I,.

B

Think, that's all that I have actually okay yeah, but I was wondering if she me was trying to say something else other than the the request you closed. Is there anything else that we need to keep keep in mind or keep an eye on.

G

Also, how the trade association team has been working very while I mean it very good. I.

B

Saw it was smiling any comment on that.

C

Merchant appears, as.

C

Well, that's very good! Thank you. Thank you. Thank you.

D

A

Is awesome, so thank you very much for your help, reviews and approval.

A

All right: let's move on jr. and Claudia. How is the Korean localization going.

F

Update we had called me the rest week. We introduced our documentation, localization good actor Bureau and we get another members to translate the Korean documentation.

F

F

We are edgy, as you guys know, we are working on the table, one certain branchy, so we coordinate with our team to.

F

Which releases cancer so we're gonna make our final. Our final protocol 240 Deborah, one surgeon. We put the December Sun.

F

And put the deb 113 branch or we are going to update about ten pages and translation.

F

A

A

Junyi, I know that you had that you had a code snippet that you were using to to compare dips, but we know genes and I. Remember at one point you sharing that that code snippet. Would you would you mind providing a link to that again just for reference.

F

Sure I showed the link in the chat window.

F

Okay, great, thank you.

A

Claudia any any updates anything you want to add.

A

A

A

That is the end of the agenda that I have so for localization. Is there anything that is there anything that folks are having difficulty with anything that we can do to support you.

A

Well, that's great! No! No! No support needed perfect! You.

B

Know I was muted, I was trying to say it I. He was the guy we st. Matt's, you know oh I'm,.

D

B

A

Great, oh thank you Jeannie for posting that code snippet. So this is this is the the tool that you use to diff between branches.

A

Is that right? Yes, right, okay, cool yeah, I recommend so really I know that this is. This might be of interest to you, in particular, based on our discussion about how to how to make sure that differences between branches are obvious.

A

Okay, let's let actually, let's go back earlier. Tim I see that you have joined us now. I I was 1.13 going yeah.

H

Sorry, for joining a little bit late, there, everybody I'm, Tim I, don't think I've been on this particular call before it's nice to put faces to names so yeah I'm running the doctor, the 1.13 release, so the the release is going to be happening on December 3rd and early we've been trying to get all the english docs PRS closed by today and the still I think several open.

H

So we've got 13 open still, but there's a lot of activity on them, so hopefully they'll all be closed soon. I think in particular, if there's anything that anybody would like to get in to the 1.13 release for localization.

H

Let me know- and and and hopefully we can try and get that in and was any other way. I can help out with the wound up their chain released for people. um You know, please, please let me know or if anybody has any questions on apologies- a little bit late, because it's happening on December 3rd yeah, all.

A

Right, thank you for the updates. All right. We have plenty of time left for anything that folks want to discuss. Is there anything that folks would like to add to the agenda.

A

You Steve, you look very thoughtful. Is that these the thought of an agenda edition coming.

I

No, it isn't I've been so out of touch lately that I, just I see everything's moving along nicely yeah, that's about my sense of it: okay, yeah, I I, don't think of anything! I have to add right now, perfect.

A

So Roy's asking is there a quick for the December 3rd release, what his code freeze or when is Doc's freeze for the December 3rd release.

H

So Doc's fries really started today. Actually so we're not you know, we tried to get everything in by today, but unfortunately you know it's run over a little bit. So if you're really do need to get something in, it's still possible to get something in. If needs be.

A

So what I hear you saying Tim is that, unless there's something that's already open and just barely pending, merge that really folks shouldn't open things that.

H

Don't I wouldn't start anything new, exactly yeah.

A

Okay, Brad and Julia I see you asking about a new PR for one being perfect. Thank you, okay. Cody! uh Do you want to tuck in and pour Cody got the deer? The headlights look do. Do you want to talk a little bit about I know that you and Andrew have talked a little bit about the the set up bucket of content from last week. Do you want to talk a little bit about that and just like what that's looking like in the next few weeks.

J

J

Okay, sorry Andrew hasn't hasn't, come back from Shanghai yet, but basically is just gonna, be the smaller fracturing like the categories already set, and it's effectively just rebranding, slash cutting down of sections to make it more user friendly and like just kind of easier to navigate. So there's not too much here to report and yeah, we'll bring it up to the cig before we push any changes but yeah. Since everyone agreed on the different categories last week, I think that's the rut. We're gonna go okay, cool.

A

Please let me know if you need any help or if you want review or feedback on that work, I'm happy to help out with it. I know that I know that many folks would be so.

A

Thank you for taking it on and looking forward to the results.

A

Other things to add to the agenda.

A

All right well.

A

In that case, let's finish up early I want to say thank you to everyone that was wonderful to meet you and look look forward to continuing to work together.

A

All right thanks, everyone.