 Welcome. This is Jenkins documentation office hours. It's the 10th of November. These are office hours for Asia. Today's topics. Google summer of code 2024 preparation. Contributor spotlight version documentation. LTS 22.426.1 and final comments on Hacktoberfest 2023. And then a concluding item on update CLI that if we've got time we'll get to we'll need to limit ourselves I think today to 30 minutes or less so we'll we'll try to be prompt. Chris anything else you want to be sure we add to the list. No. Okay. All right, so here's what here's what I've got sir first sincere apologies that I missed the meeting it was on my personal calendar I forgot to put it on my business calendar and didn't even look at it. So here are some ideas, one of the things that were some of the things we discussed in that meeting were project ideas. And here are some that came to my mind Chris so maybe you and I could spend some time here discussing these as possibilities. Okay. So plug in health score additional probes these are ideas from Adrian. And we can see the probe list later. I think I think it's a reasonable one I'm just not sure which specific probe but I think there are more probes to be done there. Yeah. Okay, then the, we're getting some and we're seeing some additional traction Bruno LeRochten is doing some experiments and we've seen others on open rewrite. So we have the same as the same kind of ideas what Basel has suggested on plug in build metadata updates, and I've actually done some experimenting with it as well and so we might benefit by having a GSOC participant, write more recipes or improve the existing recipes make them better etc. Have you have you had any experience looking at the Jenkins recipes for open rewrite. Okay, so what I've been impressed with with some of the changes Bruno just took me through a tour today where he used one of the rewrite recipes to replace successfully replace power mark with my keto. And so it was a non trivial replacement. Yeah. And then plug in installation manager tool improvements is an idea that had been there last time. And I'm, I'm not as interested in that one as I am for instance in this one here I'm going to put it above it bear token authentication for the get plug in and they get client plug in so there is some. It's a new new authentication technique. We've had a few requests for it. Okay. Then we've had we've had the rest API specification generator up as a possible for a number of years. I'm less enthused about that one than this next one which is, we've got a tool that generates here I'll show it to you it generates Jenkins.io documentation. For extensions. And unfortunately, or for it fortunately it depends on how you view it. The extensions index that's here is steadily getting smaller and smaller because every time a plug in enables incrementals it drops off this list. Okay. So what we need is we need a re implementation of this tool. For example, there should be a line here for the extension points to find in the get plugin but there isn't. And what we really need is a re rewrite of this tool. The the idea is do rewrite that's much much smarter than this. This tool was this tool is very heavyweight and Jesse Glick has suggested some techniques that will make it much lighter weight. So that one is one that is interesting to mark. Because we're currently broken, and it might be one we implement with student help during the prep period for GSoc. I that I don't know I'm not sure when we do it but it's, this one is interesting to mark the tool is currently broken right. Then there's, there's a project inside CDF called the CD events project. And generating or extending the existing cloud events plugin to do CD events could be a very attractive project. Yeah. The last one I had was open telemetry. So this is one that the infra team is looking for wants to do wants to perform deeper monitoring of job specific jobs on ci.jankins.io and info.ci.jankins.io, etc. Any comments from you on any of those particularly. No, I think that all good ones. Okay, good. All right. Now, what would you like me to do in terms of, of, do you do you want these placed into some Google document or how would you like them hosted etc. Oh, I think there's a Google talk for it like elites and prepared but do you have the link for it. I don't know if I do so. Oh wait a sec, but you say was this one that Alyssa Tong had created. Okay, all right, so, so mark insert those ideas into the Google doc that Alyssa Tong has shared and I'll double check that if that I've got it. Good. Very good. Anything else, any summary that you want to share of the session that happened earlier happened, I guess about 12 hours ago on GSOC ideas. Okay, one thing is we need project ideas, but I have contributed so it's like together viewers and existing ones we should have enough for like a good application to Google. All right, so with ideas from Chris and Mark, we've probably got. We have a good start for application to Google. Good. Now when is the when is the application to Google do. I think it's, I didn't, I don't remember it but they just send an email about it yesterday. See if they too. Maybe because you're not one of the organ means but I can avoid that one through you. Great. Super. We have we have some time to prepare to prepare our application and project ideas. I think that you have done the you've already started the process on the Jenkins.io site for GSOC 2024 is that right. Yes. Oh, here we go. All right, so we've got project ideas from very good. Okay, so if I want to just insert something into the draft project ideas. I could, I can do that by pull requests to Jenkins.io I don't even know. Yeah. Okay, very good. All right, so let me make myself a note there. Pull requests Jenkins.io for the for draft project ideas. And let's put it there as the location. Very good. All right. Anything else that you wanted to be sure we discuss around Google summer of code. I think we have to develop the ideas like the details. Before we can like look for mentors for each project. All right, seek mentors. As the ideas are developing. Very good. All right. And this one, for instance, open rewrite recipes. I wondered if we might persuade persuade Steve Hill or Rahul of Netflix to help with it. And this one, we may ask. We actually could consider asking Jagruti. Our last year. As a comment. Yeah, so Adrian certainly Mark Jagruti, et cetera. This one is clearly me. And then this one is also me. Yeah. And we could there we could consider Rashab. Other some of the others other previous GSOC mentors. GSOC participants. We've now had three, three or more years of GSOC projects on the get plugin. So we might be able to get. Those good. All right. Good. Anything else on Google summer of code. Um, no. Looks good to me. Great. All right. Next topic I had was contributor spotlight. Do you want to share what you're observing there what you've seen so far. I actually have no idea what, what's going on with it. I just like the last I checked. I think I opened a check of infarting. And that's, that's like the last time. Yeah, there was some updates back and forth. But on that, I think it's still in progress. I guess because there's always having me uploaded yet. I think it's still in progress. Uh, Seriously. Okay. And so the. My understanding from Kevin in Docs office hours, Europe earlier today was that they've info team has put it into their work for, for the next week for, so for the next seven days. Okay. I don't know. I don't know. I don't know. I don't know how the household moves and whatnot. So I'm not sure they're going to squeeze it in in the next seven days, but I would expect. Uh, Next seven to 14 days. It seems likely. Yeah. Good. And I assume you're okay with the idea of contributors. Jenkins. In parallel to stories. Jenkins. Yep. Yeah. Good. All right. Questions or topics on contributor spotlight, Chris. Nope. Okay. So version documentation. Anything you want to share there on how Vandy's work is going. That one. We're still working on the blog. So it was like, we have to fix it. The offer info for the blog pages. Okay. So I think, I think that's been fixed. Good. Good. All right. So now is it. Let's see. So if I look. Is it likely visible on the prototype? No, the prototype is just user documentation. Right. I think, I think it's like, you can try to, to navigate to maybe Jenkins stocks and not, not know the, but blog. Okay. So let's go to blog. That's like this. I'm not sure that's right. So no, no, not this one. Maybe not even Jenkins. Yeah. Okay. So let's try that. So let's go here like this. This is blog. No, it doesn't work. So it's not ready yet. Okay. So not, not yet visible on the preview site. Yeah. Cause like we probably, um, the thing is that I told him to, um, like, but maybe I didn't tell him in the way that he understand it. I told him to set up so that we can have a blog. Yeah. Yeah. Yeah. Yeah. I was there as well, but that was like in passing. So it was a while back. So I'll, I'll mention it again. Great. All right. And now I know that Bandit had set a personal goal to try to complete the work before the holidays in India. Um, I'm, I'm unaware when is, when is the wall in India is that. No, sure. Okay. So November 12. Okay. Got it there. So it's coming very soon. Yep. All right. Anything else there? I think it may take more than one month to do it because we have, we still have a lot of studying items. So you may not be ready by the end of November. Right. Yeah. Certainly understood. It's a matter of time. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Certainly understood. It's a major project. Congratulations on your work there. Okay. And thanks to Vandit on his work. Yeah. Anything else on version documentation? Um, we're not much for now, but except, we'll need to prepare some documentation. For like how to use it. That's one part we haven't done yet. Okay. So this is how to contribute to the site. Yeah. How to maintain the site. How to contribute to the site. All right. Anything else? No. Okay. Next topic then was two dot four 26. One upcoming release on November 15. So the change log and upgrade guide has. Been proposed by Kevin Martens and merged. And so now it's. It's actually merged and in line. Unfortunately, we can't see it there. But if you're okay with it, I'll show it. Here from a prototype site. Is that all right? If we look at it together. Run. So Kevin and I have been through enough iterations on it that I felt comfortable merging it. Into the main line. So if we look now. There we go. Okay. So, so in the usual pattern, it has. Changes since the baseline. These are the things that have been back ported, including today's back port of. The update of the snake YAML plugin. And then changes since. The previous LTS. And these security fixes. Were both already included in. 2.414. No, they were included in a. Yeah, they were included in 2.414.3. Interesting. And included. Included in a weekly after 426. So, so. Hence they're listed here prototype is gone. Centos seven is no longer supported. And so. And et cetera, et cetera. Whole bunch of system five. Initialization scripts have been cleaned up out of the, the system be installer. It's actually, I'm quite impressed with how much has come into this release. And my testing so far has been very positive. Okay. The release checklist is progressing and I'm feeling actually pretty good about it. So thanks to your work on helping make this checklist so easy to use. Right. Any questions or comments on that LTS. Nope. Okay. Next topic then was October fast. And here. We're pleased that in, in the month. We had over a thousand pull requests. And of those 400. Over 400 were hacked over fast pull requests. And over 81. Over 80 submitters. With three over 350 of them. Over 300. Over 300. Over 300. Over 800. Over 800. Over 800. Over 800. Over 800. Over 800. Over 800. Over 800. Over 800. Over 800. Over 800. Over 800. Over 800. Over 800. Over 800. Over 800. Over 800. Over 80 submitters. With three over 350 of them validated either being marked accepted or merged. And 68 submitters. Now, what we see is. About a 30% decrease compared to past years. And that's roughly the same as seen by other projects. observation was the lower spam rates been worth it. It's great. Yep. And anything you want to observe there? Thinking like we have less like percentage degrees and a number of two PR so we don't. But yeah, maybe just some people just don't don't want to bother with active events. Yeah. Because I can see I got the other percentage PRs for active of us degrees by above 30%. But the number of PRs created on the whole has decreased by 15%. Yeah, good point. So in this case, maybe it's small and that smaller reduction in total polar face may indicate more involvement from the community offsetting a smaller October Fest contributions from new arrivals. Yeah. Good. All right. Anything else? No. It's a last topic and we're almost out of time. So let's let's hold with last topic here. There was a pull request merged that Bruno Verracht had proposed a change to do tracking of the recommended version for the choosing a Jenkins version page and several others. So if we look at this page, just a minute here, I'll show you what what I mean. So for developers of and maintainers of plugins, they have to choose which Jenkins version they should set as their required minimum Jenkins version. And this page generates its its values based on the current LTS versions. So you'll see here 387.3 and 401.3 and 414.3. And what Bruno has done is automated this with update CLI to replace the Ruby script we're using before. And so here we've got fact this one just just changed last week or two weeks ago. This number was 2.361.1. And it's now moved forward to 2.361.2. Okay. So one of the one of the worries I had was, will this correctly update now that it's sort of switched its method? The reason Chris, I think it matters to you is this is changing the technique we're using here. It used to use a templated source file. So if we look at the source file, from improve this page, what you'll see is, see, let's look for release. No, let's look for. Yeah, so here it is numeric. I'm going to cancel these changes and we're going to go back in history and look at it previously. So see what this one was here, for instance. Oh, that didn't help me. Sorry, Chris. Let's look at it this way. No. Okay. I want to see. Yeah, this document. So here. No. Well, maybe I've maybe I'm not going to be able to show it in the time we have Chris. Okay, no worries. What there is is there is Oh, here it is. Good. This marker text like placeholder oldest LTS place holder oldest weekly has now been replaced by the literal version. So the file on disk or the file in the repository now actually includes a specific version number here. Okay, we think that makes it easier for the version documentation project because if this files on a branch and your version and it's being versioned, now the version will stay constant until it's revised by the tool but for old for old releases for old versions, version branches, it keeps its constant nature and doesn't have to be generated with a Ruby script. Okay. Yeah, does does that say I mean, and currently, if I understand correctly, you're not doing version documentation for the developer doc. So this one really isn't isn't an issue for for the version project immediately. But the concept makes sense to me. Okay. Well, I need to follow up on this one too for the retooling project. Okay. To accommodate for this. Maybe maybe we don't need to but just just in case we can check in. Great. Well, and that's that's I think that's the right approach. The the site continues to evolve and version documentation. We can be sure this this is still behaving well with the version site. Yeah. Great. Excellent. Anything else, Chris? No. Alright, thanks for your time. I'll go ahead and end the recording and we'll make the recording available in 24 to 48 hours. Thanks. Thank you. See you, Mark. See you, Chris.