 Welcome. This is the Jenkins governance board meeting. It's the 27th of November, 2023. Thanks for joining. Topics on the agenda include upcoming calendar. News items. Action items. Community activity and I've added an item that was not in the preview agenda that I sent on the Jenkins contributor spotlight. Oops. And so then governance topics added a topic related to a letter of recommendation request from a GSoc contributor that I wanted some help on and attribution request for the downloads page. Any topics that people want to add to the agenda that aren't already covered there. Okay, then let's go ahead with the agenda items we've got. So on the upcoming calendar. Jenkins 2.426.2 is scheduled to release in a little over two weeks. Chris Stern is the release lead and he's opened the backporting pull request. The release candidate is scheduled to go out on Wednesday. It looks positive the backporting pull request contains only two items and neither of them is particularly huge. The next weekly release is 2.434. And there will be a two week break in the LTS schedule over the end of the calendar year. So we like to in the last two weeks of December and that that holiday period for many regions to take time off so instead of four weeks between 2.426.2 and its next release dot three, there will be six weeks. It was discussed in the developer list. I don't expect any break in the weekly release schedules because they're automated. We're not going to turn off the automation. They, it's not harmful to have a weekly release that has relatively few changes in it. Any questions on any of those release related dates. The next topic is FOSDOM 2024 is our next major event. February 2nd through the 4th of 2024. On Friday the February the 2nd we'll have a Jenkins contributor summit all day at a facility in in Belgium that John Mark Mason has reserved for us. He's gathering agenda topics in this community forum. And you're welcome to propose them there we've already got understood that Uli you'll be there and that Alex plans to be there. I plan to be there and I have high hopes to be there and I expect that Bruno will be there. I'm not yet sure. Actually, if I will be there I hope to also have Basel there. Depends on budgets. FOSDOM 2024. All right, the next topics are on the news items to a little less than two weeks ago we released Jenkins 2.426.1. And the ratings look really good. Congratulations to everyone who is so involved in this release. Notice that number 79 that's users who have on their own. Oh, somebody says they rolled back. Okay. And since I captured this about 30 or 45 minutes ago, 70 side 79 say no major issues to who said they encountered notable issues and one says I had to roll back, but did not give us an issue report number so I don't know what their cause was. When I look at the Jenkins Jira tracker, things look really good for it. The removal of prototype JS seems to be going very, very smoothly. Java 11 end of life administrative monitors get some some noise from people, more even more noise from the red hat enterprise Linux where people say but what do I do I'm stuck on Cento seven. And the answer is you get off Cento seven. All right, that's where all we're doing is giving you six months warning that that operating system is dead to the vendor in six months and Java 21 support thanks special thanks to Basel. He detected a an intermittent memory leak in one of the automated through one of the automated tests and submitted a script security plugin pull request to resolve the intermittent memory leak. And that was just released less than two hours ago. So thanks very much that's a good sign that Java 21 is looking good and we're detecting we detected an issue that Basel I think you had said it failed in one of 50 or one of 20 test runs. No not of 25. So, so it truly was one of these intermittent failures, but that's it's good that we're testing Java 21. We are watching the Jira issues quite closely. There is one issue related to the removal of an adjunct of a stapler file that is getting some noise and we'll need some more investigation as we go forward. Any questions on the news items. Which is the adjunct one. Do you remember. I can, I can get it separately. I think it was, let's see, 7236 is the issue number. Thanks. Yeah, and, and it's where I'm, I'm working with, I've been asking questions to the submitter and a new submitter who attached to it. I actually already fixed that in Scribbler like a couple of days ago, but I don't think it's been released yet. Ah, okay. Yeah, well and the, the Scribbler problem was not the one that worried me as much as the, as the next comment from a user which was unrelated, completely different but happened to have the same message. So that's the one that the Michael Lupo thing that worries me more. Action items then is our next next on the list. So I had an action to create an issue to drop the weekly build of bomb. That action item is implemented and done. Basel we had listed that you're going to drop the middle two lines from the full test label. I don't, I don't remember if that happened or not. Do you want to give a report on that. Oh, I filed the issue like we talked about. Okay. The issue has been filed. Great. That's, that was the action. I'm so I'll put that in. Thanks. And then Damian was going to create an issue to switch the agent implementation to virtual machines and I, I didn't find an issue in the tracker there. I'll have to go looking separately. You had an action item to propose a PR revising the election process to nominate a month earlier. Anything you want to report there. I proposed the PR. No, no good. Okay. It waits for reviews now. I think Alex already reviewed it and helpful if someone else could review it as well. Good. All right. Thank you. I don't know the number right now, but yeah, you will find it. Right. So I assume the PR was submitted to the Jenkins.io repository and therefore, yeah, it's, it's on my list to review then. Great. Thank you. All right. Next action items was run the officer, oops, run the officer and board elections. Alex or really you want to give a further report there. But I don't think there's anything new to say compared to the last meeting. Like there will be no elections. I've closed the election group on the community forum so people can't join to it anymore. But that's basically it. I think, yeah, I think we need to remove all a couple of few groups and add bezel to a few groups and the middle of December when the actual transition happens. But we should revise the documentation from last year, which groups exactly the change there. Because if I remember correctly, you wrote that down and I think you can simply reuse that. Great. Yes, that's right. So remove Oleg and add Basel to the appropriate groups. Now, do you plan to do a blog post or other form of announcement? Yeah, actually have a blog post and draft or do I have a question. We should definitely publish a blog post, but around the time when the actual transition happens, like not now, because Oleg is still a board member that would be weird. But around the time we changed that we should announce that Oleg is out of the board and Basel as a new board member. Similar like with it last year. Great. Thank you. Thanks very much. Which date is it? Is it on the 2nd December or the 11th? I had made notes on the 11th, but it's a good question. Did that maybe my notes are wrong? The 11th is a Saturday, maybe the 10th or 13th. Oh, no, you're completely right. That's the 11th. That's the last government meeting we'll have this year. Okay, so it's on the date of the governance meeting that will do the transition. Absolutely. Okay, not on the, I thought in the past we'd done it on the, I guess it doesn't matter crucially. In the past, I think it had been, as Uli mentioned, December 2nd, independent of governance meeting dates. Uli, am I remembering correctly or? Well, actually, because I just filed a new pull request that documents the new process I found the date the 2nd of December. So I did not remember it, but I've seen it in our documents. So I wondered why we have such a, you know, it's not a strange date, but typically I would say we have a period is until 31 of December or something like that. And not the 2nd or the 11th. These are both somehow strange days for an election period. Right, compared to end of month or start of month. Yeah. But actually, it's not a political position. So it's okay if he chooses the 11th. So I'm fine with the 11th. Whatever makes sense. So Alex, you're okay with the 11th I assume and Basel no objections from you. Yeah, I simply chose the 11th because that is the last governance meeting and during the meeting we can make sure that everything works out that we didn't forget anything, but I also agree the 2nd is an arbitrary weird choice. Great. Okay, so we'll, we'll look to the governance meeting on the 11th as the place where we checked that all the changes are correct and complete. All right. Thank you. Anything else on the governance officer and board elections. I wanted to go back to that previous bug that we had talked about if we have a minute. Yes. The user who 2nd user that you were referring to just updated the ticket and said that they have solved their problem and sorry for spamming a different bug report. Oh good with that. And the original problem with the script where I already fixed last week and it was released already so I think we're all I think we're good to go with with that ticket. I'll make sure the, I'll make sure to watch the ticket in case there are any other updates. Thank you. Thanks very much Basel. Thank you. Thank you. All right, other action items. So I have the action item to converge us to sub projects and six into a single concept called working groups. No progress. Sorry. Next one I am proud to say that there is some progress Kevin Martins has started his local Kubernetes development environment to prepare to remove the Chinese Jenkins site. And Damian took us through a tour to how you do that. I need to do the same and then once Kevin and I have got it we'll meet with Damian to do one more step before we're ready to submit the poll request that actually removes the site it's a change to the home charts that deploy the Jenkins.io site. And therefore Damian correctly said hey let's have you test drive this locally be sure that you're confident in your poll request. And once you've prototyped it and seen it then we submitted to review. Let's see. I've also got the action item to draft a proposal to the board for policy and phrasing changes on licensing no progress there. So I apologize for any apologies that's that's going to be delayed it may be all the way until the first of until January 2024 before I start on it. And then the last was update the GitHub repository I've been faithful about updating the community site but I've still got to go back and touch the update the GitHub repository so we have a an archived copy outside of community Jenkins.io. So action items that I might have missed or topics that need to be discussed. Okay next topic then is community activity. So we've got, we've got a preparation for a new site that will be coming online contributors Jenkins.io as a way to highlight the stories of our top contributors. The finalist for this was the realization that Linux Foundation contributor stats show that we've got 500 to 600 Jenkins contributors in any given 30 day period. That's a great result. However, we did some additional analysis and what we see is that the top 30 contributors. So 5% or less are contributing the vast majority of poll requests to the Jenkins project. And it is much, much more valuable for us to work to retain those top 30 contributors than to worry about adding new contributors into the into the big pool. So we've started a project to retain top contributors in the advocacy and outreach SIG. What we've done is first did some data gathering to identify those top contributors based on poll request data based on others some other data sources looking who's who are these top contributors and then ask them to answer a survey about their experiences coming to Jenkins and deciding to be a Jenkins contributor. So what Kevin Martens has done is he's preparing the answers to those surveys to be used on this site contributors Jenkins.io where we will see those new contributors or those not new contributors those contributors and their stories as part of this site. The infra team has has provided a repository to host the stories. The site content will be visible later this week on contributors Jenkins.io, it will be, and its processes will be similar to how we do stories Jenkins.io today. Thanks to Alex as the first of the of the highlights Alex Thank you very much. I think you were one of the first respondents to the proposal. Alex Earl is also up and the ideas that will spotlight a new contribute contributor about every two weeks with 30 plus contributors that gives us a good years worth of seed material for this initiative. In addition to that cloud bees has donated funds for a thank you gift to be sent to these top 30 contributors and Alyssa tongs coordinating that. Any questions from me any questions from you as board members on this topic, any concerns any things where you're worried or things that we need to we need to address. No, I think this is really wanted to highlight that it's not a matter of one to the exclusion of the other but doing both doing both recruiting new contributors and pertaining existing ones, there's no. This whole thing is not to the exclusion of one side or the other, but just making sure they were balanced in our approach. And I think that's a good thing to highlight, because we still are doing recruiting efforts. Good. Thank you. Good insight. Who Lee your comment. I think it's a really good idea to see the people behind the project. So typically you see only the initialize it up credentials or something like that but you don't know who is, or who are these people so now you can see that this is a really good idea. I agree with you I think I like Basel's point very very much that this is not excluding new contributors. What for me it was is a realization that I had been so intensely focused on the product the efforts to to gather new contributors that I was losing losing track of the fact that retaining our existing contributors is actually much more valuable right adding 10 new new contributors. The loss of one of those top 30 is an unbalanced so we we want to balance our efforts to retain these top contributors we want them to know how grateful we are for what they do for the Jenkins project. Great. Thank you. Any comments for others. Alright, thank you. So, next topic then was was Java 17 Java 1117 and 21 and here. The key thing is the Jenkins enhancement proposal and I've got a bunch of work to do there. We've done a very good job of noting that we need to be much more detailed in our planning for this. What does it mean to add a new Java version and how do we do it. What does it mean to make it the recommended version. And for me right now the concern is, what are the steps we need to do when we drop a java version. The reason this one is important is come October of 2024 when Java 11 is no longer supported. We want to be executing a well defined plan that has a good way of retaining everybody and keeping things smooth and comfortable for users. So, further refinements are coming in the jet my apologies that it's not made the progress yet but it will. Any questions on that Java support plan. Next topic then is into the governance topics. I had a request from a former Google Summer of Code student Rishabh, but already asking for a letter of recommendation as part of his application to an advanced degree program at a university. He didn't provide the letter of recommendation but he said hey it needs to come from the organization on organization letterhead so that's a US thing on paper that has our logo on it. My question to the board was, is it okay with the board. If I write the letter of recommendation as Mark weight, but place the Jenkins logo at the top of the page, and in the from statement say that it's from Mark way to member the Jenkins Google Summer of Code mentor. Is that okay, or am I misusing my position as a member of the board to do this. Comments, Basel Basel you're giving a thumbs up okay that's good I take that as a yes. My experience in academia probably is best to guide me here. I realize you're not a US university but nonetheless. What, what would you any guidance you want to offer here on how we should handle this. I think I also have to write such recommendations for students who work in or who apply my courses and then they want to go to a company and they want to have some recommendation or they want to join another university in another country. And therefore you need some recommendations and typically yeah I do it. It's hard work to do such a recommendation. And, yeah, and I think if you worked with with students somehow. It would be fine if you would do it for us because I don't know the student at all so. Yeah, it would be helpful if someone who worked with him can write this recommendation. And I'm fully supporting is this. And if we put our Jenkins sign on it it's fine for me as well. It does make sense. Thank you. Great okay so now one of the other things that Richard said that they require is an organization email address and we don't have those. So I'm just going to use my, my mark dot erl dot wait at gmail.com address and hope that that will be sufficient. Any comments or concerns from others on the idea. We have the governance board mailing list. Oh, that's a that's an interesting idea. Yes. Okay, add the right right. At least as one of the addresses right. Why not I mean adding my email address and the governance board even better. Good. Okay, thank you. Any other suggestions. Any other insights or concerns there. Okay the next topic is an attribution request for the downloads page for JFrog. This one. I like the request because it reminds me that we want to be thankful to our sponsors and find ways to express that gratitude in ways that help them. So, JFrog submitted a one of the friends of Jenkins at JFrog asked that we add an attribution section to our downloads page. So that's this page here so Jenkins download saying hey thanks to and at the bottom here we have public cloud but we don't have a thanks to our sponsors who host the download sites. I thought that's a good idea. In this case, JFrog actually does not host the content that we download from this site we use our own mirror system. But it's a good excuse seemed like a good excuse for me let's describe the architecture in a link and provide the JFrog logo and the Oregon State University logo and the single university logo and etc. On this downloads page with a link to our downloads architecture description so that people understand how we handle downloads. I don't think that this requires board approval per se but I wanted you to be aware that we're, we're doing such a thing any concerns or comments there. Okay, do you need any help creating the PR for this or is that is that already have covered. I, I haven't, I haven't created the PR that's a that if you'd be willing to take I could use the help just because I've got so many other things that I'm worried about. If you're available Basel I'd love to have the help on it, if not I'm also okay it's, it's certainly something I can do and have done before. Yeah, I could take the action item to do this if you just give me the requirements for what they would like to be attributed for. Great, yeah okay I will let me I'm going to put that on the action items list then and let's we'll go from there so. Create. Actually let's put it this way mark provide details of the attribution for the downloads page. Basel create the blog post. Not the blog post create the attribution pay attribution entries for the page. Great added to the action item list. Thank you. Thanks very much. I'm glad you can see them. Anything else on the attribution request. Now I guess there is one, one idea that ever the mirror had offered in a conversation with him. He noted that the eclipse Temeron project uses a thank you widget on their top level page. I wanted to show it to you just to see if you thought that this would be okay. The next thing right here says, thank you Teresa M for three contributions to TKG. If I refresh the page. It's a different thank you. Oh, okay, maybe we consider something like that but for me the attribution to the companies who are sponsoring us is much much more crucial. All right, next topic then I think we're settled on board and officer elections. Social media posting status report two weeks ago when we had our meeting. We discussed guidelines for social media posting and I think we can come be comfortable that there have been improvements in the last two weeks based on the guidance that was offered. The social media posts have been technically focused. And there have been several since we last gave that guidance. One of the challenges is the social media, the folks who work on the social media like Alyssa are not generally as connected to technical topics as the rest of us are. Please if you've got an interesting thing that you think might be useful to post to Jenkins social media. Please submit a proposal to for it to the advocacy and outreach getter channel. After a conversation with Alyssa she came back and suggested she and I came to the conclusion, maybe we should allow an occasional purely social post, but only as a small fraction of the total post think one in 10 or one in five. So that if we want to do something purely social we still could other board members. Do you have any comments or insights on that would it be okay to have an infrequent purely social post or no let's keep them entirely technically focused. Really I think you were the crew, the key one who suggested let's be technically focused anything you suggest. It's hard to decide when I don't know what the content is. So, I think it's for me or let's say it so it's fine for me if Alyssa is proposing it and we are gathering a lot of plus ones, then it's fine. So, yeah, it's hard now to say no, I don't want it and maybe it's really a good idea to have it. So we that's a good insight we may want more plus one votes on a social topic. Yeah, that's a good idea. And then on a then on a technical topic right because technical topics are much less likely to be controversial. Good. Okay. Others any insights there comments that you want to share. Okay, so I'll discuss it further with the with advocacy and outreach and bring back a summary of where we're at from that. Thank you. The next topic was on the Azure credits donation so we're very grateful to Microsoft, they've donated $40,000 to the continuous delivery foundation that's been credited to the Jenkins Azure account. And Damien has opened an infrastructure help desk ticket to show progress on consuming those donated credits. And the goal being that certainly by end of December 2023 will have started consuming those credits for our ephemeral workloads as he described to us one or two meetings ago. Thanks special thanks to Damien for what he's doing there. He's looking positive and promising, and it has not risked or altered the payment processes we use for our Azure account, nor has it had to alter or damage the permission system so big positive for having made infrastructure improvements without threatening the ongoing operation. Any questions on the Azure credits. Okay, last topic then is Oracle cloud cost donations. Still no progress. I, I think it's worth just removing this from the governance board list, because there's truly nothing we can do about it. I'm, I'm sort of done asking Oracle to take the action that's needed. When they next ask me mark when are you going to pay us these zero dollar invoices I will again refresh to them. You need to make them non zero dollars. Any concerns there if I just remove this one from the from the board list sounds good to me. Okay, great. Thank you. Any other topics before we close our meeting for today. I failed to turn on. I'm a little worried I may have failed to turn on. Well, I think you did because I got the notice when you started. Oh good. All right, thank you then I'll stop the recording now. Thanks everyone.