 Welcome. This is Jenkins documentation office hours. It is the 29th of April, Asia time. Thanks very much for being here topics I've got on the agenda for today include news. Google summer of code she code Africa contribute on we should probably also include Jenkins to dot 332.3 LTS change log and upgrade guide. Let's see. ongoing prep for June LTS discussing baseline selection. rough draft or review of changes. Since 2.332.33.x. Any other topics. Chris, were there topics that were specific for you though we should maybe we should talk about localization, localization, internationalization and localization meetup. May 12. And crowd in is the thing. Okay, good. Great. All right, so by way of news we've got a weekly 2.345 has been released. And let's see other other items that's, I think that's the big one. Google summer of code. So we are in the proposal evaluation. By potential by potential mentors. And that is due by end of this week is that right Chris. Org admin. Oh, go ahead. Excuse me. Thanks. Then org admins do further further review prior petition and submit to Google. And then Google selection selected projects are announced in May right. Yes. We wish everyone all the best. We look forward to that and hope we have several selected for Jenkins. Chris anything else you wanted to mention on Google summer of code. Um, no. Okay. She called Africa contributon is ongoing so the inclusive naming project has found several places that need updates. This is the word master be needs to be changed to controller word slave needs to be changed to agent. Blacklist to a better phrase where the better phrase depends on the context, and likewise for whitelist whitelist. They were in those two were never particularly helpful phrases we use them as secret keywords to describe the meaning of something that's been banned or not banned, or a specifically allowed. Then the, the screenshot updates project has found many screenshot many screenshots that need updating. And they're using Jenkins weekly to create the screenshot so that they are close to what June LTS will look like. That means they're actually a little different than what the current LTS looks like. Yeah, and I'm I that was a we've had fun with doing that one because finding the pictures and then taking them. I did a demonstration today and in the demonstration today, promptly showed why it's difficult to create screenshots correctly by taking exactly the wrong screenshot and creating a pull request with it. So, fix that. That's a good teacher mark right sacrifices you make for your students are showing showing by total hypocrisy complete failure this is how you fail to do the task and then let's let's fix the damage. The pipeline help project was somewhat of a struggle today. Because we picked a plug in that was difficult to add help. And so I've got we've got more work to do to find places and examples there. And I'm going to go on the chicode Africa contribute on it ends ends mid May. Then two weeks of two weeks of wrap up of conclusion and final reports. How are the participants going doing though are they having fun or they. I think I think they are. It's a little slower than it was last year. But I think there we've had everyone's plans and ideas reset as necessary to be sure look, we're here to learn about open source together. We're going to show you some things that may surprise you you're going to learn some things we're going to learn some things and that's those have turned out to be positive. Good, good. The next topic then was the Jenkins LTS change log an upgrade guide the PR has been submitted reviews are encouraged. And the PR is at. I should put it pasted in here just so that everybody's got it if it helps me. Yeah, here it is. And if I remember correctly you have to look at the screenshot the preview doesn't work because previews are only available for weeklies not for the LTS previews. So look at the picture but the picture is included. Any questions on that LTS change log an upgrade guide. Okay, so next topic is the ongoing prep for the June LTS and this is a big one because there are significant UI changes. I'm grateful to to Jan Farachik and to Tim Jacome for their work for buzzle crow's work for Alex Brandes for three or four other contributors who've all been involved in UI improvements in since 2.332 dot x. Oh, we've got one more item, which is require Java 11. Java 11 is now planned for the September 2022 LTS. Right. So Java eight end of support by the Jenkins project. Any questions or concerns there. I think most of the African people while they're looking at screenshots watching I think most of the Java eight stuff is gone but are they watching for it. They are not it's been it's been that's a good suggestion. I'll, I don't know that they are, they would be able to detect which things would be would be Java eight specific and which wouldn't. So you said Java eight. So for text we can always do get grep to find any. But it misses the screenshots. Yeah, good point. Although that seems likely that if it's got something that's Java specific in a screenshot. It's probably. Yeah, I suspect it'll be detected but I'll remind them good suggestion. Thanks. Thanks flag them for now is suspicious or. Right exactly just adding them because what I've got is we've created a sheet of screenshots that we have pages. And then as we as they visit a page they mark does it need a screenshot update or not. Okay, yeah. The pages will use that list, even if they don't get through all the pages themselves that list could be used for others to do screenshot updates. Oh yeah. Okay. Any other questions on the Java 11 Java eight end of support that require Java 11 project. Okay so last topic then for me is internationalization and localization I've got to show you this one. Chris, I believe you're a native speaker of Chinese aren't you. Oh yeah. Okay so then you are an interesting candidate for this one. If you would be willing to help us with the experiment so this is crowded in Jenkins.io. What it is is a localization facilitation service that submits pull requests to Jenkins plugins with translations. So so what what we've done here this is okay admittedly this is not a very popular plugin we intentionally use one that was not popular so that so that no one would be dismayed. Or if you want a popular and very interesting plugin design library plugin. What it allows is it allows a contributor to contribute translations in through a web user interface, instead of contributing them through heroic efforts that they have to do by editing property files now I don't. It doesn't offer any machine generated translations into Chinese traditional and I'm not sure why, because for example, if I do the same thing in Italian. It actually offers me. Come on, come on. It will offer me machine generated translations. I'm not sure if they just don't do multi bite really well, or, or what it is but we're certainly interested in feedback from people. How does this feel how does it work for them for for people who are native language speakers. Do we have anything in a different alphabet. Well, Russian. That's a good question let's see what else we've got so we don't have any. Let me look to see if maybe, maybe design library plugin has some multi bite translation, just a minute, because I'm not sure that I know there's none in. I know there's none in the. No none none have been translated yet. So there's nothing multi bite here. And we're doing it with just plugins for now just to get an understanding of. Yeah, what, what does it mean. Oh no look, there it is it's offering a translation okay. Okay, now Chris, while you're here. Can I have you look at these machine generated translations. Do either of those look reasonable to you. The first one is okay the second one looks kind of weird. Okay, alright interesting. So, so this one didn't look unreasonable to you. Yeah, it looks okay. Interesting. Okay, well so that's, that's, I'm going to dare to save that because. Now this one. Oh hey they got it right here when we did a German translation earlier today, the, the code L colon main panel and code thing was incorrectly translated into local language. Now do any of those look reasonable Chris. Similar except. Let me see which was the best one. I think the third and fourth ones are quite similar. Yeah, and as I look at three and four I the only difference I see now I don't have. I certainly don't read multi by main dash packer versus main dash panel and main dash panel is the correct one. At least for the non translated string. I think the second one is the best second one okay. So, I'm just going to go ahead and save this because now this gives a chance if you're interested later Chris you could register with this site and I think you may be able to make yourself a proofreader. And then come in, come in and say hey look it did it. And then within 12 hours a poll request will be submitted to the plug in proposing that localization. Okay, okay. And it comes by GitHub poll requests which mean, which means we then we just use standard poll request processes to, to manage it so I can show you one that I just processed today from schedule build plug in. It came in looking like this new crowd in translations. Okay. And here's what changed the section title I kept it schedule build plug in and then horario pre definite to the construction and panification, which is some sort of Italian. And zone or area is actually pretty close, at least for the limited Italian that I do. So I'm, I've been really impressed we're going to do a session on this May 12 and show, show people one how do you internationalize. And then to how do you use crowd in to encourage others to help you translate into local language. Yeah, I am, I am really impressed and thanks to crowd in enterprise they've given us the license for free. So we, we get all sorts of benefits from what they're willing to let us use their hosting the service. All we do is is hook it up to our repositories and they'll submit full requests. So we'll have a time when say simplified Chinese will be partially, you'll look at it and some will be in English and some will be translated. We already have that right so they're, there are plenty of cases where we have, we have actually and I can go ahead and proofread this I'm going to say yes to both of them because Chris was here. So, so we already have that kind of partial experience today, what this will do is allow people to help us make more and more of the strings translated into local language. Right. So what if one of the ones that isn't well translated can you, can they go in and change it. Can they be word or edit it or something. I think so I think that this gives them a facility to say, hey, I'd like to alter something here. So whoops, I clicked the wrong thing I need to click. Instead of proofreading if I click crowdsource here, then I could change this to be. Piano. And it does allow corrections now in my case I definitely don't want to correct that, at least as far as I can tell it does now we're, we're still learning. This was first introduced to me by a student in Germany, Alexander Brandus who's been actively involved in UI improvements and it's, I'm quite impressed. Any other topics we should review today. Okay, well that was that's pretty simple. We could look at some old PRs. Unfortunately, Meg, I'm not. I've not got capacity right now to make any progress on old PR so I'm hesitant to bring them again. We've certainly got lots. There are 38 open. We've proposed blog posts, etc. Actually, I guess there is one do any are any of you Mac OS users. Not willingly. Okay. Chris, did you say you are or was that a no. Oh, okay. So, so Chris, if you'd be willing. I need somebody who's got access to Mac OS, who can see if, if this proposed phrasing makes sense. I'm not a Mac OS user and me approving it feels feels like I could make things worse rather than better by saying yes. So what they're describing is something about how to make user local bin accessible to a Docker image. And that surprises me in all sorts of ways so I don't quite know what to think of it. If you were would be willing to review that do you mind if I tag you in this just to ask hey could you help me. Yeah, sure. Oh, thank you. Okay. Thanks very much. All right, any other topics for today. Okay, then I'm going to go ahead and stop the recording. Thanks all terrific thanks everybody.