 Welcome everyone, it's Jenkins governance. Today is the 28th of July. So I had some agenda items. I'm open. If others would like to drive, I'm just gonna walk through the agenda. We've got news, press contacts, updates, status, discourse evaluation, reminder on LFX security V2, and ratings for releases was one topic that might be worth discussing here if you wanna share something Gavin of anything on that. Other topics. Nope, pretty quiet this week. Okay, great. Sorry, one thing, maybe I missed something because I'm bad at reading emails, but there was something about the election coming this year. Oh yes, that should be a good one for news. Absolutely. So elections coming in December. Yeah. And officers, I believe it's two officers up for election. And, oh no, no, I take it back wrong. All officers are up for election. So release, advance security, et cetera. And I thought two board members, but I'd have to look at the terms to be sure. Oleg. Okay, so Gavin and Oleg. No, I'm, oh, got it. Okay. Nope. No, no, Oleg and Oleg. And me. Listen carefully to what's being said. You're really trying to kick Gavin out. I'm sorry. I'm okay with less work. Don't, don't. That is not the objective here. Great, yeah, so. So was the board seven at one point or has it always been, wait. As far as I know, it's always been five. Five, okay, it was an odd number though. I just thought it was six. Yes, yes, it is an intentionally not number. Yeah. So are we short one? No, no, it's just Kosuke is officially a member of the board, but- Right. He's a lifetime member. Got to- Exactly. That's correct. All right, so by way of news, Jenkins 2.289.3 released today. The Docker images are delayed because we've had a problem in the scripts. We'll keep working it. It may be a day or two before the tags are placed for the, that those Docker images. We've got a choice on the next Jenkins release. LTS has been chosen to be based on 2.302. And it will, it should release on, if it's on schedule, August 25 of 2021. And Google Summer of Code, all the projects successfully completed phase one and shared their results in a webinar. Then elections are coming in December. This is the regular annual election. All officers will be up for election. So events officer, security officer, docs officer, et cetera, and two board members. And the process will be described further, et cetera, as we get closer to that date. We will need someone to run it. Result of all the emails this week was that someone needs to lead or spearhead it. I don't want to volunteer for more things, but his recommendation was Evelina or myself because we're on for another term, so we're around. But it really can be anyone as far as I know. It doesn't have to be a board member. Right. I would, I would need to learn a bit more about what does it really mean before I commit to something that I don't know can or cannot deliver. But I, yeah, let's, I'll try and I'll talk to Oleg and let's see how it goes because it is, yeah. Gavin, I think you're busy enough. So yeah, I'll pick it up with Oleg and we can talk next time. Great. And for your info, Evelina, Olivier Verneen has good details of the election process and past years, the techniques we used, et cetera. So by all means, you could talk to Oleg or to Olivier and then guide you on, hey, here's what it means and here are the kinds of processes we used and here's where you read the retrospectives. Good, great. Then yeah. I think we even have a checklist. Right, right. But then I'll reach out to Olivier and let's see how it goes and then we can pick it up next time. I don't remember when it should start really when all the activities, but I guess sometime is autumn soon, but not like very, very soon. So yeah. Right, it's September or October is usually the healthy time to get that started so that nominations can be accepted for some time to process them, then the ballots can be sent out, et cetera. Yeah, the balloting can start. Okay. Anything else on elections before we go next? Okay, contributor summit. We're considering doing a contributor summit with we're planning for a contributor summit associated with, oh, this was the last contributor summit. I'm sorry, this was the June contributor summit. And I've still got an action item there to post the summaries and the action items. The videos have been posted and lots of notes but action items and roadmap updates are not yet complete. Okay, new topic, press contacts update. Gavin, you wanna take a minute to summarize the result there? Actually, there's no results. I did go in and find the press page on dengs.io, which I can't be the only one who didn't know that existed based on the fact that it hasn't been updated in a while. I replaced Tyler. I replaced myself. Sorry, I swapped Tyler and myself on the page. So now this is a North American press contact. We should follow up with all the people who are listed to make sure that they still wanna be listed. I also updated the trademark section. So it has been a little bit abandoned. I'm also wondering if we necessarily want that page or we just wanna say, hey, contact this mail list or something like that. But for now it's done. I haven't heard anything from Alyssa about her request. So, so far, nice and quiet. I don't have to do anything extra. Excellent, thanks, Anne. I noted to Alyssa that you are interested and are willing to be hosted on DevOps Radio and she'll likely talk to you separately about that. Yeah, I replied to that email too. Oh, good, very good. All right. Okay, next topic was discourse evaluation. Really hope to live here. Could have made this meeting. It seems to be going fine. The people who use it like it. The thing is we have to get more of a critical mass because right now we've had three user questions on there to which I've answered and a third I have no idea which makes it a little bit frustrating for people to use for questions. The discussions that have been happening on there are pretty good but we just need more of it. Then we get more users, then we get more discussions. So I need to do another email blast but I also need to know how much we wanna spend time and effort on this. So I don't, yeah, I'll chat with Olivier and see where his feelings are at. If you wanna push harder or just be like, okay, this is a fun experiment but it's not going anywhere. Yeah, it was a good check with Olivier. My perception, I know I'm one of the users but I just went through with Aditya today, one of our GSOC students and showed him how to create a feedback section that goes into a blog post and it just works brilliantly thanks to discourse combined with Jenkins.io. So thank you. Yeah, I'm a big fan of it. So I'll push, I've just been with the heat and everything. It's hard to see, motivated very long. I do have a work in progress post I'm gonna do soon that will do an FAQ. So things that we talked about last meeting which was how to set up subscriptions, where to post that kind of thing. I was hoping to add more to it but since I haven't got back to it I figure I'll just post it as is. And then I'll do, I'm gonna hopefully do an email blast soon. I just don't, I haven't. Great, thank you. All right. Anything else on discourse? Okay, next topic. LFX security V2 adoption project. So this is a two-pronged project. It's got a component that is infrastructure related that Olivier is leading. And it's got a component that is related to plugins and core source code. And both are a little bit on pause right now. Further contact between SNCC, the vendor LFX and Olivier is needed in order to get the infra scanning working. He's got it enabled. He's got partial access but not full access yet. Oh, I do have one more topic. Okay. We can come back to it after. Digital ocean sponsorship. Oh, yes, yes. Thank you very much. We should put that, yes. Very good. That was mentioned in an info meeting. So we had a topic last meeting on ratings for releases where ratings is the application hiding the PHP app hiding behind the Jenkins changelog pages. Yeah. I don't think there's anything more to discuss here other than what's already been described in community and in discourse. Yeah. The discussion is really good. It's a little bit going in circles. So someone needs to like step up and be like this. I'm owning this and I'm taking over and doing it. But I don't think anyone really wants to own it yet. So the discussion isn't bad. It's just people debating what the best thing is. What is it bike shedding? Everyone argues for their own little thing and none of it's better or worse. So, yeah. If anyone feels like getting involved, it's probably not a bad idea. I figure it's actually a newbie friendly one. So if you know anyone who wants to contribute to Jenkins that hasn't really gotten involved yet, it's probably not that hard to get involved either to rewrite it or to update it or discuss it or anything else, but yeah. Right. Yeah. Thank you. Excellent summary. Okay. Digital ocean sponsorship. Gavin. Yeah. So I have not been following this as closely as I probably should. We do have a yearly budget from them now to pretty much do whatever we want on the service. Olivia and I are gonna sit down at some point and just see what we can do with it. But essentially we can run droplets. We can run microservices. We can run managed databases. I don't know how much of it's useful because we do have a zero, but there are things we could probably move off of a zero and reduce the cost of a zero quite a bit. So I don't think it's been a priority for us to just jump over to that, but it is something that we should really do. Yeah, I'm not sure we have the budget there to do a mirror. It's something on the list, but I just don't know if 2,500 a year, we'll cover that. Right, and that was one that Olivier specifically noted to me. I suggested, gee, I bet DigitalOcean has hosting in India and he said, yeah, but we would destroy the $2,500 budget if we hosted a mirror in India. The bandwidth charges would suddenly, it would become the most heavily used mirror in the entire world. Yeah, and they actually have like mirror mirrors as opposed to running as a droplet that would be a mirror. I don't know if they're doing that with, because I know they sponsor like Gen2 and a bunch of the other distributors. So they might have something that they could do just as a one-off, but I haven't pushed because work's been busy and this is not a priority for me. So I would say we can probably do some stuff or maybe get some things off the legacy infrastructure to something as code, but yeah, we'll see. Great, thank you. Congratulations. Thanks for your help on that and congrats to the project for receiving a donation. Okay, those were all the topics that I had. Any other topics that need to come to this meeting? Okay, so thanks very much, everyone. I'll upload the recording after it's recording, processing is complete. Make sure everyone has a discourse account. I don't know, I'm good. Bye. Yeah, do it. You should do it, you should do it right now. Like right now, right now, now, now. All right, thanks everybody. Thanks all, bye. Bye.