 Hello and welcome to the Jenkins documentation office hours. Today is January 25th and today, and this is the EU US edition around the table. Currently, we have Mark Waite, Bruno Verrachten, Chris Stern, and myself, Kevin Martins. If anyone joins, we'll welcome them as always. For now, go over the agenda. We've got the Jenkins contributor summit at Boston next Friday. Jenkins was announced as a winner of a DevOps Dozen Award, so we'll note that. Really exciting about that, and yeah, just great to celebrate Jenkins in any way we can. Contributor spotlight updates, couple of new blog posts that were published today, the LTS and weekly release yesterday, Google Summer of Code Prep, the Maven and Python tutorial revamps, version documentation for Jenkins.io, the sponsor attribution page, and I wanted to highlight the related pages in the 404 issue that's been getting some traction lately and work done, upgrading the Jenkins section, which is what we started talking about last week, and a housekeeping note regarding office hours next week. Is there anything that we want to add to the agenda or anything else that we should note here? Or if not, we'll get started. Yeah, nothing else from me. Okay, thank you very much. So, first on the agenda, again, Jenkins contributor summit is next Friday, February 2nd, the day before the FOSTA conference starts. We're gonna be there, like I think all of the officers now are going. We found out Tim Jacome's gonna be there. So we have all the Jenkins officers will be there, four out of the five board members. We've got more than 20 people confirmed to attend the distributor summit. This is shaping up to be amazing. Yeah, actually it's even better than that now, Kevin. John Mark disclose that the room is full. That means there are 30 scheduled confirmed attendees. So we're now at 30 attendees planned for this event. Yep. Wow, that's amazing. So that's fantastic to hear. I'm really looking forward to everything that's gonna happen. John Mark also posted the finalized agenda on the community site. So you have an idea of what the schedule is gonna look like for the contributor summit. So presentations, lunch break, discussions, and things afterwards, and then celebratory dinner. Check the community posts for real detailed information and to get a better idea of that. John Mark's also posted a couple of blog posts that we've got linked here regarding Kvazdom. So lots of great information out there. And yeah, really looking forward to it. I'm really excited just to be able to meet everyone and share the love. Next up on the agenda. So the DevOps dozen is a awards that they do every year. This past for 2023 Jenkins was awarded the most innovative DevOps open source project. So thanks to everyone for all their work. I mean, this is a result of all the work that happens throughout the community, throughout the Jenkins project. So it's every single person that touches it. And thanks to Alyssa and the other folks that helped make the award happen and get us nominated for that. Here is some organizational stuff that goes on in the background that we absolutely need. So thanks to everyone involved in this. It's great to celebrate Jenkins in another way this year. So fantastic. Mark, anything else on the award? Or am I forgetting anything about the award? Well, so we're going to use the opportunity of the contributor summit to take a photograph of the 30 people or so that will be attending. And our intention then is to overlay an image of the DevOps dozen trophy when it's shipped to us with that picture so that we can highlight that the reason it's an innovative DevOps open source project is because of people like this group of 30 that we're meeting. Now, admittedly, we can't get everybody but showing that this is not a one or two people thing, that this is an entire community that created this. So yeah, looking forward to it. And so we will take pictures. We're going to have a lot of fun at the contributor summit and we'll use some of those pictures to highlight this DevOps dozen award. Amazing, great. Thank you so much, Mark. And yeah, and just like previous years, post-Fosdom will have a recap sharing insights from everyone that was there and just recapping Fosdom as a whole in the contributor summit. So to be more recommend that in terms of the contributor spotlight. So we just published Uli Haffner spotlight on Tuesday. That was done off schedule by one day just because we have the LTS and weekly release yesterday which ended up being security releases. We wanted to make sure that Uli's spotlight did not get lost in all of that. So we wanted to publish a day early. Everything else will be back on schedule as normal going forward. And next up will actually be Valentine delay. So their spotlight will be published on February 7th and then we've also got the next couple of months planned out on top of that. So we've got plenty of content to come and just I want to say thank you again to all of the contributors that have been working with me on this. This has been really great to not only meet and learn about you, but also get the chance to appreciate and share all of that with the rest of the world. This work should not go unnoticed and it's great to be able to just share that and highlight these folks that deserve it. Yeah, a special thanks to Valentine. Valentine was attending our Google Summer of Code intro that preceded this and Valentine is planning to attend Foslem and will be at the contributor summit. So thanks, Valentine. And we see that the same thing. Uli Hoffner will get to see him face to face at the contributor summit along with Alex Brandis and several others. We won't see Alex or all face to face and I don't think we'll see Chris Stern. Sorry, Chris, that Belgium is not on your trip plans for next week. Anyways. Yeah, no, it's gonna be really exciting. I'm really jazzed up about meeting all the contributors and like all these folks that we've been working with and I've been partnering with on this to be in person, it's gonna be great. Next up, so a couple of new blog posts that we published again today. So first up, do it out of order. 2023 recap, thanks to all of the SIG leaders and officers, everyone that contributed to that. Everyone that's put in the work that we could recap for the year. And Alyssa Bruno, putting the recap together. Thank you very, very much. It's great to see all of the wonderful accomplishments that we had over 2023. There's a lot of content there. Definitely check it out when you have some time and look at just so happens to be the award again. Look at that. And we'll have a separate blog post regarding the award and some background as to that soon. Most likely after Fosdum, but if we can get it published before then we'll get it published, but no, nothing concrete there yet. And then the other blog post that I wanted to highlight is a blog post from Sonar, which is they are noticed a vulnerability within Jenkins and we're able to detect and partner with the Jenkins security team to resolve it. This vulnerability was found. This was something that was part of the security release that came out yesterday for both LTS and weekly. So we wanna make sure that this is published so that we have as much insight and we can share all that information to the community. So real quick, Sonar helps clean up code, make sure that everything looks good. They had a really high praise for Jenkins in terms of the code setup, the quality of code and just structure around Jenkins, found a vulnerability that could lead to some issues, detected it, alerted Jenkins security, and they worked together, collaborated on resolving the issue, making sure that this loophole, or not loophole, but that this hole is covered up and not accessible anymore so that nothing dangerous could be happening. And yeah, like I said, they released it. This was part of the security release yesterday for the LTS and weekly release. So this is included within all that. And I just wanna say thank you very much to the Jenkins security team and the Sonar team, Yaniv specifically, since he was able to write up the blog post and provide us that. So great to see, really lovely to see the collaboration and it's always a win when we have security, security victories for Jenkins. So really, really excited to see all that. On that note, I just wanna ask if there's anything I might have missed or not included about the Sonar blog post. Mark, if you might know anything else about it or that's pretty much everything. Well, I've got more research to do because I'm doing a what's new in Jenkins 2.426.3 later today and it'll be a key highlight. Thankfully, Darren Pope's really smart about these things so he's there to help. Great, and yeah, and for anyone unfamiliar, whenever there's an LTS release, Mark and Darren do a live stream talking about what's new. So that'll be today, like you said. Thank you very much. And again, on that note, so LTS 2.426.3 and weekly 2.442 were both released yesterday. Again, this was a security release. So thanks to the Jenkins security team for handling the release and change logs. And as far as the next LTS goes, so right now the baseline is looking like it's gonna be 2.440.1 is gonna be the next LTS release. So really looking forward to that, excited about all the changes and everything that's gonna be happening there. I will be working on the change log and upgrade guide in the upcoming couple of weeks. Make sure we have that ready to go. Boston will be taking up a good chunk of time over the next week or so, but we have some time before that will be released. So everything will be taken care of way prior to the LTS. Next up on the agenda, so Google Summer of Code 2024 prep is ongoing. And we actually just had right before this the contributor roundup. So anyone interested in participating in Google Summer of Code 2024 with Jenkins is invited to attend. And yeah, it just finished up as Mark stated, Valentines there, Valentines there. Chris's organization, or forget what the actual title is, but Chris's org admin, that's what it is for Google Summer of Code this year. So really, really excited to have Chris on board and like leading the way on that. Just overall really excited. We've got a lot of Gitter activity, people talking about it, offering reassurance, offering any kind of advice, any kind of insights they can. Chris or Bruno, would you want to share any insights about the contributor roundup or the meeting that just finished up? I think Bruno went, so I was there, Mark was there too. And we had an hour long discussion about how to best prepare for GSOG applications as a contributor. And I think we got more than 20 questions during the Q&A session, which was a very good sign. And I think like at some point, we had more than 20 people showing up to attend besides the four panelists. So we had quite a good turnout. That's awesome. That's fantastic to hear. That's a lot of folks, all things considered. So that's great kudos to you Chris and everyone that's part of the Google Summer of Code team. Like this is, that's fantastic news. So thank you very much. Next up on the agenda, so something that we've been discussing the last couple of weeks that we got now fully taken care of, the Maven and Python tutorial revamps have both now been merged. So you can see with both the Maven and Python tutorials, they now have instructions for using Docker compose. So this is again, the result of one of the Google Summer of Code 2023 projects. And thanks, huge, huge, huge thanks to Bruno Vrachtin for implementing that and getting the integrated into the tutorials. Everything's great, everything looks good. Really straightforward, much, much easier to use and navigate and work with compared to the more complicated manual Docker instructions. So that's just fantastic all around over there. Yeah, Bruno, do you wanna share anything about that? Have any notes, comments about it? Well, thanks a lot to Damian and Mark for the idea to begin with. I think that it was their idea to start with these tutorials. And we still have a long way to go. We want to simplify the rest of the Docker instructions when it comes to Jenkins. So how to install Jenkins on top of Docker, for example, that's our main target, but we still have a few tutorials to work with. The one I'm working on these days is a Node tutorial. It follows the same pattern, more or less. So it shouldn't be that difficult to finish, even if I'm not much about Node. Yes, there are still a lot of things to do when it comes to these tutorials, but we are progressing, that's a good thing. And thanks for pointing out that this was the result, the follow-up to 2023 GSOC project. And all started with Ashutosh Saxina, Leo Bervianto and Jean-Marc Messin, of course. Thanks a lot to all of them who are applying in that project. Great, thank you very much, Bruno. Yeah, it's really great to see. It's amazing to see the whole progress and process of Google Summer of Code working its way through and then completing. Yeah, all of this is just fantastic. Thank you again. And something that I've been talking about with Marc, actually, is potentially working on the Docker installation instructions, having you show me the ropes a little bit so that I can do that. Yeah, it's cool. I'm really interested in it. And the Docker installation instructions are someplace that I've been in a lot. So yeah, I'd like to see them improve. Good luck with that. Yes, count me in if you need any help with that. I'd be happy to participate. Yeah, yeah. And we'll talk more later on and figure that out. But yeah, it's great to see you. Thank you very much. Next up, so another Google Summer of Code 2023 project is that we're getting ready to get to the finish line and publish. So the version documentation for Jenkins.io, this was born out of the Looking for Alternative Build Tools for Jenkins.io, that Chris and Vandeet have been working on since Google Summer of Code, now beyond. Everything is looking really great there. It's set up in the Jenkins infrastructure. So we've got, sorry. For clarity, yes. Kevin, do you want to talk further? Are you OK if I give current status? Yeah, go ahead. Go right ahead, Mark. Sorry to interrupt. It just, in for team meeting on Tuesday, we were discussing it and realized we've got challenges with our Azure costs for the January, February, March, where we're over our cost amounts. Because we're over costs, we've had to delay some projects. And one of the things we've delayed is this deployment of docs.jankens.io. Chris, I apologize for doing that. But we've got to keep ourselves as close to budget as we can on our cloud expenses. And that meant Damian and Erwe and Stefan had to switch focus to do some cost savings. Now, one of the cost savings was successful already today, ci.jankens.io has moved. It moved from one piece of Azure to another piece of Azure. And users don't see any difference. And that's a really good thing. But what they just did with that is we'll save us an estimate of $500 a month by having made that change. Because now we'll use donated Microsoft money to run that machine instead of using money that CDF has to pay. But there are still several more changes like that that we've got to do in order to bring our costs down to where they need to be. So I apologize, Chris. We're going to be delayed. I'm not sure if it will be. I suspect we'll resume after FOSDM so early February before we take a look at it. Go ahead, Chris. You had unmuted. OK, that should be fine. Great. Thanks. Sorry for the bad news. But thank you for your patience. No worries. Thank you very much. Back to you again. Yeah, thank you for clarifying all that, Mark. I think I might have missed that one or that didn't register in my brain for some reason. So that's good. Yeah, that's great to know. Thank you very much for that. On that note, I have been going through the version Doc site reviewing things like navigation, pages, content, et cetera. So I've been raising issues as I've come up against them. And both Fondi and Chris have been resolving those issues really quickly, really easily and really well. There was, I think, I submitted five or six issues the other day. And they all got taken care of with one fellow swoop. So just really fantastic work. Thank you very, very much to Fondi and Chris for all your work on that. You're welcome. Next up on the agenda, so the sponsor attribution page. So this is, again, something we've been discussing for some time. Essentially, JFrog asked if we could attribute them in the downloads page, make sure that they're recognized as a sponsor, which, of course, that led to a larger conversation about, well, we should make sure we have sponsors. Everyone attributed as a correct sponsorship. Right now, we have a list of sponsors at the bottom of the root page, which we also removed Red Hat from recently because they are no longer part of the CD, the Linux Foundation. And therefore are not a support. Part of the CD Foundation. They're probably still part of Linux Foundation. That they just left exited CDF. OK, sorry. Thank you, Mark. So yeah, so they are not part of the CD Foundation anymore and therefore are not a sponsor of Jenkins. So they've been removed from there. But the bigger point of the attributions and the sponsors is that Basil Crows had gone and created a sponsors page draft so that we have an idea of what it might look like, what kind of levels we'll have. This is then going on for a little bit now. We've taken a little bit backseat due to Fosdham and other things going on. But it seems like we've got a good place to work from. And like I said, Basil has a sponsor and was just going to need some hammering out. We've also got a couple of sponsor questions at the moment. I think Oracle, they've stopped donating. AWS has not donated to Jenkins in a while, but have time before they're going to get removed. So there may be some shifting of the sponsors on the page. But for the most part, CloudBees is an anchor or like the highest level due to the amount of support they're offering Jenkins. Others are going to be mirrors because it's a different kind of sponsorship than providing money, providing other services, stuff like that. So it will be relative. But it's going to be within the ideal scale of how much support is Jenkins receiving. So yeah, it'll be a nice little page and presentation once we get that sorted out. Next up, so this was a pull request that's been getting a lot more attention and comments on it in the last week or so or in the last few days. So Sridhar has been working on creating a new 404 page that lists related pages. They've done a lot of work. They've been working with Chris and Gavin Mogan has been assisting and providing feedback and suggestions. A lot of folks are helping out with this to hopefully improve the 404 page so that it's a little bit more usable or just provide some insights for the user when they're looking for something on Jenkins.io, whether it's related sites or providing the search contents that they were looking for in the first place. So really great to see here. Love the work and the back and forth that's happening between various people within the community. Thanks to, again, Gavin. Thanks to you, Chris, for helping out, for Givnix, for them helping out, for everyone. Just, yeah, this is great. And it's nice to see a new contributor embracing the community like that and the community embracing them back. Just wanted to throw it out there. If anyone wants to review, provide some insight as well, by all means. It's welcome. And then next up on the agenda, so we have the upgrading Jenkins section. We started this discussion last week and essentially, Vandi has, had submitted a pull request last year for adding an upgrading Jenkins section. It's a great start. There's a lot of good stuff there. However, there are a lot of nuances and particular is when it comes to Jenkins and how someone might have installed it or be using it that are not necessarily accounted for. And it's one of those things that it's hard to account for if you're not really aware of what other people might be using. So it's probably gonna be a bit more involved in terms of what the content looks like, how we organize it, and what kind of instructions are provided. Again, it's gonna depend on how someone set it up, whether they're using Mac versus Linux versus Windows versus something else. If they're using Yum versus Brew versus App, like there's a lot of pieces to it that have to be considered. So I would love to have that discussion going forward and maybe talk about some of that stuff here. If anyone has any opinions or ideas one way or the other, welcome to it. But yeah, that's something that we have to do right this second. No worries there. And then the last thing, the last note I have here, this housekeeping note. So Fostom is gonna be the second, third and fourth. So starting next Friday, however, both Mark and myself will be traveling for Fostom. So Docs Office Hours next week will be canceled for both EU and US and Asia. So that will only be next week though. Once Fostom's over, everything will get back to normal after that. And so, yeah, just really excited about Fostom, that's all. Yeah, that covers the agenda I had for today. Does anyone else have anything they wanna discuss? Talk about there on the agenda. Kevin, I had one item that I wanted to borrow Chris while he's here. Chris, while you're here, Chris, are you okay if we cancel Docs Office Hours Asia that's scheduled to start in eight or 10 hours? Yeah. Okay, thank you, Chris. The preference there is that way I can reduce the number of hours I'm working today. It's very lazy of me, but I admit it. Okay. Thanks, Chris. And thank you very much for being up at all hours of the night to join this session, much appreciated. Always. Yeah, thank you, Chris. Please go get some sleep after this. You deserve to rest and relax as well, though. Yeah, that covers everything for today. Video, the recording will be up in about 24, 48 hours. And then we'll see you in two weeks. Until then, take care. If you're coming to Fostom, stop by the Jenkins booth, we'll be there. And we look forward to seeing everyone at the conference and the summit. Thank you very much and take care. Thank you. Bye. Bye-bye.