 Hello. Welcome to the Jenkins Governance Meeting. Today is October 21st and finally we are back to the common schedule of governance meetings. So starting from this week, we will be having meetings every two weeks and it will be signed with the LTS process. So today we have several items in our agenda. We will talk about recent news, about the election status, updating officer definitions, also marked at the topic about epiphany video and at least I wanted to discuss Jenkins Comics straight. Is there anything else we need to discuss today? Okay, then let's continue. So the first news, October 1st. So big news that only 10 days left. So if you haven't participated in October 1st yet, please consider doing so. We still have a lot of newcomer friendly issues. We also have documentation and number of featured projects. Several of them have been edited during October 1st. And if you're interested, you're welcome to contribute to any of them. And you can find more information on this page. Also, yesterday we had a new weekly release. So this one, right? So it's 2.263 and hopefully this release stabilized the infrastructure, actually, because before that we had several releases and all these back coming ratings due to regressions. But now it's finally stabilized and it's actually a good thing because we have just started LCS baseline selection. So we are discussing what will be the next LCS baseline after 2.249. And if you have any feedback, please participate in this thread and a bit of it. Other folks will help you discuss. Okay. Going back to weekly release outage, Mark, would you like to share something? Sure. So we made a mistake yesterday. The mistake was an interesting one and complicated. We're still investigating why what happened was Jenkins 2.263 weekly was built successfully. So it's released to the Artifactory was worked okay. The packaging process, however, did not complete. Part of the packaging process blocked on a windows container problem. We have any infrastructure that needs work. However, it had been published to all Jenkins users of weekly as being available in weekly. So they attempted to download it and their attempt to download failed because it was not yet visible to them. Olivia is going to publish some comments notes on the retrospective from that. And we will work to improve it so that we get better at doing those weekly releases. This is the first time we've had a weekly release hiccup like this. Since we started doing core release automation, our apologies, we'll work on it and get better in the future. Weekly release was not a big problem. Well, it's just running release and the war files have been available immediately. So I didn't even notice that there is an issue. Well, and the Docker images were available shortly after the after the war files. The gap was in the Debian package, the Red Hat package, the Susie package, and the Windows and MSI installer. Okay, yeah. So the release is ready for evaluation and any feedback will be appreciated. Okay. Yeah, more about releases. So Oliver has made an announcement in the developer pilot list about stepping down from the release officer role. So first of all, thanks to Oliver for his contributions. Oliver has been leading the release team. Well, even before there was a release team. So for eight years, since the beginning of Jenkins and the modern release automation after the Hudson infrastructure was redeployed. Now in the release team, you don't need to work together in order to reestablish this kind of a testing flow and also as a part of the elections, there is a number of limitations for the release officer position. So they definitely will be election in November. We invite all contributors to participate and to help the new release officer to pick up the role. But hopefully this other release team, etc, will basically be business as usual for Jenkins users. I do not anticipate that there will be major changes in how we deliver Jenkins. Any comments, additions? I would like to thank Alyssa for all of the amazing things she has done for this community. And it just, it's just super amazing. And I thank you also to Olivia. Thank you as well for the amazing work that both of you have done. Thanks, Markey. I'm still around, not going anywhere. I'll still be here to help out. That makes me happy. A rotation of officers and board members is actually a sign of a healthy community. And it's natural to expect that officers living in these roles can take vacations, can take breaks. And yeah, I think that everything happens quite smoothly. Okay. From the community perspective, just a big thanks to you, to Oliver and also to Alex, steps down from the board's role. But yeah, I believe that we are in a good state to just continue the effort and ensure that there will be some transitions of all these roles. And I totally forgot Alex and I do apologize. That was not intentional. Thank you for everything that you have done, Alex. You are a totally invaluable member of this community. Thank you very, very much. Plus one for me. Thanks, Alex. Thanks. I'll still be around a little bit too. So you all can read me that easily. So put away your shovels, everybody. Okay. So yeah, let's keep working. And again, elections. Yeah, basically, just switch to other topics. So yeah, elections on. There are some shifts in date. So as it was announced, we will delay publishing copies of candidates to 26 or maybe one or two days later. Basically, it doesn't change anything significant in our process because the voting begins only on November 10. So the intention was to publish the candidates a bit earlier so that participants can see all the candidates. But the date of 22nd has no significant importance in terms of the process. These dates are quite hard. We'll adjust. So we've got quite a number of nominations. Right now, the elections committee works with candidates in order to get affirmations, get statements, and then we will be preparing a final announcement. Most likely this time it will be on Jenkins.io or maybe in Google Doc like on previous year. Yeah, this is coming soon. And yeah, the deadline for nominations is over. So if you want to nominate someone, it's probably too late. Well, the governance board deserves its right to add additional candidates. But yeah, from what I can tell, there is no strict need to do that right now. We've got quite a number of nominations, thanks to everyone who reached out to the board. Yeah, right now it's rather processing. And yeah, the separate part of the process is actually about voting because I can say for sure that even on this call, not everybody has registered for voting. And yeah, if you haven't registered yet, if you want to participate in the elections, the deadline is November 2nd. So we can ask participants to sign up. We will be doing some additional steps as discussed at the last meeting to increase number of registrations and to outreach to plug-in maintainers and other contributors. Because yeah, right now we've got registrations, but you would like to have more voters because we know for sure that there are thousands of contributors eligible to participate in the voting. Basically, if you need any contribution, whether it's got or not until we sign up, you're eligible. But yeah, a number of registrations definitely doesn't represent this number. It's common for other communities, but we still want to have more. Any questions or additions? Is there a way for me to decode if I have registered or not? I assume there is not, so the safest is send another registration and you'll just reject it if it's already been submitted. If you do the form, it will tell you you've already you've already filled out the form. Yeah, good. So yeah, this is specifically the reason why we use Google Form and we enable mail tracking because this is our way to ensure that the form is submitted on the once. Well, there are still opportunities to submit it to multiple times from different accounts, but in the form we explicitly ask you to confirm that you will be voting on the once and we will be doing additional scrap of voters before we send out ballots. So you can just log in and vote. Thanks, Alex. Oh, like just a question. Thank you, Alex. Just a question. I am just testing the voter form. I'm doing it through Safari and Chrome. And when I click on the link, it is giving me an error, Firebase hosting proxy page link error. No idea. Okay. So if you could report it to Jengist 720 elections, we could take a look at that. Okay, thank you. But yeah, I tested in a few browsers, et cetera, and I haven't seen any problems. Thank you very much. Okay. So yeah, I just tested. That's why I stopped screen sharing for a few seconds. Okay, still, if you're not comfortable with the mail tracking, you can have an option to just send email to the Jengist 720 elections at Google Groups and basically the process is the same. You just handle it in a normal way. Okay. That's all about elections. Anything else? Then updating officer role definitions. This is a follow-up to the previous meeting. So the previous meeting I did just in time for request a few minutes before the meeting happened and we didn't vote on accepting the change. But now I think that actually the change is ready to be considered for integration. And I wonder whether other participants had a chance to review it? Still did not. I will do tonight. Thank you. Okay. Then a process question. Do we need formal governance meeting approval to nurture the changes? Or is it fine that we have a ratio consensus and the full request? Just right now, Olivia confirmed, Mark confirmed. We discussed changes. It is Alisa. So I guess Alisa is also fine with changes for event officer. Yeah, I am. So assuming that we get confirmation from Daniel, Oliver's role didn't change too much. I mean, it almost didn't change. It's yet to be defined later when we work on the list and we did test and et cetera. So if Daniel and Berta prove, I think that we could go forward with NERSH. Mark, you're muted. On the assumption that Alex will, that Alex's concerns that caused him to request changes have been addressed. I believe it was something minor for me making a mistake. Actually, it's a small tweak, which was. Yeah. So then I think full request approval should be considered sufficient. And you're taking the announcement from Oliver. I do not anticipate response in the full request. I forwarded this a while ago. So anything else with regards to role updates? So one topic which might make sense to discuss. I will follow up with Daniel because there are some questions about it. It's about onboarding of contributors. So right now what I've done, I introduced a new section for general responsibilities. And there is a mentorship and now sharing within the team to ensure a healthy officer rotation in the project with what you need for team leads to move on to other roles or take a break. So when we were discussing 2020 election, the perspective where there was feedback, I guess from Marky that you should rather have a shadow officers. I felt short of proposing to explicitly, though I added this text. And my question to you, Mark, is whether it works for you or whether you would prefer something more explicit? Was this for Mark or Marky? Marky. This looks good. We can probably keep it to this. And again, this document can be modified later. So I just felt it's important to update it before the elections. No, this looks very good. Let's keep it to this. Thank you. Okay. I'll put some notes later. Should we move on to the previous video? Mark, would you please tell us some rights on the topic or Alisa? I think I can. Alyssa will certainly correct me if I make a mistake. Fair enough, Alyssa. Sounds good. Okay. So in the July 30th governance meeting, we reviewed a proposal for a draft of a video to highlight Jenkins and how Jenkins is used in sort of a fun cartoon kind of way. That video is now ready. The Ready for Publishing link there is a link to that video. It had been discussed also in advocacy and outreach. And what we think we would like to do is place this on the Jenkins.io page, placing it below the jumbotron but above the blog post. It will probably require some changes to the handle to allow us to embed this. It would be actually hosted on YouTube but displayed here that placing it in that location where it's on screen now is all like showing it means it will be tend to be below the fold for the typical reader of this page but still trying to get it as visible to them as we can without disrupting the top level page for the jumbotron. So you're saying it will go below the jumbotron? Right. So my thought was it's either above the six sort of blue dots or just below them and above the calendar. So it would be above recent blog posts in the section that's visible on the screen now. I didn't want to put it right front and center because I think the simple elegant layout of the topmost section of this page is exactly the right thing and I don't want to displace the jumbotron. Yeah, no I totally agree. I think that's that's more than sufficient if we can just get it like below the jumbotron or above the calendar in that area anywhere it would be perfect. Do you plan on the video also some content in addition to the video? Yeah. I had not planned on anything more than the video. It's a good question though. Should we consider a blog post or something too? Because Alyssa's submitted one blog post already and we've got another one pending. We've got a blog post that just arrived for Jenkins is the Way and we could consider highlighting one or more other Jenkins is the Way topics as part of a blog post to introduce that video. No reason we couldn't put it in two locations, right? We can embed it in multiple places. We could put it top of a blog post as well. Yeah, we can do both. That's fine. I was speaking of that automation on Jenkins is broken because the GitHub app is no longer operational. Oh, that's why the automatic labeling isn't magically appearing. Yeah, I filed an issue a few days ago. So basically, GitHub changed the APIs and the app is no longer operational. And if I ever get to that, I would rather move to GitHub Action or somebody else could contribute. Yeah, there is no need to keep an app for this particular use case. Great. Okay. But yeah, so just for other copy editors, basically automation is not fully functional. And it also impacts, for example, governance docs, because right now we don't have governance label here, automatically injected. So our documentation for copy editors, please do not touch your governance documents also is half functional. Right. So it's not a big deal. But what issue was that again, Oleg? Well, GitHub app we were using for automatic labeling is broken. Okay, 3872. Yeah. Yeah. Well, basically, you can just take something from the marketplace, move configuration file to the new format and everything will start working. And this format is actually quite close to what we use now. So well, it's not a big deal to fix it. If somebody wants to work on it. Okay. And we have just we have merged to one block post right merged one yesterday still have have more to more to review. Yes. Okay. So there's I have one blog post that talks about the Jenkins awards winner. Are we okay? Am I is there something else that I need to do on that one? I need to actually I need to update the date of that one. And I want to do a review of it before we post, Alyssa. Okay. Yeah. All right. Thank you, Mark. I'm still not 100% comfortable about the text. Because I wanted to make it explicit that it's basically not a Jenkins official award. It's a lot of this award. We still appreciate that it happens. Yeah. But yeah, I just wanted to make it explicit here so that there is no confusion. So do you want me to go back in and change the content a little bit more to make it clear? I approved the previous change because right now it's for sponsorship. Maybe we could shift it a bit more. Okay. Well, so in principle this award was with advocacy and outreach seek. At least with some members. I don't recall what was the process. I guess everyone was invited. But yeah. So maybe it's something for you, Mark, if you have a better word in mind as a native speaker, just put it. Yeah. That's what I was thinking, Oleg, is I'm going to go do a review and I'll negotiate and discuss with Alyssa and we'll get this move this along. I like the concept and I think your concern is worth considering and we see if we can find some minor phrasing changes. Alyssa and I will pair up on it. Okay. You're right. But anyway, thanks Alyssa for doing that because you're promoting COVID-19 prevention. Yeah. And yeah, also maybe somebody can look at open graph. Social media cover is a good thing. Okay. So anything else on the epiphany video? I actually would, if the board is okay with it, I'd like to ask for a vote to say for approval on that. Has there been enough conversation about it to ask for a vote, Oleg, or do I need to wait for another meeting? Does everyone have enough information to vote? Yeah, I think we can vote. Yeah. This topic has been around since August that guess there's a few iterations. So I think I have never heard any specific minus one about publishing the video. There were some changes noticed and may talk to you in the video. So I think it's very fine. Okay. So who's plus one? It's on the market. Non-binding plus one. Okay. Plus actually everything is binding because everyone has equal vote. Okay. So yeah, that's it. So it's approved. Thank you. I'll submit the poll request. Thank you, Mark. Okay. So the next thing is about coming straight. Yeah. So we have had two Jenkins comic strip released well since it began the year until now. So we're working on our third one and trying to figure out if the team has any suggestions for a topic. If we don't, we were thinking that right now a topic is working from home. So we can use that if there's no other suggestion. But I like to get suggestions from the team if possible. Even not the third comic strip. I believe they will be more later. So any suggestions? So it would be I like the working from home idea. Okay. I think that'll resonate with a lot of people, especially since everyone is doing it now. Right. Working from the office. So thinking of other possible. I love working from home. Are there any sort of hot buttons in the current industry that might be worth considering as another? I'm all for working from home. But Hectoberfest has been one. Are there other things like that that we might that might be fun or enjoyable? Yeah, Hectoberfest is a bit too late. Same for DeWops, Waltz, Siddiq, right? Right. So the next major event we have on the list is Fosdom. Fosdom is on the January, February. Okay. So doing Fosdom from home was also quite an experience. Fosdom is true. Right. That's true. Working from home and recording your conference talks from home with like all your kids jumping around and the dogs and cackling crazy. I can see something really funny there. Okay. And doing the keynote in your in the garage, the basement or out in the street, right? Yeah. And I tried to do that street thing. That was not an easy thing to do. So he made that work really, really good. Well, he got lucky because he had somebody else that was recording him. But I did hear that there were some times where he almost got ran over. So Oh, my goodness. Yeah. Yeah. And I don't know if you guys saw a, I don't know if this was part of the keynote, but there was a guy that was doing his keynote in his garage. And it looks like a wood working garage. So there's like lots of boards and wood in the background. And that was really interesting. Okay. So, so we'll, we'll, we'll make it a go. We'll try to get something together for the first draft and then I'll share when we'll use the work from home idea. Well, we have Jenkins selections. Probably it could be a topic if it could be done quickly. Yeah. Say that again. Oh, like, I'm sorry. There's Jenkins elections. Uh huh. So I'm not sure whether it could constitute a good commerce trip. But there is a chance that it promotes registrations. Why not? No. Yeah. Don't be feasible. It should be published, let's see, by November 10th. Yeah. Maybe even earlier because it really makes sense to do it before the vote of registrations. Right. Yeah. That feels, I'd be really amazed if they could hit that kind of a schedule. That would be truly impressive. So, so we would want the, the, so if we go with the Jenkins selection topic, then we would want the, the comic to be out by November 10th. Am I understanding right? Well, in principle, yes. So it could be after December 3rd. So when the results are announced. Okay. So it's rather what you want to promote. Well, elections is still probably not that public topic in terms of, yeah, this is a community matter. It doesn't, well, if you're not worried about a community, you're just a user. Probably it's not too relevant. Okay. Yeah. I think, I think work from home is much more likely to resonate with the audience than, than something funny about administering the Jenkins project. Yeah. And I think the work from home would last longer in terms of it's, what is that word? Yeah. Yeah. The resonating it will last longer versus I think you'll be dated. It would do with the selection. Yeah. Working from home is definitely something we should do. Okay. Yeah. I agree. And it's unfortunate that I think that you're right. It said that I think that COVID-19 is going to keep even people who are working from, yeah, yes. Also, the current political climate, I think if we put that elections in a joking, you know, sort of white, it may be taken the wrong way by somebody, even though we all here know that that would not be right. But somebody could be like, what are you making jokes about elections for in a comic? This is not a laughing. I can just see that happening. Good advice. Yeah. Okay. I like that idea though. Yeah. Maybe we can make a joke of it out of it like subtly, like a poster on the wall. Yeah. Or like a one in the comic, one of the screens on somebody's, you know, CRT in the background has, you know, something about the Jenkins elections on there. Yeah. That's a great idea, Alyssa. Okay. Cool. Cool. Good. Thank you so much. Okay. So I'm a screen sharing. No. No. Okay. So anything else on the comic strip? Maybe it makes sense to send another message to the developer mailing list to pink people. Maybe somebody will come up with more ideas. Okay. Yeah. There are a few items on the roadmap which could constitute, I think, to announce. But yeah, it's something to discuss with our main cameras, some of the pipelines. Yeah. Well, definitely a lot to joke about there. But yeah. Maybe for a mailing list. Okay. Anything else? Nothing for me. Okay. Yeah. And then just quick update about the trademark pages. So thanks to mark trademark pages have been moved to the Jenkins IO website. So basically this is action item which we had this in May or so. Now the wiki pages we had they actually represented on Jenkins IO. Basically this content which has been moved from wiki. Now it's patchable but needs some revision. And also we need to update the trademark usage page because there is a backlog including the recent request. Yeah. At least now we have everything called Jenkins IO. So thanks Mark. Okay. And yeah later we should actually check what else is left on wiki. But yeah I've seen that almost all governance talks have been already moved to the JAPS or to the website. So maybe we will be able to just shut down the entire section by redirects. Now only one thing was we had approved I believe two trademark usages that are not on the new page. Are you okay if I take the action to propose those and then you'll see them as part of the governance review process? Yeah that's fine. Or you can just use me because I have another action item because last spring Kajinka's rule was approved. And it's asking it to appear today. Okay. So I'll leave that to you then. That's great. If you already were going to make another change wonderful. Yeah. So well actually I wanted to I had an action item you want to move this data. Thanks Tomar. He was able to do it first. Okay. Yeah. So if somebody wants to approve more trademarks, last the last meeting we have reached consensus that we wanted to proceed with adopting the limits of trademark usage policies. It means that a number of patterns basically become almost pre-approved. So until we formally vote on the process there is no pre-approved trademarks. But from what I understand, even in the current state, if you follow the Linux Foundation trademark usage policies, for example these patterns, the trademark usage probably basically is rubber stomping. Yeah. Once we have this policy officially adopted, then we can even say that it's automatic. Well there is no particular reason to build the process around that. Any comments, questions on trademarks? Okay. Yeah. So basically just here. And your next meeting. So it will happen according to the usual schedule. So it's November something. Right. I can check what is calendar day. But yeah. November 4th. 4th. Okay. And it's 6 p.m. UTC. So for those who haven't yet had a wintertime change. Yeah. The time may change, but at the meeting point it's in UTC. Anything else to discuss today? I assume LTS baseline selection will continue to happen by email under Oliver Gancho's guidance as the release officer, right? So. Unless communicated otherwise, yes. So if Oliver decides to step down early, I believe it's totally possible. And I believe that the release team can handle the process so that Oliver can focus on other things, which is totally understandable. But yeah, until it's communicated or decided basically business as usual. And yes, the most important thing right now is wish consensus. Currently, that it's 2.258, which is quite old and 63 is both assumption that nothing explodes. Right now, community ratings are quite good. I'm going to switch my testing cluster to 2.263 today or tomorrow so that yeah, I want to be able to give feedback there as well. Thanks. I switched yesterday. So for my home setups, everything works fine on those Linux and Windows. I also changed my, sorry, my Jenkins FedRunner test setup. They are not everything is smooth. But yeah, as far as I can tell, it's a problem on the Jenkins FedRunner side, not on the Jenkins Core side. So it's not something which would nearly justify going with all the version. I haven't tested on 58. So if anyone is using Jenkins or can deploy, provide feedback, or at least vote for selection, please do so. I guess we won't have a final conclusion today, but sometime this week after that, we will still have almost six weeks to stabilize the release experience and issues. Anything else? Nope. Nope. Then thanks everyone. And yes, this is the first time in a couple of months when we finish on time. Thank you, Oleg. Bye, everybody. Thank you, everybody. See you in two weeks. See you in two weeks.