 Welcome everyone. This is Jenkins documentation office hours. It's the seventh of October. Thanks for being here topics on my list action items. The change log and the big one is really hecktoberfest. Any other topics we need to be sure we put on the list. A short topic from my side is discussion on the GSOG blog that is pending from the plug in health scoring system. Okay, good. All right. Any other topics. Okay, so I'm going to put that one top of the list then dirage because that was discussed in advocacy and outreach earlier today as well, or about 12 hours ago. So action items. I've still got the action item to archive the docs mailing list that will need to wait until November because of the second item which is for the next three weeks of office hours I'll be out of the office. So that the, but see the 13th, the 20th and the 27th, the 27th I will just have arrived back in country and I will be too, too weary to be able to see straight in order to do office hours. So next three weeks no office hours I'll send the notice I've deleted office hours from the calendar. So that the Jenkins calendar is correct. Exactly. All right, so dirage your question on the GSOG blog post. So shall we look at that. Okay, okay, so here's the blog post. Yes. And do you want to look at it in context as a deployment. This. Okay. I really think show environments for you to plan. That's not helpful. Are you ready for us to review it first question to you dirage I assume you are. Yes, I am. But the question is, we still need to add the links to the slide and the recording that's remaining. Correct, because I watched the recording as he said outreach I watched it last night, and I saw that you had discussions on that and this is something that you want to publish by the end of this week or early next week early next week. So what what Kevin and I did earlier today was updated the publication date to be October 10. So it'll be published the plan is to publish this and the other blog posts on the 10th of October. Now what we did recommend is we would want Oh, and I've got to make a note. This image has the wrong aspect ratio for use as a an open graph image. Open graph images need to have a very specific aspect ratio for most success. And this one is too, too wide and not tall enough. I've got the action item to give you to post the pointer to that and I'll include it. Hang on, we can do that right away actually I had that action item from Docs office hours Europe and I didn't get it done let me find my comments, and I'll put them there. Okay, and the one where here where there was. Okay, so. So for your benefit, do Raj I'm going to put these comments in so that you know, oh this is why Mark wants to have the have the aspect ratio changed on that image. All right, so let me put a note here. And the image is this one. Now I don't know how to comment on an image. Okay, so I'm just going to put it as a comment in the text just a moment where we say. Okay, so the image needs different dimensions. And this is where we learned, we learned by sort of hard experience. When images are reduced. Okay, when images, your problem I don't know if it was below an image. Or are have the wrong aspect ratio. So the wrong height ratio fights the width. They are displayed incorrectly so it says hey don't we want to be sure that we are greater than 200 pixels in each dimension, and the preferred dimension is 1200 by 630. And if I remember right this one is much wider than the ratio between 1200 and 630. That's why Jenkins looks taller and thinner than normal too. That I don't know. So, I, yeah that is interesting he is taller there isn't he. So one, one technique I use dirage to get images that are the right dimensions is I go to the Jenkins social media covers slide deck. So you could go here as well. So let's see so open graph image needs to have its size corrected. See the social media slide deck. So in the social media slide deck. What's typically done is will take. See what have we got for do we have 2022 something already. I'm good. Okay, oops, no. So here they are. No, none of those. Okay, so season summer G sock, we could grab, you can create your own slide, etc. But what I'll typically do is do a file download. So choose the slide get it to be the way I look and then do a download a PNG. PNG then has the correct dimensions. So that for instance is now a correct dimension picture. So you downloaded from this slide. Yeah, so file, download PNG image, right. So you create a slide in Google, Google slides, and then download a PNG of that slide and that's the image. Wow, that's a very nice trick. Okay, great. So really tangential question. I'm Angelique's female Jenkins are we ever going to use that for anything or was that just a good joke. No, it's actually on the artwork page. But we never use it. Let's see. Well, I've not seen it. That's a good point. Yeah, so let's, that's a good one we ought to consider. I think we have used it. Okay, let's let's do a search. How do I do that now Google image search. Image search images here we go. Okay, and now what we need to do is drag, you know, not that one this one. We need to drag this image because I'm pretty sure we've used it in quite an elf that didn't help. Drag an image here or upload the file, okay, paste the this because I'm pretty sure we have used it in. Okay, so here are image searches. Oh, yeah. Oh, well, but that one is. Yeah, okay, so we used it in Hector profess 2021. Where when it was contributed. And you're right, we certainly should use it elsewhere. Just so. So where can we use it. When do we decide how do we decide. I think we can put it well. So for instance, it would be a great one to contribute to put again on G so on the, on the Hector profess 2022 list because we've had a number of of. We've actually had a member of Duchess France be one of the contributors. So Kayla, all Peter is a member of Duchess France and she's contributed to Jenkins core. So if we look at Jenkins core Kayla's Kayla's pull request. Kayla. Oh dear. Now that may not help me how would I find that she did a she did a very nice fix and now where is it. Maybe it's already merged. Oh, I apologize. I'm not finding it out. There it is. Oh, right. So what she did was did a fixed to table layout so that instead of the old, old style table it's got the new style and here's her work and Kayla's a member of the sec. Based in Minneapolis I must be wrong. I'll have to do some more looking. I don't have any questions. Where else do we use it. I'm open to other suggestions. Absolutely. We should periodically put it on the main Jenkins IO page. Oh, that would be cool. Rotate through right. Be nice if we had more than one. Yeah. Okay, tangent done. Right. So back to back to your GSOC post. Deraj, did you get all your questions answered or are there other questions. Yes, one small note. So I'll be adding the link to the slides and the recording in the end or somewhere right. Right. What is this. So you've already added that. No you added this this is a this is for phase one. All right, this is midterm status. Oh, and so in phase two, you'll just do the same thing, add that video in the phase two section. And in the end every section like, check out these slides. Here's the link. Right. I also wanted to add one more thing near that link to Google slides link is that I wanted to thank Jake, because he helped me very, very much in preparation of the presentation. So I wanted to make sure that I give the credits. So can I do that. Yes, absolutely. Yeah, it's your, your blog post to write you are welcome to do that. Absolutely. So you've, you can work on that. It will be merged. I'm at the point where it will be merged no matter what on Monday, because John Mark felt like hey it's already good enough so you've gotten to Monday to make corrections. It would be good if you could be the one who presses the button that marks it ready for review. So that others know Oh, do you Raj thinks he's done and ready to publish. Complete all this pending task today and press that button. Yes. So this was all for this topic. Okay well and congratulations on completing. That's wonderful. We're thrilled. Thank you so much. And is the content right because I kept it very brief. And is this what you're expecting in this kind of blog. This, this worked great for me. I thought this was this couple, particularly with your presentation. And oh, hey, I got to show you. So you may remember that plug in health previously had only two probes now it has five. Yes, the UI looks better. Yep. So, and, and there are plans for how to evolve at the next step so thank you for your thank you for your work. Thank you so much. It's just the mentors who helped me reaches a big thanks to them. Now, I guess, let's see if this page is not linked from your from your blog post you probably ought to link to it. I think it's a point of pride that hey it's deployed and it's already started working so. That's a very good point. Because it's like the result. Yes, exactly. So I'll add this in the blog for sure. Good. Okay. Anything else on on plug in health scoring and your blog post. No, I think this is it. And I'll work on the pending items by myself. All right, so then next topic was the 2.361.2 change log an upgrade guide it's released. And we detected a mistake in the to the 2.361.1 upgrade guide or change log. There was an entry in the upgrade guide that had no corresponding change log entry. That's that's upside down usually if something's big enough to be in the upgrade guide because we need paragraphs of text, it absolutely should be in the upgrade in the change log. So, that's fixed. So, is this related to that comment someone made on talks to the channel where they said that I upgraded to LTS and some, it was missing some entry in the LTS change log. That is correct. Yes. So what had happened was, there was a the minimum remoting version has been increased. And they were running in a very old remoting version and were locked out their agents couldn't connect. Well, the answer is you shouldn't run really old remoting versions running a current remoting version is much better. Oh, so when they have created is that when it happened. It is that's correct. So, next topic then for me is the big one and I propose we give it at least five or 10 minutes. First, thanks very much Meg for your work with the rest of us here in office hours for the work on October Fest, because those good first issues already were being chosen and worked and resolved beginning October one Saturday. So we've had great progress thanks to good first issues. You see a number of them that have been closed in the last few days. So PowerShell Python app pipeline page groovy hook scripts plugin page that was out of date agent glossary entries. All those things are thanks to having been identified listed as good first issues. They've been resolved and merged. And several of these things actually have relatively sophisticated things hiding behind them. This one, for instance, had some had some interesting things going on that. Oh, no, I take it back that was an easy one. There was, there was one that was especially complicated. And it was, Oh, wow, where did that come from. Here's as a good one on the open with work pending. If we look in the good first issues that are pending. What you'll see is for instance, someone took on updating the Kubernetes install guide. Whoa, and, and yeah you talk about there's a big deal. I mean that is an amazingly big deal. In fact I need to mark this one as Hacktoberfest accepted we're not done reviewing it yet. So it's not ready to merge but it's absolutely Hacktoberfest worthy. Yeah. Not a good first issue. Oh, no, no, and, and, and significant work and of course it needs good verification to be sure. Hey does this accurately reflect what we need it to, but very, very good. Yeah, that too. And it's, I guess I'm getting old. We're starting to see over dinitrace to the junior people coming out of school, no Kubernetes. Right. You know, kind of, I kind of know Kubernetes a little bit but these people are coming out with massive Kubernetes knowledge. And they're looking for stuff to do with Kubernetes, which also makes me think that's something else though for that I don't know that's the first issue. But the information that we've got about nodes and agents. As I recall the last time we looked at it. I mean there's a little bit that you can do this with Kubernetes but there's not a lot of details and sophistication about it. I don't know if that's something else if that's a Hacktoberfest project or I just thought of that I haven't looked at it. Yeah, good, good question and I don't, I don't, I don't fundamentally have an answer for it. But we could, I will try to get to the last couple of weeks get crazy. I will try to go and look at some more stuff. We need more good first issues right. We do and that's, that was the I was, I truly was fully expecting that our work on trying to identify good first issues was going to be largely wasted because people would say oh no that's not what I want to do. Like I said I was completely wrong. It was very good. It was very well worth the time invested, and the things that were discovered. I'm not sure why I'm not seeing it here but there was a particular one around a tutorial revision that had all sorts of surprises and ultimately it didn't end up being a very large change. But actually I've got to show it to you because there was a change in a tutorial where we got two new Jenkins logos, Turkish Jenkins and nerd Jenkins. Oh, right. So, let's see isn't this one. No, no, it was this one address reported issues with the Hello World tutorial. Okay, and so what happened here was this took to pull request to get it resolved, and the set of changes was ultimately relatively small, but crucial to the behavior of the of the tutorial. So let me show you what the tutorial looks like it's. So this is the top tutorial guided tour. And I went through this one says okay download the jar run it. And then in this next page we had failed to tell them this first step. You must install the doctor pipeline plugin. And if they fail to do that, then the tutorial fails. Right. And so that that part and then it gets even better. And by the scripted examples had this comment in them requires the doctor pipeline plugin, but the scripted examples are by default hidden. So we said hey, let's copy this same comment in hopes that if they skipped the first step. Right and hit a failure, they would see this comment and say, Oh, maybe I'm missing something and that's why it's failing. Right. Yeah, so so and again it was, it was what you'd think was oh that's such a simple thing. No no to get it right it was two iterations and multiple people looking at it and realizing Oh, oh here's this flaw and this problem we need to fix. And of course, one of the contributors included this video from Darren. So, so again, exactly it's like oh yeah you know what, I don't have to go to additional resources. But if I want to, here's a video that talks about how to do it. Nice. So yeah, and, and special thanks to Hacktoberfest it's done a great job of helping that. Right. So much for a hello. Right, right exactly well gee hello world should be pretty easy except it's not as easy as all that and, and in this case it's doing something really interesting it's saying hey, what if you want to run a specific oh and by the way we upgraded all of the tool versions here to current modern versions, so that we don't look like we're running ancient stuff. So every one of these versions is now the recent release. And it looks very it looks much more believable now. Right. Nice. So, so really Hacktoberfest has has already shown positive things for for the project thanks very much Meg for your work on on good first issues. A long time ago, the plugin stock or the developers guide or something did not have the same rendering as the user guide. I remember you couldn't. I think you couldn't x ref into a subsection. We had a PR to make that work the same did that PR ever get done, or could that be a hot it, it didn't get done it was identified as Hacktoberfest and someone has actually said, I want to work on it. Oh yeah. Now I was very skeptical of it and I'm, I'm still a little skeptical of it but the person who's offered to work on it is reasonably skilled and therefore I think has a good chance of it actually succeeded succeeding. I was let's see where did I put it it was. I don't remember where it even is, because I think we flagged at Hacktoberfest but not. Good first issue. Right. And this one use same navigation for dev docs as for user handbook. Yeah. And oh yes right. And this is one of our one of our Google Summer of Code organization admins. Chris Stern was the release lead for Jenkins 2.361.1 and 2.361.2. So Chris is experienced and said hey yeah I'm interested in working on this so I gave him a brief outline. Hey here's what you need to consider and here's, here's what the good thing looks like and here's what the bad thing looks like, and his answer was oh good. He'll start work on it. So yeah the, and the problem to remind the problem is that it looks like this right so here's the user handbook with nice expanding contracting and highlighting of which section I'm on. It just looks good, and it feels good it helps the reader as they navigate they understand where they are and what's next. When you do the same thing with developer handbook. This top level page is not a bad thing. But then if I click how to guides, I get dropped into something that's, well where am I, you know I don't know quite where I am. And, and it, it actually goes gets worse from there so oh me what if what if I do improve a plug in. Okay I still don't okay this one highlights where I am but the other one didn't all sorts of inconsistencies like that. So it's not for someone who's like, it's not like a good first issue right that's what you're saying. Yeah, this is definitely not a good first issue this, this thing that Chris Stern has picked up is is well worthy of Chris's skills, because I expect it will be challenging to understand how the site is generated with the awestruck to generator, what the ruby code does that does the generation, what's different between the user handbook and the developer documentation pages, and what will it take. It probably will be a relatively small change in terms of number of lines, but a large change in terms of understanding how to unify the two things. Yes, exactly. And, and, again, very, very grateful that Chris is interested in it and willing to work on it. Now I apologize, I don't go ahead, do Raj. Yes, thanks. So I have a question for Meg. So how do you this, like, how do you decide the, or how do you find the good first issues so that I can use your strategy and try to find some. Do you want me to tell you all my, I just started opening stuff up and reading. And, and it's amazing how many pages if you open them up and read them you say, ooh, ouch. I especially looked for sort of older basic topics because the stuff that's been done lately I think has been in general higher quality than some of the old stuff. I went back and looked for things that didn't match. Or, or I started looking, I discovered, like, I forget a couple of them. There's like the same topic in four different places. And I don't, you know, and I don't know that they're all matching etc. sort of like one of those whoever was writing just decided to say it again. And one I wondered about is doing that with some of the plugin guides to is just open them up. I mean I remember when I was looking at them every once in a while I'd look at something and go and kind of go, ooh, ouch. I mean it wasn't so terrible that you just had to stop everything but Well and certainly there are well I guess one one valid point is or one one area of that is, there are still approximately 900 plugins that need docs converted from wiki to get hub. But we intentionally did not put that as a hacktoberfest topic, because the usual problem there is not the conversion, it's getting a maintainer to merge the change and release it. Right. Exactly. So it takes time, so it ends up not being a hacktoberfest contribution. Right, we did we don't want someone to spend the energy to create it well, and, and the poster child for me is this one. Right, I'll show it again just because it's, it's a painful one so if I look at docs table. Plug in migration progress. Here we go and if we look for Ansible. So Ansible is has 20,000 installation so it's the Ansible plugin is a popular plugin 20,000 means it's somewhere between 5 and 10% of the installed base hasn't installed. And the pull request has been open since September of 2021. So it's it's now 15 months old. Yeah. Let's see who is the Emilio Escobar or, and then it's, I don't remember who the others are so it's just not getting any JC Searle was the original author and it's it's just not gotten any any attention. Yeah. That's kind of bad. And the hint there is okay it's also not been released very recently. The last release was in 2020. Yes. Is that what's the current release of Ansible I mean is it up to date with the current Ansible releases. And that there's there's not been a lot of bug reports on it. So, so that's a good one to check but I can show you I think that in terms of bug reports. There haven't been a bunch if we look at open issues against the Ansible plugin. It's only got 46 issues and in terms of recent issues. There it's not a high volume of recent issues. But still makes it mean do we have here sort of an orphan that nobody knows they're living alone in an abandoned building with no adults. Certainly it is it shows every every attribute of being an orphan plugin. And it just needs someone to adopt it. But in order to get someone to adopt it we need, we need people who are willing to adopt. Right. And that's why we have the tutorial on how to improve a plugin. Can we can we make a October fest to review and adopt Ansible. No, that probably doesn't work. Yes, see, adopt a plugin feels much bigger than a hacktoberfest topic. The idea with the with the improve a plugin tutorial was get people started towards adoption so that they're comfortable and confident. Hopefully by the time they've completed for pull requests for a hacktoberfest they realize oh this isn't that bad I could adopt this plugin. Right. So what is it for for PRs to get a t-shirt or something like that. Exactly the threshold this year is for PRs to get a t-shirt. It is a category of if you do. I mean, actually, I must be sort of a wiseacre here but adopt a plugin and do it well, and that gets you that counts as for PRs. Oh, see, adopt a plugin and do it well will will require more than four PRs ultimately. Right. The tutorial shows us that right the tutorial has many more than four steps and as preparation for DevOps world, we took a set of 25 plugins and ran the steps through about 15 or 20 of them. Absolutely, every one of them had at least three or four items on this checklist that needed to be done. So you look at this list and you say wow really three or four pretty much of every every one of the 20 plus plugins we we chose. Yeah. Okay, so adopt a plugin do it right get three t-shirts I don't know. Right, exactly. But just I mean, adopting a plugin is on a different. I mean, maybe we could make do we have a lot of orphan plugins out there right. We have we have over 100 that are up for adoption. We have a special October fest category of adopting a plugin to encourage that you somebody comes in for October fest because it looks like you're getting some sophisticated people. And did you know maybe make a list of some that I mean those that have got, you know, 10 installations the last one done five years ago who cares. We got a list of like 10 or 15 high priority plugins that need to be adopted. Yeah, and certainly see here's the list right you. You look at this list and plugins plugins with 170,000 installations like Java doc or local resources are great candidates to be adopted right now they're a little bit. That's kind of the fear part where you say wow 170,000 installations if that's for users per installation, I'm almost at a million users. Right, I'm at least I'm well over half a million users for this plugin I got to be sure that I don't don't hurt it hurt somebody with it. Right. But you're talking about humble nerds. Like, wow, almost a million users. That's going to make a great posting on social media look what I did. Right. And, and that's a valid point right if I adopt. Yes, if I adopt the Apache HTTP components plugin, I am serving 290,000 controllers. Yeah, absolutely. Yeah, I mean we could almost if you if we get a few of them we can almost make a special t shirt it could be a special subset of October fast. But um, um, I'm a dear as you're asking, how good are you with kubernetes. Hmm. So, yes, I'm bigger, but I do have knowledge of it I completed the tutorial on open shift by that. And I do have knowledge on it. Okay, my, and I'm not sure because I don't so I'm just talking off but off the top of my head see what you think of this. My feeling is like we have the section on how you install kubernetes and I and somebody you've got somebody who's working on general stuff. But my eye is that a lot of the basic Jenkins topics that are covered. There's a kubernetes aspect like when you're talking about nodes and agents. You know, where, you know, what's what's the ramification of two nodes in the same namespace versus in different namespaces and, you know, it's just little things like that and I'm thinking that could make a lot of. I don't know if they're good first issues or not, but there's certainly hacktoberfest. You know, to go in and update this. A lot of, I don't know about mark God proxy stuff and plugins. Like if I install will find solid kubernetes or a plugin on a kubernetes environment. That has five namespaces. Do I have to install that on every on each namespace or is it good enough to put it on one if it's all one Jenkins instance. Nothing nothing special actually ugly and right outbound traffic and things generally are okay. Yeah, can I can I for performance reasons are there some of these that it would make sense to you know, there's just there's a lot of places where just a sentence that says, I think changes on kubernetes put it wherever you want to do whatever you want to with it, which is still knowledge because I'm looking at something in there I'm like well gee I wonder if this is different for kubernetes. But take somebody with more knowledge and me to go through and come up with really valid things there. Yeah, and see that I think is a good topic to put into. But really that's where what we I think what we need for that kind of knowledge transfer is we need kubernetes administrators who run Jenkins to tell us so people like Damian to portal, like every the mirror, like Stefan Merrill, all three of them run Jenkins on kubernetes for the Jenkins project. Sam Gleska, who I'm pretty sure runs Jenkins on kubernetes and others like him, who are expert administrators, and know the barriers the strengths and the weaknesses you know hey here's here the network routing problems that occur, but those things I think really do require experts. And there's my understanding, which may be wrong, is that there's another class there's people that are running jake, not running Jenkins on kubernetes, but are using kubernetes for agents. Interesting so they're running Jenkins outside of a kubernetes cluster but they're not positive I think I got that from one of our external training groups, a couple years ago and it may have ceased to be true also. Interesting that they were, you know, that they were fine with their controller and everything but all the dynamism was with their agents and notes. And I, you know, you'd have to check with somebody with more knowledge but it might have been something that was just happening in the early stages of adopting kubernetes and that we've moved on. But that that was, you know, that they had it already running they just needed more agents and nodes and they needed more flexibility and how many agents and nodes and they were just throwing up a kubernetes cluster and throwing them up there. I don't know. Yeah, so so that that for me is a running topic. And I'm still in the crawling phase. I've got a crew. So I, I'm right now, I think our first step is get this pull request, these pull requests that are related to kubernetes reviewed and merged so that, and there are plenty of things hiding in these two of, oh that needs work and that needs work, etc. The other thing that was dear I was asking was just reading through some of the docs on general topics and think about, are there kubernetes questions related to this that are not answered. I see what you're saying. And that, and then that is an issue of, you know, discuss agents and nodes on kubernetes and the agents and node section, or one of them I think there's a multiple sections on agents and nodes I think I made that I'm just trying to think of place places to look and read and some you know some of what you read you're going to go yeah that reads pretty well. And some of it you may read and say gee I wonder about this and I wonder about that we don't have to answer it. That just becomes an issue of is there something here. Since we seem to be seeing a lot of a lot of people coming in who knew no kubernetes better than they know anything else. Okay. So, basically going through the guides and trying to see whether it's human friendly or not. And try to see that there are helpful documentation around kubernetes doms or not. Well, yeah. So, there's certainly things that a reader could could identify if you've got some kubernetes experience say, Hey, what does this make sense or oh no that's that's flawed etc so absolutely good things to read. Also might be some maintenance there's probably. And I don't I don't know for sure what's in the kubernetes it might be kubernetes admin, but if I'm running Jenkins on kubernetes what information can I get out of cube control that I that's relevant to me. That's not in other words, all most of our docs here were written by people who were Jenkins people who were learning to get it up on kubernetes. Somebody who's really the kubernetes sort of end of things and really want to use, you know, use kubernetes to the greatest effect. I mean are there performance advantages to splitting stuff between namespaces or separate clusters and all of this sort of stuff. Right. Nice. But yeah, here it's basically and I went looking. I went looking at a lot of like the older stuff the basic stuff because that's why I think there's more problems that got written once. And it's written nobody's looked at it for a while unless something changed in that area. So when you look at the old documentation of you mentioned that you find them lagging behind. So by lagging behind you. What are the criteria that you mean, do you mean phrasing changes. That other than just the information was a little shallow. You know, it's, you do this and this happens and life is good and you know a lot of places where there's nothing about what could go wrong how do you chase it. What does this fact all that sort of gnarly stuff. Sure. It's really fun because you go reading you don't have to fix anything you just look and say gee that looks suspicious issue. Exactly. Yeah. And you might find there used to be more bad writing it seems to me that a lot of just the pure bad writing and formatting issues. But there, there were a couple I found a couple, you know, a few bullet lists where half of the items were Nick capped and half weren't and some were bold and some weren't and few inconsistencies like then those are to me. My idea of a good first issue is something that's brainless, so I can get used to the tools. And, you know, so. Yes, exactly. I'll keep that in mind. The older tutorial documentation and read through them. And you could look at some of the, and the, like some of the plugins that have been around for a long time but pretty stable that do have owners do have known owners. I don't know, Mark, we didn't get you out of here early. Well, but I think, I think we're set. Thanks very much for your answers make any other topics we need to cover before I can end for the day. Nope, you don't need a couple of warm milk to get to sleep right. I am ready for bed. A very short topic. Sorry, Mark. Go ahead. I get DM on Gator from contributors who want to contribute in that improve a plugin tutorial right. So they asked me what plugin should they choose. And my intention before answering that question is, I should be suggesting them the plugins which maintainers are ready to, you know, review the PRs. So, so do we need a section for this in the plugin tutorial because, or is there any section in that already I need to go through that because when you're reading the tutorial, they would need to pick a plugin to improve. Correct. And there are some guidelines that you they need to follow before deciding the plugin or else they're, it would be like answer the plugin. So what I did was I provided a list of plugins that have already already have people who are really willing to review pull requests as part of Google summer part of Hectober fast. I'm trying to find the list now because I copied and pasted the list into a getter post and you are welcome to just reuse it. Where did I put it. What about What about the step documentation that we were working on with. She codes Africa. Is there anything there that we've got somebody who will review that's doable that hasn't been done yet. There really, there really isn't the problem there is, it's a, it's usually a beyond beyond a good first issue level of skill required. Because we have you have to find the place in the code to, to add the content then you need to learn enough to, to actually add the content and between those two things that's, that's a larger barrier than, then most people can overcome. Where is that list. I know I generated a list. I got it. Oh, you got it. Good. Okay, great. So, yes, that was the question so I'll refer that list. And we do not need this in the tutorial right because it might seem. No, well I'm hesitant to put it in the in the tutorial because it's so variable. I don't quite know how to do it to make it make it such a thing but here let's yeah so I assume you're going to paste the full list. I'll switch my account. Oh just just paste it as a proposal. I'll happily, happily you don't have to change account just paste it as whoever you are. And there we go. Okay, good. That was that was exactly it great. Are these clickable? They will be soon. There. Now they're clickable. And, and these are just, these are actually plugins that for your info. These are DevOps world contributing to open source. Candidate plugins that we candidate plugins up for adoption. So what we did is John Mark Mason Bruno Baratshten and I adopted about 25 plugins and this is that most of that list of adopted plugins that we are we intend to drop and not have them adopted anymore once we've finished this exercise so we need someone else to adopt them. But you're foster parents you're not exactly we are fostering. I'm not sure the word fostering would go real well in our international community but yes. Foster parenting that's very good. So is there a more proper term internet I mean there, there are always people who care for children whose parents can't care for them temporarily. Maybe she does. No. I think mega is alluding to, she's using an analogy for a longer term case so let's for example say that a child, a child has both parents die in an accident. And then someone needs to take care of them in in the US at least there are times when those children will be offered as they'll be adopted by another family. And sometimes in the transition period before they are adopted by another family they're placed with a foster parent family that's known to be temporary non permanent adoption. Oh, that's interesting. Yeah, so don't don't worry about it. Alright, so we've we've got a list and that list is usable and pull requests are already actually I'll show you one that was just processed today. So here's this one. And we see a brand new contributor submitted a pull request, I reviewed it and it's been merged. Thanks to Pam. That's awesome. Alright, thanks for the work on that parameterized trigger plugin thanks for that because my peers were open for too long and I did not work on the comments. So thank you for your help there. That's one of the sort of the joys and the surprises right is sometimes there have been long standing pull requests that just the mere act of clearing out the pull request is a real positive for the plugin. Yes, exactly. Alright, thanks everybody recording everybody have a wonderful tour and we'll talk to you in November. Enjoy.