 Okay, then I will share my screen. Can you see my screen now. Yes, we can. All right. Everybody. Today is May 5. This is Jenkins advocacy and outreach SIG. On the agenda, I have she sock update. She code Africa, CD con dev ops world. And Jenkins online meetup. Is there anything else that we need to add? Okay. So first on the agenda, so she sock update, we are done. We're closed for the reviewing and grading period. All the org admins met and we are working on the ranking at the moment. We think we have most for the most part what we need in place to deliver to Google by May 12. I'm not sure. Right now, Mark, I'm not sure if you're the person I can ask about this, but we need to provide. Pioneer information so that how. Our compensation will get compensated. From my Google via the pioneer system. So I need that information. Okay, good question. So, so let's have me take the action at a mark to ask. How do we deposit money in there? That may also be the seed seed. The answer to that may be the seed that I can use to. To take care of two action items. I have related to Jenkins funding in the governance board. So there are two places where I can do that. Mark. Okay. I'm already reaching out to them. So yeah, let me. So, so it. They are, they are the, they are our, the keeper of our accounts. And therefore they are the best contact to tell us how do we deposit money in there. So that's what I'm going to do. I'm going to do that in the governance board. So there are two places where I need something similar to that. So if you ask the question, you may also help me when you find the answer. Okay. All right, I will do that. I know that they are. At an offsite this week. So I will still send out communication to them, but most likely they'll get back to us next week. Just. That's great. Thank you for doing that. Thank you so much. Thank you. Thank you. Mark. Add Lisa as the action. Oh, you're. Is there anything else that I thought you need to add here? Mark. For. It's. It's moving well along. And we're. Preparing the next phase. So we're okay with meeting that deadline one week from now that we're going to get the deadline. Yes. Yeah. We, we have, we have already our draft. Decision. Filled in. Great. And we only have a doubt for one project. And we're still. Reflecting on that one to make a decision. Yeah. But we're, we're good and checking. That the procedure is well understood. That we didn't forget something. Excellent. Thanks. Thanks to both of you, and to Chris, you've been absolutely wonderful. I know that it looks like the Jenkins project is deeply experienced at Google summer of code, but this year it was all new org admins. You've been great. Thank you. No problem. She code Africa. So Mark, I have here. I don't know if there's any update you want to add here. Yeah, if it's okay, I'll just do a brief status report because I'm, there's some things I'm that make me proud and other things that make me a little bit of flinch. And so let's, let's take both the, Hey, here's some points of pride and here's some things that we'll do better next year. So on the, on the points of pride, the, the screenshot update and the inclusive naming projects are working very, very well. And the contributors are actively involved. They're interested. They're contributing and they're, and they're also learning in the process. And so we get both the benefit of them learning things and them contributing at the same time. And that's a good hybrid. We like it when it's not just us teaching and we like it when it's not just them contributing without learning something in the process. We've got this hybrid of contribution and education that is helping them grow. And part of that is because those two projects screenshot update and inclusive naming were relatively simpler projects. They don't have enormous technical complexity. They do have a lot of learning that was required in order to update a screenshot. You've got to be able to recreate the screen and recreating the screen means you've got to know enough about Jenkins to get to that place. And surprisingly enough, it's not in many cases trivial to get to that place. So it's been, that's been the education part for them. Inclusive naming the same kind of story. There are places where you can make changes in places where you can't. And they've had to learn where it's where it makes sense to make changes and where it doesn't. And that's a learning piece on the weak side, on the shame side week, whatever you want to call it. The pipeline help project has not gone as smoothly. And part of that is because we didn't do as much preparation work this year as we did last year, but we use the same kind of project ideas we had last year. And that was too technically demanding. Too likely to fail. And has too many opportunities for problems. Right. It's. Go ahead, John Mark. I'm, I'm very interested by, by that experience. So. But maybe we can take it offline because I'd like to record the. The learning. Of that. So. One lesson learned is that we didn't. Prepare the scope or the tooling or a precise description. That we had to, to organize that on the fly. So do I understand that correctly? Right. Yeah. That's, that's, that's one of many. And, and these are the comments. We had a retrospective on last year's project. And many of the challenges we're seeing here were already included in last year's retrospective. So we will do a retrospective again. It's just, we didn't heed the notes from our eye. It's not we, this is not the King global. This is Mark weight did not heed the notes from our previous retrospective where we said, Hey, look, this is technically very demanding. And there are opportunities for failure hiding in technically demanding projects. That a brand new contributor shouldn't be made to submit to the task, right? We, we owe it to contributors to give them a better experience. And, and my, my initial, my, one of my mistakes was thinking, oh, it's too easy. There's, there's too, too little learning in these other projects whereas it turns out screenshot update and inclusive naming have plenty of technical complexity hiding in them. Plenty and enough for a, for a brand new contributor. Okay. So, so it's just a matter of those kinds of things. Right. Going to ask you pointers on the lessons learned or retrospective of last year. I'm interested to, to, to read them as supporting material for the GSOC effort. Good idea. Well, and I'll put a, I'll put a hyperlink to the retrospective into this document. That way we've got a copy of it because, because last year's retrospective is there. And it has, has many of those, those notes in it. So let me go get that. I'll do that while the meeting continues that way. I can paste it in here in a minute. And that's all that I had on she code Africa contribute on. Thank you. CD con. So that is slated for June 9th. For the contributor summits that's taking place on site. The agenda for the contributor summit is currently live. It's, I posted it on discourse. And then I'm asking CDF to post it on the Austin meetup page as well. So that will be done next week when they are back in the office. I'm ordering some swag for the event. So getting some Jenkins socks and stickers. Yeah, I figured it's lightweight for me to carry. Okay, that's fun. Okay, good. That's, that's, that's the definition of swag. Okay, got you. Stickers and socks, Jenkins socks. So I'm working on that. Okay. Okay. So, um, See DevOps world. So as you already know, the CFPS been extended to May 25th. Our Jenkins contributor summit at DevOps world is scheduled for September 27th. So that is still. Available for us. So we just need to get our plan. So we still have some time, but planning to come soon. Yeah. Did you see the new date and date for the CFP on the website? Or because Jean-Marc and I saw it yesterday on a video on a live, I think in a meeting, but it wasn't yet available on the website. So now it's official. It's on the website. It's May 25th. I actually, that's a great question, Bruno. I have not checked on the website. But I know that the website, it's worked by a different team. So probably that message hasn't. Gotten or the task hasn't gotten on their plate. Good. And Jenkins online meetup. So localizing Jenkins with crowded enterprise that slated for May 12th. And that is already. On the Jenkins online meetup webpage and we are getting, I yesterday as of yesterday, I think we had about 28 RSVPs. Cool. And that one is, I would expect the attendance to be less than our typicals because most online meetups are targeted at showing some feature to general Jenkins users. And that's a smaller audience than the, than the, how do you use Jenkins? I would kind of surprise because I wrote it on LinkedIn, Facebook and Twitter. And on Twitter, I got two people from Russia or maybe, you know, East Eastern countries out of the blue that I never heard of. Oh, I'm, I will come. I would be delighted to be able to participate in a meeting. I will come. I will be delighted to be able to participate and ameliorate Jenkins for the translation. So maybe that's the subject that's interesting people, which are frustrated with the current state of the translation in Jenkins. And I agree with you. I think there's a lot of room for frustration there, right? Because, because it's just more comfortable for a Russian developer to see things in Russian language, likewise for a Chinese developer or for a Korean developer. And, and yet those translations are in many cases quite weak. So, so yeah, or missing, they've got big gaps in, in not being up to date. And I think crowd in enterprise is a great step for us to find ways to make them much better. Crowd in enterprise coupled with continuous delivery of plugins has been a treat because last week there must have been five or 10. Plug in changes that came in that were released automatically because someone merged a new translation. And guess what? You get a new translation. You get a new version. Boom. Great. So mark this next one. Mark to propose me that for bison bisecting with Basil. Right. So I've just got the action. I'm there. Basil and I have agreed that as a developer topic, and this is developer centered again, not user centered, but as a developer topic, highlighting how to use get bisect to very effectively and rapidly identify where a problem was created, was injected into Jenkins. It's, it's a developer centered activity. But what Basel's detected is many people don't know some of the foundational capabilities that get provides in order to help us identify exactly which commit created a problem. There's at least one. There's at least one audience for that. I'm, I'm interested. I just know the feature by, by name use it a couple of times, but I'm interested to learn from a man of the trade. Right. And I think that's the story, right? Is that is really many, many people know that there is the concept of bisect and that it exists, but we don't bring it out of our toolbox often enough to be confident with it. And Basel has used it very confidently and has, has enough experience with optimizations that he can use in Jenkins specific that not just do we get a story about what is, how does get bisect help us, but how do you apply get bisect with maximum speed in the Jenkins project? Yeah. So I'll be proposing that one. The proposal probably won't go out till next week just because this is busy week. Yeah. Mark, can I be annoying? Yes. We, we had two other topics. Oh, yes. And we should put those on the list too. Absolutely. So let me put those on the notes that thank you. That's right. So you need help. I just need to negotiate. I just need to negotiate. I don't think that those are really a help thing. So, so good question to give some background. Yeah. Fixed it. I pressed alt A when I shouldn't have additional meetups to propose. Accelerating Jenkins builds. This is this, what this provides is a build caching. Yeah. And then accelerating. Jenkins testing. Test automation. With launchable. Yeah. And what this does is. AI based test selection. So it's using pattern matching to. To decide which test should be executed and which tests could be ignored for any particular job. And the reason this matters is today. A Jenkins core PR. A Jenkins core pull request. Needs four hours. Of compute time to evaluate it. And you can imagine that many of those pull requests are executing tests that are unrelated to the change. That is being proposed. Right. You can envision that as large a code base as Jenkins is. When I submit a small change to one Java class. There are many, many tests that will be executed that just aren't relevant to that. That change. And launchable is, is a conceptual idea of. Hey, let's find the most valuable set of tests and execute them. Them in preference to others that aren't as valuable. Mark, you, you gave me another argument to continue chasing you to organize these tests. I'm, I apologize for that, but these are great subjects. Great little thing I heard about that, but. Yeah, they are really great subjects. Couldn't they be transformed to a CFP proposal for DevOps world? They could be, but the problem is what, what these, what these talks are, or what these, these meetups are is to introduce some of the, the concept and announce the experiments we want to run with Jenkins infrastructure. So we, the challenge is when I talk about these things, I'm talking about hypotheticals because we haven't run the experiments yet. And what the meetups are is to announce to the community. We're going to do these experiments and then we'll share the results as we learn. And great. A little enterprise has been willing to, to support the experiments here with build cashing and. Kosuke Kawaguchi has expressed his interest in supporting the experiments with launchable again in the Jenkins project. But they, they would both just be experiments as we. Try to see if the, the hoped for optimizations provide real. Performance improvements in our use case. The greater enterprise when, for instance, there are some experts in Jenkins who have said they're not sure that that will actually provide a, a detectable significant benefit. And it, until we run the experiment, we just don't know. Okay. Thank you. Hey, anything else? All right. I think we can. End. The. End. Anything else? All right. I think we can. End the. End. End. End. End. End.