 Okay, welcome everyone. This is the Jenkins documentation office hours for the 24th of August. We excuse Jonathan Marise he's got work that needs to keep him occupied in Brazil where he's based. We excuse make McRoberts she's got other things going on that need to keep her unavailable. Great to have Markey Jackson here we'll go ahead and let's look at the agenda. I'll start sharing my screen and off we go. Okay. So, Markey if there are any topics you want to add I like to go through the topics on the agenda first and then we'll actually start working through them. Yeah, no I don't have anything to add other than maybe some pieces here. Okay. So, first topic will be the doc sig meeting that schedules for this Friday. Second topic is actually going to be three topics, the Jenkins 2.249.1 release candidate that will be coming is expected out this Wednesday. Then we'll talk about the Jenkins 2.249.1 release that will come two weeks later. And then a proposal for Jenkins 2.249.1 on online meetup to review its features. We did this kind of meet up for 2.235.1 and felt like this next release is large enough to justify doing it again. We'll be doing it with the features for that release then terminology updates we should discuss and look at progress and talk further. And then a brief mention of Jenkins Update Center improvements. Any other topics that you need to get on the agenda, Markey. No sir. Okay, great so let's start it then and a first first is the doc sig meeting so we'll be having the meeting this Friday. It's got a number of topics on the agenda, but the most crucial topic will be Zina Abu Bakar who will present her and discuss her plan for Jenkins on Kubernetes documentation. We think that she's got a great plan. It's really really excellent work that she's done so far we like the proposal. One of the crucial needs we have is we need more Kubernetes skilled users that can act as mentors for her. So Kristen Whetstone has agreed to mentor. She's got Kubernetes experience. I'll be a mentor but I have very little experience we're looking for others. Markey Lee chance. Please definitely count me in. I've got a great deal of knowledge when it comes to Kubernetes. Excellent. Thank you. Very good. Okay, so we will look forward to that. I will review that. I'll review the dignity stock and I'll be ready to be able to provide any feedback on that. Super in particular, one of the things that is most of interest is what's what's an effective way to structure the material so that people will understand what they're how to get there, etc. And with your experience, I would particularly with your experience on the Kubernetes project. I think you make you have some good insights on Oh, we should introduce this way and then this way and then this way. She's open I believe to refining and revising her plan. Based on feedback and input. So the plan is here linked from this document. And we have a startup meeting that's also linked here that includes a number of action items for me for instance to announce her selection as the as the writer. Okay, do I need to get access as a mentor to the Google Summer of Docs. Oh, good point. Yeah, let's put that on. Yes. Yes, absolutely. If we if you don't do that I'm sure there will be some. Okay, so Markey. And you can also add me as an org admin too. I think we had talked about it with the whole leg back months ago. All right. And you may actually already be an org admin. I know that you were listed as an org admin. Just double check right now. I think I may still be. Excellent. I have a question item assigned to you to request to be a mentor and review all all of us get the action to review the plan for Friday and be prepared to discuss one of the things that we're going to need to find is need times to meet twice per week that fits with her schedule. I'll reach out to her and as a mentor I'll reach out to her and see what she'd like to set up and I'll get that set up by Friday I'll have an update for you on that. And no, no crisis there we're in community bonding right now. And community bonding is a time when we know that it's, it's not expected that she's working the 20 to 30 hours a week during community bonding this is just get things prepared. Oh legs observation I'm sure you saw in Google summer of code is that most projects that fail, fail already in community bonding and that's the most visible problem. So, so we want to be successful in community bonding to assure that the project itself will be successful. Great. Thank you. I do not see that I have access at all. Okay, so then, then that's that's a good now is a good time for us to get the request in to have you be a mentor and an org admin. So that's great. You want to send that request I think the way that works is that goes to Oleg. Send the request to Oleg. Yeah, hey, could I be added as an org admin that that gives us that then we've got three, three org admins available so that if one of us is gone the other one of the other two can help. Any other questions or concerns on the doc sick meeting topic for Google season of docs. Nothing for me. So, upcoming, we've got, we've got Jenkins to 249.1. It's the next LTS, and it will be coming in the release candidate is scheduled to come out this Wednesday. As soon as the release candidate comes out I'll start work on the change log. And that change log because it's a dot one release will combine the changes from 2.2 35. And the backports to 249.1. It's it takes more work it will need review by docs team member by docs sig members. It will need testing and assessment. Be sure that it's well described. For LTS is we provide an upgrade guide and the upgrade guide in this case is crucial because this is the first LTS where we're going to drop support for the ancient Microsoft.net version that we use for service management previously. We're now going to use Microsoft.net for and and drop support for that meant to. Two issues that have been flagged. And we've got to give descriptions of how to work around those issues or avoid them. So that's, and again this will need review testing and assessment. And at the same time we did an LTS flat Silverman was a great help on assessing the the windows changes in 2.2 35.3 and I hope to enlist itself again on this one. Any questions there for me. Okay, so, in addition, feature wise, this release will include the next step in the user interface improvements. That is further refinements to include prove the look in the field, keep things consistent, better color management, etc. It's also prep work for the tables to divs transition is coming is like expected in the December LTS. So that prep work is getting all of us ready so that our plugins can be adapted to no longer use tables for layouts, instead of using tables which don't work very well on narrow devices. We're switching use dibs and the work has been major. This is an 1812 to 18 months full request. That is now coming to conclusion. And it is much better than the old way it, but it naturally changes an awful lot. Any questions on the release candidate. Okay. All right, so then the release two weeks after the release candidate. See the RC for details. So, we will do an actual release September 9 with all the capabilities. I guess the other piece we should highlight here is testing is encouraged. And needed and expected right right there we go. Next piece and this one's one marky where you may be able to assist. We've got an online meetup that I've proposed. I've started a draft haven't yet submitted it to the advocacy and outreach mailing list that I've proposed to host an online meetup, describing the UI improvements, talking through windows upgrade. And then also looking forward to the next LTS to alert people that tables to divs is coming. You can, this hyperlink will take you there to see it. It's, it's still in the rough draft stage. I, let me put myself an action item to mark to submit the proposal this week to advocacy and outreach. So that we can get it on the calendar. Right now, it's not yet calendar and therefore no commitment that it'll happen. So, so that that release is going September 9. Right. So, maybe we could do meetup next week at some point if that works. Well, Oleg and I have discussed this and his suggestion was wait till after the release to give us a day or two of getting the feedback from people so that if there's something we need to desperately tell them. We could do it in the meeting. So the thought was make it the 11th rather than the 10th or the 11th, so that it's actually after the release. I think that's a good idea. And right now there's the only thing that's on the calendar for that day is, is the pipeline authoring sig meeting and that's at 9am. Okay. All right. Thanks. Anything else with regard to the online meetup. Nope. Okay, next topic then terminology updates. So the terminology, terminology vote for the replacement term for the word master has completed. The new term is controller, and Alex Earl sent out the announcement of that. We've had our first pull request merged, which makes a change at what it did was it converted all the security advisors to use the correct new terminology. We need a lot more pull requests for Jenkins.io. And we'll need text changes also Jenkins core. I was just looking at Jenkins core today and saw as an example of the word blacklist. And that's one that we've got an agreed, use a different context to use it, use a better word than blacklist so deny list or an even better term if one is available for the context. So we got a bunch of pull requests to make there. Yeah, I can start taking some action items to go through Jenkins.io and oh great do sort of a master PR, excuse me a large PR. That would be that would be wonderful in particular the docs. I think we're even we're even allowing that will change blog posts. So that the docs for sure, we would like to make that change. I did the I did the blog post for our previous terminology change so I'm pretty familiar with how to do it. So I'll do the blog post. I can have that done probably by the end of this weekend. Oh, that would be great. Excellent. Thank you. All right. And then anything else on terminology updates. No, just other than super proud of this work. It's definitely very needed and super proud of it. Yeah, delighted delighted with the results and I'm really glad that's great. So last item and this is more informational for folks who are working on docs. The Jenkins Update Center for the last 15 years has delivered its data over HTTP. And we're now upgrading it. Daniel Beck and Tim Jacome have made the changes that finish the work that Olivier Vanine started to get us from HTTP to HTTPS and still using mirrors. So, as far as I can tell Jenkins itself is already adapted. Everything's using HTTPS and the plug in plug in delivery mechanisms are in progress. And Daniel and Tim seemed to indicate that today that things look pretty good it may even already be done. Those are all the topics I had. Markey anything else. I do not have anything else other than to say it's good to be back. Great. Thanks for your help. Much appreciated looking forward to working together going to enjoy it a bunch. All right, let's call an end of the session then. Thank you. Thank you. Thank you. You are so welcome. Would you like me to do the the publishing to YouTube, or did you want to take care of that. I, I'm not sure where I did the recording so I may have to. Okay, if you didn't record it to the