 Welcome everyone this is Jenkins governance board meeting it's the 17th of April 2023. Thanks for being here topics I've got news, action items, and budget and expenses, and then CDF topics, any other topics that need to go on to the governance agenda today. Okay, great. So let's highlight. In the news topics, new LTS has been delivered. And we've started removal of a very old major component to be replaced by standard JavaScript. Thanks to Tim Jacome to Basel Crow to Jan Farachik to Alex Brandus to others. I believe you've even contributed one or two on these. Thanks very, very much. Exciting to see. We've also got good, good results on Google summer of code we're in the midst of reviewing those early May it will be our package will be submitted to Google and they'll then announce how many projects were approved, etc. The last item of news may eighth and ninth in Vancouver Canada will be CD con sponsored by the continuous delivery foundation and coincident with get ups con and so a conference there. The Jenkins words will be announced there. Any questions on the news items. Okay, next topic. This is a CLA. No progress and no requests. Oh, excuse me. Okay. The other submit pull requests to combine sub projects and SIGs, I've started it. And there are four pull requests submitted to begin small incremental steps to retire and active SIGs, then I'll do roadmap update pull requests later. This one is in progress on retire the Chinese Jenkins site. We're making progress there that it's no longer available on the top level site. And next stop still is further work to do a full redirect from the www.Jenkins.io slash ZH to the root, but that'll need some info work and we're tracking that in a help desk ticket. Any other any questions on those items. Okay, last item, our next item was archiving meeting notes. And here we've got a we had an open question where to put them, but we don't have an answer from Oleg I propose we just accept that we'll place them in Jenkins dash infra. I was recommended by many people in the comments on the help desk ticket. Any objections from others. Lee, are you okay with that? Yes, this makes sense to put it there. Okay, Daniel any objections from you. When you say many people who suggested that I mean I realized that I'm arguing against myself because I requested Jenkins infra originally. But I was sure many others agreed Damian agreed with the recommendation I believe I also saw a comment from Alex Alex agreeing with the recommendation. And I'm fine with the recommendation and I think Uli said he's fine with it so I think, I think we should just simplify our lives go ahead with Jenkins infra and get this one off the list so that we're done with it. Right. It's not like we cannot move after the fact. Absolutely right. It's a repository it's very mobile if we need it. So any objections from you Daniel. No. Okay, great. Okay, thank you very much for your time. Thank you very much for your time. Thank you very much for your time. This one was just added last week, or two weeks ago. I need to schedule a retrospective on our certificate renewal process because it was too, too filled with bumps and bruises for our Linux users and two full of very, very nervous very last minute changes for the windows users windows users didn't see the problem, so we've got things to improve there. Any questions on the signing certificate renewal process, and it's retrospective. Okay, next topic then budget and expenses. So we've got two outstanding expense items that haven't been reimbursed. One of them has had a request submitted. Tonya submitted a request many months ago for reimbursement of $52 and 99 cents been approved, but he's not received the funds yet. So, I propose that we take that this one becomes an action item for me to figure out why Vodx not getting reimbursed and what it will take for me to be reimbursed for the $1,500 that I spent for the code signing certificate. I have funds and I've sent the request to the Jenkins board mailing list asking for everyone's explicit approval. I think it's okay, Uli, I can ask here, are you okay approving that expense here. Yes, I think mail already to you, or to the, I replied this mail but I'm approving it again, you know, that's fine. Thank you. And I'm not sure where do we get the money from or where do we need to make it. I'm not sure where is it. So the money actually sits at the on the crowdfunding account at Linux Foundation. And right now there's this 10,000 US dollars that's in that account with a nice track record of receiving steady small contributions from various places. We haven't spent money from it for quite a while and part of that is because it's been surprisingly difficult to get the funds out of it. So I have the action item I think to work with the, the continuous delivery foundation and with the Linux Foundation to understand what we can do to make this easier. Daniel, any concerns from you about the reimbursement request and the expenses there. Go ahead. Great. Okay. Thanks. So then I'm going to put that as an action item. And it's a I'm a personally interested action item. Because I want to get reimbursed. But you know how or what the next steps are how to get the money. Okay, I've well I've, I've sent the request to the people who are the best hope. Okay. I think we actually use an expensive high account, or Linux Foundation uses an expensive high account and somehow works it through that but I've asked them for the details. All right, and last topic was on the from the CDF side, Linux Foundation has a, an analytics thing that they use called insights. And that insights is intended to be a replacement for the, the dev stats statistics gathering system that they created several years ago, and that we've been using to collect data that I've been using to collect data on how the Jenkins community is doing. So this, this dev stats conversation includes the list of the five items that I use regularly and if I get as I add more I'll put them in this list for instance, this graph shows us over the last two years. So contributing to Jenkins, who companies whose employees have contributed to Jenkins have been at a high of 149 and are currently at about 97 a low of 71. So, I find the data interesting in terms of individual contributors we've gone from a high. We've had peaks of 707 yet the moment we're at 610. The peaks in the valleys are interesting and this data comes from dev stats now, eventually it will come from Linux foundations insights project. Any questions on that topic. All right. That covers all the topics that I had on the agenda any other topics that need to be added to the agenda before we close. Okay, thanks everyone.