 Hello, and welcome to the Jenkins documentation office hours. This is the EU US edition, and it is December 14th. Thank you for joining. Today, we have myself, Kevin Martins, Mark Wake, and Bruno Verrashten. And on our agenda, we have the latest LTS was released, the election results blog post, contributor spotlight update, Jenkins contributor summit, Google Summer Code 24 prep, and some great progress and work done in the version documentation site, adding the sponsor attribute page, or adding the sponsors page overall. And then a couple check-ins on Bruno recently has been working on getting Docker compose integrated with the Jenkins documentation for tutorials and installations. So we'll take a look at that. And then something that came up this week, just how update TLI is getting the baseline for its updates. So starting up at the top. So again, LTS 2.426.2 was released just yesterday. Everything went well. Changel are going to create our live. And thanks to Chris Stern for being the release lead. The next LTS release is scheduled for January 24th, 2024. This coincides with the short break we'll be taking at the end of the month for Jenkins LTS release work. And during the time weekly, releases still will take place. So you can expect 2.437 and 438 accordingly. For the election, the 2023 governance board and officer elections. So there was no voting this year. We only had a single candidate for each role. So the officers that were in the roles are going to continue to stay in their roles for another term. And the big change for the governance board is we are now welcoming Basil Crow to the governance board. Really great to have Basil board. Thanks for joining. And thanks to everyone for participating, nominating, and showing their support. Alexander Brendes has written a nice blog post explaining a little bit more, providing some background, and sharing some insights from Basil himself about what this means and his involvement with Jenkins. Next up on the agenda. So the contributor spotlight is live. We've talked previously. We had Alexander Brendes as the first contributor. And we just published Alex Orwell's contributor spotlight page yesterday. So he's currently there, listed as the featured contributor. And yeah, everything's going really well. We had a couple of things that I missed in the first place, like the plug-in macro not being part of the contributor spotlight repo. So something we can talk to Chris or Aravay about potentially incorporating. But yeah, everything's going really well. Next up is going to be Chris Stern's spotlight page. However, since we're taking a little bit of a break and due to the holidays and end of year, there's typically lower traffic, lower visibility. We want to truly give Chris a chance to have the spotlight shine and have that be with normal traffic, normal visibility, normal user flow. So we're going to push back the original date of December 27th, and we're going to push and have Chris's page be published on January 10th. So we'll start the new year with Chris. Chris has done a ton for the Jenkins project. We will summer off code the contributor spotlight site itself over the past year. So we think it's only fair that Chris gets a well-deserved time in the sun. And then something else that we had started talking about previously is the page navigation. So Chris has created a pull request to suggest updating the navigation of the Jenkins text logo here, because right now it goes to the root of whatever URL you are on. So if I go to Alex's contributor spotlight page and click Jenkins, it just takes me back to contributors. Jenkins.io. That is intended functionality right now. But there's been a question lately of, is that expected behavior for users if they want to go from contributor spotlight to Jenkins.io directly? This logo doesn't do that for them. They would have to click somewhere like blog and then there. So saving that effort, saving those clicks, saving that confusion, yeah, potentially helpful. So this would be a change, however, across all of these sites. So it would be the contributor spotlight. It would be the plug-in site as well, where that might be a little counter-intuitive. Someone might want to just be brought back to the plug-ins index homepage. So there's definitely a discussion to be had. And it's happening in the pull request. I've checked in with Alyssa and others that were tagged in it to see if they might be able to take a look and add some comments. So time will tell. But yeah, there definitely needs to be a discussion made because it comes down to user expectations, intended functionality, stuff like that. So are we going to vote at the end of the discussion? Because I think I remember Mark was against the change. And I was more or less agreeing with the change. So I don't want to battle at all. But how will we know which way to go? So I checked in with Alyssa earlier today, since she was one of the people that was tagged in it and was part of the initial conversation about what is expected behavior versus what is the actual behavior. So we're looking for the conversation to happen, whether someone agrees with or disagrees with the idea. I mean, we can figure that out at the end of it. If no one says anything, though, that becomes that much harder. And yeah, and Bernadette was absolutely right. A couple of weeks ago when we first started talking about this, you were supportive of it. Mark felt differently. I'm somewhere in the middle because I can't make a decision to save my life sometimes. But yeah, I think it's not so black and white in this case. No, even I am also sure I'm a supporter anymore of this change. I may have changed my mind. In fact, the current behavior is somehow awkward in certain situations. But the change would be awkward in other situations too. So I don't know what to choose, in fact. We'll see. Yeah, and that's the thing. And like you said, it's a change that happens everywhere. So while it could make sense in one case, it may not make sense in another. But is that extra step of navigating away as crucial of an issue to do this change, I guess, is how detrimental to the experience is that at the end of the day? It is tough to measure. Yeah, and I had a worse idea, which would be when you are somewhere deep into one of these subsides. When you click on the Jenkins icon, you get back to the root of the subside. And then if you click again, then you go to Jenkins.io. Forget it. OK, I think I see what you're saying, Bruno. Yes, I think that. See, I think with that, it would be similar to the issue that we're in now, though, where I click the logo, it brings you, and then you have to still click around to get back. So Mark, any thoughts, concerns, questions, curiosities on that one? Unfortunately, I don't have any. As Bruno noted, if the top left icon always takes you to www.jankins.io, there will be people who will be confused by that. There, the plug-in site doesn't really have another clickable link that takes you to the root of the plug-in site without having a trip through www.jankins.io, unless that top left-hand corner icon has exactly the behavior it has today, right? That's your return to root of plug-ins. Now, the return to root on other locations. Yeah, so no, I've got an opinion. And as Bruno said correctly, whichever path we choose, we'll confuse some, right? We can guarantee it will confuse or inconvenience some. OK, thank you very much, Mark. Appreciate it. So yeah, that will tell. Well, hopefully we'll get some more comments and some discussion happening on the pull request. We can take things from there. Next up on the agenda, so the Jenkins Contributor Summit, if Boston, it's been announced. We've got a nice blog post here from John Mark Mason describing it, adding some important dates, info, times, et cetera, about it. It's going to be occurring on February 2nd, just prior to Boston, which is going to be the third and fourth in Brussels. And we have the Meetup page for the event. So if you plan on attending, feel free to register that here and share that indication with the organizers of the event. Google Summer of Code 2024 prep has begun. We've been discussing this for a few weeks as well. We just had a call for mentors blog post published from Alyssa Tong and John Mark Mason. So we're now up to 10 mentors that have signed up, which is great. Still could use some more. The project ideas are growing. The list is available. And there are still ideas being added to it. So really great to see that much support and interest in these. There's a couple other ideas that have been getting thrown around in the last couple of days that still need to be added. Chris Stern will be adding a PR for one of those. And yeah, there's constant work being done right now. There's still a little bit before the organization application can be submitted. But we're ramping up towards that, planning the meetups for the potential mentors in January and discussing things going forward. So really great to see the amount of participation. We'd love to see more, of course. But things are the balls rolling, which is nice. Bruno, any other insights on Google Summer of Code that we want to share today? Or does that cover everything? Pretty well. Yes, pretty well. OK, great. Then next on the agenda is the version documentation site for Jenkins.io. This is something that's been being worked on for some time now. It's part of Google Summer of Code 2023. Vandeet and Chris Stern have been working on this. And they are really close to release, or at least getting it integrated into infrastructure. So they've got the docs.jenkins.io almost ready to go. And then Vandeet and Chris are looking for review and feedback on that's not the addressing. So that link isn't leading to the right site. But I can get that really fast. So this is the updated version documentation site that Vandeet has been working on with Chris. Everything looks great. Like I said, they're just looking for feedback, reviews. Tim Jacome was actually taking a look at it earlier and noticed that there were some images that were in line. And so they were extending past the table of contents. Vandeet's already on top of that. It plans on submitting a PR. Everything looks really great to me. So it's really just a matter of making sure that everything is OK, lines up, and content is accurate at this point on the version site. They still have a couple of things to take care of to get that integration started with the infr team. But they're asking for the feedback and the review so they can do that part. They also have a repo for this under Jenkins Docs. So yeah, everything's pretty much on the doorstep waiting to go in, which is really exciting. And it actually looks like Vandeet's joining us now. Vandeet, I'll give you a second to get connected and everything. But if you feel comfortable or you want to talk about the version documentation, it'd be really nice to have you share your insights. Everyone, a sorry I couldn't hear you. I just connected my earphones. Can you repeat it for me? Yeah, no worries, Vandeet. We were just talking about the version documentation site, going over some of the notes from the previous Docs office hours. And yeah, just wanted to give you a chance or some time to talk about our share insights. I know that in the Gitter channel, you'd asked for a review of the site for any inconsistencies or any issues anyone else might find. So yeah, I just want to give you time here. OK, OK, yeah. So currently what I'm working on is I am clearing up the Endora build errors. That these are mostly about the linking. Interpales linking is completely different between Austrex and Endora. So that I have done. And I think around 80 links to each pages, like interpages, is left. After that, something I need to share is for the GSOC pages on the Jenkins Docs, the version Jenkins Docs, the table of content that is on the left side, the left side one, table of content. I still have to put it in a nice way, since currently it has project ideas for each page in a dropdown. And it is making it really, really long to scroll. If you go there, you can see it. So I think I would need some help to what to show on the front. Yeah, if you go to the projects. No, no, left bottom, left bottom. Jenkins user documentation. Yeah, I guess it will be in the projects. Yeah, see currently under the GSOC section, it has Google Summer of Code. If you drop it down, if you drop this one down too, on the left side. Similarly, this makes it really huge. And if we all drop down other link, other dropdowns too. So I think this will need some help to what to show on the front. Do we intend only to show about current GSOC of current year and the previous one, or all of them stacked, and we don't show the project ideas, because the links to the project idea will be on the main GSOC page of that year. So Vandit, my wrestle there is I would consider the GSOC materials not to be a version documentation topic at all, right? Yes, it's not. It's not. OK, all right. Yep. Since you can see the default one, default or the latest tag, we have to make it uniform. I think only two of them are default. What Chris and me agreed on way back was we will name them, give it a label tag of latest. So yeah. So we need to rename it to the latest. I will write it somewhere so I can do it. And currently, if you go to the download page, it is if you scroll there, download and deployment. It's not going taking you anywhere. I have fixed it. I have linked it to the current Jenkins.io download page for now, because this page is built with Gatsby. So it will be hosted separately. I'm not sure I understand what you do. So what I see is a page that doesn't render correctly. Your intent is to replace the current downloads page with one that's rendered with Gatsby instead of the way it's currently rendered with Ostrich and Ruby. What I meant was when we click on it, we don't go to the download page. If you search on Jenkins.io download page, this is not it, because Gatsby is rendered with Gatsby. So because we don't have the Gatsby site up, we can't link them. So Kevin, if you click in the top right-hand corner, download, I expect that link to take me straight to the actual download page. I don't think so. I don't think so. That works like that, because the banner, the top banner, is exported from Jenkins.io components. And it just appends the current URL. So it's just going to slash download. But on the main Jenkins.io page, you should see this. This I have already built with Gatsby. When it will be up, we can link the Jenkins download deployment button to that one. OK, so Vandi, just to be sure I'm understanding. So what you're saying is that on the current GitHub.io site, on the prototype site, what we see when you click the download link is it takes me to a download location that is slash download, but then slash latest slash index.html. Kevin, if you just rewrite that URL as slash download, I assume it's still the same page. OK, and Vandi, what you're saying is this will eventually be a Gatsby-generated page. Yep. OK. And basically since, yeah, hey, Kevin, go on. And I was going to say, go ahead, Vandi. Since the Gatsby site is not up, we can't link it to that one. So I have linked it to the current Jenkins.io. I asked it on the GitHub channel to Chris, and he suggested me to do that. And I was also thinking the same. And I think that's all for now, that I can remember most of the things are working properly. The one issue I can think of right now is some links are not getting in the error log. Some links may not some links, not most of them, but some links on the page are not working properly and they're not also getting in the error log. So I think we can add it in the banner that if you can, if you find a link, you can create a issue or something like that. I think they'll be really low since I have checked and the error logs came out. So most of them are working. And some links that are orange on the Jenkins doc site are also not working. So I am also fixing them right now. If we go to project on the, yeah, yeah, that one, that one, yeah, exactly that one, like that. So these pages do exist, but they are just not working. So just I need to fix how they are linked. Currently, if you tap, if you click on them, only the URL is getting appended with that if you say on the top. Yeah. Yeah, it's adding this, everything after the hash mark, basically. Yeah. So it is the location. It is actually the location after the hash. So I will just check why it's not working on some pages because I have uniformed all the links. So there might be some other issue. I'll check it when all the error logs will be cleaned up. So yeah, that's all from my site one right now. And then just to clarify, you said you've got this site already essentially built in Gatsby for when you go to link it in the version site, you said. Right? Yeah, yep. Okay. So this is- The code for that is available on Jenkins Docs GitHub repo, on the same repo. Thank you very much. Yeah, you were saying something. Sorry to interrupt you. No, no, no, no, nothing to worry about that. Yeah, I was just asking, I was just clarifying for myself. Anything? Yeah. So no worries, all good. Thank you. Awesome. Great. So yeah, is there anything else to be aware of or anything that we should keep in mind when looking for anything or when reviewing the site, Kondi? Everything's been covered, I think at this point. There's one thing I was thinking of proposing to Chris that Chris helped me with the local installation, local Playbook file. So basically, Antora uses a Playbook file to generate the Static file. So I was thinking of proposing that we create a make file target of make local and make prod. So you don't have to change locations. That will be much easier for the local setup when someone else will be doing it on their local machine. That is something I am thinking of proposing. It took Chris, I still have to form a complete structure if I'm proposing something. What will be the benefits and some disadvantages if there will be any. Great. Thank you so much. Really appreciate all the work, Kondit. Yeah, we're really excited to also just see the progress of this so far. It's going from Google Summer Code to now. It's really exciting. So thank you. Kondit, I had the action item with Chris. He and I discussed yesterday in another meeting. I forget what the meeting was. That you're at a point where you're hoping very soon to make it to be very near complete, or at least near to a point where we'd be ready to deploy to docs.jenkins.io. So over the next two days, it's a really good time for us to evaluate and look for any other problems on your prototype site. Is that still correct? Yep. OK, so these next two days are very, very valuable for us to give you feedback on the prototype site. Yeah, it's the weekend, so I'll be hyperactive on the Gitter. Just bring me anything. If I can fix it in the next five minutes or 10 minutes, I'll do it. Great. Thanks. So next up on the agenda, we have the adding the sponsors, either to the download page, or what we've been discussing and what Bazel's created is having a separate sponsors page. We've been discussing things like what levels to use, what kind of denomination that means for the sponsors, and how we can properly take care of all this and list everything. So right now, the PR is there, Bazel's got a mock-up of the page, which looks really good. Mark suggested using the Olympic medals for levels, as well as the aforementioned anchor and mirror levels. So if anyone has any strong opinions otherwise, I think that works really well. And I think it makes sense for the financial component and for the non-financial aspect that some of these sponsorships include. So I think that's a really great idea and also provides the recognition to the sponsors that we want to make sure is present on the site. Mark, any other notes on the sponsorship stuff? Or just speaking about it. Bazel reported that he now has access to some of the data that he needed in order to do a little bit more refinement on the prototype. And he's going to go ahead and do some further refinement. Fantastic. Thank you very much. And so now we are at time. Bruno, we have put the Doc Compose and Update CLI baseline pull requests on here. Do you want to talk about them? If we are short of time, we could talk about that next week. That's OK. As you please. OK. And for a warning, next week I won't be attending. Yeah, no worries. So speaking of which, does that mean next week's Asia Docs office hours is then canceled? Will be canceled. Yeah, it's my 40th wedding anniversary. My wife is going to get my full attention. Rightfully so. Good call. Yeah, and I'll still be here. So we'll have regular US Docs office hours. And then we'll talk about housekeeping for the next week, next week. Yeah. Yeah, that wraps everything up for us here. Anyone else have anything they want to share before we wrap up? Nope. Cool. All right. So the video will be available in 24 to 48 hours. Stay safe, take care. If we don't see you next week, happy holidays and enjoy the end of the year. Bye. Bye-bye.