 Welcome. This is the Jenkins governance board meeting. It's the 2nd of October, 2023. Thanks for being here. We've got, let's see, no old leg yet. But we do have Kevin Orton's so topics on the agenda that I've got. Include upcoming calendar and then news. And action items, several items there and 2 governance topics is all that I put on with Alex not here. Uli, I propose we put you as the person to speak to board and government officer elections, if you'd be willing. Yes. Great. And then I've got a topic on Oracle cloud costs just so that everyone's aware of what the current status is and then community activity. Are there any other topics that need to go on to our governance agenda today. Okay, then let's go first to the upcoming calendar. So we've got an LTS coming two days from now. No, no, I'm sorry, 2 weeks from now, not today's 2 weeks, October 18. Thanks to Chris Stern acting as the release lead. He's preparing the release candidate. I think it's due Wednesday. Oh, we've also got one more upcoming item, which is LTS baseline selection. October for 2023. So this week. Major events, the board and officer elections are running now any comments on any of those before we go on to the next topics. Okay, then let's take the next thing, which is news. So, elections nominations are now in progress. Uli, I assume that you're receiving nominations. When we get to that point in the agenda, you'll share more with us. I assume. Actually, I can look into the mailing list in the community forum, but actually there are not so many. Yeah, election candidates yet, but we have enough I think so. Great. Okay, so we're looking for more nominees. I know we're looking for need more registered voters. Right now, the voter registration is low and I think we're going to need to do some active promotion to persuade people to register to vote. Yeah. Great. Next topic then was cloud flare sponsoring the Jenkins project. So congratulations to the infrastructure team. It has been awarded a sponsorship from cloud flare, which will host the intent is to host a major bandwidth consumer on AWS on cloud flare instead and thus reduce the AWS costs for the cloud for the, the, for the Jenkins project. The buckets have worldwide distribution facilities. And so we think we're going to get not only better behavior, but also lower costs. Thanks to everyone and to Demian to portal for their work on it. And then Java 21 released two weeks ago. Congratulations to the teams at Oracle at Red Hat at Eclipse at so many places. We're going to release from and no date on a release from Eclipse. Temerun has not released their version, Amazon Coretto has released theirs and several others have released theirs, but Eclipse has not yet. Basil, are you still okay with the idea of doing a blog post that summarizes all the different Java stories as we get those settled. Yeah, I think that's good and I think we're getting more and more agreement to as we get closer to October between between, you know, the, the administrative monitors and the default version and the Docker images everything seems to be slowly coming into with this plan. So that'll be good to communicate that later on in this month. Excellent. Thank you. All right, then in terms of a major announcement, prototype JS will be removed from tomorrow's Jenkins weekly. Congratulations to Tim and to Basel and to so many others who've done months and months of work and an amazing level of of detail to get rid of this 10 plus year old JavaScript library that was felt like it was almost everywhere in Jenkins marvelous marvelous work. The Google sheet shows the current status. There are still some exceptions. Those exceptions are noted here and they're mostly from companies that provide plugins that access their services. Thus, those people will be motivated to do it. When their users start telling them, hey, I can't do this anymore or something's not working the way I expected we've contacted each of these Tim Jack Holmes reached out I've reached out others. So they're aware of this, and we hope that they'll they'll comply quickly by November 15 we're expecting it'll be in the long term support release. Any questions or concerns about prototype JS. Thank you Mark for merging the same. Yes, yes, oh that was that was the best feeling I confess that was a great feeling after that. So yeah, that was that was a treat. The sheet really thanks thanks for to everybody who's made so much progress the sheet is a thing of beauty to look at right. It just shows, hey, we've made great progress in terms of high usage plugins that were detected with the issue. We even received a blog post update just today from somebody who had detected a new set of patterns to use on this prototype evaluation so very very nice thanks to the community as a whole. So next piece is the base LTS baseline is selecting it will be selected on Wednesday. And as far as I can tell, tomorrow's weekly looks like a good choice but this is a good time to be doing testing if there's any such time as a good time this is it. To beginning tomorrow we're going to have a set of code that has all sorts of good in it, including no prototype. Also thanks to john mark Mason to Chris stern and to all the mentors who are involved in Google summer of code it is now completed for projects successful. And the Java 11 end of life monitor will be enabled in tomorrow's weekly build as well. So Java will be end of life. October 31 for the Java project for open JDK and tamarin. And Jenkins itself will declare end of September end of life, because if we wait till end of October we have to do it in the middle of an LTS cycle. Any questions or comments on any of those. Yeah, tomorrow's weekly will also have the Docker images will default to Java 17. Oh, good. Okay, so we've got to believe also the next LTS build will do the same thing. So I think that's going to be two point. What's the next LTS I can't remember the number now. Yeah, we think it'll be 2.426.1 depending on talking about the next, whatever LTS release comes next chronologically, I see 414.3. Yeah, I think that one is also going to have Java 17 as a default in the Docker images because it uses the same code which is not branched by LTS. So in 2.414.3 and in 2.426. Good. And that's that's for users that choose to use a container image that does not include a JDK name in the in the container image name or in the container image tag. Right. So if you say, oh, I must have 11 you just use the dash JDK 11 variant. Great. Thank you. Thanks very much, Basel. Anything else on the news section before we get on to action item. Hey, then action items here and Uli, I think this is a well, let's see. We could talk to this one more time or I've got another topic later on in the agenda. When would you like to share current status. I think it's right now it's good it's a little bit different strange that we have it three times here. Yeah, sorry. Yeah, it's okay. So, I think the, yeah, not much has been done in the last two weeks we are just waiting for new nominations for the boards and nominations as a contributor. And as you already mentioned in the beginning, we have, I think enough nominees for the, as for the positions, but not for the contributors. But yeah, I'm not sure if it's a problem because we don't have much contributors anymore in Jenkins at all. So the same is for the people who want to make an election. So I think it's a normal thing when the contributors, numbers are going down and yeah, the people who want to vote are going down as well. Yeah, so encourage fellow contributors to vote right to register and vote. Yeah. Great. All right. Any questions to Uli or other anything around election process. Okay, so that's the good story now the bad stories come on the action items. I've got the action to complete the retrospective on code signing certificate renewal. I still haven't made progress. It'll be at least two more weeks before I make any progress on that. The retrospective document is there. And I've started to work on it gathering various data, but it's not nearly complete enough to, to make a really good retrospective. So there is fix the concept of sub projects and sigs on Jenkins that I own again needs more pull requests. This one we may do as part of further further work on the Jenkins that I oh site thanks to Chris Stearns leadership with a Google summer of code project that's now looking at when can we switch to use and Torah to generate the Jenkins that I oh site instead of using austra. And then Kevin we've got one for you on retiring the Jenkins, the Chinese Jenkins site anything you want to report there. Nothing for me no mark. Thanks. Okay, and I think we've got this is one where we just have to figure out how to insert the redirect and make sure it works as we expect. And then the last topic is licensing policy and phrasing changes and I've made no progress there we had good comments last two weeks ago reminder from Basel that there are other projects that use, deal with the fact that they may have mixed licenses and we can, we could grab their ideas and use those as good concepts, take those to the Linux Foundation lawyers and get their input on which of the pattern should we use as best choice. Anything on any of those action items. Okay, last one is governance topics and only yes the third time on the list, anything else to share there. Not from me I think I said or everything. Okay, so then the last item on the governance topics is, we had an ongoing email conversation between members of the board. It's kind of a sad story but it comes with a positive ending about two and a half years ago the Jenkins info team subscribed to an Oracle cloud promotional program. It was very, very low cost think like 90% discount so very attractive and work great for us for about two years, January of 2023 that promotional period expired and I failed to detect that it expired and it was on my personal credit card. And it was an expired personal credit card so it stopped getting paid. And so, as a result, they called me by telephone in August, and said hey you're overdue. So I looked at the billing amount and persuaded cloud bees, hey would you be willing to donate up to this amount where the amount looks like it'd be less than $2,000 total. And cloud bees said, yeah, okay. So we've we've used that cloud bees corporate card to pay all the invoices that are open to be paid so that they now show us with zero amount due. And thanks to Damien, the Infra Officer, we've migrated completely off of Oracle by the end of September 2023. So we're expecting no further charges from Oracle. So the account open until I get confirmation from Oracle that they agree all invoices are resolved. And right now, the total donation from cloud bees looks like it'll be $1,800 or less. Any questions on that. Okay. Next topics then. So Java 1117 and 21 in Jenkins. This is the next step of that of this two plus two plus two diagram that we discussed two weeks ago and in board meeting. No changes here it's being implemented now in various ways the admin monitor for instance implements a portion of it and we're going to continue forward. I've will create a Jenkins enhancement proposal to describe it a little more formally with the idea that we've got some upcoming dates that are happening according to the plan. Any questions or concerns there as anyone found problems with that that we've missed so far. Now this looks good. Yeah, great. The next next item then is the Artifactory bandwidth reduction project so about six or nine months ago JFrog contacted us and said hey, the art the bandwidth use for repo Jenkins CI.org is out of range, it's just too high. And they asked us to please reduce the bandwidth use. So what we did is a series of log analysis exercises, identifying heavy consumers blocking or altering their behavior asking them nicely, etc. Ultimately, we implemented one change to the configuration where we no longer keep a copy of Maven central on our own repository. And that happened in September. We now have final log files I've got to do the log file data analysis just to be sure. Got a really cool tool again thanks to Basel he's got created a tool for us that uploads log files to an SQL database so I can ask SQL queries. And it makes it very elegant to do this analysis. We think the project's done and we'll close it out within a week or so. It's already been closed out on the JFrog side right. Yes, yeah, their their answer is hey you're done. And, and our answer is we're done except we'd really like to see the data that proves that we're done. Last item is Hacktoberfest has started. Now this is probably a good one to ask to board members who are involved in the community in dealing with code specifically. Mark Messon has sent the announcement we've got friendly lists in various ways. Has the impact on you been okay from Hacktoberfest or are you getting spammy or noisy Hacktoberfest contributions is it any worse this year than last year is it any better. Maybe let's Uli you're probably a good first one to ask what's your experience been. Yeah, actually I have two or three people who are trying to solve some issues, but they try to solve one code issue and one CSS okay CSS is also code but you're not really. So it's more something for styling, and they are asking questions good questions and they are starting the pull requests. And the, actually, the most of the main problem is that these people normally do not have Jenkins installed on their machine. So they ask, they want to implement something but they don't know Jenkins at all so this is a little bit complicated to get them running because they need to install Jenkins first and need to understand what can be done with Jenkins so. But this was in the last year the same. I have a lot of had a lot of students who did not know Jenkins and did not know what to do with Jenkins or with continuous integration. So it takes the month to get them ready. But this is good, I think for Google Summer of code so we have enough time to get them running. Okay, so what I'm hearing I think is okay we're only two days in so it's not a not a huge sample but it sounds like it's no worse than years past. You're seeing comparable patterns to past years where a brand new contributor doesn't know Jenkins wants to do something and hits the initial bumps. Okay, Basel anything from you. I haven't seen as many as many people doing it this year as before. But in that sense, there's less overall activity so that also means less, both less noise and less signal to answer your question indirectly. Yeah, well and that matches with my observation I think less noise and less signal is both both accurate there is. I've not seen nearly the noise level that we had in past years of spammy things arriving on the on the other side. Also not this, not the number of contributors we've had now we did different things this year right we didn't do an online meet up to get people started we didn't do a major push. It's a much, much lighter effort this year than we've done in past years Bruno or Kevin anything that you want to observe Kevin particularly in documentation is there been anything that you've seen that was Hacktoberfest sort of spammy or Hacktoberfest distracting. I haven't seen anything spammy or distracting coming through yet mark I did see one user who was interested in doing some of the UI and components updates from the pull request we had last year there are a lot of changes made but um, yeah no nothing inappropriate or spammy. Great. And Bruno anything from you. I haven't seen any pull request yet on the few repose I'm trying to maintain. So, no effect from Hacktoberfest first time being the only thing I've seen is a lot, quite a lot of people asking for some help where do I start in in Gitter and most of the time you're the one but no for them being nothing major, but like the others, I didn't go into the forums, Twitter or LinkedIn, whatever they are it's open common we have lots of issues to solve please come in. So, no. Good. Okay, great. Thank you. Maybe other addition. What I noted in the Gitter channel. A lot of people are coming to the Google Summer of coach channel and asking hey I want to contribute to open source and Jenkins, but they don't know Jenkins so this is really a little bit silly so when you try to participate in Google in some of code you should know Jenkins at least you should know where you can make something new or something like that so. I think that's a that's a practical thing that we had seen last year as well right one is that Hacktoberfest is GSOC prep for many of these people right is GSOC preparation and we use it as that as well. Another is, it means that there's there's lots to learn about Jenkins in order to contribute right and you won't make a good proposal for G for Google Summer of code if you don't know Jenkins. It just not possible you've got to know the thing you're trying to improve. I don't know in which channel sorry to interrupt Mark. But yes, I had this very same question on channeling on Gitter and I didn't hear the image from John Markino build your Jenkins muscle but the idea was there. Yes, of course, Hacktoberfest is a good way to learn about Jenkins and build your knowledge so that if ever you want to make a proposal for GSOC 2024. Your proposal would be of a better quality than if you just started from scratch next March. Right. Good. Thank you. Any other observations. Okay, then let's go ahead we'll call in any other topics for today. We'll call an end for today's meeting. Thanks very much everyone.