 cloud. Okay, so welcome everyone. This is Google season of docs office hours for September 17th. Thanks very much. And Zina, if you want to take us through the agenda. Okay, so I started working on documentation on installing Jenkins on Cuban letters. So probably if it is possible for us to review that today and discuss about it, I also configured Cata Coda and installed Helm. So I've been reading on those tools. I'm hoping I was thinking would have the session, would have had the session with Maki, but since we're unable to have that, I think I'll just save my questions, see when we have the knowledge sharing session. What else did I do? So I'll share the link right now. I'll share the link to, I started working, the draft of the documentation is in Google docs. So I'll share the link now. So I'm so for this, I'm still going to make a couple of changes to documentation. And this, this looks like a great start. Thank you for drafting it. It looks, this looks exceptional. So the idea is that reviewers like me and Kristen and Maki could make comments in the Google doc as you're evolving it quickly. Exactly. Before opening a pull quest on Jenkins.io. This, this looks wonderful. Kristen, are you okay with that, that review technique? Great. Okay. Go ahead, Zina. Sorry, I didn't mean to interrupt you. Okay. Also, I wanted to mention something. Okay. Yes. For the structure of the documentation, as discussed in the last meeting, I'm not done with that, but I, I started working on something I'm going to share with you also. That's how we intend to merge Jenkins on Kubernetes. Documentation with existing documentation on Jenkins.io. So, and this is based on notes from previous meetings and now you're refining and improving that, giving, getting more ideas there. Yeah. So, oh, no, sorry. I think there's a wrong link. This is a proposal. Okay. That one is just the structure. Yeah. This looks like the original proposal, right? Yeah. I have a document with just a structure here. So we don't have to scroll through the whole document. Okay. So, share the link. Excellent. Thank you. It is, you know, very good. Let me link into that. So scroll to the last page. Okay. Yeah. So, since I'm working on installing Jenkins on Kubernetes, I have not updated the latter part of our work on this, but for installing Jenkins on Kubernetes, I don't know. I proposed putting it on the installing Jenkins. So I noticed there are different platforms. So I don't know if this works or if it would be better somewhere else. For me, this works great. I think that's very reasonable. That means people who want to install Jenkins will find links into all the installation instructions in this one document. So that seems very reasonable to me. I might put Kubernetes. I wonder, should it be below Warfile? But really, no, it's probably more popular to do on Kubernetes anymore, becoming more popular than using a Warfile. So that's great where you put it. Right. Especially if Docker is that high up, it makes sense to have Kubernetes. Right. Right. I suspect Kubernetes is at the moment, maybe marginally less popular than Docker. Docker is probably rapidly overtaking. So yeah. Yeah, I can see that because if you're using Docker as kind of a test environment, or you just want to spin something up quickly, like as a preview and then eventually move to doing it more formally in your Kubernetes experimentation, I guess, like that would be. Right. Right. Using Docker for preview environments or test environments, or we've got ci.jankens.io that runs a Docker image of Jenkins just in Docker, no Kubernetes. And that's one step on our direction towards Kubernetes. Eventually, we're ci.jankens.io. So this looks great to me. Zina, thanks very much. Okay. So I'll keep updating this. This is current content for Jenkins.io. So I'll keep updating this template here with the new content for Jenkins on Kubernetes. So if at any point we need to create a new volume, probably the content I want to document does not really relate to anything that is already existing, then that's when I'll create a new volume. But for now, just keep updating. Great. And so when you say new volume, for instance, that would mean something if you find you need to create something at the top level here. Yes. Yes. That looks exceptional. Very, very good. Anything else you want to review on that document structure proposal? No. So really see the proposal for the insertion points. Excellent. Thank you. Thank you. Next topic we had on the list was knowledge sharing sessions. I apologize that Markey was not feeling well. But as Markey joined us, not yet. Okay. He had a meeting that he said was running late. And so there was a chance he may be still late yet to join us. The proposal was to have the session, to shift the session that we had planned for yesterday to be during Monday's office hours session. So this time Monday, is that okay for using up? Yes, that's fine. All right. And Markey had suggested he would like to do Helm and Codacoda at that time. And that felt good to me. And then if we want to have Torsten Walter do an additional session on Codacoda on Helm, that can also happen later. Yes. That sounds great. Thank you. So anything else on the knowledge sharing sessions? No, nothing else. Okay. And in your, I guess I have a question that I didn't put on the agenda. Let me put it up here is cluster access. So were you able to use Minicube like we had hoped? Yes. Yes. I was able to use Minicube. Excellent. Okay. So you, you don't, you aren't at a point where we have to do a cloud hosted thing yet. So that's, that's great. Good. Thank you. I had one item updating the Google season of docs documentation page on Jenkins.io. I've submitted that pull request. I would love to have reviews of it. I'm sure Oleg will be one of the reviewers of it. All right. I'm hopeful. I think I've made things accurate and move things around just a little bit without being too terribly disruptive. If you find something that I've made a mistake on by all means, tell me right in the pull request. Okay. Then also, I wanted to ask a question about the last pull request that I made. That's making changes to the layout, the layout. Oleg raised something in the last year. Okay. Shall we go look at that? Let's go read the comments. Let's see. Yeah. Just a minute. So let's need the closed PRs, author. Oh, no, that's interesting. Oh, it didn't finish my typing. Okay. So was it the ad Jenkins uncrew? Okay. So let's look at this one. And let's make the text big enough to read. Okay. So the concern was, oh, the menu. Okay. So is your question, how do you do that? Oh, yes. How do I do this? Okay. So let's take a look at that. And what I think you would do is this is, this is a Hamel, a Ruby derivative indentation based market language that represents HTML by using indentation as the way of hinting at what the structure of the document is. And so what we would need to do is you'd need to take, let's see, let's find the place. There should be a Google projects. Yeah. So projects. And if we look there, okay. Jenkins area meetups. Ah, yes. Okay. Got it. All right. So what this does now is it iterates over the list of projects in the, in the directory structure and places those into the sub projects. And I think what we would, we could take a simple approach and say, after doing all that iteration, we copy, copy something that looks like, where is it? Looks like, well, for instance, like this, these two lines right after this entry here. So that in the dropdown menu, there would be a new row added with a percent a dot item feature. Oh, no, no, sorry. It would be one level deeper. And it would be one of these that. So let, let, let me bring it up just to be sure that I'm, I'm not giving bad, bad guidance, but I think what we want is we want to add something to the end of this list. At least that's my proposal is either because overview is at the top, it's going to iterate the list. And so we then put, let's see if I can see double check is overview. Oh yes. Okay. So you could, you could also put it above the list. If you were to insert it between lines 101 and 102, that would, that would also work, but it's the, my mental model is either we put it above the top of the list or at the end of the list. And what you do is insert an entry there, which says, so if we look, yeah, if we, we want something that's sort of like wiki or issue tracker. So if we look at how issue tracker is done, it would be these two lines. Oops, it would help if I could copy those two lines. You could replicate here to either line after line 100 or after line 105 and put the correct text in them for where it's supposed to link. Okay. So my question would be like for the other dropdown menus, like community plugins in, in the code that's on GitHub, like in the pull request on GitHub. I'm not trying to understand your question. Could you ask the question again? I want to ask the question from here. So I can say that for this other dropdown items, they are actually explicitly defined, say for mailing lists, for accounts. Yeah, exactly, they are defined, but in subprojects, we don't have, like under the subprojects, we don't have all this. Yeah, exactly. Right, right. And that's, you're exactly correct. What you're seeing here in, in subprojects is this dash character that starts to line. I believe says we're now going to do Ruby code at this location. So this is actually Ruby that's in line inside the page. So when the page is generated by the Ruby, the Ruby page generator, it will be turned into a static page, but it actually executes this Ruby, Ruby code, and the nested dash gives us another, a curly braced section of Ruby code that is then executed as well. So if I, if I understand correctly, the way Hamel works, this leading dash means this is literal Ruby code. And then percent, a percent A says this is HTML code or becomes HTML code. Okay. Okay. I think I, that's Clara. So I'll just add another option that's after line 105 for Jenkins on Kubernetes. Well, or yeah, let's see. So, and did we decide it was, I think we did decide it was Jenkins on Kubernetes? Yes. Okay, great. Very good. So, so you're, I apologize that this is, this is, this shows a bent towards programming and programmatically generated sites. And I apologize for that, but it makes the site much more consistent because we use this programmatic technique. Okay. Okay. Let's find it. Thank you. All right. So let me make a note of that. So I've discussed how Ruby is used, Ruby and Hamel are used to break the pages. So you're, you're okay with that description? Yes, I am. Okay. Great. And if you, if you have questions, you're welcome to ask me and get her chat in the docs, get her chat. There are others there who are also familiar with Hamel. So there should be several of us available who could help with it. Okay. All right. Any, any other questions that you had or any other topics we need to bring up today? This is, I apologize for being late. Oh, well, hey, Marky, since you're here, that's, that's wonderful. Are you at a spot where you want to do some already get started on the Monday office hours topics of Codacoda and Hell? I think we've largely completed the agenda topics we had with Xenob. And if you'd like, we've got time. Xenob, do you still have time that you could stay for another as much as 30 minutes? Yes, yes, I do not. Unfortunately, I don't, we'll have to move that to month to leave that for Monday. But I do have my session ready to do for both of those. Excellent. Okay. So we are set for Monday then. That's perfect. All right, well then anything else, Xenob, Marky or Kristen? Nothing for me. Nothing for me. All right. I think, I think we can call our session done for today then. Xenob, congratulations. Marky, had you seen this, this marvelous work here? So project, let's see, here we go. Xenob has started creating the documentation. She's now five or six pages into a Google Doc, waiting, looking for feedback from mentors on the content before she submits it as a pull request. She's got a proposal for the structure here, including where to insert the Kubernetes install. And she's looking at having, we did a review of Hamel of how to do the, how to do the insertion of entering into the menu. I will go over that doc today and have my feedback shortly. Oh, excellent. Thank you. All right, well Xenob, thanks very much. I'm going to go ahead and end the meeting then. Enjoy the session. Thanks, everyone. Thank you. Thank you. Thank you all.