 Welcome. This is Jenkins Governance Meeting. It's the 8th of January, 2024. Thanks for being here. Today we've got upcoming calendar. We'll talk about news, review action items, community activity, including Artifactory Bandwidth Reduction and Community Contributor Summit. Brief on Java Support Plan and then governance topics. I'd like to bring up the JIRA system that we recovered. The attribution request from JFrog. Azure Credits Donation. Oh, I've got Damian there. I shouldn't. And AWS Credits Donation Request. Any other topics that we need to be sure are on the agenda for today. Okay. Then let's look first at the calendar. So, weekly release 2.440 is scheduled to come out tomorrow. And as part of the next story, it looks good as a candidate to be chosen as the LTS baseline. LTS baseline will be selected Wednesday. And we've got a release candidate that will also be out Wednesday for 2.426.3. It's scheduled to release January 24th. We've got upcoming major event February 2nd. There will be a Jenkins contributor summit in Brussels, Belgium. And looking forward to seeing everybody there and being face to face. FOSM will be February 3rd and February 4th. John Mark Mason is coordinating the agenda for the contributor summit and we'll review later in the meeting some of the details of it. Any questions on the calendar? Okay. Let's look at the other items then. So, on the news side, we're delighted that the Microsoft Azure donation of $40,000 is being actively used. We've consumed the first $1,000 of the donation. Thanks to Microsoft for donating. Digital Ocean is also sponsoring the Jenkins project for 2024 with $20,000 of cloud services. Very grateful to both those sponsors. Thank you. Thank you. Thank you. We had action items on license policy and phrasing changes. Basil, would you like to give us a summary there of the results? Sure. I think we're all done with this topic in the sense that we've taken a few actions, one of which was to explicitly allow public domain. Public Dedications and public domain equivalent licenses, which solves the issue regarding the JSON library, which is released under a public domain dedication. And in addition to that, we've clarified that library plugins should ideally use the license of the wrapped library unless they have significant production code contributions. And that's a soft recommendation, not a requirement. Simply designed to eliminate ambiguity around these library plugins. And there are a few of them that have recently been updated to match these recommendations as well. So we, we're not only recommending this but have actually gone through and aligned reality with our recommendations in several cases. And I think that said, I don't think we have any other open questions regarding licensing. Those are the two biggest questions. And I think they've both been resolved by now. Thanks very much. Any questions from others? I feel like they are, they are done just as you said. All right. Next topic then was an attribution page for the attribution entries for the downloads page that actually I think has has mutated to become a sponsors concept. Anything you want to report that I've put a bunch of items later for for further conversation Basel unless you'd like to give some details here. I have an update on this task, but I think I do. I think I am unblocked to start working on this. So it is on my to do list, and hopefully I'll have some progress the next time we meet. Great. Thank you. Now, I do have one item it is that red hat is no longer a member of the continuous delivery foundation. I had kept them on our top level page at www dot Jenkins that I owe because they were a, they were a premier member at the, at the continuous delivery foundation as of December 31 they exited from that. And I had talked with the red hat representative during a CDF technical oversight committee meeting and said I thought that would mean we would need to remove their logo from our top level page. They're just they're not contributing enough to justify being at that high level that we put GitHub and JFrog and others. I'm open to other comments from others on the board in terms of my thought was we take a short term step, remove that logo from that root page that won't derail the long term steps that Basel is going to take and lead us through the sponsors improvement. Any objections from others. Yeah, that sounds fine. And presumably, the calculus will match when we make the sponsors page and they would be at a different level than you know the highest level. Once we create that page. Yeah, and there certainly are still red hat employees contributing so it's not that they're there. All contribution has ceased but cash contribution has ceased and. So I think we need to bring them down a little early your comment. I think it's fine as well. And I'm wondering what did they tell you when you talk to them. It's this is okay for them. They agreed that it made sense that we would remove it yes so they were they were not dismayed they I think they were a little feeling a little bit dismayed that they were not able to continue with the continuous delivery foundation. The person that was talking in a did not seem terribly thrilled about that but had to do what the company had decided. So and he seemed very understanding that if you're not contributing. We we can't leave you on the sponsors page. Super any other questions on the sponsors topic. Okay, the next topic was me hanging my head again that I haven't submitted the Jenkins that I opal request to combine sub projects. I'm prone given the long life of this should I just drop it from the list and admit I'm never going to do it because at this point I've got so many other things that are higher priority. It's not making progress any objections from others if I just drop it and say Mark's not going to get it done. It's okay. Remove it. Great. Thank you. Done. And then Kevin had one last item on the on retiring the Chinese Jenkins site and here again marks the problem Kevin's done his actions but I've got to do a Kubernetes setup. We've had the discussion with or Kevin do you want to give any further details on that. We've talked to Damien Damien's aware of where we're at is offered time to look at it. We just want to make sure that Mark and I line up on everything before we take that back to Damien and make sure that we have the right questions to ask for him when we do have that session again. I've been out for the last week or so dealing with medical stuff so I'm just kind of getting back up to speed but this is something that we're going to be picking up soon so. Thanks Kevin. I'm not going to lose on any of the action items. Okay on the community activity side, the Artifactory bandwidth reduction project came to us back in. Well it was early 2023 when Artifactory when Jay frog asked us hey please reduce the 50 terabytes a month of bandwidth that the Jenkins project is using, and we took some initial steps to reduce from 50 to 25 to 30. And those initial steps were successful, but they came back to us and said hey could you please reduce further because there are some configuration things that you can improve that will help and still deliver good value to to Jenkins developers. That tuning has been has been done, and we have no traffic to the two problem repositories that we had before. So no significant traffic there. Good win. We've still got some tuning that needs to be done in terms of the orphans local repository has to be removed. We did the info team did reset the caching proxies this morning, and seem to be okay but we're trying to deal with some surprises that Alex Brandis detected over the weekend that I detected over the weekend that are still working through. We're not sure if all of those are related to artifacts, or if it's just a subset where we'll keep working it. Any questions on the that project. I think the orphans was finally removed this morning so that that's all done. Oh, good. Great. Thank you very close to the finish I think, as long as we can get to the bottom of these remaining operational issues. Think the configuration looks good from my side. Excellent. Thanks, Basel. Thanks very much. And then is the contributor summit February 2. So we have 20 plus confirmed attendees, including four of the five Jenkins board members, and most Jenkins officers. So really it's going to be a great session we're looking forward to it john mark Mason is coordinating the agenda, and he's proposed this rough outline as an agenda to fit within the about six or seven hours that we'll have together. We'll have a report so a board member it could be me it could be Alex Uli Basel any any one of us as a board remember, then infrastructure report from Damien release officer we're not sure who will do it. I'm still trying to find a way to get Tim Jacome there but he's not sure he can get funding to travel. Then Kevin will do the Docs officer report and a list of the events officer report Vada Falone will be there and talked about his security report. I was assuming that if Tim can't be there I'll talk about the user experience sick I'd really like him there because we would like to have a discussion about user experience later and he's crucial for that. Then Vincent Latoma of cloud bees has agreed to do a presentation on the kinds of changes that they've had to propose in Jenkins for high availability and high scalability support. We've also got a topic on blue ocean deprecation what does it mean to eventually someday in the future deprecate the blue ocean plug in. Specifically Damien Deportal has some usability challenges that he's worried about that he wants to use for a discussion and that would lead us towards user experience evolution. Then if time allows I'd love to talk about Java support plan but if it doesn't I'm fine if we skip it. Those are the ideas now any questions or concerns there or other ideas you'd like to suggest. Okay, great. So if you have ideas and one of the thoughts we've been having is can could we do some group coding exercises as well. We think we would do those likely after the the bulk of the presentations are done but we think it could be a good experience. We're going to have Stefan speaker there we're going to have Uli's going to be there Basel will be there Alex Brandis will be there. We've got a bunch of people there who could who could really benefit by some time together coding. Next topic then is just a status report that Java support plan continues to evolve but I've got a bunch of work still to do on the what are the details of it. And I apologize that I'm behind schedule I hope to get to it this week. Governance topics now here's the bigger one we had an episode on December 6 where a 1000 plus issue reports were harmed by a spammer. And we ultimately decided we needed to restore from backup so we restored from backup that's done and you can read about it. I've still got to look at some of the things that we that arrived on the system between December 6 and December 18 to see if any of them need to be restored the security team did a specific bring back of things that were relevant to them. There are some other issue issue tickets that were reported then that I need to look at any questions on that Jira Jira recovery problem. I don't think it's that high a priority to get every single last piece of data restored. I mean, if it's too much trouble then you know I wouldn't be opposed to just dropping it and saying that this is good enough. We restored the bulk of the changes. So that's fine with me. Yeah, and you've described exactly how I'm approaching it I'm acting like I want to look at those things and see which of them might be serious risks in terms of did we have an important bug report that arrived there that has been misplaced. Otherwise, you're right I think we're going to just leave it as is good. Next topic then was the the sponsors page the attribution request. And here we'd had two different proposals one from Basel for various naming the other from me on naming. Are there any things we need to discuss your Basel. No, I don't think so. I'm hoping to make some progress on this this month so hopefully I'll have something more concrete to talk about soon. Great. Excellent. All right. The last two items are the Azure credits. There it's me talking not Damien. The Azure credits we've now confirmed that we've spent the first $1000. Thanks to Damien for not disrupting our use of Azure billing processes and still being able to take this in. We expect that that will accelerate because we think that we will spend about 3k a month from the from the Azure donation based on our predicted consumption will watch it and see where we're thrilled. It's kept us under budget overall and clearly under budget compared to what we had proposed to the CDF for budget. And then the last item was before the Christmas break before the end of 2023, I submitted a request to AWS for a donation to the Jenkins project. They said that they would reply within 30 days so I hope that by end of January 2024 will know if if AWS is willing to donate to Jenkins as well. Any other topics we need to include on our agenda for for today. Thanks everybody.