 Welcome everyone. This is the Jenkins governance board meeting. It's the 22nd of January 2024. Thanks for being here. Topics that I've got that I'm aware of. We've got upcoming calendar to discuss. News action items, community activity. And governance topics and under each of those. Oh, and oh, and Alyssa is here. Very good. Thanks, Alyssa for joining us. Any other, any topics that aren't on the agenda that need to be brought to the agenda for today. Okay, then let's go ahead. So next weekly release 2.442 will be Wednesday, not Tuesday. And that's because it will be a security release. So it will be on the same day as the release of Jenkins 2.426.3, which is also a security release. Look forward to that. Thanks to the Jenkins security team. Details of the contents of the security release are intentionally held until after the release. So that there will be a an advisory published and referred to the link here for the details that Kevin Garoge shared when he announced the the upcoming publication. We've got the next LTS baseline selected and special thanks to Alexander. Alex, anything that you want to highlight in terms of 2.440 and getting ready for its upcoming release? Nothing in particular, nothing in particular. I'm waiting for the security release to take place before starting the back port to make sure I don't get into any conflicts. Right. And that makes perfect sense because certainly the security fix will have to be back ported in addition to in addition to any pending backports. Good. Very good. I've got an open question to board members and other attendees. We're currently scheduled to have a board meeting the day after Fosnum. I propose to cancel it because at the time we're scheduled, I'll be in the New York airport. Basel will be somewhere in Europe out of the office and others will be probably in various transit, various positions of transit. I think Kevin's probably traveling. Alyssa will be traveling any objections if we simply cancel the meeting, or would you feel like we need to rather reschedule it? So I'm going to assume, unless there are objections that I'm going to go ahead and cancel it. Is that okay with everyone? Great. Okay, cancelled. So Mark to remove from the calendar. Great. I will do that. Okay, then on the major events that are upcoming, we've got the Contributor Summit, February 2nd, Friday in Brussels. Agenda topics are identified there, thanks to John Mark Mason for his work. After the Contributor Summit, we'll have a dinner for everyone who attended the Contributor Summit. Thanks to CloudBees for sponsoring that. So Alex, look forward to seeing you there. I hope you're still planning on being in Brussels for Fosnum. Yeah, I'll be there. Excellent. Great. Thank you very much. Then Saturday and Sunday, we've got Fosnum in Brussels. Alyssa's coordinating the assignments of people to staff the Jenkins table at the conference. Others can wander the conference, attend presentations, coordinate ad hoc programming sessions, all sorts of things that we think will be a real positive. And then Alyssa and Basel and I are all planning to be at the Southern California Linux Expo in mid-March. That'll be in Pasadena, California here in the United States. And there will be a Jenkins booth there, thanks to the Linux Expo for letting us have that booth and thanks to Alyssa for helping staff it. Any questions on upcoming calendar? So next topic was news and reminder security release, right? Merges to Jenkins Core are currently blocked so that we don't risk disrupting that weekly release. That means though that we've got a set of 18 or more poll requests piled up ready for merge that will come in after the release is done. And we thank Docker for their continued sponsorship of the Jenkins project. We had a little bit of excitement where we got a message that said our sponsorship had been canceled, but they've reinforced that no, not really. The sponsorship continues. Very grateful to them. Any questions on either of the news items? Okay, action items. Attribution entries for the downloads page with Jenkins sponsors. Now, Kevin had implemented a change on the root page so that Red Hat is now removed from that root page. Any other comments there or discussion that's needed there? There's no update from my side, but I am still hoping to get to this pretty soon. Great, thank you. Thanks very much, Basil. And I'm going to delete that item on Red Hat removed because it was removed. Kevin, I think that was weeks ago, wasn't it, that that removal happened? About a week or two ago, yeah. So it's done, regardless. Great, thank you. And yes, our donation request to AWS was submitted before the end of the calendar year. We hope to have an answer by end of January. If not, we then need to remove AWS from the root page since they didn't donate any funds to the Jenkins project in 2023 at all. And if they choose not to donate in 2024, we shouldn't list them as a sponsor. Kevin, anything you want to report on the Chinese Jenkins site? Nothing right now, no changes as of last week. We'll be, or last meeting, we'll be picking it up for sure after Fostum. That's just priority number one for the time being. So yeah, we'll come back to it. And hopefully by that point, we'll be able to come to Damien with the right questions and plans so that we can have a constructive conversation about it. Great, thank you. Okay, on the contributor summit, we've got 20 plus confirmed attendees that will be at the contributor summit. Agenda is being coordinated by John Mark Messon. And you can find the details of the agenda actually here in the draft agenda proposal. So he's got roughly the first half of the day is reports from the officers and the board. And the second half of the day is focused on presentations from contributors, things like the, what has it been required to do the CloudBees HA solution on top of Jenkins. Alex and Damien, we're looking forward to a discussion about what will it take to remove Blue Ocean? And what does it mean to deprecate Blue Ocean? And then several other discussions. Basel has proposed a topic on searching the code with the Usages and Plugins tool. And looking forward to that. And Oleg Nanoshev has proposed Jenkins File Runner Update. Basel, on the Usage and Plugins, anything you want to share here about what that will mean? No, I plan to do a demo of how to use this tool for both searching for Java Usages as well as some other use cases like looking for jar files as used, but a library plugin into a separate plugin and things like that. So this should basically just be a quick demo because this tool isn't actually too hard to use, but it does have a somewhat high learning curve. So I'm hoping that by showing that demo, I can demystify some of the difficulty around getting started with this. And it ends up being very helpful when you're doing code reviews, if you want to assess whether some change is going to be a breaking change or not. So I'm hoping that we can make that easier for people to use by educating about these use cases. So when I'm considering a pull request that's proposing to remove something, that's one of those potential breaking change examples you gave of, hey, changing a method signature or deleting the method, this tool can help me. Yeah. It does require a lot of disk space because it downloads every single plugin that's in the Update Center. So it requires a few gigabytes of disk space the first time you use it. And there are some other confusing things about it. If you're searching for a class, you have to use slashes. And if you're searching for a method, you have to use periods and various other things that don't make a whole lot of sense. But once someone explains it to you, it's pretty easy. Thank you. Any other topics that others would like to see on the agenda or that we should be proposing to John Mark? Okay, next topic then is my ongoing Java 11, 17, and 21. I am sorry, I still have not made progress on this. I hope to make it before Fosdom so that I can stand up in front of the Fosdom contributor summit and say something more than I've not made progress. That means I've got about a week and a half to make some real progress here. What it needs is a prototype implementation in terms of checklists or steps based on some of the things we did from Java 8, but some of the things are really very different. When we drop support for Java 11 in October of 2024, that will be the beginning of a drop every two years pattern where we'll want to get good at this using these checklists. Any questions there? Okay, so next topic, I'd ask Alyssa Tong if she'd be willing to come to us and talk briefly about Jenkins awards. So what they are, what the process is, et cetera. Alyssa, can you go ahead? Yep, so hi everybody. So the Jenkins contributor award recognizes individual contributors from the community. So just like past years, and we've done this several years now, CDF is hosting this event. Winners will be announced on April 16 to the 18th at their CDCON event in Seattle. So the three categories for contributor awards are most valuable advocate. This is for people who help Jenkins through organizations of Jenkins meet up virtual events, you know, speaking opportunities. And then there's the most valuable contributor award. And this is for people who has made the most contributions through features, bug fixes, and development efforts. And lastly, the security MVP award. This is for people who provide excellent security reports and resolving security issues. This remains the same as in previous years. So nothing has changed there. So nominations is still going to be done via GitHub issues. And thank you so much to Kevin who created these issues just right before this meeting. So the issues are up. And so it's open for nominations. And then it will stay open until February 19. That is when we start voting. And that will be done via a Google form. 2023 winners cannot win again this year. So we have to choose new people. And that's always much welcomed. And then lastly, I will write a blog with all the important details and important dates and links and such to this award program. That's pretty much it. So questions from board members or from others? Just wanted to share, Mark, I posted the links to the issues in the chat. So if you want to put those in the agenda as well, they're right there. Thank you. Thanks very much. Okay. So what you created, Kevin, is three issues? Is that what? Yeah. So one issue each for each award. And then like last year, we'll do the same thing where each award will get its nominations in that issue and proceed from there. Okay. So I'll put those in just as hyperlink. So most valuable contributor, security MVP, good. Great. And so security MVP, it's been not just members of the security team, but also people who submitted really excellent, excellent issues, right? Really. So somebody who made a contribution by virtue of finding and reporting an issue. Do I remember correctly? Yep. There's spot on. Okay. Great. And those who have won in previous years, years prior to 2023 are eligible. Am I also correct there? So a 2022 winner or a 2021 winner is eligible. It's only if you'd won in 2023 that you're not eligible. Correct. Okay. Great. Thank you. Now in terms of announcement, once it's announced, I assume we publicize it on the Jenkins website as well. Yep. We usually blog about it and then LinkedIn and tweet as well. And CDF will do the same. Great. Okay. Thank you. Any questions from others? Okay. Next topic then was on the attribution request. Here, action items in progress. I don't think there's anything additional we need to note here. We'll evaluate the sponsors page as it evolves and discuss it further next, next meeting then for the discussion will be in about four weeks or it will be in four weeks. Any questions on that one? Okay. Next topic then and this one, I apologize. It's new added to the agenda after I published the draft agenda to the developer mailing list. We got the Azure expense report for December for Jenkins Infra and we were at $7,000 and I think CDF was hoping for $6,000. So, CDF said, hey, Mark, Damian, what's your estimate for budget? We can't run hot all year because CDF has not budgeted enough funds to do more than we had originally estimated. Current estimate is that January we will spend $6,500 and so based on that working with Damian, he and I worked up a counter proposal to CDF for a new budget. We asked for a revised budget of $67,500 total for the year. CDF said, yes, that's okay, but you can't go higher than that and what Damian is seeing is that the Infra team has seen that there are additional costs that are arriving and so they're going to make some further changes during January and early February to reduce costs further. One of them is looking at switching what type of file storage we're using. It's a surprisingly large expense and the other is for a potential savings of $500 or more a month moving CI.Jenkins.io from one set of hosts on Azure to another and positive note, the $40,000 donation is being consumed. We're using parts of it but not consuming as fast as CDF would have liked. Any questions on the Azure expense report? Is this kind of status information helpful for the board? I'm hoping I think that we want this and maybe I should systematically put in every three months report. I've just been nominated for and elected as the CDF treasurer so I'm responsible to report these kind of things to CDF and therefore it's a good excuse for me to also report here. Okay, last topic, AWS credits donation was submitted before end of calendar 2023. We hope to hear by end of 2024 so hopefully we'll know by the time of FOSDOM if they've approved a donation for us or not. Any other topics that need to be discussed here at governance board? I just wanted to throw out their mark so this week we would normally be publishing Lulie Haffner's spotlight on the 24th but with the security release and everything else going on we're going to publish release tomorrow so the normal two-week period is going to stay in place we're just publishing release tomorrow so that it doesn't get lost in the shuffle of everything else that's going to be announced on Wednesday. Good, thank you yeah so I'll note that here in the being published and that's being published tomorrow. Correct, the 23rd. Great, thank you. Any other topics? All right, thanks everybody. I'll stop the recording.