 And share my screen. Thanks, everyone. Welcome to Google Season of Docs Mentoring. It's the office hours. Thanks very much. Here's what we've got for an agenda today. Can everybody see my screen art? Yes. All right, so I assume we want to add poll request review as a topic. I apologize enough. I have not made any progress on it. The weekend was spent testing Jenkins 2.249.2 and other topics. Do you want to talk about incremental delivery of segments further? Yes. OK, and transfer of org admin that continues as a topic. All right. Any other topics we should put on the agenda? Also, I'd like to ask Maki if there's any updates on the issue I was having with user group. OK. Oh, so I have another one, I guess. Should we have a helm chart session at Torsten Walter now that he's back? That's just an open question for the agenda. OK. And that's the deal. Great. Any other topics to put on the agenda? All right, then let's work through the agenda. Poll request ready for review. So again, seeing of my apologies, I have not reviewed it. I hope to review it today or tomorrow. So sorry that I didn't get to it yet. Maki, did you have anything you'd like to report there? I know that there's two PRs in. Am I correct, seeing of? Yes, you are. Yeah, I reviewed one of them. I have not reviewed the second one. I will have that done today. OK, I also like to ask some, I forgot to add that to the agenda. I'd like to ask some questions regarding the structure of documentation. That's the second PR I opened. Right, I saw that one, and I was wondering if it was supposed to be like delivered first because it was talking about like being a framework versus the second or the first PR that was submitted, which was the installation guide. Right. OK. OK, so would you like me to open up the PR? Is that this one, the skeleton? I have a Google Doc here. I think it would be easier to use the Google Doc for the structure to explain. Would you like to share your screen? Yeah, I've just stopped sharing. If you go ahead and share your screen, we can take a look at the Google Doc. OK, can you see my screen? Yes. OK, so I don't know if you remember this Google Doc. When I started working on installing Jenkins on Kubernetes, I created this to show the section where I'll be adding it on Jenkins.io. So I added additional content to this doc. That's what is in that request I opened. So for administrative, these are the initial topics we talked about. So what I did basically was to pick out sections from this proposed content and fit them into Jenkins.io. So for administering Jenkins on Kubernetes, I don't know if this is OK. I put it on the system administration. Let me open Jenkins.io. That's here. Oh, there we go. OK, now I'm seeing it. So the idea was to put it here at immediately below system administration is administering Jenkins on Kubernetes. See now, I'm afraid I'm not hearing your comments. Maybe others are hearing it, and I'm not. Markey, Kristen, are you hearing? No, I'm not hearing anything. OK, all right. So we may have just lost her audio. So while she's getting back to audio, any of, oh, OK, I assume she's reconnecting. Any objections from the two of you on that approach, putting system administration for Kubernetes inside the system admin section? I don't see a problem with that. I mean, the other option. More consistent, because if that's where you're going for system administration to answer those particular questions, maybe it makes more sense to put it there anyway. So the other alternative that was on my mind that I don't have a strong opinion one way or the other is should that that should. Hello. Oh, hello, Zena, you're back. Great. Yes, I am sorry. OK, so as I was saying, I don't know if it's OK here. Optionally. Oh, no, I think she disappeared. I think we may have lost her again, yeah. Yep, she's dropped out of the participant list completely. So the other thought was just like we have a managing Jenkins chapter and a system administration chapter and a scaling Jenkins chapter. Conceptually, we could have a Jenkins on Kubernetes chapter. But for me, my personal, I think, somewhat preference was put the content inside system admin and inside installing for Kubernetes rather than having a separate top level thing for Kubernetes. I'm in favor of that. OK, all right. I guess for me, whatever would just be consistent with how we have it for other groups. That's what I like. Right, and others, for instance, the Docker install directions are inside the install. The instructions on how to manage pieces in Docker are inside the system administration chapter, if I remember correctly. Zena, you're back. Yes, my network is kind of bad this evening, sorry. So we were just discussing. I think your question was, should we use put the system administration related content in the system administration chapter or somehow put it at a top level entry? Is that your question? Yes. And I think that the consensus was that putting it inside the system administration chapter sounds really good to us. Does that seem sensible to you? And does that fit with how you'd like it to evolve? Yes, actually, that's what I did currently. The pull request I opened, that's where I actually put it. But I just wanted to confirm. Excellent, very good. So we can review that pull request as is, and it's using that structure already. Yes, yes. Very good, OK. So that makes me even more guilty for not having reviewed it. Excellent, good. OK, no, so that's the second pull request. The one you've not reviewed is the first one. The first one just has content of this, but I opened another pull request, as I mentioned in the last meeting. OK. Great. OK, also for cloud providers in the content on Jenkins.com, I didn't really see something relating to cloud. I don't know. So I just created a different section for Jenkins on Kubernetes and put it on there, but I've not added that to the pull request. I don't know if that's OK, or if there's some way that we can improve the information for cloud providers. So I'm not sure I'm understanding the question. Is it that? OK. Let me share my screen again. OK. Can you see my screen? Yes. OK, so for this information here, cloud providers, they're setting up CI, CD pipeline, and all that. So I was saying on Jenkins.io, I didn't see any existing section where this cloud provider information will fit in. I don't know, except if I missed it. So proposing creating Jenkins on Kubernetes session, I'm putting cloud providers on dynes, except if there's better option, but I'm not sure of that. OK, so then for me, cloud providers would be a system administration attribute. So I would have expected it to be under system administration, but I'm OK with it top level as well. The is yours. I'm impressed that we've got anything to say right now about the cloud providers. I thought that the things that you had later in the document were just links to the documents that are provided by the cloud providers themselves on how to use Jenkins in their cloud. Yes, so I've not written on the cloud providers yet, but since we spoke about the skeleton of the whole documentation, so I just thought you wise to just take the content as a whole, then subsequently rebuild the content under each section. That makes sense. OK, thank you. So this is as far as the placement of cloud providers. I mean, I think it could either go top level or in the system administration. I don't have a hard preference. Yeah, so that's where you've placed it is fine. So it's and that is a skeleton that's a placeholder and you'll populate it as we get more information or we might offer the cloud providers. Hey, Google, if you would like, this is the place where you put your material and this is good. I like that. OK. OK, so I think that's all the question I have on the skeleton. I'll just update the full request as far as discussions. OK, so then I think that answers the topic we had on incremental delivery into larger structure. You've proposed a full request representing the larger structure. Yes. Next topic then was the user group issue and more conversation and discussion. Marky, I think that one was where you had done some user group investigation. I'm sorry, I was multitasking. Can you repeat that? Yeah, so there was a question that I think you and CNOP were investigating last week relative to something with the user group. So this is the run as and when CNOP runs it as zero, everything works because that's considered rude. When she runs it as 1,000, it is running into a permissions error. I tried this locally and when I switched the port numbers, I think it was between, I can't remember, it was like 1024 and 1020 maybe. I got it to work. Now, when you switch the port to CNOP, you still have the same problem? Yes. OK, keep that on the list of my action items. I'm going to do some more looking into it. CNOP, is this blocking your progress or you're able to work around it and continue? Yes, I've found a workaround for it. I just wanted to see if there is something, probably a step I missed or something so I can update the documentation if it's necessary in case there's someone else that misses the kind of issue. I think for now, I'm sorry. I think for now just operate on using zero. Yes, I've gone past that and I'm good for now. OK. Yeah. All right, excellent. Thank you. Next topic was that a possible Helm chart session with Thorsten Walter. Now that he's back from vacation, I guess the question is to using up, are you interested in a session with Thorsten or was the Helm chart session that Markey provided already sufficient and an additional session with Thorsten won't help you much? Well, the session with Markey was really helpful, but I don't think it's worth to have another session with Thorsten. Just in case there is. Great. So how about, let's see, the last time we attempted that, I tried to schedule a time that I worked for my schedule and completely failed. Do you want to reach out to Thorsten and ask him because you and he are both in relatively nearby time zones. He's in Germany. You're in Nigeria, and so you may more easily be able to find a time that works for the two of you. OK, I'll do that. And if you need access to the Zoom account, or if you need me or someone else to host it during an odd time, just let us know. Yeah, you can either bring myself or Mark. I think both of us have access. OK, thank you. Great. All right. Next topic was transfer of org admin. Markey, anything you want to report there? This is still open. I know Oleg said he will take care of it this week. Great, OK. And I have one more item that I forgot to put on the agenda. I'm going to be out of the office Thursday and next Monday. I'm going to go play with my grandchildren. Nice. It is grand grandchildren are the best. They are absolutely the best. I'll have fun. There's nothing better than playing with grandchildren. Nothing. But that means Markey, will you be available to run this session, Markey, through the CDF Zoom account? Yep. OK, great. And likewise for next Monday? Yes, I can. Excellent. Thank you very much. Sorry for my being out, but I'm actually not going to apologize because I get to play with my grandchildren. Yeah, don't apologize at all. All right. Any other topics we should review? That's all for me. All right. Thanks. Recording will be posted about an hour from now. Thanks, everybody. Thanks. Have a good evening. Good day all.