 Welcome. It's Jenkins documentation office hours. This is the 6th of January 2023. Happy New Year. So items I've got on the agenda for today. Action items. Pipeline. Oops. Pipeline Docker. Let's get here. Pipeline Docker plugin possible deprecation. WMI windows agents deprecation. Archiving the website component on Jira. Interesting poll requests. And the poll request backlog. And the December newsletter. Any other topics you want to be sure we put on the list, Chris. We can talk about these are like that. What we have in terms of documentation. The ones for the project. Good. All right. So Google summer of code documentation. Yep. All right, good. Let's include that. We'll put that right at the top of the list. Okay. Great. Excellent. Anything else you want to add on the agenda. Oh, not much. Okay, then let's go ahead. So my way of action items. Kevin's got the action item to archive the docs mailing list sometime this month we hope it'll be done. That's those are the only that I'm aware of. Google summer of code documentation so what do you need to share Chris and let's talk more further. Okay, so we have got thinking about 10 project ideas so far and but only one of them is confirmed. So which means that nine of them needs working on by contributors for potential mentors. So we may need to communicate better with like potential mentors. Okay. Yep. And I think we're going to have a meeting soon. And that's going to be like the week or two. That should be a That's a next Wednesday or next Wednesday. On the next Thursday. Next Thursday we're going to have a meeting. And this is the Org admins or Org admins and mentors. And it depends like we should start inverting management to us to if we can visit. I think the next Thursday is one that's mostly for me or admins. They should be open to us because we got a few more holidays, which is good news. Good. All right. So the topics tell me more about the topics that we discussed there. That's, is that more about how to improve the project ideas to further refine them. Is it. Yeah, more about. Okay, so. Yeah, so we need to like you're using jmms term to crystallize the ideas. Go ahead. I know that therefore for many of the projects. It's good for a start but we do not have all the complete set of like details for the mentees to start. So may remain need to add more for a complete set of starting points. Good. All right, I like that. And so how will that be announced that'll be announced in getter and community. This course. Okay, good. I mean, I may need to coalesce with jmms first to see what he thinks. Because the proof of that's possible. And that makes sense that absolutely makes sense. Yeah, mainly it's an email to, to everyone in the advocacy and I wish as I jso you, Lisa, Jim and Anna and Bruno, because it's new. Yeah, I should include into you. Right. Very good. Okay. So the other topics that you wanted you wanted to highlight there are there. So do we need to should we spend some time here looking at those specifically I think if I recall correctly there were some projects that are documentation projects. Some of the project ideas are documentation specific. I think that we're going to spend a little time here talking about them looking at them and trying to improve the, the depth of the things we should. Yeah, if you have to tell me. Well, I think with with you and me here together and the two of us. It's probably much more effective if you do that than anything else I have on the agenda. Okay, okay. So how about let's look at those ideas, and then we'll, we'll decide which ones we should improve and how so if we look at Google Summer of Code in Jenkins. And GSOC 2023 project ideas list. So we certainly could talk more about the plugin installation manager tool improvements that's one that I've got a little involvement in. It's very specific to documentation. There was an autumn or go ahead. Yeah, yeah, go I go and talk about that first. I should. Sorry, sorry, which one. Because like, I think it's the one I have been assigned to work on like, I think that the alternative tools also involves documentation. It's like, we go up. Yep, that one. This one. Oh, oh yes. Good. Okay, well so let's yeah so let's spend, let's spend more time on this one. That's a that's a good one to to talk through. Okay, yeah. Okay, so the background here is that we've got we today we generate the Jenkins.io site with at Ostrich using ASCII doc sources and YAML files and data sources and Ruby scripts and all sorts of cool things that ultimately result in a static site. And the challenge of course is that Ostrich is no longer being actively maintained. So, so the idea was okay should we consider Antora or Hugo as a tool that is actively being being maintained to replace it. And this is the one that that I know CloudBees documentation team is using it so we're more likely to get mentors and coaches from the CloudBees side if we were to choose Antora. Gavin Mogan likes Hugo, so he might be willing to coach on Hugo. He also suggested Gatsby as well but I'm thinking like I say, both Hugo and Gatsby they're not they're not designed for ASCII docs per se. So they may be a good idea but maybe extra work would be required if you want to use these tools. Good. All right. So, so whereas Antora I believe was actually created by the ASCII doc creator wasn't it so or a key voice in the ASCII doc community so yeah. Okay, maybe a better idea to use Antora because it's like it's more direct. Okay, well and and that Mitch matches with what this says so that's good most likely we will lean towards using Antora. Good. Okay, that's that's why I added. Okay, well so then. I think we may need to work a bit more on the background. Because like right now we don't really discuss much about Antora or Hugo because like you can't like with I mean this I said, I think we should set on one tool. Well so how about shall we show you and I let's take the time right now and let's do the writing and propose it. Okay, are you okay with that or would you rather. Yeah, we can do it. Yeah. Update. G soc. Let's see update. Doc site. Yeah, generator idea. Yeah. upstream slash master. Be sure that I'm in the right place which I am good okay so okay so here's a mention, and there we go. Yeah. Okay, so, would you be okay if we just like to embed. How should that be. Yeah, I'm going to leave that the way it is just because we don't like to embed. WW that breaks the resolution of things if I'm using. What do you call it if I'm using if I'm jarring the site locally. Okay, so the. Doc sources. Yeah, the ammo data files. Yeah, and Hamel. Yeah, that's that's okay. Stored in GitHub right. One of the drawbacks is that the technical documentation is not product version about that's absolutely true. Is not possible to you, that's correct. Only the latest can be viewed. This leads to unnecessary confusion. Yeah. Okay, and, and is a worse experience. Yeah, then many other side documentation sites. Like the get site. So I think I suspect others, the free BSD and others right there are many sites now that do versioned documentation. Yeah, most sites are like versioned. Except I was maybe. Okay. So, the preferred tool. How about if we just admit it, we think we should use Antora. Yes, and this is generated as a static site. Using awestruck. Yeah, uppercase. Oh, thank you. Yes. Yeah. Right. From ASCII doc sources, YAML data files and Hamel templates stored in GitHub. Okay. So the preferred tool to replace awestruck. Is Antora. Yeah, and let's just admit it. We, you and I have a have a strong enough opinion. And our opinion matters. And if I'm going to mentor it, I'm actually going to shamelessly promote something that I think I can go ask other people to help with. Okay. And Damian Deportal knows Antora and likes Antora a lot. And so do a number of other people that that could be good helpers. Okay, okay. Ostrich is Antora. Okay. The potential would be to build a working tool. Okay, working. Okay, I'm not hearing you. No, I didn't say anything. Oh, okay. I'm some other crosstalk. Okay, good. My colleague working in the background. Oh, got it. All right. Okay, so the potential GSOC project we do to build a working site generator. Yeah, that was weird wording. I didn't realize it until now. So a site generator to district to demonstrate. Yeah, right. So the existing site. Okay. And add the concept of versioned display. Am I saying, saying how, so for me just getting to the existing site will already be quite challenging. There's, there's an awful lot that the current site generator does. I think it is what we're waiting for it. Okay, so then, once the existing site is generating the existing or no. Once the existing site is generated with Antora. It should be the site should be reworked should be extended how about that. To add versioned versioned what what would you say versioned copies of the documented versioned specific. Yeah, documentation, right. Yeah. Okay. So we've got the quick start and the quick start. This one I think we can actually put it in is some ideas might be create quick start. So documentation. Quick start steps include. So build the current documentation site locally. Yeah. Familiarize yourself structure. Exactly. Yeah, actually let's say this way, become familiar with the current site, including so page types, and how they are generated. And this includes things like roadmap. Right is kind of an exotic one. Security, let's see, change logs roadmap user handbook. Yeah, developer guy developer handbook right. Yeah. The artwork page, which is a little different artwork. See what are some others. Oh security security advisories. Yeah. version specific to have content in tutorials. Because there is some of that right see the like, like what's the example. Like, like, oh, improve a plugin. So now page types in there probably more but all right so then familiar then. Page formatting or page content. Sources like. Hamel. Yep. The most important is ASCII doc. Yeah, there's also a Hamel. And I think we may have. So, and, and this is another web components, because that just barely arrived web components. Okay, so, so familiarization already. Are there other things you'd say, hey, oh, using make files right. Yeah. So the build process. Yep. Make file. Docker containers. Yeah. Inside the Docker containers. Yeah, because that's how I believe that's how Ostrich is doing it. And, and so we ought to put Ruby in there. Hamel slash Ruby. Okay. Docker containers. We just had some additions. Syntax and spelling checks. Okay. So then maybe as another part of quick start might be fix. One fix several good first issues. And we should probably include a hyperlink there to the good first issues. It's in the, it's below. Oh, is it? Oh, we've already got it. Oh, okay. See this one goes to this one goes to get first issues. Oh, it does. Okay, it's got. All right. Very good. Yeah. Excellent. We'll just steal that. Okay. Good. Okay. Okay. Now, after they've fixed several of those that gives them and they've built the site. Now it's that's that's gives them familiarity with the current tool set. Now, how do we get them familiarity with with, and maybe this is where we should put. Explorer and Torah. Yeah, I just did it. Okay. As a start, I downloaded it. I started it. Oh, good. And it was kind of cool is to use and they did have this thing called playbook. You can use to as a temp like as a conflict file. It's quite easy to set up everything from there. Good. Okay. All right, so Explorer and Torah. Should, should they as part of their quick start. Should they review. Version. Specific documentation techniques. So we have used by and used by and Torah sites. Yep. Give them examples. They like CloudBees. Oh, good idea. Okay. Yeah. So, for example, CloudBees documentation site. Good. Okay. Now I haven't looked at the CloudBees site. So let me see if I can grab a quick link. I haven't looked at it recently cloudbies.com. So let's see capabilities. We want to see developers. Oh, here we go. There we go. Okay, so let's see. Well, let's see. I think those this may just be stories what I was telling people. I was looking more for detailed, detailed documentation about continuous integration. Let's try. Okay. Folders plus. Controlers. This is an awful lot of marketing material. That's lovely. But now let's find. Okay. So, well, maybe this will help me and maybe it'll be versioned. Oh, yes. Here we go. Notice. Here we are. Okay. Wow. This, this gives me the folders plus plugin in this one. And if I want to go back. It gave me an older version. Okay. Yes. So this is a good choice. Thank you, Chris. Excellent pointer. All right. So let's embed that into the, into the text we're creating here. Okay. And since we'll probably want more than one, I'm going to make that. CloudBees documentation site. And I personally really like, I don't know if it's generated with Antora or not, but I really like get SCM. I read it a lot and it actually has. A versioned concept. Let's find this, the documentation, the reference manual. Look at get config. And notice here in the top left hand corner there are all the versions. So, again, it's this one. Okay, so. Get config reference manual. Any other sites like that you think that we should point people to. I think because like a lot of sites do that, like. Yeah, we could try. Let's see, is there something on maybe a Ruby site? Yeah, it's fine. Maybe it's just Ruby. Yeah, so let's go Ruby. Yeah, they do documentation. Because they've certainly got a long history and I would bet Python may as well. Let's use pythons because like I saw with this one is more rudimentary. So I definitely got version control. Okay, so Python documentation. And here we go docs Python. Oh, yes, this very much has version. Okay, good. So let's use that as another example. But this one is generated with, if you have a tool used to use for all these things. Python is definitely with things swings. Oh, we're choosing. Okay, and that's. Yeah, that. And I don't care which tool it's using. I think it's still a good things. Sphinx is the generator. The notion of how do you do this navigation. And I don't know how get does theirs. I'm sure it's probably not Antora. But I think each of these is, okay, this is how they navigate. And how, how would, and notice I like, again, there's a highlight up here at the top that says, you're reading old material to this application. So, so, and that's, that's a good thing, right. They should understand it helps them as they're preparing a proposal but hey this is how I think it should be based on these other projects that do the same thing. Okay, so get SCM we did Python three Python we did. Yeah, any others that come to your mind that we should include as, as things to study. We can use any more jobs like I think. Oh, you say Java. Yeah, John. Yeah, so let's that's a good one let's look at. I'm not sure that they're a great example but let's try it let's see Java. So let's see Java, Java, well let's look at Java doc for Java 11. Right, maybe we can find so here's the JDK 11 documentation. So this may not be what we want. I mean, it's, it's certainly an example of of version specific and it provides another for me. I'm not as thrilled with that one but I think maybe what we do is we include it as a here's an example. Another idea to see how somebody else did it. Let's refer the Sphinx technique or the cloud bees technique where it embeds it right into the, it makes it more obvious in the page. Yeah, I think maybe pytorch as it to which one you said pytorch. Yep. Okay, so let's find that pytorch. Okay, so here docs. Right, there's another okay good very good example. So this has index on the left and direct access to which version you want to see. Nice. Okay, good. Very good. Okay, any others that you'd recommend. I'm given how nice those are I'm taking off the Oracle one. But just, it just doesn't fit with how nice, how nice I think the others look let's let's keep what I like as really elegant examples. Okay. Okay, like spring boot docs but they're not like really doing the versioned. Okay, it's really like spring boot not a good idea. So Java later. I don't see anything here that tells me anything about. The version 3.0. So if you look at the box, box, okay, which box, the one way bill. Yeah, you see that. Oh, it shows here, right. It's like, it doesn't give you a choice to, to select. Well, and maybe I just went to the wrong place. No, that's not terribly helpful. Is it. No. Okay. So they've got it, but they don't have a really terribly comfortable navigation path to it. Right. Okay. Yeah, we can try out. Yeah, one thing we can try is like, it's kind of like, not sure if we should use it. But I think for the docs of TensorFlow. Let's see when let's okay, TensorFlow talks. Okay, so here. All right, so they've got a version number that they're showing there. Oh, and this is a different way that they're navigating versions. So if I want to travel through their versions. Yeah. Okay, that's I like that. That's a good one. So let's, let's put that one in there. Thank you. Maybe more five. Yep. Yeah, and, and I think at least this gives the candidate a chance to think about several different ways that people are doing it they don't, they don't have to get stuck on Oh, there's only one way to do this. Yeah, it's no there are a lot of different ideas, and they've got to, they'll need to bring their ideas to how should it be done. Yeah. Okay, anything else we think so as they're getting started. Build the current familiarize yourself with the current or go ahead. I wanted to change earlier like for like the skills to study and improve section can we can we change it ask it dogs, the two uppercase. Oh, yes, absolutely. Yeah, we should do it that way because it's the purpose for it. Good. Okay. Well and should we have. Are there more things that we should include in this like the YAML for YAML data files to drive. Web page templates. Okay. Yeah. And then probably Hamel files, Hamel templates. Hamel, Hamel templates, YAML data files. And maybe those are just subsets of static website tooling. Yeah, I think so. Yep. Okay. Yeah. No. It doesn't go to the new feature. Sorry, say that again Chris I missed it. We have a new section called new feature. So maybe we can use it. Oh, yes, yes, good, right. Absolutely. Yeah, because for the new feature we can have like an improvement on the current layout. Good. Good. I like that. My editor is has decided recently that it's going to do highlighting of characters a little differently. There we go. Okay, so. All right, tell me again what were the what were the things there that should be said. We can include like new layout for the web pages. Oh yes, right, right. Improved layout of the existing page of existing site and pages. Right. Oh, we should come in now. Yeah, that one should come in. Oh, I was just going to take it out like that. Yeah, cool. Okay. I mean, I think. For me, that's, that's already a big one is a very big one. Yeah. There's, there's a piece of this which, which we need to be sure that they deliver iteratively and incrementally. Yeah. So, so maybe one of the other things is as an expected deliverable it is. See so do I dare change it. Yeah, I do. So let's make it. iterative and incremental improvements to the site. I don't know about the project. If they're doing it as big bang at the end. I don't, I think that will, that will lead to all sorts of problems. Yeah, we better not do that. But the thing I'm kind of worried about is like how to, how to introduce a changes. As we go. Because we need to change it. The tool. To be as fast. Or should we like start a new branch. And we're going to that one is that. So, so you mean in terms of chain, making the transition from Ostrich to Antora. Yeah. Wouldn't we wouldn't we want them to set as the first objective. Just to do this thing, right. Get equivalent, but using equivalent to the existing one, but using Antora. Oh, okay. So what you mean. Yeah. That was that was at least my thought is make the transition from Ostrich to Antora. And find a way to do it. So that we get the current site. Yeah, that was that even, and if the project only achieved that, it would already be a dramatic improvement. I know. Yeah, it would be. Because then, then I don't, we don't have to worry about, oh, Ostrich doesn't being cared for anymore. How do we deal with it? Okay. Sounds good. So that's, that's okay for you phrase that way. Yep. And maybe actually maybe what we. Put this one first, even. The iterative and incremental is the way we do it. Okay. And, and fully automated CI is another piece of the way we do it. But we want to use Antora to do it instead of Ostrich. Yeah. Now, is there a way we could do Antora for a subset. I think about that too. Because it might not be the best way to do it. Right. We cannot segment the project and might introduce some problems. So if, if, do you think this would be, are we at a point where we should submit this already as a pull request where, or at least build the site to see how this page works now that we've done it. Yeah, we should do that. So let me make the site. Okay, so the site's rated of you. I'm going to bring it up in a web browser and I'll drag the web browser in in just a minute. Okay. So here's the web browser. And let's look at. We have a number of code 2023 project ideas. Whoops. I picked the wrong thing to get there. Oh yes I need to go here. Google summer of code in Jenkins. And this one has the project ideas list. Okay. And here we should find building Jenkins.io with alternative tools. Let's see if the layout came out correct. Nope. So I didn't get it right. So I need to do the nested list thing. I used the wrong syntax just a minute. Okay. Oh yeah. So in this case, it's that it's probably two. Instead of spaces, it's double asterisk. Let's try that. Yeah. Yes. Okay, that's it. Good. All right, back to where we were. So the easy thing here is then. And then this one. Help if I typed correctly. Okay, checking now if I got it right. So the indentation was. Page types. And then here's the list of page types, page content types, build process, and then fix several good first issues top level. Okay, I think that got it. Let's go read it and see. Okay. Where's my page. That's not the page we wanted. Sorry, I'll have to edit that out. Here we go. This is the page I wanted. Yeah. There we go. Okay. So that layout looks okay. Yep. Good. All right. Any other changes we need need before I submit it as a pull request. It looks really good. All right, let's do this. That's great. Excellent. So we're going to update. The project idea with. Update and site generator idea. With more details. Okay. So we've got one ahead. Let's do this. Update site generator idea. Details. So Chris, you are a GSOC or Gadmin, this has the nicety that you can go in and approve it. Later today. Yeah, yeah, you can do it whenever it's comfortable for you. Okay. I'm going to say that as soon as somebody's approved it, it's going to auto merge. Okay. Because you and I worked it together. And so once it gets its first approval. And has passed CI, it will just automatically merge. And whenever you do that approval, or if John Mark approves it or, or Bruno, whoever approves it is fine. It just, once it's approved, it gets merged. Okay. Great. Thank you. All right. So back to our agenda topics. I think we've covered the most valuable thing that I could have wanted to do today. That's great. Okay. Anything else you want to see that we do on Google summer of code before we end our session. Today. That's a more important thing. We still need to. To work on the other ones. Right. Yeah. Great. All right. Well, so we've got, we've got that first idea. Just give you a brief overview. Maybe we could take a few minutes on one or two of these others because I think you may be able to help me on some of the others. Sure. These deprecation topics. What's happened is there's an. Plug in deprecation process in the life cycle of Jenkins plugins. And that deprecation process. Shows a warning dialogue to users. To tell them that, hey, this plugin you're using is deprecated. Well, one of the plugins you're using is deprecated. Well, one of the plugins that was recently deprecated was this WMI Windows agents plugin. And it was deprecated for very good reasons. The reasons are described here in this issue tracker. Why is it deprecated? What's that mean? What's the impact, et cetera. But the crucial thing here is that. Jesse Glick. A core maintainer offered a really good idea of a way to. Make it so we don't have to do. Quite as much work to do this. And so there's a core change that's been proposed here. To make it so we do much less work. With. In order to implement this. Finalize this deprecation and make it. Good for our users. So that's, that's the info piece here. Now the next piece. Is an entirely different topic. And the next piece. That's the info piece here. Now the next piece. Is an entirely different topic. And this was the one if you could stand to spend five or 10 minutes with me, we'll, we'll try to make progress together on it. There's, there's a component in Jira. Called website. That's the place we tracked issues until about two years ago. And so what Kevin's done is he's gone through the work of closing out. A bunch of those issues. And here is that list. And what he, what he did, he closed out a bunch of them, but there are a few that are not yet closed out here in this very bottom section. And I wanted to just you and I. Take some time to go through those together. And decide if we want to make a recommendation to Kevin on what should be done with those. Okay. So let's read them. And we're just going to read them. One at a time and. Make our decision. So this one is. System administration capabilities using groovy. And the suggestion was. Hey, there's a lot of capability in the Jenkins script console for administrative use of groovy. And this could be a dedicated section. I think this should just be. Transported as an issue to Jenkins. It's a. Yes, we want this. I don't know when we'll get it, but I think it would be a good thing to have. Okay. Good. So we're just going to say. Move to get hub. Okay. The other one is now let's take the next one is. 734. Create a C or C plus plus tutorial similar to Maven. Python and no JS. Yep. And again, I think. I think that's a good thing. There's still plenty of people who code and C and C plus plus rust is not used by everybody. Yeah. So for me, I'd say move it to get hub as well. Yep. Good. Okay. Now updates to the solutions pages navigation. This one. Improve the look and feel of the solutions page. And. There's the navigation page. You get it from you. I think you get to it when you. Go to. Solution pages. Yeah. So it is actually now used here. But. Well, what is it asking for? It is negative and accessible now. Yeah. I think this one we call done. I'm going to say this is done. It asks for some additional things add Kubernetes, but that's an entirely different story. This one is done. Okay. All right. So that one is done. Thanks for your patience. We will. Just keep going through this. Broken links throughout the Jenkins site. These are pages of broken links that were generated by someone. By a contributor two years ago. And for me, I think this one, we should just. Close it. And say that we're going to. Find broken links a different way. Okay. So I'm going to, you're okay with that idea. Yep. As for broken links. In a different. And track them. Using. Get hub issues. Okay. Done. So we call it because this one is done. I just submitted. Fact here, let's see if it's done. If it's. If it's finished the, the pull request. Oops. Where's my pull request link? I didn't put it in there. Sorry, Chris. I need to fix a mistake I made. Okay. I go do this now. The mistake is. GitHub. Here. Pull request. Broken artwork credit links. Fix this mistake too. And I am going to boldly merge that myself. Because that doesn't seem very risky. Okay. Merge without waiting squash and merge. And that means. This issue is closed. And all the issues in the broken links. Epic are closed. That looks very tidy. Yeah. Okay. So. Done. It's not that it's ever all the way done because we continue to have broken links that pop up. Yeah. Next one. So we have five minutes left. Okay. So we continue to have broken links that pop up. Yeah. Next one. So we have five minutes left. Okay. Continuing to do this as we work through it. All right. Oh, that one. That one. I already image. Oh, that one's done. Okay. Good. Like in page sorting does not work. Like in search updated. I don't understand. How did he do sort equals. I don't even understand what, okay. So sort equals updated. How is there an updated on this page somewhere? Not sure. Recently updated is here. Oh, oh, maybe it's over here. Okay. Sort by state though. Right. But there is no way this is sorted by release date because look at this. SCM API three weeks ago. Is after Mailer released six months ago. It isn't working. Okay. So it's, this is real, but it's not working. Okay. Sort by relevance. Sort by most installed. It looks like they're all sorting by most installed. Yeah. I don't know. I don't know. Because title sort didn't, doesn't do anything. Now I don't know how did this sort thing. Appear. Oh, it appeared like this. Okay. Okay. So what this, what, so what we need to do with this one then is it needs to be transported. Copy to or move. To get hub. Plugins. Jenkins. Yeah. Because this is not the. This is not Jenkins.io docs. Site. Okay. So. Move to and let's just call it. Make it so it's less likely to make a mistake there. Okay. Okay. Turn security page into main tab. Oops. Main tab menu item. Oh, yeah. Okay. That's. That's a valid one that I think belongs in GitHub. Okay. Community. Okay. So 772. Okay. This one. Is. This one is nothing we're going to do about. Won't do this one is. Tracked in other locations. What this is really asking is, Hey, please. Please give us some way of filtering. The content of this community reported issues. Text. Okay. So that people, when they submit bogus bug reports, like 69 or 420 or whatever. They, they would not appear here. Oh, I see. I can show you an example of a live example is even better. We look at this. So download. What happened was. People. A user clicked. One of these two cloud icons, either this one, I had to roll back or this one I experienced notable issues. And when they did. They typed a bogus number in here. So instead of typing 69955, which is a valid issue. Yeah. They typed. 1, 2, or 3. Oh, or 2, 9, 9, right? 2, 9, 9 is not. An interesting issue in, in jank in that version of Jackens. Okay. But the problem is there's a whole curation problem there of. Three is in fact a valid. GitHub issue. It's not a valid Jenkins issue. It's just not a valid Jenkins issue here. It means someone has to review these and filter them and that. That is. Well, the core maintainers haven't been willing to do that yet. And I'm one of those core maintainers who's unwilling. Okay. Chris, thank you for your patience with this. So I'm going to close. I'm going to list that one as closed. Okay. Thank you for this. Let's call an end for our session today. Much appreciated. You're welcome. We'll see you. Yep.