 All right, welcome. It's the 6th of May 2022, at least in Asia. And we're grateful to have everybody here. Thanks very much. Agenda topics I've got for today. News, Google Summer of Code and Chris I think it'd probably be best if we had you be the voice on that rather than me. And then she code Africa contribute on I can talk to that one. Then other topics ongoing prep for the June LTS baseline selection I can talk to that briefly. Java 11 plan and internationalization meetup. Any other topics that anyone wants to be sure we add. Okay, alright so this one actually Chris this one is Asian language complication. That is being investigated. It'll be a fun one to discuss remind me to talk through that one because multi bite languages have an interesting twist on that one. And by way of news. We've got a new long term support release. It's out and the new weekly came out as well both looking good and running and seem well behaved. We did have a upgrade guide addition. After the release. So crow. I like that when other people propose upgrade guide changes, and in this case it was a change to a logging behavior change that was introduced related to reducing memory pressure. I want to share with us what you can publicly remember we're being recorded so no saying anything you're not allowed to say, how's Google summer of code going for you as an org admin etc where are we in the project process. Okay, so we have selected a few projects we would like to accept and we are in the process of contacting and confirming with the potential mentors that supplement mentors about mentorship. I think we are about ready to submit the names to Google. That's about it. Excellent. Thank you. Okay. Yeah, and as I understand it, it will be late May before Google announced which projects worldwide have been selected so we'll go into a quiet period once you've submitted they then have to process right. Yeah. Excellent. Well, thank you for for leading that thanks very much for being an organization admin. Okay. So the, the she called Africa contribute on the inclusive naming process project has had pull requests already merged. First pull requests have been merged. And the participants have learned more about GitHub and how to use it to search and to submit pull requests. Yeah, we did a we actually did a two I did a tutorial and showed them how to do a multi file pull request from the GitHub web UI. Wow. I know I know it was like really that's scary. Yeah, it worked. And they now have a recording of it so they can use that, and they'll be able to use it after they're done with a Jenkins project in other areas professionally and otherwise. Indeed. The screenshot updates project we've had our first pull requests merged there as well. And those those first more merged pull requests have been using Jenkins weekly to show the most recent UI. It will be included will be included in the June LTS because the June LTS baseline has not been selected yet. So for the moment there are some screenshots that are outdated or that are newer than the the LTS version that people are running. Any categorization of where they're finding the screenshots that need replacing or they just everywhere. We the things we looked the bulk of the most of them were are in the user handbook. And then a few are in tutorials. And what sort of issues are they needing to be replaced for just everything just that the menus menus look wrong. Or the plugin manager layout is incorrect. Okay. Is outdated, you know if you if you put a screenshot of the plugin manager 12 months ago, it's a completely different look now. Right, right. Okay. And we haven't I haven't seen any Java eight references at all. So, so in, at least in none of the screenshots that I've seen so far. This worry does not seem to be a significant worry. Excellent views. So on pipeline help. We today guided them to the get plug in for a very specific point of embarrassment that that I had found so there's no checkout SCM examples in the get plug in docs. So, potential use credentials in pipeline examples in the get plug in docs, it's like, oh dear shame on me. So, pointed them to those. There is still more work we need to do to find the ways to reliably add top level house help. So adding top level help to pipeline keywords. in a plugin is somewhat of black art, somewhat problematic, right? I'm not always able to find the exact place to put things to be able to add the help. And I think that's one where I may have to go begging people like Daniel Beck or Jesse Glick to give me some tutorial on how does a plugin find its associated help file so that we know where to put it. All right, okay. Now we're about one to two weeks away from the official end so and then we'll do a two-week conclusion and final reporting. And your project manager's working out well too, still? Oh my sakes, that is wonderful. Yes, she's so great. Xenob joined the Docs Office Hours for Europe earlier today, so yesterday, Asia time. And I was able to tell her, oh my sakes, yes that project manager role has been just wonderful. We must be sure we do that again next year. Wonderful. Yep. Any other questions on Shikot Africa? Okay, next topic then, ongoing prep for the June LTS baseline selection. So here the story is that I had asked for a two to four-week delay in selecting the baseline while we worked on regressions. And we're now, let's see, it was April 20th. So let me do a quick math thing here. It was calendar. So April 20th was the original baseline selection date. So we are now officially two weeks and one day delayed. So we're now inside the window, but things are looking much better. We hope it will be next week's release, next week, the next weekly that is selected, or one after that. And what that would mean is the June LTS moves from June 1 to either June 22 or June 29. Any questions on that one? The big hit there is I need time to prepare the summary of changes because there are all sorts of things that need to be highlighted and indicated to people. And glad that we care more about the quality of the release and the date. Well, that was the thing for me is we learned by heart experience that when we made a major change like tables to divs, we had an awful lot of people who struggled with it. We hope that this one will have less struggles, but it's the same kind of change. It's quite dramatic to change the UI. All right. Any other questions on the June LTS? Okay, next topic then, Java 11. So today we support Java 8 and Java 11 fully with Java 17 in preview. The proposal is that September 2022 LTS will no longer support Java 8. And that means that we'll do a drop support for Java 8 in a weekly well before September. The final date has not yet been selected, but it could be as early as June. And this is for running Jenkins. Can they still do use Java 8 agents? Well, so they don't need to use Java 8 agents. So this will drop support for the controller support would end and the agent support would end, but they can still use Java 8 tools to run Java 8 compile, build and test from inside an agent that's actually executing with the Java 11 JVM. Good. I've run into people who got confused by this in the past. Right. And that's an important point we need to note to people. Look, you can build just like you can compile C code with a Jenkins agent. You can compile Java 8 code even if the agent itself is running Java 11. All right. So date to be determined and communicated. So any questions on the require Java 11 story? All right. Next topic then, and this one is one Chris, Chris for your info. So we've got on May 12th a localization meetup that we'll have where we're going to look at and show how crowd in enterprise has donated a license to use their software there and they host the software themselves for translation support. And so what it does is it allows us to have a much better experience translators and proofreaders to have a much better experience working on Jenkins. Did I show it last week? I don't remember, Chris, if we showed you a tour last week, you say we did? Yeah. Okay, good. Then no need to show it again. We did discover last week a surprise or yeah, middle of late last week, there was a surprise detected that Asian languages naturally are written by crowd in as UTF-8. That makes sense, right? That's that's how we do it now. But the Jenkins property files assume ISO 8859.1 with encoded with backslash you encoded UTF characters UTF-8. And so right now Alex Brandus is investigating what alternatives are available to make that work better. We think there are possibilities like we write a little translator that converts UTF-8 to the encoded ISO format. The other is we could we may need we just wait until Java 8 support is dropped, then use new methods that are UTF-8 aware. Now this is only for the Asian languages that use non-Roman alphabets, right? Well, so it's not just yeah, I guess what about Cyrillic? Is that affected? They are also affected, right? So so Cyrillic is affected. The Hebrew the Hebrew characters are affected. Anybody who uses a non-ISO 8859.1 encoding and ISO 8859.1 is actually a relatively narrow set of Western European character sets. So we think there's we we can see we think we can see a solution. It's not clear which solution, but we can see a way to solve it that will let us use this tool for for Chinese language, which is simplified Chinese, traditional Chinese, Japanese, Korean, Russian, Hebrew, etc. Any questions there? Do we just for nitpicking? So do we want to call this Asian language or do we want to call it languages that use non-Roman alphabets or something? Yeah, so I'd actually call it UTF-8 because it's it's really yeah non-ISO 8859-1 if we're going to be going to be precise. It's because it's not it's not anything about the different syntax of the languages. It's just a character set. It isn't, right? And it's not about whether they read left right or right to left, right? It's be it's just if they're using something that's not an ISO 8859-1 character set, whatever that is, whether that's Greek or Karakana or the Korean Hangul, you know, any one of those, it would still have the same kind of problem. All right, those are the topics I had. Any other topics we want to bring? You're not volunteering one topic, so that's the answer, which is fine. We don't even need to mention it. I apologize, but we can talk about old PRs if you'd like. Right now I don't have any story to tell on them. And I haven't been reviewing them. I'm too buried and other stuff, so. Right, that's been my feeling is I've got projects right now that are certainly keeping me hopping. Is it like anything? Something that I wonder about is when we get through GSOCs, we've got the Shikot Africa, and then we've got GSOC. And is there ever a time like this fall where we could call a special meeting and invite a lot of people who don't normally come to this and go through? We've got an awful lot of open PRs that are very old there. Well, and see if we could get rid of some of them. Well, actually, I think that's a that's a good task, eventually, for Kevin. Kevin Martin's to take on and say, hey, help us do a triage of the triage and close or revise or close the outdated pull requests, because we've got some that are potentially useful, but haven't yet finished. And then the question is, is it easier to finish them or abandon them and close them and bring them back? The embarrassment for me is we've got one pull request that's from September of 2019. So we're I'm clearly not keeping up. We know, but under your we used to have a whole bunch that were from 2019. So we're down to just one. You've done some work. Well, we've got three still. And here again. And actually, one of those is is related internationalization. I may crack that one. That's a good one. Because it was trying to move information from international on internationalization from the wiki to Jenkins that I owe it may be worth trying to see. Hey, can I get this? And it's got some feedback. Good. Okay. Okay. Anything else? Chris, anything from you? Nope. All right, well, I'd propose, let's call it done. And I may actually take this opportunity and go through the this pending pull request, resolve the conflicts and see if I could get it over the line prior to prior to the that internationalization session. Yeah, cool. And then, oh, and then we're going to have to update it for the new tools, certainly. Well, that's that's part of the benefit here is knowing that this thing's available. It may be that the ideal thing is I use it. I've got several plugins I need to internationalize, follow the instructions here as a way to test. And then having internationalized, then we go go ahead and we've proved it works and we publish it sounds good. All right. Well, thanks, everybody. Have a great week. Yes, thank you very much. We will talk next week. See you next week.