 Hi all, today is October 9th and we have the second part of the Jenkins contributor summit. So the today's plan is to have a short session of project updates and then maybe take a look at the roadmap together and then have unconference sessions focused on various topics. For example, we have sessions about Jenkins and Tecton integration, open-line telemetry next steps, et cetera, et cetera. It will be quite a relaxed events, but thanks a lot to everyone for joining. Hopefully, we will have very productive technical discussions later today. And for this particular session, I want to keep it really short. So maybe 15 to 20 minutes and then we can just do one planned unconference session to take a look at the roadmap stuff or maybe we could do live demos earlier. Okay, so what is Jenkins contributor summit? It's our soon-to-be-regular event where we discuss Jenkins evolution, major updates. And this time we decided to do it in the Asian and Pacific time zone. So to have a better outreach. And this is the second part. We had one contributor summit on June 25th and before that in February, we experiment with different formats and schedules. And hopefully we'll have another summit sometime around Fosdam. So it will be February and stay tuned for that. So maybe just have informal discussions. So please be ready that many topics won't have slides at all. And everyone is welcome to participate. So if you have to use Jenkins, if you contribute particular projects, just unmute yourself and start talking. This particular session is handled in a Zoom webinar, but all the next will be handled in Zoom. So there will be less restrictions. So what's our schedule for today? Unless there are some last minute proposals for sessions, maybe start this short opening. And then we'll have two sessions in parallel, one for Jenkins documentation without Wiki Jenkins IO because Wiki Jenkins IO is no longer a thing. We disabled it. Then in parallel, we'll have a discussion about Jenkins and OpenTelemetry. What do we do about having OpenTelemetry plug-in and OpenTelemetry for remoteing, how we continue the integrations. And the second sort of third talk submitted by Rick is about making Jenkins a part of Kubernetes. It's particularly focused on better integrations and on our CubeSphere project. So hopefully Rick will join so that we can discuss it. And then we will have a short lightning talk session. Then we will have a break and later at 10 AM UTC. There will be two hours session focused on the first class citizen. So Andrea Frittoli from the Tiktron community and maybe other contributors will be joining us. The idea is to brainstorm potential integrations. What would it cost and maybe start drafting the JEP for that. Then at 10 AM UTC, there will be discussion for Jenkins file runners so that everyone can share feedback and we can discuss roadmap. And in parallel, there will be hyper-modern pipeline development visual studio code by Levy. So these particular sessions we can adjust if needed because I believe Levy wanted to participate in Jenkins file runner session and they completely messed it up. So maybe we'll just move it a bit if it makes sense. That would be nice. OK, then we will definitely adjust so Jenkins file runners. Let's do it at 1 PM and then after party and 2 or something like that. OK, so for the next meetings, for the next parts, we will be using Zoom. I'll share this link in the Slack channel. So yes, we have Slack channel for this contributor summit. Now it becomes more or less permanent one in the CDF Slack. So if you're a member of that, there is Jenkins contributor summit channel. I'll share the link later. And yeah, there is link to a few Zoom sessions. For the discussion, we have community Jenkins IO, which is basically discourse. Feel free to join and share your feedback here. Well, basically any feedback will be appreciated. And also, if you want to start particular discussions, you can just start a new topic here. OK, like that's also where they've registered to vote in the upcoming elections. Yeah, we will talk about that later. OK, OK, so just quick summary, everyone can participate. Yes, submit your questions, comment in the chat. You still can do lightning talk and please be nice because everyone contributes today. It's Saturday, so most likely everyone joining today joins on their spare time. Mark joins super late. Is it 3 a.m. already? No, it's only 1 a.m. Oh, yeah, sounds good. But yeah, thanks a lot for doing that. And again, city of slug. If you want to join, there is a link on Jenkins IO, which describes how to get invitation. And if you are not a member of it, please join because for some items, it will be just posting links there. OK, so. Before we begin, I would like to ask all huts of conference sessions to record the video and then to publish it. And if possible, please recognize some meeting notes so that we can share this information with those contributors who can participate. Because, yeah, today is Saturday, also. You are in and Asian time zone, so many people cannot attend. OK, let's do quick state of the union. So it's basically built on collaborations from all officers and board members who had an opportunity to collaborate. And if something is missing, please feel free to just jump in and discuss the topic. And the first one, which was already committed by Mark, is about elections. We will have elections in November. And currently there are open applications. So everyone is welcome to register and also to submit nominations. So we will be re-electing two board members. It's my seat and seat of Uli Haffner. So there might be new contributors joining instead of us. They might be asked if we submit if we apply. So but everyone else is welcome to submit their missions. And as always, we will be re-electing all five officers. So security, documentation, release events, and infrastructure, right? And, yeah, for example, events officer, this position is just open because Mark Jackson stepped down last February and since that I was acting events officer. And definitely I kind of dedicate as much time as I would like to this role. So if somebody is interested to take it, you're more than welcome to do so. And well, same for all other roles. OK, so if you want to participate, this year we use the new process. So basically, you just need to submit to join election voter group on community. And, yeah, currently we have 26 registrations. And I'm pretty sure that some people at this meeting haven't registered yet. So please do so. OK, Oleg's much too polite. I would shame you and say, if you haven't registered, you probably should because your attendance here is already contributing. So yes, the definition of contribution is very broad and lots of ways that we contribute by helping each other, by helping others. Agreed. OK, so key dates October 31st into nominations. So November 7th, we should have any dates published. And then there will be three weeks of voting. And then December 30th results will be announced and will be effective. So the timeline is quite relaxed, but again, please submit your nominations and your current Jenkins officer or board member and plan to not proceed. It would be nice if you reach out to the Jenkins governor's board so that we can plan for transition. OK, anything else regarding the elections? Then, OK, role updates. Most probably I missed someone, so please add changes. So Basel Kroll has joined as new Jenkins core maintainer and thanks a lot to Basel for his contributions over the past years. It's much appreciated and Basel currently works on Goava update and a few big projects in the Jenkins core. So stay tuned for the next releases. Also, I believe that I missed Steven Spilker, who is currently who joined as PR reviewer. Well, so do we want to put my my being given JEP editor status and the JEP improvement process steps that you're planning? Is that a is that a reasonable one? I'm not sure if that you consider it's reasonable. Welcome aboard. Though, yes, I mean to the proposal that we basically make care of the officer and board member, Jeff is by default. Right, which I think I like that proposal as well. Yeah, Jenkins enhancement process. Good thing. Yeah, so, yeah. Any other updates? None that I know of that that covers it, I think. OK. So then let's press it with a quick updates for projects and six. Yeah, so maybe a few updates which I didn't put slides for. Firstly, we will be officially joining the inclusive naming initiative as continuous delivery foundation. So it's more or less settled. Currently, the blocker is quite hilarious because two life of membership I need to provide email in the enrollment form. And yeah, Gmail accounts are not accepted. And I don't have any other right now. I will figure it out. But yeah, you never know where you experience surprises. So what will happen? Yeah, continuously the foundation will open during this list. I will be the primary content as to see my back. And yeah, we will also be listed as a related project on this list. So Kubernetes, IBM, Jenkins as well. And yeah, everyone is welcome to keep contributing to this topic. There are some marketing activities around that. So welcome to another foundation. OK, are there any other major updates we're missing? Well, on inclusive naming, for me, there's a reminder that plug-in maintainers should be sure they run their tests with Jenkins versions 2.307 and later because inclusive naming actually changes some testing environments. So inclusive naming is going to have real impact. And we should embrace it and be glad to have it. Mm-hmm. Yeah, there is a lot of work to happen. And actually, if we start following the recommendations of inclusive naming, it will be a lot of work because currently the terminology recommendations evolve. So for example, it is your website is this. Yeah, so there is a word list which is being formed by multiple contributions. So there is tier one. And yeah, tier one includes a word, abortion, then a white list, black list we are working on, master slave we are working on. But yeah, so we will abort abortion if we follow these recommendations. It's something that we haven't discussed yet at all. And also there are other recommendations for tier two, tier three, for example, all military terms needs to be replaced. Some more people are proposed to replace the executor because it's affiliated with executions. So we will need to have discussions of what we do. But if we want to align with all the recommendations, it will be a long, long work for us. OK, and you think else? Not that I know of. Yeah, so it was quite silent this summer. But yeah, you can discuss a few other bits. OK, Jenkins infrastructure, do you have anyone who wants to? Yeah, so I can talk to that briefly, so the next slide is the one that's got something useful on it. So we're working actively on ci.jenkins.ios code. Unfortunately, sometimes that means things are disrupted like at the moment where the Windows agents can't find Java. So sometimes we make mistakes. But our Azure controller, Kubernetes agents on AWS, yes, we've got ARM, yes, we've got System 390, yes, we've got PowerPC, and we've got other suppliers coming. So it's evolving and developing. Next slide. And we're actively working to reduce costs. We're proud that this month we changed what was a $600 or $700 a month server into a much, much lower cost server hosted on Oracle Cloud. Thanks to Oracle for their donation. And thanks to Olivier Vanine for doing the work to make the transition. And we know we'll make future configurations to increase our cost savings. That's it for me. So what else was mentioning? Yeah, currently there is ongoing commingration for the commentations for Wike. I believe Mark will speak about that during the communication update. And that's it with regards to major infrastructure updates. Yeah, the next slide shows the infra meetings that Aditya Srivastava and others join with us. But it's just the usual stuff there. Yeah. So we also have some items on the roadmap, I believe. I'm not sure is our roadmap up to date? I thought it was. But I didn't do a detailed look at the roadmap with the card infrastructure yesterday. You're certainly welcome to check, though. It's under the About menu there. Oh, like, oh, got it. Well, I finally issued at redirect. So here, what do we have? Yeah, so continuous delivery of Jenkins plug-ins is in progress, ci.jankins.io as code is very much near term where we're working it. Yeah. So what else? Funding, community bridge, it's basically a life. We just need to announce it. There are some other items which are not included. It's my fault. So for example, LFX, easy CLA adoption is ready to go. I'll probably enable it for the engineers for the owner this weekend. And we can discuss other projects. So yeah. What's other missing things? We will be transferring AWS account. Yeah, I guess that's it. Right, yeah. Yeah, also LFX security. But I won't be talking about it today because it's nothing to talk since June we made no progress. We're still waiting for the Linux Foundation to proceed. Yes, we should move on because the infrastructure is kind of fringe topic for many of users. OK, Jenkins platforms. So platforms, the first topic is that we successfully transitioned to Java 11 as the default in Docker. Java 8 is still available. We also just this week received Java 17 previews available in the Docker images. So if you're interested in experimenting with Jenkins and Java 17, there's a Docker image that you can use both for the controller and for the inbound and the SSH agents. Note that it's hotspot only. We're not going to do OpenJ9. We had toyed with OpenJ9 and it's just there just aren't enough of us on the project interested in OpenJ9 to do that split. You go to the next slide, Oleg. In terms of processors, our Docker images are now multi-platform. We now in the same Docker image can support AMD64, ARM64, and System 390 mainframes. Eventually, once we get a particular bug fix for QAMU, we'll have PowerPC as well. And we're regularly testing the Debian install packages on all those platforms as well. So not just Docker, but also the Debian installs are confirmed that they work on multi-platform. And that that's it for platform SIG, I think. And for documentation. So documentation has two two big stories. First is the plug-in docs transition to GitHub. Seven hundred and fifty plugins have migrated. That means that the plugins that have that are installed on over 10 percent of the Jenkins installed base are already migrated. But we identified additional plugins where maintainers have agreed during Hacktoberfest to review pull requests and you can then submit. It's a very easy place to do a nice Hacktoberfest contribution, help us transition this documentation, help the plug-in maintainer, everybody wins. The video that's linked there is a video tutorial on how you do that next slide. And then today we'll be discussing what it means to not have wiki.jankens.io with Confluence and how we're going to get the transition there. That that's really all that I needed to say on docs there. Yeah, thank you. OK, so for Advoc, send outreach, I will do quick update. So, yeah, we participated in Google Summer of Code again. It was our fifth year. It has been fully completed. We had five projects, all students passed the evaluation. And yeah, so projects we completed, Cloud Events plug-in for Jenkins. So now Jenkins can submit Cloud Events and later we will be talking about how to integrate it with CD. Events project, then Conventional Commits plug-in provides version management for Jenkins in pipelines. We've got better credentials by Indian for Git. We got Jenkins remote monitoring with basically open telemetry so that you can submit this data to other open telemetry consumers and monitoring systems, for example, for traceability purposes, for logs, for events. And yeah, the results security validator for Jenkins Kubernetes separator, which was created. So I would like to thank all students and it's great progress, as always, and looking forward to the next year. We did a retrospective and hopefully they will be a mentor summit soon. But generally Google Summer of Code is completed. And yeah, another event we have these days is of course, Hacktoberfest. So if you're interested to participate in the events Hacktoberfest, everything is published there in terms of the links. We had a kickoff session one week ago. Thanks to Mark, Wadiak, Uli and other contributors. And yeah, hopefully we will have more things happening here and there. So what's not listed other events? So I will just summarize what we had this year. So we had DevOps world, where we had workshops on for newcomers, so there will be a lot of Jenkins sessions there. And then there will be coming soon. So there will be a day of Jenkins Japan in December. Jenkins will be represented there. Then there will be a supply and a chain summit on October 12th, again, Jenkins is represented there. And there are other minor events here and there, but yeah, these are two bigger ones. So if you're interested to participate, please do so. And of course, FOSDAM 2022, we will also have some agenda. We're still waiting for FOSDAM to announce the program for this year, whether it will be in person or remote. And yeah, depending on that, everything else will be defined. But yeah, if it's in person, I will, I'm going there to your life. Yeah, I sincerely hope it's in person. I wanna be there. I want real life experience face-to-face again, just looks, sounds so nice and so wonderful again. Yeah, so let's see. Any other events we are missing? So one thing which makes sense to mention, there will be no LFX mentorship programs resultant because basically there was no applications. We tend to be discussed having two documentation projects, but we haven't heard anything from potential mentors. Mark, I guess it's no longer planned, right? That's correct. Yeah, one of the, it's a reminder that one of the challenges we have is getting enough mentors to do these kinds of projects. Right now we just don't have the capacity to run one. I think we could get funding. The problem is not funding, it's mentors. Yeah, basically the CM40 tone client, we had discussions, but we didn't proceed. So unless something changes, I call it we are not starting this year, but yeah, maybe next year, in February, who knows? So we have some money in our pockets and if somebody wants to participate, please do so. We just need a champion who would make it. Okay, and yeah, as you might see, we are skipping many CX this time because we don't have all the contributors who are willing to participate, but yeah, and who have opportunity to do so. But yeah, there are other shifts here and there, of course for cloud native CX, there is a lot of progress after October 1st, especially for observability space. And maybe we'll talk about this at a separate session today and yeah, for the CX, we can proceed. So is Rick on the call? He is, he's currently an attendee, hasn't been promoted to panelist yet, but I definitely see Rick there. Yeah, sorry, I can't promote people and talk in parallel. So yeah, I just grant everyone who wants to participate upon this permission. Maybe Rick would like to update for change is localization seek. Okay, so for change is localization seek, one update I can make. So in the continuous delivery foundation, there will be officially change is localization seek too. It has been started, it has been approved and currently there are just logistics questions left. So we are waiting for the attendance delivery foundation to create our mailing list, grant Zoom account so this seek can actually kick off. We had a quick syncopation about that last week, so hopefully it will proceed. Okay, does anyone else want to share updates? Okay, then let's proceed. So again, it's a great time to contribute. Yeah, we have October 1st, everyone is welcome. A lot of activities in Jenkins are done by pull requests if you want a t-shirt and you have documentation, design, everything just submit, just contribute and we have a lot of featured projects already and all these featured projects are actually a part of our roadmap too. So here, if you go here, you can see what we promote to Jenkins website, Jenkins core, plug-in site of course, we've changed a lot, Jenkins for the runner, Tecton client, plug-in primitives, terminology cleanup, of course, artwork. Yesterday we got a logo submitted by this just community from France. So what it is, it should have much thread. It has been merged and yet I don't see it. I'm gonna have to go look like because that new image is delightful. I believe that we have issues with some promotion but yeah, at some point we had a discussion about having a she Jenkins logo. So yeah, this is the first one and everyone is welcome to submit more. It's here. So it's not just about code, you can create logo and also get a pull request towards how you do it. Okay, so yeah, back to this summit. So in 25 minutes, we will start a session for Jenkins documentation or Jenkins open telemetry and Jenkins be a part of Kubernetes. These sessions will happen in Zoom webinar. So there will be no problems with granting permissions, et cetera, and you can find a link here. So basically let's join maybe 10 minutes before the session start and yeah, there I will create rooms so that everyone can start their own discussion. And as discussed, there will be some changes. So I will push Jenkins follow runner a bit later so that we can participate in parallel. Does it impact anyone? That sounds good to me. Okay, deal. So like when the Zoom meeting starts, the webinar absolutely will end. So people need to grab that link now while they've still got the webinar running. Yeah, I will update the link on the Meetup page. And yeah, please join it. So... Do you mind dropping that link in chat right now? Yeah. Okay. So again, today is quite a relaxed summit but hopefully we'll have a nice chance on technical topics. And yeah, if you want to propose something, so for live demos, we still have some bandwifes and yeah, we can dynamically update or maybe going forward, we won't even schedule such big contributor summit events and just opt out to scheduling several sessions. I mean, for example, we want to talk about TikTok and Jenkins. So we schedule a session after creating Doodle so that you'll have more working group like meetings. Okay. Any comments, questions before we close down? If not... See everybody in the Zoom sessions in the shared sessions. Yeah, so 15 minutes break and again, I ask all session hosts to do the recording locally. Then you can share the link, for example, via Google Drive and we'll republish it on Jenkins YouTube channel and be a bonus points for meeting notes. Okay. Thanks all. Thanks.