 Hello, welcome to the regular Genghis Governance Meeting today in September 30th. Actually, we slightly moved the meeting in order to make it happen in the middle between DevOps World and CDCon. And today we have a few topics for the agenda. So we will talk about the recent news, then we will discuss and then go on the collection process. And we'll talk about updating officer role definitions and mark as an update for JFrog artifact reconstructions. Is there anything else we need to put on the agenda? Okay, then let's continue. Okay, one of major updates regarding Genghis Governance. Today, last week we have announced Genghis Board of Officers elections in 2020. So these are the second elections to be held by the Genghis project. We had elections last year, we elected three board members and five officers. And this year we are running elections again and we made some changes in the process as we discussed in the previous meetings. So key days for the election, October 15th is a deadline for board of officers minimizations. There is some documentation in the announced one. So you can see how to eliminate them. And on November 2nd, voting registration will be over. So if you're interested to participate in Genghis elections, there are two action items. We just registered for the election by submitting the Google form or by sending the mail to our mailing list and then we need contributors for all roles. In this year, we elect all officers. So it's five officers at the moment, security events, release infrastructure and documentation. I don't think that we will be introducing any more officers taking the timeline for the elections. And we will also be elected to governance both of us. So the election itself will happen in Alemba. We still have quite a lot of time, but maybe we need to facilitate a bit last week to prepare everything. Any comments, questions about the elections? And let's move on with other news. October 1st. Sorry. I'll like back to elections. Do you have any or is it is the board comfortable sharing any status in terms of number of people who have already registered, etc. Or is that not not acceptable to share yet. Well, it's acceptable, I think. So, yeah. It's okay to share the nation starts because it's ongoing for the rest of the nation's discussion. So, for voting, we have a few dozens of voters who signed up. So much less than in previous years at the moment, one of the obvious reasons is because we don't do muscle mail distribution. We don't have elections referenced on the jambotron on the events page. No, on the calendar. And, yeah, well, let's give it some time. And if there is not enough registrations in the next week, so then we will definitely need to think how we facilitate participation. Last year we had more than 300 voters, but again, we reached out to the entire database in java. Right there we we we risked almost 100,000 email messages right to get those 300 voters. Yep. Well, it's common for other organizations. So not so many contributors and users actually participate in elections. Thank you. So we are not an exception there. But still, it's our best interest to actually get more community members voting. Okay. So, it starts on October 1st, anyway, on the earth. So, effectively, it means that it has already started. If you're interested to start contributing, it's a good opportunity. This is this month's long event. Basically, you can submit a full request anyway on GitHub to public repositories. And if you submit full requests, you can get some Schwark and cool t-shirts. So Jenkins project also participates in the October 1st. We have a number of featured projects prepared, for example, a website. We have a blogging site, Jenkins core, Jenkins file runner, terminology cleanup, artwork, and hopefully we'll have more featured projects submitted by contributors soon. For each project we have contributing guidelines, good first issues, and even if you're not familiar with Jenkins, you're welcome to participate. Yep. Just submit the purchase over the months. And if you need any assistance, we have an educated Gitter chat for that. So, any contributions, you'll be welcome. Okay. Any comments, questions? Yeah. So, back to governance. So, Alex made an announcement about his governance position in the main list. So, Alex, would you like to summarize it? Yeah, I just, I have a new role at work that is going to take significantly more time. So, I've decided to step down from the board after this year. So when the next board term starts, I will just be stepping down. So we'll be electing two individuals to the board this year. I'd like to say thank you for everything that you've done for this community. I'll still be around. I just, I feel like I just won't have the time to fulfill this role, but I'll still be around helping. That's good news because we need you around. Thanks. Yeah, thanks Alex. Yes, Alex, it basically makes two both members to be elected this year. It was one of the major concerns last year when we made the decision to elect three instead of two. It balances the process a bit. Again, if you want to nominate someone please send nominations. Yeah, thanks again to Alex for all contributions to the governance and to others of the Jinx community. Okay, so anything else before we move on? Okay, so the next update is CDCon, so it will be October 8th and 9th, 7 and 8th, right? Yeah, that's correct. 7 and 8. Lisa, would you like to summarize the conference? The CDCon? Yes. I'm online if you want me to. Good, that'd be perfect. Thank you. Jumped in and started lurking. Everybody, good to see you all again. Yeah, so CDCon is coming up next week. And we've kind of made a bunch of changes just based on community feedback. So just the first thing to know is, oh, look at me on the video. Anyway, we are, we got rid of the donation as a blocker, so it's now optional so people can register for free, especially if that's a barrier to them signing up. We are starting the sessions earlier in the day to accommodate our European audience and most exciting, we try to factor in some more interactive sessions, so we will be having birds of a feather sessions. And particularly there's a Jenkins one, which is, if you click on the pink box sessions, I think that shows it. Yeah, I did it. And that is on Thursday, kind of early on. So what we're looking for that is if folks can be on hand in that session to welcome community members, even create a shared doc, we can add that to the agenda so people see it and they show up, they can either join in chat or they can join on video. So that's, yeah, I think that we've seen a lot of registrations come in in the last while I think we're up to about 550 now aiming for 1000 so we're on course for that, which, which is pretty good we're looking forward to the first kind of virtual CD con that brings the community together. So I encourage folks to register if you haven't already signed up to help us out with the boss, just promote the event and encourage folks to come along, and yeah I think we'll be adding in some kind of fun stuff as well but to be announced. Any questions. Great, we'll see you there next week. Any actions needed from the Chinese community and focus and outreach seek the current state materials, whatever. Yeah, no I think it's pretty good. Thanks so much for getting it on the banner, and I think maybe just a couple of tweets or LinkedIn to mine folks. It's coming up and that will be. Yeah. Maybe the buff on the calendar I don't know if anybody reached out about that. But just for saying look is a chance to kind of come into a way to meet the community members in a newcomer friendly way. I think that will be nice. Okay. Definitely we could do that. Great. Thanks very much. Okay. Thank you. Any other news. I have some CDF news. Well some updates, I guess just one thing is, if I need chased up the payments for Google season of dark so we should be able to manage that at CDF, and for you the details from from the finance folks so we can get that taken care of. We can go to that in first two parts. So the first part will be managed the payments and then once we've got the payment we can set it up in in the community bridge platform. And the other thing I think I shared this at the talk meeting, but there is going to be a new training course from the Linux Foundation training team on Jenkins essentials and I believe that's going to be launched on October 6. It's the folks from up lemur who have written that so it kind of, I think there's a free edX course. I think this will be a paid for Jenkins beginner course that's being announced yet next week. And I think other than this folks will do a press release about that. That's all I can think of from CDF, but yeah if there's any questions or outstanding issues happy to take those. Any major that's there. And the rest we can discuss CDCon. Yep. Okay, great. Just let me know if anything I can help. Thank you. So one related topic is, we still at some point we will need to recover the Jenkins area in the top discussion, because we had an intention to recover meetups, then the COVID happened. This topic got frozen, but I think that at some point we need to discuss what we do is still meetups, and whether there is any feasibility to recover them in the current environment. Yeah. No, I think after CDCon we should have some more bandwidth to relook at that and we can get Jackie involved as well. Thank you. Any other news? If not, we can go forward with other items in the agenda. Yeah, I think that's all from my side. Thank you. Okay, so yeah for Jenkins support and officer elections. Everything is going pretty good at the moment. So we'll be announced the elections on time. Same for voting sign up, both processes are working. So we've got a number of nominations, we've got a number of registrations for elections. And the next deadline for us is October 15th. So for 15th, we target officer and working nominations. We've got quite a number of them. It would be great to have more. So if you have somebody in mind, please send an email to the Jenkins government board as documented on the page. Yeah, I think that it should be. Okay, so for 20 seconds we have all, we should have all the nominations, these personal statements published. So right now it's basically a seven period where we try to facilitate the registrations, but there is no video lines at the moment. Okay. Any questions, concerns about the elections? Okay. For officers who are present on the call, I sent individual emails to every officer just to check your interest to continue in this role in the next term. So if you do not want to continue, please reply to this email so that the Jenkins board can act on that and prepare. Again, it really depends on nominations, because if there is more than one nominations, they will be election anyway. But like we had last year, in a few cases when an officer was willing to continue in the role and there was no other nominations than basically just proceeded as it's documented now. Okay. Moving on. Okay, updating officer definitions. Actually, it's an action item which I had last spring, but you haven't delivered on that at the time. So there were some concerns about definitions for officers, because some definitions were dated. For example, for event officer, we still have documentation for Jenkins area meetups. We transitioned it to continuous delivery foundation. We discussed about how we actually update the definitions so that these requirements represent actual expectations from officers and actual needs in these domains. I would like to follow up on that so that we can have the definitions updated before the end of the nation's phase, October 15. But yeah, this update isn't ready for voting. I haven't started the developer mailing list yet. Still, it would be great to get your feedback. So there is a pull request 2943. I wanted to have changed in this pull request. So for all roles, I did something like facilitate projects within the domain. Again, the wording is something we can discuss. But the main idea is that officers, while they're expected to actually facilitate and empower initiatives in their domain, and also to get the key initiatives represented on the public Jenkins roadmap. So the expectation that officers would be working on an initiative on their own. But as officers, as team leaders in the community, it could be a good item to be able to explicitly. Yeah, there are a few other changes, but the main changes are in the events of the role. Your feedback, Alisa, would be great, especially what items we need to keep, what items we need to reward, etc. So there are a few patches there. But before we actually mention that, it would be great to get your review. Yeah, I'll do that after the call. Yeah, basically the same for release the communication officers. So I slightly expanded the description. But again, this topic is still wide open for the discussion. So if you see any items, you would like to add, remove or amend, please just do it as proposals in this pull request so that we can keep the discussion going. One documentation for me, one of the potential issues is the release of several because the release of several change significantly. Firstly, this release automation infrastructure, which is currently available. Plus we used and expanded Jenkins maintenance team. Plus we changed the LTS process slightly. So there are some entries here which could be adjusted. Only the reason for the call. So I will definitely take it offline to the mailing list. But here right now, it looks like this definition might need an upgrade. Also, for example, manage code signing keys right now it's added to the release role, but the fact that it's infrastructure officer doing that at the moment. And since we have keys being used for multiple purposes, maybe we should actually move it to the infrastructure. So, if you see such items, please just raise to the box so that you can update it. Any feedback comments. Thanks for starting it and I'll give feedback in in the pull request. Thanks very much. Okay. Thank you. So, again, sorry that it started slightly late in the process. But yeah, there was a crunch to just get elections announced with all the checks and the requirements to be met. Thanks a lot to Uli and Alex for helping with that and for being from the elections committee this year. It would be difficult to do the result. I haven't talked to the person involved, but everything is on time so far. Okay. The next topic is Jayfrog Artifact Recourse Productions. Mark, would you like to share the progress. Yes, we had a very good session with Baruch Saragursky of Jayfrog Daniel Beck and me. Today and talk through both the high level vision. And the high level vision is the most gratifying Baruch reinforced that Jayfrog truly intends to continue support supporting Jenkins project and the Jenkins project development. They want to block usage that's unrelated to Jenkins because it makes a cost burden on the Jenkins project and on them that they'd like to not be absorbing they however stated very clearly that they want to support the Jenkins project and its continuing use of Jayfrog factory. Now they offered Baruch offered my suggestions of ways that he thinks specific changes we can make in the use models that will likely hit the entire target they need for or their, their objective of supporting the Jenkins project. Daniel Beck understands those requests and is going to do some experiments based on them. He was quite hopeful that it was not a wholesale massive modification of things. But he's going to know if his experiments work out. So, Baruch is going to help with log analysis from inside Jayfrog, and he'll find that person, and then we'll, we'll have a discussion with them. At some point in the future further further discussion. I've been into the meeting very concerned and came out of the meeting, meeting feeling much more comfortable and much more confident that Jayfrog is still very committed to the Jenkins project. Thanks for the summer. So why it's important. Jayfrog hosts the entire report on this. So basically it's mission critical for development and mission critical for delivery of artifacts. So we don't, well, we basically store all the jars and whatever produced by made in the middle of close north factory. Also, we use it for incremental releases and a few other delivery focused flows. And yeah, the current cost is quite high. I'm not sure whether I'm allowed to disclose the number. And Baruch didn't know the number so we should know I wouldn't disclose it because I talked with him about the number during the call. And he noted, he's not focused on the cost he's focused on being sure that we have legitimate use but you are correct oh like the cost is substantial. So right now, one of the updates was that we actually added Jayfrog to the list of major sponsors to the project. Yeah, we definitely, we definitely interested to see how we could reduce the cost. Right. Okay, thank you. So there was an item I added by Lisa and guess it's isn't related to the officer updates. Totally different. It's from me. All right. Yeah. Okay. Yeah, it is on my to do list. I think a couple of months now. So what I tried to figure out what is what is the current state of our donations to FF is so first I wrote a mail got no answer and now I wrote a formal letter and got no answer. So he signed out of the, you know, the leader of this. It's not a company. It's, you know, I'm actually not sure what's actually behind it. It's a one person show and nobody's responding on these donations thing. I think we have three or $4,000 built on their account. But currently the website is kind of down. And I'm not sure if anybody is, you know, responding. So I think, or I fear the money is lost. I don't know. Actually, I'm not a lawyer. So I don't know what we can do now. So it's a little bit strange. I wrote emails. I wrote a letter. So, yeah. Has someone an idea what we can do here. So, well, it's a good question because actually we didn't have a lot of leverage or whatever options and also it's a question of time cost. So, yeah, I'm also not sure what to suggest. But if you're confident that it's just about two or three years, so maybe taking the current situation needs better to just put it on hold. Well, it's still unfortunate. But yeah, I'm not sure what exactly we can do. Maybe with just putting it on hold. I don't see. I don't see a lot to be gained by us attempting to, to chase that I'd rather have these time and other board members time focused on helping improve Jenkins. If it could have, we could have found it great but it, it looks like they're, they're not, not readily findable. I think I have one option is we have computer magazine in Germany. They are caring for customers and things like that. So maybe I'll write them an email if they can help here. Because if something is going into public somebody sometimes is willing to help. So, I think this is an option is not too expensive because it's just writing an email. They normally help people for their work against companies, but maybe they also help open source projects. Let, let us see. I'll try. Why not. Yeah, thanks a lot for driving that. So, yeah, once we discovered the state for FFIS, FFIS, we updated our donations for, so last spring we actually removed it from the donations page. Right now with this only coming into bridge. I guess the only problem that their website still will be the Jenkins project. If you know the hyperlink, right. Yeah, I have the hyperlink but the website is now broken because MSQL is not responding anymore. I think, I think they still have the domain, but the computer behind the scene is broken. So it's FFIS.de, I can post it here in the chat. It would be very unfortunate to lose money of those who don't need it to the system. At the same time, by spending months on withdrawing this money, it's definitely would be even worse to the service. Yeah, those who support the project. Let's see if no low cost option. Yeah, just moving on. Okay. Thanks so much for driving that. And yes, speaking of donations, we still have community bridge account. This account isn't actually used at the moment because we don't really promote it. Well, in any means it's just reference on the donations page, but we do really pronounce from a multi donations page either. So you can see that it has opened $80 at the moment. But it actually raises the question because right now we don't have so much money left in our coffers. Over the past years, we invested a lot in programs like Outreach, we also paid all our debts for infrastructure costs and other activities. So we spent quite a lot of money. At the same time, we don't have continuous money in flow because yes, pay flow is shut down. We have, we still have money there. We also received money for Google Summer of Code this year. So even though there's an emergency, we have some cash in the coffers. But if you want to start our own Outreach programs, or if you want to self-found a 3G or community bridge documentation projects like we discussed a while ago, then actually our opportunities are quite limited. We can always shake some trees, find sponsors. We could contact the continuous delivery foundation and see whether we could find options there. But if we talk about funds, the Jenkins project on itself, we are not in the best shape at the moment. So maybe we should think about how we actually facilitate donations and how we promote them. Without being super aggressive, but still making the page more visible would be nice. I have it in my to-do list. So once the situation with elections becomes better in terms of time required, I might take a look at the donations flow and get it over the line. But if somebody has any ideas how to look after the promoted, and if you want to contribute, please do so. Okay. Anything else for today? I have one, Oleg. So I am putting a link in the chat window. So this is circling back to a video that I shared with the governance board a few months ago. Daniel brought up the issue that I guess the gun and the tank looks a little bit non-impositive light, I guess. But we changed that. The production team changed it a bit. And so I like, and so this is what they've given us with that change. So I like to get feedback and see if that's okay to use. It's still, to me, it's not much different. It's still some, you know, some that looks like a gun. I don't know how much we can do about it. It's supposed to be a telescope, right? Well, it's, well, you, but it shoots something out though. It's a projectile launching device. That's fine. But thankfully, no longer has quite the direct correlation to the, to, that it earlier have. I think the change looks good from what I can see. Okay. I agree. It looks, it looks much more cartoony now. Okay. And I like that. I think that's a positive. Yeah, I agree. So, first night thing that, yeah, since we have a video, it might help to promote Jenkins, et cetera. But concern about publishing it for me personally, this guy was always about from the earth to the moon book, even in the original version. So, I'm perfectly fine. Okay. So you wanted to publish it through social media channels, right? Well, that and I'd like to get it on Jenkins.io homepage somewhere. And then I'll talk to Jackie to see if we can get it on CDF as well under Jenkins. And a list of the ideas. It would actually be hosted on YouTube so that we could embed it, or are you envisioning a different form of hosting. You can let me know what is best for Jenkins.io. I'm, I'm totally easy with that. Yeah, for Jenkins.io. Yeah, it's better to have it on YouTube for another public hosting which supports embedding videos. So we can put it on the Jenkins YouTube channel. Yeah. Right. Yes. Yeah, we could. Yeah, after that, it's quite straightforward to add it to the page. Well, it's still yet to be seen because if you embed the video, it might be, it might have some issues with JavaScript, et cetera, connected to the page or health collisions. But in principle, it shouldn't be a problem. Okay. We certainly have other pages that embed videos. Right, but we have some pages which appear as a SkiDoc and we have a macro for that. And this page is not a SkiDoc. It's Hummel. It's a, it touches additional JavaScript. So, so for clarity, I was not assuming that Alyssa was asking for the ad to the root page. Were you asking to add it? Would it be okay, for instance, if we put it on the Jumbotron, a link to a page that would then show you that video? Or do you want it on the root page? So Jenkins.io with the home page, would you consider that as the root page? Sorry, let's be very specific. The page that Oleg is showing right now, is this the place where you would like it? Yes, it does not need to be on the Jumbotron. Because I think I'd like for it to live a little bit longer than, because like DevOps World or CDCon, once the event is over, or after a certain amount of time, we remove that. Right, so I'd like to live on the page where it can, at least on the home page, this page right here, where it can live a little bit longer than, you know, taking it out after a few months or something like that. But I'm totally open to what you guys feel is best. Somewhere on the home page works for me. Mark, you look confused. I'm wrestling with where we would put it visually in this, but maybe that's, let's you and I take it up separately to try some different ideas. Oleg's right, this page is not directly ASCII dog, but I suspect it'll take a little bit of extra work to embed a video on this page. If this is where you want it, let's work through some experiments to see, is this sort of what you want or that and see what we can find. Okay. I'm totally open. Okay. One more topic. Do we have a list of specific terminology change issues that we're going to include in Hacktoberfest? Do we need to open some? We think that we need to open some. Yeah, and actually Alex, you took this section item, noticed. So, yeah, right now what we have on the, so on the roadmap, we basically link a mailing list for master terminology up and at least for agent terminology cannot have an epic. So there we are all set, at least to some extent. The problem is with this entry. So what I did while publishing Hacktoberfest page instead of link and mailing please. I just said that all the terminology follow the example for agent terminology. Yeah, there are some references how to do that and things. But yeah, it's a kind of work around. So if somebody has been bought to start creating issues, it will be great. And we have multiple places where we could create issues. I'm going to say that to me, I'll take that action item. Is there an epic already in Jira for that? No. I'm waiting for that. So, yeah, for Jira, it might not be needed. So in principle, it would be nice to have Jira. But we can get away even without Jira. I'll get an epic. I'll get an epic creative and then I'll start building the tickets, the issues under that epic. All right. It doesn't matter if it would be an overarching, if it would be okay with you. The doc, SIG in the meeting Monday afternoon. Said that they would be okay with putting things specific to the Jenkins. IOS site as GitHub issues and I've got the action item. They've got a, they probably agreed to a plan of how to structure those so that we get. Maybe five or six total issues, each not huge, is that okay for you? I'd rather not track Jenkins.io site issues in JIRA because we've got the GitHub issues that we're using to track it. Yeah, I'm fine with either or for the Jenkins.io that can get tracked in GitHub. For the other items, I'll track that in JIRA. Right. Okay, so if you have this documentation, it would be definitely beneficial because again, HectorBerfest has already started, but this page, you'll be kind of finding a page for the next month and we will have HectorBerfest that this information can be used because obviously it will take months or years to clean up everything. But having guidance is definitely a way to facilitate the contributions. Okay. Just on HectorBerfest, I think the CDF newsletter is going out tomorrow and that's got a link to a landing page which will also link to the Jenkins one as well as other projects. So we are happy to help try and get some more attention and eyeballs on HectorBerfest. So enjoy those PRs next month, everybody. Thank you. I already completed my HectorBerfest. Last year, I completed it 34 times. So I don't want to do so much. Thank you for bringing that up, Alex. Make sure you're driving that, Markey. Last one. Okay. Any other comments on HectorBerfest and all the changes? Yeah, just one small thing I was just going to say is like recording keynotes for CD-Con, but I will be highlighting that in kind of the overview of CDF is, I think, just a really important direction and thing we're doing. Thank you. Okay. So next meeting. So in September, we will be moving meetings to make some space for DevOps, CD-Con to ensure that the contributors can go there. Technically, we expect to have the meeting next week. Do you want to have the meeting next week? I'll be busy with CD-Con, I can't attend. It's October 7th, if I recall correctly. So for me, it's a bit late. It will be great if somebody else drives that unless there are major topics to discuss. But if we can do this meeting and then return back on the original schedule, then that's fine. If not, we can just close another meeting in two weeks. Yeah, I'm happy to run the meeting October 7th. I'm Markey, I mean. October 7th, I'm happy to run it. That would be a good day for me. Alex, would you like to take it? If we have it, do we have some topics to discuss next week already? Let's see. Okay. So I can tentatively say that Mark to drive it. I don't have access to any of the Zoom crads for running meetings. So Mark would be a better choice. Okay. So let's see. Okay. Then anything else we need to discuss today? So the next mile, is the next milestone two weeks out? Is that a critical deadline date for nominations? Is that a critical date on the elections process? Well, it's critical date on the election process. But it doesn't influence the governor's meetings. Okay. Great. Thank you. Yeah, the election committee will have their own meetings to basically review nominations and to prepare the final list of candidates. This meeting won't be public, but it doesn't require governor's meeting. Great. Okay. So yeah, the calendar is not that packed at the moment. But yeah, it's an overlap of the city comments, please pull it. So when we will definitely meet meeting is 21st. Oh, no, it's right. So on 21st, when we start the release candidate, we also make a baseline selection. So we will meet at this meeting. So maybe we do the meeting for next week and then return back to the original schedule so that you be aligned with LCS full as you plan. Sounds good. Good for me too. So then we have a plan and thanks everyone for your time. Thanks. Thank you all. Thank you, everybody. Bye, everybody. Bye.