 Hi everybody, welcome to the Jenkins Advocacy and Outreach SIG. Today is Thursday, November 17th. So on the agenda, I will cover last week's action items. And then what's new in GSOC 2023, yes, that's happening already. And then Jenkins election update, Kevin, I'm hoping that you can give us a brief update on that. Fastem 23 and Scale, which is Southern California Linux Expo 2023 that will happen in March, early March. So anything else that we need to cover? Maybe a shameless plug for me because I gave a talk about Jenkins last week at Mobile DevOps Summit. Okay. Just one minor. Mobile Summit, was it? Mobile DevOps Summit. I'll give you a link later or modify the documentation. Thank you. Yeah, I think we still have it down below. So, okay. So I had an action item from the last time that we met was to create a Google form for our newsletter. And the purpose of that was to have an opportunity for Jenkins users to add input or share what cool things that they have been working on for the last month within Jenkins and that share that with the community. So I've created the form and it's quite simple. I didn't want it to be a long form. I didn't want the newsletter to be too long because, well, people aren't going to read it. But it's here. So basically contact information, share with us what cool things that you're doing with Jenkins and then suggestions for how we could improve the newsletter. I'm open to suggestions. So if you have any feedback, please send it my way. And that's that. Do you have any questions here? Straightforward. Awesome. And Mark is not on the line. So we were supposed to talk about the contributor summits. The action item was that I spoke with Mark and he was going to send out a communication with the initial. I think it was the initial. Suggestion for the remix. So basically it's three days. Contributors summit two hours. Yeah. Yeah. And then so the first day we will talk about status reports and the UX future security on the second day and then end user experience. So Mark has highlighted these items, but he just needs to communicate it. And then we were supposed to like follow through and set up the contributor summit. So waiting for that to happen for Mark before I can do anything. Listen, if I can give you a small advice, I think we should poke this correct English mark and remind him. I think he has a very busy schedule right now and eventually see if this can't be delegated. Yeah, but I did ask him. He's like, well, I think it should come from me. I'm like, okay, Mark. Yeah, I'll poke him again. Yeah, and see otherwise we need to ask him. Can we go ahead to the group here? Yeah. And because the time is ticking. Yeah. Yeah, it's December, lots in December. So, so we need to move. Yeah. Agreed. Yeah, I will do that. So GSOC 2023 Google has sent out the communication for that already. They announced that it's just a couple of things that's going to be new in GSOC 2023, which is that instead of it being 12 plus weeks long, it will be 10 to 12 weeks. This gives it flexibility for for contributors and mentors to focus on small to medium to large projects. So that was nice. And then the other change is that they are now opening it up to both students and new contributors. OK, and the timeline is there. And my line is available here. We need to submit our application. So I know January beginning of February. So I like to get that stuff done earlier rather than later. So I will definitely work on that. We're earlier than we're about one a month and a half earlier than last year. Yeah. But it's not a reason not to continue pushing as we know that we need project ideas and mentors. And this will require some work. So we're good. Yeah. So we did a blog post call for mentors and project ideas. So, Ania, if you want to speak to your CMO, we are looking for mentors. It does not need to be, you know, anyone that you're you're new to the project welcome and, you know, you want to be a mentor, we can help guide you in this space. But we're always looking for mentors and projects idea that will help improve the project, the Jenkins project. So yeah, feel free to share this within your organization, especially with people that's currently using Jenkins. We can make an impact. We can make a difference by mentoring new contributors and students. So the concern as we usually have with pretty much I guess every year and previous year is that we do not have enough mentors. Right now, I only have four mentors signed up and project ideas. We're still working on that. We're still looking for project ideas for how we can improve the project. So that will be an ongoing discussion and we will be reaching out to individuals to see if they want to mentor again this year and looking for always looking for prospects for mentors. Anything else to add to Mark? No, I'm working on improving the pages on Jenkins.io. So enabling everything for 2023. And making notes on what what needs to be update. So the pull request is up. So as you see, it's still references 2022 and I'm working on the PR and I should release or make it available for review tonight. My time. Awesome, awesome. Let me know. OK, let me know if you need anything from me there. Yep, so that's moving along now. And updating also the runbook with all the all the things that I. Yeah, thank you for doing that. OK, Kevin. Yeah, so as far as the Jenkins election, let's go. We have we had 61 people registered of both and we have at the moment one nomination per role. And so we'll have a blog post coming out later this afternoon to announce everything. Voting is closed officially or voter registration is closed officially. Sorry, you scared me. Kevin, don't do that. I am so sorry, Mark. I would never try to scare you on purpose, I promise. But yeah, but I have a pull request open right now that I'm just getting a couple final reviews on and we'll be publishing that as soon as I have confirmation that everything's all set. And that will announce the candidates and what the process will look like for this year. I can't really say much more than that at this moment, because that one that's published, it'll have all the relevant necessary information that Mark told me not to say out loud. OK, OK. Now, since we only we have there's one nomination for per each role. We're still voting. Yeah, so that'll be part of the announcement. Yeah, OK. Yeah, that's so like I said, there's a couple things that I don't know for sure that Mark wants me to disclose just yet. So I'm trying to be as judicious as possible with not sharing anything, which is kind of rude. But yes, we will have more information about the voting process, the candidates, the statements, relevant links, affiliations and everything else. And it looks like the time frame that we had in mind is going to be perfect for all this as well. So the current term is going to end on the second, the next term will start on the third, everything should be good to go. And the current members and officers will be reaching out to the other individuals to set up transit transition and just knowledge, share after the fact. So yeah, great. Thanks, Kevin. Thank you. OK, it's Boston, 23. So the CICD Dev Room CFP is currently open and it will close December 12. This is taking place in Brussels, Belgium. And I know that Bruno made a submission to the embedded mobile and automotive dev room. Yes, because the CICD room is only half a day. So I don't want to, you know, to be just about everywhere. There must be other voices that we need to hear, not mine this time. So Bruno, is the is the embedded mobile and automotive dev room? Is that like running a regular schedule? Like it's not half a day. I was afraid you would ask me this question because I have no idea. So, yeah, I know the same sentence I just said for CICD also makes sense for this room, but as I know, nobody who is ruling, you know, this room, I don't know, and the organizers know what they want to hear. So maybe I just posted the proposal that would be refused. And it's perfectly fine with me. Sorry, Zoma, go ahead. No, no, but can't you submit to both? Of course I can. But I don't think I will. I don't know, but you can still choose which dev room you want to to do your talk. So I will not prepare a talk for. For there, yeah, I'll be busy with the universities, I believe. Yes, and anyway, we have some kind of a booth. So yeah, if we don't give talk, we can be there at the booth speaking with Jenkins enthusiasts, and that will be cool. Right, right. And yes, Jenkins will have a booth. Well, at least we've submitted an application for a booth have yet to be accepted, but we did apply and so for every year we've always had a booth. So hopefully that will happen again. OK, and then scale 20 X Southern California Linux Expo. This is the event that. KK has been going to since my gosh, maybe as long as I've known him and we get this for free because we are open source. So we get a 10 by 10 booth space for free. And last year, Mark and I staffed the booth. We had a speaking slot at the conference as well. And and we plan to do that again this year. And so far, many people come to us and they tell us how much they love Jenkins. So it would only be right that we are there. OK, Bruno, this next one is for you. Yeah, I already told too much, but anyhow. So last week, there was a mobile DevOps summit. A lot of interesting thoughts to hear. I don't know if the videos are up and running yet. I don't know, but mine is screwed up. So we had some technical issues. Unfortunately, so I don't know if it will be available or not. So the next day, I will call it the talk separately in the same condition, except for the technical issues, of course. So I posted it today on my new YouTube channel, which is some kind of parody channel about Jenkins. Parody is not the right term. You will find the right one. It's just that it's not deadly serious. It's just me talking about Jenkins. And as I don't know much yet about Jenkins, it is what it is. And with my bad sense of humor, there you go. Well, thanks for thanks for showing up and thanks for for for doing that. You're welcome. Try trying to have more subscribers than Darren. What a challenge. Yeah, at least I have two to additional points. Yes. Tell me when I can go ahead, you can go ahead. So first point, I'll be working on based on the statistics that I made for October Fest. I will start to build some statistics so that we can see the eventual impact on submissions, PR submissions and contributions, following actions that we organize so that we have something where we can measure the contribution of the ecosystem. So I'm making progress on that and we'll have more. So will you deliver that via blog post on Jenkins.io or how will you at least so publish the raw figures and probably make it available in a form or the other. So either an online meetup, a blog post or something like that. But this is material that we will share with the community. OK, at least with the board first, and then we're going to see the publication is not. I don't have a clear idea how to do that. It's not my focus right now, but it's designed to be published. OK, although in the beginning, there will be a lot of hands digging and a lot of. Ad hoc queries to try to understand fine patterns. I think the blog post will be the. Regular blog post will be the way to go. Still need to think on it. OK, so we do have the September newsletter that we can include in there, too. November newsletter, you scared me. So that that was that was OK. Here, let me first crank out the raw figures. Yep. And then I make these figures talk to me. OK, I will carefully listen to what the figures say, but you know, figures, you can make them tell whatever you want, right? No, I hear I'm collecting data and will will do some some data analysis and try to see what what we can understand. OK, the other point is we have the CDF outreach committee committee restart or where we have a bunch of things that we should or could. Prepare, I think there is a meeting planned for mid December. OK, so that's in four weeks. I need to check. There was a mail. Was that sent out recently, Jean-Marc, or I think. There was a refresh of that mail. So Laurie sent a new mail on November 15th. Oh, OK. An update. And normally. Marc copied you on that mail. So we have and it's December 14th. OK. So they want for that representation of each project so that we're sure to keep the community informed on all the existing things happening in each project, as well as hit the CDF goals and objectives for 2023 and beyond. So there's some preparation to be to be done. There and they would like to have a representative. OK, Jenkins project. So we have our homework to do there. Maybe we'll do an ad hoc meeting with a core group here. And. Yeah, I I plan to be there. Because I've been part of CDF for a while now, so it's not completely new for me. Yeah, you need to be sure that you're reelected, Alyssa. You need to do your your your campaign. I will I will work hard at it. I will I promise. OK. We should all wave our little flags written Alyssa. Alyssa Alyssa for officer. Though they're they're as far as I understood from Kevin, there are no other candidates. But yeah, it'll be a tough fight. It'll be a very tough fight. Yeah, well, with yourself, yeah, indeed. But you're doing a great job with that. And so normally I think we should wait for for this election to be finished. But I think you can bridge the the gap and attend that meeting. We need to review what are the questions that they ask and see that we we don't go right. Yeah, I'll reach out to them and then so that we we have those questions in hand and be prepared for it. Yep. Otherwise, I don't have anything else. OK, no, this is great. Thank you for sharing these items. OK. If there's nothing else, we can call it a day. Thank you, everybody. Have a good evening. Have a good day. OK. Bye bye, everybody. Bye bye.