 Thank you for joining the Jenkins Advocacy and Outreach SIG. Today is Thursday, June 1st. I can't believe June is here. So on the agenda, I have a quick four items that I wanted to share. I wanted to go over the May newsletter, GSOC update, DevOps World Tour dates, and CDF Outreach Committee meeting that they are scheduling for June 21st. And they're looking for our input and I'm sharing, being trying to be transparent and share what I have here with you all. So is there anything else that I should ask to the agenda? That's good. I'm seeing shakes. I do have a question though. Should we include like other plans for the upcoming LTS or weekly release Twitter announcements? Because we do have plans for it to be done consistently from now on. So you're, okay, so I want to make sure I understand. So it's the LTS tweets you're referring to. Yeah, currently we only have LTS, but will it be permanent or is it, is it for every release or is it just for like the major ones? The point one release. I think that would be a mark question. Yeah, I don't have an answer to that, Chris. Okay. So normally like, I don't do the point one release. I have up with the other ones, but so normally Alice does like all the point one release these days. And I do the West sometimes, sometimes the volunteers to do like some of the like non point one releases to you. But when it's my turn, I don't normally like request for a trade for the releases. So should we make it like a pattern from now on, every LTS release, we should make a trade if that makes sense. Yeah. My point of view is the question makes 100% sense. Yeah. It would avoid wasting time to reinvent the wheel each time. Now the answer as for for Alyssa to what would be the correct method. Yeah. For that. This I don't know. So we should ask where Alex and Mark was there, but describing the process. Communication part would be very wise. I think it Chris, I think my, so my gut feelings telling me that might be worth a discussion on the, the Gitter channel. So that you get other folks in their feedback too, because I don't think the right folks are in this channel at the moment. Okay. I'll try to talk to them tonight because I know they have a meeting tonight. Yeah. Yeah. And then if there's additional action items that, that needs to be taken from that. And then I mean, we can, we can. I'm back here if needed. But we, I think we need a broader input from others. Okay. Yeah. But I think that's an excellent point you brought up though. Okay. Okay, so the Jenkins newsletter for May, it's currently in motion. So I spent a lot of time on that yesterday Bruno. So we got most of it. I think, well, where is it? It's somewhere. Yeah, we've got. I think we got our input a couple of, we just need a couple more input. So it's mainly Mark and I don't think we're going to get documentation from Kevin. Kevin. Yeah, but maybe Mark might have something that he can put in here. But I will chase with Mark to get this. Together and or his input in and then hopefully we can push it out next week. Cool. Thank you. Thank you. Um, GSOC update. John Mark, I, if it's okay, I can leave it up to you for this update. Yeah, no problem. So we ended. One week ago, we ended the bonding period. Went very well, quite active. Some late starts because of exams that needed to be done, but all the objectives are achieved and since a week. All the project teams are working and start moving. Facing the first problems and solving them. So it moves, moves ahead very well. The four as part of the deliverables of the bonding period, there was a blog post, a presentation blog post that was done and published went well to and we have the weekly office hour going on and where status is exchanged, so through the status we pick up useful experiences that are then shared with the rest of the team. So currently all lights green, everything's going well. And the fun factor is high. My update. Thank you. I don't write that fun factor. That's good stuff. It's good. Oh, I saw good smiles on people's face. So yeah, good sign. Yeah, I know. I think it's a good point to include. And I think can I add something? Yeah, because I just want to add like the contributors this year is super active during the office hours. So it's a good sign. Yeah, they're all present and make an effort to be present. So that's a good point. Yes. Okay. Thank you. DevOps world tour 2023 so now we can officially say that there are dates and locations. So I put on the link here. They've announced locations for Chicago, Silicon Valley and London. There's two more that is to be announced. So if you're interested, check it out. We do have one session for Jenkins at each location. They are pulling together the agenda. They're still reaching out to speakers. So the agenda is not yet up. But Mark is, is slated to speak at least in the US. And then Tim Jacob is going to be speaking in London. So that's a really good sign. And then as I mentioned earlier, a CDF outreach committee is having their monthly meeting. And this next one is in on June 21st. Each project members are supposed to provide their project updates. And what I have listed here is what I will be including for. For the Jenkins project. And thanks to John Mark for adding your input here. But I will list out our number of LinkedIn members, Twitter followers or contributor numbers or installs or plugins, because those are quite, they're quite impressive numbers to share. And then the things that we want to highlight with other members or project members and the CDF community is that we are, there's work within the project that is towards rejuvenating the mature code base. Modernizing UI UX. And our impressive seventh year in GSOC. And then lastly, our newsletter. And I think that I wanted to highlight the newsletters because just so that people can, in case they want to know what's happening. But I think that within the project on a monthly basis, they can just go through here. That's it. Any questions? I hope the words, the choice of word of mature. It's not like to hurt anybody. But here it's the word is cracked. Yeah, because of the experience. The experience has also the weight of the years and the joints or, or the muscles maybe lack the power of a younger code base. So mature is for me the good word. I like it. I will not hurt anybody with it. No, I think, I think it's a good word to use. Better than old. Right. I like the word. Good. Okay. All right, I think that's it. Thank you everybody. Okay, thank you. Enjoy your night, enjoy your evening. Thanks. Bye.