 Welcome everyone. This is the Jenkins governance board meeting. It's March the 6th 2023 topics that I had on the agenda include news. Action. Oops, action items. Code of conduct reminder was one that I wanted to just bring up. And it's more for discussion JIRA license changes and our continuing use of JIRA CDF topics and community activity. Are there any other topics that others want to be sure we add to the to the agenda. Okay, then let's go ahead. So congratulations first to the Jenkins project and being accepted as a Google Summer of Code mentoring organization. And thanks to John Mark Messon to Bruno Verachten to Chris Stern to Alyssa Tong who are acting as organization admins this year. Thanks also to the mentors or the potential mentors, including Basel Crow me and others. Thanks very very much. Right now it looks like there are far more there will be far more application applicants than we have projects, and we will limit the number of projects by the number of lead mentors that are available. We want to be sure that the projects have high chance of success and a successful experience for the contributors the new contributors not just for the Jenkins project. Other announcement is that next when this Wednesday so two days from now, we will have a security release, including Jenkins 2.387.1 the first release of the 387 LTS line 375.4 and 2.394. And then the February newsletters being prepared. Submit your, your text. If you're part of that, please. Let's like roll on any other questions or comments on news. I have a question about Google Summer of Code. I'm wondering why we have so many applicants this year is the program different. So, I think it's a factor of five more than last year. I, I don't, I don't have a fundamental reason why we've certainly been better organized this year than we were last year and better promoted. But I have a suspicion that there must be active promotion of Google Summer of Code in the universities in India right now. And I think that's the primary catalyst, but I, I don't know for sure really good question. Bruno, maybe you have other insights. I think this year Jean-Marc has taken his vitamins or vitamins, but other than that, no idea. Okay, great. All right. Okay, next topic then was on action items. So first item on the list rework the press contact great page. Alex, do you want to give us a report there. Yes, a couple of weeks ago, Gavin Morgan started a post on the development mailing list that he wanted to remove himself as point of contact from the past web press page from Jenkins.io. He submitted a pull request and this took place. He had no longer press contact on Jenkins.io. He also noted that he has been a press contact for a couple of years by now. And within the past couple of years he received basically nothing but spam, or was subscribed to mailing list he never wanted to be in. So he came up with the idea that we probably should rework the press page and get rid of the individuals and rather focus on one single point of contact. So he came up with the idea to use the press category on the forums, which I wasn't aware before. So I submitted a pull request to Jenkins.io, which gets a rid of every person and recommends to use the press press subcategory or whatever it's called on this course. Good. So that's in this pull request I assume Alex. Yes. Great. Okay, so what it's doing is as you said getting rid of a bunch of individual contacts particularly this one for instance has not had involvement in the Jenkins project in over two years. So far better that we give a contact to some to a place where we can see it where multiple people will see it and can act on it. Yes. So given one place that is actually public available. So not something like email inbox that possibly gets lost if you don't check in it regularly. Right. I left the note to the security. I left the note to the security team. In case there's something they need to be reached out to but yeah that's basically it. Yeah, so and. Okay, very good. Yeah, I'm surprised. I see I would assume they prefer mailing lists and I would guess they will likely still continue but but you this is just a link that points people to a page that then says send to the mail and send to the list or Yeah, the specific page has a disclaimer like added to not reach out to the security team for certification and stuff like that. Right. That's basically the reason why I don't want to meet their mailing list there. Good. Okay. Any questions from others on on Alexander's proposal. Okay, next topic then thanks. So I think this one. Are you ready to move it out of draft Alex so that we could we could go ahead and merge it. For sure. Now I guess press contacts is something that really should have a choice by the board. Yes, this is at some level a project organizational level this decision. I propose that we ask here for board members for actually all participants to give their approval that yes, we're okay with this conceptual change of press contacts I know. Oleg had said he was fine with it in separate email. Okay with a call for a vote here to be sure that we've got everybody agreed. Yes, that makes sense. Okay, so let's let's get the votes then. All right, so votes from the board so I'm plus one. Plus one. Okay. Alex, your plus one I presume. Yes, I'm plus one too. Okay, and votes from other participants here Basel, Kevin and Bruno, any objections, plus one from all of you. Yep. All right, great. Thank you. Perfect. All right, thanks very much. Anything else on that action item. Next topic then create and distribute election badges. Sorry, no progress for me and no intent to make progress in the next two to four weeks. Would anyone objective I just deleted this action item and said I'm not going to bother with it. Yes, it's not really important. Great. Deleting. Okay, thanks. Next topic was easy CLA to be documented by Oleg and no progress there. I don't feel a grave concern that there's no progress but any comments or insights from others are we at a point where we need to take this back from Oleg and put it on somebody else. I think we should just pick it up if there is actually someone who submits the CLA. Okay, if I remember correctly, there have been a couple of people maybe three during 2022 who actually signed the CLA, and these have been on corporate be these have been on corporate. Yeah, the corporate one so I don't think there's much interest from individuals to submit a CLA at this point. Okay, so low risk continues continues. The next action is just a standing action item for me to create the agenda empty agenda. I think I'm well enough practice, I'm going to delete it. I'll keep doing it if you catch me not doing it, I will take the action item then. Next one was pull request to update the Jenkins.io site to combine sub projects and six into a single concept of working groups. I've not done it, and it's not likely. This is this is mine I accepted I also need to update roadmap so it's it fits with me. Next topic retire the Chinese the Chinese Jenkins site. So this one we had originally started with an action item oh like ask them, we've received the answer now, Rick has recommended that we redirect the Chinese pages to English equivalents and Kevin. We put it on Kevin our docs officer to track this help desk ticket that is proposing to replace the Chinese pages with redirects to English pages. I assume it's relatively straightforward but like many things in that that world of web pages and redirects I could be very terribly wrong. Any questions there. Okay, next. Are we are we blocked out anything or is this. Do we have all of the pieces in place that we think are needed to move forward. I think we have the pieces that the thing that we don't have is someone to do the work to make the changes, because, as far as I understand it the Chinese site is under our control. So when I go to the Jenkins that I oh site here. I don't think I don't think the Chinese pages under our control associated in a separate GitHub repository. Oh, okay. Unless you're part of the organization I'm not aware of, but it's in Jenkins dash, the Jenkins dash, I don't know. Yes, here is the organization. Right it's like this. So, but whatever repository is generating this content. It's still on a domain that we control so we could redirect it somewhere else and stop using the content from that repository. I think so right I mean I think we have control of the DNS or the this we have control of this website of this, the web server that answers www dot Jenkins dot IO and therefore we should be able to redirect those pages. So is it a matter of finding the mapping of old page to new page is that the work that's that we don't actually since it was since it was translation I don't even think there's a mapping needed it's rather. Any any URL that includes ZH slash at its root needs to have the ZH slash removed and use the same URL. That's even easier than I thought it would be. That's that's my that's my assumption anyway and I would, if that's not the case and they had done custom content. I wouldn't trust that custom content anyway because it's now at least two years out of date. I think it's just doing the redirect from ZH slash to root. Yeah, that seems pretty straightforward. Yeah, now. Now I haven't checked to see where let's see this is the improve the page. In fact, this the site page the pages are in a repository that we control Jenkins info so absolutely we've got, we've got end to end enough control of this thing to be able to to make the change we just need someone to do the change. Did that address your question Basel. That was good context because I wasn't sure how far along we were but it seems like the biggest concern of mine which was producing the mapping is actually not a concern at all. So that's great. Right, so it's it's basically, I think we need someone to read, we need a redirect from. www.jankins.io slash ZH slash to that. And accepting the consequence there is, if they did custom content. It's now hidden in a GitHub repository that we have. Great. Anything else on the retire the Chinese Jenkins site. Okay, next topic then was archive the governance meeting notes and I have made no progress on this. Sorry, Gavin's done the work and I've got got more, more work to do. Last item was build monitor view plug in Basel anything you want to report there. We contacted the GitHub organization admins through a help desk ticket. So it's just a matter of someone with the appropriate access, executing the transfer. Great. Okay, so, so we're now in execution mode on this one. Great. Yeah. All right, thank you. Thanks very, very much. Any other action items or action item topics that we need to discuss. Okay, next topic was, this is a, this is a reminder for me and an experience thing so in the Jenkins code of conduct. There is text that says, board members are responsible for clarifying enforcing standards of acceptable behavior. It was not too long ago that I read this for the very first time and thought, oh, I'm a board member I have a responsibility here. So, my reminder was then became pertinent when we had some rather, rather harsh comments on on a getter channel and I stepped in and said as a board member. I am acting on this responsibility and saying that you need to be aware of code of conduct. And the user responded very positively. Oh, you're right. So sorry. And then we had a good conversation. And it was a, it was a good reminder that he has a board member it's okay that I, I know that we have a code of conduct and we expect people to adhere to it. Now if when you look in when the rest of you look and get her chat and you see that, and you have a different opinion of it, you are certainly welcome to tell me that different opinion or say oh no that that should have been handled very differently I'm open to that as well. I've also seen this conversation, and I was only on phone available so I couldn't really answer on this topic as well. But I think it was a really good reaction from you and I think it was a really a good discussion afterwards so it was, you know, maybe sometimes you just need to say a simple thing and when everything is working okay. And that's now, now there've been other cases where where I, there was a case some six or nine months ago where I, I noted someone that they were they were in, I thought they were in violation of code of conduct, and I didn't initially cite that I was a member and he said, I think you're, you're, you're out of line. I was, I was a little too gentle, and they came back with sort of more harsh phrasing, and I, I then put on my lawyer mode and said I am a member of the board I am enforcing the code of conduct. And that was that didn't go nearly as well as this one did where I started right off by saying hey look, I'm a board member and I'm noting you're, you're, you're not behaving the way we want. Great. Anything else on that topic. Any Alex for instance you're, you're frequently on these kind of interactions any places where you've seen problems or wanted to highlight anything. No, not much if I'm interacting with the guitar channels. People are mostly friendly and have friendly and nice tone. At least I didn't see anything disrespectful harsh or I don't know, even rude comments so yeah. Great. Super. The next topic then was, there's a Jira change that is coming so Atlassian has stated that their move in general for open source projects is to move them from being self hosted to being hosted by Atlassian. Most most projects that makes a lot of sense. If you've got a relatively small Jira installation, if you've got a reasonable number of users having Atlassian hosted is better for the open source project. The Jenkins project is somewhat distinct in that sense because we have over 100,000 users on our Jira installation and we've got a long history of use of that with important security procedures etc. And Atlassian thankfully has approved our continued continued use of that system, even after February 2024 and Linux Foundation plans to continue hosting us. They're going through some detailed discussions about what it means to make this transition because on their side at Linux Foundation they will need to do some effort to to get us to keep hosting us this way. I'll keep the board aligned and aware so that you're informed as things happen, but I've got an open help desk to stick it with the Linux Foundation, and they've confirmed that they've got access to the information they need from Atlassian. Any questions there wasn't there a blog post. Oh, thank you. Yes, thank you, Mark. Good, good point marks proposed blog post draft has started but not finished. And the reason it hasn't finished is I sent it to Atlassian for approval they said, it's only two paragraphs do you want to say some more stuff. Oh yeah I should say some more things and so I started gathering data mark to gather more interesting data, more data to make the blog post more interesting. And so I've got some more writing to do things like hey how many, how many issues are there and how many users are there and those kind of sort of facts and figures I think will help people be more interested. And so, once we get right the blog post. Once we have final details from LFX, because they may have to schedule some downtime in order to do the transition from from the current configuration to whatever the new configuration is. Any other topics or questions on the JIRA license change. Okay, next topic then with CDF topics. So, one of the items is that the technical oversight committee for the CDF meets, I believe that's monthly, and they've asked their contributing projects to present status reports. They've got a status report already scheduled for March and I believe for April and I tentatively put us on the agenda for May. So I was I'll create the presentation share it with board members. Invite you to comment and share it actually share it with this group. Invite comments, corrections, etc, and then we'll present it. If others would like to be part of the presentation would be like to be co presenters I'm happy to have that as well. The next topic then was during the last technical oversight committee meeting. They noted that one of the facilities that we use in the Jenkins project this dev stats facility it was created originally by Linux Foundation will eventually be replaced. And they've started a working group to be sure that the Linux Foundation knows what things we need so that we don't lose information as a result of this transition from the dev stats thing to the new Linux Foundation insights program of data collection. I'm involved in that others may be involved as time goes on any questions there. Does your mark know about that. He does. Okay. Yeah, so just so everybody's aware this is the kind of data that this shows this is two years of Jenkins contributor counts across the entire set of Jenkins repositories. And the bottom line is companies where they make guesses which company you're from the top line is individuals. And it's fascinating that they can gather this kind of data from public commits. And it helps us decide hey are we being effective we got really concerned back here in December, when the numbers plummeted right when the numbers dropped. And we're glad to see that the numbers came back. There are other charts like this that use the data from GitHub to help people understand how an open source project is doing. All right, next topic then was on community activity. So here, we've got an ongoing project to try to reduce the bandwidth used by repo Jenkins CI.org. What it's been doing is costing it's costing a lot of bandwidth to its sponsor art and JFrog, and they've asked us hey please can you find a way to reduce how much bandwidth you're using. So the infrastructure teams created the artifact caching proxy, and it has done a really great job we were previously three of the top five consumers were Jenkins own CI servers. And with the caching proxy, we're now completely off that list. So good win. Now there are still other things that need to be changed like, we've got a misuse that's happening at an IP address in China that we can't figure out how to get them to stop. We see the pattern where we just haven't found a way to find them to ask them please stop asking over and over and over again for the same files. So we continue to log file analysis. Thanks to a brilliant little tool that Basel created that uploads JFrog log records to an SQL database. So I can sit there and ask SQL questions about the usage of the system. It's it's a treat. So be aware that future more changes are likely coming up. But we'll continue making progress. Any questions on that one. Are they the JFrog, give us any update about adding the block IP feature. Yeah, so far no possibly working on that or right so no final answer on on blocking specific IP addresses. We'll come again today. Because that would that would be the single biggest gain if we could block this exact IP address. I think. So I will ask them. Yes, until they change it, but we'll give us a few weeks. Yeah, well and that was why the that was why the JFrog people said hey it's not even worth it, because this could be they maybe that they'll really change it but looking at the pattern of use. I'm not sure but what it's not really just a computer, not some something more than that and somebody's just doing things that don't make any sense on that computer. Other topics, we've got Alyssa Tong and I will be at in Los Angeles ended this week for an open source conference the Southern California Linux Expo. And the CDF Jenkins awards nominations are open congratulations Alex for your nomination. It's fun to read those nominations. Thank you very much for contributions. Any other topics for today's meeting. Alright, then I'm going to go ahead and call an end here. Thanks very very much. Recording should be available in 24 to 48 hours.