 Welcome, everyone. It's the 23rd of January 2023. This is the Jenkins Governance Board meeting. Thanks for being here. Topics on the agenda today news. Action items. And then build monitor view and community activity. Those are the only topics that I had. Are there any other topics that anyone like would like to add to the agenda. All right, well, then let's go ahead and get started. Here's the news front Jenkins 2.375.2 released a week and a half ago thanks very much to our release lead there much appreciated. Alex I may have forgotten was that Chris Stern release leader or that was you. Yeah, that was Chris. Great. Thank you so special thanks to Chris, and thanks in advance to Alex for acting as release lead for the next LTS coming up. December 2022 newsletter was published. It's quite impressive. Don't miss the chance to read about all the things that have happened in the Jenkins project in the last 12 months, governance security infrastructure platforms, localization UX. The website improvements, advocacy, all sorts of things happened there. Great, great collaborative effort creating that blog post. It's a long crit one, but it's interesting to read. Good. Yeah, so now then, now the next newsletter has already started its preparation so the hyperlink there will take you to the seed if you'd like to add content to it you're welcome to I'll certainly put some things in for the governance board. The security team has announced that tomorrow they'll be delivering a plug in security advisory. Thank you for that. Thanks to the security team for the ongoing work they do. February 8 will have Jenkins 2.375.3 expected to be the last release in the 2.375 LTS line. Thanks Alex for acting as release lead. The back ports had a couple of items that I think are of interest and thanks very much to Bobby sandal for a back port to Alex for doing the initial back ports thanks very very much. And we are also this week going to choose the next LTS baseline and really pleased to note that the ratings for the last seven weekly releases have been consistently positive. The stability of the weekly release it keeps getting new capabilities it keeps getting new enhancements gets keep it keeps getting improvements and yet the ratings are holding high. Thanks very very much. And last item is on the fourth and the fifth of February, Saturday and Sunday, Fosdom 2023 will be held in Brussels. Alex I know you're going to be there. I believe you were not going to be there. Oh, had you decided. Oh, you are going to be there. Oh, you're not going there. Sorry. Okay, got it. And I don't know if I should answer with yes or no, because. Right, I'm sorry I speak English and I speak it's worse I speak English like an American which means I ask upside down questions and I apologize for that. Oh, like, had you decided where you're going to be able to make it to Brussels. Yes, unless something can happen, it will be there for two days. I'm not giving any talks so I will definitely join the booth. Also have an action item to follow up with at least on a dinner and to poke people who go. If you're alert. According to the ex cloud this channel they will be also a few other people joining. I mean once on the Jenkins community so prepare for interesting conversation. Great. Thank you and I'm afraid I won't be there. But I know I have several friends who will be there john mark will be there Damian will be there. Bruno roched and that option will be there so looking forward to hearing good things about it. Next topic then was action items. So Alex yours on reviewing community members and lists for membership or for ownership. Anything you want to report there. Yeah, following up the three items from past week. And this week, or at least last week, the public a GSO group has been archived in favor of the community forums. And it touch it. I think the docs office mailing us has been archived. At least I got a man from you. It has been that's correct. And the hardware and EDA group has been removed from all documentation sources. Great. Thank you very much. Now is there, is there more that needs to be done there should we mark this one as can as complete. I think that is almost done. All lists on Jenkins IO are up to date and are in use. Great, and I'm going to mark it as done. Thanks so much. Alex. Thank you. Thank you. Great pattern to be getting things done. Thank you. Now on the negative side, I have not completed the election badges for the 2022 elections, I'll have to learn how to do that and do it separately. You mean the open bench on the next foundation. I don't, I don't know how they were you how they were done before like so I was going to have to do do the research. Okay, I can get you that maybe later this week. Sure, that'd be great. Yeah, I'm just traveling until tomorrow end of the day, but after that, I can show it to you, because I also had an action item of one other thing in these pages. Great. All right. Thank you. And Alex noted already that the community jank the doc sig mailing list has been transitioned. So that one's done. Thanks. Easy CLA Oleg. Yeah, I remember that one month ago I said that I'm going to finish it. I'm still going to finish it. But yeah, sorry about it. No problem. So next one was create an empty agenda item I'm embarrassed to admit last last time I failed to do it. I will keep this on the list until it becomes a consistent pattern. So this week's agenda I had to create in the last two hours today. And the next topic was the concept of working groups to combine sub projects and sigs into a single concept, haven't done it will do it. We do have, however, a very nice edition, I've got a show that thanks to Gavin mogen and Vandit sing security now has its own top level entry overview administrators reporters maintainers and security team. It's, it's, it's not just not just a few people doing it this was a person who's preparing for Google summer of code who wanted to contribute contributed very nicely. Next topic was send a proposal to Rick to retire the Chinese Jenkins site. Oleg anything you want to report there. Well, I sent the proposal. I didn't get the response. I guess it's a time to think again. So currently there is a lunar year and learn a new year in China. So actually, I believe it just happened yesterday or, but yeah, it's safe to assume that this week nothing is going to happen but I think Rick next week. Great. All right. I was looking at activity and there's Rick has had no activity in the Jenkins project in terms of pull requests in about two years. So I think it's safe to assume that that thing really is not active. All right, next topic was. The question is whether anyone is willing to step up and maintain the site. But I wouldn't expect so and force your maintaining one quality version is better than having alternatives. Right. I agree wholeheartedly. Next topic then was archive the governance meeting notes here we had the action. Gavin has done the extraction work so the archive is ready we just need the repository. The infra team had a we had a proposal to put it in Jenkins CI info said it should be an info or vice versa I don't remember which do does anyone on the board care strongly about which of those two locations host this this archive. So it's a kind of normal pattern in open source projects to have a governance repository. So in since here we see the community repository that is standalone or governance. And I think for us governance would be handy and then we can put other content there as well. Okay. Any questions from others I don't recall which which which preference the infra team had and so I'm, I'm open to either. Okay, so then let me take the action and mark check the infra team preference. And if it is, if they're okay with it being in Jenkins CI will just go with it there. Great. Thank you. Any other action items that we might have missed. Oh, next topic then is the build monitor view plug in Basel. Was there a question. Just, I think I think the question would be, what's the current status of it so last two weeks ago we discussed it, agreed that it was approved that it should move to the Jenkins CI organization and that the request from the maintainer were were good, good requests we were fine with that. Any further progress you want to report on it. Yeah, I've been in contact with Jan Molek and most recently he was he has expressed a desire to get the test suite working before transferring the repository to us. So I followed up with him to ask him what the reason for that is because I don't see why it would be a blocker in the short term or the medium term so still waiting for reply, and hopefully we can get to a conclusion about that pretty soon and move forward. Great. Any questions or concerns from others on build monitor view. I just wanted to plug in. So once you get all the approvals. It's fine to just move it. Yeah, I think the in the last board meeting notes there were details of what john's concerns were and how buzzles been resolving them. Great. Thank you. All right, in terms of community activity, the two points that I had were Google summer of code where interest is growing and the next LTS baseline is being it will be is to be selected soon. Any other topics that need to go on the list for community activity. I'm not sure what it counts but we need to do a project update at the CDF to see meeting. So something called projects would be expected to do from time to time. Is that is that something where it would be. Could it be taken from the 2022 summary is it kind of a look at the year at the past year. I think it's perfectly fine. Okay. I think if it's a refactor of the kind of presentation it would be perfect fit for such kind of the things. Okay. So if you mark. Alexander or anyone else. So, so the blog post wanted to present it. I can help you. I think it's scheduled. Yeah, does anyone object if I present. I'm happy to be the voice I need to attend that meeting periodically anyway. Does that work for others if I'm the voice presenting that thing. Okay. I don't need to print. I don't need to print control P. Great. Thank you. Any other topics for today. All right. Thanks very much for your time everyone much appreciated recording will be available in about 24 hours.