 Welcome everyone this is the Jenkins governance board meeting it's the 15th of May 2023 topics I've got on the agenda include news. Action items budget and expenses. Kevin Martin's absence for a month as documentation officer application to ampere for arm hardware proposal to cancel the May 29 governance meeting in two weeks and community activity. Any other topics that anyone wants to be sure we add to the agenda. Not here. Oh, oh actually I missed one in the news section. CD, oh it's already here good CD con completed good. All right, then let's go ahead so by way of news we've got a two dot 401 release candidate scheduled for Wednesday thanks very much Alexander for your willingness to act as release leads as as the release lead thank you thank you. And thanks to Basel Crow Basel thank you so much for the prototype JS work that you and Tim Jacob have been doing the blog post is live and it guides people who may not be experienced with Jenkins or who want to learn more about JavaScript. Hey, here's a chance to do it and do it in a way that really helps the Jenkins project. Thanks very much. We've got for Google summer of code projects that have started. Thanks in advance to the mentors and to the contributors. And congratulations on the Jenkins awards to the three award winners to young farachik to Daniel Beck and to me. Tomorrow we've got a plug in security advisory. Thanks to the Jenkins security team. They sent the announcement out for warning Jenkins administrators that they'll be seeing some updates to plugins related to security tomorrow. And plugins that Jenkins.io now shows health scores. So the the scores are visible at the bottom of each card, telling you how healthy or unhealthy a particular plugin is guiding you on whether or not you should install it. Any questions on the news items. Okay next topic then is action items. So easy CLA no progress from Oleg. Requirement shed as far as I can tell. Sub projects and SIGs into a single concept. I've actually started the work on this one and we'll continue that there's there's more work to be done lots lots more work to be done. And it'll just continue. The retirement of the Jenkins, the Chinese Jenkins site has also started. It's no longer visible on this page here or on the drop downs. And we don't have the full redirects yet, but we've got this first that first step taken governance meeting archive sorry that's no further progress on that we've got answers with from the infra team that will place it in Jenkins info. We've just started the retrospective on the signing certificate renewal process, capturing the notes in that Google Doc, after a week or two of me gathering timelines and other details. We'll, we'll actually host a formal meeting where we were the players in the session talk about it and go through it. Next one, the reimbursement process for the code signing certificate is continuing and made new progress today. Any questions on any of the action items. Okay, for the for the retrospective. Are you including in that the conversations you had with the Linux foundation folks about the I remember the last meeting you. You had mentioned that you talked to them and they had given you some ideas about different ways that this could be done for example I think one of them was having a dedicated package that simply updates certificates. I remember you mentioning that they had seeded that idea. And since you mentioned that I, I noticed that some of the software that I use on my own desktop is using the same techniques. For example, I think I noticed that Microsoft was doing something similar for vs code, which I have installed on my computer. And I think they had. I don't know if it was vs code or some other program I use but but I saw the same technique being applied there with this kind of dedicated package for updating certificates or keys. It would be interesting to learn more about that. So, if, is that being included in the retrospective or is that a different topic. No, no, that's that's absolutely. That's those two things are I think key parts of the retrospective because they are, they are, well they were both really bumpy and there's no need they have to be that bumpy. So yes, you're absolutely right and they will be included there in the retrospective. Any other questions on, on the action items. Okay, next topic then is on budget and expenses. So the 1500 us that I spent for the digit cert code signing certificate is now in progress. The, the expense report has been submitted to the Jenkins projects designated single finance person. And that I think right now is Oleg so I'll ping him separately after this meeting to let him know that he should have seen an email that invites him to approve it. Once his approval is generated, then it goes to the Linux foundation and their net suite system where they send it out for disbursement. And they have had an additional test case where Oleg had already approved this $52 and 99 cents expense from last year, and they have refreshed it at the Linux foundation sent it to net suite for disbursement so I will check with Botic tomorrow to see if he's, he's made it to this meeting indicating he's been paid. Any question on the budget and expenses. Okay, next topic then is the board received a note from Kevin Martens that he'll be unavailable May 12 to June 12. Before we move on, I had one question about the certificate is this this I was just curious after we, after we do this is this what what was done previously like the last time the certificate expired or is this a new process that we're coming up with. So it was, I think the last time three years ago when we had to do the, the certificate reimbursement. Olivier Varnon handled the expenses, and I believe he was reimbursed, but the expense if I system that we were using at that time or the expense reimbursement system was different from three years ago than it is now so it's not so much that this is a new process because it's the same process we use with Vodic Filonia a year ago, but it is, there were enough wrinkles and bumps and bruises in it that that it felt almost like a new process. Okay, that makes sense. Okay, good. Then on Kevin's absence so as documentation officer he notified the board that he'll be unavailable May 12 to June 12. What I propose is let's intentionally choose to just have other members of the community help out during Kevin's absence. For instance, he's been working on the change from Java 11 to Java 17 in the documentation in the install docs. Let's just accept that will be delayed and others are welcome to help documentation pull requests, we invite all the documentation contributors to help there, and I'll volunteer to take on the change logs and the upgrade guides. Alex, does that work okay for you from the perspective of the 2.401.1 release lead. Absolutely. Okay, great. Any concerns there on the plan for what to do during Kevin's absence. Okay. And then was, I said a request to the board, about three or four weeks ago, suggesting that we'd had an opportunity presented to us by ampere ampere is a hardware vendor base, they created and sell systems based on arm 64 bit server class processors and their they're used at Oracle for their cloud hosting and I believe at one or more other cloud vendors. And they'd offered the that hey, they donate to open source projects that are interested in using their hardware to do some validation. And this was an offer of physical hardware and it happens that I already have physical hardware at my house. So I prepared an application and send it out to the board. Two or three weeks ago, two weeks ago it got approvals in various places from Alex and from Uli. So I went ahead and forward it on to ampere. Any concerns that want to be expressed about that the ideas will put in in my house and connect to it as necessary to use it for Jenkins purposes. That sounds great. Okay. Next topic was two weeks from today is a US holiday. So I propose we cancel the meeting that schedule for two weeks from today unless they're compelling reasons we need to have it. I'd like to take that US holiday off and spend it with family. I'm in favor of canceling the meeting because in a couple of weeks we also have a holiday over here. Oh, so it's not just a US holiday. It's also a European holiday. Good. All right, even better. Okay. Any objections to the cancellation then. Great, go ahead. So I'm going to list plus one from all three attendees. Great. Thank you. Okay, next topics then our community activity topics. And here. I think it might be might be good to give Basel some time to share if you'd like Basel on the prototype JS work on the artifact rework we're making progress. I need to schedule a session with JFrog to summarize our latest results and talk in more detail with them about next steps. I'll do that and have something to report on next meeting. Did you want to give any further details on prototype Basel. I don't have too much to add to the blog post. I have a developer mailing list thread where I listed a number of plugins that I've identified that might in my quick search to look for common keywords that are associated with prototype, but I am planning to do a more thorough search in the next couple of weeks. So that low hanging fruit that I wanted to get out of the way first. And that includes the dozen or so pull requests that I've already filed against some of the most popular plugins. And that low hanging fruit. That makes it more difficult to find the higher hanging fruit, because it gets in your way so I am planning on doing a more thorough search. And when I when I do get to that, which is probably going to be the next couple of weeks. I'll create a some kind of spreadsheet or tracking system. That would be a good way to coordinate. To coordinate efforts to fix plugins. So I've done a couple of these types of spreadsheets where I have the plugins sorted by popularity and use different colors to indicate status such as whether a release has been done or for still waiting on the pull request to be merged etc. So, once we have that I think it would, I might go back and update the blog post and add a link to it. I think that's the point. The best because I had a number of people have asked me like where do I start and that mailing list thread, the list of plugins there is the best place to start right now. And that and that and that like I said I'll make that more formal in a spreadsheet once I get the chance to do a more thorough search. Great. Thank you very much. Thank you, thank you. Congratulations, Alex from you in terms of prototype JS or from anyone else. Okay, then let's go ahead. Next topic then was Google summer of code congratulations the Jenkins project has been approved for for Google summer of code projects. Each of the project has projects has a designated lead mentor and two or three additional mentors to help help that contributor be sure that they're successful. Thank you very much to John Mark to Chris to Alyssa and to Bruno for their work as organization admins on infrastructure, we've got an active effort going on to reduce infrastructure costs. Thank you to Porta, Evele Mure and Stefan Merle have each been working on various aspects of this, including things like looking at better choices of machines to be used that are more cost effective, or switching some tasks from AMD 64 to arm 64, or reducing bandwidth demands when bandwidth is a high cost item. Thanks to them for for that ongoing work. It's, it's very, very promising. It's looking really good. Then I've got an ongoing project to propose an early end of life for Cento seven in the Jenkins project. And there's a developer mailing list thread on it, it will be continuing. Probably several months before it will get to the point of being ready to announce with blog post etc. But I'm determined we're going to get that thing end of life before June 30, well before June 30 of 2024. Any questions on any of the topics up to this point. The next topic then was launchable experiments so Basel has been leading an effort to, to test drive ways to reduce the number of tests that we use and still get high quality results from our tests, using launchable a product or a company's a product from the company that Kosaki Kawaguchi is part of now. Basel anything that you want to talk to on this one, in terms of ongoing or thoughts. The last step in this project is to enable it for Windows tests in Jenkins core. And then after that. I plan on adding a launchable subset of ATH to Jenkins core as well. So those are those are kind of the first two areas where I think it makes the most sense to use launchable. You know, I know that the infrastructure team has been trying to reduce costs in ATH itself. So that's also an option. If they want to because I know that they were talking about, you know, do we need to run all ATH tests for all dependency updates, you know, similarly to bomb and your launchable could be used to implement. So I'll stop sitting there in much the same way. So, that's another option. I probably won't get to using launchable in bomb itself till after we're successfully using it in core and ATH, which might be in a couple of weeks. Great. Thank you. Thanks very much. Any other topics we need to discuss here in governance meeting. I do have a couple of items I didn't add on the agenda before. And the first is maybe you already noticed it. I enrolled the Jenkins CI and Jenkins info organization into the private GitHub activity beta thingy. I posted on Gitter a couple of hours ago. All repositories within these organizations now have an activity item on the right hand of the repository overview. It actually doesn't add anything new of content. It is like get lock just with a web UI dashboard. Are you saying it would be visible even now. So if I were to open up a plugin repository, I should see it. Let's pick something fairly innocuous. This one. Yeah, then the right. Oh, there it is. Okay, got it. That's basically the same output. If you type get lock in your shell just in a visualized form, a filtering between pull request mergers force pushes and so on. Thought would be a nice addition for our maintainers. Nice. Thank you. Any questions from others on on the GitHub activity facility. No, thank you. No problem. The other item was regarding our deer instance. I'm not sure how much you track the JIRA and support and end of life cycle. However, we are currently on JIRA eight which will be and of life and actually end of support within the next five months. I was wondering if the Linux foundation plans an upgrade or if we need to request an upgrade from the Linux foundation from the current LTS to the next LTS. Good question. So, usually we request it and they will take the action on our request. Yeah, I'm happy to open that ticket. I've, I've done those before or you could open Alex, but whatever your preferences. The latest end of life between mid of October this year and zero nine dot four or nine dot two would be end of life in late 20 25 and that is the current LTS version, which we likely would go to. Good. Thank you. Thanks for detecting that. So how did you, how did you find that was that something that the user interface announced and I just missed it or I'm going to look at the bottom footer of issues such as it tells you the version and compared to other giras I'm using I was a bit surprised that we are still on eight or 20. Got it. Okay. All right, so if you're okay with it, let me put an action item to open the JIRA ticket. For sure go ahead and open those. I don't mind. Yeah, our JIRA instances certainly it's it's a somewhat of a distinctive case in that it is a JIRA. What do they call it it's a it's it's their data center I guess addition right because we're because of the size of the number of users we have we're allowed to consume being self hosted or being hosted by the Linux foundation. Thank you Alex, any anything else. All right. Thanks very much. Let's go ahead and and call an end to the meeting. Thank you. Thank you.