 Oops, wrong session, there we go. Welcome, this is Jenkins documentation office hours. It's the 22nd of April in Asia. The time zone we sent her this one on. So thanks for all for being here. And topics I've got, news, Jenkins changelog for the upcoming LTS, Sheikot Africa contributon. Those were the most pressing ones for me. I don't think we've got anything to report on last week's topic. Where do we place upgrade instructions? We had a decision from it. And I don't know that Sahidjah's, I haven't seen anything from Sahidjah proposing a change, but there are many, well, we'll talk about it when we get there. So current status is worth discussion. Any other topics, go ahead. A quick update on GSAC. Oh yes, Google Summer Code. I have nothing, I'm just curious. Yeah, that's a very good one. Google Summer of Code status. Let's do that as well. Any other topics that are hot on the list? Look through. I would propose we not touch on open PRC just cause I'm not ready. Oh, I take it back, there is one more. It is a governance board decision on the logo change for www.jankens.io. Okay. Raise our voice against the war. Okay, so I'll show that one briefly as well. Any other topics? Okay, then let's go ahead. So one item of news that I think is really, really interesting is, I find it fascinating, Alex Brandis, known in the Jenkins Commits as Jenkins user, not my fault. Yes, don't mean that as university student, I'd never choose a name like that, but good for him. That's great. Has led us through a series of steps to enable CrowdIn Enterprise, which is a translation support web user interface to help us get more translations and easier, more easily collect translations of the Jenkins UI. So I'm gonna open it just so you can get a hint for how it feels. It's really, it's quite amazing. So here's the schedule build plugin and there are the translation files here available. And I can, by clicking one thing, I can enter into a translate mode. It offers me machine generated translations where I say, oh yes, this is a good choice for the Italian translation of time zone. I've now contributed, someone else comes in and does the proofreading to say yes. And then after contribution and proofread, CrowdIn will automatically submit a pull request in the correct format to our repositories. Oh, wow. That's really cool. It is wildly cool. Yeah. Wow. I mean, translating before was the current translating techniques is this horrible experience of editing Java property files and trying to get the character set correct and trying to do all sorts of exotic things. And this just makes it magically easy. So it's been demonstrated in the Dock's Office Arrow as Europe time. We will schedule a Jenkins online meetup to show this to other people, I'll highlight to them just how easy it is to do. And we'll begin steadily adding more and more projects to these things that can be translated. So it's right now, I admit it, I'm using very simple ones, right? We're using the design library that Alex had created with Timzrich Home and that you can see on weekly.ci.jenkins.io. This is the design library is a new way of showing people examples of how to interact with the Jenkins UI and how to write Jenkins UIs with the new Jenkins UI facilities. And so it shows all these things. The cool thing about that story is it's also translated. And it's been translated with crowd in. So in this case, Alex Brandis has started the German translation and we'll go forward and make more translations as we go. So really quite an elegant setup that's happening here in getting more languages supported in Jenkins for native language users. We will eventually enable it for Jenkins Core. It's very usable with Jenkins Core. It's just we're not sure we're ready with all the processes to make it successful with Jenkins Core. We know how well it works with Jenkins plugins. Aha, yeah. So any questions there? Special thanks to crowd in for their enterprise license. It's how they do things for open source. We're very grateful. They've been this amazingly supportive bunch, just wonderful for how much they've helped us. All right, next topic. Jenkins LTS 2.332.3 change log and upgrade guide. The release candidate is built and being tested. Mark, to write the change log, submit the pull request. I'll mention both of you in the pull request to ask for your review. And we'll mention Dirage and several others just to invite reviews so that we get a good review process. Okay. Any questions there? Okay, next topic then is Shikot Africa Contributon. Here we've got three projects and a project manager. So there are seven women from Africa who are actively participating. The first project inclusive naming. So seeking out and replacing master with controller, slave with agent, et cetera. And the cool thing there is these women are paid to be being paid to do this work. So they're doing the search, they're learning how to use GitHub. I'll actually be presenting a, I'm presenting a tutorial on interacting with Git and GitHub this Saturday. And if you are interested, you're welcome to attend, no requirement. Pipeline help is the other one. And this is the same project as last year. Then one more was the screenshot update. And this one has been fun because they're running Jenkins Weekly to prepare the screenshots. Since Jenkins Weekly is the most up to date and we will very soon choose the next LTS baseline. Ooh, ooh, good point. I should note that. Next LTS baseline selection proposed to delay two weeks, two to four weeks. We had many regressions and we're taking active steps to reduce regressions before we choose the baseline. So it feels very promising on Sheikot Africa. We just started, we completed the community bonding period and have started project work. That will continue, project work will continue for four weeks, then a two-week shutdown period, then a two-week end of project. Right now I'm a little concerned we're short on a number of mentors, but we've got Kevin Martins, Bruno Verrachtin and Angelique that have all connected in the Slack channel. And if you're willing to do asynchronous, you could certainly connect to the Slack channel and do it. We do have meetings weekly and working with them as they make progress. Any questions there? I just, you said you have a project manager, so is one of the Sheikot Africa? Did you go ahead and do that? Do you have an assistant? How's it working out? Exactly, Nafisa. Nafisa, she's great. Oh, my sakes, it's wonderful to have someone who says, Mark, could I do that for you? It's a great, and that's just the sweetest word you've ever heard, really? You wanna just do, she says, would you like me to send the reminders to people about meetings? Oh, yes, that would be wonderful. How about if I do this for you and that and she reminds them, hey, be sure you update your project documents. So instead of one voice, me harping away, there are two and she's doing great. So very, very nice, yes. Too bad you can't keep her permanently. Well, that's part of the delight of this, right? Is, wow, what a treat it is to have somebody helping in that way. Right. All right, so any other questions or comments on Sheikot Africa contribute on? All right, next then was, the LTS baseline selection had been scheduled for yesterday, it was not selected. There were, there are still quite a number of UI regressions that are open. There's a dashboard available on issues.jenkins.io that shows what the UI regressions are. Six or eight of them were resolved on Tuesday's release. So very, very good progress. We hope to continue making progress over the next week or two and then choose the baseline. That means it will delay all releases throughout through the rest of 2022 by two weeks. We're not gonna try to hide this delay anywhere. We're just gonna change the release dates as the proposal. Now that's, and I call that a proposal not yet fully accepted by our release officer. He's in the middle of a move and busy doing things. So we haven't got a final conclusion from him. This is what we hope will happen. But this is the release you said with all these UI changes coming, right? Exactly. The last LTS did many significant and very nice UI changes. This has even more. Yeah, it's, I loved it when Olivier Van Nel, our former infrastructure officer said, hey, I came back and was using Jenkins and it's quite different, very nice. So it's fun to have people, oh, that's cool, nice UI. So it's improving. Any other questions on LTS baseline? Okay, next topic then, Google Summer of Code. Thanks to Kristin. She's got one of the project proposals. It came in for the Pipeline Steps Dock Generator and we've got review, we're in the review period now. Potential mentors, review and comment on the proposals. And then we've got about, I think it's two to three weeks for that. Then the org admins submit our proposed priorities. Mentor lists, I think is part of this and requests for number of slots to Google. Then they go into a period where they choose which projects Google then chooses the projects that they're willing to fund and the projects start. They announce it and then projects start. So how many proposals do you have or how many good proposals? I think we received, I think Alyssa told me 18 in advocacy meeting. Oh, wow. Now that's actually, apparently Oleg said previous years we'd had as many as 40. So it's lower than in the past but given the number of mentors we have, 18 is a very reasonable number, right? My personal sense is if we can run three or four projects in the Jenkins project, I will be delighted. I won't be surprised if we only run two. We just don't have the same pool of mentors as we've had in past years. Yeah, and I think I've heard that in general the number of submissions this year are way down. That seemed to be the noise in the org admins mailing list. Yeah, I've seen that too. I was wondering, I think someone brought up a really interesting point about how maybe it's because people, things have not come back to in person so there's not as much talking about it as previous years. So I was like, oh, that's... Yeah, it certainly, well, and there are, certainly we had a very, the Jenkins project had a very different group actually running Google a summer of code to Google. It looks like Jenkins is a very experienced project but to us internally inside the project we had two brand new people who had never done Google summer of code before and one who had been a previous student. So we feel like we're brand new still learning how to do it, how to promote it and we're delighted with the response we've received even if it's less than previous years. Yeah. So just a reminder to Kristen, to me we've got to do our reviews. Yes, yes. We're in the, there's some work to be done and we got to do that work. Are you doing anything for Google summer of docs or just doing the summer of code? Oh, good question. So Google season of docs, season of docs has their proposal period I think has closed and we intentionally decided not to do it. Okay, we is Royal, we, me, I, Mark, wait decided not to do it because I just didn't feel like we had the capacity. Yeah. The one time we did it, I felt like it worked out okay it's just it needed more engagement. And right now my focus is on helping Kevin Martens as he gets ramped up into the Jenkins project in documentation. Yep. And having that next year you may be able to really do something dynamic. Right. And we may have him be able to mentor somebody in Google season of docs in 12 months, right? I mean, there's a potential there we just grow people and let them help so that I don't have to. Yeah. All right. Anything else on either summer of code or season of docs? Okay, next topic was upgrade instructions, current status, let's do a quick check here. I haven't looked, but I don't think I've seen a poll request from Sahitya proposing upgrade instructions. Nope, nothing. And that's no shock because it's surprising the level of complexity hiding in this thing. We haven't documented it ever. And I thought, well, that's because it's so simple. And the more I've explored it, the more surprised I've been, oh, oops, it's complicated in this way. It's complicated in this way. There is a stack overflow page, for example, from five or more years ago that describes how to upgrade Jenkins and describes it exactly wrong. It's total mess what they described there. And there are three or four answers, independent answers, each of them being wrong. It's like, oh, yes, you install it with this and then you upgrade it this other way and you use, you grant root, you change the permission on this file that the installation created. It's like, no, no, no. So there are many, many mistakes to correct and many ways to make mistakes when doing an upgrade. And it was, I was dismayed. I thought no one would ever install with a Linux package manager and then upgrade manually. That's just, that's second wrong. And in fact, that's what this thing described is doing exactly that, upgrade manually. It's like, oh my no. So all sorts of interesting hiding in that. Indeed. And that doesn't talk about windows even where it's a whole different thing or Mac OS where you had another different thing. Okay, any questions on upgrade instructions? Okay, the next topic is sort of a hot one. This is, there had been about three or four weeks ago that had been a proposal come in from Ksenia Nanashiv actually with a pull request proposing this. We've got, you've got to see it because the, I love how the preview site works that Gavin Mogan has provided for us. So here it is. This is one alternative she proposed. All right, there's one. And now here's the alternate. So when we brought that one to the governance board, one of the board members noted, hey, the Cossack may not be a positive image into some people who know Ukrainian history. And so we put it to a vote and actually invited people to vote between that one and this one. Ah. Okay, so oops, too big. There we go. So the choices were this one or this one. And this one, the Jenkins image with the open eyes and the flag stopped the war, one by a slight margin. And it was a relatively slight margin, two or three or four vote difference between them, if you will. Okay. So not a huge one, but the governance board approved on Wednesday that this is the one we're going to use. And special thanks to Ksenia. So the colors in the background behind are colors of the Ukrainian flag. Right. And we continue with this message on the site that encourages people to donate to the International Committee of the Red Cross and other donations to support the people of Ukraine. Right. And both of these are just marvelous work. Remind us just how good Ksenia is at what she does. That's really what a treat. Very talented, yes. I wish I could do things like that. That's just amazing. Great. Agreed. Why don't we do more though? We've got the female Jenkins now. We just had that. We don't modify that one for anything. Certainly, spinoffs of that could be done as well. I think you're referring to this one, Meg. So this one came from, let's see, who was it? It was a group in France that provided it. And I was like, the women's Java? Yeah, I should be able to find the name here just a minute. Where is she? Come on, in the artwork. Paris? Why don't I see it? OK, clearly my ability to resolve images is really sad. There it is, there it stops us all up. Oh, yes, Duchess. And it was Duchess for it, that's right. Yeah, exactly, it's like we're all like trying to see it as quickly as possible. Yes, yes. Right, and I agree. But for me, that one, I like it just exactly as it is. I think that one is just delightful. I agree. So and thanks to Duchess France for their work as a group on that. Yes. They were actually a great contributor team to the French localization during last October Fest. I look forward to even better involvement with CrowdIn because it's much easier to do translation. They did it. They did it the really hard way. And now we're going to have a much better way in time for October Fest 2022. Oh, yeah, OK. Yeah, and really, translations are a great way to contribute truthfully. It's it's marvelous to read Jenkins in your in your native language instead of having to do it all in English. Great. All right. Any other topics before we close for today? OK, well, thanks to both of you. Thank you. Oh.