Kubernetes SIG Docs, 19 Sep 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: [SIG Docs] Bi-Weekly Community Meeting for 20230919

Description

[SIG Docs] Bi-Weekly Community Meeting for 20230919

A

Hey folks, welcome to the Sig docs uh meeting today is September 19 2023. This is the bi-weekly uh Zoom meeting. We have for kubernetes I'm your host today I'm one of the co-chairs. My name is Ray lohano, a few things to go over before we start. uh We do this meeting abides by the CNF code of conduct, so that boils down to just be kind to everyone into respect. Everyone uh also, let me go share the agenda. I have the agenda in the chat as well, so we can review the agenda together.

A

uh So we like to start off with uh folks who are new to this meeting artistic docs. If you want to introduce yourself, uh feel free to go ahead and come up. Mutant I'll, give a few minutes here for for new folks to introduce themselves.

B

And hi, can you hear me? Yes, yes, uh I think I can introduce myself, I am Cairo, Valencia I think I know uh feel, um but right now, I am uh the communications lead thing in this release and yeah I think that will be my main introductions that anything that we need to think for. The next vlog feature release for this 29.

A

Yes, thank you Carol and welcome back and Carol is also been. The uh really stocks leads lead in the past as well. So thank you for all your work, uh all right. Anyone else that would like to introduce themselves.

B

uh Yeah I think I can help with that, because I I can see that the more of my Shadows that is also James and Christine and Abigail.

B

And I think they could say hi because he will work also with me in the release.

B

Christine hi yeah.

C

Hi, um just a reintroduction of I'm, the one of the calm Shadows for 1.29 and, of course I was the doc's lead on 1.25, so I'm really happy to be working with Carol again.

A

Welcome back nice to see you again.

D

Hi um I'm Abby, so not a new contributor to this meeting at all, but uh new in the role of being a release, calm Shadow, so I'm really excited to be part of the release. Team, um yeah, yeah.

A

Thank you, Abby Abby oscillates the uh localization sub-project as well. Also the upcoming uh doc Sprint that we'll talk about a little bit.

A

All right, thank you for all the uh 129 release team members uh I think it's about just a few weeks into the release, so I did see that shadow orientations are are occurring currently um so yeah. So please feel please update US during our bi-weekly meetings with how the release is progressing all right, any other new uh contributors. That would like to say hello.

A

All right, so we can move on um some updates and reminders. uh I am your PR Wrangler for the week so feel free to ping me on PRS uh shadowing me this week is uh I've.

E

A

Me for the pronunciation, but but ansh uh Roshan, and we did a one-on-one Zoom meeting yesterday to review uh just how I review PR's the role of the pr Wrangler um went over the style guide and content guide as well, uh and we also reviewed several PR's yesterday. So uh if there's any questions just feel free to ping me this week, next week's PR WR Wrangler is Taylor delizal uh or also no one's only Dole. uh Next and the following week is Tim Bannister, so SF Tim.

A

uh So that's uh two weeks from now there's a link to the pr Wrangler shift on the agenda as well. uh Lastly, last reminders: if you notice any uh code of chronic violation during any during a meeting or during uh GitHub up comments or slack as well, feel free to reach out to the kubernetes code of conduct committee.

A

Any questions before I go on to the agenda.

A

All right um going, let's start off with the release, 1.29 uh and uh the status I believe is from the docs team. um I know the docs leaders at open source Summit in Europe, so that's cat, but cat has uh updated the mention on slack that cat has updated the agenda uh so just reading off the agenda. Shadow on boarding schedule for tomorrow um we'll be scheduling the branch syncs as well and who will deliver the release, team and docs update as well, and the early docs release tasks are done.

A

I also will have two more videos up, so I've been creating videos on how to do specific, docs uh tasks for the release, and this is also including more more on the tasks that are more likely done by a kubernetes tech leader co-chair in Natalie Phi, so that uh the knowledge isn't just kept within a few people so that it's uh it is, uh it is saved and on YouTube for anyone to reference, so I will have two more I think I have about three or four videos up right now, so I'll have two more up by the end of this week.

E

I'm sorry never mind, I was just gonna say if you had links to those but I think that's what you've already done right, yeah.

A

So there's videos already done um I'll have a link to the playlist. Let me send the get the link to the playlist I'll put on the agenda as well, and you can just keep the use the same link to playlist and all the added all the new videos will be added to the same uh playlist. So I will. Let me see if I have that link, if not I will send it in the agenda. I send it a few times on the really stocks.

A

um Channel I should buy, save it in the description for the channel, uh just so that it is it's easy to find. But uh if.

F

A

I will update everyone shortly with that, with the link to the uh YouTube playlist.

A

All right, um one of the tasks- I'm gonna, do it's it's just creating it's with the new I'm, sorry with the release, Dash 128 branch, and um now we have auto, save uh Auto, protect mode or Auto feature for new branches. So I do want to note that there is um a branch that was created are tags that were created for that really stash 1.28, which is actually incorrect, so that should actually be made in December at the end of the 129 release. So I will go through uh the efforts to get that uh deleted.

A

So you, if you do, you will see that currently uh that release Dash 1.28 uh Branch was incorrectly made, uh so I will get I will I'll go through the efforts to get that deleted um right now, with the changes I I could not delete it myself. So I will go through I'll talk to the GitHub management team on how to delete that I'm, using that in my next video, so I'm, not deleting it now so on on how to uh on how to do some.

A

Now, if I put a point to the to the release, Dash 1.28 Branch, so any questions on that.

A

Yeah, so that was with the with our Auto protect feature, so any new Branch we created it's Auto protected, so uh it's just because it is. We do have that I I have to find out how to delete branches. Now, um okay, uh Carol, do you have any updates on the comp side or is it similar to the docs update as well.

B

Oh yeah I was with yeah. uh We've already did the shadow, uh the onboarding session for the comps, and we will divide it between us about to track all the features of the six. We are in this status that we will divide it to check our current blocks and I have one questions also.

B

That I was seeing the issue that we have for improve the checklist about uh release stocks and shadows that we open I, think is the 23 24 I can put it here that uh I I was checking that you have an, but maybe we could also include a little detail that how could? How could be the communications between Communications teams?

B

What will be the checklist that we can do in each B week list session that you have.

A

Yeah I saw that for the um docs release handbook uh side to have the checklist, but we could also do the same for the on the com site as well. um I know uh Mickey, who is uh working on that issue for the doc side has uh for that checklist for the release. Docs team has also been a comms lead as well, so I could always. I could also ask to have a a a similar issue for the comms uh Team. If there's not that once up already open, so we could uh work on that.

A

Is that the one they referring to or is it already I see the uh she already have.

B

A

So, on the dark side, since I've been at Doc's lead before uh one of the. uh So this is for the guidance or checklist to see to see if uh the status is green or red or yellow uh just a few of just some uh some just to summarize what I would check for is uh if the weekly Branch Sync has been done or if the integration branch is healthy. We used to report on that every week where the integration branch is either healthy or not.

A

uh Sometimes the the there's a merge conflict or you would need to rebase uh the integration branch, and so, in that case, I would consider that yellow or red depending on- and you know, uh probably red if it's if it, if it's needs rebase or there's a merge conflict.

A

um So that's there it'll be it'll it'll go in higher priority onto to fixing to get that integration Branch healthy. So those are a few items off the top of my head, depending on where you're at in the timeline as well. If it's uh x amount of days be before deadlines, that would also affect the red yellow green status as well.

A

If you have, um if it's on the docs uh last deadline for for let's say for docs, where dots docs are have to be complete, um if you have many PRS to open uh many PRS that need tech reviews, so those will be a red is as well and I. Don't know if we should add a a number to that, or maybe we should have a guide to that.

A

So we should have that added, in my opinion, to what should be kind of red, yellow or green, because uh for the uh what we're getting last release cycle. This is. This came from the really 128 release retrospective. Well, that we were getting a lot of green um uh statuses, so everyone, so we thought it was the the cycle was going well, but it turns out there was uh lots of things um behind the scenes that it may not have been green typically, so uh so things like Branch tanks have to be done. Weekly.

A

Make sure that the integration branch is is healthy, uh make sure there's uh the PR's being for the docs, for the release are being reviewed. uh Tech reviews are being done or, if they're not being done, that this Accord, that the corresponding Sig has to be notified and requested. So so those are some of the things and we could do something similar with the comms with the comp side as well.

A

um Pont side will be more in the feature box to make sure that there, if there's a tech review for the feature blog as well, um make sure there's a date that is scheduled um so that in the last release there was many. uh There are several blogs that were scheduled to cut on the actual release dates, but the actual release date. We we typically save that just for their release, blog and feature blogs, tend to go after the release date.

A

So so those are a few things off top of my head for their calm side is to have a schedule uh set up, make sure, there's uh tech reviews as well uh done or assigned, or the folks can be assigned to to do. Tech reviews for those blogs um also make sure as well. There's blog reviewers as well from the sigdoc side um and and a bigger one else, goes to to have the schedule worked out so that um we're not trying to schedule things very last minute.

B

Okay, uh I think I think your mute.

F

Yeah um just I hope this is obvious and I'm going to say it anyway, even though I hope it's obvious, if you're not sure what color to something, if you think something might be green or yellow, probably highlighted as yellow, because then we can discuss and say hey, it's actually green, it's much better to say, I'm, not sure it's yellow than to say it's not sure, it's green, because that and they're like I'll get screen, and then we find out uh two weeks before yeah.

F

So no, no, no problem in Coloring, it's a sort of worst color be cautious like that. Please.

A

Plus one uh because green would kind of might get ignored well,.

F

A

Will be looked at and red will be looked at. I'd rather have something marked as red than marked as uh green, and if there is any even a slight issue, if it's red I'd rather having white thread.

B

Yeah and one question that I have also that I noticed that is they mainly the blocks that will be published will be after the release. uh The communications things have has to help after the release. 29 is long to tracking this, or how could be this because it was like right now, I see a lot of blogs and I didn't I responsible from 20a or yeah. That thing please help us.

F

The happy path is that the blogs are all ready before release day and uh on release date. We we unfreeze the repo, we unhold, those blog articles because we've held them saying. Well, we don't know like maybe we'll cancel the release, maybe we'll postpone it for three months, but as soon as we know, the release is done. We unhole, you know 6 12 um PR's, and we and we and we sit back. We we pour one and we go. That's all great. The automation will publish on the right days.

F

This has never happened, but that is what we want to aim for.

A

That's a big plus one.

F

A

Think that if things are done on schedule- and you know in a timely manner that we do not have to do a lot of work after the release, that it'll be all it'll, be all done by the release day.

F

Now I would say for this release. We had a real split I think we had about five articles that did merge on release day that were ready to go. People were proactive, we had dates assigned, but we also had two articles that completely missed it. We had two people, two sigs that wanted to publish an article, and it was so much missed that those articles didn't get included. So a real spread, um I'd love to skew that and tighten it up so that it's all it's much more on the happy path.

F

um We're volunteers, it's okay, to make mistakes, it's okay, that things didn't go right um and that's fine, but what we'd love to do is to get to that that desired. State that, like it's all, happy and all the blogs are ready. The blogs were ready for review on the date they were due to be reviewed. There was enough review capacity to make it happen, didn't need any rework or anything and yeah. We I think it's believable.

F

There are bits of the release process that over the last few years, have gone from difficult for problematic to it. Just works, let's see if we can make this be one of them.

A

All right um any other questions.

A

I do also want to note I always say this on the last release of the calendar year that a lot of deadlines fall on around holidays.

A

So we understand that and um it's all with this release always tends to be pretty much like a week short of the other release Cycles as well. So we also understand that so uh yeah. So we understand that there's more difficulties with scheduling for the last release of the calendar year, so yeah, we'll work with with uh everyone on that.

A

That's not if there's no other questions or or about the 129 release, if there are any just feel free to Ping us also use a release. Dash coms, Channel and release Dash docs Channel as well. Also the the sick, docs channel, uh moving on I, don't see any issues in PRS um on the agenda, but are there any issues in PRS that or or PRS that folks want to bring up.

A

I do want to bring more on. um It was already merged, though, but there is, and I can't get to my. How do I hide this.

A

There is a new page under Concepts under concept security, a Harding guide for authentication mechanisms um that had that has merged, but there is discussion that we might have a different place or a different home for guides or good practices as well, so that uh that's that is it. It might be a temporary home right now, but we might have a place and there are. We certainly have a number of good practice guides.

A

uh I want to say best practice, guys, but Harding guys guys security, best practices as well, so they might have a new home uh in such. But that is the um place to order the home for now. I don't want to say temporary. But who knows um so? That's a new page I go to concept, slash security, slash hardening guide, Dash authentication mechanisms and the safe security docs.

A

There's a docs subject: sub project team under six security, uh they're working on other additional Pages for the for a hardening guide, so there'll be other Pages uttering under Harding guide.

A

All right, any other comments, questions on issues and PRS.

A

All right, I'm going to go to questions and discussion uh points I do like to highlight. uh We have open GitHub discussions, one on General of AI discussion, um one on localization, contribute uh contribution updates and when the issue Wrangler as well, I did link um the cncf uh staff member Roberts with I know.

A

The Ukrainian localization team is looking um at some uh translation uh mechanisms, so I did like Robert to the Ukrainian uh Ukrainian localization slack channel, on that uh we had a in-person discussion um at Google next about it so I, uh so he is working on that on the LF side or the Linux Foundation side.

A

um Other two good-up discussions on localization and issue Wrangler discussion issuing there's a new name role, because we have many many issues. We have a PR Wrangler uh to review many, the many of the PRS we have but issues 10 uh uh needs also be wrangled. So um so, if you're looking at ways to to help uh kind of help with contributions as well um initially, there is also an issue Wrangler role that will has been created. Any questions on those three uh GitHub discussions.

E

Ben has his hand up. Oh.

A

F

Good, um maybe we need a discussions. Wrangler the localizations one, four, two, four zero nine uh says from August the 6th. This discussion item will be open for a period of 14 days after which we'll be opening up an issue.

D

F

D

um Am a bit behind on on closing that and creating an issue. um I I think I forgot to actually hit save on a comment that I was going to add on that discussion, saying that I'm going to move it into an issue, but yes, I I, agree that one is that one's on me. uh I had a rough beginning of September with a lot of uh family illnesses, but uh we're back uh on track now, but I I, agree. I.

D

Definitely think uh that one in particular is my my bad and I I'm moving into an issue, hopefully this week, um but yeah I, agree.

A

All right and I know there's some work efforts um moving forward with the issue. Wrangler I have not look at the closely but I know that I did see some earlier, either last or late last night or earlier this morning.

A

Any other questions.

A

All right, a new one. uh The cfp is open for Keep Calm, Claude native con uh Europe and Paris. So put the link in the agenda. The cfp closes November, 24, I, believe or 26.. uh So it feels a little bit early this time, but maybe it's maybe it's around the same time as we've done before uh so I just want to have that out. There also I want to make a note at this year's kubecon in North, America and Chicago in November.

A

There will be a doc Sprint at the contributor Summit, um but Abby's name down here, as Abby is going to be uh helping out or leading that efforts, um and so that I put a link to the registration as well or the events page on the contributor. Summit um I will do have another obligation.

A

The company I work for has a zero day event at the same Hotel Site, so I'll be going back and forth so I, don't know how much I could participate in the doc Sprints, but I will pop up I will pop my head in once once in a while.

A

All right any other comments or questions or discussion uh topics that people want to bring up.

A

All right I will stop the recording.

A

I could find that aware.