 Welcome everyone. It's the 16th of September. And this is documentation office hours Asia. Topics I've got on the list for today action items. DevOps World 2022. Hacktoberfest. And any other topics that you'd like to add to the list. Okay, all right, good. The Hacktoberfest when we spent significant time on it in Europe office hours and I'd love to do it again here if you can, if the two of you can stand that. It's been really good to go through the preparation work. All right, actually, I saw last week you were going to kill me if I didn't shut up. No, you were you were you were marvelous and it was a great story to tell the show. Hey look we're making progress in every office hours session so this earlier today when we did it in Europe office hours it was the first time they've actually processed anything for Hacktoberfest so action items nothing to report of positive the things are all still on the backlog and probably will stay there for six weeks. I do have to actually I guess I should warn. Mark is out of the office. The week of September 26 through the 30th. And then October 11 or 10 through October 27. So the, the September 26 through 30th is DevOps world. I propose we cancel during that time. October 10 through October 27 is Mark take Colleen to Italy. And, and a lot of known known see fat channel so so yes we will. I would propose we cancel any objections to canceling those those during those weeks. Not at all. Okay, great. All right, thanks. Okay. DevOps world. So, we've had several blog posts arrive on various topics for DevOps world. You can read them, etc. And the modernizing a plug in or request has been switched to OPS bad choice. Let's try the. That's what I get for embedding an old URL, just a minute, we'll go find the real one now. So this thing. And if I'm lucky it will. Here's the blog post. I'm not going to be giving properly giving credit for me and for dirage writing it and I upgraded dirages. biography based on his submission for a Google summer of code. And so, Meg, you're certainly welcome to review would love to have reviews, anyone else who can. So the. Here's the link now. Oh right, I know what it was I had to change the location. Because I had scheduled it in the last guest publish in June, and it's only September now. Okay, and you meant to have this video here showing October Fest of 2021. Yeah, because that's when this was created. Okay. So the video is just a. A link to the to a playlist of five videos that were all created during that time. Ah, that's right and you're not redoing those you're just doing a class based on that material right exactly right so we're using what we what's what's happened is inside these pages are links to subsets of the videos. So this one for instance when you click the play button it will take you exactly to a thing that describes this precise thing. So subsets are embedded throughout these in hopes of making it easier for people to contribute. So this one is in part two and it jumps into it however deep in order to show that step. Such good work. It's been fun. It really has so. It's a pleasure to merge September 21 reviews welcomed and encouraged and happy to hear any improvements, etc. Any questions on DevOps world. Okay, next topic then is October Fest and this one where the work happens. So we've now got a page on Jenkins that I offer October Fest 2022. And it highlights how you get connected what you do list of repositories marked for October Fest. So there are right now 71 in the Jenkins. Oh, this is the wrong. Yeah, this is no this is the right one is 71 repositories currently marked for October Fest, and etc. So the challenge for us in the doc SIG is we need to identify good first issues and others. Now, I learned that there's a, we had initially done a marking of these to say hey, we'll mark them with October Fest, if they are need some skill needs and experience and will mark them only with good first issue if they are good for a first time contributor but the problem is, October Fest instructions say mark all pull request are all issues. As October Fest so good first issue plus October Fest means it's easy, and only October Fest means it's more challenging. So that makes sense. I mean, you've got it we've got a couple of issues that you don't really want work now or don't want work by an outsider. Are those also marked for October Fest. They are not. Okay, although actually this one so good thing you asked that. So here's one that is incorrectly marked that way so let's fix that. I think that would be grabbed by somebody that, like, maybe someone who is familiar they were thinking about. No, well see the problem we've got is any of these wiki migration proposals, end up creating more work for us. Then, then they're actually worth because we've got a lot of we've got a whole collection of pull requests for wiki migration right now that are stalled, because what happens is the an inexperienced contributor goes and reads the old page, and having read the old page, then attempts to do the action and they perform the transformation, but they don't know that a seven year old or an eight year old or a 10 year old wiki page. It has a lot of things in it they're now mistaken that it is wrong. And so now we have to have an expert that goes in and corrects all of the mistakes in the page. And the reality is, if we look at all the bug reports that are listed with the wiki migration label, or all of the, the pull requests with wiki migration they're about 10 of them that are blocked right now because nobody's done the be done the whole bunch of work to go in and correct all the, all the errors in them. Okay, so how does an outsider know that are, do we have, does the description of each issue include information that the wiki information itself is obsolete so this involves that or we, or do we have a general, or maybe and I said everything that is currently wiki migration are things that do not are not easy migrations or we've so we've definitely got, we've definitely got instructions here in office hours that say wiki migration is not recommended for October FES, but I think you've got a good point what we ought to do is also put text on each of these pages saying this requires additional skills, or rather it's it's not so much these as here. The issues that are wiki migration because the, the pull requests that are wiki migration there's, they just have to be reviewed by experts, but these issues should not be marked as. Okay redirect it's okay this one actually is okay if we have it, have it marked for that but in general wiki migration. No I'm not even a bother with it we're going to fix that just take it out. Yes, it truly is a good first issue but no I don't want the confusion. So the idea being issues that are that are labeled good wiki wiki migration will never be labeled good first issue and never be labeled October FES. And the idea being, I don't I don't want to add more load on the 10 that are already not making progress. Right. Okay, so, so back to the then that tells us. So if we look at the issues then that are currently labeled for October FES, what we should see as a mix of easy and good first of good first issues and issues. Interesting, wait a second label. Oh, whoops. It combined the labels. There we go. Okay, so we've got 17 open issues for October fast. And if we look at those with good first issue label, good first issue. Then we've got 10. Okay. So the last time when we met we did the first one or two pages, and Europe office hours did pages five and six. I'd propose let's take a look at pages three and four today. If two of you are okay with that that way we can try to try to have at least been through many of the pages looking for things. And the way this has worked well is if you look at these things just scan them and say, hey are there things there that I think would be a good first issue. What about 3799 that says it's and and 97 they both say they redirects. Yes, and second one's wiki migration. Well, I think it's wiki and this one should be a wiki migration, and is not correctly labeled. Okay, so let's get that labeled so good we've, we got that corrected. Okay. What about the evergreen. Where do you see evergreen 3771 evergreen Wow. I thought that was fixed long ago. Okay, let's see. I thought this was gone. Nope, it's still there. Okay, this is just about adding a banner. Maybe that's a good first issue because it well depends I think I think in this case it would be. It would be rephrased as something even more more blunt than the blue ocean disclaimer that we put in other other pages right because this one blue ocean is is actively being maintained but not being enhanced. So, so yeah, but now, now the question is what do we do with it so we should we could I'm seeing the challenge for me is I'm not comfortable that a new person could successfully do that one. I think it could be a hecktoberfest topic, because I think I think it might be worth saying hecktoberfest and saying, look, evergreen has been shut down the page of the pages that reference evergreen and be removed can be redirected to a single summary page. Because evergreen is offline is down and won't be brought back. And it's not even use at your own risk. It doesn't exist anymore. Okay. Yeah, so good. All right, so hecktoberfest is fair for that one I think. Good. This eclipse section in the ID configuration page. I think an experienced eclipse user could describe for people how to configure for Jenkins development. No, maybe not. I was like, I think you need someone who is experiencing eclipse and experienced. Right. It could be like it's one of those weird things where it's like maybe it is a hecktoberfest but it's going to have to have. It's not a first issue. And I don't know. I don't know. Does the description, maybe if I look at that and say, I might be interested. Good question. I suspect not because what it's saying is, look, use this wiki page and other places to describe how to configure eclipse ID, but what it warns is the wiki page is badly out of date. And the reality is that means it's out of date with Jenkins and it's out of date with eclipse. And, and those two things. I think Kristen's right. It just won't work to have somebody try to create that from whole cloth. Right. Okay. There's probably some if somebody like that shows up in hecktoberfest, they can always write and say, you know, they can always post and say hey, you know, absolutely. Hey, I'm a, I'm a Jackson Jenkins expert and I happen to love eclipse. Do you mind if I write a page about it. Absolutely. We would love that. Yeah, that would be great. Yeah, but we don't tag it doesn't mean they can't have it. Exactly. We certainly can apply tags after the fact right if someone says hey I want to do this, and they're successful. It's a bigger problem we've had in the past has been people saying I want to do this, and then they don't do anything. So, so I'm, I'm, we're more than happy to tag something hecktoberfest after after they've started on it that would be just fine. Okay, this one. Okay, so I'm not sure what to do with this one because this is really other than warning. I guess we could warn people in the. Okay, so it's this is. We could put in information in this place saying hey, you when you register for an account before if you do not receive an response email, please send email open a an infrared help desk ticket. So, so this one is I think this one is is hacktoberfest and good first issue. Any objections from the two of you. Nope. Okay, so put the text in there should be clearly mentioned. Sorry. See a quote reply. Okay, got it. Now. The documentation on that page on that page should note the risk. An incorrectly entered email address, email address, or an aggressive spam filter filter may prevent the welcome email from arriving. If that happens, open a ticket at just a minute. Open a ticket at help desk here. Okay, got it. And since that only requires GitHub authentication. You can open that ticket even if you're a Jenkins that our account doesn't work. All right so correctly noted as hacktoberfest. Let's keep reading. All right now the cradle thing. This one I see it marked hacktoberfest. Kristen, are you comfortable that somebody using cradle can be told how to do a release. And so I feel as ignorant as the day is long when it comes to do with greater. Okay, so no estimate from either of us great. All right. Okay, more. Sorry, what was that. Sorry, what's the open liberty. Oh, this one is a wiki migration. Oh darn it. Okay, sorry, I missed the tag. I was like, Oh, okay. But as a wiki migration is saying, Hey, there's this thing called the liberty profile about web, what do you call web containers, like Tom cat. And apparently open liberty is a web container. Okay, I was wondering if it would be something easy because it was. But yeah, anyway, I guess it would not be never mind. What about 3650. Here. Oh, this one's a fun one. This one's a fun one. I think this needs to be fixed. Yeah, but it's really a tough one to fix. Okay. Yeah. For me, the problem is this one really needs skills. And when I talked with Damian to portal about it. He thinks it may be that the best thing we can do is completely replace this particular tutorial with use something done using Docker compose to create the multi component thing that we really need for this tutorial. So I'm hesitant to, in fact, I'm unwilling to mark this one as a good first issue because it requires a level of skill that if I picked it up, I think I would spend three or four days working on it before I was confident I'd fixed it. Because it's, it's, we say, we say very simple things here. Hey, it's easy. Just copy one of the examples and paste it into your Jenkins. And I'll tell you that in order to use agent Docker, you have to have a certain set of plugins installed. And you have to have a certain set of permissions on your on what your Jenkins controller is allowed to do with Docker and it's uncommon for people be to be allowed to do that. And this one assumes that you've probably got executors enabled on your controller. And you've already added an agent and of course it never says any of those things. And it's this thing is, is really, really, it needs an awful lot of preconditions before this tutorial can be successful. Is there another issue of this scroll down someplace there's a mention that they go and there are just a zillion Docker containers for Jenkins. And what the difference is. And the issue. Oh, on the issue. Okay, so. Oh, no, I think what he's saying here is a bewildering number of Docker plugins. And that is correct. There are multiple. Each with a different approach to how you do Docker with Jenkins. And therefore, it makes it amplifies this even worse which plugin is it that provides the Docker declarative step. And you have to find that one. Right. So what he says is at least add install the Docker pipeline plugin. My worry is that the Docker pipeline plugin may not be enough. Okay. Oh, no, no way to say this here the user says installing the Docker pipeline plug and fix the problem. Maybe we should mark this as October fest. Yeah, if that's enough and then maybe have them as part of it, you know, clearly test the documentation but if this is all it takes. I think this could be great. Okay, it really is. Well, and if it's not fixed in October fest, we should fix it post taste ourselves later. Good. All right. Nice catch. Thank you. Good question. I don't understand that set of words. Okay, so it's saying as shading that only scalers and literals are supposed to have. Huh, wait a second. First line of sequence entries name doesn't have shading name Jenkins home does. Oh, I see what the concern is. Got it. It is that this thing is shaded in an unexpected way. They were expecting either only only values to be highlighted, or both the name and the value and in this case, we got a name and a value highlighted but then we got a name with no value with a value. And only the values highlighted, and the point is well taken but I have no idea how to fix that, because I think that syntax highlighting from. Well, let's look at it and see just to test it. I think this is syntax highlighting from ASCII doc as ASCII doctor. Three and YAML so this is their their YAML syntax highlighting. So one solution for it would be switch the layout so instead of using name colon we put name and then we indent the value but I'm not sure that's worth the pain. So I would propose this one is not a good first issue. Any disagreement there dispute. Continuing are looking then. Wait a second. Okay. Yeah. Refreshing this page sorry just a minute. Yeah, okay. Good. Okay this one is a is a wiki migration and so I want it. Not to be listed October fest. Actually, we can we can do one more search to find that those mistakes. The author of the issue if it's get JV, then they should in general be listed as gave this one is this one is. So I'm now going to label these all as wiki migration. All right. Okay. We have looked through pages three and four. My assessment is we've covered the whole range of bugs because five and six were reviewed by Europe office hours earlier and we've been through one and two more than once. Everybody okay if we call that done, would you like to have enough good first issues that we're going to have a big October fest. Good point so we should go looking for more maybe we've got 11. We're doing it to come up with things maybe are not on our list. That's that's what mega done last week and I think it was particularly effective. So maybe the technique then as we do some quick looking to see if we can find obvious problems. You want to just look at look at documentation we could put the three of us in parallel we could look at the pages together, looking for things for instance, a common area where we had problems before was in the developer guide. No developer is probably a bad choice for first time contributors isn't it. Yeah. Well depends what we find, well the tutorial of the thing that tutorials like early so it's pretty good. Let's see what did troubleshooting Jenkins that's something that people tend to throw something in, and nobody goes back and reviews. Right. Yeah, it's only got two entries diagnosing errors. And obtaining a thread dump. So it lacks content and we can't make it a good first I should effort to write. What's in the appendix and glossary. So appendix just has the disclaimer please don't put anything here. Okay that's useful. Well it's it's I think it's how we actually want the appendix we don't want it to have anything in it. There's something in the appendix it means we didn't have a fine to have a find a place for it to put it otherwise. So then I would ask them why do we have an appendix but exactly that's a valid question. Remove appendix and good first issue. Yeah, there you go. I'll give you that one I think that's that's a very good idea. New issue. Documentation. The appendix page. Empty and and will remain so empty. Yeah. Okay so an open source project. I mean they're in in proprietary old fashioned proprietary author documentation there's a place for appendices for like reference tables and stuff. And open source you got too many people chiming in I think it's just going to be a disaster. Right. We don't intend for there ever to be to ever put content on that page and agreed that this is a good first issue. Sounds good to me. Good first issue and hack taller for us. All right, continuing our search the glossary glossary is a point of can of conversation and dispute. I'm hesitant to put a new contributor into it because it's about usages and words. They're going to get burned yet. Exactly. Unless there was something are there newer topics and see this page for more for me. See what what I would like to see. I don't like straight glossaries I think they tend to be useless and annoying like that. But, but like for the plug in there was a link I don't know where it's going. Oh, right. So the link is to job. So it's just within that right the links within the glossary are. It might be that what each one should say is for more information about this topic, go here and then take you to a better page, or to a more in depth page agent for instance, could easily say, hey, here's this page all about agents pipeline here's here's a whole section of the document about pipelines. Right. So there would be a bunch of good first issues. Because most of those terms are covered elsewhere in the docs and look through the docs and find what's useful. So now is that is it likely to be a source of significant contention. When someone chooses to link to using Jenkins agents, instead of linking to managing agents managing nodes. So my worry is, is that to the there may be there may be enough contention there to make a poor experience for this first time contributor. Well, on the other hand, they should be able to look. I mean, keep looking just because you found one reference, keep looking. And maybe you know and for, for a lot of these things you may you know that makes sense you've got here's how you use it here's how you manage it or here's how you troubleshoot to take any of those topics and make sure that they flow through to each other. So here would, how do you install core. Downstream. Do we have instructions to how you do the pipeline documentation tell you how you set this up. It should so there's the build step that describes it. Oddly enough, I don't see any really obvious matches for downstream or upstream in the search. So, so could be I mean it's it's not a not a bad idea to say hey should we should we add links from the glossary to other pages for instance, agent for more information refer to managing nodes and refer to using agents using Jenkins agents. Right. And there's a security section on agent security I think isn't there. Ah, good question or access control securing or maybe in an unmerged PR. It could easily be in one of these sections under for instance, access control. No, okay. Yeah, I don't see it at the moment but but it there could be could well be something so the agent listen port for instance is certainly there. Because your suggestion is extend the glossary so that it becomes not just a definition of the term but also links to other useful content related to that term in the in the documentation. If you wanted to bulletproof the thing of course we could make a series of because instead of having one big one you could have, you know, make the agent glossary item link to other docs make the control you know we could and we can hand feed it we could say make it point to here and there, but then writing the then it'd be easier to do the work than to make the ticket. Well but but isn't there isn't that same risk there as we review it because they, they may approach this and say well I don't know where to find things about agents. And they'll then have to do the research to go reading here okay where should I where should I look where should I search. And especially because the agent no terminology is right, but that meant to go and I mean, but it's also I mean it's a good. Well, and you know what else because it is hacktoberfest. If you got some people who are interested in this. And you could two or three could sit down with somebody with one is somebody who knows stuff and go and look through and say, you know, and we could point some things out, because right somewhere there is. And I think I shoved it in someplace a little summary of agent node next, you know, I know where it was it was in the training it was something I tried to save. Yeah, so what's a node. What's an agent. Yep. Yep. I mean, there is a good exercise I mean for when you're a writer you do this periodically is just take a topic and start tracing it through and see are there holes does everything point to each other are their redundancies are there. Things that contradict each other. Yeah. And trying to add stuff to the glossary would put somebody into that which could be good for the project and a great exercise for them. I mean you might end up with only two people who want to do hacktoberfest to a real novices and it'd be irrelevant but if you had a group. I don't know. Let's, let's take it so I've, I'm going to submit. Oh I hadn't finished submitting this one okay so remove the appendix page let's create a new issue that says. Okay so extend glossary page glossary entries with links to documentation sections. I would like this. I don't know. I would like that not to be just one issue but I don't want one for each term or this there's some grouping that would work. Sure. Sure. So let's, let's talk about for instance what if we said agent and node glossary entries they make a logical grouping right. There are there's some others like that so job and build and artifact might be well connected cloud cloud probably connects to logically to agent executor probably connects logically to agent. Yes. What would master. I see that listed to that might actually be an update that we need to generally make. Well, no master in this case tells us hey it's deprecated. So, and that's intentionally good good good good listed as the evil term please don't use it use the correct term. Okay, cool. Even even that one could include a link to. Here's the blog post that describes that it's deprecated. Nice, right. Oh, we, although we don't have the word slave. Interesting. Okay it's our slave has already been removed and I guess we may be at the point where master could even be removed. No, because it. GitHub's trying to move away but master's still there for GitHub slave is in the software. Certainly, both terms are in the software and we'll be there for years to come. Right and but that would be worth mentioning to that, you know, there's a you know we could shut down everything for a year and rewrite all the software to not use them. Yeah, be much more than a year and it would be broken early. I think it's bad that slave is not listed here. And because people in talking still. I mean, one thing that a glossary is useful for is if you're in a conversation and people are throwing out terms and you don't know what they are there a quick memory thing. And if some and people still talk about your slaves. When they talk and I go look and I got nothing. Tell me it's an old evil bad word you shouldn't use it. And here's, you know, and here's a blog post that tells you why. And unfortunately there are some references and software that just. Yeah, I think you've got a good point. So, so that may be a separate topic for discussion. I'm not sure I'm ready to put a, a novice on the, let's add the word slave to it. Yeah, it may need a conversation with Daniel and others may need some digging into the get history. Yeah, right. What about when it was deleted. What about making the issue like this would be extend agent and related entries and then for the touch just for the title and then have the list inside the description. Good. Yes, I like that. Okay, so now the challenge here is we need destinations for them and I'm not sure there is one for cloud agent glossary entry should connect should link to using nodes and using Jenkins agents. Right. Security. Additionally. Oh, you know what because there's there is that. Agent controller filter. That's it there was a section on that and then that, I think in that PR that subsumed because it's no longer something you can set. So it's just something that's there. See, and I think the agent, the agent to controller access control is no longer mentioned anywhere in the documentation. I think Daniel deleted it completely. Oh, because it's it's no longer I thought it was no longer a facility right you no longer get the option you simply can right but if you want to know what does what what are the ways that Jenkins could potentially be breached and what what do we do to protect that that is an important protection that is there you just can't turn it off. And I'm hesitant to put that level of detail in a link in the glossary right for me the glossary is is much more high level but these two managed these two pages make sense. I agree but I think that I'm saying is I think that information is someplace. Let's talk about how the agent is kept secure. Oh, there's another one. ephemeral agents are safer there's also the issue of if you use an agent over and over again it could get tainted by malware and affect another build. There are there are security issues related to agent and they are discussed someplace. Okay, let's see so ephemeral agent defining execution environments. Agents for use in the pipeline. Yes. Okay, good. So that's a tour of agents that makes sense. So that should be included. Good. And, and defining execution environments. And this exercise is showing that we have to give those destination lists, because I don't see how a new contributor can do this successfully but I think it could be quite successful if we do it. Right, and have them do the do create the text. Yeah. Okay, so. Now cloud I don't know if we've got really good documentation. What about installing because there there's some how you install it. I don't know. Oh, well, that's a good point there are. Yeah, so for me cloud is cloud in the context of the glossary was talking about agents in the cloud. Right dynamic agent provisioning through Azure and easy to mention of Google. That's nice. Well, it could mention Google it could mention digital ocean it could mention. Hetzner. There are there are several clouds now that the Oracle cloud. So, so that's a maybe that's a different one for clouds. Some place of all the cloud there must be a list someplace. Well, the glossary. Well, it's a good point isn't there. Kristen this is when we look to you for isn't there an extension that is a cloud extension some one or more extension points that are cloud cloud related right and this extensions index. So let's look at maybe we look at EC to. Okay, here's the Amazon EC to plug in. It has no. Okay, I don't see anything there. I was like, it could also be that we could ask people to improve some of these. Yeah, what I was looking for more was cloud so Adobe cloud. Actually Adobe cloud manager would be another one that let's see what extension points it has. Nope. Okay, so, so maybe cloud providers are not done through extension points, because having. Okay, so for example, open stack. Again, this doesn't so it's so I think I'm just looking in the wrong place. What. Well, no way to sec. Yeah. Alright, so it's a no easy way to, I guess I know the easy way to find cloud implementations cloud. Right. So here we've got all the cloud beast gets stuff. Yeah, interesting. Okay, here's open stack cloud oracle cloud infrastructure compute Google cloud build EC to cloud access access oracle cloud. So, so there definitely are cloud plugins but non trivial work to find them all because I EC to isn't even listed here right. Maybe it's not the word cloud. So, Oh, well, that's not even nine years ago. Oh no. Well and that's and that's definitely not the, no, not the EC to plug in, right. There it is. Okay, so, well, alright, back to our. Okay, we've got cloud. I'm so cloud. Entry should lay or how about this the cloud entry should link to more plugins for it shouldn't it should including. All right oracle cloud. Adobe cloud manager. I think Hetzner. Let's see who else so Google cloud. Azure. Azure's already in there. But that's included Azure. And fingers. See, let's see three may Oh, so we've got Azure Google cloud. AWS EC to or AWS. And I thought Hetzner had a plugin. Oh, digital ocean, digital ocean right. Shame on me. And now I really do want to check to see if Hetzner has one I thought they did this is a German provide yes Hetzner cloud okay. That way people know there are lots of cloud implementations. Right. Fair enough. Good first issue. And hacktoberfest. Oh, now I need to link to the glossary. Okay the way it's phrased. All right, I'm taking your silence as as a scent as yes agreement. Yes. Okay. All right so that was that's one. In addition to the glossary. Are there others that are as promising for instance build and what else might we link build and job. No. Yeah, so okay. How about how about the pipeline related items should stage step stage and step. Some place that's more useful more. Right. Now, now where would it go is is now the question. Okay, so if we look at pipeline here. We could lead them to getting started. We could lead them to using a Jenkins file, which talks about concepts build test etc. It's open to suggestions there. Oh steps should reference the steps reference. Oh, that's fair. Right. Although isn't that a little terrifying. Yeah, yeah, you're right. That's good point. It should. Okay. If I'm a sophisticated user even new to Jenkins. And I want to know about steps I want to know what steps are available. Right. Okay. I will extend glossary entry. The step glossary entry to link or no link from the step glossary entry to various to pipeline to helpful pipeline pages. Okay, link from the step glossary page glossary entry to multiple to several pipeline pages. And now the examples getting started. And would you be okay if using a Jenkins file we're in there. And we have run up against my time limit. Oh, sorry to make the two of you endure me typing any other topics we need to go over before we, before we call it the end of our session. You're such a nice person I would love to just throw some big topic at you that we have to discuss before we stop and see how you react. Right. When I tell you Meg, please go pound sand or something. What we're going to do is put that on the agenda for the next meeting and exactly massive defective shield goes up and thank you for asking that was an excellent question about that next time. Yeah, I had my opportunity at the beginning to add items so. All right, let's go. This would be good. If we have any spare cycles. We still need some more first. And my experience last week was almost any doc that I opened up if I glance through it I could find problems. Right, right. And certainly, there are things to improve in all sorts of places right absolutely. I almost, almost like you could just say, read this doc and see if it needs editing updating etc. Oh, Kubernetes, there's no Kubernetes entry in the glossary. Oh, interesting. Okay, yeah. And we certainly use. We certainly use the word Kubernetes and lots of places. And install, I think we even have a section for installing Kubernetes. Right. Yeah, there's a subsection of for install for Kubernetes. Okay, so. Oh, it's a long meeting one to we. Oh yeah, when that was a Google season of docs that was our first our Google season of docs project where Xenob created the installing guide for Kubernetes. Kubernetes entry entry to the glossary. We have an entire section installation section. With two or three different ways to install on Kubernetes. But don't have a glossary entry entry for Kubernetes, add a glossary entry entry that describes Kubernetes. I'm not going to insert any cynical comments here. And, and link to the installing page. Okay, now on that theme should be should the glossary entry that says Linux. Oh, there isn't one. Okay. Or windows right. Okay, so. All right. Now we're five minutes into your time. Yeah, so now I'm really going to disconnect. Thank you both. Thank you. Thank you. Next time, same place. Next week, same time, same place. Okay. Excel. Bye.