 Okay, so this is the Jenkins governance meeting it's the third of November. Thanks everyone for being here. And sharing my screen. So proposed agenda that I had was news and election status report were the only two things that I had on my list, any other items. Okay, and I apologize I have a hard stop about 20 minutes into the meeting so I will have to delegate the meeting host thing if we reach that point to someone else. Good. Alright, so news security release is happening tomorrow. LTS baseline is also selected and will be the same version as is in the security release tomorrow. And big news the guava update has merged, it will be in the weekly after the LTS baseline. So think of this is similar to the tables to divs change where we will give ourselves several months before the will give ourselves three or four months of weekly testing of the guava update before it visit arrives in an LTS next year. What is the likely impact for users. There are there are some plugins that are appear to be un-maintained and need an update it's a relatively small number of plugins, but there are some and so some some users will be impacted. I don't think the impact will be anywhere near as large as the tables to this choice. Will it be obvious users when that happens. It will. Okay, yeah, the failure mode. I understand correctly is quite obvious. It's good because it's hard to explain why tables to dev failed. So, right, right. And this one I think I think will fail with with much more obvious failure messages like plug in failed to load because of a resolve symbol. And then a static version of wiki. Oh, the hacktoberfest blog post is online and a static HTML version of wiki dot Jenkins that I always online. The content can be edited from the GitHub repo and engine X redirects are available and seem to be working so most of the plugin pages are correctly redirected to plugins that Jenkins that IO. Nice behavior. Any questions or concerns on the news items. I'm sorry about the static HTML conversion. What is the plan here. I thought we wanted to migrate everything to Jenkins IO. Now we have the content in the wiki, and we can edit it. They took a dump of the wiki when it went and went down. And all those pages have been shoved into a repo and served by index. There's no dynamic content. There's no database is pointed at a GitHub repo. I'm like you though I don't think it should have come back. I think it should have stayed down so that we had motivation to get it finished. I think every time we bring it back, the problem just gets still longer but a valid point in this case. By bringing it back we got the benefit that links resolve and links that were dated to and for instance pointing to a plugin documentation that had already been redirected are again redirected. User experience is better, but you're right that we've got more to do, and our plan still is to move content to www.jankins.io instead of leaving it just to sit on wiki. Did that address your question really. Yes, yes. Okay. Anything else on news. Okay then election status report, we have 74 registered voters. And if I understand correctly nominations nominations have ended have closed and registration we're now in the phase where the election committee is verifying that the nominated individuals are willing to accept the nomination and beyond the ballot. Yeah, do you want to say anything or do you want me to read out Olivia's notes. Yeah, I know nothing more than Oliver's note I did contact with notes I did contact a few people last week. They, they, those who answered answered in the messages to the community, sorry election committee. But then I started new work this week and my, my head is somewhere else than the election so I don't have anything more than what Oliver has shared. Do you have it. I put up so it's fine. He says we have three candidates that have accepted for the board position. And notes and what is wording here. Yeah, just three candidates have accepted the position or accepted nomination. One hasn't replied and one has declined. So on top of that. So I'm pretty sure that means three total. So that's a position we only have one that there's any competition everyone else is straightforward. And between the three of us we've collected most statements from most people that we're still finishing that off. And Olivier is a word prepared to send out the emails or pull the emails from discord. So he should be doing that soon. Okay, so he, and he had mentioned to me that there was a surprise for him in terms of querying the, the discourse email addresses is that resolved for him so he's got it. Once he finishes mergers a fix it should be fixed. I think it was necessary to add that note. Excellent okay. Yeah so looks like he could use only originally grabbing 50 a time and now he's paging any properly. Okay. All right, that's excellent. So, so now in in the spirit of Adelina's Olivier starts a new job next Monday as well. So he's got the complication that he'll be he'll be quite heavily loaded. I understood he planned to have them email message ready to send so the sending active effort was going to be pretty simple so that when he, while he's starting his new job he also is, is able to still send that email on time. I mean that's not in the notes. Okay it's not all right okay well we'll hope the next step for me is to prepare the email to invite the voters and to board members next Monday. So I mean, he said Monday. Okay good. Excellent. And then the, the, the actual ballots sent early next week. The last sentence is next step for me is to prepare the email to invite voters to let the documentation officer and the two board members next Monday. Super. Okay, great. So I suspect that Monday as well but I don't know. Super. Thank you. Any discussion needed on that topic. I'm not here if if if he's in trouble with time then I would expect him to post the message and let's see who and how can help but yeah, we'll take it. Yeah and he didn't indicate he had any time challenge when I talked to him. There are things that are brought up in the mail list that I don't think board needs to address but it should be because this is a weekly or bi-weekly meeting. There's discussion about one password. All right. Like I said I don't think it needs to be decided right now but it's worth writing in the minutes. You had great luck with people stepping up to adopt plugins lately, which is more work for Tim and I but it's a good thing. See, and I had proposed proposed docs triage team members. And I'm getting plus ones from that another day or two and I'll act on the plus ones. Oh, good days Jenkins acceptance test is now fully passing. Oh yes Jenkins ATH is green. I mean, how long ever. I think ever. So it's pretty close to ever. If it's not ever it's pretty close. I'm just looking through the last two weeks of mail in this post there is talks about companies being able to manage teams. I guess I don't know what that one is about I'm not going to go into that one. There's we resurfaced the discussion about having some sort of job board. Yeah, and then the government's meeting again so yeah, I mean I just sort of highlight some successes and stuff from the mean list. Great. Thank you. Thanks very much. Anything else. I'm continuing to work on my fun project of converting the website to Gatsby. So expect some more Jenkins that IO PR coming to fix data. And thank you for that data repairs that we're getting from that are wonderful. Thanks very much. The website now support searching for everything. Yeah, that was a big one. That's a really improvement now. Yeah that's a special thanks to our goalie and that was amazing how easy that was we ask. They propose their own pull request that makes the change and we see after they do it and merge it it works. What a great no idea that met it with that meant it's data does but I'm so happy with. Yeah, really nice. Very, very nice. Absolutely. Yeah, super. I think next meeting I'm going to try to remember to do this again I like having the topic so I'll try to make sure that we have some both mailing list and forms if anything. Oh, good. Yes. The farms have gotten a little bit heavy on just support questions. I'd love to see more non support stuff on there, but right, it's still good. Thank you mark for helping me out because I'm getting a little exhausted answering everyone so well and thank you for answering Gavin that's great. Thank you for being great. You're just in time for us to finish this off. I think we just reached the point of done with our agenda topics like are they any topics you need to bring to the meeting that we're not not already on the agenda. Oh, I can use the advantage of not so many topics and focus on the big way. Okay, so speaking series. First week update regarding government stuff. Yeah, continuously every foundation has applied to the inclusive of naming initiative. Before we are waiting for Jenkins to be listed there. Just a second. I lost the zoom. Is it waiting for Jenkins and I missed the last word there. So we are waiting for the request to be approved. And once it's approved. Yeah, you will have Jenkins officially listed there and Jenkins will be added to the list of events we want to promote. All right, so, and when you say it for the rest request to be approved that's by the the I and I board not by CDF. It's a bit tricky because it goes to the Linux foundation, but it's generally at the CDF level we are prompted. Okay, thanks to stages one on the to see level and the one on governance board. So we passed through that. And yes, speaking of that, it's rather personal update. So as far as I discovered the CDF to see member is also a member of the CDF governing board. So with regards to budgets, etc. I cannot present Jenkins interest directly on the CDF governing board level, at least until the next directions. So that's you're on the CDF governing board or the Linux foundation governing CDF. The Linux foundation would be cool but it's way above my current rating in whatever foundation. Yeah. So you said you can't talk about it. No, I can. No, I thought you said you can't talk about something because you're on the board and I was like that's okay, I just, I'm sure I can represent Jenkins there. So, for example, we will have quite interesting budgeting discussions for the next year, which are about to start including infrastructure budgets. Yeah, there is spending requested to Microsoft is regards to Asia sponsorship, but it's not clear where it will go. So, basically, being involved in these discussions would be nice. And for your information Mark Anders Walgreen, he basically represents cloud bees on the governing board because cloud this is a premier of member. So we used to have one to one meetings with you while I was at cloud bees. So if you want you can take it over. Thanks. Okay. And maybe for the record, I'm changing my affiliation and no longer employed by cloud bees. I officially joined the dynamic race on Monday. I will send official notice to the developer mailing list, but it impacts elections, because I'm no longer affiliated and no longer, I don't even have no competition and other things. So I will be representing another company. Yeah, I'm looking forward to quite productive cooperation, because that interest is quite active and distributed tracing domain is these. So observability stores, etc. Okay. Okay. Yeah, official announcement to be sent. But yeah. Excellent. I think we're going to meet. Mark still in. I think we are. If there are no other topics I proposed to close the meeting. If, if we don't close the meeting I need to hand hosting to somebody else because I'm, I've got a hard stop that I've got to deal with for personal needs. Let's just call it over. I'll try to join on time next time. But yeah, it depends on this small kid. That small kid is is a great first focus. Thanks for joining us all like Evelina. Gavin, thanks all. We'll talk again in two weeks. Thanks.