 Welcome. This is the 18th of May, 2023. It's documentation office hours, topics we've got today. Kevin Martins is unavailable. April newsletter, transition from Java 11 to Java 17 in the documentation, Google Summer of Code. And then the other items I think it's safe to just leave them in the list. They're more to remind that we need to be sure we get them all the way to closure. Anything else that needs to be added? Nothing comes to my mind. Thanks for asking. Okay. So first item, Kevin, Kevin Martins is going to be unavailable until June 12. He shared with the Jenkins Board that he's offline. And so we've got about another four weeks, three or four weeks where he won't be available. The idea there was let's accept that the documentation transition from Java 11 to Java 17 will be delayed. And encourage others, Bruno, you, me, Alyssa. I've asked Meg McRoberts as well to review pull requests in his absence. And I'll handle the change logs for the weeklies and the change log and upgrade guide for the upcoming LTS at the, that happens May 31. Any suggestions or guidance there that you want to change or recommend something different. No, no, no. Thanks for asking. That's okay. All right. And thanks to you for publishing the April newsletter. Thanks to Kevin for correcting reviewing Alyssa. So it's a group work, but yeah, I'm happy. It's almost on time. Well done. Very good. The next topic is just to say that the documentation transition is delayed. We got a ticket that if other contributors would like to contribute here, here is a list from Kevin of the pages that need to be visited. And he started an initial pull request for one of those steps, if someone would like to pick it up. Next topic was Google summer of code. So we're pleased to welcome Vandit same as working on the Jenkins documentation project to rework the Jenkins.io website, so that it supports multiple versions, much the same way as for instance this site does so I can look at the documentation for the reference manual for say get config and notice that up here at the top there's a choice that lets me look at old documentation versions. We want something similar like that for the Jenkins documentation now it certainly won't have this look and feel but that's what Vandit is is working on is is that kind of experience for Jenkins documentation. It will prove handy. That's for sure. Exactly. Then Ashutosh Saxena is working on the Docker quick start project Bruno since that one's yours anything you want to share there on on how that's progressing etc. I think that was first time being because it was difficult to find a correct time slot for all the mentors and Ashutosh, but we'll have our first meeting tomorrow. So hopefully we'll progress. We already have defined our communication channels, and I think we'll work on the plan tomorrow. Good. Excellent. Thank you. Thank you. Anything else you want to share on that one. No, nothing to share. Okay. Right so may 20 May 28 10 days from now will end the community bonding period and start phase one of the project development. That's great. Thanks. The last three items really are just status reports there's no change on the on the pipeline steps reference it still works. Let's just prove it to be sure. So it works by going here pipeline, the pipeline steps reference. If we search for checkout. And we open it. It has the full content good. So still working the test that's in the code defends us against breaking changes. We don't have time yet for anyone and probably not for a month or more for investigation of what actually broke that and any question on that one Bruno. No more things. Okay, so low risk, low risk. Tests defend us from a breaking change. Okay, so other topics are idling until we get more traction we just got another request on a community thread, asking about support on Centos seven. And the answer is, hey, we intend to remove Centos seven support. And the submitter said, oh, that's okay, we're going we're going to keep using it anyway and here's the change that they did. But the reality is, we don't intend to continue supporting red hat enterprise Linux seven and its derivatives for a long time. Yes, I saw this week on Community Jenkins IO. Somebody asking for help. It was using Centos seven and Docker and Jenkins, and I was trying to put the blame on Centos seven, just in case. And, and, and certainly we, we've got lots of places where the Jenkins project actually uses Centos seven in, not in its own our own build processes, but we will reference things from Centos seven and so we've got work to do to get it cleanly removed, but the sooner we start, the sooner it'll get done. Yep. All right, that's all that I had anything else Bruno. No more things. Thank you.