 Welcome everyone to Google season of docs office hours for the Jenkins project. Let's look at the agenda. Here's what I've got for today. And Mark, he said that he will join us a little later. He's running a little late in a meeting. So I had pull request to review cloud providers. We had some notes from previous. AWS account. A timeline concluding season of docs that I have not done yet. We don't need that topic. What's next after Google season of docs and anything else that any of you would like to add to the agenda. All right there. Let's, let's go ahead. So with regard to the pull request, I don't remember if I provided any feedback within 24 hours like I was supposed to. I doubt it, given my poor performance lately. Nope, I did not. Sorry, Zenab. So we've, we've got this one open still. So that holds merge or adapt. Okay. Anything else you wanted to discuss on the pull request, Zenab. If there are other things you'd like me to add to documentation or other things you'd like me to do it's fine. Great. All right. Wonderful. Okay. Good. Okay. Now are there other pull requests pending. I think from you this is the last pull request for the season of docs in the season of socks docs timeline is that correct. Oh no, we've got okay we've still got one more open, and it's been open for a very long time. I need to get that one reviewed as well. This was sample data files in the Jenkins.io repository. For that one, where is this really where we want to host the files. But let's take a look at that conversation because I thought that the. Yeah, this Oleg's only concern was that we needed to refer his key concern was that it needs to refer to the Jenkins info repository and not to Zenab's fork. Yeah, so, so I think I think he'd be okay with that. But what I think his concern was that in this case what you see is Zenab is referring to her own copy of the repository. To the copy on Jenkins.io or on Jenkins CI to Jenkins.io. So I think that would need to be changed but that's a change I could do or Zenab you could do whatever you prefer. I didn't put the links to the main repositories because the files are not there. So if anyone is trying to review it, if you just need to an empty page. That was why I didn't, but if you want me to change that now. Yeah, I think I think we'll have to change it because now okay, if we don't do that. Yeah, it was just for the purpose of review. So if the files are okay then we could. Because if I put links to Jenkins.io it might be difficult to access the files or see what they actually look like since it's going to be leading to a dead end. But if it's fine then I can change it now to the main repository. Great, yeah so change the destination links to point to master branch on the official repository. Yeah, excellent. Anything else on pull request topics. Okay next topic cloud providers as you know you had had requested I think an AWS account. Have you been able to log into it. Could you share with what's your big experience. Yes, I've been able to log in and I was able to create an easy to instance and I was able to install Jenkins normally on it. I want to now expand there's a lot of content I don't know if you want to have all the content on Jenkins.io because we have creating virtual private cloud creating EKS cluster adding close to scalar and all that before finally creating Jenkins. I don't know if you would like to have all this information on Jenkins.io or just provide links to references or to documentations where you could do this and just provide content only for Jenkins for installing Jenkins. I don't know short considering all the processes that you would have to do before I even have installation. Yeah, so we've we've had, we currently have one tutorial from a cloud vendor. On Jenkins.io and I'm not sure it's it's terribly well suited. It's from IBM cloud. Most tutorials from cloud vendors for cloud vendors are on the cloud vendor site. I have an opinion there my thought was to say, let's not put a detailed AWS cloud tutorial but I guess it wouldn't harm us. And, and if we have it go in as a tutorial maybe it's the right thing to do. Would it make more sense to have it as a blog post, like the one for IBM cloud that way it's consistent. Oh was the IBM cloud when a blog post I thought we had a tutorial for them as well let me look. Yeah, I thought that we had a tutorial here. Yes, there it is. So we had, but, but look, this is an excuse to say if we said we wanted to take Zenob's notes for Jenkins on AWS, why not. Yeah, I think I think we should it doesn't hurt to me it's like it doesn't hurt to have the action information I would just not put it like in this getting started guy I would put it in a separate like it's like this like the IBM cloud. That was my thoughts. Exactly. The content was much and looking at documentation for Jenkins that I just felt putting it in where there's going to make it feel out of place, because there's a lot of content on AWS and all that so putting it under systems administration or managing Jenkins is, there's going to have a lot of content that is out of context. So, that was my talk, but I think since we have something like this it makes sense to just add another tutorial on data section for Jenkins on AWS. Yeah, I think. Okay, that, and that seems sensible to me I like that if if the two of you are also okay with it that sounds great to me. It felt felt a little weird to me when I initially approved this one because it was the only one of its kind it would be nice to have an additional one. Okay, and especially if there's little tips and tricks for getting started on certain cloud like you know this particular like Amazon cloud these are some helpful settings it's helpful to have that specific things called out. Yeah, I like that I think that sounds very reasonable. Great. So, so Zina, does that address your question. Yes. Okay, now, now long term. I'm not sure how long cloudbies is willing to continue donating and reimbursing me for AWS usage. Do you have a plan, do you intend to continue using that AWS account for the long term. What's what's your, your plan longer term. Well, for now I think it's just for Jenkins. I've probably talked about long term if I'm going to still maintain the account but for now it's just for Jenkins development. Okay, good. All right. So how about if we put a limit on it let's say we'll continue for a month, then discuss further. That all right that way, that way you and I are regularly checking so that my credit card isn't getting billed too badly and I'm sure that my employer is still willing to continue donating. All right. Hey, so next topic was Google season of docs timeline. So today is scheduled as the conclusion of the writing and now the next part do one week from today, I think it's one week from today is that correct. Drive. The oh no it's this Saturday. Okay, so this coming Saturday is completion of the project report. Xenob I confess I'm not sure what. How does a project report look. I've never done this before so what's the format for me I think it's going to be a blog posts probably doesn't contain a full summary of everything we're able to achieve. I like that. Okay, that makes sense. Yeah, that's okay that's very good that it's public. It's very visible it helps the project. Yeah, okay. All right, so we'll see that we'll see that this week then. Yes. We're ready to meet the deadline. So do you think you could show that I'm, I get it reviewed in time could you do you think have it ready before the end of the day December 4. So that we can be sure it's okay. Yes. Hello, I apologize for being tardy meeting or work meeting ran over. Thanks for being here. Markey thanks very much. Okay, so, do you know if you've got. If the end of day December 4 and then Kristen, Markey and me we need to review it so that it's done by end of day December 5 viewed and merged by end of day. Saturday December 5. Excellent. Okay, super. And the next thing is an evaluation of success and the experience and I'm not sure should we just do that begin that in next week's office hours. I think likewise, Markey and Kristen for you for for all three of us. Same thing. Do we also want something is our own assemble our own Google assemble a Google Doc that we use to, to just to collaborate. Yeah. All right, and then the following week we agreed we do an office hours in the office hours will do a retrospective still okay with everybody. Yes. Great. Okay. Anything else on timeline before we go to the next topic. Okay, conclusion. Last time we met we proposed a Jenkins online meetup, December 9 to have Zenab. And I think it would be Zenab present and Kristen and Markey and I act as backup vocalists or as you know as as contributing and helping or encouraging or commenting would that be okay with you Zenab. Yes. So we use the usual web webinar format. Now, this one needs an abstract and I haven't sent you sample abstract shit so I'll send that today sorry about that. Let me put this as an action item from using up. Mark, when you send that abstract. Are you also going to link just to the steps that need to be taken for presenting the abstract and where to do it and how to do it. Oh, good suggestion you know I hadn't thought of that so that's, I'm not sure I've got a good list of those things. Good. I will draft up a I'll draft up a list and I will shoot it in an email or whichever form you'd like it to be sent. Great. So this is like a checklist of successful meetup items. Yeah, there's a jet somewhere out there that explains how to do it but I can't remember off the top of my head what it is. Excellent. Okay. Yeah, that's super thanks Markey. Okay, great. All right and Z nob is December 9 still okay for you. Yes. Okay, so it's just what are we just under two weeks away so it's a little over a week away now for a little crunch for time but I think better to do it then then shifted out one more week. Anything else on the concluding web on the concluding online meetup. Next topic what's next. Anything that you need to share their Z nob or any topics we need to refine there. This actually, and this has the Thursday time slot has been approved and agreed on Oleg was previously hosting one at a time that was three months earlier than this time but we were getting no attendance. So that change has already been made on the Jenkins calendar. Google season of docs office hours will be Thursday. At, I think it is 1700 UTC, and I'll have to look up the exact time. This meeting will be will be Kent will end December 17 and we won't do more Monday meetings will only do the Thursday meeting. Everyone okay with that plan. Plus one. Okay. That is done. Okay, any other topics we need to discuss today. Nothing for me. Everything looks good. All right. Thanks everyone. Thank you. Thank you. A number of action items. Looking forward to those. I'll conclude the meeting post the recording later today. Thank you very, very much to everyone. Cheers all. Bye.