 now. Okay, can you see my screen still? Yes. Good. All right. Hi, everybody. This is Jenkins Advocacy and Outreach SIG. Today is May 19. And on the agenda, I have GSOC update, Shikot Africa update, CDCon, brief, blurb about DevOps worlds, and the next Jenkins online meetup. Anything else that we should add? Nope. Nothing to add to the agenda. Great. Alrighty. So GSOC update project announced to orgs is today in a couple of hours. So we're very excited about that. Accepted projects will be announced publicly tomorrow at 11am pacific time. As org admins are quite busy. Thank you, Jean-Marc and Chris for driving the efforts for the preparations for the upcoming milestones. We what we're planning to do is welcome the new accepted contributors, and then talk about having a meeting to to go over the bonding period, what needs to be covered, et cetera. The goal is to make life easy for everybody and to make sure that we check off all the boxes that needs to be covered. And also to share with them that we're going to be around and available to help in any ways possible. Anything else you'd like to add, Jean-Marc? No, I'm preparing a mail that I'd like to discuss with the group here and others. I'd like to reach out to the candidates that submitted a proposal so that they don't abandon and give them some recommendations how to get prepared for a more successful trial for another GSOC. Some recommendation. It's nearly done, but I want to have to verify that the tone is correct. But I think it's worthwhile to extend the hand to them that they don't fall in the bitter cold and darkness of not being selected because they made important work. And I think that's a great pattern, Jean-Marc. It was certainly positive in years past when Oleg as an org admin would send a specific note to each person who can, well, each what I'd call each viable proposal that was received. I don't think we have to respond to the spammers, but the viable ones, it's good for us to answer them and say, hey, thank you. This would solve a doubt I had. But I will do that effort. I discussed it earlier during the office hour with Bruno and Chris. I can add to that a personal note. Great. Here, I'm still preparing the communication. I expect to send that on Monday so that we can rest out. Thank you for your advice, Marc. Okay. For She-Code Africa, Marc, I know that the program is ending as we are approaching end of May. So what I have here is you're in the final reporting phase. And I also saw a couple of reportings on discourse by the contributors. Right. Yeah. So we've got, we just had another session with the Pipeline Health Project, or we had a session with the Pipeline Health Project and reminded those two contributors, they need to submit their final report to community.jankins.io as well. That is so much easier to submit a page to community.jankins.io to modify it to edit it than it is to submit a blog post to jankins.io that we want to encourage them to use community. It fits with what Gavin Mogan has asked for from the governance board. Hey, let's centralize more and more of our communication on community.jankins.io. And it makes it easy for them and very approachable. We had the benefit that one of our earlier submitters, Peace Okafor, had done a really good job of writing her report and we can just encourage others. Hey, use that as a template. Yeah, I agree. I think I have it here. Did a great job. And I'm sure the ease of putting this in this course is much better than the jankins.io blog. Yeah. Yeah, she did a wonderful job. Well, here she here, she described some of the real problems, right? She's not she's not hiding the fact that we made mistakes this year again. And there are some mistakes that we should we really can correct. There are things that we can do to make the startup easier when she lists her challenges that she faced. Those are those are things we could avoid in next year's program. So I think it was a good thing for her. Very grateful she did it. Yeah. All right, thank you for that. So for CD con, we are still we're we're we're making arrangements to go to Austin, Texas in June. And I have swags, I have cable bags, and I've got Jenkins stickers ready to go. So Bruno and I, we will start working on the slide deck for it, Mark, and we'll share it with you and Tim Jacome, just so that we have everybody's slide content in one place, just that we can move along smoothly. What else, what else? Yes, and CDF did post the announcement of the Contributor Summit on Austin meetup page as well. Anything there, Bruno or Mark? Not on my side. Thank you. Nothing else from me. Thanks, though. I have a point on the previous item. So either I keep it for the end or I just throw it now. Oh, let's talk about it now. Yeah, very quickly. Mark, as you were leading the effort, or maybe Bruno that helped there, do we plan to do some kind of document to get prepared? For next years, some kind of guidebook or checklist for preparation, as it currently exists for Google Summer of Code, the Run Book. Oh, so for Sheikot Africa, is that your question? Yes. Yes, good point. Yes. Do we plan to do that? Yes. That's fresh. That's part of the that's part of the wrap up process. I'll actually schedule, I did it, I did it last year, and I'll schedule it again this year. We'll schedule a retrospective session with the participants. Invite them to join us and then use that to generate something that will go into the Jenkins.io site, describing the the things that we learned and how we would do things differently next year. And typically what it'll be is the page that describes Sheikot Africa will include a link to another page that says, here's how we do Sheikot Africa I can forgive that. Yeah, some kind of a manual if another person needs to start it, right, that this person has the recipe to, to start and be successful on that. Yeah, maybe we could give links to one of the, to several of the best recordings you made Mark and that are on YouTube. You know, the one regarding Git, for example, the way to work with GitHub and so on, because I learned a lot of these and I think the ladies learned a ton of things too in these sessions. Well, I'd like to reuse. Yeah, sorry. Go ahead, John Mark. I'd like to reuse this kind of material that was this morning a question from somebody who was wanting to contribute to Jenkins and was starting very low. So obviously he was missing some, some basic skills, no judgment there. But these kind of videos, having them handy for these kind of public. And Mark, you also have a list of videos you made with daring about contributing to open source project, I think, but are really, really relevant and helpful. Yeah, right. So, so maybe what we want. Well, I guess there are two parts there, right? One is on the Sheikot Africa page for Jenkins.io, we should probably embed that Git, that Git intro video, just because it's something that many people who want to be involved in Sheikot Africa need this skill, right? We and, and we could embed it there easily. Then we ought to finish the, the contributing to Jenkins tutorial sequence that I've got in a pending pull request right now to Jenkins.io. That that thing is, well, there's a 27 page Google document that backs it. And we need to just get it all the way so people can use it, right? Right now, it's, it's no value because it's not merged. So yeah, those are both, both very good topics. Great suggestions. Moving on to DevOps world. The CFP is closing in about six days, May 25. We currently have about 13 submissions under the community track. So we definitely need more. I think the whole conference, the whole CFP is receiving slightly lower than usual submissions. And I'm thinking it's due to COVID, because people aren't sure whether that they're, they can make it in person. So it's making things a little bit harder. Well, and I haven't submitted my, my proposals yet. So shame on me. No worries. You got six days, Mark. We know how you function. Yes, right. Manage, personal schedule management by Cliff. All right. I understand. Well, yeah. Stopwatch submitting. Yeah, right. Shame on, shame on me. Exactly. And then the last item I have is the Jenkins online meetup. So I will, my focus right now is mainly on the next thing that's coming up. So mainly the, the contributor summit, just to make sure that we got everything we're aligned in such Google summer of code. And then the Jenkins online meetup that we have there bisecting with Basel and Mark. So I'll reach out and I'll schedule something for us. That's all I have. Excellent. Good. So and on the Basel topic, I haven't discussed that title with him. So he may absolutely reject that topic and say, I'm not a surgeon. We're not going to talk about this. Okay, but, but by all means, we have the discussion with him to see what works. I don't know what the word means. So I know what's behind forget, but does it have a meaning in English? I'm going to research that. Yeah, possibly inferred meaning, not a direct meaning as any, but the sectioning is sectioning is a surgical technique that you slice things to see what's in them, etc. Okay, I'll look in the dictionary what's behind it. So dissecting. Yeah, okay. I think I see what's behind. Okay. I thought it was crossing roads and trying to wait, which is also is the geometric precise definition of bisect. Absolutely. That is the precise geometric definition of bisect. Yep. Okay, can stop the recording triggered my curiosity. Curiosity is always