 Welcome. This is Jenkins documentation office hours. It is the 8th of December 2023. We've got topics for today, LTS coming up, contributor spotlight, contributor summit, GSOC preparation and version documentation. Chris, any other topics you want to be sure we add? Nope. Okay. All right. So first topic, the change log and upgrade guide for the next LTS has been merged. Chris, you're the release lead. Anything else you need from documentation? Don't think so. Okay, great. All right. Contributor spotlight. Yes, congratulations. Contributors.Jenkins.io is online. Chris, thanks for your amazing work on it. We've got the first, the first contributor spotlight, Alexander Brandus. We've got the next one upcoming in the next few days, right? Within a week, in less than a week, we'll have Alex Earl. And then I've seen a pull request. Chris, I think for you next. Yep. Yeah, thank you. Thanks very much for answering the survey and thanks for being a Jenkins contributor. Any other thoughts on either of those? Nope. Okay, contributor summit at Fosom. So from Hong Kong, I assume Chris, you probably won't make that trip. But it's been announced and agenda is being gathered participants, etc. Hello, Meg. Welcome. We've spent through our several topics. So contributor summit is coming in early February. And see the notes there. Google summer of code preparation has started. So Chris, you want to give us a summary of what's happening there. We have composed at least of potential project ideas, but we are still gathering more ideas like as they come. And we are going to have a meeting today to discuss like what's what will be the next steps. Good. Alright, so coordinating meter in about 12 hours. In 12 hours or less. I think we'll have a meeting today and I think tomorrow because it's getting late, but yes, exactly. Now I did see a question from from Alexander Brandis that I was interested by. I was interested by it because repository permissions updater as code was an interesting idea for infrastructure. And I had had a back and extension index or replacement. I don't remember though if that one got into the list or not Chris, do you remember. I don't think so because it's a short project but I can add it. Okay, well, it's long enough to do to be its own project. Yeah, and I'm one of the things that Basel Crow suggest is hey for for really successful projects we may want to prototype them. And I haven't done the prototyping on this one but I think it's a doable thing I think it's feasible. But I think he's right it does need a prototype before we decide, and I would hope it's a short project. You know, they offer they offer short projects that are roughly half the duration. Is that right or half the half the time investment. I think it's 10 weeks. Okay. And a long project is a regular project is a regular should be. I'm not sure. I've changed the format so like we now have small, medium and large. Okay, all right. So, so well so this one, this one needs more exploring then I'm, I'm very much interested in it because this page is broken. Right, so if we look at the extensions index. We get this very sad story that the get plugin for instance which definitely has extensions is not anywhere on this list. And it's not on the list because any plug in that enables incrementals disappears from the list. So any plug in that's modern disappears. And that's not a good thing. Yeah, I'll make a PR for it. Okay, great thanks. And maybe for the RPU project to but not sure. Great details. All right. We need we definitely need more details for the project ideas and we need more mentors for the projects, right the reality is we've got to have have mentors in order to have workable projects. Yeah. All right. Anything else you'd like to highlight on Google, Google summer of code 2024. I'm not really except maybe like many people have expressed interest as like contributing as a contributor in the future. Like I see some activities in in the various GitHub we pose for Jenkins. It's good time. Okay, so, so it continues to be a good way to invite first time contributors. Excellent. Thank you. Next topic that I had was the version documentation site and I think for me this one is the big one for today's discussion. So you had asked a question and get her what what will it take to deploy it. I think we are about ready to deploy the entire site. So at least the version to talk to me. Okay, so ready to deploy to docs dot Jenkins that I owe. Good. Now would you be okay, I'm a little concerned that I don't want to lose functionality but deploying to docs dot Jenkins that I owe does not lose any functionality right all it does is gives us a whole new site. Yep. Right so new site. No risk to existing functionality at all. Because the next step might be a bit risky and this stop should be fine. This is a safe step. Good. Okay. Now, if would you be okay if we said if we put. Well I guess let's let's see if we put that if we were to deploy it to the new site. That would let us test drive. Making changes to both sites. Right to old and new. And maybe maybe let me put a note here so changes to old and new, comparing content between old and new, comparing navigation between old and new. We're not seeing many downsides to it. Just the idea being hey let's test drive, try it there and see what we get. Today it's already available on the preview site. Yeah. And, oh, and then it even has the current nav bar with contributor spotlight in it. That's kind of yes. Nice. Very, very nice. Is there any possibility of somebody who's brand new to Jenkins comes in and finds because of the URL docs that Jenkins that IO and doesn't realize they're on a test site and doesn't matter if that happens. Good question. I think I at least I've got a proposal to offer as a as an idea. Right. So, what if we created docs Jenkins that IO but did not include it into the navigation menu, but did not include it into the nav bar. I would there's so many docs that something or other. Oh, you think that's not enough hiding, huh. Maybe. My suggestion was more banal was just to throw banner across the top. So Chris, what do you think would it be possible to put some hint here that this is beta or this is next generation. With a link to the current one. And as I said, I don't think it needs to be. I think it's a small number of people who would get there. And I think it's a small price. I mean, most of the information is the same. They're probably going to be fine. Okay. We can try to see not like they're, you know, oldest child is going to be removed from them permanently or something if they read the docs here and said the whole site. Okay. So open question. Can we can we add some indicator to each page to each page that it is not that it is an evaluation copy. It's a valid valid question. Now, Chris, I see that we've only got 2.401.3. Oh, we're going to have only one version because like we don't, we don't like we have to. Because it's kind of hard to like keep track of which versions which before we start. Right. So, so then the initial would be, I assume the initial would be 2.426.1 or are you thinking the initial will be something older than that. Something new possibly update all the content. Okay, can we update the version to most recent release. Now, now should we should we attempt to have an older version as a snapshot that people could use to navigate between versions. Or is that that's is that way beyond where you're where you're ready to be Chris right now I see one version in the pick list. Um, it's, it's going to be only one version when we start because I guess to track, like, we, we, it would be too much work for me. Ah, okay. Interesting. Okay, so the navigation is different than I expected here so hardware recommendations looks like I expected. Yeah, we have to work on those. Okay. So, like, I don't think they are ready. I need to talk to him. Because they received up top. If you go back to the other. Yeah, this, this that hints that there's something amiss there. Because I think it's supposed to, it's not supposed to show. Right, right. Okay. Okay, so Chris, would it be okay if we did some given my initial initial sort of smoke test here is finding several things. Are you okay if before we choose to deploy to docs dot Jenkins that I owe we give a have a test sweep through it to look at it to see what Yeah, sure. And best to report issues to the, to the Vandy repository there. Yeah. If I remember right that was, oh dear, I should know what the you are. Oh, I can find the URL right here. Can't I edit this page. Perfect. Okay, and it's got issues enabled. Good. Okay. So, so we can log report issues there. Good. All right. And I assume you're okay with more, more reviewers of the current prototype would be good. Yeah, because like, but, but the thing is like sometimes not ready yet. Because they just got updated. So, might need to, maybe a few more days at least. Well, and, and fixes proposals for fixes are welcomed right because, because the sites buildable by others it's not Vandy it's the only one who can build it. And the proposals for fixes are welcomed for the existing content and that's a good way for us to get for the, for the new site. Good way to test drive developing with a new site, because if I can't figure out how to do, how to do it, how to make a change that'll be a problem we've got to have other people be able to edit the site just as well as Vandy does. So you're okay if I do an experiment right now Chris in front and front of everybody. Yeah. Okay, here's windows.a doc. Oh, that one. Okay, this is a redirect. All right, so this one shouldn't be there. That one's a surprise. So let's, I want, let's find the other one that had. Here we go this one mon backing up.a doc this is one that I believe mega originally wrote. So let's grab it. Okay, here is layout section with this extra character. And I'm somehow suspecting that extra characters the problem. Yeah. Now I can't be sure that but if I open this page and look at the others. How about this one. It doesn't have that extra character. And diagnosing errors. It does okay. This one should be fixed to me, but um, Yeah, that's, We try not a page that works. Okay, so, and so now we need to go find a working page. So open this one. Okay, so here we are on a let's go back to system administration, administering Jenkins on Kubernetes is a page that or managing Jenkins let's see let's pick authenticating scripted clients okay here's one. I'm going to attempt to edit this page. It does not have the Oh, we move the whole layout section. Oh, so I don't need the layout section either. Okay, so like that. Yep. Okay, so let's commit those changes. So remove section heading from backing up. And I'm going to create a new branch so I can do a pull request fix page layout section heading. Now will this generate a prototype site that I can I can evaluate on a on the pull request or prototype sites not available here. We don't have the resources to do it. Okay, and, and that's something that I know that everything I'm pretty sure everything knows how to do it he did it for the contributor site didn't he. Yes, he did. Okay good so we know how to do it on the on the on the final site. Okay, so there and, and I could then even go in and add additional additional changes. Now this should also be a thing where I could, I could build the site myself locally right so I could do a clone of this and build it. Yep. Do you mind if I do that live. Yeah, go ahead. Okay, so I was working on another another problem that's Let's see what have we got here docs. Okay, get clone this for I forget how big the doc site is, there's a lot of data there. Okay, and I think we have to do a list. Is that what you're looking for. In the dogs, so we should see the new dogs. So, oh, we should have to go back. Sorry, I bet. Go back where one level. Because like we have to go to where the playbook is where the playbook is. So is is the playbook to the. So we go into playbook. Not going but site. We're good. Yeah, it's good to when you see this like you can like there's some command you can use and break me down. Yeah, so what I need is this one right so I've got. I need to run and so into do have it. I don't know. Let's find out. Yeah, that's right. Cool. Okay, so it's working. Yep. It's working. Okay, so I did. And if I just just for my sake, I want to check here. Okay, so I'm running node 14, node 14. Wow, that's ancient. And the MNVM use minus, minus, yes, thank you very much. Now let's try it again. Nope. Oh, I didn't install it. I didn't NVM install minus, minus LTS. Yeah, there we go. And now if we say use node. Okay, and we say NPM version, something much more modern. Okay, good. Fix my. And if I ask which node it'll tell me it's somewhere in NVM. Okay, good. So now back to the read me thing. It was. Do I need to reinstall Antora? No, just go running Antora. So like NPX, this is a command. Ah, okay, so. Not that one. Next one. Okay, which, which you say, oh, this one. Okay. Oh, it didn't do work at all. Antora version didn't work. No, it didn't. But maybe it's not been installed yet. Oh, because like, yeah, it just said, so don't wait. Okay, so do I need to CD to the playbook directory in order to run it? I think it's. No, we don't have to. Oh, maybe you do. Yeah, I think you do. Sorry. So it's it's cloning it's cloning the repository again. Even though I'm inside the repository. Okay, and now it says open the file. Yeah. Okay, cool. All right, so I've got there's at least I've got at least a rudimentary setup where I can do where the, the read me gives me local development. Now let's check out my, my. Change. And is there a way with, with Gatsby to run a local HTTP server? We work on it, but it's not. I don't think that's a way to do so yet. Okay, so it's, it's local file based for purely right now. Good. All right, so. Okay, there's my change. Interesting. How would I search for a literal. Closing square bracket. Okay, that worked. Interesting. So the. That was the only place in the source files. Oh no, I'm in the wrong directory. Got it. There we go. Okay. So here we've got several files that have. Yeah, which may hint that we don't want that. And it seems easy for me to test. Okay, this one. Doc title. Right. This one is a full on a doc from. From our, from the site. I'm going to leave this one alone. I'm not sure what to do with that format. Yeah. It needs to be updated because like the tax. So like, um, it's not tax anymore. And I'll try it on. I'm always like, I think it's like page. Type page. Okay. So here are my changes. Pushed. Oh, whoops. Wait a sec. That's a problem. Okay. There it is. Origin. Why does it not think that. Oh, but of course now I've. Now I've got the problem that I didn't build that on my own fork. Because I had permission to do it on. Von Beats upstream. Shame on me for writing to upstream. We can do that. Well, I'm just going to do it. I'm going to do a cheat if you're okay with it, Chris. What I'm going to cheat with is this temporarily. I won't do that in the future, but for right now. This way I can push the changes directly. Hotel. Okay. Now back to the no push permission to upstream. Okay. Okay. Excellent. Well, Chris, thank you. For the time with this. Thanks very much for your work with Vandita on it. And in terms of what I'll do then is view the site from. From its file, local files. That way I can do experimentation with it. Figure out what does it mean to add or delete things, et cetera. Okay. Great. And you're okay if others help with the review. So if I enlist help from Meg or help from Kevin Martins or others to do reviews of the site, you'll be okay with that. Yep. Great. Thank you. Anything else that you wanted to share on that topic. I think it's like we, we are, we, I have a discussion, like some, some discussion with Vandita before and we're trying to push for mid December. Is it like that line for to be ready. Okay. I like that. So we, that's roughly, roughly one to two weeks from now, right? So. One week. Yeah. Okay. One week from now. So, so now is the time to. Do checks. Now is the time to. Check the content. Sure it is correct. Complete. Et cetera. Great. All right. Anything else, Chris? Um, no. Meg, anything else from you? We may have lost many people. Okay. No, no. Meg was talking, but she was muted. So it was. Cause I was just pulling a cookie out of a very noisy container. So I muted myself. No, I think you guys are doing great work. I got nothing to add here. All right. Well, let's go ahead then. I apologize. I'm, I'm sort of at the end of my stamina for a long working day. Chris will talk in about, about 12 hours, about Google summer of code. Yeah. Thanks. Thanks Meg for joining. Recording. Everybody. Have a good week. Thank you. You too. Talk to you next week. Bye. Bye.