 Hello, welcome to the Jenkins documentation office hours. This is today is February 22nd. This is the EU US edition. And today, at this point, we have myself, Kevin Martins, and Bruno Roche in joining as well. If anyone shows up during the session, we'll welcome them in as always. Otherwise, we'll go over the agenda and go from there. And so on the agenda, so we had the latest LTS release yesterday, version 2.440.1, Contributor Summit and FOSTA recap, some notes about Google Summer of Code, housekeeping about Asia Docs Office Hours, Jenkins Community Awards. I wanted to note the JIRA upgrade for issues.jankins.io. It might not be something that directly affects documentation in the moment, but this is something that's important for everyone in the community to be aware of. Version documentation for Jenkins.io, just some updates there. And maybe in Python tutorial revamps have been merged. Now, we're looking at next steps, the admin password reset instructions, and sponsors attributions, basically just making sure that we have sponsor page and where that's at. Anything else that you want to throw on the agenda, Bruno, while we're here? No, I'm going to thank you. Yeah. OK, great. So starting off, so again, yesterday was the latest baseline LTS release. So 2.440.1, that's the start of a new baseline. Thanks to everyone that helped out with the release itself. The release went well. No issues with the Jenkins core release. There were some issues with the upgrade guide, which may have messed up the Jenkins.io builds. But thanks to Kristen and Damian de Porta, they were able to recognize and find the issue, resolve it, take care of things very quickly and efficiently and got everything squared away so that the release and everything else could go out accordingly. So there's no issues now. They've been addressed. But as a result, we're going to make sure, or I'm going to make sure that going forward, the upgrade guide has a screenshot included, as well as the change a lot. So learning experience, yeah, we'll do our best to make sure that everything goes smoothly from here on out. Contributor Summit Fosden Recap stuff. So I'm working on a blog post right now. I've got a Google Doc started and shared around with the other officers and community team members to just, if they have any insights or content they want to share, add, put in there, make sure it's made available, et cetera. But right now, I'm looking to publish it probably sometime between tomorrow and Monday, depending on what kind of actions we're getting. If no one's adding anything, that's OK. They don't need to. We have enough content there. I just wanted to give everyone a chance to add their two cents if they have it. That's all. So yeah, more to come on that probably within the next few days that will be published, though. In terms of Google Summer of Code, so we got confirmation that Jenkins has been accepted as a Google Summer of Code organization. So super excited about that. Really great to see. It's another chapter in the journey that we've been on with Google Summer of Code now for the last, well, we've been doing it for a while now. So really, really excited to continue that. We're going to have a blog post for that announcement. And we'll update the carousel on the website with that information as well. So more to come on that. But just to usher in the coming session, so we've got that approval. We just had an online meetup this past Tuesday to go over some of the project ideas. We're going to have another one either this coming today or it is definitely this Tuesday, Bruno. OK. Yeah, yeah, I think so. OK, cool. So we'll have another meeting this Tuesday to go over the other ideas. Mentors will be there to help provide some insights there. Yeah, anything else on Google Summer of Code to write down, Bruno? No, we have quite a few contestants, I would say potential contributors. So there is a lot of activity on GitHub and even on community.genkit.io. That's a joy to see so many young people wanting to contribute in a way or another. I think we have something like 11 projects to these days. In fact, these are not projects, but just project ideas. And then we'll receive the proposals from the potential contributors. And then we'll assess them. And in the end, we will know how many projects we will keep. If ever we manage to mix and match contributors, mentors, commenters, everything. So it's not over yet. So if you're watching this video, please have a look at what's going on community.genkit.io on genkit.io itself on the documentation website because the ideas are exposed there on GitHub. Why not? So yes, welcome to the party. Great. Thank you so much, Bruno. Yeah, and it's just it's really exciting time. We're getting ready for all that. And now that we've got the official organization acceptance, it's just a matter of getting everything, all the pieces together for the rest of it. So fantastic. Thank you very much. Housekeeping notes. So Docs Office Hours Asia, the next one is going to be on March 15th. So it is canceled for later on today, this evening, tomorrow morning, whatever it might be for you, the March 1st session and the March 8th session. So for the next three sessions, Asia Docs Office Hours is canceled. Mark is away, so there won't be an available host at that point. Next up, so the Jenkins Community Awards have been announced. The nomination period just closed. They were opened until February 19th, which was Friday, or no, that would have been Monday. So they were open until Monday. We've got plenty of contributor and after-kit nominations. So just thanks to everyone who nominated someone, thanks to everyone that's been nominated. You wouldn't have been nominated if you hadn't done some kind of work for or contributions to the Jenkins Project. So just great, great, great to see all the efforts and work being noted, appreciated, and highlighted, and frankly, celebrated like they should be. It's just great to see the community coming together for that. So voting is actually open starting today until March 22nd. So for the next month, we can vote. And you can vote in any of the pinned issues. So if you go to Jenkins.io and go to the issues, the three pinned issues here are the three community awards. And you can vote by going in, finding a nomination here, and clicking the little icon here, the thumbs up, or there might be a rocket ship. There could be any number of emojis. Definitely just pick one, vote, make sure it'll most likely end up being that this number here is counted towards whatever the highest number there is, and that's the winner of the award. You can vote as many times as you want, technically speaking, because you can click multiple emojis. You can vote on every one of the awards. You are not limited in any sense in that way. And there is also the overall CDF awards. That's something that you can also you can vote for any of these as well. And it's the same process for the CDF awards themselves. They've got an issue. You go in, react with an emoji, and you vote it. So over the next month, take a moment. When you have time, check out the CDF awards page itself. We have an announcement blog post in the Jenkins.io blog. And again, the issues are pinned in the Jenkins.io to get Hub repo. Take a moment, vote, share your appreciation, and show these people that their work matters. Next up, there's the JIRA upgrade for issues.jenkins.io. So this is something that's been put out. This is something that's been discussed in the governance board. So this is a page that's available on the Linux Foundation site. So it is out there in the public. But on March 12th to the 13th, the JIRA, there's gonna be a JIRA upgrade for issues.jenkins.io. The site will be unavailable during that time, but we're hoping that it shouldn't affect too much in terms of downtime. It's supposed to only be a couple hours, a few hours, so it shouldn't be disruptive. That is, of course, best case scenario and provided nothing interrupts or causes a problem. So ideally, it's only gonna be a few hours long. Otherwise, that status page will be updated accordingly. And I'm sure we'll communicate that out somehow. In the version documentation site, the alternative build tools for jenkins.io. So this has been a constant discussion that we've been having for some time now. It was delayed a little bit from going into, from being pushed into production due to Azure cost-saving measures. So that's still being worked on. That's a higher priority at this point. So once that's addressed or in a better place, we'll come back to pushing this towards being a part of the live infrastructure. But right now we're reviewing, we're making sure that everything works appropriately on the Docs, the version doc site. And then just this week, Chris Stern and myself were able to meet with Daniel Beck. Daniel's part of the Jenkins security team for anyone that's not aware. But we also want to make sure that their needs are met as well. While the version doc site is great for users in terms of the documentation, tutorials, et cetera, et cetera, security advisories and security as a whole is a large part of the Jenkins documentation and site. So Daniel wanted to make sure that when moving to the version site, we're not gonna have any sort of degradation and quality in terms of publishing security advisories, in terms of the load response time, in terms of a lot of the backend stuff that I just personally didn't have the answers for. So we met with Chris as well, who's been able to provide insight to a lot of that stuff and more importantly than anything else, give reassurance to Daniel Beck and the security team to let them know like why this is a good move and what kind of benefits they'll see from it. So I think one of the things that we talked about towards the end of the session was how long it takes from him pushing a commit and how long it shows up on the site and it's like eight minutes or something. Gatsby and Tora, that's gonna be cut in half realistically speaking. Just the power alone, it's... Or go ahead Bruno, sorry. No, no, no, sorry to interrupt. I would just to say that's interesting getting to have the time of the generation. That's pretty cool. Yeah, from our... No, that's a rough estimate. That's not something that we did right there in the session to prove, but Chris is saying that roughly three to four minutes instead of eight minutes is what they were seeing with their testing and everything. The specific action that Daniel was taking, it might go through a different process steps. Something might be a little different about that. So it's tough to say if that would exactly be the case, but even if it's down from eight to six or like eight to five, even if it's not fully half, that's still a lot faster than it was. And the main concern for security is obviously making sure that the user gets the information as quickly as possible. So anything better than eight minutes is a win in that case. As long as it wasn't slower. Yeah, I was also thinking along the lines of time is money. And it's true for Jenkins, because the minutes that we're using in the cloud cost us some money. So if we are faster, it is better. Definitely. So yeah, so thanks so very much to Chris Stern and Von Dietzing for their work on the version doc site. Thanks to Chris for being able to meet with us yesterday and just being able to showcase the version doc site and what benefits that will bring to other parts of the project beyond just documentation. So thank you very much. And then Daniel Beck actually had an interesting idea. I put it in here because he did submit it as a pull request, but he suggested having separate pages created for, basically when a changelog is created instead of there being an anchor link that goes to the full changelog having a separately generated page for just that changelog entry. So if someone links to 2.440.1, they don't need the rest of the changelog. They just want to have that. And right now the way it's working is you set the link and it brings you the full changelog. So the whole thing gets rendered. His suggestion was instead of that having something like this where it's literally just that version changelog. It's a lot more focused experience. It gives the user exactly what they're looking for as opposed to the noise above and below. So I think it's a really neat idea. And I can see exactly why this would be value and appreciate the simplicity and like the directness of it. And for all intents and purposes, I think that makes a lot of sense for the changelog and for what people are potentially using it for. It's not going to be a cover all answer and it's not going to necessarily be the right solution for every single case or every usage. But I think it's a great idea and it aligns with something else that Daniel had mentioned which was creating a separate page for like each security advisory kind of in a similar vein where they wouldn't have to necessarily have one longer page for all of the advisories that might be getting discussed at once. So yeah, if Antora, if Gatsby can handle this sort of thing, I think it's a really good idea. Any thoughts or feelings on the first impression, Bruno? No, I'm on the same line of thought. That would be cool that won't answer each and every kind of question people may have when they want to use the changelog. But if it's cheaper, faster and it answers, it's a response to an issue that people are dealing with nowadays. That's cool. Thank you, Daniel. Yeah, no, thanks to Daniel again for asking questions and sharing the thoughts and concerns about this sort of stuff as we're getting ready to push it forward. It's good to have that insight and we wanna make sure that the security team is fully on board with all of this, of course. They're gonna be using it and we need to make sure that security and everything is very clear and consistent and available for everyone using Jenkins. So yeah, just thanks again to the security team at Leville for all their work in general and for working with us on this. Next up, the Maven and Python tutorials. So again, these have been revamped thanks to Bruno integrating Docker Compose instructions into them. Thank you so much for all of the work on that, Bruno. Right now he's working on the Node.js tutorial. So that one's been submitted. I need to go and review that. And then once we get through this, we're gonna, well, we'll have to partner up and Bruno will show me a little bit of what I need to do so I can incorporate that into the installation docs for Docker. The ultimate goal is to have the Docker Compose integrated into the documentation as a whole. So the tutorials are a great place to start. It's lower, less invasive than the installation docs. So that's the big step there. Yeah, and it's definitely useful. This week on GitHub, there was one user who was having trouble starting Jenkins with Docker with the official documentation. And I asked him if he could try the Maven tutorial just in case that would help him getting started. And he tried it and it worked for him. So he's now up and running and he will be able to work on the weekend because he knows nothing about Jenkins. But now he has a working Jenkins instance with just one Git clone command and Docker Compose of minus the Maven. Boom, it's working. And frankly, it's heartwarming that what we're doing is useful to some people and will help newcomers into Jenkins community. Before tackling with main installation tutorial for Jenkins and Docker because this one may take us quite a lot of time, there is still one tutorial to work on which is the multi-branch pipeline. So I should start it tomorrow. And then whenever you and me have some time in common we will work on the installation of Jenkins through Docker tutorial. We'll do what we can. Yeah. And I figure at this point, Bruno, the, you know, this, you know, I put eventually here for the Docker Compose because I don't think it'll be something that happens prior to April. Of course. So there's a lot going on in the next few weeks between Mark being gone, I'll be gone for a little bit. Just other things that are happening for everyone. Everyone, like there's a lot of stuff going on. Google Summer Code is ramping up. So yeah. No hurry. Yeah, it's an eventual project, but it will, it will happen eventually for sure. Yeah, someday. Yeah. Next up, so the password reset for admins this is something that we talked about last week. I've reviewed everything was good, the steps work, we merged that. So we now have the password reset instructions for administrators in the Jenkins documentation. Thanks to Shridhar for putting that together. And it's admitting that. And then last thing on the agenda is the sponsor attributions page. Discussions ongoing here. Nothing's really changed since the last we spoke. It's an ongoing process and work. Basil Crows created a draft of this and he's still working on that. We just needed to get some better details about things like monetary donations versus services that are being donated, what those kind of stack up, how those stack up against each other, et cetera, et cetera. But Basil is gonna be continuing to work on that. Digital Ocean has been donating for 2023 and has donated for 2024. So they should definitely be visible. AWS has donated $60,000 of credit towards Jenkins, which is amazing. So we have a lot of sponsorships and partnerships that we wanna highlight and make sure are attributed correctly and appropriately on that page. So we wanna come on that. Thanks to all of our sponsors constantly providing us with the means of giving the lights on for Jenkins and pushing forward with Jenkins, keeping us on the cutting edge of everything that we're doing. And so just thank you very much to all of them. Go ahead, Bruno. And we now have another kind of sponsor. I don't know if it's a new category or something, but as you may know, Ampere has given to the Jenkins project two ARM 64 servers. So I don't know how this kind of donation will suit in the existing categories or if we should create another category. Time will tell. That's a good call out, Bruno. We do, is that now for clarification, is this a new sponsorship as of the server donation or have we been working with Ampere for a while now? And this is just a different kind of sponsorship that they're providing. No, in fact, it's the first time we've ever been working with Ampere. And when I say donating, that's not really the truth. It's some kind of loan, but without an end date. So yeah, we could use them as long as we want to. So it's not really a donation in itself. I don't know the exact term, but you get it. And yes, it's the first time in 2024. We've been discussing that for about a year now, but the server has finally reached Mark's house. Well, great. So that's cool just to highlight the working relationship and the bonds that we're creating are showing results. That's fantastic. Yeah, the cool guys, Ampere. Yeah, well, they were, I know that on the Sunday of Fosdom, the gentleman in Mark were talking a lot. Ampere. Yeah, yeah. Aaron, if you see us, hello. Aaron, thanks again. Appreciate everything. Cool. All right. So that covers everything that I have on the agenda for today. I don't think I left anything off there and I'm pretty positive I covered everything that we had talked about earlier. Yeah, yeah, everything's good. So on that note, I'll go ahead and stop the recording in just a moment. It'll be available 24 to 48 hours. And yeah, we'll see you next week. Until then, take care, stay safe and reach out through community.jenkins.io or the Gitter channel. If you have any questions about docs or Jenkins in general, you can find us there. Take care and have a good weekend. Bye. Bye-bye. Well, though. Okay.