 Welcome it's April the 8th, 2022. And this is Jenkins documentation office hours agenda we've got news she could Africa contribute on Google summer of code and I had something on weekly change large process but I don't think we need anything on that. Make any other topics you want to put on the list that does it for me sounds good. Okay, so by way of news. Oh, a good one. She code Africa has started started April 5. We're in the two week period. For community bonding. We're trying to know each other understanding the project, talking about how we'll deal with each other, preparing blog posts, those kind of things. And that's new this year we did not have that last year. Correct last year we did four weeks started and stopped and boom. And this year we're making sure that they're configured ready to do the work that they're introduced to the team that they've had some introductory training, those kind of things well before we actually did the official work. Excellent. So, so preparation right now and then. Then we will, we will start the actual work in. It's about two weeks from now so figure April 15 or 18. And that'll only go for four weeks and then they have a two week end of project period so it's a good match. Yes, sounds good. Now there are our detailed notes in the meeting notes from our meeting earlier. So the meeting that was yesterday in calendar time has a bunch of notes on things that we described took them through a tour. Two of the contributor to the Chicot Africa women that were there. We talked about the steps they do to download and run Jenkins create a GitHub account. Create an account on get pod.io so that they can do video they can do website development. And there's this tutorial that shows how. We discussed how to divide the work between us. This is one actually make where it probably help if I show you what what we've decided to do is let me show you the idea. The idea looks like a word I put the sheet is this it. Nope. These are the people. Nope. I closed the sheet. Maybe I hit it away. So what I've got is a worksheet that lists every plug in sorted by installation count. And then I assigned 15 of them to the first person. And then I set up a four and 15 to the second Catherine to and hero, and then we alternate back and forth. And what I was just doing was doing some sanity checking searches looking for inclusive naming failures in those and in each two or three blocks of 15 that I checked I found at least some in every case. And these are very popular plugins so when I say the high popularity these are the top 30 or 50 plugins, which means averaging more than 200,000 installations each. So those are those are good things and many of them have been solved right many of them are there. There's no reference to slave or no reference to master, and so that's good that's a win. But having just found a few that says this exercise of having them go through it is valuable, it will help us weed out those last few remaining things, even in those high volume plugins. Yep. Excellent. The idea is we'll use that sheet as the, as the arbitration point to decide who's going to work on which, which things and how, and we'll let it run from there. Terrific. So, that's really the topic I had there then and for Google Summer of Code we've got ongoing reviews of projects are needed. A lot of plans are needed of proposals are needed and do by April nine, so that the candidates can refine and submit in time for the deadline, which is April 19. I recall correctly. So do you have a lot of proposals ready for review. We have, we have three or four or maybe five that are all being actively reviewed on different, different topics to that are very active on the get get idea to that are very active to or three that are active on another one and then the plug in health topic we've got one very serious one so it's it's looking okay. Yeah. Those are the topics that really I had. Are there other topics you wanted to bring Nick. Dare I bring up my old favorite any movement on that. So, good question let's put open PR is there I think that's what you're talking about right. So Mark still has not negotiated has not made the trade with the security team. So I'll talk with them for some of their time so I'll, I'll talk with them. It may not be tomorrow but I hope to talk with them before, before we meet next week. Yeah well let's not burn you out I mean if it waits another right. I was just curious. What I mean to me is I'm, I'm admittedly accepting that I'm going to fail on some of my action items just so I can keep the other ones, get the other one. So, if this gives if this makes you comfortable that you failed on this one this is a good one. You know, I mean some, some of them are more serious if you fail on them, let's face it. Right. Exactly. Some of them are much more pressing have a have a hard deadline or yeah, exactly. I just kind of want to make sure this doesn't fall off the edge of the earth. That's all I care about. Right. And, and that is wholehearted agreement we're going to we're going to get that thing through all the way to the end yet. It kills us. Right. Seems like such a good idea at the time. It was a good idea and it still is. So any other topics we should discuss today. I don't think there's anything else urgent I think the GSAC stuff is probably calling. Okay, then let's call tonight done. Thanks Meg have a great evening. Thank you. We'll talk. Bye.