 This is Jenkins governance meeting it's the 9th of February 2022. Thanks for joining us. Topics on the agenda news. We tentatively put easy CLA status report all legs not available so I'm going to move that off the list for later. And press contact email alias topic Java 11 or newer require Java 11 or newer a JEP discussion for me that's happening and highlights from the mailing list. Any any other topics that need to be on the list. Okay, then by way of news. These two security release fixes today one for LTS one for weekly. Thanks to the security team it was a medium security vulnerability in XML serialization. And the new LTS baseline has been selected. Tim, our, our release officer has asked for a release lead volunteer and so we're looking for that volunteer. And we've got Jenkins is the way stories that we expect will be arriving on Jenkins.io thanks to Gavin's work. We've got to do I've got to still do more review the pull request and then we got to negotiate the automated redirects from the old site to Jenkins.io and get get the money saved that was that a certain sponsor is spending on that site for now. I think I need to hit a doc on Office Hour Docs Office Hour to figure out how to make that a little bit more reviewable because it crashes GitHub browser pages because it's 600 files including PDFs and zips and stuff. Fair enough and we may want to we may want to explore further but it does deploy with the deploy deploy tool right so we can we can actually review the site using the view deployment button. Yeah, so I think I think that's actually already enough now I don't know what that means in terms of. I assume that that the reason it crashes just sheer size of the pull request not that it's going to make every pull request in the future crash. No, no. The initial creating the pull request because it has every file open killed eight my browser up the subsequent loads are fine as long as you don't expand every file. Okay, good. And then special thanks to Gavin for spelling check for submissions to Jenkins.io documentation is having correct spelling now thank you very very much. It was interesting to see they were like most of the stuff in there were minor minor typos but there are things like dear tickets. I don't know you may want to put in the note here it's it's a program called cargo dash ci slash typos. So it's someone wrote a little rust CLI that is code aware. So you know like a lot of times like markdown and stuff have usual symbols and the mess of spell checkers. This is a code aware spell checker. So it's, it's pretty slick it went in and it handled ask you to find a handle the formatting fine. It had to put a bunch of overrides because of people's names and stuff but it's improving and I'm pretty happy with it it caught a lot of things pretty nicely so. Yeah, well I'm impressed with it's, it's very low failure rate, the number of times and it actually has a failure is much lower than I expected my spell checkers are not nearly as good as it is. Yeah. Excellent next topic then press contact email alias so Gavin. Yeah, so you mark and I had a bit of a discussion off this. I'm one of the, I think one of the. I would say I'm probably the only remaining person on the press contact page so Jenkins.io slash press that is still an active member of the community. There are, I mean, there are lots of people who are engaged like our Tyler is still there, but you know just not an active member anymore. And so, you know, I think we do want to look for volunteers to be press contacts. But I also think we should remove the individual members on that list. So one solution I was thinking of, and this is really just something we've been in my back my brain, is we just set up another Google groups, we've been using it for everything else we can set up Jenkins CI press link to it there and people contact the Google groups. I actually kind of want to put in discourse discourse or the community site has support for inbound email so we could have an email that gets automatically posted to a group. And, you know, then anyone, we could either we can move it around so if it's in the wrong spot we can move it to something public. I would say the press email probably should be not open by default, just in case, but it doesn't mean we couldn't open up and moving around after the fact. So I kind of like discourse for that reason but I think we should have longer discussion and actually figure out something a little bit more sustainable than having people's hard coded emails on a webpage. And I like that. So is this something it would be okay to discuss in the dev list or in the, I'm not sure where the best place is is it advocacy and outreach is a community Jenkins that I owe the people I know who watch advocacy also watch community so they'd be, they'd be there. Yeah I really don't know this is one of the issues I'm having with the community right now is where to have to know so it's where to have discussions but who should be involved. Right. It's always easy for us to pick one spot and then tell all the other spots that discussions happening there but it feels dirty. Yeah. I don't think it needs to be sold right now so I mean, I'll make it clear I did get a press contact today which is why this came up, but I can deal with it the one today and we can just look at a future something going forward. Great. I think you had said that you had received you'd been contacted a few months ago on a similar topic and you just responded and didn't seem to be a huge issue so it's not that you're being overwhelmed. No, I'm gonna. I think I've gone in for email so far one would have been that big exploit I think confidence. And then to companies looking to get more involved at Jenkins. And that's in a year so not a heavy use thing. Great. All right. Excellent. Thanks. Anything else on the press contact email areas. Okay, next piece is informational mostly. I've opened Jenkins enhancement proposal for trying to lay out a plan for the transition so that Jenkins will require Java 11 or newer. That will be the eventual end of support of Java eight comments review comments are coming in. There's a lot of work that I still need to do to review the open issues related to Java 11. People are certainly welcome to look at the JIRA issue welcome to comment on that on that Jenkins enhancement proposal it is by no means finished it needs lots of thought and lots of people helping. We should get spell check in this repo. Yeah, that's a good idea. Yeah, I know it's a little bit sarcastic but it's also like not not quite a valid comment why not we should we should spell check it. Yeah. All right and I see Oleg you've joined us. Did you want to do any give us any update on easy CLA or were there any other topics you wanted to. Okay. Yeah, the ball is on my side. I focused on for them when I completely messed up for them. So now it's probably time to get the 20 easy CLA again. All right, thank you. Okay so ongoing. Excellent thanks. Gavin we usually deferred to you for highlights from the mailing list in the community forum any topics you'd like to highlight there. Nothing specifically from the community form. There was the new blog post or post I guess on the form about the one that you approved and posted it to her yesterday. Do you remember what it was. The vendor. Oh, so are you talking about the tweet from test. Yeah, they also posted a whole thing on the community side as well. So I mean that was in the show off group. I always like to show off group. Oh, I see good right. So hi. Yeah, I see what you're saying yes thank you. Yeah so very you know clear and articulate, which is all everything I am right. But otherwise I don't remember anything major coming up there's discussion about I 11 which I think was the last meeting. And we approved your last meeting. Yes, the end of support was approved. And I think it's been implemented right implemented in weekly. So I think we're and I haven't heard any angst from anybody about it. And then yeah I mean it's a community site has been pretty a question heavy last week couple weeks there hasn't been a lot of it there was Yeah, oh there was I guess Google somewhere code is started, not necessarily started started but you know there's office hours I've seen missing those meeting minutes. Yeah so the applications open on February 7. I've been applying for applications since February 21. Yeah, so all project ideas, but yeah for the record I'm not sure what they will be even able to be meant to this year. I think what I mean I stepped down. And neither original mentors out of his house counselor know the new one suggested by his sub works for me. I still have no idea why it is discussed. So right now, I don't feel confident about being a mentor in Jenkins. So neither the Asia schedule nor the Europe schedule work for you. Well Asia schedule is something insane I'm not sure how it was discussed. So, well I understand that if Alisa wants to meet with students in the back region it's probably the best time, but how Jean-Marc would participate. I'm not sure whether it was discussed with mentors. The new slot is just not particularly helpful for me because it collects these meetings I have to attend. I see. Okay. All right. So, well, if I was a mentor of a project, we would be able to find another time slot. But yeah, so let's see, I will, I still want to finish the project ideas and put them on the list. But right now I'm not sure what it really makes sense to apply because there is not enough potential mentors, there is not enough project ideas listed. So most likely in the current state Jenkins will not be accepted. Interesting because we've got four or five project ideas and it's not enough. Okay. Well it's, let's say, by a minimum that is a key for the first year application. But for other organizations the expectation is higher. Jenkins might be accepted, but yeah, right now it's still, let's say, on the lower side, especially when we talk about potential mentors. I know that I'm not particularly helpful there because yeah, I can crumble, but I didn't really contribute as much as I would like to this story. But yeah, if I just look at the current situation, the guidelines are not updated for 2022. The application is not ready, not sent for review, we don't have enough project ideas, we don't have enough mentors. So currently it seems to be at risk. So Alyssa is certainly planning to submit the application draft to the as a pull request by end of this week so that we can review it, discuss it and then after it's been public for at least several days then submit it next week. Well before the February 20 on deadline. So, yeah, the main thing right now will be to actually have more potential mentors listed. This is the most critical thing from what I see about the project. Good to know. All right, because if you have more potential mentors in captain than current injectors. Well in captain we just started one week ago. All right. Any other topics or any other any other items from the mailing list or the community forums. I think so one item is about CD corn. So, there was a threat last message on February 3. But my assumption that basically so the running the trade. So there's a proposal for a proposal for an onsite contributor summit. At at CD con. And yeah, Alyssa or others will run it. Yeah. So one thing for keep on I'm organizing captain coming today. Well it's to be confirmed but so far it looks good. And if you want to organize just happy hour or maybe a small event for those who go to keep on something we can help with. Regarding CD con. For me, I want to start with application process next week. But right now I'm not confident that I will be even able to get to visit for this event. Okay. I plan to be there. So, Mark plans to be on site. I think it's in Austin, Texas. Yes. So you can say hello to wine. Yes, yes I will. Anything any other topics there. Gavin anything further from you. No, I have a couple posts I need to make but I just haven't got to them yet. Great. Then I'd say we call this this session done thanks everybody. There's no other topics I'll end and we can go from there.