 I think it's ready to roll. Yeah. All right. Hi, everybody. Thank you and welcome to Jenkins advocacy and outreach SIG. Today is Thursday, November the third 2022. On the agenda, I have Hacktoberfest. So probably this is going to be the last update from John Mark for for Hacktoberfest for this year. And then I have the October newsletter on the agenda. GSOC 2023 already. Jenkins election. So, Kevin, if you want to talk about that later, and then I have FOSTA and the contributor summit. Is there anything else that I should add. CDF news. Okay. Or CDF. It's more a question because there were some requests there during the months of October. We'll discuss about that when we reach that point. Yeah, and maybe I should miss plug about me giving a talk next week on Jenkins at DevOps Mobile. It's advocacy. Yep. Bruno, if you have a link to that, you can add it. Oh, yeah. Okay. Okay, so October fast John Mark, I will hand it over to you. I make it short because I have the impression that I keep repeating myself on all the various channels. This is an important channel here so participation was really good this year. And we were able to reach out to very experienced people but also to first time contributors all over the globe so that was really a great event. We ended up with having 95 contributors completing over 500 PRs that are October fast completes a very good participation to them. Kevin and myself are going to write a blog post about the facts, but also the stories behind this year's October fast. I had very interesting discussions with various participants with various experience with with the Jenkins project so what were the motivations what was their advice to new contributors and so on so This is what I can say in a couple of minutes about October fast. Okay, I think it's great we've captured. I basically copy and paste your update for the newsletter here so we've got the stats here so I think that's perfect. The little footnote so the one under so you can either remove that or it's a link to the small tool that I used to compute the figures so I can give you the URL. Okay. So, I was not able to remove. I'm not able to remove this right now. Then remove the one just behind strong above higher. First line of the pattern. Right. Yeah. Okay. Right here. Just delete the one. We go. Thank you. Okay. Moving on. The October newsletter draft is ready for pull request. Thank you Bruno I so I haven't checked I've been in meetings since this morning so I haven't checked status on that but since our conversation last night or yesterday Bruno. I just put it here. So hopefully that's okay. Thank you as a preview feature is off for the time being so I can see how it looks for everybody but the PR is done I have to get it reviewed by tonight. So we'll see hopefully it will be published tomorrow morning at worst. Okay. Perfect. That's great timing. And then a per Gavin's mogans suggestion that we should start making the draft public and allowing people to add comments or input for the next newsletter. So I will be creating a form for that and I will be sharing the draft via community dot Jenkins.io. So that will be for the November newsletter. Okay. And then for GSoc 2023. I've already started the discussion on community dot Jenkins.io. So basically the usual stuff. We need volunteers as mentors as org admins and project ideas. So. Thank you, Jean Mark and Chris Stern who has volunteered to come back as work admin so I will be or admin as well. So I'll be reaching out to individuals to get volunteers as mentors and project ideas. But if you have any suggestions please add your comments to the discussion on discourse. Kevin, do you want to go over the election portion. Yeah, sure thing Alyssa. So, first things first we published a blog post on the 20th, explaining that the elections are open voter registration nominations are open. There was a tweet and post on the morning of the 25th to share all that with everyone. We are currently at 17. Folks in the voter registration group so we're hoping that we can signal boost this in some way shape or form. Mark mentioned we're going to send out some more emails and stuff for users, but we have a ton of newer users. With the fact that we know how many new users or newer users there have been in the voter numbers, much further away from that. So we want to try and make sure that that's getting recognized or at least highlighted for folks. Yeah, Kevin maybe something to mention in the communication we do that if we're participated to elections the previous years we have to register again. Yes, that's actually a good point Mark I have. I hadn't thought about it since I was in here last year, but that's a good call because it is two different groups. Yep, for voter registration that's absolutely right. So thank you for calling. And then, let's see, Mark, I think has plans and ideas for who are going to be candidates for at least four of the positions officer positions. And then the voting and voting registrations open until November 17. The nomination period is open till November 10. So that's coming up a lot sooner. And then the voting is going to run from November 17 when voting registration closes. That's also going to be the day we announce candidates share their statements and basically set everything up for the actual voting. And then December 2nd is the last day of the current term. So December 3rd, the new folks will step into their roles. But we may have a little runoff after the fact due to the time frames this year. And so we might just announce them a little bit later than usual. Typically it's around the third or fourth and might be a little later this year. But yeah, I'm going for the documentation officer role. And Alyssa has noted that she's going for the events officer role. And I am not 100% sure on what everyone else is doing, but at the very least we do plan to have some representation or at least try to. So all in all, it's going really well. We just need to get a little bit more communication if possible around the election. And yeah, I'm more than happy to help creating any communications or anything like that. I'm just not as well versed in how to get that to people. So I'm more than happy to collaborate and connect with anyone. Alyssa, John Mark, if anyone can help me, maybe get some ideas going or, or yeah, like I said, boost that, that'd be great. So Kevin, have we sent out an email to the mailing list like the users and the developer mailing list. So that I don't know for sure Alyssa I can definitely check in with Mark later this afternoon when we have some time because I know he had mentioned that just a few moments ago that the plan is to send more notifications out and emails and stuff. But I just I just don't know the back and work of that and what needs to be done for that so yeah. Yeah, I can work with you on that I can also check I had like as I haven't been on email this morning so I can definitely check and then I'll work with you on that as well. Perfect. And for community dot Jenkins dot IO. Do we send a communication there. Like posting a thread. Yeah, I want to say Damien actually created a thread for it. He said, yeah, I'm pretty positive Damien actually created a product community already for it. A little check though and make sure. All right. Yeah, if it's not there then we can that's another place for us to put as well. And then I'm looking at the date so I think once we get closer to like the deadline of the nomination that we can send out another tweet and do another LinkedIn. Same thing for the voter registration. Yeah, just to signal the end of one period but you know, still showing that there's still events happening and you still register and all that stuff. Right. So I'll put those states on my calendar and to remind me to send out tweets so I'll be sending out proposals. Okay, great. Thank you very much. Thank you for that. Thank you. Foster so we know the date and I think I believe the organizers are still playing with with whether that the event is going to be in person or online at the moment. I. I got a message last night and he says that hopefully we'll see you in Belgium, you know, if it's an in person event, but I did submit a an application for our stand. And Bruno, I put you as a secondary person I hope that's okay I needed to come up with somebody. That's perfectly okay and I received the email from for them saying that they were still reviewing your proposal to have a stand at first time yeah. Okay, so our stand is there. So I think that the call for participation for speakers is going to be November 5. I looked around on their website yesterday and I couldn't really find a link to where we can make submissions for our talks. I'm thinking that's probably not yet available but once I have that I will definitely share it with the team, so that we can submit our speaking opportunities at in the CI CD deaf room. Okay. Anything else that we need to share for foster before I move on. Then the contributor summits, we have notes here on the context of it what we want to do, but I just haven't come around to it because it's here and and I've been working on budgeting numbers. So, we need to talk about that and November I can't believe like the holidays it's just around the corner so. So we need to come up with a date and time for this quickly so I will be working on that. Okay, so we need to come up with a date and time for the CDF news. So, John, you just showed what we discussed. Yeah, last week about that. Yes, weren't there. Yep. So, so there was a request for I didn't follow it closely so I need to remember but it was a request from CDF to have the confirmation of the official. The representative for the CDF advocacy and outreach SIG. Yeah. So I've seen some mail pass. And I think the position from the people that were involved in that discussion was okay we'll we'll wait and see for the results of the November elections. The Jenkins November elections. I see. Okay. Yeah, I don't see. I don't mind joining. I don't mind joining their, their meetings or being on their committee, because I've done that in the past so. But, you know, there's always room for more than one of us to be there. So, but at least there's always one person covering. Yeah. So we need, we need to follow that. It's important that we keep the connection with the CDF. Yeah, good quality connection. John, Mark, can you forward that communication to me. Now you're scaring me. Oh, I don't remember seeing it. I need to dig it will not be today. So I think about that. I don't remember. Yeah, don't worry. I can also reach out directly to CDF as well. Yeah, let me do that instead. Yeah, we can we can listen. We can listen to that. I'll dig my end of October was a little bit hectic. Yeah. Yeah. Okay. Okay, we got Bruno your talk here thank you for adding that. Should I add this to our Jenkins calendar? I think we should. It's not to master class, you know, it's just 25 minutes of me speaking of Jenkins and Android my discoveries because I was a Jenkins newbie a few months ago. I still, I still am, but I was a total newbie a few months ago. So that just my path my journey with Jenkins. So if you're an experienced Jenkins user, don't come to this session. If you want to know more about mobile CI CD within Jenkins. Yes, you can come and you'll be welcome. And this is going to be in person. Unfortunately, no, that's why I say everybody can come except the Jenkins experts. It's online summit, you know, because we then everything so. Okay. Last topic. Yes. Let me go back to my okay with that. Yeah. Sure. When marking you were on holiday. There were some questions about accessing the Twitter account. So we need to review the, the access to the Twitter account how we do it. How is the access shared and there were some good ideas flying around that need to be investigated. If we could automate this so that we have an audit trail. And do some, some technical voodoo. It's going to make your life more difficult. No, maybe not. I think gave him proposed to make something around the GitHub action. So as I become an official reviewer of the pull request corresponding to an upcoming tweet. Yeah, it will, it would work that way. Yeah. I don't want to scare Lisa, but. Only two weeks of training and you'll be ready to go. No, 10 minutes will be sufficient. Don't, don't be afraid. I didn't want to, to, to scare you a listen and we'll be there to help. I was enjoying what we have right now. Yeah, but then we, then we need to tell you that you're not able to go on holiday anymore. Especially together with Mark. So we ran into an issue. But this doesn't happen that often. Yeah. So there's no urgency, but I like the idea from, from Gavin. And it can be done in such a way that we say, well, this is a pool of people that can submit a tweet. There's no process of that. And there's no need to have the password for the Twitter account. So it would work that way. We can make it in a user friendly way. Be helpful. So, so that means that so even people who currently do not have access to the Twitter account are able to submit proposals for tweets. Is that how? Yeah, so it, it will be that either everybody or a group of people can propose a tweet. And then there is a dedicated group of people that are allowed to approve it. And instead of asking on, on the Gitter channel, put someone up vote. The send that we have a more formal process for that and supported by technology. Okay. For that. So, but here there is no hurry for that. It's only something we need to investigate, but because I think it will happen again. Let's, let's be prepared and have a playbook for that. Yeah. If somebody wants to tweet during Thanksgiving, we are doomed. So that means that somebody has to approve it, right? So there's going to be another person that has to approve it. Yes. And we can't set a rule that two people from that, that group need to review it and approve it. And when this is done, then it's fired. Okay. Here we can describe that because this is what I understood from the conversation with Gavin. And let's not forget to work on that. Okay. When do we want to work on that and we are going to set to set that in the priority list. I think they're more urgent things to do right now. Okay. My fear is that we forget it. So this is why we should put it on the to do list. On the top, but on the to do list. Okay. And the intention was not to scare you. Can you help me? I will. We need to design a system that you can do it alone. Yeah, I think if I do it often enough, it should be okay. Yeah, the rule is once you have done it 21 times, then you'll know it this is this is the rule when training kids and dogs. Yes, practice makes perfect. Right. That's right. Okay. I fear I'll rune. Yeah, you're making me a bit nervous, but I'll, I'll, I'll grow up. I'll grow up. I promise I will grow up. I'll get with it. Before we leave, you will be able to do a full Jenkins IO pull request. I'm not leaving before. Okay. A year and a half, a year and a half. And, and I will not leave before you can, you can do that. Okay. All right. So I'll update this after the meeting. Mark, we're actually ending. We're pretty much done with all of our topics. Anything that you thank you I just needed to drop in and see how we're doing an election promotion. That was the thing it looks like you've got the topic already so I'll read the notes. Okay. Yeah, need to work on the communication channels but we can discuss that offline. Yeah, so I'll work with Kevin to see whether that there were communication sent out to our mailing list so we'll do that. And then also on discourse. Great. Thank you. I think that's something that I think I spotted is that you need to re register. Even if you voted already last year, it's implicit. But I didn't hear it in the communication up to now. Yeah, so we'll emphasize that in our communication. I'll update the blog post to include that information as well. And I also went and updated the Jenkins.io election process page that just kind of houses the general election information so I can also put that there if it's not already called out there as well. Awesome. Thanks Kevin. Okay. That's it. We're good. I can close the recording. Yes, please. Thank you.