 Welcome everyone. This is Google season of docs office hours for the 26th of October. So, Zeno, I had one of the things that I thought we might want to take on today is spend a little time doing a retrospective on the first half of the project. See what's well worked well for us what we could improve etc. And status on Jenkins.io and then blog posts. Those are the things I was aware of. Are there other things that you would like to include? Okay, so I'd like to take permission. I might not be available for the next meeting on Thursday. My wedding is actually this weekend. Oh, well, congratulations. Thank you. So, um, though I'm not 100% sure but if there's any change I'll, I should be able to attend the meeting on Thursday but just in case I'll let you know before then. I think we should just cancel the meeting in honor of your well now. Now, or is it is next Monday's meeting will you be leaving available next Monday because usually post wedding, at least for us traditionally, there's a period where the husband and wife are gone. Are you available next Monday should be canceled next Monday's meeting. Um, I'll be available. There's no console. Okay. Yeah. Great. That's that that okay, congratulations enough that is, that's, that's wonderful. Thank you. This is a lot congratulations enough you really proving that it's possible to keep life balance in work and life. Yeah, great. Thank you. Thank you. So, are you okay if we just cancel it out right now rather than rather than making a question. Okay, we're going to do it let you enjoy. Enjoy the wedding. Congratulations. Thank you. All right. Good. So I will remove it from the Jenkins calendar, etc. And so it's very clear that we're canceling any other topics you'd like to be sure on the agenda. No, that's it for me. Okay. How about then let's look at pull requests first. So we've got the skeleton PR pull request that I believe still needs. Sorry, Mark, are you sharing your screen. Oh, am I not. I thought I was but maybe I'm not that's not very helpful if all we're seeing is you're right I was not let's let me fix that. The screen sharing control. Okay, I am sorry that I am not finding the screen share control return to meeting. Ah, there we go. Sorry about that. Let's try share the screen. Okay, now you should all see my notes. Do you see the notes. Yes. Very good. Sorry about that. All right, so first topic proposed was pull requests. So the skeleton PR is still meeting my review my apologies we've got Kristen's approval and Markey's approval. So I think we're very, very close. I'll do a final review and we'll get it merged within the next day or two. Oh, whoops. No, we've got a change requested by Oleg. Ah, okay, good. So if, if that's fixed, I can override override Oleg's review. His, his workload is quite heavy in other areas right now so he may not be able to re review it. Okay. Merge. All right. And then the PR for Jenkins operator. And this one, I think had multiple reviews Kristen you want to give us a summary of that one. I'm going through this. I started, I don't think I actually had saved but I had a couple comments but mostly they were around like your echoing that Oleg had from what I can tell like going through or like kind of like walking through because I know that there's multiple branches of like, oh, if you have helmets all do it this way or not. It seems it makes sense to me like walking through it's very clear so it's like if someone was following the steps. It's like it makes sense if you're coming at it from a first time operator. Yeah, and I made a comment kind of or like I know I didn't get to say that yet but one of the things that Oleg had mentioned about the master branch, I guess that's maybe more of a question for the operator team, if they're going to really have something where you could do a release where it would be, you know, like the latest version of the, you know, constantly doing master which might might be like maybe they're testing some experimental changes for the next release and we're not ready for it yet. I don't know. I don't know, but I think it looks fine, like from from what I've done so far, walking through it. It looks, it looks really good. Okay, so this one, this one it sounds like is very much in progress making great progress. I was trying to see what what change mark he had requested or just minor wording changes okay so so usually those. Those are easy for us to have him re review and and say if the changes made are okay. Good. Excellent. And I did see that the Bob the Bob o body, the one of the Kubernetes operator maintainers has given comments as well. So that for me was a real positive congratulations. See not great work. Thank you. Okay. So this one. So you continue. Anything else on the pull requests. Okay, next topic. Running Jenkins IO.io on your computer using WSL. You want to share with us. Yes, I was also clone. Jenkins.io on my Linux. We have not been able to do that yet. So I don't have much update on this but before the next meeting I'm sure I'll be done with that already. Great. Okay. Next Monday we look forward to it. Yes. And you had done a draft blog post. Yes. I also opened the PR for this. Before I was supposed to open the PR for this. The PR. No, I've not opened it yet. Oh, you have not. I see. Okay. So that's here is still pending. Yes. And is your time going to allow me tomorrow. So we can be reviewing that before the next meeting. Excellent. Great. Thank you. Thank you very much. Anything else on the blog post. No, nothing else. So the next, the next exercise was a proposed retrospective in the past for me these have worked well if we allow anyone who'd like to type to type at any time into them you should all have have access to this document but I'm also happy to just have a conversation. While we're chat and chat about it and I'll take notes. Those are also fine. I'll paste the link to the URL into the chat. Open to any comments in terms of what we've worked well. What are things we could improve, etc. So here are two that were on my mind. Did not let sharing sections also worked well. I'm sorry, tell me what say that again. Yeah. Oh, that's right. Yes. Yes. Right. Very well. And there we have Helm chart sessions. Yes. Two of them. And was there was there one other that I had missed. Oh, I know the one that I was thinking of is the webinar on docs for a hacktoberfest contributions, as it had a piece on running Jenkins that idol. Okay. Okay. And weekly meetings also think that really worked out great. But one of the things that I've liked has been multiple mentors has have allowed absence of one mentor and still have a team. So, Marquis unable to meet today there have been times and I've been unavailable or times and wasn't for me that that that is a pattern we should continue. I think we've been pretty good about the reviewing, keeping the reviews moving forward. It's been something really nice to it's not like there has been like an obvious stall out, like, kind of along those same lines that you were saying mark where, you know, someone was had to be out and they weren't able to review other people were able to jump in. Yeah, although that's one that for me, at least I know my reviews have not been as prompt as they should be. I felt like, Oh, you know what, we're having to remind mark every meeting he needs to review this and so I've actually been been surprised that we haven't needed. I don't know where to put it actually surprised that we haven't needed a cloud solution yet. So I guess that's on the plus side. Zenop work with mini cube is great and does not require a cloud provider. Yes, so far been able to use mini cube so think we're good on that and for now. Right. Any other insights. Yeah, actually, given your, your participation or anything that you would offer. Oh, hey, not an official mentor and yet part of this things that we should consider in any one of these categories. Well, I glad that they have mentioned so many good things that worked well. The only recommendation I would suggest is to put if it is possible some reference links to sessions knowledge sharing sessions that worked very well, which is up in this document in worked well session. So other team members can benefit from exploring those sessions, or maybe they had been recorded, or if there is some, well, some pointer, if it is possible to review those sessions. That's a good suggestion. We've certainly got those. They're recorded and available on YouTube but embedding a link here will make them much more convenient for anyone who reads the notes. Good. Yeah, I like that. Okay, good. Others. Again, regarding like running Jenkins.io site on Windows in case if they know you'll have any issues. I would be glad to help in case if I can. So feel free when after your wedding when you will be in assistance. Thank you so much. I'll reach out. I'll most likely try before then. So if I have any issues, I'll just reach out some guitar. Thank you. Any, any others. I think that concludes it. I'm going to take this, these notes, I will put the, I will embed those links, I can copy them from elsewhere in the document. And the notes will be available. I should be able to post the recording in this session in about an hour or two. So it'll be available and the link will be placed inside this location right here. This will become a hybrid. So no meeting. Let me make a note here 2020 dash 10 dash. What day is Thursday. Thursday is the 29th and so. In the next session will be 2020 dash 11 dash two. And I'll put draft notes in there with us to do. Okay. Any other items we need to discuss today. I think that's it for me. All right. Thanks very much. Zina. Happy wedding. Marriage is marvelous. And great for me. Good luck to you. Talk to you next, next Monday. Thank you. Yeah, see you next Monday. Thank you. Bye bye everybody. Bye.