 Hi, everybody. Welcome to the Jenkins Advocacy and Outreach SIG, today's April 21st. So on the agenda, we have GSOC Update, She Code Africa, if there's any update there, Mark. There is. Great. CVCon Scale 19X and DevOps World. Anything else that we should add to the agenda? We have a new governance board decision on the, so yes, new topic at the very bottom governance decision on Ukraine, on the war in Ukraine and how we express it there. Okay. So yesterday's governance meeting made it came to a decision and we will go ahead and make that so within the next day or two. Okay, and this is the image on Jenkins.io. Absolutely. Right. All right. Okay, so GSOC Update application period ended April 19. We are currently in the mentoring mentor grading period. We're not grading mentors, but we're grading proposals. And that started yesterday. So we're expecting to end that period on, sorry, April 30. I thought I'm in May, April 30. That's where we are at at the moment. Do you have any questions there for me, Mark? Well, I've got I've got to do the grading. So I'm one of the graders right who's who's reviewing the proposals. We did actually have I guess I've got a separate topic there for you. Raj joined the GSOC office hours earlier today, Europe time, and had a question about eligibility, a question about eligibility that I think is best handled by him having a discussion with the with the org admins. So you and Chris Stern and John Mark Mason. And just be aware that he's got a question. And I said, yeah, we really he can't we can't give him an answer until next week because John Mark said a conference this week and unavailable. So he's okay waiting. He has no problem waiting he understands that he just wants to be sure that he has a chance to talk with the three of you about it and understand your opinion and how you feel. Okay, I appreciate his excitement and all right so we'll see. Great. Okay, so she code Africa contributon. Yeah, so we are, we've completed the community bonding period. We are now in the project. So we're we completed the two weeks of community bonding. We're in the four week period of doing the actual work. And, and we're trying to help these new contributors get started get involved. The community bonding didn't go quite as fast as I think I would have liked. Meaning meaning we didn't get as much done during community bonding as I would have liked part of that as we just didn't have enough mentors. Part of it was I didn't schedule enough meetings during community bonding to assure that they would get started and be motivated to report in every day or every other day. So for next year will probably do community bonding meetings, every two or three days. It was it's a little slower start than, than we had last year and, and the last year it was a super fast start because we had no community bonding period whatsoever. And so we had to be very, very fast to get started. And this year we thought oh the community bonding will make it easier but as it turns out. It wasn't as easy as I might have hoped. There are three projects running the three projects that are running our pipeline help. Pipeline help is something like last year's project. So pipeline help is one screenshot updates is the other. And this one is because Jenkins UI has been through major changes in the last several releases and is still going through some really exciting changes. We need to update the screenshots on Jenkins.io. And then the third project is. Put your pipeline help screenshot update and I should remember. I get. That's that's okay I'm sure I can add it later. I have it down here. I've got it absolutely in all my notes. It's lots of places just a minute. I just have to look really quite carefully. It's an old age thing sorry about that. So pipeline help screenshot updates and inclusive naming of course. Yes, right. Talk about embarrassing to so and the inclusive naming one and so inclusive naming. That's getting rid of the potentially offensive verbiage in Jenkins documentation and online help words like master and slave and whitelist and blacklist that the project has decided need to be replaced by more inclusive terms like controller and agent. So we've got those three projects and I'm actually excited about all three of them I think we've got potential to get benefit from all of them, and these contributors in Africa are certainly getting introduced to open source as part of it. Excellent. Yeah, we can definitely use to help in, in all of those areas. And that's it for me on she code Africa contributes on. Okay, thank you mark. So with regards to CD con so the contributor summits, the Jenkins contributor summit is now on their website on CDS website. We are confirmed for Thursday, June 9 from 9am to 5pm. There is a fee, as I mentioned, previously $15 I did bring this up with CDF, and they said that the reason for this was to, to, to discourage the no shows. And that makes sense that's so it's a token fee it's very, very inexpensive it's well below the cost of running the event. It's just by paying a little bit we persuade them I should be there. Right. And if we do get a lot of pushback within the community about this, and we can definitely address this with CDF there. They're totally right. Great. I am awaiting for them to confirm about whether contributors summit attendees needs to pay for the main conference. As well. So I'm waiting to hear back from them on that aspect. However, I have started a planning document. And it's very, it's very, very draft in draft mode right now I mean very beginning. I'm filling it up as I get more information but I think what we can do is what I plan to do is go back and see what we've done in last year's contributors summit we typically have project updates or from like event security, things like that so we'll start that, and then we will open it up to, you know, breakout sessions and such, but I will initiate the discussion on this course on our community page, and open this up for input and ideas and suggestions. Excellent. Yeah, and, and there's if you look on Jenkins that I owe you'll find, you should find links to the past contributor summit agendas. So we absolutely do want to project update section locally presented so we know it will include documentation and platform because I'll be there. It'll include events because you'll be there. And then others, we may we may choose to act as proxies for others depending on who's there for instance, if Tim Jacome is able to attend we may ask for a report from the release officer. Yeah. Great. I will get those added. Okay, so that's it for the Jenkins contributors summit on CD con at CD con. And then the next item is scale so that is slated for end of July, we're they're moving the event from Pasadena to LA. I'm not too excited about that because traffic in LA is horrific. I am waiting for the organizers to confirm our exhibit table. Things has changed since they have moved location in Pasadena it was easy for us to get table. So now this this event is taking place inside a hotel. I'm thinking that might cost a lot more money. Okay, so and, and that I assume they'll tell us right what they're doing how that's working and they'll guide us on. Hey, we can you have to do this or not do that, etc. Okay, right. So we'll probably, we will forgo the pipeline training at scale this year mark, because I'm not sure about the attendance level. So let's, let's just have a presence there via and a table. And I also saw that Kosuke is going to be speaking at the conference as well. So that would be nice to catch up with them. That will be great. Yeah. Yeah. DevOps world. So the event CFP is open and the submission will stay open until May 12. And for for Jenkins at DevOps world is that we will do the, the, the things that we've done in the past with regards to in person events at DevOps world so we will have a an all day contributor summit before the main conference we will have a contributor appreciation event in the evening. We will have our usual booth space with ask the experts and lightning talks at the booth. Yeah, and then many men were expecting a lot of Jenkins talks at at the conference this year as well. So that's the plan and that is taking place in Orlando, Florida. What else and then I will start a discussion on this in our community channel as well governance decision on the Ukraine image on Jenkins.io mark. Yeah, so we discussed it yesterday we had three of the five board members in attendance, and after a two week, an over two week voting period. The voting was slightly in favor of the, the Jenkins image with the open eyes and the flag stop the war rather than the Cossack image. We're going to go ahead and merge that one. I admit it was only slightly in favor but it was slightly in favor. There were a few more votes for the Jenkins image then for the Cossack image. Okay. And so my sense was, it's better that we get the message there stop the war, then it is that we worry about whether or not it's a Cossack image or, or the butler. I agree. So I've taken that as yes and what I'll probably do is mark John is adjust the setting on John Marks. John Marks pull request so that it's no longer draft close one of the one that's the Cossack image, and ask, I think I want to ask Cassania if we can use insert her Cossack image into the artwork collection. I don't want to lose the image because I think the image is a wonderful piece of work. It's just not the one that we're ready to do yet. Okay, I can take them the action item to reach out to her on that. Oh that would be great. You'd be willing to do that. Oh yes, that would be a great help. Okay. Alrighty. That's it. That's all that I had. Thanks Alyssa. Thank you. Bye. Bye. Oh, Bruno wait a second Bruno. Oh, very nice you are here. Should we stop the recording Mark? No. We are welcome to stop the recording or just have Bruno introduce himself live on the recording. Oh really? Bruno, do you want to be recorded as you introduce yourselves or do you want to wait until later? Oh maybe do it later if you don't mind. I even don't have my camera on icon. Get into work today with zoom.