 Okay. So welcome to the first of our Thursday docs office hours. And here are the topics that I had seen up. Can you see my screen? Okay. Excellent. Okay. So AWS account deactivation was one topic for me. Pull request progress. Another calendar for the next two weeks. What's next. And I propose we review briefly the Jenkins wiki plan, just so that Zina bureau aware of that and, and have some notion of it and can consider it. Any other topics people would like to discuss. So under pull requests. I don't know if this is more of a question. So. Is there a way to tag pull request as working progress? So reviewers don't have to review yet. Say when you open the request and you're not done yet, it's not ready for review. Question. Yes, there is. So yeah. So let's, let's review how that's done and we can show it as part of part of that topic. Yeah. Let's be sure that we include it. That's great. Happy to show it to you and draft pull request. And how it works in the Jenkins project. Good. Sure. Anything else. Okay. Excellent. All right. So top of the top topic was this one. And I'm going to drag my screen in Z enough so that we can, we can look at it together. So what I'm seeing is. I'm still spending roughly two US dollars a day on elastic container service for Kubernetes. And EC two other. Now I don't know what those mean. And actually maybe what we ought to check is, are they in a different region somehow and you're not seeing them because of the region they're in. So they're definitely in the US East Ohio regions, which I think is US East two. Yes. But that's, that's the region you were using, right? So that's the same region you were using before. Okay. So, and you've looked to see if you could find these things and you don't see them when you log in from your account. I don't. But maybe I can also share my screen so we can see. That would be great if you'd be willing. Okay. Oh, let's see. And maybe I need to grant. Your permission is allowed. Okay. Can you see my screen? And yes, thank you. So Kristen, my apologies, we're trying to, trying to stop the spend on Google's some season of docs, AWS resources that's being done on my personal account. So we're going to use some of your time today to do that. It's all good. Don't worry. This is my EC two touch. And it's definitely Ohio. Yeah. Sorry, my network is a bit slow this evening. And that's perfectly fine. Just it's a fact that you're doing this for me is a great help. Thank you. Okay. So you can see instances running. Okay. So could you, would you be willing in the top search segment to type in EKS. Yes. Let's go look at the elastic. Kubernetes service. Let's see if it's hiding an instance, some other place. Yeah. Pick that one. Because I don't understand why it's not showing them to you in the instances. It clearly says in there, they seem to be continuing to charge me for it. But it's, it's not listed in your EC two console. Just like it's not listed in mine. It's not listed. So yeah, this is my. You can see, like, Yeah. So if you click the clusters over on the left, I bet it will tell us you have none. Okay. Oh no, you have a cluster. Good. So we have something that we can delete. Big win. Why not? I assume you're okay. Yeah. Yeah. But like sometimes, you know, if you contact the Amazon. And you mentioned things or like trying to describe what's going on, they can like point it out. But, but yeah, if you have something that's even more. So whoops, your spell. You're, you have to make correct a typo there. Oh, yeah. Perfect. All right. Big win. Wow. Okay. So is there anything else we can check? Yeah. So that is already good enough because the only place I was seeing potential charges were in the EKS cluster. So the fact that you had one is a big victory for me because it says, even though I can't see your cluster when I look at the same account. You found it, you were able to delete it. So major victory. Thank you very much. Thank you. I'm sorry for the extra charges. That's a problem. My part of part of part of this exercise is the company gets to the company that employs me occasionally gets to be asked to donate to open source. You're okay if I take back sharing. Yes. Okay. All right. Oh, that's great. So I am going to hang on. I have to make a note of that major victory. EKS cluster found. And deleted. Excellent. Thank you. Okay. So next topic was pull request progress. So I've been doing this one. I wanted to safety check with using up. If you're okay with what I'm doing, I've just taken the, the bold approach that as I find little changes, I just keep pushing them. Are you okay with that? Yeah, I noticed I'm okay. I'll just pull. On my local branch. Yeah. And, and you are welcome to. Before we merge this, we will actually squash all of this out. So we won't. In particular, because a number of the pictures that I did. Are with, with the brand new. Current weekly UI. I don't want to waste the space because it makes better pictures. But they are large and I don't want to waste the space having. Old outdated pictures in there. So I will squash this before we. Before we, or squash or rebase before we do the final merge. Okay. Okay. So, so the answer to my, is that okay with you? Yes. That's okay. We'll review. As changes arrive. Excellent. So as part of that, I've been working through and I work, I work with it in about two hour chunks. And since I'm a Kubernetes novice. My two hour chunks tend to be spent exploring this exploring that follow the directions then decoded. And as part of that, I'll make comments or make changes and push them. So don't be shy if you feel like, oh, I changed something that was important because I didn't understand it well enough. And I changed it wrong. Let me know. Okay. And the other is, I think. Likely. We'll partition the content. Into other locations rather than the scaling page. Because the more I've more, I've been experimenting with it. There's managing agents. Right. And that's, we've already got a page on managing agents. It's weak on content. So adding Kubernetes would be a big win. There's more on choosing. On, let's see, there was, there's a nice section on installing. And administering agents. Now I did have a problem that I, oh, oh, the other was I, I boldly changed. The Docker image that the Docker file content to not include Maven. From the master. Just be master. Oops, that's the wrong word from the controller. So, so be sure you check that Z now in case there's something I've missed that later on is dependent on that. And I've broken things. And the other was that I simplified plugin installation. And broadened. So the, the similar plugins are still installed, but I use two plugins at the top level to get them. One was Kubernetes plugin. The other was the blue ocean plugin. And you'll, you'll see that in the, in the changes. And I'm, let's see, the other was I'm still struggling to make the, the demonstration. Kubernetes pipe pipeline work. And I don't know why I haven't, I'm going to have to ask, actually, Kristen, I may, may beg your help on this. Somebody else's when I, I try to start it. The pipeline and it never gets an agent allocated. Okay. And I don't know why and I'm, I'm not fluent enough. So if, if I don't solve it myself within the next little bit, I may drop something in the chat asking for help from people saying, Hey, what could I be doing wrong on this? Sure. Yeah. So when Zina, when you were writing the original material, were you able to make the agents run? Yes, I was. Okay. Good. So then it must be some mistake I'm making. Only be some mistake I made in documentation. Actually, it worked for you and didn't work for me. So that highlights, it's likely my mistake. So I'll keep looking great. All right. So that PR, I suspect we're probably still a week away from merging it just because of the pace that I'm going at. Thanks for letting me take the time to go through it. It's been very instructive to me. And, and I'll keep working at it. I've, I've spent two different two hour sessions this week. And I assume it'll take two or three more, just like that. Thank you. But they can all the time. Oh, hey, this, well, this has been so educational for me in terms of. I need to be sure I know how to administer Kubernetes because part of my responsibilities in the Jenkins project is dealing with our Kubernetes server, but. I'm unskilled in that. And so I tend to avoid it. This is helping me stop avoiding it. All right. I'm glad I could help. All right. So, so the next, your question was how to tag a pull request as a work in progress. Let's go grab a pull request and let's look at one and you'll see, we can see them, the marker that's used and how you, how you activate that marker. So we should be able to find a thing. Here we go. This is a good one. It's, this is one that's proposing to add a change. And it uses this. Big draft label here. Yeah, the word draft is a nice help, but that's not the crucial thing. The thing is actually this big button draft. And if I remember correctly, we can mark something as draft. When we create it, or I'm going to temporarily mark this one as a draft. Notice I'm going to zoom this, this page in. And over here on the right hand side. They're under reviewers is this still in progress question. Right next to it. Is the word convert to draft. Right. So watch what happens when I click that I click it. And it says, Oh, are you sure you want to do this? You're going to make this a draft pull request and a draft means no review is required yet. So I'm going to convert it to draft. And notice it put up the pretty, the big button there that says, Oh, this is a draft. Now, when I'm done with that, when I think, Oh, hey, this is ready to be reviewed. I will then press this button here ready for review. Oh, right. Okay. So this one says now I'm ready to review it. And it's, it's now back in now back. Ready for ready for review by whoever. So did that help? Yeah, it did a lot. Like through the G sort program up until now, most times I don't open full request until the work is ready for review because I don't want people to have to be reviewing work that is not done yet. So I just thought to ask today cause of the AWS tutorial, it's kind of much and different from the other work. So if there's a way I could open full request on that and keep updating it to it's ready for review. But thank you. And there is. And in fact, something like that tutorial is really a good thing to put up for review because it may help others steer you if they choose to review it with while knowing that they're not there, the things they're reviewing are not yet fully vetted. Yeah. So for me, one of the things that earlier review might have, that might have helped was let me grab that the scaling one. The pictures here inside. I've shifted them so that they, they are much smaller in terms of screen width. And, and by making them smaller, they, oops, not that one. That's one of the existing ones. This one, right. I think it's this one. Let's try that. Yeah. So, so this one is a smaller picture. And it expands to fill the space so it's easier to read for the, for the, the person reading the doc. So that that's something that early review can help with sometimes saying, oh, hey, make the pictures bigger. Next topic, anything else on that topic before we go on. I think we were supposed to do retrospective. We were. Oh, my sakes. That's embarrassing. You are correct. And I'm not ready for that. You're right. That's, that is really awkward. Let's, let's get that. That should have been higher priority than any of the other things on the list. Sorry, let's put that here. Retrospective and we had, I had a document started on Google season of docs. Let me see if I can find it just a minute and we will, we will start with that retrospective. Sorry about that. Okay. Google season of docs. Retrospective. They're 29 2020 Google season of docs retrospective. Here we go. Okay. Wow, that, that, thank you very much. You are wonderful. Sorry that I forgot that. All right. So this is where we, the way I've done retrospectives in the past was try to encourage people to outline what we've got in timeline and then talk about strengths, weaknesses, improvements and actions. Will that work okay for the two of you? Yeah. Okay. So this is where you start calling out any one of those categories and I'll quickly type the notes. What things went well, what things didn't go as well, et cetera. I think we had a really good topic selection. Like not only was it a good, like something that was needed by the community, but I think it was, had just narrow enough focus to be easily accomplishable in the time period. Cause I know like, you know, I was awesome doing all that good work and then, but it's like, you know, you know, it's not a full-time position. So giving her time to be able to work on everything. It's like produced like very good documentation because I think we had a really, there was a good topic and it wasn't too broad where it got too large. So we had a lot of time, you know, discussing the, discussing what we needed to do for documentation. I think that helped make the project successful. I like that. Very good. Zina, any, any strengths you wanted to highlight? Yeah. Regular communication. The meetings. Twice a week. We were able to follow up with that. And it really helped in speeding up the work. Okay. Very good. So one of the struggles for me was, and I thought we, I thought we handled it well, but the, the. Internet bandwidth. Across continents is not always reliable. Right. And that's just the nature of it where we're dealing with someone who's in Africa and people who are in North America. And we adapted by using screen sharing without video. Worked great. And system requirements also was another weakness. Oh, yes, yes. Yeah, that's a particular one. Now, do you feel like that one worked out okay? Or for me, that one was a Kubernetes is resource intensive. Right. And. Yeah, I think it worked out well at the end of the day. I think the only time this came up, or this was kind of a block, I was running Jenkins. I was able to solve that. That's a good point. So the thing that, that I would had thought would be the barrier was not the barrier, right? Good point. Jenkins.io site on. Windows laptop. Finally ran a virtual machine inside the windows. It was a Nubuntu virtual machine. Is that correct? Yeah. Then another thing about this. This virtual machine was it's, it's really as regards resources. It's, it was kind of resource intensive, like running my virtual machine sometimes stops docker from running on my windows books because it's not able to assign enough RAM to the VM and docker. So sometimes anyway, not always. Well, and since, as I understand it on windows docker is also running in a virtual machine. So effectively you were running two virtual machines. Yep. Okay. Good. All right. Yeah. So, so that's, that's the surprise. Or Mark. That the, that Kubernetes was not the issue. Resource use was not the issue. Need. To assure. Jenkins.io dev on windows is easier. Or tell people it's not a tell, tell people it doesn't work. Use Linux. Yeah. Good. Okay. So I think we don't have windows out completely. Maybe just include more like system requirements or something cause for people that are running in version of windows, I can't really remember the exact fashion. But I wasn't able to run the BSL to conveniently and I think they were able to run the BSL to should be fine. But I wasn't able to use the BSL to my PC because of the fashion of windows. Right. Good. Okay. Then also another thing is probably we might have been able to make the BSL one issue does that we're not able to then and not to take up much time. That's why we updated out for the PM. So it'll also be a good idea to try and maybe look at the tutorial on how to make the BSL work on windows. Right. Right. Good. Okay. Other insights. So was I assume that GitHub, GitHub use GitHub workflows were not a surprise for you. You'd use them before. Yeah. Oh, review was okay. Work, work well. I know I liked. That's enough allowed me. Allowed reviewers to push directly. There is a setting that you can use to disable that. And I was grateful that you didn't disable it so that I could give faster feedback that way. Kristen, any concerns for you or weaknesses that you saw? I guess the one thing I was like, I didn't really see us have many, many tickets or maybe I just somehow missed that in a lot of our, like, or how we were planning out the work. I guess it was mostly just through Google docs. I didn't know if it would be better to have tracked that somewhere or like to show. To point to stuff. I don't really know if that was as important for this project, but I don't know. I think it might have been a good place to like source it early feedback. But really, I don't really have much that was negative here. Overall, the product, the project was really good. So a lot harder to find things that are wrong. Well, but I think that's an interesting one because GitHub issues. And a GitHub and GitHub projects. Are both being used in different parts of the Jenkins project. Portions of the jank of Jenkins. So. GitHub issues are available for Jenkins.io here. We could have used issues to track. And a project is, is an interesting one for me. It was, I found GitHub projects to be something lighter weight than Jira projects than Jira epics. But we didn't use it. So that's an interesting idea. Yeah. I mean, have you worked with GitHub projects before? Or just with GitHub issues and pull requests. Okay. All right. So it would have been unfamiliar to you, just like it would be to many others. Okay, good. Jira epic. Good. Okay. And maybe I should rather than saying Jira tickets. Chris and I think what you'd said was not many tickets. So you wouldn't object if we use GitHub issues. You don't care what ticketing system I presume, but rather that it might have helped clarity. If we'd used a ticketing system. Right. Yeah. I don't really care what ends up being used. And sometimes GitHub is easier. The issues are easier than it's right there in the repository. But I didn't know if it would be like it. It's kind of like publishing a timeline of what would have been expected or like kind of maybe being able to share that out with the wider community. Right. Right. Yeah. Yeah. I mean, I mean, I mean, And then just have a chance for people to make comments on that versus like, cause we were doing a lot of things on Google docs and that was great for like, you know, going and editing and things before making the pull request, but it would be given a chance for maybe some other people, the community to have some, say something or have input or just be like, yeah, I'm really excited for this. And it's something they can track and follow. For when it does get released. But I mean, that's kind of like not, it's neither here nor there to me. Okay. Good. Okay. I think there was some struggle initially where I'm not sure we were as clear with the outline. Zina of you, you overcame that pretty quickly, but should we have started the project already with an outline in place rather than having you develop it after we start, after you started the official writing. Yeah. I think it will have been, yeah. Because part of the proposal to, to, yeah. Yeah. Okay. Starts. Outline creation is a good definition. Exercise. Rather than content creation exercise. I think most of this content. Andy, let's see any other, any other things like that where we say, Oh, we could, we could do this better or do that. Oh, we're, we're times times were sometimes a complication. I think the times are finding times that worked. For everyone was, well, it was crucial and sometimes challenging, right? Because it's end of your working day and in the middle of Kristen's and my working days. Yeah. Yeah. Yeah. And then also, I think it's to be great. If the knowledge sharing sessions could be. During the community. Period. Oh yes, good suggestion. Okay, that's. Yes. Yes. Very good. In the community bonding period. Well, and let me put a note on that. I felt like the knowledge sharing was a real strength. That we got, we, we had great information from them. The, the improvement for me was due sooner. Knowledge sharing sessions. Very valuable. Whoops. Okay. Really here is better than later. Okay. Good. Other other suggestions, other recommendations. Actually, there were times there. One for me was. May need more mentors. Even with three. There were times. When reviews were delayed, right? The most recent PR is still is a good example of that. Right. That's a good point. Like just any chance to have extra reviews. Right. I think that's a good point. More mentors or more. Maybe even it's just more committed reviewers, even if they can't attend the mentoring sessions. That's a good point. Yeah. Maybe that's more of it. Be getting people to review. Actually, maybe that is it. We needed a different concept. Yeah. So that's a good thing for improvement. So I think just being able to kind of reach out to other people who might have been interested in reviewing. But I will agree to on request help with reviews. Go ahead, Kristen. Excuse me. Aside. Oh, sorry. Oh, no, you're good. No, I'm sorry. I was just saying that that was it. Okay. So, um, aside the fact that mentors might not have time also then. Consider. You know, there might be people in the community that has more knowledge about the topic we're working on. Say, for instance, Tostin reviewing the full request on health. And things like that. So I think that's another reason to get. Good. Very good. I like that. That. And that should probably be. We should probably do that prior to start of community review. Yeah. So which means we need to highlight specific topics. We intend to work on. So we can know. Reach out to the community. And. About specific. People who are going to be. Just topics. When. Contents is ready. Good. Yes. Excellent. Okay. Any other things that come to mind as possible improvements. So how about as a proposed as a draft action plan. Mark. Um, Summarize. The improvements. And then we'll go to the pages on Jenkins. I'll. Uh, refine the process description there. To include. Proposed improvements. Because I think. This one. And this one. And this one, all three of those. Can be just part of our standard process in 2021. Yes. Any other action plan that you'd like. So this didn't address our WSL one challenges. Do we want an action plan relative related to that? Um, so I like mentioned. I don't know that he. Might have been able to help. So I don't know if there's a possibility. If there's a way to work with him. So maybe like work on a tutorial or something that could help. So far. Okay. Yeah. So his, his experience with WSL one. And how it works. That's good. I like that. Um, he could help resolve the issue. Then I could work on it. Good. Okay. So is he not, do you want to attempt to schedule that session with him? Would you like me to schedule it and facilitate it? Yes, please. Okay. So let me. Let me see. It will be after January. He's largely unavailable during the holiday period here. Great. Okay. Good. Anything else on our action plan. So we had mentioned tickets. Do we want to. Or an outline and between those two, it feels like we ought to get something there. Is that something we put in the process document? Yeah. So include. Outline and destination for the content. Destinations for the content. In the proposal. Good. Okay. Any other suggestions for improvements? Okay. Well, so let's. I propose we call the retrospective done. We're a little bit beyond our typical 30 minute limit. Okay. Okay. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. I think I have to, I have to run to another meeting, but. I'll catch up with. Well, and I think, I think these other topics could easily wait until our next meeting. So I'd propose let's just call them as let them wait. So long as we can agree on the next one, which is calendar for the next two weeks. Okay. Yes, I have. Kristen, that okay for you. So we'll meet again on. Oh dear. Wait a second. I better check my calendar to see if it's January 7th. Okay. January 7th is our next scheduled meeting. I am out of the office on that day. And unavailable for a personal thing. And so. I don't have access to any of the accounts, but I'm probably going to be out on the, yeah, I'll be there for the January 7th meeting, but I don't have access to running the accounts. So. I would ask Marky. Let me check with him and see if he can do it. All right. Okay. All right. Thanks y'all. Thank you. Okay. Thank you. All right. Talk to you in the new year. All right. Bye. Bye.