 Hello, welcome to the Jenkins documentation office hours. Today is February 29th, Happy Leap Day. And around the table, we have myself, Kevin Martins, and Bruno Vrachtin joining us today. For the agenda, so just check in on the LTS release last week, this week's weekly release, the Contributor Fossum Recap blog post, some notes on Google Summer of Code. The Jenkins Community Awards are the voting periods now open, so notes on that. Housekeeping for Docs Office Hours Asia. And then the GRO upgrade for issues.jengens.io, something that's coming up that we've noted last week, some discussion on the version documentation site, the tutorial revamps to use Doc Compose, and the sponsor attribution page. Anything else that you want to make sure we put on the agenda for today, Bruno, or does that cover all your topics? Exactly, nothing more from me, thank you. OK, thank you. So starting off, so again, Happy Leap Day, February 29th, only happens once every four years, so that's fun. We get to meet today. Last week, we had the new baseline LTS release, so 2.440.1, so everything went well there. There were no issues with the release itself. The upgraded guide did have some content that caused some issues with the Jenkins.io build, but Damian was able to resolve that, take care of all that, address that accordingly, so now everything went through. Being going forward with the upgrade guide is going to have screenshots in the TR as well as the change log. So there was some code in there from the remoting update that ended up causing some issues, so it happens. No worries, like I said, we were able to fix it and then get everything going and rendered and published properly, so everything is good to go there. Welcome to Chris Stern. Thanks for joining. And then, so this week, we had the weekly 2.447 release, that went well, everything went through there, and everything, yeah, the release went smoothly, change logs been published, everything is good to go there. Next up on the agenda, so we were able to put together and publish the Jenkins contributor summit in positive recap. So thanks to everyone who joined, participated, Fosdum, the contributor summit, et cetera, everything in general that weekend, what a great turnout, and yeah, we're just happy to be able to share some of these similar experience with everyone, the memories and some of the photos from the event as well. So this was finally published yesterday. We had a, there was an issue where I had, I thought I had updated the file path for the images to coincide with the release, the publication date. There was an issue, so we had some broken images for a bit there, but thanks to Tim Jacome for approving my pull request, we were able to get that resolved, and so now the blog posts appear as properly. In the blog posts, I just wanted to call these things out. So one is we did include the contributor summit presentation slide deck, so if you wanted to view it, you have that option to do so here, and that way you can follow along with the blog post itself. It was oriented in a way that it matches the presentation slide deck, so that it should come in the follow suit. And just a really, really huge thank you to BetaCo work for providing the space for the contributor summit. Jean-Marc Missin went and was able to collaborate with them, partner up with them, get a room for the contributor summit and just make it possible in the first place. So huge thanks to BetaCo work for that and Jean-Marc for organizing it, and Jean-Marc has gone and followed up with them as well for next year, which is great. Jean-Marc may not be part of CloudBees as that organization, but he'll be part of Jenkins still going forward. Jean-Marc's retiring this summer, so we'll miss him around in different parts, but he'll still be active in the community at different points, so yeah. But yeah, the contributor summit was great, just really still riding that high for a lot of us, I think, and yeah, just really fun experience. And so now everyone can take a look and see what that might have looked like for us. Next up on the agenda, so the Google Summer of Code, over the last two weeks, we've had Jenkins online meetups to go over the project ideas in more detail. So I think the first week, the first five were discussed and then the second week, the rest of them were overviewed. Bruno, Chris, any notes, insights you'd like to share on the Google Summer of Code and where we're at or what kind of has been going on the last couple of weeks? Please go ahead if you don't mind. Oh, I have a correction to make. We now have nine portrait ideas in step 11 because we have to focus on the ones that will mostly be more successful than the others. Yeah, no, that makes total sense, Chris. Thanks for clarifying that, appreciate it. And obviously with the Google Summer of Code, we want to invite new contributors to join projects, but we also want to make sure that the work being done is useful and relative to the project itself. And so by focusing on these better quality, higher chance of success projects, that's going to create a better environment for the contributors, the mentors, or the admins, everyone involved. And it's a lot more likely that the projects will finish and finish successfully, which is really what we want most out of this to not only give that experience to everyone involved, but the work that's being done have it be incorporated into the project itself. So great there, lots of Gitter activity has been going on, lots of chatting, lots of responding, lots of welcoming people into the organization. I know we had a couple of new mentors add their profiles to the project, so that's really exciting as well. So yeah, we have two contributors from last year, we turned as mentors this year. That's fantastic. And then Chris, do you know who they are off the top of your head? Yeah, one is, I think it's, I don't remember the full name, but his name is Harsh, one is Harsh, the other one's Harsh. Yeah, Anna Vendit Singh. Oh, they're both his things. Yeah, so Harsh Singh and Vendit Singh. Yeah, great, and that's good. I'm glad to see Vendit back. I know you guys have both been working on the version documentation stuff for Jenkins and Vendit's been a great contributor. So really nice to see both him and Harsh back, fantastic. Yep, great. So lots of stuff there. Oh, I skimmed over this. So Jenkins has been accepted as an official Google Summer of Code organization. Alyssa and John Mark put together a blog post announcing it, and we also have on the Jenkins site itself an update to the carousel. So we now have the Google Summer of Code 2024 here as well. So communications have been sent out, lots of good information in the blog post as well, key timeline, key information for contributors, lots of just really, really important information here, and also links to the Call for Mentors blog post, couple other items that are crucial for any potential contributors or participants. Great, thank you so much, Chris, appreciate it. Next up, the Jenkins Community Awards. So this has been, we announced this a little while back. Alyssa wrote a blog post for it at the end of January. We have three Jenkins project awards, so the most valuable contributor advocate and the security MVP. So last week before the, or during office hours, I had mentioned that there's a voting process involving the reactions to each nomination. However, that's since been changed. We actually have a dedicated voting forum for the Jenkins Awards. So that is linked in the blog post. It's also linked here in the agenda, but this is where you would actually want to go and vote for the Jenkins Awards. You can only vote once, but everything will be tallied on March 22nd or after March 22nd when the voting period ends, and then winners announced in CDCon 2024, as they were last year. So we've got a handful of nominees for each of them. Security MVP, there's only a couple of nominees, but they're very high-quality nominees. So I can't go wrong there. Most valuable Jenkins advocate and contributor, again, all very high-quality nominees and candidates, there's no wrong answer here whatsoever. And so the voting period opened on the 22nd of February. It goes until the 22nd of March. There's also a voting forum for the Non-Jenkins Awards. I only bring this up as much as it pains me to say, because I've been nominated for the Documentation Award. So if you wanna vote for me, you can. This feels awkward, so I'm just gonna stop advocating there. But yeah, so the community awards are really important. We want to show people that what they do really makes a difference, and what a great way to do it. Next documentation office hours for Asia specifically. So last week's was canceled, this week's is gonna be canceled, and then next week's will be canceled as well. Mark is currently away and not able to host. So for the next week as well, I'll be here for all your documentation needs. And then I will be gone for a couple of weeks after that. Mark will host the EU-US office hours as well. So no interruption on the EU-US office hours for the next month. Something that we wanna note, and make sure everyone's aware of, is that for March 12th, there's gonna be a JIRA upgrade for issues.Jenkins.io. The service will be unavailable for a period of time. However, we're hoping that's a minimal period of time. You can see here the idea if it's only a couple of hours. So if everything goes well and there's no issues or hiccups, that should be the case. And there will be further updates. You can subscribe to updates if you want to get be updated constantly, when there are updates for this. But yeah, just something to note, something to be aware of, that there will be a couple hours of downtime for issues.Jenkins.io. And then next up on the agenda, so the version documentation for Jenkins.io. Again, just to recap, this is the result of a Google Summer of Code 2023 project of looking to build Jenkins.io with an alternative build tool. It's been decided that we're gonna be using a combination of Antora and Gatsby. And so Chris Stern, Vandeet Singh, others, myself, we've all been working on this in different ways. Chris and Vandeet have been doing the bulk of the work. I've been helping to review things now that it's at a point to do so. And everything looks really nice there. The transition from one to the other has been really nice. We're not ready to push it into the infrastructure fully yet because of Azure cost saving measures that we're looking at. But once we have a confirmation that that's a bit more under control, this will be coming right back to the forefront of what we're looking to do next. Chris and I were also able to meet with Daniel Beck last week from the Jenkins security team to go over some concerns that they had or things that they want to make sure of in regards to security advisories. Everything went really well with that. I think Chris was able to give a lot of reassurance to Daniel Beck and make sure that they understand why these changes are coming and why they're a good thing. Stuff like making sure that their frameworks kind of still work for the most part, reassuring them that there's not gonna be an increase in time between pushing commits and having them be published, which is, I think we actually went the other way on that. It's gonna take less time, which is really fantastic news and really definitely put a smile on Daniel's face even if we didn't see it. And then Daniel also had created a pull request to inquire about individual pages being generated for the change log entries. So ideally, what would it be is instead of having an anchor link that goes directly to the full change log, but singling out the section that you're looking for, it would instead create a separate page for each change log or versions change log. So they would just be for the 2.426.3, for instance, it would just be those entries on the page. It wouldn't be the full list of change log entries. So that could cut down on time in just terms of rendering and displaying the page that removes unnecessary information that the person may not be looking for. If they're looking for specific version change log, we can give that to them directly. And that's a really nice idea, I think, as long as it's not adding to any kind of cost or any of the backend stuff that I'm not fully aware of, it sounds like a great idea. And Mark was actually able to review and comment as well, saying as much, so it does seem like it's a good idea and everyone's on board with that. So it's just more a matter of implementation and whether or not that's possible or what that might look like. So, yeah, more to come with that. It's right now, it's just a draft, so nothing's gonna be changing or happening immediately, but something to look forward to at some point in the future. Next up, so we've been talking about the Maven and Python tutorials, getting revamped to use Docker Compose, and now we can factually include the Node.js tutorial in that as well. It has been revamped, it has been merged, and now we're using Docker Compose in all three tutorials, which is fantastic. Thanks to Bruno and Harsh for their work on this and getting this across the finish line from Google Summer Coat 2023 as well. And Bruno was actually able to confirm last week or the week prior that the Maven tutorials have actually helped the user get started. So that's really fantastic news, the Docker Compose instructions are being proven to work and confirming that we made the right choice here. Bruno, any other insights, notes, comments on that stuff? Not really, except thank you for the detailed reviews. And yes, I'm working on the multi-brunch pipeline next. There are a few more changes that for the previous tutorials because it doesn't work as is, even in its current form. There are some errors here and there, so I will maybe have to make a few changes and even use a sample itself. We are basing our tutorial on another repo with React code and it's not working as is for the time being because things have changed. We have to update some dependencies and so on, but that will be okay. I hope that next week I will be able to have a draft PR with the working tutorial, at least on my machine. And then we'll see. I'm not really fluent with React, so a node and all those JavaScript stuff. So I hope it will work for other people too. Great, thank you very much. And I know Alex Brandes has also been reviewing and approving a lot of these too, which has been great. Having Alex's knowledge on that is really helpful because I know the documentation side of things and I can test, but yeah, having multiple people with different backgrounds and skill sets looking at these things really helps make sure that we're, it's a complete, complete revamp, if that's what we're going for, that everything is done accordingly. So yeah, really fantastic, great to see. I'm sure I'll keep an eye out for that Bruno. And yeah, hopefully it's just as easy. Yeah. Thank you, Gaby. And then eventually down the line, soon and later, the goal is that we incorporate the Docker compose instructions into the installation documentation and make sure that we're simplifying things as much as possible right now. The Docker and Docker is a lot more complicated and not nearly as secure. So the Docker compose actually resolves those issues and those concerns, so just makes sense. All right, and then the last thing on the agenda that I have for today is the sponsor attributions page that we've been discussing. It hasn't had any further development done this week or anything since our last session, but now that Basil's returned and able to start working on this again, there'll be some movement in there eventually. But the idea is that JFrog asked about being credited as a sponsor for Jenkins, which yeah, they deserve that. They are, that makes sense. But we wanna make sure that they're getting the correct sponsorship attribution. We have sponsors of varying levels, different amounts of donations in terms of services versus monetary versus credits towards up. There's a lot of different levels and aspects to the sponsorship that we have. And so we wanna make sure that we're doing our due diligence when we go to make this page. Basil Crow's created a draft of this page and the way it works is it's set up in a handful of different levels going from anchor, which would be like the most crucial sponsors of Jenkins to mirrors where there are sponsors of Jenkins that are simply providing mirrors and that's great, we need those mirrors, but it's a different kind of donation or sponsorship than say, yeah, what the anchor would be in this case or gold where it's something like AWS or CloudBees where they're donating significant credits or services or support in any way, shape or form to Jenkins. So we have that information though, which is really great. So Basil can start looking through that and working with the rest of the government support to determine what that might look like, what the sponsor attribution should be and how that's gonna kind of shake out on the page itself. Some recent donations that we wanna call out especially and thank AWS has donated 60,000 credits to Jenkins. That's amazing. Thanks AWS for their continued support. DigitalOcean has donated in 2023 and 2024, more to come on that, but their donations are always hugely impactful. Microsoft's donated to Jenkins, which is great to see and Ampere has recently donated to ARM64 servers. Right now they're at Mark Wade's house because that's where we have to store them. But this is the first time sponsorship with Ampere. This has been in the works for about a year or so. Thanks to Bruno and Mark for facilitating the sponsorship and the partnership. I think, I forget what the gentleman's name is, but. Aaron Williams. Okay, so one more time Bruno, sorry, I missed the first. Aaron Williams and Dave Neary. Okay, so. Together with Ampere I am in contact with. Cool, perfect. So yeah, so, and then was Aaron the person at Fostum? Yes, he did. Okay, so yeah, so Aaron was at Fostum. It had a very long conversation on Sunday with Bruno and Mark, mostly Mark, about the servers and just Jenkins in general. So just thank you very, very much to Aaron and Dave and Ampere for their sponsorship, for their collaboration, for just everything up to this point with this really great to be part of the team and yeah, just be involved, be collaborating with these folks. So yeah, everything is going pretty well. Everything's looking good. Jenkins is really healthy right now. We're seeing a lot of growth and a lot of contributions coming through. Google Summer Code 2024 is on the horizon and lots of other great stuff is coming. So I think it's gonna be a great year for Jenkins overall. And on that note, we've reached the end of the agenda. So we'll go ahead and wrap up the meeting. Recording will be available in about 24 to 48 hours, maybe sooner depending on when I get that posted. But yeah, we'll see you next week. Take care, stay safe. Thank you as always for joining and contributing. And if you have questions, definitely reach out in the DocsGitter channel or on community.jankins.io if you have other topics you'd like to discuss. Until then, take care. We'll see you next week. And have a good rest of your day. Bye now. Bye bye.