 All righty, we are recording. Welcome everybody. This is the Jenkins cloud native SIG meeting. This is a sort of impromptu meeting because we don't have an official meeting time yet. My name is Marky Jackson. I'm one of the SIG leads. And before we get started, just a couple of house cleaning items. This is a recorded meeting. So it is available on the internet and we do follow the Jenkins code of conduct which essentially amounts to be nice to one another. So we have, I'm gonna go ahead and share my screen. And we have two topics on the roadmap. The first topic is meeting cadence. So we started this impromptu meeting today, Friday, October 30th at the eight AM Pacific standard time. And what I wanted to do is set a meeting cadence. Is this time work for everybody? On my side, this time is good. Tim, what about you? Yeah, this works okay for me. The previous times weren't possible. Okay, so Tim, so what I will do, I am going to add an action item. Give me just a moment. I will add the meeting to the community calendar. There will be a new zoom link and I will update that in the chat. So that is it. Does anybody have anything else regards to that for meeting cadence? Okay, moving on to the next. I just wanted to ask like how did these meetings like go on before this kind of free initialization? Wait, can you repeat that again? How did these meetings, what? Yeah, so how did these meetings go before like before right now? So previously the meetings kind of were, they're much like every other SIG meeting. There's a note taking, there'll be, we'll talk about items that are up for discussion, items for road mapping and things like that. Really what we want to try to do, I would think in the first few meetings is try to start thinking about what we're looking to accomplish with this SIG as well as start getting a roadmap together for the things that we'd like to accomplish in the next year. Does that answer your question? Yeah, yeah it does. So if it's okay, can I ask another question just related to this one? Yeah, totally. Yeah, so before this re-initialization like what were the goals that were set for the SIG? So if you go back at that meeting doc I gave you, there weren't really, the goals that were set need to be re, we sort of need to revisit them and make sure are they still the same? So if you look back at some of these previous meeting notes here, you'll be able to see some of the things that were being worked on. And that's kind of once we, I think with this meeting what we want to do is make sure we set the meeting cadence and then what we want to accomplish, what we want to start doing next weekend, which probably will be everybody reviewing these notes and seeing if there were things that were left open if those are still of value and if we can accomplish those and then start to build out the roadmap. Does that answer your question? Yes, yes it does. Thank you, Marky. You're welcome. So the next topic is, Vibhab you've entered that and that's the Jenkins operator roadmap. So I would like to just touch on this topic with just a real quick bit. The Jenkins operator is handled by another entity like they're an actual company that handles it. And so we don't, I know they did publish their roadmap. If we wanted to try to bring that into the cloud native six then we're probably gonna wanna reach out to them and get them involved here. But please take it away, what were your questions? So it's my questions. So I just wanted to kind of go over what is happening with the operator right now and then on our side. So I'll just give a little introduction of myself. So my name is Vibhab and I work for Red Hat in the OpenShift Jenkins team. So we have an instance of like a Jenkins image and a few plugins that we maintain. And we've been giving it to our customers and supporting it. And now that we are in our main product has like moved away from the Jenkins image itself we are slowly getting into like the Jenkins operator. And for the last, I think it's been a little more than a year since we've kind of been looking at the Jenkins operator and have been working on it. So apart from that, like right now with the governance stuff that is going on, what we've done right now is we've forked the Jenkins operator repo and we have, we are working on it actively. So I, so in this I'm basically going to discuss like what we have as in the fork like doing with the Jenkins operator and if it would be possible to get the, you know, people from Vertus lab involved with this and, you know, get discussions going on on how we can really, you know, move the operator forward. Yeah, so I know that there's an email chain that has been going back and forth in regards to getting that. I have personally reached out to the team that is handling the Jenkins operator to get some feedback. I know some other people have also done the same thing. I think before we can have discussions about the Jenkins operator roadmap we definitely need to get them involved in the SIG. So I'm going to reach out again to see if we can have them attend next week's meeting and see if there's something we can do. But I definitely think that before we have any discussion about that we need to have them here as well. Would you agree? Yes, I agree. So, yeah, that's all that's, that's it from my side then for the roadmap case. If we need Vertus lab to be in this meeting, I'm, I agree with that as well. Yeah, so what is the current state about that? We got a request response from management at Vertus lab. They said that they are about writing back to the developer, and they pleased, never happened. But they also declared the intent to start the distributions in November. Jenkins both tries to get the response. If it doesn't come, maybe you'll consider other options because right now the situation is not, the project just doesn't work, but there are private folks which are being co-opped, which is not exactly what is expected from our open source project being hosted within the Jenkins organization. And yeah, if it gets stuck through the, I think we will have to opt on that. Okay, so let me just make a note here because I can't spell. Okay, so basically what we're doing is we're reaching out. We're gonna wait and see. We'll wait until once the Jenkins elections are done to see where we stand. And then we'll decide the next course of action once that's done. Is that okay, Bibhab? Yes, that sounds good. Yeah, it's not really dependent on Jenkins elections per se, but yeah. It's also a matter of the bandwidth because the agent's board was quite busy this month. It will be a bit better in November because he did the most of the legwork in the direction Saova. But still, I would give another chance with the shop to this point. Does anybody else have anything to add to that? Just sorry that it takes so long because it's something to think about in our processes so that we can introduce another escape hatch to prevent it in the future. Okay, does anybody else have any other topics that they would like to discuss? Okay, so I'm gonna go ahead and just cover what the action items are for next week. Everybody, Oleg, everyone has agreed to this meeting cadence, meeting this day and time. I know that this may not always work for you. But this time is actually quite good, especially now in the meantime. Okay, awesome. I'll add you as a plus one. Yeah, for me, the biggest problem is time after 6 p.m. Especially at 5 p.m. That's why Pipeline of the Tanksick was a problem. But now this meeting is 4 p.m. and Pipeline of the Tanksick is 5 p.m. So basically I'm just, my availability is not the time. Awesome, okay. So the action items that are for next, between now and next meeting will be, I will be adding the meeting to the community calendar. I will set up a new Zoom and then I'll update everybody in the cloud native SIG-Gitter once that's done. An action item for everybody on this call will be to review the previous meeting notes and see if there's any areas of interest that we would like to extract from these previous meetings and resurface them. And we will go over that next meeting, which will be next Friday at the same time. Yeah, I will pull a couple of additional meetings which are not listed here. Because they happen to be limited group and not in these documented guests. And yeah, there are a few other action items I took in May-June. Still remain on me. One is updating basic pages. We also had an agreement on things like moving JCask to another SIG de facto and de facto rank what is actually on the page. So it reflects the state on the roadmap. It still remains on my list. Yeah, unless somebody else wants to take it in short term, you can basically keep it as is. Can I assign that to you Oleg for moving the JCask release? Okay, I've also assigned updating the landing page to you. If you'd like, I can take to do that, but I think we should maybe sync on the verbiage that we want on there. There is a half updated page somewhere in my branches. So yeah, I like to start doing that, but anyway, there will be a pull request. Okay, so it looks like we have our action items. Does anybody else have anything they want to add? Talk about. Yeah, if you don't mind, I had a question to you, Markey, especially, you're part of the CD foundation, if I'm not wrong, like CD foundation interoperability. So are there any things that are overlapping between what cloud native SIG might do forward and the interoperability SIG of CD foundation what would be doing? I think, so the way the interoperability SIG is working is a much larger sort of scope and that's for all of the projects that fall under the, under the CDF, I do think there will be times that we will go and update the interoperability SIG, but I don't think the existence of this SIG as well as the interoperability SIG overlap with each other. Because well, the CDF sort of guidance is larger to every project under the CDF where the guidance for this SIG is specific just to Jenkins. So there may be times when we update them, but there's gonna be no overlap. Does that answer your question? Yes, it does partially I think because what about then plugins such as the one that I've been working on, Tecton plant plugin and if there are others like the Kubernetes plugin, not Kubernetes, maybe OpenShift plugins which do builds and stuff for Jenkins. So would these be considered overlaps or just no? No, those would not be considered overlaps. I think those would be considered specific to this SIG. However, we can update the interoperability SIG from time to time about the presence of these plugins. So for example, Oleg recently gave a demo of what was it the file runner? Which one was it Oleg? It was the file runner and I watched it as well. Right, so there are interoperability things that we can update them on, but the work that goes on within those plugins would be more specific to the Jenkins SIG and not the CDF interoperability. Does that answer your question? Yeah, it does make things clear. Awesome. It's basically how it's supposed to work in foundations. So yeah, we will have a lot of Jenkins internal things even if they contribute to communication with other projects at some point. But yeah, at the same time, we have a lot of pure Jenkins things. So for example, Helmcharts for Jenkins is definitely something you may want to discuss at the cloud native SIG, but it's unlike the interest for interoperability SIG at the moment. Okay, awesome. Well, if nobody has anything else, we will close this meeting out and I'll give you 10 minutes back and I will see you next week. So you want meetings every week, right? I think we can start every week, but then once we start to get going and we have the sort of roadmap laid out, then we can move it to bi-weekly. I'm fine with that. But for now, I think we should keep them every week until we get everything ironed out. Especially if we keep them short. Yeah. Alrighty. Everybody have a good weekend and I will see you all online. See you all. It was nice catching up. Cheers, everybody. Bye-bye.