 It's recording now. Thank you. So welcome. This is the August 25th edition of Jenkins Docksoft Sowers 2022. Today on our agenda, we've got action items, Google Summer of Code, if Verhan wants to share any updates there. The September LTS, aka Jenkins Version 2.361.1. Search improvements for Jenkins.io. The commercial support page proposal. The current blue ocean admonition status. And then if we have time, a couple of other items here about change log entries in the October Fest. So first things first, Mark's been able to take care of the SheCode Africa Contributon results blog post. Everything else is still needed to be taken care of. But he is out of office this week or today, which is why we're joined by Alyssa, who's helping with hosting. And I hope to have more when he gets back. Verhan, do you want to share any Google Summer code updates? Hi, yes, sure. So just last week, I've been working on completing the tests for these processing layer. So those tests are complete. And Kristen has given me a couple more tests to write. So those will be completed by the end of the week. And after that, I think we'll be almost set on completing the Google Summer of Code, the entire project plan. So nothing would be left on our to-do list. And there are a couple of things, small things that we have to still look after. One is the cleanup that I mentioned last week. So the website, you know, we want to see if that changes the content. And after that, we'd also like to get some examples of the experimental plugin releases that has mentioned the issue on the pipeline step stock repository. So we want to get some examples for that so that we can go ahead and rectify that issue if it's still personal. So we were not able to find an example for that. So we are not sure if that is even an issue as of now, because the example that Mark mentioned is not an experimental plugin anymore. So it has been converted into a proper plugin. And so, yeah, we have to look into that. And we have to do some research on the side of getting the plugin name in front of the classes. For example, for Class Get It CM, we want to see that it is coming from Get Plugin. Or that is more on the resource side, since we don't have proper descriptors for those parameters. But yeah, it is something that is ongoing, but it's not a blocker for a GSO project, as far as it is concerned. And I have not changed the UI of the links as much. After clicking on the expand button, the links are the text size remains the same. So I'll just show it real quick how it looks great. So share. So this is how it looks now. So earlier, the links were getting slightly larger. Now, they go uniformly with the code font size. So basically, we can just see that happening everywhere. And as a part of the project, I would also like to create a configuration file as a starting point so that we have some result of this processing. So using up some work from the docs maintainers, we'll try to add around 9 to 10 parameters in the config file itself, so that we see some results in the reduction of the size of the page loading speed. So I think it would be a good starting point for the process, the new feature that is added. And yeah, I don't think there's anything else. Thanks a lot. Thank you very much, Bihal. Is there anything else that we can do to help with what you're looking for, as far as the examples go, or any of the other items here? Yes. So we were actually looking for help in identifying any experimental plugin that could come up in the pipeline steps reference. So if anyone is able to find an example for that, please let us know via the docs channel or anywhere else. And I'll see the issue that I was talking about in this space. Okay, great. Awesome. Thank you so much. And is the link in Gitter already, or would you be able to share that? I'll share it in the chat or I'll add it as a comment, maybe. I'll have the link next that you add in. Yeah, that would be perfect, Bihal, if you could do that. Thank you. Sure. Thanks a lot. Yeah, thank you. Next item on the agenda here is the September Jenkins release. Jenkins 2.361.1. So there are the change log and upgrade guide are essentially complete. I've been able to compile everything, get all the back ports in there. We've had some items come up with open JDK 11 that we were able to add in there and make sure people are aware as it does affect the latest release coming up. There are already resolutions in place. We just didn't get a chance to get to them prior to the release. So it'll be coming down the pipeline soon enough. On top of that, the faith is looking for a blog post for the CDF blog. This would be a little different from the RequireJob11 blog post that Basil had contributed recently, but we'll probably draw a lot from that. It's a little higher level and more about the innovations and major changes Jenkins has had over the years that gets us to today in Java 11. It will also provide Java 17 support. This is a big new one for users as well since before it was only available in preview. So now that this will be general availability, that's going to give a lot of access and control to the user base. There is plans to improve the search results that show up on Jenkins.io. We use Algolia, but right now the Jenkins.io Algolia is a little older and needs to be upgraded from the legacy scraper. That will take some time and it looks as though someone with specific credentials will need to take care of this, aka either Mark or Gavin Mogan. Mark has created a GitHub issue for it, but there has not been any movement on it as of yet, so there's nothing of note in the issue itself. This is something that is needed and will be vastly improved in the long run when people are able to search for things like upgrade and find the upgrade guides themselves. We've talked over the last few weeks, months about the commercial support page proposal that Gavin has submitted and shared. Still looking for feedback, still looking for any kind of ideas, discussions, suggestions, anything at all for that. If you have any proposals or ideas on how a support page would be helpful to vendors, commercial vendors or support vendors, feel free to share it there. It's available to anyone, so the lines of communication are open. We have the blue ocean admonition, so right now it's actually been compiled into all the Jenkins pages. We've got it in the tutorials, we've got it in the blue ocean docs. We are looking to put it into the plugin documentation, which Basil has done already, and then we still need to try and figure out how to add it to the Docker Hub entry for the blue ocean container. This is something a little outside of the Jenkins project, but connects directly to it, so it's just a little bit more involved. And then in here, the idea would be we have a link to the official docs and the embedded admonition as well. The change line entries from multiple repositories, just a matter of fact, if we get multiple change log entries from multiple repositories, anytime there's a wide sweeping release, Mark's going to check in with the developer list about potential solutions from that, or best ways to combine all those into less entries. And then last on the list here is just HectoverFest documentation contributions. There are some spaces in the docs that need to be converted from Wiki to Markdown. We're still discussing what the docs project might look like for HectoverFest. There are some things that we've been discussing, but it would require a lot more knowledge of Jenkins overall than might have time for, so we want to make it a little bit more accessible for anyone who wants to help. More will be discussed as soon as we come up with those ideas and as we get closer to HectoverFest itself. So that's all that we had on the agenda for today. Does anyone have anything else that they'd like to add to it, or any other comments, concerns, discussions they'd like to have? Nothing for my sake. Thank you. Of course, John. And I'll take everyone else's silence as we're all set on that. So I think we can stop the recording.