 Hello Aditya. Oh, we're already recording. Cool. I'm going to start sharing since we're already recording. That's great. Share screen. You should be able to see my proposed agenda. Hello, Mark. Hi, Aditya. Thanks for joining. Hi. Happy to be here. See, so am I sharing the correct screen, Aditya? Do you see the agenda on screen? Yes, I do. Great. Okay, then let's get started. So welcome, everyone. It's the Jenkins Advocacy and Outreach Special Interest Group meeting. Oleg has joined us as well. That's great. I've got draft agenda topics here. I don't expect to see Elissa Tong. I believe she's out this week. So topics I had, KubeCon booth support, DevOps world, and Hectoberfest. And then outreach programs, we had talked last week and the week before, or two weeks ago and four weeks ago about campus programs. I could give a status on Google Summer of Code and SheCode Africa for 2022. Any other topics that should be added to the agenda? It depends on whether we have people joining. It doesn't make much really in discussing color topics. Agreed. And I don't expect, I don't know about Jackie, but I don't expect Elissa to join. And so I would hold any topics that need Elissa for another time. Oh, did I misspell your name, Aditya? Oh, I did. Thank you. Corrected. No problem. All right, so I propose let's go through the topics we've got and we'll conclude the meeting after we've covered them as well as we can. So KubeCon booth support was a request sent by email from Jackie. I believe it went to Jenkins users or was it Jenkins advocacy? I don't think I've seen any responses yet. She's looking for both remote help and local help at the conference. And I'm confident, I think I could mark expects to be available to help. I just haven't blocked it out on my calendar yet. I don't commit on that because time is terrible for me. And yeah, I mean, it happens on the evenings and many other details you mark know about. So yeah, I prefer to not commit at all. And my KubeCon application was rejected anyways. Okay. Aditya, are you interested in joining as part of a being part of a booth at the KubeCon conference relative to CDF? That could be good, but I'm not aware of the timings and the dates of this one. And so let me let's that's a good point. I should have had that ready. Let me find her message and let's get the details put into this into these notes because that that will certainly be important to people. Where is it? It's in Oh, here we go. CDF virtual booth. Okay. It will be she says this coming. Oh, here we go. Okay. Virtual booth staff hours. So there are there are her notes. Oh, that didn't help. Okay. Let's just do it this way. Monday, October 11 through Friday, October 15. There we go. And let me embed the the link to that email so that others can find that it is. Oh, interesting. Okay. It's it's at CDF foundation mailing list. So it's not. Okay. There we go. All right. But I don't see any replies to it even even on the CDF list. Okay. So more help needed for Jackie. Like the time they are in which time zone? Pacific. Yeah, US. No, this is US Pacific US Pacific. Okay. Yeah, sorry. So that means shift them by what 11 and 11 and a half hours. So yes, I guess. Terrible. Late evening, late at night to impossibly early in the morning for you. Looks like it. Yeah. And that's that's certainly a challenge with any of these conferences that are in US time zones, right? That's your your time in India is half a world away and it really is half a world away. Yes. Okay. So that was all I wanted to do was remind on that. Be aware of it. Next topic was DevOps world. The announcement has been approved by the governance board and has been merged. Now we've got more topics happening there. So we've got DevOps world talks by Google Summer of Code students. So Aditya, you'll be speaking, I presume? Yes, I just got the invite, speaker invite for DevOps. Great. All right. Excellent. Thanks very much for speaking there. Then other topics for DevOps world. We've got workshops the 28th. Oleg, does it still feel like it's going to work for you to be involved in the in the contributing to Jenkins workshop? It depends. We still need to discuss it with all organizers whether my involvement is required. Okay. It's currently not in my quarter plan, but theoretically it's possible. Okay, so it depends on the complexity of the workshop, because it was just guided tour, we can do one if it's something really complicated. We will need to prepare. Great. And previously, I had, Dheeraj had agreed to assist, has agreed to assist. I don't recall if I'd asked you, Aditya, if you'd be willing to assist again with another contributing to Jenkins workshop like you did for the contributor summit. Yes, Mark, you did. And my reply to that was that 28th and 23rd September, right? So that's a little bit far in my calendar, because it'll be a new job and all at that time. So I won't, I'm not sure whether I'll be able to give my time to this. But yes, I am interested in general. So you had put me on hold as far as I remember last time. Oh, good. Okay. On hold. And let's just, that's great. Thank you. Sorry, I should have, should have brought my notes forward. Thanks. Excellent. So Mark, planning to lead. And, and yeah, I agree, Oleg, with your observation, it depends on, I think we should keep it simple. But, but even then, let's be sure we keep talking to see does it actually fit in with, with your capacity? I'm still not sure what is my capacity. By default, I'm not sure. Is Damian still interested? I, I, I think he was interested. I'll, I've, I've got to double check with him. That's my, my action item, a check with Damian to see if he's interested. I don't recall. I thought he and I discussed it and he said no, he just wasn't going to be able to do it. But let me double check. Great. Now, on the Jenkins or the, on the, is it a CDF track or Jenkins sessions? Is there anything, Oleg, that you're aware of that we need to do there? I think the conference organizers have already got their speakers selected and started the recording process. I know that Xenob and I have submitted our recording or have, have had the recording session. So I know for sure that my student has submitted the recording for GSOC. I don't know what status for the rest. I believe it's Kara who was managing that. Maybe you and Elise, I have no idea. Yeah. So GSOC recordings are in progress and, and that's good. I was just thinking if there were any other details that you, you were aware of that outside of GSOC, I'm not aware of any. I think, I think that's under control and the organizers have got it handled. I'm not sure the plan was to publish the agenda in June. Now it's August and from what I understand, I think has been published yet. So for me, I still don't understand whether we will have lots of feedback, whether we will have booths for Jenkins at this time, et cetera, et cetera. But yeah, I'm slightly disconnected. I want to chat with Alisa, but we haven't done it yet. She's available today. Maybe I'll have a chat after this meeting. Yeah. I think she's on, on vacation today. I don't think she's in the office today. I will check it. Okay. Yeah. Because currently I have zero overlap with Alisa because of various things. Right. So yeah. So that, those are all the topics I had for DevOps world, anything else on DevOps world? Oh, logistics. I don't have an answer. Oh, go ahead. Contributor summit. Oh, yes. That's right. Good. Do we have everything confirmed? So the, the confirmation things that I was aware of is that we will do it during, do it during Asia pack time zone and that we will host. Basically, right. Hosted on our, on the Jenkins zoom channel, zoom channel. Because then I would like to challenge the date because October 1st, if you do it, it will be firstly complicated for any DevOps world participants because of the conference is over and then next morning you wake up and something like three or four hours to start at the Jenkins contributor summit. I think that in this case, we should push it to the next week or maybe to do it on Saturday. Because Saturday may be more convenient for many contributors who kind of dedicated their working time for that. Right. Good insight. Yeah. So particularly with this, with this effort to reach Asia Pacific. So Aditya, does Saturday work better for you and for colleagues that you know who are employed? If we did it Saturday during the, during the, say, waking hours, would that be better for, for many people in India or is Saturday off limits? Saturday is fine, but Saturday is compared to which day over here. I think Friday evening would be better than Saturday. If you're doing Saturday evening, but if you're saying morning hours, then definitely Saturday morning is better compared to Friday morning. That's what we will be meeting today. So how I envision that it's not confirmed, et cetera. So we would start at something like seven, eight AM UTC so that Europe can participate as well. And yeah, in this case, it would be second part of the day for E-PAC region. And yeah, I checked time zones two months ago, it would be even for New Zealand, if you are going to us like that. But yeah, it's still tentative. So, so that I had to just do the translation. So that would be 12, 30 PM or 130 PM. Oops, it would help if I didn't, right there you go. Sorry, I pressed the wrong key. 12, 30 PM or 130 PM India standard time. So for me, that's, that's noon or lunch or yeah, afternoon, India time. And that would, that, oh, like your point is that has the benefit that allows New Zealand and sort of Eastern Australia or is it Western, Eastern Australia and China and Japan to still be able to reach into this during, at a reasonable time of day. Great. Okay. So is that a discussion week? We should start in the mailing lists. Should we, I guess discuss it with Alyssa, et cetera, first and then I think my link would be fine. Okay. Again, taking time zone, Alyssa will like to be able to participate on her own. Right. So for us, well, the critical question was whether we align it with the world or not. My assumption taking the currents or that you mark a good information that no, is it correct? Sorry, we'll ask your question again. I missed the question. So when we were discussing contributor summit, maybe one month ago, you took an action to discuss with stakeholders and confirm whether we align with the DevOps world or not. And, and I talked with Alyssa and other stakeholders and she wanted to continue that alignment. But I think even so, it's still open for us to have this conversation with them to see should we separate it because of the APAC time zone. APAC time zone. If you do APAC time zone, it's already separated. Ah, I see your sense is that that, that, that action alone disconnects it because DevOps world is in Pacific time zone. If I remember it or USC, it's, it's not in, not, not compatible with APAC time zone. Well, theoretically, it's possible to do a contributor summit in West Coast Slasher Park. So basically instead of doing it in the morning call the, you doing it late night, you, so it's possible, but then somebody, well, it, it will be more like this DevOps world, APAC will be able to participate. Europe won't be able to participate. It's doable, but yeah, we need to align on that. Yeah. And I think, I think Europe morning is a much better choice for the success of the contributor summit and for, for our engagement in the contributor summit. So I think that's, that's worth in the conversations with Alyssa and others to, to change the time or to set the expectations that we're going to meet during APAC time zone. I shared that with her previously. So I think she's aware of it. It's just this would say, Hey, we think it needs to go at least one day later so that we can get some sleep after the end of DevOps world, or we may want to do it during the following week for, for, if we want to do it during a weekday. So it's for someone to decide. Definitely have preference of a contributor summit in the APAC time zone. Definitely cannot commit to doing two contributor summits like briefly discussed in June. Yeah. I agree. This, this is a single event. Absolutely. No way should we attempt to do too. Well, it could be possible, but it requires bandwidth, organizers, and we have just three participants at this meeting. So I'm not exactly confident about having enough organizers for this event. Right. If we do two. Got it. Okay. All right. So Mark, to start the discussion on contributor summit date and time. Okay. Got it. Anything else on DevOps world and contributor summit? So the result of common topics like Schwach, etc, coordinate sponsorships, but yeah, until we have time, I wouldn't commit on that. Right. Right. That's the, there's, there's an awful lot of organism organizing agendas, etc. But let's get a date, a date assured and then we'll continue the organizing. All right. So next topic we had was on Hacktoberfest and we discussed in our last meeting with Aditya what topics we wanted to cover, etc. So one idea was in the 28th contributing to Jenkins workshop, we could do an introduction to Hacktoberfest there. We could also do it during a contributing to Jenkins segment at the contributor summit. Both great excuses to involve people, particularly from Asia Pacific, who are being Hacktoberfest participants in a session that's Jenkins specific. And we've got, we've got some rough material, some materials that have already been prepped from previous Hacktoberfest that we can use to prep and run this. So I think that's part of the exercise. We need a plan. And then we've got to review the plan and talk about how we approach it based on capacity. Now Aditya, you had asked a question last time, or you mentioned Hacktoberfest and active loop. Could you give us a little bit more on what that concept was? Yes, Mark. So the concept was something like this. Active loop was a part of, so there were two entities over there. One, there was a curated list of all the, you can say, organizations slash projects that are participating in Hacktoberfest. And these what made them different from the rest of the crowd was they were providing some kind of a leaderboard that I'm keeping tracks of the contributions made during the Hacktoberfest for swag or mostly for swag. And yeah, that leaderboard was, you know, something that was encouraging some healthy competition. And that, and I forgot the name of that repository, which had this list, but active loop was one of them. And I participated in that and contributed to active loop. So I know the name of the organization and yeah, that thing. So active loop was one of them. And they had this leaderboard where they were keeping track of issues, the candidate is solving the quality of the issue as well as number of issues. And according to that, they were scoring them. So the issues had easy moderate and difficult difficulty levels. So stuff like that. And finally, they gave swags to people on the leaderboard list. They give t-shirts to top three. And then some other kind of swag stickers to rest people saw something like that. So that was a way of like a parallel swag thing along with the W, wait, I forgot the name, Digital Ocean, along with Digital Ocean Swag. So that was the whole program. And I see you have already mentioned, but yes, they did that, but they had specific Slack channels just for Hacktoberfest questions and support. Okay. So this feels like it would be an expansion of techniques. Now, Oleg, you had, if I remember correctly, in a previous, was it a previous Hacktoberfest or a Jenkins Hackfest, you had a GitHub repository that we had used that tracked contributors. Is something like that usable for this concept? Or am I misremembering things that know that idea wouldn't work? It worked quite well. It's possible. This repository is basically a configuration scope. So it's still available. It's just GitHub action to be connected to the repository. Yeah, I think we can do that. Again, just raises a question who would be administering that, who would have time because all this administration requires time. Right. Exactly. And is your sense that that's something that requires your level of skills, or could somebody with my level of skills or Aditya's a new arrival be able to do that? What's your sense of how difficult it is to administer that kind of a thing? Well, it's not difficult. It's just a matter of self-organization because there are so many various things. There are so many time sensitive topics, you need to perform to make it efficient. So basically it's not about technical skills. It's about ability to dedicate time and to deliver on major action items. Because, for example, if you don't announce October 1st, you wasted some time. If you didn't summarize results, like it happened with the contributor summit again, maybe lose some impact. So you need to just be careful to handle and not Okay, great. Well, and so I assume we would need to, we would have to announce it. And as part of the announcement, we'd have to show how the repository tracks and tracks contributions and how we use it. If we were to use the idea of that Aditya described, we'd have to find a swag sponsor and some people who are willing to spend the time scoring contributions. And my guess, my fear is that maybe more than we can handle. Okay, great. Yeah, so the three people who are on this call with their limited capacity. Yeah, so, okay. It feels like, well, anything else to discuss there on Hacktoberfest. It's, for me, the big gap is we've got a planning exercise that's got to happen and people to help lead the exercise. And I'm not feeling like we've got all the all the capacity we need yet. So probably have to ask in the community, look for others who may be willing to help see if Gavin or other other community participants might be available to assist in some way. Yeah, my case, I prefer to not commit on anything. Right. I'm thinking about organizing something for Hacktoberfest. I will be definitely doing a local meet up should be allowed at that time. Nothing's, but right now I don't want to commit. And I think that makes perfect sense. Absolutely. All right. Next topic I had on the list was about outreach program status. So we had talked in depth about campus programs. But I think that needs Alyssa. We had had a discussion with Aditya and with Dheeraj in our meeting two weeks ago. Aditya, is there anything additional you wanted to share on campus programs while you're here with us today? Actually, no, Mark. I did share everything in the last week. If you want, I can maybe speak on it, but it would be just a reputation basket. That's okay. I think we can refer to the previous meeting notes and when I get the recordings uploaded, they'll be available as well. Great. So Google summer of code brief status report there. It's moving forward. Thanks to Martin and to Oleg and to Kara. Martin's getting things scheduled for the final presentations. Aditya, congratulations on your progress. So presentations will be done in a webinar to the community as a whole and also at DevOps world. Then she code Africa is planning their contribute on for 2022. So think April of 2022. It's a long ways out. I've posted an initial question to the Jenkins community forum to community.jenkins.io. No responses yet, but we'll continue working that topic as we get closer. Probably participate in that, but in a more public language that we did at last time. We need more mentors, but I think that we can do that. Yes, and I agree with you. We need to use what we learned from our last retrospective to do a better job with contribute on, but I think we can and should participate. Yeah, one other things. So a few other things for outreach programs. So last year, we tend to be discussed. Yeah, LFX mentorship programs for documentation. So it's a question for you, Marcus, the documentation officer. Do you see any possibility that we can make it happen? I think it might be possible in like November, December. I don't see anything between now and end of October to we had someone who was interested in applying and we had topics relative to Kubernetes, but I don't have capacity between now and end of October to to do a documentation mentorship. And I don't think others have that capacity either. Now, we've got we've got several consistent attendees at our docs office hours. Diraj attends every week, Meg McRoberts and Kristen Whetstone. So we could conceivably repurpose those documentation office hours as mentorship weekly and and consider that. So I'm just not sure that that I can see it happening yet. Is there a time? Is there a time scale on this Oleg that it needs to happen soon? Money might go away or something like that, or it's more of, hey, the sooner we do it, the sooner we get benefit from it. It's the latter and also policy. So there are standard timelines for the next standard consulate starts in October. But yeah, I don't think that it's something. So next next you say starts. They they have a running series of is it quarterly every six months? When do they start new mentorship? So October and then January when we want. So there is a kind of standard pattern. So if you want to be in newsletters, etc, you should follow this pattern. If not, yeah, then it will be a bit more complicated, but it's doable. Okay, I see. And is that newsletter promotion on a quarterly cycle or on every six months or every year? Because, well, let's say they're organizing LFX team at the moment. So I'm not sure who's handling that. I have direct connections with leaders of LFX at the moment. So we can help with that. So again, it shouldn't be an obstacle for us. Okay. Great. So if we had if we had mentors, we could we we've got we know we've got funds available. And we know we've got we we could use this if we're October if mentors are available. Maybe what I'll do is let me I had not put this under the docs office hours. Meeting agenda. Let me put it on the agenda for discussion there. I suspect the answer will be no, I don't think there's capacity, but let me ask. We also had a tentative discussion for who is the operator of the client plugin. I mean, I don't have to revisit it right now. Maybe I'll think people later. Yeah, so there was Kubernetes in general. And you said Kubernetes operator and tecton client plugin. Okay. Any other outreach program items that we should should note? Not at the moment. So I guess you won't be applying to even the session of our preaching. I haven't seen any interest in that at the moment. Yes, it is. It helped me out there is outreach different than the Linux Foundation mentorship. Yes, it is right. It's a separate project, separate program. But firstly, it's quite expensive. Secondly, need to apply in September is project ideas. And I wouldn't like to commit unless there is a company sponsor who wants to fund this effort. So many funds in Jenkins will spend 20k dollars on outreach. So as events officer at the moment, I'm against spending funds on that unless we have clear idea how it would be official to the community and how we could use it efficiently. Okay. Well, and I assumed that we would would prefer a corporate sponsor in that case rather than using Jenkins fund direct funds directly. We don't have enough funds to fund the preaching. So just some numbers. If you want to run outreach, you have put six and a half thousand dollars per student. It's higher than Google summer of code at the moment. It's higher than LFX mentorship. It's basically higher than almost any outreach program in the world. Okay. And so far, I don't see that it achieves its goals, because students participate but then they disappear. We have never had any student who's ticked around in the Jenkins community as a result of outreach. So if we want to actually reach the program's goals, we need to come approach completely different. And I'm not ready to commit on that this year. Got it. Okay. So not planned, not even hoped for. That makes sense. It just doesn't make sense for us to attempt outreach. If we could, it seems like we could get greater benefit and more flexibility from the Linux Foundation mentorship than we could. Yeah, you can run three programs instead. Right. With funds. Choose of mentees, because in outreach, you basically don't have much choice. Other than assuming replicas and yeah. Got it. Okay. Yeah. So the crucial. I'm sorry to cut you off. I would have to drop off because of another meeting. That's perfectly fine. Thanks, Aditya. Thank you for joining. And I think we've covered all the topics. Were there other topics, Oleg, that you had? Well, there is one minor heads up. I will be sending an email to Advox, because I've got a request from whatever German aggregator of open source jobs, etc. They want to list the German Jenkins community on their website. So they requested some collaboration from the project site. I will probably just start a thread in the mailing list. And another quick heads up with it. Most likely I will be returning to the question of job sport incoming into Jenkins IO. So we had a brief discussion this game in Morgan about that discussions with these other contributors. I think it might sense, might make sense to have it. But yeah, I need to firstly be consensus in the Jenkins governance board. Great. And last but not least, we have the elections cycle starting in September. Right. So and the actual election is elections are in, is it November with announcement in December? Is it actually elections or in December? No, elections are in November. You might adjust the timeline slightly. But if you follow the biggest timeline, it would be November. Yeah, excellent. Anything else? Okay, then let's call this session end. Thanks very much. I'll post the recording. I'm way behind on posting recordings. So my apologies, it may be several days before I get to posting the recording of the meeting. Notes are available here and recording, I'll get to it as time allows. Thanks.