 Go to the cloud. It is recording now. And I'm sharing my screen. Can you see my screen? Yes. All right. Welcome to the Advocacy and Outreach Special Interest Group. It's Friday. No, it's not. It's February. February 24, 2022. The agenda topics for today include review the outreach program's webpage. Remove Jenkins is the way from the Jumbotron. Yesterday, we'll go over yesterday's Jenkins online meetup and GSOC, GSOC Next Deliverables, CDCon, Shikode Africa, and March Jenkins online meetup. Are there any things that we could we put an additional topic on after remove Jenkins is the way on Jumbotron? Could we also put one Jenkins is the way on Jenkins is the way site URL, et cetera, or site hosting and URL? Got it. Got it. Thanks. All right. All right. So Jean-Marc, this one, this item is yours. Do we have status on this one? Or what are you planning? No, I didn't work on it. So we discuss it. I had the information last time, but I didn't work on it. OK. So I'll just leave it on there for next time. Yes, because either we review the pull request together the next meeting. OK. But this needs to be done. And Jean-Marc, it's just a pull request. So you've submitted the change as a pull request to Jenkins.io. Yes, this is the way to do it, but we can look together at the preview, which is a way to review it together here, just proposing. The updates will be quite simple. Great. So you can put there. I'll update the meeting minutes after the meeting. Taking notes here. Good. This is how I roll. All right. So remove Jenkins is the way on the Jumbotron. I think we can remove it, because the program isn't we're not doing anything with it. We're not writing stories anymore. So it might be worthwhile to, I think, remove this and then when we do get accepted for GSOC or if you think that we should put the GSOC program on here now, we can do that. Yeah, actually, I think there are two things we have to put on there now is CDCon 2022. And GSOC both would go on here. And this is a great excuse to take Jenkins is the way off for the moment. Yeah. OK. And who can do that, Mark? John Mark or I can do it. I'm confident. John Mark, you willing to pair with me tomorrow on it? Yes. Yes, I'm interested to learn. Yeah, Jumbotron edits are a good thing to explore together. This is it's a little different than the relatively straightforward, how do you do the ADOC changes? OK. You ping me for the pairing? I will. Yes. OK. Got it. Thank you. All right. So Jenkins is the way site hosting and URL. Yes. So here just I we had a conversation with Gavin Mogan and well, we had Gavin that was kind enough and willing to take the WordPress site that is Jenkins is the way. Jenkins Jenkins is the way.io and has converted it to be a site that can be managed as code from a GitHub repository. And that's really nice. However, we also need to change. We don't want to lose the content that's on Jenkins is the way.io. And so his initial thing that he did at my request was what would it take to put it inside www.jenkins.io? And so he did that. But it's large. It roughly doubles the size of the Git repository. And it will be relatively low change volume. So for me, it was like, oh, maybe that doesn't make sense to put it right inside www.jenkins.io. So the counter proposal was what if we create a site at the top level? Jenkins is the way dot Jenkins.io. And put the content there. Gavin said, hey, if we do that, we could host that top level thing at Netlify. Or Damian suggested, ultimately, GitHub pages. So we don't even have to do the infrastructure or the bandwidth to host the page. And it still is inside the Jenkins.io domain. So for me, it was like, that's brilliant. I'm working with infrastructure. I'll make a proposal to the infra team to discuss this, to find a way to do it. But I think Gavin was willing to put it on a separate location and a separate GitHub repository. And then when we have new user stories, we can put them there. We'll just put them there with pull requests. Instead of doing the technique we've used in the past of taking things from a Google Form, people have to submit a pull request to share their story. So Alyssa, would you be OK with that? And John Mark, does that sound reasonable to you? Yeah, I'm goal. Yeah. OK, great. So I'll continue with that. And if we just make note that, hey, the idea is we'll work with the infra team and get their agreement that it's OK that we do it that way and coordinate with Gavin. How do we get the separate repository? How do we publish it? We'll probably then want a blog post that announces it. Hey, it's now here. And highlight this is if you'd like to submit more stories. This is how you do it. We're not any longer. I suspect able to send swag anymore. So given that they can submit their story, though, they still have their story visible on the site. Yeah. And Mark, I mean, we can do this swag. If OK, I mean, I think that was kind of like the encouragement. So I want to keep that going if we can. But we probably won't get it at the volume that we've had in the past. Certainly, because we don't have an active organization that's promoting it and seeking people, right? So we expect the number of arriving stories to decrease. Yeah. Yeah. And I'm totally OK. We get a story once in a while just to keep our database up to date. Right. Yeah. Awesome. Thank you so much for your work on that. Thanks. OK. So next item is the Jenkins online meetup that we had yesterday for GSOC. The recording is there. The slides are there. I posted them on the meetup page as well as on the GSOC Gitter site as well. Mark, you mentioned that was it this time that we had more participants and on the. It wasn't. It wasn't more participants. We had far more questions that I remember previously. I think we had an active participant group that we had running about 20 participants. And I think in past presentations, we've had as many as 50. So we weren't as many as many in total count participants. But that was more questions than I remember getting in past webinars about GSOC. So again, that's not that's not captured data as much as just my recollection. I felt like it went very well. Thanks very much to both of you for doing it. Yeah. Thank you. It was it was fun. Yeah. Yeah, I thought it was good. I think we covered. I think we covered all of our bases pretty much. And I mean, if they didn't get get what they need here, there's always office hours, recordings. There's, you know, there's just lots of discussions going on. So I think it's good. What a great story about the worldwide present presenter community that we had there. Let's see. So we had Chris Stern from Hong Kong, John Mark from Belgium, Alyssa from California, Kristen from North Carolina. So so we had we had a great mix. Yeah, well done. Awesome. All right, so moving on to the next item, so which is GSOC next deliverables. I listed down here some of the things that is for at least this is for me to keep my eyes and ears open on. And so the mentoring organization application submitted prior to deadline. So we've completed that. Mark, seven lists of accepted mentoring organizations published. So that's coming up soon. March, seven to April, third potential GSOC contributors discuss application ideas with the mentoring organizations. So Mark, in the past, has this been like a busy period so that Jean-Marc and I can really keep our eyes open on Gitter for? Yes, yeah, so so those those discussions, we that's that's the that is sort of the hot time. Yes, I see. And that's where that's also a place where it's crucial that we if we have additional mentors that we want to recruit, we need them recruited so that we can get get have them as part of the evaluation of the application of the proposals when the proposals are submitted to Google. Right, Mark related to that. There was a discussion point during my office hour. First question was when will the the approval of projects, you know, for having them on the top top level status, don't remember the exact name of the status. So is there a deadline where we're going to say, OK, these are the accepted projects? Well, I think it's not ongoing one. It is ongoing, right? That's that's certainly there will be. There's a point where a project idea moving from in this under discussion to draft may not be interesting to to most of the most of the candidates, right? Or from draft to accepted. It's it's not. But that just continues, right? We can we can move those any time. Those ideas we I think we highlighted really well to them in the online meetup yesterday that they are welcome to do any idea they would like, right? These are just ideas that we've vetted that we think are interesting that they might consider. Right, OK, so I'll be more. Active in promoting so so there's because what I want to avoid is that people have a false message and say, but this this is interesting. But as it's still under discussion, I don't dare. A present. Oh, OK. And so so if that if that's the case, if you're worried that way, then we certainly can actively work to to speed things into accepted. Right? I think I think there's no reason we cannot. Chris Stern just submitted a poll request today with an idea that had been not even listed as under discussion. It was just mentioned in community.jankins.io. And he submitted that Chris has submitted a poll request. That this is this is a result of the office hour we had. Great. OK. So the one with a screenshot update. Yeah, yeah, exactly. Yeah, no, no, that that was the other thing I wanted to report here that there are still some ideas coming and we want to speed the the process so that these new ideas come with a correct status and they agree. Get the necessary attention. April 4 to the 19th is the contributor application period. And then, Mark, this one is a question that I had. So May 12, GSOC contributors lot requests do from org admins. So is this something so this is what happens in the past as well? I thought that they would GSOC or Google gives us the amount of slots, but it looks like that we're requesting for slots. Yes, see, see, I suspect the March 7th announcement is we've been selected as a mentoring organization. And then between March 7 and May 12, we are assembling our mentor teams to assure that we think we have the right number of mentors to support this many slots. And then May 12, we submit we have mentor teams ready to support this many slots, give us this many slots, Google. And Google may say, you ask for six, we'll give you a three. But but I think that's what happens is they they they choose us as an organization based on do we look like an organization that's well suited to Google Summer of Code? And then they decide how many slots do they allocate to each organization after allowing time for those organizations to better assemble mentor teams, project ideas, potential candidates, etc. OK. Mark, I need to reread the documentation details. We as organization don't have to vet the eligibility of the candidates is done by Google. Right. That's my understanding is Google. Google's Google's task is to worry about eligibility. We don't have to check their whatever requirements, Google places. You know, we don't have to confirm that they're greater than 18. They're 18 years old or greater as an example. There's there's a very precise example. If a 17 year old applies, it's not our problem. I think that's Google's. Yeah. OK. Yeah, makes sense. We're not checking IDs. Exactly. Well, and it could have been that they'd say, no, that you have to check check those validate those things. But practically speaking, I I've never seen anyone mention anything about us checking out the eligibility in any of the times I was involved. The the the thing that is itching me is more the the new rules say that non students can apply as long as they don't have experience in open source. I have no clue how you demonstrate that. What is the evidence for that? Right. Right. The the absence of proof is a really hard proof. Yeah, I agree. And and I suspect they're they're asking just on on good faith answers. Please don't apply if you're already deeply involved in open source. Right. So it's bad. I hear the message that at this stage, it's not our business. Yeah. And and I can think of some candidates, right? Diraj Jota, for instance, who's been very active in the Docs office hours and has been a great contributor to Jenkins may say I want to be involved and I want to submit a proposal. And in terms of code commissions, I would say he is not open source experienced. In terms of Docs submissions, he's deeply experienced. Yeah. That's a good point. Yeah, because he's interested to do some some coding, I believe, from from this question. Yeah, it was he was on the office hour. Well, good. OK, yeah, sorry to mention a specific person, but that's for me is a good example that there are there are people we know who who are involved in open source, but I would say are not deeply experienced yet. Yeah, but this is where the definition is and where do they put the cursor on? And I prefer that Google decides that. Exactly. Yep. Another item that I have on that I want to mention here is which I didn't write down, but I was thinking I think it would be worthwhile for us to maybe do some kind of swag for GSOC, at least for the mentors. I think for at least for us, I find it hard to recruit mentors. And for those who mentor, that means it means I mean, for me, it means a lot to me because, you know, they're giving back to the community. They're using up their personal time for this. So I think some kind of swag that says, hey, I was a Jenkins or Jenkins GSOC mentor. And hopefully that they will wear it proudly. But I like that. Yeah, if we can, if we if now that that will likely require that we ask for some well, yeah, we got to find somebody to fund that. Right. Yeah. Yeah, definitely. OK, good, good. But the suggestion is good. No. Mm hmm. Awesome. Moving on to the next. And sorry to. Oh, sorry. At a certain point, we may write a blog post just to say where we're standing. And and now that we're starting the actual preparation of the submission, I think it's a good moment also to to to start that. OK. All right. Well, a good point, sorry. The good point is when Jenkins is accepted as. Well, and that might be a sweet time to announce, be a mentor, get a T-shirt. Right. Right. We just if you if you're willing to provide a proposed T-shirt design, that might be a great incentive. Say, you know what, anyone who mentors Jenkins GSOC will send you this T-shirt. OK. And now we need somebody to design the T-shirt. I'm the wrong. I'm not a T-shirt designer. And it's embarrassing, the kind of stuff I do in design. I'll take a lead on that, Mark. All right. OK, that's good. Yeah. And then Jean-Marc for the blog, let's you and I sync up and then I'll see what see how we can do. Yeah. We start to have a good a good way to cooperate in these kind of adventures. Yes, adventure it is. OK. CDCon, so, Mark, you made the submission, the CFP submission, you made it on time. Oh, two, you made two. I submitted two. Yeah. And I hope that at least one of the two is accepted. OK. All right. I'll I'll touch base with CDF. Great. Follow up with that. And I am planning to be in Austin and we'll we are going to do it. I am still committed. We're going to do a contributor summit there of an in-person contributor summit. We have a number of of friends of Jenkins and contributors who live in Austin and we'll ask them, hey, please come join us. Great. Anything else to add there, Mark? That's it. We I'm sorry, we need to add somewhere in the planner that we start organizing the second item. Well, in advance, that we don't lose track that a certain moment we need to work on the contributor summit. Oh, yes. Right. Yeah, we need a draft agenda, start the conversations. Exactly. Absolutely. Yeah, that we start that on time. Yeah. Beginning of June is the event. Yeah. OK. She code Africa. So there I need to get the project ideas submitted through their form. Xena and I will probably talk here in about 90 minutes, actually, today about the topic and it feels like the ideas are good enough. I've had several people who have expressed interest in being mentors. Angelique Jard, for instance, again, is willing to be a mentor. She's in a perfect location, time zone wise, being in Europe like she is. So we've got we've got some good candidates as mentors. And I think we'll go ahead with submitting the project ideas. I'll just make my best guess on which ones I think will be most successful. We're going to try something different this year. I'm feeling like trying something different this year in that I'm going to propose one of the one of the one of the mentored people would be a project manager and work under my mentorship to to manage the project. I like that. It doesn't it's not coding, but I think it's a useful skill. And if they want to put someone there, that would be great to have somebody who can assist with that kind of thing. I was thinking, you know what, one of the ways that we were talking earlier about some of the some of the legwork we do in open source projects like some of the sort of nuts and bolts work, things like uploading videos to this location or making postings. Those are things that these contributors could do as well, right? They could they could help us with those kind of things. It's community building. It's not coding, but it is community building. So so those kinds of things are not out of bounds for Sheikot Africa contribute on. And so I'll I'll bring that to the project idea and we'll we'll talk from there. I like it. And I think being a project manager, you can project manage pretty much anything, right? That will take you carry you a long way. Well, and and there are there are unique attributes about open source projects that are more complicated than many other projects confront. The let's see, everybody's a volunteer, so you don't have leverage of command and control in any form and everybody's remote. So you don't have the the benefit of being physically in the same location. And those complications are good skills to develop. So yeah, yeah. Cat herding, Catland is required. Yes, exactly. Cat herding. That's right. OK, anything else on this mark? No, nothing else. OK, great. So we are approaching March. So we have two Jenkins online meetup that is on the radar. That's me. I'll get those I'll get those proposed. Sorry. Yes, I still have the action item. OK. And I've one of my talks proposed for CDCon needs those two. And therefore there's motivation. There's intense motivation for me to get those two rolling. I see. OK, well, let us know if we can help in any ways here. All right, I will. OK, so that's all I have on the agenda. Is there anything else that you guys want to add? Nothing for me. No, thanks. OK, all right. Thank you. Let me stop the recording. I will stop sharing. Stop the recording.