 Hello and welcome to the Jenkins documentation office hours. Today is July 6th and this is the US edition. Today we have myself and Bruno Brockman. If Mark is does end up joining us will invite him in later when he comes but for now it's just the two of us so for the agenda. So, I know that we had the midterm presentations for Google summer of code just short while ago. Welcome. We're just talking about you. All good things I promise. And just going over the agenda. So, yeah midterm presentations just happened earlier today so there'll be lots more about that in the future. There have been some open pull requests of interest that we can discuss. I added a few more this morning, based on what I've been working on for the Java seven transition. Just a couple notes about housekeeping. Is there anything else that we should be putting on the agenda or anything that anyone wanted to add. If not, no worries. Okay. So, starting off so Google Google summer of code is well underway. And we've actually reached the midpoint of Google summer of code. And as a result today, we hosted the mid we, we had the midterm presentations for Google summer of code. It wrapped up roughly around 12 o'clock earlier today so very very fresh, which is great. And the mentors were asked to evaluate their, their work on GSOC for the contributors. And some of the questions that they asked themselves and we're part of the evaluation are listed here, really, just to get people to reflect on their actions their their connections and really like how can you improve from here for next year, if you want to continue to be a mentor. It's a lot of them are very straightforward questions, how do you communicate and how often when how did you help, how are you helping them track this so just really good insight to keep in mind for Google summer of code now going forward. And if I'm not mistaken, and Mark, maybe you and or Bruno could confirm the web, the presentations. The presentation recording it will be available layer and available for everyone to give a watch. Yes, correct. That's right. Beautiful. And anything that you wanted to share about the midterm presentations Bruno or Mark. Mark, go ahead if you have something now. Ashutosh did a great job demonstrating talking about Docker quick start. Thank you. Congratulations to Bruno as the mentor and I felt really good about the get lab plug in modernization presentation from harsh harsh Pratap Singh. So the two that actually I guess the third is the Jenkins.io rebuild. That one is for me the most scary because it's such a huge project, but it's making good progress. Yeah. And I was actually checking out the prototype site earlier that Bundy had provided and it looks really nice and clean and I like the presentation of the page and how everything's called out a little bit more like specifically I was looking at the installation docs and just really enjoying the fact that like the code blocks are color coded now so that they stand out. The notes are a lot more kind of a parent instead of hoping that they're noticed and like the text is always a little grayed out on the notes which I thought was interesting and the fact they're just regular text here but clearly signified is, is, I think a lot better and visually in terms of the documentation so yeah. So, Google summer codes and making great progress we're going to continue to do so we've got how many more weeks is it in total for Google summer code. I think we still have six weeks to go. I think so. Awesome. So, yeah, so that brings us right towards the middle and slash end of August. So, perfect. Great. Lots of lots of stuff to look forward to and yeah even if that alternative alternate build for Jenkins.io is a larger projects will be available to keep working on after the fact to just because Google summer code doesn't continue forever doesn't mean that doesn't that work stops. So, next, so some open pull requests of interest. There was one submitted recently by to new Sharma updating the administrative Jenkins on Kubernetes docs. I've gone through from a documentation standpoint and really more than anything else this is just requires review from people that are experts on grenades, or anyone that's more familiar with Kubernetes and it's an ounce then I would be. I think we've asked Davion and a couple other folks in the pull request if they'd be available to take a look at it and provide their feedback. There's anyone else that feels comfortable or so inclined to review the Jenkins and Kubernetes pull request there's still plenty of room for feedback and suggestions here. We'll be working with the news to make sure that this is organized and put together in a way that we can actually merge it and get it published on the page on the site. Thank you to the town news for this and this is a continued effort that he's been working on for a little bit now. So, just, again, really appreciate the work and the consistency that's usually been putting in on that makes a lot. It makes a lot me feel a lot better and a lot happier just having everyone working. So, there was one that Jeffrey Chen had submitted a while back for the best practices page. This just needs some more text and context to be filled in on it. It's something that has been that was being migrated from the Jenkins wiki. So, this does need a fresh little eyes some more view and potentially some help in finding any gaps and closing those gaps in function form function or any sort of updates that we've had between when it was originally written now. Yeah, that's one where I think I need to enlist help from Darren Pope, as one as a possible reviewer just to say, Hey, what should we say here and what other practices should we add the the concept of a best practices or preferred practices is inevitably loaded with opinion. Right. And so what you're seeing here is Mark weights opinion, based on things ideas extracted from the wiki page that was created long ago. And best practices or definitely something that users come to expect and get a lot of use out of and I mean at least my own experiences it's been it's always been very helpful so having something there even if it is opinions and suggestions, you know, it will get someone started and that's the best thing that they can do for someone. There was another podcast submitted on the scripting and security. This was actually one that was submitted a couple years ago, November 21, but makes created a lot of great content here and has gotten a lot of feedback and review from folks like Daniel back who are the security go to person for Jenkins or that like a lot of people have gone through and worked on this. This just needs to be updated and put together in with the comments suggestions everything applied. And some more of you of course by the security team there's most likely didn't change it since 2021 women's first submitted so once we have that. This is something that myself or Mark could work on because there is all this already existing context and content. So this is something that is going to be now on my radar going forward and I'll be looking at this to review and edit. And also on the script security page that we should be aware of Mark or anything that I should keep in mind as working on this. You described it well it's, it's a long ago attempt by Meg to create some something helpful for users and it's been through multiple reviews and probably yet needs more. So Meg doesn't have time or capacity to do further work on it. And so it's up to somebody else and Kevin you could pick it up I could pick it up etc. In any case I think our work on Java 17 is higher value than that for right now. Yes, of course. And speaking of so as part of the Java 17 transition. I'm going through the installation guides and updating the documentation as I can. And put we merged the Linux installation documentation so this now has a note indicating the change with the release of devian 12 that open JDK 17 is now the option the version being delivered and all of the corresponding paid parts of the Linux installation now include JDK 17. So I've gone through and tested this one in on devian and I was able to also get review from Mark and a couple others confirming that everything was working and correct. So, we've got that. And then I just also submitted an update for the Docker installation documentation. There was no hard and fast mention of Java 17 but I went through and updated the formatting. And some of this in text and some of the other I didn't change their content necessarily just cleaned it up so that it's yeah more in line with the guideline the documentation guidelines that we have set in the style guide itself. And I'm still going through and I've got other installation documentation, the job of upgrade requirements, etc. that I'm working on getting the transition finalize there and completed. Now, maybe a few months from now after GSOC will have to make another PR regarding the update, you know, the Docker installation guide, we may have a way to install it with less instructions, we'll see. Thanks to the Docker quick start got Docker quick start and everything. Maybe that's my hope. I don't know. It's just out of the blue will see. Yeah. No, for sure. And I was when I was reading through this earlier. I noticed that there was, it was stated that there would not be a need for the dind anymore. And so that would definitely change the instructions here so yeah, if it does come down to that we can absolutely. I can't promise that for each and every tutorial existing in the Jenkins IO, we will be able to do without Docker in Docker, but for the first five, I can promise this is the case for the other ones. We'll see. And then so the last note that I had here on the agenda for today is that mark will be out of office the next two weeks so the docs office hours Asia either will need to be hosted by another person if there is a volunteer or if not skipping those meetings so just something to put on your calendar keep keep be aware of this will. I'll be sure to bring this up again next week during the EU US office hours so yeah and there's we discussed it during Asia office hours last week and came to the conclusion that we just accept that the meeting won't happen. Okay. So, I'll I have the action item to delete them from the calendar if I haven't already done it. Is there any so that was what I had on the agenda for today is there anything else that we want to talk about or bring up or discuss here in office hours today. Just maybe about the June newsletter. The PR has been created it's not ready yet mostly because I did not do correctly my homework. I should read that tomorrow and we hope to get it merged on next Monday at worst. I'll be reviewing and going through it right now as well to get everything aligned so that any additional updates or changes that need to happen are not so time consuming. Yeah, and thanks a lot to all the contributors. Absolutely. Great. Okay. I'm really scared of everything I had for today. What will will end the recording here and the record it'll be available 24 to 48 hours. Thank you as always for joining and have a great rest of your day.