 Okay, we're now recording. Welcome to the Jenkins Governance Meeting. This is October 17, 2022. We have Evelina, Oleg, and Kevin as myself on the call. I think we're going to have a fairly short meeting, as none of us really know what we're talking about today. But yeah, I'm going to get started with some of the news. We are currently working on the next LTS release, which is supposed to be 2.361.3, which is scheduled to release on November 2nd. I know there's a call out for the next release manager. I believe that is Alex doing it, but I haven't kept up to date with it. And then we also have Alex and Alex are now involved with the repository permission updaters. So hosting requests are managed or managing by them, which should mean it gets handled a little bit quicker and easier. I was not able to keep up and Tim has a lot of other projects. So it's an Alex has done a massive amount of work in the last week or so updating dependencies on some of the scripts and approving and following up with hosting requests. So already a major improvement. And then is there any other news that we haven't listed that should be brought up. No, cool. I'm going to skip over the action item of Mark to use community docs because he's not here this week and it's an ongoing thing. Mike, do you have any news about documenting easy CLA? Not really. I start looking into the current status of easy silly, because I wanted to have the same documentation for Jenkins and for captain. And I discovered that there are some changes in easy silly. I need to discuss privately we said the Linux foundation before I write anything. I need to discuss more with Linux foundation before. Okay. This is where basically I'm left. I need a meeting with them. But yeah, sounds good. Likely after coupon. As you can do this. Okay. So I'm going to move on to elections as our next topic. I have not been following on this as Evelyn and I are both up for reelection. I've been purposely ignoring the whole process. But it sounds like there is a process and it looks like it's going to start this week. So I can actually speak to this guy and so I checked in with I was working with them. I'm working with them in on the election stuff. So I'm just going to go back to that. I'm going to go back to the announcement all that sort of thing. What we wanted to just figure out today is confirm the timelines and key dates. Because Damian and Mark were supposed to work together at DevOps world a lot on the election stuff, but since that didn't happen things have been pushed back. So we wanted to see. And so we were able to get a full list of the time frames from Jenkins to be a three week period for registration and nominations, and then roughly a month for voting, but with the constricted time frames, it might not be as full. So we were wondering if right now, Damian said he could probably get everything registered or organized for the registration by the 19th. So Wednesday this week. We're looking for three full weeks of registration and nomination that would put us a little bit past November 10th. So we'd only have 15 days or so to do the voting itself. And I'm not sure and we wanted to make sure that a we're giving enough time for the nominations and whatnot, but also that voting does have enough time as well. I don't know a lot about the history of the election than what is required and what is not only do you know. What is particular question. So this process was followed. Well, it does look like we need what we agreed on the community. It does look like we need three weeks to encourage nominations. I don't see anything about voting. Well, technically we can speed it up if needed. Okay, yeah. Yeah, I would probably kind of how your planet keep enough time for nominations and just shorter voting. Yeah, that's my feeling to we can. I mean, honestly, going into December is not the end of the world. I would do to some degree what you're comfortable with, but I would say three week, three week minimum for nominations and registration, and then voting can be adjusted as needed. Okay. Does that answer the question you had. Yes, yes, absolutely. Because we can plan everything out once we once we know for sure that what is more flexible or not. So if the voting is more flexible in this case we can, you know, determine everything else around it. And the other question was, so the current terms were to be ending on the second so anyone who is voted in would be starting their term on the third if we go into December is that still okay in that sense, or would we like to have everything completely buttoned up before the third. There's always two board members that are rotating in and two that are staying. So I would say, I mean, I guess I get the thing is, Evelina, and I would probably be okay with sticking around for another week or so if we need to. Even if her terms are up, it's going to be transition period anyway so I'm not sure it's a big concern. Okay, that works. Great. Yeah. And we'll make sure to check in before anything's officially announced or published or anything like that to make sure that everyone's on the same page. I will say in the two years I've been involved with this process, we've never hit any of the dates. Good, you know, something's always come up last year the voting service went down middle of the voting period. You know, another year we had trouble collecting. The nomination period because it didn't get enough nomination so it is strict but it is flexible, you know. Okay, great. Perfect. That takes care of all that. The only other question I had then is there a way to get a list of just all the open positions that we're looking to get nominations for. You know, be the two board members and I know Mark's Docs Officer is coming up but I'm not sure. So officers are always one year. Okay, all the officers are up for re-nomination. Generally they tend to say the same but who knows. And then Evelyn and I are board and we're up for our two year terms are up so we're up for re-nomination. Okay. Or nomination or whatever. Okay, wonderful. Yeah, then I think, yeah, I think that takes care of the questions that Damien and I had so that helps a lot. Thank you very much. No problem. Do you want to put it, do we want to put anything in here or do you want to update this section later? Yeah, I can update that section later. No problem at all. Okay. We're moving quite a quite quickly along. What is it something else, Oleg's reply. Okay. CDF topics. Oleg, do you have anything you want to bring up in for about CDF? Yeah, there are two topics. First of all, so there was a message from the, from Laurel, Laurel, so she's a new chair of the outreach committee. So she asked whether Jenkins could designate a representative to this committee of a security organization of all communications. So the scope is all kinds of community marketing, ambassador program, also events by the continuous delivery foundation. Yeah, yeah, this is why I proposed Alisa as a conduct by default, but I'm not sure what is Alisa's availability. Events, not investor. I wish we had investors in the CDF. So I thought you said three things and I only have two written down. Events coming out, yeah, marketing also ambassador program. Ambassador or ambassador program. Yeah, go, go, go. Okay, cool. Do you know the deadline for this? Well, there is no deadline. Okay, because I feel like this is when I find someone, it's great, better than no one. Yes, I feel like this is something that the new officers might want to be involved with it as opposed to Alisa who is the current officer and I think I don't know if she's planning to come back again. So, yeah, so congratulations. There is voting in progress. Basically there are general consensus that the project should be agreed. There are no direct consequences for Jenkins disease. Yeah, it will no longer be the only good idea to project in the foundation. So basically that's it. Yay. I wonder what actually the consequence for Jenkins sex that bundles both Jenkins and tick ton. While it doesn't bundle Jenkins really right now it's rather a dawn in the helm chart for Jenkins X3. Yeah, for everything is good. Yeah, we're here. I mean, yeah, do you have anything else for CDF? Yeah, that's it. Okay, so there was one I just saw, because I only just replied to it. We have Alex. I don't know how to say it's nothing Alex brand is as the a new core maintainer. I don't know where we want to put that but is that done. Is it because I don't I see a wide consensus in the community. I mean in the minute list so I would assume it's done. But yeah, we haven't officially confronted. So I'm happy to just rubber stump it at the meeting can go forward. Just to do a legwork and to Alex told the groups and whatever. Do you want to officially part of the board or is this a board decision. I don't know. No, no, I'm fine. Just leaving it as a, we'll leave it at the news then. We'll leave it as a community topic. Yeah, we'll put in the community topic section then. And I think that's the fact that again, no one had any concerns on the on the board meeting and we should move forward. Other than that, October fast is continuing. The October fast chat channel is someone active. A lot of people are looking at doing various small works and stuff. I saw that Kevin updated it. So we have 245 October fast pull requests, which is really good. I'm really impressed by that number. With 71 different computer contributors, which is again, really exciting. Hopefully most of them will stick around or at least some of them will stick around for future after this month. And I just, I do like that little thing that 19 of them got their t-shirts with just Jenkins PR, which is, you know, kind of cool form topic wise, I don't actually have anything this week. There hasn't been anything really big. There is a couple ongoing requests about, I think, HTPS in the topics, but I don't think they're actually an issue. It's just some people upgrading finally. And I think we have a general discussion about Tomcat Tomcat that we're going to make sure there's a documentation on the Dallas page that says, well Tomcat should work. We're not officially supporting it and we're not, we're not going to spend support time on it. So, you know, essentially a matrix like we do with browsers to say which ones we actively support, which ones we actively test and which ones should work. Compatibility matrix. Cat issues. I can't type and talk at the same time. So if anyone else wants to add anything, they can. Otherwise, there hasn't been a lot of community topics that I think need to be brought up. I'm really excited to see all the various people helping out on the forums. I've slowed down a bit. And there's a lot of people who have stepped up, which is really good. I was a little nervous with Mark being away because Mark is very good at answering in very concise and clear ways. And even without him around last this week it's been, you know, fairly smooth. Does anyone else have any topics? I'll separate mine. Everything fine for me just quick heads up. There was no ETE when I will be fully back in the community. I mean, with the original capacity. I hoped to return soon but yeah, then they were in Ukraine and now I have a few other events to take care of. So right now, no confirmed ETE. I hope I didn't block anything. But yeah, I wouldn't say that I'm doing how much beyond governance and some basic. I think there's one good thing I have is being vocal when I need something. So I think for the most part, you're not blocking anything and if you were I would make a fuss. The only thing I would say for the next board to deal with is figuring out exactly what our plan is for the CLA. We're kind of in this weird mixed state of kind of doing it one way. We're kind of doing it both ways and we need to actually get that formalized. Yeah, that bull is on my side. Yeah, okay just but you're right now. I definitely have a plan to close it. Well, and since I'm doing the same for three communities by now. Yeah, I think that I have some motivation to get it done. It's yeah it's not blocking anyone so it's not the end of the world. Oh, we did have that email this morning about content. I don't know if we should put anything in the meeting minutes about it. I don't think there's anything for the board to do about it. But I don't really want to put a lot of attention to it unless it comes up someone was requesting access. They're asking to be able to copy some docs to their site and I said as long as you meet the licensing cars of the creative commons share like that's fine if you want a different license or terms. You can request them but the moment that's what we're going to go with so that's fine. We'll have some content which is not explicitly licensed. But for what you have in the repositories, all licenses fine. Yeah. So website content included. Yeah. I'm going to stop sharing and stop recording unless there's anything else. Stop recording.