 All right. Hi, everybody. Welcome to the Advocacy and Outreach Special Interest Group. It's Thursday, January 13, 2022. Today's agenda topic will focus on Google Summer of Code. However, we're waiting for Oleg Nanachev who is going to transfer his wisdom to us. He's not here yet, so we will go ahead with other topic agenda items, which includes She-Code Africa and the end of year blog. So I will hand it over to Mark and let me see if I can share my screen. Oh, I'm going to actually share mine, Alyssa, if that's okay. Perfect. Because then we can be working off of my copy. Great. So you should see a blank screen for now and now an outline of a document. Yes. Okay, so the Oleg suggested, and we've done it consistently for many years, that we create a summary end of year blog post to post on Jenkins.io about the result in the Jenkins project in 2021. Here on screen, what you see are the, is a draft outline that I assembled with docs office hours and with input from the mailing list. The idea is make it primarily looking at people and highlighting people's contribution, but using this framework of big things that did it. And so events, Google Summer of Code with five projects completed She-Code Africa with five women who are mentored. Hacktoberfest with 90 pull over 90 pull requests and three contributor summits that's a record for us. We've typically only done one contributor summit a year. And this time we did three. So we've also added several really important new sponsors to the, to the organization. And the sponsors are providing very helpful things for us. So the community site is sponsored by discourse. Our site that hosts all of our archives for the internet is hosted by Oracle. Algolia has provided site search. So these are sponsor stories of hey look thanks to them and I'll include text on deep thanks for the ongoing sponsors like cloudbies like AWS like red hat, like JFrog like, etc. And there are GitHub, there are many ongoing sponsors. One of my worries actually enlisting sponsors is I may offend someone by not mentioning how much we value their ongoing sponsorship. So help me as we're when I submit this for review I'll look for people's review and comments on did I get the right coverage. Exactly. I don't want I want the sponsors to know how grateful we are for what they do for us. Then other topics in 2021. We had some really impressive improvements to core configuration for modernization back in March upgrades to core components like the security framework like the XML serialization framework like the libraries. We've modernized how we're delivering plugins so that many plugins now deliver every time there's a relevant commit. And we've upgraded the Java 11 is now our preferred JVM so talking those kinds of improvements really quite impressive then security improvements and documentation improvements. So there's a whole data thing on the community site for for top users and most topics and most replies. So, I think we've got good data are there other things that you as outreach sig members would say, Oh, Alyssa, I'm sorry there's one that you had given me that was that probably should go in outreach. Because Jenkins is the way. Yeah. Oh yeah, definitely. Right because that that program the Jenkins is the way program. Now I don't believe we launched in 2021 we launched before 2021 right right right should include the results from 2021 in the in the summary. Yeah, very good. Anything else that I've missed. Participate in first them in 2021. We did the participation though was for me not a highlight. And I intentionally left it off here to it's a good point. Okay, we participated but I wasn't at least the feedback we had really was. It wasn't it just wasn't a big event for us because it was remote and participation was really complicated. Right. Okay, just wanted to check. Yeah, also didn't note, let's see we didn't do scale so that was one that it was a non right didn't do CD con as an event CD con certainly was a big event. I didn't put it there because I didn't see an awful lot of Jenkins talks in the in the in the agenda. So I left it off here. I did a contributor summit around CD con, and that was a nice result. So DevOps world mark, do we want to. Oh, right. Oh, that's a good one right. Yeah, that's a very good one certainly there were a number of talks there and yeah very good. Alright so now that needs more research that's a little embarrassing sorry that I forgot that. Yeah, but that's one I'm going to have to go digging to get some because I think that's a good one to highlight. Yes. Yeah, let me know if you need help with gathering information for that. Right. Okay. Anything else that you can see obviously missing. That's a great looking list I was wondering. And I don't think we got many of this but there were people who made monetary donations. Do we want to call them out or highlight them. I don't know that could be a very sensitive thing. I hesitate to do it because the donations are relatively small. Okay, that sounds good through the donor site. Now there is one of the donations will be highlighted. AWS donated $60,000 and in AWS credits and so that's a significant donation and and that I will, I will know in the in the ongoing sponsors section. Okay. Okay, that's not that sounds good to me. So that was it for the that outline the other piece was on she called Africa contribute on. So, last year in 2021 we as a Jenkins project and listed and participated by mentoring five women from Africa. They were from Nigeria Rwanda, and I believe it was Tanzania. We met her these five women from Africa as they began their first contributions to an open source project and they were contributing to Jenkins. We'd like to do that again this year. We'd like to use what we learned from last year's experiences to do a better job. One of the some of the things that we see benefit this year. It's starting one month later. So instead of starting first of April. Starting first of March, it will start first of April. So we've got a little more time to play prepare and plan. It's going to be a longer session this time. So instead of just four weeks like we had last time it will be a two week warm up period, four weeks of development then in a two week cool down period. So we think that will help the project be healthier as well now that the big challenge for us as, as advocacy and outreach or outreach is, I need to start the process of encouraging additional project ideas. So, two project ideas that were initially thought of the inclusive naming initiative get rid of the uses of the term master and slave and blacklist and whitelist and replace them with correct terms. So the pipeline help was a project we use last time. Others had suggested some additional ideas like test automation. We've got unit automated tests inside Jenkins that are using an old framework in many cases. There are some and certain certain plug in that I maintain has some J unit three tests in it still that need to be converted. It is long gone J unit four has now been upgraded to J or five. And so there are lots of opportunities there. The other suggestion was multiple tutorials on Jenkins.io where using these new contributors as test cases. Hey, why does this tutorial not work and what would it take to make it work. The getting started stuff there is they're very difficult. So that it's not because it started. It takes a lot of work to have a very nice but the incredibly useful. Right. Exactly. Now, now the other piece is that this one this one I worried maybe more advanced than a brand new contributors ready to do because John Mark as you noted, it's difficult to do a good tutorial. You have to know an awful lot about an awful lot of things in order to do a really good tutorial. And so, so this one may not be suitable but the next one screenshot updates. So in March. Oh, go ahead. No, that's a good one that's that's it and it improves the quality of things and it can teach a lot of interesting things and get people proficient in using the product and making updates and that's a super idea. Yeah, so, so this screenshot updates concept is in March, there will be significant UI updates to the Jenkins long term support release. So the March 2022 release will have really nice UI improvements thanks to the work of Jan Farachik and of Tim Jacome. Their work with supported by Daniel Beck and others their work has has brought a much nicer look to the Jenkins UI. But that means our screenshots are any screenshots we have are pretty much out of date. And so in this April timeframe, it might be a really good opportunity to have them do screenshot updates. Any other project ideas that you've got or my next step is to post a proposal for this to the getter channel to the community Jenkins.io and then start actually to community Jenkins.io and start the conversations there about possible projects and recruiting mentors. Last year the biggest challenge we had was not getting funding for the project he was getting mentors who were willing to coach these brand new contributors. There's one side project or or I don't know how to phrase it in English, but I'd like to use these kind of projects to clarify, improve or work out the Gitpod implementation documentation and have some real usage under the belt to to see so it's a project per se, but I would encourage young contributors let's call it like that to use the technique so that we do qualification of that and see where the friction points are. And so so it's more a tooling and sidetrack to the main effort there. I don't know how to phrase that correctly. Well, and let me give a strong yes to what you're suggesting. Because one of the problems we saw last year was that many of these new contributors in in West Africa don't have a high speed computer that they're running on locally. They may be using something like a Chromebook they may be using an outdated Windows computer. It's difficult for them to get the latest thing of this or that but Gitpod would provide that to them. Do they have adequate networking. That's what is adequate so this is what I would like to try. Right well but and that's where, at least for plug in development. It may be much better to use Gitpod because when I start up the plug in development environment and it tries to download a big chunk of the internet for dependencies. And Maven, I may not have great internet bandwidth but Gitpod does on the cloud right and so they, they have suddenly downloaded all their dependencies from one cloud location to another instead of taking it all the way into West Africa. Right, indeed. And, and you're making a strong point. At least I would like to try it out in a while. So really see with with random users. But especially for some lightweight things where no, you know the screenshot updates, but even changing the J unit things and no I'm, I'm, I'm, I think you know I'm strong promoter and interested by that technology. And that's, that's, that's a good one to do so, Alyssa those were the two things that I had she code Africa my next steps there are start the conversation in community dot Jenkins.io to prepare these project ideas and invite mentors to volunteer to help. The challenge is, of course, there's a part of it that's competing or conflicting with Google Summer of Code right, not the actual development of Google Summer of Code, but the mind share for Google Summer of Code so I don't want to sabotage our efforts with Google Summer of Code but this help out help a fresh brand new person who's in Africa is is still interesting to me any guidance from you Alyssa on how to approach it. I'm not off the top of my head, but I'm, if there's anything that I can help with, please feel free to pull me in. Great. So, I'm going to go ahead with with that approach for she code Africa and, and we'll we'll see how it goes. Okay. Great. And I think those cover the two topics I had so I'm going to stop sharing my screen. Great. Thank you for that, Mark. All right, and I will try to share my screen. Okay. Can you see my screen. Yes, yes. Apologies for the. So many windows open, but I've added the Jenkins online meetup which we scheduled for end of this month, Wednesday, the 26th of January. And that is with Uli Haffner. He will be talking about setting up the Jenkins deaf environment at his school. He's a teacher so he'll he'll show us how he's doing that. We're suggesting that people sign up via the meetup link and I've put the link here as well. Alyssa, I've got another as a sub bullet of that I've got two meetups that I need to schedule and haven't done yet. One is a meetup with Etienne Studer for Jenkins development acceleration with Gradle enterprise. And the other is meetup with Kosuke Kawaguchi for Jenkins development acceleration with launchable. Yes. Have you reached out to them yet or. They've both agreed in principle to do it but I need to write an abstract and propose dates. I need to actually do the work. Well Mark, how can we help. In this case, I think it's best if I do it because I'm the, I'm the noisy one who launched this project and I'm the one who is, who is sponsoring it so I'm hesitant to bring another voice into it right now just because I agree, but don't hesitate to ask for help. Great. Thank you. Thanks very much. For sure. Okay, so it looks like. Just, just a little note. Maybe, Alyssa, we should both write down somewhere the idea so that we can serve as a crutch mark so that he doesn't forget. Yeah, I'll update it after the meeting. I have it somewhere. I'll update it. Thanks, Mark. So it looks like all I still isn't here. I think we'll wait a sec. So I just see a Gitter post from him. He says there's no meeting invite for it so I'm going to send him a link to this meeting and see if he's available maybe he is. Okay, just a minute. Let's see if I can. Well, it just, you know he's a busy guy. So. So if he's available, that would be great. Yeah. So while we're waiting for a leg or what I have listed down here are the proposed project ideas and our planning document. I laid it out as much as I possibly can at this time. So we do have. We do have a date for the. I will add Chris to here as well. We do have a date for the application at this point. So they've published the timeline. Yes, they have. And it's here. So February seven. Okay, that's the opening and the closing then 21. Yeah, it's not much time. Okay, so we've got two weeks, February, February seven, they open it. We have to be complete and submitted by February 21. Great. Okay. All right, so we've got just this month. And well, we can certainly continue soliciting proposals project ideas, etc. But, but we've got to largely have our plans in place or good project ideas, etc. So that's the end of January, first week of February. Okay, great. Right. Listen, do you know what the, I've read so many documents that I forget what are the prerequisites for the application. So we've actually got a skeleton application from past past we would typically record the answers to their questions in a form so that we could all review them before we submitted the application. Yeah, and we've got those from past years. Okay, this one I didn't mark do we have last year's. I don't know that we have last year's because last year we submitted through CDF. So I don't know for sure I'd have to look. Okay, we certainly have the record of submissions from previous years before that. Okay, so what I have is only from for 2017. Yeah, that's the only one that I was able to dig up. And the application is five years. Yeah, so I'm sure things has changed since then. But I would love to see if I can get something from the previous year if that's possible but I can also reach out to CDF mark if now I know that it went through them. Well and Tara Hernandez is a great one to ask for help on that she may have have a copy of the document that they submitted. Well, I'll also check I thought that the submission packets were linked in our archives. So I think I may be able to find at least for 2020. I'll look and see if I can provide it to you separately Alyssa. Okay. All right, sounds great. Yes, here it is the GSAC 2020 application draft. So definitely, I'm going to paste that into the chat here. It's right on for there. There's the 2020 application if you want to put it into the notes. And then I think if we look at 2019 we have the similar thing. Application draft. Yep, there it is. So here's the link to the 2019 draft. And then the 2018 draft. I don't see a link at 2018 draft so I just got 2019 2020. Let me double check maybe we've got a draft for 2021 and I know. So, we've got the CDF organization page but not a, not a draft of the packet that was submitted. Okay. Great. Great. So I will. So we will work on that. And I'll drive this effort for us to make sure that we get things lined up before January or by the beginning of January. And, and make sure that large work items that are required for the application are identified on the to do list. Yes. Absolutely. So I know that for at least for the, for the immediate deadline that we want to accomplish is the project idea. So we need the descriptions of those I mean we I think we did great we have 12 submissions or proposals for project ideas. I already have at least, I think I'll have about three abstracts or descriptions for those. So the rest I still need to chase after the project idea process process that only has used in the past, that it helps us assure that the idea is well enough vetted involves a submission of things. I'm going to give you some sit down with you and with John Mark separately for some. Hey, here's, here's what what we could consider doing if we've got people are willing to help with writing those things. This is something that I plan to do this afternoon this afternoon to check that we have either templates or what is the material, because I read the recommendation about that fast that that parts in the Google documentation. Ellen and Elisabeth on your screen you'd be willing to open a new browser to Jenkins.io. We could we could actually take a look at it and talk to the perfect. Okay, so here if you go sub projects, Google summer of code in Jenkins, and then on the top right hand corner on this page there's Jesus 2022. I think if you click the oh no that that right now just takes us there. The, what we want to see is the price oh yes see the current project ideas so click that hyperlink that's under the. It's in the first sentence in the top paragraph. That one right click that because what this shows us is accepted ideas. And these are ideas that have enough text describing them that people can actually, it's quite strong, and then draft project ideas so you notice here we only have three, but you've got 1212 so there are nine things that we probably would like to at least some of them have them appear on this page. Right. For instance, nine of them could at least be ongoing discussion, where we would put them in the ongoing discussion section here because there's something happening in that in the in the mailing list discussing. Okay, this is something I'd like to to review with Alyssa and cross check, or maybe we use the technique that I start based on the first input by Alyssa. Make a prototype of it so that we can review it we need to synchronize and make work of that. So, and I think that's as a as an idea what if we took the, I believe the three that are on this page are already in your list of 12 right that these three are there. So you took the other nine. Oh, you say what's so to to that's on is already on this list from last year. One is an automation project idea from basil. So that's new. Right. So, those are the three that I have descriptions for. I don't know the basil idea needs to be vetted and approved and all that. No, I think I think what Basel has written. I think he gave a description in the mailing list. Yeah, and that was that would for me already be enough to justify if you scroll down. We could the section that's labeled ongoing sessions discussion here. Yeah, says these are proposals in the mailing lists. So, so this would be a great excuse to link to Basel's mailing list item and say, look, here's a mailing list proposal from Basel crow that suggests this project idea. Okay. Okay, and then the other ones should be would be under draft project ideas. Yeah, or, or even if if it's if the discussions only on the mailing list at least we put them in ongoing discussion. I say got it. And if that that's very light, just put them in ongoing discussion because they're being discussed in the mailing list. And if the people who are discussing them are ready to bring it as a draft idea, then an ASCII doc file gets, we need to create an ASCII doc file like this pipeline step documentation generator improvements thing that you see in the middle of the page. Okay. All right. What is the next step for that. So, what. Mark, would you do you think you'd be willing to attempt to figure out how to add something to the ongoing discussion list. Right, I will do that. And once I figured that out, I'm going to pick where we losing one day there. And the other way around that Alyssa looks what she would like based on the discussion we had right now what she would like to have added that and pointers to the material and tomorrow my time I'm going to create a draft. Perfect. Yeah, that's a pull request. So we leverage the time zone difference. I like that that's great so Alyssa Alyssa reviews the topics and suggest to you hey I think we should link to this mailing list discussion this discussion and this discussion and you can then submit the pull request. Yeah, and you can send that in any form you want mail slack or whatever. Great. Thank you Alyssa. Thanks very much. You bet no problem. You had mentioned Oleg and my read from his post in the Gitter chat channel is quote gentle reminder I cannot join the advocacy and outreach meetings unless they get moved to another time slot. I'm not sure if that means he's not available today. Again, I assume it is and let's just look for another time, because I would love to have his guidance on this. Yeah, it would help us a bunch, but I think we would benefit just by going with this little step that we see. Let's take it and let's continue forward. Yeah, absolutely. Okay, so I'll touch base with Oleg and we'll see that we can set up another time. Great. Super. Let's see what else do we have so I think that is all that I have that is related to what is do next in terms of Google Summer of Code. So this project ideas along with preparing for our application are the two big things on my plate for this. Now, now, Oleg prompted one question in terms of, should we change our meeting time and with Chris and dirage both joining us now we've got two people now from Asia who are in in the call. I wonder if we ought to put out a doodle poll asking for questions or proposals from people on when they would like to meet because dirage for instance meets with us pretty regularly on the, what would be for you Alyssa late night Monday. And for you, Jean-Marc is impossible. It's like the middle of the night. Well, okay, then we'll have trouble here at home. Right, exactly. Where are you located just for for me. Dirage is in Mumbai. Mumbai. Okay. Well, it reminds me. Okay, hello. Really challenging just for my information now is the middle of the night to for you or late evening. What time is it in your play for me it's late evening right now it's 1014 PM. Well, okay. So for Chris now it's over midnight because he's in Hong Kong. Right. Very courageous, both of you. And what we've found worked in the past was to have or what's worked for docs office hours is we actually do two sessions, one session that works for European times, and one session that works for Asia times. And that's, I think there's no shame in us considering that kind of thing where we say look, we, we, we live around a 24 hour world, we can't all be in any one meeting. So, so, Alyssa, are you open to considering looking for another time when we could meet hoping that Oleg might be able to join us at least occasionally. Yeah, because we can we can flip flop between dates. This is what you pose Mark. Yeah, alternate. That's, that's one or, or meet. Yeah, one week we meet on Asia time and one week we meet on Europe time and if you're if it's not workable for you attend every other week. And, and we, and we catch up with the recording and these kind of things. Exactly. We need to figure out a way we otherwise we're never going to solve the problem of this earth. Find something constructive. Okay, very interesting challenge. Yeah, we'll make it work so I'll take I'll take a poll and see what people think. Great. And that's all that I had for today, a dirage or Chris anything that you needed to bring other than what we've already discussed. Oh, nothing from my side just came here to say hi to everyone. Nice to meet you hi. Thanks a lot. That's all nothing else. Nothing to meet Chris is there's something that you're interested to learn or you you just catching catching up and getting. In sync with what we've been doing. Yeah, just catching up for now. Okay. Well, welcome, welcome Chris we're super happy to have you here. Yeah. Yeah. All right, so we'll talk online I guess at this point. Thank you everybody.