 Welcome to the Advocacy and Outreach Special Interest Group. Today is January 27, 2022. The agenda for today are CDCon, GSOC 2022, and Jenkins Online Meetup. So we'll start with CDCon. It is slated for June 7 to the 8th in Austin, Texas. The CFP is currently open, so we're encouraging all Jenkins experts to submit their stories. We want lots of stories there in Texas at CDCon. The organizers of CDCon is inviting Jenkins to host a contributor summit on site. We have made a physical space available for us to host this for all day for one day. I wanted to bring this up for discussion, whether we want to move forward with this, do this thing offline. Has there been other discussions elsewhere like in perhaps the governance board? I think I saw the minutes. Yeah, so Oleg gave good guidance in the governance meeting based on his experience. I had suggested, well, should we do a hybrid where we do both remote and local? And he noted he's not yet had a positive experience with a hybrid event like that. Either do it all remote or all local. And I think he's right, it makes sense. I think we should, I think we should strive for a contributor summit at that time and do it local. And then if we've got interest, also consider a remote hybrid or a remote contributor summit concurrent with it, or not concurrent, but in the same rough timeframe. One, for instance, in the Austin, Texas time zone. And then a few days later, do one during European time zone, or do one during Europe plus Asia time zone like we did last time where, where we get the benefit of being co located for one session and then a few days later, do another session and there are certainly plenty of topics for something like that, Java 17 UI improvements, documentation improvements, cloud native improvements, all sorts of things that we could and should discuss in a contributor summit. I like that idea actually it, we're, we're, we're able to cover at least participation from different parts of the world. Yeah, love that idea. Me too. Yeah, now, now one of the dangers is we can't do them back to back because I absolutely want to attend both. And I refuse to do a contributor summit that takes 24 hours of me being continuously awake it won't work. So, so, so I would, I do think we should do one on site in, in Austin, I think it would be great and I suspect we can find for instance Oleg suggested some people that we know in Austin, who might be willing to help host it locally there, like Ryan Campbell. So, so there are some some candidates in Austin specifically who may be willing to assist us in making the event successfully local successful locally. I'll clean up my notes after the meeting. No problem. Okay, anything else to add mark to this before we move on. Okay, so, so I will go back to CD con organizers to let them know that yes we are interested in their offer. Thank you. Great. Okay, so Jesus 2022. I will reach out to the previous years mentors because we are still in need of additional mentors and project ideas. With frontman's, we are making good progress with regards to updating the G soc web pages, still work in progress there's still lots of pages. And there's still more information that we're waiting for from the G sock mothership. So we will update as those information becomes available continue to update so it's a continuous work in progress. I send a ping mail on the dev list for other project proposals and mentors, mentor volunteers and see if this brings something in order. Great. Thank you, Jean-Marc. Let me see. And then as we saw CDF was able to create a Slack channel for us mentors. So thank you, CDF. Are there, do we need to ask them for additional channels or is this channel is for mentors discussions? Yeah, the watering hole, you're in mute, Marc. Yeah, I think we should ask for a channel for that we can use for general communications because our past experiences using other facilities with GSOC students have been less successful. Now, we could maybe go to community, I guess, instead. Well, this is what I lent towards in refactoring the documentation and saying that discourse or community was the main channel and the getter as a backup. Good. Okay, that makes sense. I'll let that. There is what I described as the mentor's watering hole that would be the Slack channel. And there is one still to go is a communication facility for org admin. And there was a mention of a mailing list. I will see if I can retrieve that mailing list, otherwise I will create another one or just because there's limited, there may be four people or so one on it. So what do you think for that? So I'll work on the admin mailing list, otherwise everything is set. I'm still one document to go for correcting the channels. Okay, so now on the general discussion in the CDF channel, because we're using getter and then Jean-Marc will create a mailing list for org admins or update it. Yes. Thank you very much. So maybe worth summarizing, the main global, there are two main global communication channels. The main one being the discourse one, secondary being getter. There is the Slack channel for, as you mentioned for the mentors and the mailing list for admins. So these are the communication channel we should keep. Yep, okay, and I'll update, I'll update after. Moving on, the Jenkins online meetup. Yesterday's fully session was quite successful. I myself can use some improvement with more doing more of these, but I thought his topic was really interesting. We did get really good feedback from the audience. So yeah, I would love to do more of these in the near future. The next one that we have is GSOC 2022 discussion, and I will work on us getting, yes Jean-Marc. Yeah, sorry to interrupt you. Feedback on yesterday's session, maybe something we need to think. Was the format adequate or are there things to improve of how we worked yesterday? Meaning with panel that were serving as sounding boards for the questions, was that enough? I think yes, and we were already pretty busy answering the channels, monitoring them. So the format is, in my opinion, a good format to continue, so that worked well. And the other point was that I think we had a good audience. I think we were running around 50 attendees with 150 that registered, so which is a good ratio. And well, I believe that 50 were good. So I didn't look at the sheet that you sent, Marc, with the variation of the audience, but it makes a lot like TV shows that monitor their audience. So the publicity, do you agree with me? I wholeheartedly agree. In fact, the participation rate, the participation percentage was higher than I remember it typically being. Getting a 30% to 33% participation rate is unexpectedly high. I'm accustomed to more like 20% and sometimes as low as 10% participation rate. Okay, yeah. So the fact that we got, and what I had seen was 141 registered and we had 55 or 56 at our peak. So we were well beyond one third participation rate. Which is good. Meaning that something we need to reflect once we have our first flow of presentation is their appetite for a developer or contributor or re-entered meetups or is a subject balanced something we need to work on and look at subjects in that field. Yeah, so I agree. Topics is a good question and it's a very valid question to ask. I was going to go look at, for instance, the example I have of a tutorial video is Darren Pope's part one of Modernizing Jenkins and it's got over 700 views right now on YouTube. So the recording shows hints at some interest in the topic. Okay, so we can, I can or other can start thinking on topics in that domain to leverage also the videos that Darren and you do. I think so. I think those kinds of topics seem to be interesting to people and so that's a good sign. Good, so let's reflect on that. Okay, sorry to have interrupted your flow Alyssa but I wanted to take some time to do a debrief on that session. I had fun with it so I learned a couple of things. All right, so GSoc 2022 I will be working on setting a date for our next Jenkins online meetup to discuss about this. So more to come on this via either discourse or mailing list. Oh, and Alyssa, you remind me, we've got one additional topic that's not on our list, a top level topic after we finish with Jenkins online meetups and it's GSoc office hours. Yeah. Thank you. And if you just put it on the list, we can talk to it when we get there. We can talk about it now. Oh, okay, yeah, that's great. So it's not really a Jenkins online meetup. What office hours are is an opportunity for contributor candidates to have a chance to ask any question they'd like to one or more people who are hosting the office hours and can answer their questions. It's been, go ahead. Oh, I just wanted to rephrase what I understood. So it's just a point where at least one knowledgeable person is present and where we discuss any question that can arise. So it's not really a focused meeting with an agenda or... Correct, exactly. And in fact, it happens only if there's interest and we move its times as necessary based on what the interest is. So sometimes it's been, there was no one attending except the one person who was ready to answer questions and 10 minutes into the meeting, they canceled it, said, we're done. We don't have to do this. And other times there have been three or four people who would join and then it was very important that we had the conversation guiding the candidates on how to prepare an effective proposal. Right, especially that we're now getting slowly to the period where guidance will be useful. Right, exactly. Okay, we thought of using this meeting here for that, but this is more for steering. The office hour now I understand much better. The purpose of it is more information. Yeah, well, and here in this session, we talk about administrative and guidance, whereas in the office hours, exactly what you said, we are focused on how to help individual applicants as they prepare their submission. Okay, that was clear. And there we need to be aware of time zones. So the timeframe for this to happen is around when, Mark? Is it like right before the contributors applications? Well, we should probably get it started as soon as we can because we want good contributions and that usually means we need to encourage people to come ask us questions so we can help them make a good contribution. So as soon as we can reasonably do it, in past years, it was commonly running already in January. Okay. So we better get, okay. And now I understand much better the purpose of the meeting. Yeah. Okay. Okay, I will work on that. Going back, so Mark, you have these action items. And I still have them. I'll get on them very promptly. I gotta get, I'll get the initial materials sent out this week, so before end of day tomorrow, I'll send it out. Okay, all right. And then if you can include me, I'll follow up with the rest and I'll make sure we get things on the schedule and start planning for it. Great, thank you. Okay. And you're allowed to chase Mark if you don't hear anything by tomorrow. Absolutely, and Alyssa, I was outside shoveling some of that white frozen liquid just minutes ago, so we can also have conversations about that if necessary. Yeah, we could. I was teasing Alyssa yesterday or a day or two ago about snow, because where she lives, they don't actually have it. Well, it's just theoretical. Exactly, it's just a theoretical experience there. All right, okay, so I think that's it for today. Yeah, thank you. Thank you so much. All right. Bye.