 Hello everyone. Welcome to the Jenkins governance board meeting. Today is December 2nd and we have a number of contributors on the call. Thanks everyone for joining. Today we have several topics in the agenda. We will briefly talk about recent news, about the election results and then we will focus on other topics if there is a forum for them. We have Jenkins 3x discussion. We have Jenkins 3 updates and also selecting new meeting slots because from what we've seen in the mailing piece, this slot isn't very convenient for all stakeholders. So we will need to find another one. And we will also have a panel with a port that is posited by Marke. Okay, so that's the agenda. So let's briefly go through the news and maybe one major news is Jenkins elections. Should we start from them or from others? Okay, so Jenkins elections. You will see that the elections are over. Thanks to everyone who participated. Yeah, it was a several months long process with a lot of different steps involved. But yeah, finally we finished it. We have already announced the results and what are the current results? And the final results that for Jenkins governance board, we have Marke who won the popular role according to Concordnet. Then it's Marke, Gavin, Evelina, Justin, Steven, Rick, Fred and Andre. So just I think I would like to say there that we've got nine awesome contributors and community members in the ballot. So thanks to everyone who participated. And yeah, these votes basically for me it was a really tough choice to prioritize the results. I guess the same for many others. And yeah, the final results that Marke and Gavin joined the governance board as discussed. Marke kind of joined because of the affiliation requirement. Unfortunately it happens second year in the role and maybe so we had some discussions before like expanding Jenkins governance board or maybe making additional adjustments. So it's to be seen how we approach that. But yeah, I would like to thank Marke for all the contributions he makes to the project and also to the community governance. But according to our process, we have Marke and Gavin joining the board. And that's Marke and that's Gavin. Would you like to say a few words? I can say something. First and foremost, I'm super humbled. I'm super thankful. This is a awesome project and I know there's been a lot of people that have done a lot of work here. And I'm kind of lost for words, which is a striking thing. I'm never lost for words. I want to thank those that voted. I also want to thank those that were nominated. There's a lot of people that I'm extremely close to and do a lot of work in this community. So I'm just thankful all around for everybody. Thank you very much. Yeah, I'm going to say something to the same thing. I'm a little bit in shock. I didn't expect it to happen. I'm kind of very touched that it did happen. And I'm excited to see what the future holds. So any additional comments and questions from others? Will you, as an elections committee member, what's your impression? Yeah, congratulations to everybody. It was really impressive again how many people voted. And yeah, I'm happy about that we have three new members or two new members. So yeah, because Mark again is not allowed to join. But maybe we can change that in later on if we have it in the next election that we have more people in the pond. I think it's great. Thanks, Markey. And thank you, Gavin, both of you. You're a great addition to the board. Looking forward to your contributions. Thanks very much. This is Tracy. Yeah, just going to say congratulations all around. Great additions to the board. Mark, you get to win it without actually having to join. I think that's a good too. And we've got a CDF newsletter going out. So I think we'll add a line in there just to mention that in the newsletter sounds like great news to share far and wide. I edit the results to the Jim's project update. Details. Yeah, no, if you've added that, I'll make sure Roxanne sees this. Thanks everyone for the feedback. And again, governance more is mostly a representative body. We have a lot more community leaders helping with different roles including all participants on this list and many other members. So, yeah, the Jenkins community is strong because we have a lot of participants in different roles, official or not. And it helps us to move forward. Okay, speaking of other roles, we also had elections for Jenkins release officer as it was announced in the developer list. Oliver Lonsa decided to step down starting from December. So we have just had Jenkins LCS release to do to 63.1. And this release was created by Oliver in terms of reporting. And it was the last release. I would like to thank Oliver for all his hard work on this position because Oliver was leading LCS process since 2013 or 2012. So it was long ago. And yeah, it's much appreciated. The same, yeah, if I go to say so for the Jenkins governance board. Alex Sirle helped one of the positions. Another one was helped by Tyler. So thanks to both of them because they have a lot of Jenkins community with establishing open governance in the project. Again, we are looking forward to work with them in the community. So for release officer results, unfortunately, we don't have team on the call. As I proposed in the mailing list, we will do another session, maybe next week is introductions, maybe even organized as an online meetup. So something to discuss. Again, for the release officer, we had three awesome contributors who helped his Jenkins team. He has been active contributor to the Jenkins core over the past two years. He created computational code plugin, also dark team. He helped his Jenkins infrastructure and many other areas. And it's well deserved. And thanks to team for taking this role because the LCS officer is important position in the Jenkins community because the new officer coordinates all the reporting process and it's the Jenkins release team. It's responsible for all the LCS releases. Welcome team. Also, you had Baptiste matters and Victor Martinez participating. Most of them also contributed to various areas of the Jenkins coming into the release processes automation and the Jenkins for maintenance. Thanks to them. And again, both of them are contributors. Let's keep working in the community. So, other updates. Lisa decided to step down from the event officer position. Mark, he will become an event officer. This position was that can wasn't contested. So we didn't have elections for that. But yeah, welcome Marky for this role as well. Thank you. Thank you very much. All this issues that's a big, big, big task. So I'm going to definitely do my best. I'm here to support you. So you're not alone. Thank you so much friend. Yeah, we have a whole advocacy and outreach seek. Ready to help these various aspects of Jenkins events and also outreach programs. marketing and others which are closely aligned with Jenkins events. It will be a nice experience and thanks a lot Marky for taking this role. Thank you for the opportunity. Okay, father also basically remains the same. So Daniel will remain a security officer, all of you will remain infrastructure officer Mark. Thank you for taking this role as documentation officer. Thanks for all the documentation changes in the past years, and I thought one officer. No, I didn't. So that's basically it concludes the elections. So the next steps is to firstly send an announcement and the developer may increase. I will do it tomorrow on the morning. And I also have a blog post. I target to publish it in 24 hours or so. But before that, I will send it for the view by others. So it might be slightly delayed. And in the worst case we might miss publishing tomorrow but official announcements will go to the developer. Any comments questions. So, obviously, we can always do better. Here's a retrospective document. This retrospective document is mostly empty at the moment. My suggestion is that we do it on synchronously. So, every contributor is welcome to speak and share feedback. And after that we process this feedback and think how we could make the next elections later. And these elections were the second ones in the Jenkins history. Last elections in the southern fight and having driven by Tracy, Olivia, Mark, and it was our first experience. They went quite well. We have a few retrospective items which have been addressed this year. And I think we should keep improving this process so that in the next elections, we can continue this public process and get more and more participants involved. And just to add, like, I got to step back and just enjoy it as someone voting this year and certainly from my perspective, it all seemed to go really smoothly and really well done and no one's counting votes for months to come. But yeah, no, I think it's really nice to see so many candidates and to see all the interest in the community that the elections bring. So yeah, congratulations all around. Thank you. Okay. I think your observations on points of feedback in the document are spot on are exactly correct. The registration numbers is an interesting one that I'm not sure how we address it, but I'm fascinated by it. Last year we had, we had, we must have sent what almost 100,000 email messages and and had a larger registration we did this year but this year we decided not the bomb, mail bomb people at the same way we did last year. So it was, it was, I was trying to look at the results last year, it was 150 votes last year and 50 this year. So last year, it was almost 300 votes this year was almost 70. So, yeah, if you want to see the numbers, you can just go here. So, yeah, the numbers are here. So, this is governance board elections 65 voters and 94 registered voters. So it's after processing for registrations, the petition clarification. The numbers are considerably lower than in previous year. As Mark said, it's mostly explained by the fact that we didn't send emails to every user. With respect to maybe we should have done that. But not sending emails was one of the top feedback from the previous year. So it was the delivery decision when we changed the process. So we've written this change and it's something to discuss going forward, because we also interested to get models. Yeah, other topics to consider is also a number of many, many nations, because we have got quite a lot of many nations but they came from not so many contributors. So it's the state of the previous years and it also affects the situation in other open source communities when elections actually are a bit popular. But you need to think how we could improve it. There could be more things. And also, of course, much administration other head, because there was a lot of preparation, a lot of bureaucracy on different stages. And maybe you need to think how to optimize it. So that takes less time to organize and drive the elections. I think one of one of my concerns initially was that the verification process might be heavyweight for the elections committee was the verification process painful or heavyweight for you. Did you find that difficult or taking a lot of time. The verification process was, so this year we had three members of the elections committee, but both members who are not up for elections was only Alex and me. And we need to verify around 100 responses, a bit more. But I wouldn't say that it was a bit of a head to do the verification. Because firstly, we were able to do it gradually. Once we discovered that in, since we can add voters, we expanded the registration time. So we were able to graduate voters. And verification was so trivial in many cases. There are no contributors, there's no emails. There are contributors who needed verification, but I would say that the level of spam just stations was low. So if you had 100,000 registrations for voting to this process won't work. But we can definitely scale maybe 10 times without massive overhead. Thank you. Thanks to the thanks to the elections committee for doing that was just curious. That part wasn't difficult. The most difficult part was actually just promoting elections, trying to get more registrations, etc. And if you had to beg how we could have done better, it would be much appreciated. This year, there were completely different things on minds of people. Also timing for the general elections wasn't perfect, taking events in other countries, but yeah, whatever. Anyway, I think that we can part of this topic. And again, thanks to everyone who participated, who voted, thanks to all the candidates. And it's great to have the elections over. I hope to release more contributors in roles. Now we can continue pushing the Jenkins project and evolving its roadmap and other critical initiatives we have was coming initiatives and technical initiatives. Are we able to say anything publicly or should we should we hold Personally, I don't have strong opinion because the results are public. What do you think? I would like to wait until the Jenkins IO post goes up. I mean, there's no reason not to say anything. I think it's nice to have Jenkins be the main source of information everyone else announcing afterwards. That's a good start point. Good call. So, yeah, let's start get publishing tomorrow. I'll do my best to submit it for you given several hours I have the blog post almost finished. So, and then on Friday we can start on Thursday and Friday we use all social media etc. Okay. Yeah, regarding other topics. Should we go back to news or should we continue to the agenda. And this, yeah, these topics. I'm not sure whether we have all the new people on the call to discuss. Let's return to news and then continue to the agenda. Okay. So other news. Outage two weeks ago. Mark, would you like to summarize? Sure. So we, we had a 40 hour outage. Two weeks ago during where the Azure file storage on which we depend was unavailable we couldn't mount it. We were working around by moving the service to another location we're still using that work around it's running just fine. We asked Microsoft to please do a root cause to explain to us why it failed, especially since roughly seven days after the failure it started working again, but we hadn't done anything that caused it to start working again. We called this morning about about six hours ago from Microsoft support in Europe, reporting that G didn't you do asking didn't you do something that fixed it. No, we really didn't. And they are now going to report back, trying to find the root cause from their side. So our plan there is to switch back to the to the original solution, either late this week or early next week, because it does seem to be running again and it lets us use Azure for Azure file storage in a very elegant and direct technique. So, any questions there, happy to answer them a retrospective is there. There are certainly many things we learned from instant about incident management and what to do with it to will keep working at it. Thanks to all contributors who are involved in fixing it. Status pages status pages status pages under development. And so it's not been publicly declared, but there is certainly is a status page that Olivier has been using as part of that. So should we not be linking to it and stuff yet or is it worth linking to something at all. I good question I don't know the answer. That's a that's a fair question. I suspect Olivier would would say that hey it's it's good enough but I considered still a work in progress. I guess that's my thinking is, if we have something we can link to that's good if it doesn't get updated it's already worse than before. Right. So, yeah, let's see what goes but we will need to document it. Right now we have direct links to data doc dashboards on our website. And this is the doc dashboards on this page anyway. So, again, thanks to everyone who was involved. It was quite an expected audience. But today's we were able to basically rebuild the functionality using another platform. Yeah, this is a functionality that serves hundreds of thousands of downloads every month. So it's not something. Scale matters mirrors matter and also, there is a lot of associated costs with it. So, with that you will be able to fix it quickly. LTS release. Yeah, we have one. Thanks to everyone who was involved. And I guess it's all worth in place now. So if you go to change the table you can see the release of the grid guidelines and everything looks pretty good. Yeah, this process runs well and it uses a new automation infrastructure. So, now we're doing LTS releases quite easy. So it is all for long work by the infrastructure and the teams. In the past year. For us. Another interesting topic that we will be doing winter break. According to our current process we should have created the release candidate. In late December, and you should have done the final release on 30th of December or something like that. We decided to postpone it by two weeks. The release will go out in January. Anything else about releases? A quick update on Google Summer of Code will happen. There are some changes in the process, but largely it remains the same in the previous years. We are looking for mentors, project ideas, so if everyone is interested, please join us using the standard channels and everything is in place. We will send official announcements to the developer planning team next week. But process wise everything is ready to accept new project ideas and interest students and we already had a dozen students or so. So, so asking about project ideas. Yeah, just southern 21 has that. Oh, like I have a question regards to that will we start up the org admin meetings again for planning purposes and things like that. How we used to do it in previous years, while we in the application phase in before we just do office hours, because there is nothing really secret in the process. Because you can discuss application, etc in public it's open source for project anyway. I think we could just do office hours in the time it is fine with you and we could revisit timing. If you want to find another slot. So, okay. Thank you. Historically we start the admin meetings one of the student application phase is over. Because this one we need to make decisions to review the petitions and to do other to other sensitive things which we just cannot be discussed in public. Any additional questions. Then. Yeah, just for your information, there is a discussion about Jenkins 3x discussion has been started by James North. Several days ago. Almost one week by now. There is a lot of feedback and clearly we have no consensus in the straight at the moment. But yeah, my call with it since now you have a new release officer board members and feedback from stakeholders to understand whether you want to plan for Jenkins 3, because it would involve many different actions required from the community and from the teams. And also the main question is whether you actually need to do that. Whether there is interest in the community to do that. And once we get the consensus, then we can start planning. For Jenkins 3 release, allegedly it was explained by the breaking changes we introduced into the tables to be which still needs to be stylized towards the next LCS release plugins which haven't been updated. This is an extremely extreme S&J security of the two spring security and jQuery updates plus a lot of other minor break in changes in there, mostly for deprecations. So, yeah, from technical standpoint it might be justified and we need to discuss it. So, that's just for your information. And if you have feedback, please put it in the mailing list. I don't think that we are ready to vote. Finally, everyone. We discussed this topic. In the end, it's the release officer that really gets to the side right or put every weight on it. So, I don't think that this officer decided there because it happens by the consensus in the community. But for this, the release officer has a safe and until we have this officer, I wouldn't make this decision. I don't think the consensus looks like it's three groups all saying same thing, but everything's and everything else. So, it's a little chaotic. Good discussion. Maybe we could spend some point on that. First, we need to decide until we start to release candidate for the next baseline, and it's late to January. We still have plenty of time. Okay. So, moving on. We have two iterators updates, just to be complete on the status. So the, your development in different areas. Now we have two iterators. One is called Jenkins iterator, which is the original one. And, you know, it's back to the active phase of the development as it was announced by the shop. So there is some development happening in this repository. Yeah, thanks a lot. And, yeah, we also have the second iterator. As it was requested by the red hearts team, they basically is devoted to having a separate port in upstream. So, currently called simple, simple Jenkins iterator, this name is subject for change. And there is spending discussion about what is actually inside. But as we discussed at previous governance meetings, we basically have two operators. And for my understanding, these iterators have different roadmaps. So I'm not sure whether they evolve, but yeah, that's the current situation. On the same topic. There is also a sub license request, because the shop has launched a commercial product based on the original Jenkins iterator. They haven't launched yet. They just announced private preview. So it's not the face of white announcements. And that is pending. Mark sub license request. You need to define what would be the best thing. So as we agree to the previous meetings, we have a trademark usage policy. We have strongly comments using links foundation to mark guidance. But the rest of the team to develop other meaning pattern. The community goals for that. So that's the current state. We don't have the first of his entities at the call. So I'm not sure what we can proceed right now. So if anyone has strong opinions about names, maybe we should discuss that so that we can communicate it back to the request. I still personally have a lot of questions, not so much around the name but more around what, what took place between red hat needing to create a second operator. But I know there's history behind that so I may just take it offline and Yeah, there is a history. Some bits of this history are in public. Also, yes, thank you governance for participating in communications between parties. Potential solution. Yeah, so there is also private conversation part. Not that much of the private part on this stage. This is my understanding that the current name. So basically it's, it follows the historical pattern of union, which we had before we agreed to follow links foundation guidance as our main preference. In the mailing list I proposed the greater service for Jenkins. So as long as there is such a distinction. It falls into the category of pre-approved landmarks and links foundation. Well, premium patterns which are considered to be a failure. So, yeah, personally I would wait for response whether it would be feasible. If yes, then I think we are fine. If not, we will likely need to vote on this name. I'm not sure about. Are you ready to vote now. I personally am not ready to vote. We should wait for the answer. Okay. So then let's wait. Yeah, taken. If this partner is taken, we won't need to wait until the next meeting. Okay. So, next topic is selecting new governance meetings. I suggest that we just start a new doodle. Because we have more contributors joining. And yet this slot has been considered as complicated before, especially for Europe. So we can try to find another slot, maybe even on another day and see whether you can find something. I will start the doodle maybe tomorrow. And then we will close the discussion about whether you want to keep the slots only in the current time zone because technically it would be great to have a coverage for Asian and Pacific region. Somehow, so we could start with taking slots. It's a complicated topic again and see whether there will be contributors. Any comments proposals regarding the slots or the meeting guidance or whatever related to the governance meetings. I personally like this time slot, but I don't think it's good for anyone else. I can be flexible. So, again, we are not making decision now. Kevin and Markey, you are both in the US time zone. I'm in Pacific and Canada. Yeah, Pacific as well. So we can do the other side really early European is good too. Yeah, something we could do. So, yeah, let's see. Okay. I understand that the developer mine is but I will see all the usual suspects, so that the computer some by CDF annual report. Mark, would you like to speak about it. I put this on here. Mark attended the meeting thank you for attending the meeting mark. I'm going to do, I believe, by January 13. Don't quote me on that. Yeah. We need to have the report ready. I'm trying to find the actual information. Yeah, I'm sure. Yeah, January 13. Yeah, so when we pull in the data, I can help. Anybody wants to tag team on it to get that report ready Mark did you have anything you wanted to add from attending the meeting. The CDF meeting today. No, they'll review it with Tracy mid December. And it looks like the format will be largely like it was in 2019 the format as far as I could see looks like a good fit for our need to communicate our message. In 2019 we basically created our own a new year blog post and based on that, we continue to deliver the foundation refactor to its summary blog post by optimizing for the content and bit. There are more projects to present. Maybe this time we could do the same. So firstly, do our blog post, which quite longer maybe we could even publish before the new year. And after that, we could just work this is the up to the fact that this information to the summer. It feels like I can take that task. But I don't want to take it from anyone that may want it. Oh, we can collaborate. But if you want to drive this effort. Yes, please feel free to go ahead. Got it. We can even write it in Google Doc if it's a, if it's preferable for collaboration or we could do this food request is changed suggestions is how we try to do it last year. Yeah, I'll think I'll do I remember it from last year and I think what I'll do is just start start off with the Google Doc and then we can move it into a PR. Once we're all in agree instead it's ready. That's fine. Okay. Thanks for today. I was just thinking you sent an email to me directly about getting her to work as results. Did you get a result back from it. No. So, I didn't expect to get them soon because from what it is covered the October first main blog post and main steps report is not ready yet. So, the October first team is focusing on getting their own results out of the door and after that, they may be able to help provide it for us. For example, it continues to deliver the foundation has already posted a blog post to be used to be about October first. We shared some details and statistics, which was collected from the public resources. But yeah, that's a problem with October first because we cannot identify all contributors with the current process. We should be able to now, because it has to be labeled repo or labeled issue. Yeah, right. But how do you determine who can just label repo and sense. I assume I always I would always there on anything in the month of October is considered October first. Yeah, this is one of the options. Okay, when I was sending data to continue to the foundation I just took a blog post. Sorry, for request, which I mean, it's with market market is hard to be accepted the label. We had something like 100 something for requests and 37 unique contributors. Yeah, these numbers basically, they believe come from the Jenkins project for some agreement for competitors, which we identified for other organizations. It would be awesome if we publish on some of the blog post later. Why not. Yeah, right now, we just have partial data. This part of the data is also enough because we have a few developments. Yeah, so I think we need to keep working on that. Yeah, really, if you can just put it to the panel report any other topics. Yeah, we'll start to do the whole board members officers and other contributors for the next week to see whether you could find another slot for the announcements. I will send another do the work to schedule the next governance meeting. Sounds good. Thanks so much. Thanks. Thanks. Oh, Jenkins project. Thank you everybody. Have a great rest of the week. Thank you everybody.