 Hello, welcome to the Jenkins documentation office hours. Today is March 7th, and this is the US edition. At the moment around the table, we have myself, Kevin Martens, Bruno Verakhtin, and Pranav Singh. Welcome, Bruno and Pranav. Appreciate you being here. And if anyone else joins, we'll welcome them in, of course, as always. And yeah, we're recording, so the video will be available afterwards as well. For today's agenda, I thought we'd touch on the next LTS release, which is 2.440.2, the latest contributor spotlight publication, weekly release for this week. Yesterday, we had a security advisory, so I want to make sure we note that down. Just another reminder about the contributor summit recap, some notes on Google Summer of Code, the Jenkins Community Awards, just again, noting the JIRA upgrade for issues.jenkins.io, some housekeeping regarding Asia Docs Office Hours, the version documentation for Jenkins.io, the tutorial revamps to use Docker Compose, and lastly, on the agenda, I have the sponsor attributions page, which we've been discussing. Is there anything other topics that we want to make sure we touch on or discuss today in Docs Office Hours? I'll think from my side. Thank you, Kevin. OK, so first up on the agenda, again, so on March 20th, we anticipate the release of Jenkins LTS 2.440.2. The back ports were just made available on Tuesday. I've already created the change log and upgrade guide pull request here, so I do want to just touch on this real quickly. But it's not a large change log and upgrade guide this time around. However, there were a couple of different updates that I've been touching based on with Basil Crow about. Specifically, there were two Jakarta plug-in updates. The activation and email APIs were both updated. If they're not updated at the same time or one after another immediately, there is going to be a breaking change. Similarly, there was an open JDK update in the upstream that's also caused a breaking change. So I wanted to make sure that we alert users to these things. So I'm including them in the upgrade guide. As you can see here, I've added in a note stating that these updates are not specific to the LTS release, but they've happened in the last week and they are crucial, so I do want to make sure they're included in the upgrade guide. This was the original version of it that I took a screenshot of. But I've updated it since to put that note at the very top of the upgrade guide for 2.2. I don't want to have any confusion, so it's probably best that it starts it off and then change the updates to upgrades since it's the upgrade guide, not the update guide. So just a couple of things to note there. This is, like I said, it's ready for review. And I will be unavailable for the next two weeks. So in the meantime, Markweight will be available to check on a couple of things and handle some things for me. So like Docs Office Hours, when he's available, stuff like that, and reviewing the upgrade guide before merging it for the actual release. So yeah, just to put on your radar, like I said, it's ready for review. I'm open to as much review as possible. I will be here or I will be available for the next 24 hours still. So I'm still available and can help with anything and make any updates needed. And then just a small note here. So as a result of the upgrade guide for the .1 release, including some code that ended up causing some issues, we're just making sure the upgrade guide and the change log both have screenshots to make sure that they're both rendering and loading properly. So something to see from here on out. Next up on the agenda, so again, we've had our contributor Spotlight going for a few months now. Yesterday, we published Stefan Speaker's Spotlight. So thanks to Stefan for collaborating and providing his insights. It's a really great story. And Stefan's a really wonderful contributor. It was really nice meeting him in Brussels at Fosdham and the contributor summit. So just thanks for being part of the community, Stefan. And yeah, if you have a chance, check that out and learn more about Stefan. The weekly 2.448 was released successfully on Tuesday. If I recall, there might have been some issues in the back end of things, but everything went smoothly, the release went well. There were just a couple of pickups that needed to be addressed, I guess, on the back end, but nothing serious or worth noting here. There was a security advisory published yesterday. So thanks to Jenkins security team for all of their work on resolving these things, taking care of the advisories, publishing these things. Really, really great to have that be part of the process. And it was specifically for plugins. This did not affect Jenkins core. And so as such, the weekly changelog is just the weekly changelog for 2.448. It was not a security release in that sense. So yeah, just something to be aware of there. So we published our contributor summit in Fosdham recap just on the 28th of February. So just about a week ago now. Just a nice recap here that I was able to write up going through the presentation. We've got a link to the slide deck here so you can review it and read through it, follow along. And just, yeah, just really nice experience. Thanks to everyone for their contributions, for joining, for participating, for coming to Fosdham, for just everything. What a great experience and what a wonderful contributor summit we were able to have. Next up for the Google Summer of Code. So just a couple of weeks ago, we were officially accepted as a GSOC organization. So we have a blog post in the carousel on Jenkins.io has been updated to reflect that. We have nine draft proposals thus far. We've got a couple of returning GSOC contributors now as mentors in Harsh and Vandeet Singh. So thanks to them for coming back and joining. And we've also got a new mentor from Lara. So welcome to Lara. And thanks for joining up. Appreciate it. Really great to see new folks coming and joining the project and participating in Google Summer of Code specifically. The contributor application period is gonna start on March 18th. So a couple of weeks from now. And then the application period's gonna end on April 2nd. So be aware of those timelines. The blog post that Alyssa and Jean-Marc have put together has a lot of the information and timelines and key dates in there as well. So this is really crucial. This is a great place to just keep track of things, get that information. There's also the Gitter channels. We're very, very active in the Gitter channels at this point in time. Lots of activity. Chris Stern is one of the org admins and has been replying to everyone that they possibly can and doing all the work they possibly can. So thanks to Chris for everything that they do because it's not just limited to Google Summer of Code. But yeah, just a lot of great actions are being taken, a lot of activity. We're getting submissions. There's still plenty of time to work on these things but things are looking good here. Bruno, any notes on GSOC that you wanna share? Any insights that I maybe missed? No, nothing really important. We have begun the review of the nine first proposals. So it's not yet official. It's some kind of discussion between the contributors and the mentors. So we are reviewing the proposals and telling them, sometimes you have to dig deeper or it should be more precise or this is a good idea. It should be more developed and so on. So it's nothing official for time being. It's just a time where we give some advice to the contributors with their first proposals. Not all of the projects have received a proposal yet. I think, for example, of Valentin de Lé project about open rewrite recipes for Jenkins. And there is a lot of activity in the GitHub channels regarding this project but not a proposal has been submitted yet. Which is a good thing because I think that potential contributors are working on their proposal. If you want to get good proposals, of course people have to spend some time on crafting them. So all is good, we're still on time. You can also onboard new potential contributors. We still have plenty of time for that but I would just give an advice to potential contributors, take your time, build your Jenkins muscles. Yeah, take your time, do something good. Yeah, take your time. Sorry, I'm repeating myself but take your time, do something good and that will be better for the whole community. Great, thank you very much Bruno. And I think it's nice that we're getting that activity in the GitHub channel. People are curious, they're interested. That shows a lot of initiative from the contributors and from mentors like this is just, that's great to see even if the numbers are not necessarily as high as we had hoped for, it's quality, quality, quality, quality. We're only gonna have so many projects anyway so we're gonna end up filtering some things down but that excitement, that interest, that activity is huge and really shows just how important, not only Jenkins but Google Summer of Code participation for the organization is huge. It is. Great, cool. Thank you very much Bruno. And oh, are there any scheduled meetups coming up that we should note or is it, we're kind of like figuring things out and that will alert everyone when we have the next meetup scheduled? Yeah, I don't think we have a date scheduled. Yeah, no, not yet. It will come when it will come, I guess. We presented, I think, most of the projects in the last two meetings. There are still one or two projects, I guess, but nobody showed interest for them so I think it will stay as is. So no, no meeting scheduled for the time being. Okay, great. Thank you very much Bruno. Next up on the agenda, so the Jenkins Community Awards, this was announced recently enough towards the end of January, yeah. So the nomination periods have closed but the voting period has been open from the 22nd of February. It's open till March 22nd. So if you have the time or if you have, if you wanna check out the candidates, you can go to the individual award issues here. Each one will take you to the pinnedissue in Jenkins.io's GitHub repository where you can see the nominations and then there is a voting form that's available and this is also in the announcement blog post that Alyssa put together. So you can access the voting form from either one but it's gonna be a voting form specifically for the Jenkins contributor awards 2024. The voting period, like I said, we'll go to March 22nd and then the winners will be announced and awarded at CD-Con this year, which is in April. I wanna say 18th to 20th, they're 21st. I forget exactly what the end date is but yeah. So same as last year, last year's winners cannot win again this year. So the nominations are a little different and then there's also a voting form for the complete CDF awards outside of Jenkins project. So this is where they'll have CDF ambassadors, contributors, stuff like that. Mark, Wade, did decide to nominate me here for top documenter. So if you wanna vote for me, what's that for? Vote for Kevin. Yeah, you can do that. I don't wanna talk about myself but we've been over this. So that's the thing, you can vote if you want to. I would appreciate it. I don't know if I have to go to CD-Con at that point but we'll see if that's if I'm a winner. And Kevin, sorry to interrupt, just one question. I know who can vote for the Jenkins awards. You just have to be a contributor in a way or another. But what about the other ones, the CDF one, who can vote? That's a great question. And I'm sure the CDF foundation would be more excited if they are all project contributors, Jenkins, Tecton. I don't think that part matters as long as someone's a contributor to open source in some way, shape or form. I think that's more their concern but they advise that there's some kind of connection but I mean, if people are coming to this meeting, they're interested in some part of open source. So I would hope that there's some connection there. So let's see if we can vote. That's okay. I think as long as you vote for Kevin, you're allowed to vote. Yeah, that's exactly what we're going for. No, I think it's just a matter of as long as you're part of the open source community, you have every right to vote in open source presentation or whatever that might be. So yeah, next up. So JIRA Upgrade for Issues.Jenkins.IO, this is the status page to let everyone know that there's gonna be some downtime on March 12th from 11 p.m. UTC to 2 a.m. UTC. So it will be down for a few hours but the upgrade shouldn't, this shouldn't cause any sort of disruption in service or anything along those lines. This is specifically for your issues.Jenkins.IO. So users of Jenkins shouldn't run into any problems or anything like that. It'll just be more if you're trying to report bugs or anything along those lines. And so this will happen. This is really just to note, be aware of it. There will be more communications as we get closer to it, maybe an email blast, but yeah, just I'm gonna be aware of and keep in mind shouldn't have too much direct effect unless you're up at that time and trying to get on the shoes.Jenkins.IO. Next up, the docs office hours for this evening is canceled. So Mark's not available to host as am I. So next documentation office hours for Asia will be the 15th. The version documentation build site for Jenkins.IO. So just to a quick recap, this is the result of 2023 GSOC project to build Jenkins.IO with an alternative build tool. The tools selected were Antora and it's a combination of Antora and Gatsby, Gatsby specifically for generated pages and some flexibility and more customization options. So Kristen and Vande Singh have been working on this. I've been helping Chris and Vande with review with finding any issues that might pop up, anything along those lines where I can assist with their, the blind spots they might have, I'm in the site a lot more than other folks. So just little things like that navigation. And then Chris and I met with Daniel Beck who's part of the Jenkins security team to just go over the generation process for security advisories, make sure that they're comfortable with this update because it is gonna affect them as well. And we were able to reassure them that this is gonna be a great move, that it's more powerful, that it's faster, that it's just a better experience overall. And so Daniel Beck left pretty happy. So we had a great session with him and we were able to, yeah, just absolve a lot of the fears and like concerns that they had. So that was fantastic. Chris and Vande are continuing to work on this. This isn't totally ready for production yet because we're looking at cost saving measures for Azure still to some degree. So once we get all that figured out and I think you were getting to the point where it is figured out, this will come back into the discussion and part of the infrastructure milestones that we'll be working on in the coming weeks. And then additionally on top of that, Daniel Beck actually created a pull request and submitted it, suggesting that we potentially have generated pages for each individual changelog. So instead of having an anchor link that takes you to the changelog entry, but then also loads the rest of the changelog, it would be a separate page for each release changelog notes where it's just 2.426.3 and nothing more. It's a faster load. There's not as much noise going on that the user has to either sort through or just kind of like put up with. I think it's a good move. I think it's a really nice and easy solution for something that could be very, not something that we necessarily consider a lot but could be very limiting or detrimental to the user experience in some way, shape or form, just having to load that whole page, scroll through, find stuff, et cetera. So, yeah, everyone seems to be pretty on board with this idea. So I think it's something that will eventually get implemented, but we're not there yet. So time will tell. But yeah, I think it's a good idea. Next up, so we've now got the Maven, Python and Node.js tutorials all revamped to use Docker Compose, amazing. Again, this is the result of another GSOC 2023 project being seen to completion. Thanks to Harsh and Bruno for their work on this. This is great. And yeah, we still got some work to do, multi-branch pipeline tutorials next. There's a couple of things there that need to be taken care of and addressed before we can really incorporate the Docker Compose properly and have it working, I guess. Unless there's been some change since we last met Bruno in that sense. Not really, in fact, I have a new pull request for the Node sample source code because something is wrong, but I guess we will have to wait until Mac comes back to merge the PR. It's nothing important for the same being, it's just a problem of port 3000 instead of 5000. And then I will have a Node code change also within another PR, but nothing really important. So it's almost ready to be reviewed, at least when my two PRs will be merged, then we'll be able to have the tutorial that reflects correctly what's happening in the sample source code repo. But yes, it's near completion, I would say. Great, and as the other, I had this note from last week, Bruno is the React code, the other piece of it that you're waiting for the PR to be merged on or is that something separate entirely still? No, I haven't created yet. The code has been created, but I haven't created the PR yet because I think no one is there to review and merge it. So no hurry on that side. I have made a PR on another thing, just support number that is not correct. And that's all, yeah. Okay, great. Thank you very much. Appreciate it. And then the next thing on that too is that once we get the tutorials revamped and get the documentation sorted in those areas, we're gonna look at incorporating Docker Composer to the installation docs. It's a better experience overall, it's a lot more secure. And frankly, those two things alone are reason enough to update the documentation accordingly. So I'll be working with Bruno on that point and he'll be showing me the ropes so that I can get the Docker Compose integration going for installation. And last up on the agenda for today, the adding the sponsor attributions. So to recap this one, we've been discussing for a little while now, but essentially JFrog wanted to make sure that they're attributed as a sponsor for the Jenkins project. We said yes, because that makes absolute sense. They are, they should be attributed as such. However, we wanna make sure that we're attributing them properly. And that led to a larger discussion of right now the Jenkins.io site only has a sponsor attributions at the very bottom of the main page here. So we were discussing adding a complete sponsors page that would showcase all of the sponsorships of Jenkins. So that's now, but that process had been started. Basil Crows created a sponsors page draft. We're looking at various levels and how to attribute sponsorships from anchor all the way down to bronze, mirrors a different kind of sponsorship. So it's gonna be a separate category in that sense, but we're looking at what kind of services, credits, cost, like there are varying types of sponsorships and ways to sponsor. So we have to really take a look at all of that and figure out what that equals out to essentially and like what level that means for each sponsor. Cloudbees, for instance, is an anchor sponsor. And AWS just granted us 60,000 credits to Jenkins. So like that's one of those things where we have to see, okay, AWS is clearly a very large sponsor. Does that make them anchored? Does that make them gold? What kind of levels does this get attributed to at that point? On top of that, did the lotions donated both last year and this year, Microsoft's donated. And just recently, Ampere has donated two ARM64 servers. And these are physical servers that are located at Mark Wait's house. It's our first time sponsored, getting, being sponsored by Ampere, but it's been in the works now for about a year. Thanks to Bruno for all of his work and keeping in contact with Dan and, or no, not Dan, was it? Aaron Williams, but yes, that's my pleasure. You know what? We also discussed with pine 64 CEO at Fosdame, TLM. And today I received in the mailbox a few boards for evaluation for Jenkins. So that's pretty cool. We got, I haven't opened the pocket yet, but we got as far as I know, two ARM64 boards and one RISC-5 board. So thanks a lot, pine 64 for your support. And I, it's been a few months, but I've been working with a program called Pioneer Dev Board Program. It's some kind of consortium between RISC-5 and MILK-5, who happens to be, I think, a hardware maker or something. And they should send Jenkins RISC-5 board. It's not a server. It's some kind of workstation, but that would help if ever we wanted to make the move to RISC-5. So yeah, I don't know if we need a label, a special label or something for hardware donors, but they are sponsors. That's a really interesting angle to that end, Bruno. Because that doesn't necessarily fit into one of these. Obviously, maybe there's like a monetary or value component we could look at for like what that would look like. But at the same time, maybe there's a better way to categorize that sort of sponsorship. Like you said, like maybe mirror, maybe we have another one for hardware or like something along those lines. Because the servers would technically fall under something similar to that, I would imagine. So, yeah. So I think there's definitely room for discussion on that front. I would say if anything, it might be worth like, maybe commenting on it and just like, it's good. They didn't ask for any kind of compensation or you don't want to be cited or whatever. There is nothing they want from us, but I think it's unfair not to tell about their support. Yeah, I mean, at the end of the day, we don't have to necessarily attribute them as a sponsor on that page, but we could also- Somewhere. Submit a blog post, like saying thanks for the, or a series of tweets if we wanna do one for each of them or like, I don't know, we can figure something. That can all be determined at another point, but yeah, I think acknowledging it and highlighting it is something that we can definitely do, but yeah, maybe it doesn't fit on the sponsor in this scenario. Maybe it's meant for something else or like I said, we'll figure it out. But yeah, I'm not opposed to writing up something, doing a blog post, doing some kind of highlight for them, that sounds like a nice idea, so. Thank you, Kevin. Yeah, of course. Okay, and we've reached the end of the agenda for today. For now, do you know any other things that we didn't talk about or that you wanna discuss? Nothing on my side, Brad. Nothing on my side, I see. Okay, great, thank you very much. So in that case, we'll go ahead and wrap up now. The recording will be available in 24 to 48 hours, as usual, I'll make sure to post it on the community discourse site. And then yeah, I won't be here for the next couple of weeks, so thanks as always for joining, I'll see you soon, and in the meantime, take care, stay safe, and yeah, say hi to Mark for me next week. We'll do, thank you, Kevin, bye-bye.