 Hello. Welcome to Jenkins Documentation Office Hours. Today is April 11th, and this is the EU US edition. Around the table we have myself, Kevin Martins, Mark Waite, and Bruno Rochston joining us. For our agenda today, I've got the next LTS release, which will be happening next week on the 17th, the weekly release for this week, a new blog post that Chris Stern published for Google Summer of Code and some notes on Google Summer of Code at this point in time. Update for the contributor spotlight as it was published yesterday, some notes on the version docs project, the doc compose update that has been going on, and the fixes that were implemented, some notes on the technical review validation for pull requests, and then a couple of topics that we started last week are documenting the pipeline libraries with Markdown and the additional permissions for the Wiki Docs repository. Anything else that we need to put on the agenda or any other topics that we want to include? So then we'll get started, and if anyone else joins, we'll welcome them as always. For the first item on the agenda, LTS 2.440.3 is set to be released next Wednesday, April 17th. The chain blog and upgrade guide have been created and merged at this point in time. Adrienne pointed out a mistake earlier that one of the entries was looking at the same PR title and author that it shouldn't have been, so thankfully I was able to update that, and Chris and Mark have proved and merged it, so thanks to everyone for the help on that in getting that corrected. The release candidate's been available. There was an oddity and incorrect email sent out originally, but it's been updated. Things are correct now, and everything was corrected in that sense. So good to go there, and everything is looking good for the release next week. Weekly 2.453 was built and delivered successfully earlier this week, so everything's good there. And for the next LTS baseline, the discussion's been started in the developer mailing list, but we're looking at 2.452 as the baseline. The last several, I think the rough numbers 10 weekly releases have been going very well without any issues or any kind of major cause from the community, so with how positive things have been and how many changes in everything we've gone on, we're looking at 2.452, and it's gotten the backup that it will be. It looks to be the front runner at this point. The next item on the list, so this was something that had been published last week just after Doc's office hours, but Chris Stern created a blog post for the end of the back Google Summer Code application period ending, so thanks to Chris for their work on this, essentially just explaining that the application period's over, and now there comes the time to review the applications and proposals that have been submitted. So our wonderful team of org admins and mentors, leaders, are in that process now. There's over 70 or so submissions to review, grade, and filter through, so it'll take a little bit. They're working on that. Again, the application period closed back on April 2, so this is now the focus of Google Summer Code for the leaders. And then once the grading process has been completed, we'll get back to people, let them know where things stand. We'll submit the projects to Google directly after we've figured out what we want to submit. And yeah, in Google Summer Code, we'll continue on from there. Is there any other insights, notes, or anything on Google Summer Code that we want to highlight Bruno in this, or that cover everything at this point? Yeah, you covered everything perfectly. Thank you so much. Yeah, no worries. And again, the grading period's happening. We'll have more information once that's completed and let everyone know what the results look like at that point. Next up, so for the contributor spotlight, we just published Erwe LeMure's page yesterday. So thanks to Erwe for his work on that and for collaborating with us on that. It's a really nice story. It is a really nice picture of Jenkins as well. Erwe was not necessarily a Jenkins user before being hired at CloudBus. So it's interesting to see the insights and the ideas that he had prior to and after working on Jenkins and how things have changed in a positive way, which is really great. So yeah, so thanks again to Erwe. And then after Erwe will have Mark and so forth from there. I'll be checking in with Alyssa once she's back from her time away to find out who else we can tap on the shoulder for. We're getting towards the end of the submissions that we have already received. So we'll be looking at other contributors to see who we might be able to work with on also being spotlighted. We're gonna look at the same data and everything that we had before, but potentially update the timeline that we're looking at and see what we might be able to pull from that. Next up is the version docs project. So this has taken a little bit of a backseat for the time being. The infra team is working on making sure that costs are under control for cloud costs are under control. So that is priority number one. As a result, Chris and Vandei have been working on the version doc site separately from that, just continuing to make progress on that. They've been working on the Gatsby site making sure that everything is generating properly there since things like security advisories we wanna make sure are still being produced and rendered properly. So just making sure things like that are taken care of. So the infra team is still working on this. They hope to have it completed soon in the later, of course, but that will dictate when the version doc site can be part of the work going forward again. So once that's done, we'll go from there with the version doc site. I'm still reviewing things, making sure things are good to go on that front. And yeah, and then Mark, if there's any insight or any other details that we need to know about the AWS donations or anything like that, okay. Yeah, so nothing, I think that needs to be just noting that yes, the AWS donations have been received and we're actively working to use them to be sure that we apply them so that they benefit the project. Great, thank you very much. And then Mark, just for my clarification since it just popped in my head, would that donation from AWS go towards reducing cloud cost coverages and all of that part of the work that infra is working on? Or would that be separate? Yeah, so what we're doing is we're shifting workloads from other locations into AWS in order to consume that donation. Got it, great, thank you very much. Right, next up is the Docker compose updates. So this again, for anyone joining us now, this is work that's been going on since last year with the Google Summer of Code. The project was to incorporate Docker compose into tutorials and documentation so that we can update and have a more modern process for Docker usage. So Bruno has been working on that since Google Summer of Code 2023 ended, along with, was it Ashutosh was the one helping you Bruno? So perfect, it was so great. But Bruno and Ashutosh have been working on this, getting this put together. Bruno has been updating the tutorials lately and has looked to incorporate it into the Docker installation documentation, which is the next big step. There was an issue that had, that Bruno created a couple of PRs to fix and they have been merged since we last met. So that should resolve the issue that was at hand. Time will tell for sure, but yeah. Any other, anything to note on Docker compose updates? Well, first of all, I wanted to thank the user who created the issue. And I'll do a sort of apologize because at the very beginning of the issue, I was kind of skeptical because I tested that on my machine. It's tested on the CI in a GitHub Actions. I was wondering, how come this doesn't work for the end user? It may have a very old Docker version of something, but no, that was quite a contrary. It had a very recent version of Docker. I sometimes get this lecture at the local university about Docker. And one of the things I pitch is that Docker is supposed to solve the, it works on my machine, because it's supposed to work just about everywhere like Java compile runs and run anywhere until it doesn't work anymore. But that's the same for Docker. It works until it doesn't work anymore. Docker Compose had a fix, I would say, an upgrade or something that broke the way that we were using Docker Compose. It was our fault. It was kind of an edge case. You know, so it used to work, but unfortunately, after the modification at Docker, it did not work anymore. So yeah, it's fixed now. Thanks to the users who created that. And I had a look at the use earlier today with Mark because on the repo you have some insight. And frankly, I saw some pretty interesting numbers. So it looks like some people are using it, but the numbers are so flattering that I'm wondering if they are for real or if there is a glitch into a system or something. But anyhow, that just proved that some people are using it, detecting errors when there are some. So yes, that's quite a nice bonus for the Jenkins project. Awesome, thank you so much Bruno. I really appreciate that. Thank you, Kevin. Yeah. And then just for my knowledge, the stats and the numbers that you're referring to, are those something that are available to anyone or strictly for maintainers? Oh, yes. So just if you go on the quick start tutorials repo in the Jenkins docs organization, you should see something called insights. Yeah. Okay, the insights for it. So yes, in the insight, you see quite a lot of traffic. If you click on traffic, for example, we can see that some people are cloning. But the numbers I was referring to, which is way too high to be accurate, is in another place. If you go back to the quick start tutorials main page, on the right, you have packages, one quick start tutorial Jenkins AI tutorial, on the, yes, you're there. Yeah, there, just there. If you click on that, you will see on the right, 7.69K total download. And it was 7.51 earlier this morning. And that sounds unrealistic as a number, at least to me. I mean, that does sound like a good amount of people. I mean, there's plenty of reason why that could be true. I won't sit here and try to analyze it, of course, but having good, clean, clear instructions is always a very huge benefit for anyone looking at this. Or maybe I should stop my wild true script that clones and downloads repeatedly. No, just kidding. But maybe someone has something like that in his attic or whatever, that's quite a high number. Anyhow, thank you. Yeah, no worries. Thanks for helping me at that a little bit more transparent sharing that with us. I appreciate it. And thank you for my knowledge as well. Thank you. So, great. So again, just a really nice example of Google Summer of Code projects coming full circle and how they're implemented into the project. Next item on the agenda is something that I started a discussion around last week. So I am a documentation officer. My focus is the documentation. I'm not a developer by trade or practice, so my technical skills have a limit to them. As a result of that, I've been looking to see what we can do to help make the review process and pull requests submission and review process a little bit more smooth and a little bit more constructive for everyone involved. So I discussed this again last week here in the office hours and with others, but the idea is that we are looking to have people help with technical review and validation for pull requests that are coming in. I'm doing my due diligence and putting every effort I can into understand as much as I can in that instance. But if I hit a wall, I am just really happy to be able to say that there are other people willing to help with this and review this stuff for that sort of validation where they don't need to necessarily review the documentation part of it, just how accurate are these steps or this instruction or this content that's being submitted. So again, I'm doing every last piece of work that I possibly can to make sure that that is the only thing anyone else needs to worry about. I'm doing the documentation review, testing things as best I can, following instructions to a point. And then at that point, that's when I'm asking for help and for anyone else to have another review of it. Thus far, I've reached out on a pull request recently that got some review and some help from Chris Stern. So thanks to Chris and Zbenik for their help on that one. Really appreciate that support. And so we've also updated the copy editors team to include these new folks so that review can happen. So Chris Stern has been added as part of it. Bruno has been added as part of it. I'm not, Mark, has Meg agreed and been made part of it or are we still discussing? Meg was already in copy editors. So if she wasn't, she'd already been approved for copy editors long ago, years ago. Okay, perfect, so great. Then so yeah, so we've expanded the team a little bit or the group members in that sense and it's already been proven really great. So we'll continue with that. If anyone else is interested in joining up or wants to help with reviews, by all means send us a chat through Gitter, through pull requests or however you want to get in contact with us, let us know, we're more than happy. Next up, so documenting pipeline libraries with Markdown or plain text or HTML. So I'll do my best to review this one. Mark, feel free to jump in or point out anything I might miss state. But Marcus Winter recently submitted a pull request to update and have Markdown as an option for pipeline library documentation before it was strictly just using HTML where it might not be as well worked. Friendly for writers, friendly for writers. Let's call it what it is. Yes, I can use HTML markup, but boy is it not pretty for me as a writer. Yeah, and so Marcus has done the work to submit this and do the work to make sure this works. Mark's converted his branch of the pipeline library to use the Markdown and it works really well. So therefore everything does seem to be working as intended and as suggested by Marcus. So the only thing at this point is that if we decide to include the Markdown format or plugin, which is how this would all work, it would need to be updated and added to ci.jenkins.io. And so that is a bigger task than what we can just discuss here. So that's something that needs to be discussed with the info team and security. So Mark has created a help desk ticket for that so that we can have that conversation in a place that makes sense. And so that we can follow along and add to the discussion if anyone feels strongly one way or another. But we're getting this set up for the work and it's been introduced in the infra getter channel as well if I'm not mistaken. But yeah, so this is something that's a new proposal that we're looking at and something that we're looking to incorporate if it is agreed upon. Mark, did I miss anything on that? No, you got it right. It's, we're probably weeks away from a decision and I'm likely to make some fixes to the existing pipeline documentation because right now some of it assumes Markdown but of course then is rendered as HTML. And when you assume Markdown and render as HTML it looks awful. Gotcha. Okay, yeah, that'll be something we need to update. I'll be more happy to help out with that in any way I can since it sounds like documentation stuff. Great. And then the last item on the agenda that I had for today was additional permissions for the Wiki docs repository. So this is again something that we discussed last week. It's a team that is part of the infrastructure that didn't have permissions for the Wiki archive repository as it stood then. This has been updated since now the Wiki docs team has access to the Wiki archive repository and copy editors have that same permission. So it's not something that we necessarily touch or work on a lot, but there was a case where we had to mark a plugin as deprecated and couldn't get the maintainer to do that. So we had to go in and make it a little note for ourselves so that everyone could see that from the page. I don't have the page readily available here unfortunately but there was, I forget which plugin it was specifically. Just open plugins.jankins.io and you can see it. Pegdown, P-E-G-D-O-W-N, that's the one. So yeah, so this little piece here of saying it's deprecated this was something that the Wiki docs team needed to implement because the maintainer was not responsive to the request. Yeah, because if you scroll upwards, you'll see why the last release was 12 years ago. Yeah, clear as a day there, so yeah. But again, that was something where we updated the team members for the copy editors and the Wiki docs and docs, like there was a handful of updates to different teams and groups for the org that just made a lot of sense for cleanup and just making sure things are current. So all kind of rolled into that. Oh, and just to note, since I didn't put it on here, let me just add it to the bottom here. CDCon will be taking place next week in Seattle. And thanks to all the CDF, the CD Foundation and Jenkins community members, the awards for both CDF and Jenkins will be announced, presented and given out next week at CDCon. So thanks again to everyone who participated, voting, attending, anything like that. It means a lot. The democratic process is shown to be working if people have won, so yay for that. But the community appreciates it. We've had several people nominated for the Jenkins awards specifically and each one of them has every right to be the winner there. So it'll be fun to see who actually is announced. But next week, CDCon's happening. Mark will be attending and I think Basil is too. So really exciting. We'll have a couple of people there to represent Jenkins and who better. So yeah, that's exciting. But yeah, I just wanted to put that note in there once again, just to make sure that everyone's aware that it's happening next week. That wraps it up for the agenda that I had since we are good on topics. We'll go ahead and wrap things up a little early today. Video recording will be available 24 to 48 hours. We post it on the community discourse channel as well. And until next week, take care, stay safe and we'll see you then. Bye now.