 Welcome. It's the 29th of June 2023. This is documentation office hours topics for today. Google summer of code administering Jenkins on Kubernetes. And if those were the only two things we got to I would be fine with that. I think the other topics. I have to for war and I'll be out of an out of the office topic. Others I think can wait. Anything that you need to add Bruno. No, thank you Mark. Okay, so on Google summer of code. So let's see we've got the preview site, and it continues to evolve and develop. I'm looking forward to a presentation from Vandit next week, July 6 that will highlight the progress that's been made. So, looking forward to that. And if I remember correctly, I think he's now integrated the screenshots into it. So it looks, this looks very much like the documentation I was expecting. There was a problem with the link between articles or things like that, I think, but he has sort of that also great is looking more and more like the official website. Cool. All right. Congratulations to Vandy. That's that's great progress. And then you've got your mentoring the Docker compose process project with Ashutosh. Anything you want to highlight there Bruno. Yes, we're almost done with Java Maven tutorial. And I don't want to sound too enthusiastic, but it should be the tutorial should be much, much smaller than the existing one and much simpler without Docker and Docker, which is a good thing for various reasons. See that on next Thursday. I hope the demo goes well. And I'm even trying to run it onto Raspberry Pi. Let you know if ever that works. But yes, I know it doesn't work for Windows users yet, but we'll think of Windows users we do have to do that. But it will be after the first midterm. Well, so so is is the demonstration that he's prepping already on one of these or is it on a. Yes, it's feature Maven tutorial. I should merge it later today or maybe tomorrow, but I've just tested it with Gitpod a few minutes ago and it was working for me. There are still some hiccups here and there is not perfectly polished. It's doing good work nonetheless. I may have gone a little too far with automation. But we'll see, you know, I thought that it was too difficult to ask to the end user to go to GitHub for a repo and then clone it locally. So I did it with a script, but frankly, I think I went too far. And yeah, it's almost running perfectly. Hope it will work correctly for next Thursday demo, but we are progressing well. We're happy with that. Thank you. Very good. So, so just to remind me that means what you're looking at is you've got a better way of doing this thing here where it's the tutorial build the Java app with Maven. Instead of this terrible darkness of this long explanation of detailed, here's this dark parameter and this terrible evil thing happening here and there. You're going to give us something much, much simpler or he's going to give us something. Yes. It's just Jenkins init.sh in Maven and it just works, but I know we're excluding Windows user, which is bad. So in the end, what I end up, what we will end up hopefully is just Docker compose up minus, minus build for just every platform and it should work. Excellent. Thank you. That is, that is, that is very attractive. Thank you very much. Just, okay, this, this horror being replaced by a single command. Yeah, sounds very, very nice. Thank you to Ashko for his hard work. Great. Excellent. All right, so the Docker compose project making great progress. Anything else you want to share on that project. No, thank you, Mark. Okay, so next topic was one where I think it's, it's a group exercise for us to review this. Tanu Sharma submitted a very solid poll request a month or two ago to the documentation and is now proposing a new poll request. This one is a much bigger. Administering Jenkins on Kubernetes. So what he notes is that, hey, Jenkins on Kubernetes has no content, if I remember correctly. Right. So administering Jenkins on Kubernetes is empty. And, and whether it just means nobody's written that, that page right and so what a news is proposing is here's the high level overview that he thinks should be added and I think let's And so he asked three days ago, hey, we've got we know that air they and Stefan and Damian are the Kubernetes experts in the Jenkins info team. And so what he's suggesting is here is his outline. Let's look at it in in the deployed environment so we can just see kind of the picture that he's envisioning. So we go to documentation and this was administering Jenkins. So it's a part of this admin okay system administration. This. So this is what he was envisioning. Oh, okay. And for me this looking at this way is a lot easier than looking at the ASCII doc. Introduction and overview. All right, we don't need the trailing colon so I can guide him on that architecture and components installation and configuration scalability. Okay, and there isn't a high availability solution so fault tolerance that that's that's a possible security and access control config management. Yes. Wow. Okay, so the the outline looks brilliant to me. I like that outline a lot. Yeah, I would have liked to help but for the time being I can help with you know getting more content but I'd be happy to test it whenever something is ready. And I think it's worth us doing a doing doing exploring along while while this is being developed right while it's evolving. It would be great for us to be involved in the evolution. I monitor that. Yeah, right exactly so so here I'm going to take I'm going to actually take some time and I'm going to make some touch ups. Oh, oh wait a sec. Okay, so this is a mistake. Okay, there's there are a number of mistakes here that I can correct good. We don't use three levels of indentation we use one or two in this case to not one so that and we needed to okay so I'll need to do that separately not not as part of doing that live here there's there's more to it than that but this is an easy one for us to be involved in, at least as readers I'm not skilled enough to be a reviewer, but neither am I the structure looks really good to me to. Okay, good so I'm going to make a note here, we reviewed the proposed structure structure in Docs office hours, and feel that, and like it, like it a lot. We'll provide some minor suggestions on ASCII doc format later. Yep. Great. Anything else to note on on the administering Jenkins on Kubernetes. No except that I'm super happy for this brilliant initiative. Yeah, well I'm thrilled with with a new just willingness to do the work that's really great. Okay. Good. So that covered that covered that topic we've got one more open pull request thanks to Jeffrey Chen. Jeffrey's work has given us ultimately to pull request one of them has merged. It's already in the documentation now merged and visible, and this one is a best practices document that needs more content. And I'm really I'm not ready to merge it yet because there are if if I'm going to be so bold as to claim that we should have such a thing as best practices. I want them to be reviewed by people who agree yes that that makes sense as calling it a best best practice. So thanks to Jeffrey for starting the work, and we've got more work to do. I haven't seen any reviews from Jeffrey on on my changes. Yeah, so so there's more work to be done there. All right. Any other questions or topics on the wiki migration progress that Jeffrey's been doing. No, I know that is tedious work, but now I will just review the second one whenever I have time. And thanks for Jeffrey to be so consistent with the effort. Great. And then you had this draft PR on keeping the updates see out the examples up to date I assume that that's not received any further attention that it's it's a common note from myself. No, I haven't progress yet. I was waiting for the next version of updates and I was supposed to correct thumb bugs ahead with the Ruby releases, which is now the case. So I should spend a little time on this one and try to get it merge if that makes sense for the community and the project. Okay, so a new release of updates CLI resolves issues detected earlier in the earlier experiment. Yeah. I see issue but it's more for limitation because Ruby did something not really right with the way they handled the releases into tags. So that's why. All right. Okay. Thank you. And then this one I'd like to delay again until Kevin's available, because we've got, we've got this issue that gives us some a checklist of items that need to be touched. And I think we may want to touch them one at a time probably starting with installing Linux, and then installing windows, and then we talk about the others what order should they be in. All right. That covered and I will be out of the office this is early warning I'll be out of the office July 20. So if Kevin's not available we'll have to cancel the meeting. But if Kevin's available he'll run the meeting. Okay, and I'd be happy to attend the meeting. Great. Thank you. Any other topics Bruno. I don't have any. Thank you mark. All right, thanks.