 Welcome to the Jenkins governance meeting. It's June the 30th, 2021. Thanks everyone for being here. Uli and Daniel, thanks very much. So topics that I had, news, keep it very brief. Daniel, I assume that you'll have something to share with us on news. Thanks very much for your heroism today. And then a brief on Jenkins funding update, just a status report, plugin, end of life policy, summary or discussions from the developer list, discourse. Any other topics that need to be added? Not for me. Okay, then let's talk news first. And the biggest news is Jenkins 2.289.2 and 2.300 security releases were delivered today. Thanks, it's very, very much Daniel for doing those. It also fixes security issues in three plugins. Very, very grateful for that. Anything that you wanted to share, Daniel, with regard to the security advisory? No, particularly the fixes are fairly straightforward. There is one issue I sent an email to the developer list that due to infra issues this afternoon that we had to work around these two Jenkins releases as well as Selenium HTML report plugin are not available in the releases repository in our factory as they would usually be because that didn't work this afternoon and we had to, I made the staging repository that we generally only use temporarily. I made that public. So I think nobody will be affected by this because it's part of the virtual repository called public. So as a dependency in plugins and such, it should just work, but there may be issues and we will resolve that as soon as our factory behaves normally again. And additionally, I mentioned some of the repositories and workarounds we had to apply and I would ask everyone to not rely on the continued presence of these workarounds just in case. And that makes sense. So your point there is that in order to handle some challenges earlier today with infrastructure, you had to do something a little bit different but temporary with the repository configuration. And eventually your intent is to go back to the standard repository configuration. Essentially, yes. So the artifacts exist. They're just in a different repository than expected but once we can move them over, we will and these temporary repositories will go away. So nobody should be relying on them. What details about that are in my email to the developer list. Great. Thank you very much, Daniel. And so let me make a note of that and I will include a link to the developer list for details of temporary, yeah, temporary artifact or temporary repository workaround. Yeah, very good. Okay. Thank you. Other news, the contributor summit. We hosted the summit. The recordings have been posted to the playlist. I still have the action item to post a summary and a list of action items on community.jankins.io. I hope to do that within the next 24 hours because the value of the information decreases the longer it goes outside of it. Excellent conversations around plugin end of life, Java 11, Jenkins X interoperability, cloud native, all sorts of good things. Google summer of code. We plan to have a CDF webinar for the week during the week of July 19. That's when July 16 is the end of phase one and we're seeing great progress from all five of the Jenkins projects and look forward to six projects in the CDF webinar, including one from Stinnaker. Okay. And we've got the Olegs taking a break in the Jenkins community, but we'll continue as the technical oversight committee representative and he'll continue mentoring one of the GSOC projects. Anything else that needs, welcome Randall, anything else that needs to be discussed on any of the news topics. Okay. Then Jenkins funding updates, this one to give a brief summary, Jenkins treasury has been hosted at the software in the public interest for many, many years. And now that we're part of the continuous delivery foundation, we can move those funds from SPI to CDF. It's in progress, but it will likely need to wait until Oleg returns. I don't, I'm not aware of anything that urgently needs us to move this without his help. And there are some stages and steps in it that will just be smoother if we have Olegs help to do it. Now, plug and end of, so any comments or questions on funding updates? Okay. Plug and end of life policy is continuing to be discussed in the Google groups in the developer list. And it was discussed in depth in a session at the contributor track. Encourage you to view that, that read the notes from that video and continue the discussions in the Google group. And then just by way of notes, community.jankens.io is up and running. And as far as I can tell, we're getting some traffic to it that's letting us make things work there. I will post links from the contributor summit into it and encourage you to use it for conversations. Any other topics for today? That's, now, Daniel, I did have, I know we've got the LFX security two project running or running is the wrong way to say it under discussion, but I didn't have any status to share here. And so I intentionally did not put it on the agenda, just saying, look, we're watching that thing evolve and we'll get involved with them as they continue to involve with us. All right, I have nothing new to share. I saw a threat scroll by, I think yesterday or the day before with some updates, but I was busy preparing the security updates. So I don't know the details yet. Right. And that's mine as well. I need to, before we take any time in this meeting, I need to be sure I've reviewed it and thought about it. So as far as I can tell, we're set for this meeting. Thank you very much for being here. Yeah, thank you most of the recording. Thanks everybody. Bye and enjoy the week. Yeah. Bye, bye.