 Welcome it's Jenkins documentation office hours it's the 17th of February 2023 Asia. And so we've got some items that I propose for the agenda so action items. We had Google Summer of Code preparation last time. Rajiv we could talk about that one again if you're interested Jenkins awards. Preparation transition to Java 17 and end of life checklist has been discussed. Preparation for sento seven end of life. And that was about it. Rajiv are there other topics you'd like to add to the list. No, no, I don't know. Okay, we can wait for this. And I was assuming we could spend time on Google Summer of Code preparation. So, so that's a great one to have you. Hey Meg welcome. Nope still no sound from Meg I see Meg twice but no sound so let's go ahead then. So how about while we're waiting for I see your picture now Meg, but still no audio. All right, well so if you can hear Meg that's great so there are some pieces while you're working on figuring that out let's go through the easy parts of the agenda, the kind of, we can just keep you informed and then we talk about it from there. So one of the items is Jenkins awards 2023 I'm going to move GSOC preparation down and we'll see if Chris Stern joins us. Okay so Jenkins awards 2023 each year, the continuous delivery foundation proposes and accepts nominations for three awards in the Jenkins community, most valuable Jenkins contributor security MVP, and most valuable Jenkins advocate. So what we do is we submit nominations by. So we nominate by adding comments comments to the GitHub issues linked to there. Hello, can you hear me. Yes, you can see here you just great Meg. I don't know why but all of a sudden I could hear you okay continue. All right so these the Jenkins awards are open. It opens. The nominations close the March, the third of March. So, submit your nominations, you can self nominate, etc, but submit nominations, etc. Now, as a matter of rule, the last the winter some last year can't win it a second year in a row. That means that this one. So, who was that candidate last year won't be eligible this year. I believe last year Vodek felonier was the security MVP, and therefore not eligible. Vodek was the security MVP and also then not eligible. And then most valuable Jenkins advocate I believe this was Darren Pope last year and again not eligible this year. Alyssa Tong has gotten that started and it's administered by the CDF but we host the nominations in our repository. Any questions on Jenkins awards. Okay next topic then documentation transition to Java 17. Beginning in April or May of 2023 Debian 12 release and Debian 12 at its release will no longer deliver Java 11. It will deliver Java 17. Because it's delivering Java 17. We don't want to sets of documentation. So we intend in April or May with that release to switch the default description of our installations to use Java 17. So Java 17 is already supported. Will you will just will switch the direct the instructions to use it as the default. Java 11 continues to be supported. We look forward to making that transition. Now, Tim or no, Kevin Martins has the action and we share with Tim that that's the proposal from the documentation side. Any questions there. Sounds like a plan to me. Okay. Next piece was we've got a number of end of life events coming up for various operating systems. So Java 17 ends life in April of this year. Alpine 314 in May. Alpine 315 in November and then a year for whoops, a year from now or a little over 15 months from now. So Java 17 will be absolutely end of life. So the idea here was hey let's assemble a checklist that reminds us of all the things we need to do to properly end of life and operating system in in Jenkins. So that's that's one that's ongoing work. The idea idea there is Kevin will probably create a create a template. In the Jenkins docs repo, and then create copies of that template for each obsolescence, each end of life. So the if this is patterned after, after the release checklist or the real, yeah, the release. Yes, after the release checklist that we use for Jenkins LTS releases. So it's just a nice thing to have a checklist that we use to work through. Hey, how does have we done all these things as we reach end of life on an operating system. Any questions there. No good idea. Okay, all right. And last is last. Yeah, last. We've got to I've got a proposal because I don't like Centos seven. And I admit it. It's me. I don't like it. Period. I don't like Centos X. Well, Centos seven has an ancient version of command line get an ancient version of SSH. And those ancient versions complicate complicate Jenkins plugins noticeably the get plugin. And I want to get rid of that complication. Well, as further argument why we should get rid of it. Centos seven Docker container has been deprecated for almost five months now. And the Centos project entered maintenance mode in 2020 and will end of life in 2024. So completely there won't be more Centos. Well, no more Centos seven for sure. They've, they've done a different thing with the thing they now call Centos stream that is the next. It's, it's a predecessor of the next release of red hat enterprise Linux. So they've shifted to be closer, more like Fedora than what what Centos seven was Centos seven was just a simple copy of red hat seven. Okay. Now we've got. So this is this is a difference from the past and that usually we would continue to support this thing until it's official end of support by the operating system provider. So we would typically have supported it until June of 2024. But given the Docker containers deprecated and given the pain and suffering caused by the ancient programs inside of it. I'm taking the proposal that I think I'm going to propose a Jenkins enhancement proposal that ends its life early. Does anybody have consequence use Centos. Oh yeah, yeah. For instance, Darren hope created a video showing how to install with Centos seven and they're quite a number of issues reported related to it. For instance, the big reason why this thing this ancient SSH was a problem for the get plugin was because of bug reports where Centos seven users said hey, your get plugin defaults broke me on Centos seven. The other platform was fine but Centos seven was broke. So did that answer your question make right so that I mean is there going to. Are these people are there people using Centos seven that are going to be upset by this. There will be but they'll be every bit is upset in June of 2024. Yes, because many of them will say I want to keep using it even though the project no longer supports it. And, and the answer is Jenkins will absolutely drop support it in June of 2024 because we won't support something that the upstream no longer supports. Right. So the idea is because our installer already doesn't support it. And because the containers aren't supported. It will be coming to a premature end of life. And since it's coming to a premature end of life anyway, let's make it explicit and declare it end of life. And so what we'll need is things like a blog post and timeline, you know, blog post timeline warnings to users from a Jenkins admin monitor. So that they'll get a little pop up that says hey, you're running your controller on Centos seven and Centos seven support from the Jenkins project will end in, let's say December of 2023, something like that. Just for the same way. Do they have any record I mean if they wanted to grab their own copies of the plugins and keep them updated for Centos seven etc. I'm sure they could, they could certainly fork the plugins and create their own private copies and decide hey I'm going to maintain it. That's not a typical behavior for a Centos seven user. That's what I yeah, that's what I'm just wondering if there's like a big company out there that's got some other though critical software that won't run on anything but Centos seven or something. They certainly because it's open source they could certainly maintain it themselves they could care for it and right now we're not taking any active measures to make things any worse. We just want to officially declare we're going to stop testing there. We're going to stop documenting there. And we're going to, we're going to make it here. Let's show what I like this way of describing it. It will become one of these. If we look at the Java requirements. This page says, oh no Java. No, that's not it. I want Java. Where this is. I'm looking for something different sorry Meg just a minute. We want the Java requirements page. No, I want the Java support. Oh, the Linux support policy sorry not the Java support for this one. All right so here's our Linux support policy we define three support three support levels, level one supported. All right, and in level one supported we say, hey we run tests of this thing. We test the container images. We run all sorts of different things to assure that they continue working. And that's where Centos seven is right now. There is a second layer where we say hey we don't actively test these, but they're still supported. That includes 32 bit things, a risk five and power PC other architectures that we don't support at the top level. But these are supported by their providers in terms of the platformer on the third level is this is reserved for Linux versions no longer supported by operating system providers. So in this case, we went to 16 is one of these. It's no longer supported by Ubuntu therefore we don't support Jenkins on it. Centos six is like this. The proposal is let's explicitly place Centos seven in this level three already earlier than June of 2024. It will be there in June of 2024 anyway. Fine with me. All right, cool. Centos I mean of course I'd like to stop supporting Windows. Oh, now that's terrible because I'm running the meeting for Windows computer I don't know what you're saying Windows is a lovely thing. All right. That covered all the topics I had Rajiv you as part of your work on Google summer of code were there any things that you wanted to discuss or questions you wanted to raise. So, I talked with Chris, so she said like, so Chris has updated some status page of the shop. So the thing is that I saw that coming. So we are waiting for 2022 Feb, where the list projects will be announced. And after that we'll have like session on that so we are waiting for the result, whether we will be selected for this project or not. Right. Okay, so after the announcement. There will be a weekly office hours for weekly Google summer of code office hours for org admins and mentors. Had you seen that announcement Rajiv. Yeah, so after the announcement you'll have a pick up meeting. Right, we can discuss on that. Good very good. And now you're if I remember correctly your past experiences with site generation and so you were interested in the doc site generation project. Yeah. So site generation for Jenkins that IO and you were willing to mentor. And Rajiv is willing to mentor based on your experience with a site generation project in a previous Google summer of code is that correct. Yeah. All right. So Meg for your info this is a project to use and Torah to build the Jenkins.io site. And to allow the docs pages to be version specific. Nice. Right right it's a it's a really it's a great idea. And the nice thing here is that Rajiv has done something like this in years past for another project as part of Google summer of code. So Rajiv is willing this year to help by being a mentor on it. Okay, did I say that correctly. Yeah, yeah, and the mega was my mentor last day. Oh, captain. Oh, well that's that's great okay so so you've had interactions with with more than just Chris Stern on this project very good. Yeah. All right well so do you have any other questions Rajiv. No, no, no. Any other topics for you. Nope. Okay well I think I'm going to propose to pause to stop here then because I've got a hot bug in Jenkins core that I want to fix and it needs me to write a test for it. So I'm going to call an end for docs office hours today unless there are other topics we want to discuss. I'm good. Okay, Rajiv, thank you will look forward to talking to you when Google where I'm intensely hopeful that Jenkins will be accepted and that announced that'll be announced on the 22nd. And then we'll talk to you at Google summer of code office hours. Now, next week, I'm canceling this session. So, that's right I should make a note of that. I will cancel this meeting next week, because Mark is going to Miami with Colleen. Oh, how lovely. Well, for a vacation. I don't like my any better than I like CentOS but negative today on everything you do. So we're clear Meg Miami is a lot better than the 17 degree Fahrenheit whether I had in Colorado today. I lived there for two and a half years so well Fort Lauderdale. So yeah I would actually argue I'd rather have the 17 then. Then Florida. Every building doesn't smell of mildew. So that's don't have three inch bugs that crawl across the floor that you can smash and they keep moving. All right, and that's that's the price you pay for living in a tropical paradise Rajiv I assume that you live probably in India somewhere. So you understand hot and wet, and that wintertime probably doesn't bring much snow to you right. Yeah. So we're going to make a trip to a place that's probably near to your weather than to my weather. Right what are you going to do in Miami then we're just going to wander around and have fun. All right. All right, well thanks everybody. We will talk to you in two weeks. Fabulous. Thank you. Thanks. Bye.