 Okay, welcome everyone this is Google see this is now docs office hours, and I'm going to change the title here. Fair enough. I may actually now I'll probably create a new document for our ongoing sessions you know. Okay, so I figured I thought we would want to review Wednesday's meetup. Congratulations enough excellent job. I need to check to see that it's okay that we end your AWS account access. As you know because of costs and whatnot so wanted to double check that whole requests and final reminder on Google season of docs timeline. What other topics. I assume you've already submitted your evaluation of success and experiment experience. Yes. Yes, I have. Great. All right, I, I sent to Kristen. Well, I'm going out of order on the agenda I sent to Kristen and to mark you that are submitting it last night and then I promptly forgot. So I have to submit it today, but it is due today so I think that's still okay. Sure. Yeah, I think I don't remember the exact time but it looked fine to me. Hopefully before noon, noon Colorado time. All right, so Wednesday meetup review comments observations go ahead. It was great to see so much interest in the topic, especially you know as we were saying earlier it's like, it's docs and it's showing like the really interesting walkthroughs, and I really liked again like how you're able to walk through and show that this is what we have. This is how it works. I think it was great to see the questions come in and shows the people paying attention interested. I thought it went really well. Great. See now any observations from you. I don't think I have anything to say outside. What Christina said it was, it was a great experience for me. Also, and yeah, I liked the question and answer segment a lot. It was really engaging. Yeah, which was nice. Okay, were the questions were the questions well enough phrased, etc. I was a little worried that the, the seed questions. Ultimately, I'm not sure was helpful as I hope they would be. And that was one where I don't know what, you know, I think it's, it was helpful. And subsequently, I think is something she keep cause it's actually helped me in preparing for the session cause one thing to consider is the mentors are not the only people that are going to be asking questions, even attendees are also likely to ask questions. So it's good to prepare even beyond the seed questions just for any questions that my hope of eventually. So yeah, it was helpful for me. Good. Okay, very good. Alright, so that's, that's, that's great. We, we definitely did not cover all the questions and I guess that's a good indicator right is we didn't cover all the seed questions. Some of them were, were not especially relevant to the, to the particular audience and, and so for me that was okay. Good. Alright. So I confess I was very nervous as you arrived late. That made me very scared, but but I think I think you would explain what happened because I couldn't explain on the course. You know, actually I joined the wrong, I don't know what happened. So Oleg sent me an invite, and the invite had, you know, a Google link. Oh, oh, oh, of course, which is that that silly default that Google does when you send the invitation. Oh, oh, that's an interesting. So I think it was when I joined, I realized, no, I think this is wrong because I know that when I joined I waited a while I was like, no, there's no way everybody's going to be this late for something like this. So I, I went to sign into beat up and that was where I saw the zoom link and I joined. And that reminds me that I had made a mistake that Oleg detected early on, and that we couldn't correct and may have cost us some attendees. I had not configured the zoom link, I had not reconfigured the zoom link to avoid to skip the registration requirement. And we like to not ask people for that information because some portion of them will drop off. So, mistake to fix in the next year. It's asked for my login detail, my details when I was trying to. Yeah, exactly. And I just filled it out because I was like, I need to get in. Right, right. But of course, our many of our contributors or many of our audience will say, I'm not sharing that information. Yeah, go away. Yeah, you're right. Yeah, so that that was, that was a mistake on my part and see others. Oh yeah so one one embarrassment for me was the slide deck. Mark assembled the slide deck at the last minute slide that the rapper slide deck, your slide deck was great Zeno, but the rapper slide deck with the welcome page etc. I just completely forgotten and don't forget that I need to put it on my, my webinar checklist. I didn't even think you were going to prepare a slide and I initially wasn't planning to prepare slides since I was doing it demo I plan that I was just going to show everything we did on Jenkins that I will probably bring up my project reports and all that but then I figure it was a lot of information I need to kind of like organize it so that was why I ended up with slides just to kind of organize the presentation so there's kind of like a direction and everything is not just scattered. Right, very good. Okay. Any other feedback there. Okay, next topic then. So is enough I had granted you access to my AWS organization. So it's on my personal credit card etc. And I assume that was what you used yesterday for the as part of the demo or are you not using it I'm not sure if you're using it at all. No, I didn't use it for demo yesterday, but I haven't used it this week because I'm dreaming this week here, but I've used it years for Jenkins on AWS and working on actually used it a bit. I tried to install Jenkins and all that on it. So yes, I've used it and I tend to still use it to finish up with the documentation I'm working on, but I don't think have I approved any costs because so far I don't think I tried to check it and it didn't show that I'm using I'm not really used to it anyways. Great. So then I need to find out what sources are because I don't understand the cost sources and I've got to figure out what that is. So that's good to know. Okay, so, so as far as you know you're not using any capacity right now. No, no, no. Okay, good. So that's, that means I'm safe to turn off any machines that I find there. Very good. That's excellent. Okay. All right, so I will, I will do that. So I'm not going to end your account access then. Let's just assume you'll continue using it. Let me know. I'll watch the expenses a little more carefully and I'll flag. If I'm worried about it because it's, it's, if my company isn't willing to reimburse me then it's coming out of my mind. Please do. Please plug it. But I don't think I am but please do if you notice anything like that. Great. All right. Hey, anything else that on AWS account access any problems you're having there are things I need to worry about. Next topic then was pull requests and I apologize. I still have not completed the review of this pull request. I will hope to do this within the next one or two days. The doc SIG meets tomorrow and it's official meeting. I would like to have this one merged before then so I can, I can have at least that part of embarrassment off my list. Tomorrow with, and this is why I care about that metrics reporting and mark that pull request off his metrics. I just remembered something. I wanted to speak about helm. Oh, okay. The helm installation. Because so. Okay. Well, while I was preparing for the session because you know the initial plan was to use helm. So I noticed there were some updates to the official Jenkins values file. And I tried installing Jenkins using helm but for some reason I couldn't get it. I use the manual even with user zero on my windows books and wouldn't get Jenkins run I had issues. So I still need to do further investigation and find out if the updates has changed anything major that's affecting it or if we need to update anything in the documentation to make it work. So, so that's an interesting one. I heard that we recently rolled from helm chart version two to helm chart version three on the Jenkins helm chart. So I assume that you had originally documented with helm chart, the two dot x version. Yes. Okay, all right, so need to revisit the helm instructions based on latest helm chart. Good. Very good. Okay, so your timing is perfect. So this also pulls in an interesting thing about how do we make sure our documentation stays current. When big changes like this go through, I think that our sig needs to make sure that we are aware, and I guess like make sure we can still run through everything. So I don't know if that needs to be added to like process or something just like our sig needs to watch. Yeah, like if it is a problem doesn't need to be changed right like we don't want it to stay out of sync and then we have the problem of documentation, not working anymore. Yeah, so should we, I mean maybe I like that because maybe what we ought to do is include the doc sig needs once a month. And what if that doc sig had a report a checklist on it which says, right now it's got a check a checklist of of metrics that supports things extracted from various Grafana images instances, etc. What if we added to checklist items that say we verified the helm install works, we verified the one to one of the tutorials works with Docker, those kind of things I mean that that seems like a good safety check. Yeah, I was just thinking like how making sure that when something big like that happens because I, I mean I don't really know offhand how often things get changed that would break but it's good to know especially with something that large that we should watch for it. Yeah, you know a lot of work to write all that stuff up and then have it change on you and it's like, oh no all that work you just did was needs to be redone, you know, like we're just like you know, we checked and it's like it would be a shame for it to get out of the considering most of the upfront work was done already. Right. And periodically check that it works, still works. Yeah, good I like that. And maybe, maybe what it should be because I'm not sure I'm waiting to sign up to do eight hours every month to check all the tutorials and all the helm charts. But maybe what we do is some rotating install where we say, every month, one, one of one sixth, or every month we spend two hours somebody, you know, invest an hour or two of testing and in that hour to check things that we think are worth checking. Right, like if anything major was updated. So. And now we have to do part of this check. Right. I think I think that that's a very healthy idea because, well, it's it's awkward when new new readers when new users come in and say, Oh, feedback on the page says the documentation no longer works. Right, and then people stop looking at it and it's like, Oh, though. Yep. Good. Very good idea. So I'll let me add that one to testing status report. Because I think I think that's a, that's a healthy idea as one, and then we regularly check with it each other here in our in our meeting in our office hours. Yeah. Good. Okay. So anything else Zenab on helm installation instructions. No, that's it. Google season of docs timeline so see now you had reported your books. You've finished. You've submitted your, your evaluation. Yes. Excellent. Okay. Oh, then I had one more which was December 17. Google season of docs are retrospective and we'll do that next week on in this session. And I'll submit that one. Anything else. For me. Congratulations. Now, Zenab in terms of I'm going to go ahead and stop the recording now I think we're finished with this.