 Okay, welcome to the Jenkins documentation office hours. It's the 15th of March. Great to be here. So topics on my list she code Africa contribute on want to give the latest report there on how the details are going and do some a little more detailed discussion of the concepts and why. So, got some things there and then Google season of docs application. And there we need some further discussion as well and look at the pages and see, hey, how do we fit. What's the timeline, etc. So both those things need more more discussion so make I think what I propose is let's not spend more than about at most 30 minutes on the first thing because I want to spend time on the second. Are there other things that you'd like to be sure we get on the agenda. No. Okay, these two are great. All right, so then let's let's take a look at at what we've got now for she code Africa and and what what's happening so the project application has been submitted. So this is proposing that the Jenkins project would be a mentoring organization. And as a mentoring organization what we're committed to in terms of what I listed was three people to mentor up to three people on one project. What I wanted to do was, I want a single project that they put up to three people working the project they are independent subtests within the project. And then the three mentors are Kristen Whetstone. Meg, you and me. I happily take other mentors as well but we I got commitments from those three and felt confident so I listed them in the in the application. Roughly how much time is this app to take from me. I think we'll take not more than one hour twice a week. I can slide that in. I don't think Tammy is yet real enthusiastic about the open source stuff. I'm waiting under the radar here and I for a couple hours a week I can slide under the radar. Right and that's, and given that we're what we're doing is we're offering them to mentoring sessions. Two mentoring sessions and potentially up to four, it may be that your time demand will be even less, because it will depend on the candidates and what their schedules allow I know that with Zenab for instance, our mentoring had to be in the big window of time there immediately after her working day and so it was about 10am your time which is outside your working hours right so it's. So I can't promise that you will be doing anything other than remote mentoring asynchronously. I'm not. I mean I don't have the product knowledge that they probably need what I can do is ping their pros. Well, not only ping their pros you can also, you can also guide them to documents about. Hey, this is how this is how the product works here look at this training look at this material. So there are things that are familiar to you that will be unfamiliar to them. Yes, right. So, but, but time with you I don't know Kristen but time with you obviously is much more valuable than time with me at last. Yeah, so so and that's, we've got sponsoring organizations so sponsoring organizations pay a fee, and we've got confirmation that the continuous delivery foundation has already subscribed and sent the funds. And we're hopeful that cloud bees will choose to do the same and I've the question has been asked to Broadcom and I launched the question also to IBM. So I'm hopeful that one of those may may contribute as well. What if all of them did that would be splendid. It would be it really would. I mean it's it's chicken feed for these cloud for these companies. Absolutely. That's that's part of it right is is a sponsorship of $5,000 is a lot from my personal budget but for a corporation. That's probably not a lot. No, that's probably a lunch. Okay. Yeah, so. So the skills required topic what I did was I put in there that they need to be able to compile Java. They don't actually need to be able to code Java they just need to be able to compile it. Okay. And so it's what I call rudimentary Java experience. Okay, and some HTML because they'll be writing HTML based documentation. And again that's rudimentary HTML is also sufficient. Okay, will they will need a windows or Linux or macOS computer right they need a computer that they can do development on with at least two gig of Ram. And I noted this in the application. Okay. Do we need to say, are we going to run into like windows seven and stuff. We might and even if we do in this particular case, I think it can be done. Okay, there's no no requirement for Docker. There's no requirement for, for anything particular heavyweight and Jenkins itself can run in very small footprint. And Oleg just recently confirmed it still fits in 256 megabytes. Wow. So, so if they've got a two gigabytes of Ram was conservative enough that I think that they can, they can have an experience. So now the, the crucial thing there was this this really is no no Docker requirement for the project. But there it would help if they had Docker available for the learning part. But it's not mandatory right this is not saying oh you must have Docker it's rather saying Docker will help because a number of our examples use Docker. Okay. All right so now the bigger challenge for me is this this you've already seen it I think once but I wanted to go through it here in in session. I'm sure that if there's some crass mistake I've made or some flawed thing. The idea is that that we get feedback from people that are examples. There aren't enough examples in the pipeline steps reference. And they're certainly correct. There aren't a lot of examples right it's, if we pick any arbitrary plug in let's see let's pick the Android lint plug in. So here it is, it says there's a step, and it has a bunch of arguments, all, many of them optional but no description of any of the arguments, other than that they exist their type string and they're optional. So, so that's, that's not a, not a great experience for the person trying it right clicking on them doesn't get you anything right. It does not. So now inside the pipeline syntax. In that context you can see on the UI how they're positioned and placed. And when you're doing pipeline syntax snippet generation, it's actually a little more comfortable than this. But that's, that's not the context they have when they're reading this documentation. So that's what I was, I was not completely so they can go in if they pull up the snippet generator. There they can see information that will let them do something here. Exactly research tool okay. Right and that's part of oh I need to start my snippet generator just a minute. Let's get that running. We need this because we need to be able to look at a periodic we'll give it a minute or two to start but, but the, the idea is that we want to improve the experience for people who, for whatever reason arrive on this page on these kinds of pages and if we look at this is my feeble attempt at an improvement to this kind of page with examples and hints that hey you really should use the snippet generator as described here. Right. And when you use the snippet generator it shows this and when you use the snippet generator it use does this. So the idea is to be really crass about hinting please use the snippet generator. Right. But then, now what the snippet generator doesn't tell you is why I want this particular plugin and a step. It does not it's, it's not giving you it's not giving you an overview of what can that step do for you what value do you gain from that step you're correct. Right, and I do expect that out of the documentation to right and so, so here it tells us this thing performs a get clone from a repository. It tells us something about the step and there are plenty of plugins here that don't even have that level of detail. Right. That's what I was thinking. Yeah. So, so the idea is, let's improve that now, let's improve the pipeline steps reference so that people have a better experience developing pipeline pipelines. That means pipeline steps, the arguments, and now the challenges how do they experience it and so what I did here was sort of a microsteps and old egg looked at this document and said wow that's that's that's very finely detailed much more than we would have expected. And it is right this is intentionally I wrote it for for what I thought was somebody who has almost no experience in in this kind of space just maybe they've had some preliminary preliminary experience and some of the, the people involved maybe absolutely dumbfounded that I wrote something this detail that's great I would love to hear way that was much too detailed you wasted my time. This is just marquis yes this is just why we love you. Well, and my worry was, hey if I handed this to one of my kids that's not taken a technology degree in the university, I think they could still get it. Right. Get successful even if all you've got is is a basic you know you're starting your technical education now. The first step was get everything ready to, to experience the product because I'm assuming these people don't know and haven't used Jenkins. And so they needed Jenkins account, because we're going to have them do the issue tracker thanks for catching that by the way. And they need to install Jenkins. And it's best if they install it with blue ocean so it's describing that, and then experiment with one or more pipelines using one of the tutorials, or this online video, any one of those it's the goal is do something to create a pipeline. This is not specifically saying you must do this or that tutorial, because these tutorials that are linked here require Docker, and I didn't want to say who you must be able to run Docker on your computer. Right, that that's that may be more than they're actually able to do with their computers. And then this one I was wondering. Okay with blue ocean I can create a pipeline that has a bunch of echo steps. But anything more I would be in try mean because I don't have sort of the back assumption is you've been building your app with maven so now we're just going to call maven and you get something functional pretty quickly is what we want them to do here actually is to just do a bunch of echo or I guess they come up print statements or something in blue ocean. Not really but thankfully this declarative pipelines with Jenkins video. It takes them through much more detail than just echo steps. Okay, and likewise these tutorials hint at ways that they can do much more than just a series of echo steps. Okay. So I was, but so yeah so this is, this is definitely vague. So it is this is not and this this this may they may go through several of these and immediately raise flags to us and say, Hey, I didn't know what to do here I don't know what you're talking about. Right. And if they do that then we would just step them, I mean, they could do go into blue ocean and do a bunch of echo steps. They could and and if this became a stopping point this is a great place for office hours to do a for mentoring to do a hey let's do a thing together. Right. Okay, good. Excellent. Excellent. So, so then the idea was okay they've, they've at this point created a pipeline based on either the contents of this hour long video, or of pipeline based on these specific step wise tutorials. The next is introduce them to the syntax generator, because they probably haven't seen they may not have seen the syntax generator yet in this step. So let me go through the syntax generator the snippet generator just to see. Right. Then another piece is all right, let's have them do the blue ocean pipeline editor to see how it feels this what what the intent here is during this and I'm assuming this could take as much as as much as three or four days a week for them to get through this in this kind of exploring. Right. And by the edit by the pipeline editor you mean the graphical editor right not the code editor. I do exactly that's correct it's this thing it's what it is is, it's this page right here where it shows. I'm going to click this new pipeline pipeline button or this create a new pipeline, and walk through this very step wise series of things to create myself a pipeline perfect okay. I did not mandate that they need a GitHub account, but they certainly will need one. It's a good point that just having talked this through somewhere down there I saw you have them set up a GitHub it. Oh, maybe I did okay. Oh but maybe when they get ready because well they've got to get to the source if they're going to put the right well and they could they could certainly. Oh, here it is join get up. Yes, I did. Okay, good. Okay, because they've got to be able to fork the repository right they can't submit without being able to fork. So the, the blue ocean experience here was. Okay, let's get them through they've, they've created a pipeline using using whatever techniques are in the tutorials. They've created they've interacted with a snippet generator. They've now, wait a minute, if they don't have a GitHub. There's my in training we've given them a lab where they've got to get to your repose. And that's what blue ocean. If you don't hook up to some get repo, you can't go any farther with blue ocean can you. That's correct. So they'll have to either have a bit bucket account or a GitHub account or have their own giddy server, how they get there. There, there are lots of descriptions in these things about using using those so the, the three tutorials here all assume GitHub. What I think he is that the attached to GitHub needs to come up farther in the document. Yeah, so join GitHub. That's our, we would just think they could do all this stuff without joining GitHub and only when they went to do the writing did they need GitHub but that's not true. Right. Okay, good. Yeah, so we should at least put the join GitHub here. Move that up from there into. And they're actually they're going to need to create their own repo and GitHub aren't they to do this to create a pipeline. Yes, well, for certainly for several of the tutorials they need to so these three tutorials all assume that you've got GitHub. So that you're ready to work with it now if I remember I don't know that they yeah in fact they have to have right access so, so let's just actually I think that hints. Can you move the entire join GitHub and assure you can fork up because it's absolutely correct they need to be able to fork already at this point. Good. Thank you. Nice catch. Um, don't they don't. Can they use an existing GitHub repo to do their little first pipeline. They need their own repo to do that. So what these what these tutorials will do is take them through how they fork the repo fork a reference repo to get what what they what they want. Right, that will be if they are when they're ready to write, but at the beginning no this is this is still this is still just the this is still just getting experience. So am I going to fork and then create my stupid little pipeline that says this is the way we build it says fork and clone the sample repository so it gives them the instructions on. Okay, and they do the sample repository is that what they are. Exactly. Okay. If this is, if they say oh I don't have Docker, then, then it's all right, then what you do is you do this other one where you use the the instructions in this video and then you have to have to do more work yourself by watching the video following the instructions Oh, do this do this that kind of thing. Okay, cool. Be really interesting for us to see what sort of background they have. And whether they're like American college kids by the time they get into a comp cyber have already such hackers that they can do a lot of stuff and I don't know that everybody else is that way. And that's, and I don't know at what point, you know, are these are the women in this program just having completed high school, you know, are they 18 year olds just barely completed high school, or are they very nearly completing university or are they in a trade school, I just don't know, agree. So this is, this is, well, my thought was this, this won't do us harm if it's overly detailed. If it's excessive, we're not damaged by that. Yeah, we may find it's utterly detailed, but right and if we do we fix that because they have like, do you remember DeVry Institute. Yeah, I mean you just you did a cobalt program you copied this cobalt for you know, and people came out of they could code but they had no idea what they were doing. Right, right. You know, so interesting. I don't know if there's some business. Okay, I'll shut up. So, so then the so they've been through by this point snippet generator. The pipeline editor and the pipeline steps references the last step so that they can see the steps reference inside their Jenkins installation. The reason for each of these steps is each of these introductory things will be used later in their experiences they as they're doing a real change to a real plug in. I'm back to the snippet generator because you kind of if you're working in the ocean the snippet generator is if you do something that blue ocean doesn't provide and you're getting to the code editor right. Right, or if you are not working in declarative, but working in scripted pipeline. Um, should we give them a couple of examples of steps that they might want to look at in snippet generator. There's just to make sure that they don't that they go for something common and straightforward and not some. Yeah, so what I suggested here was check out J unit. Yeah, okay, so yeah and and these several of these are sort of poster children for whoa that needs more documentation like input if I remember right is one that was high on the list of me look at it let's see where is input I think input is part of workflow durable task. Check out as part of workflow scm the number two most commented, I didn't put the number one on the list because, because it's, it's complicated and assumes things that you know things about Jenkins like what it means to have a downstream and upstream chain build. Okay, yeah, the most frequently commented one is all about how do you launch another build how do you chain builds together and we generally have advised people in general don't chain builds builds together. Right, this is not freestyle. Yes. Right. Okay, so sorry we were running longer on this review process but thank you very much for your patients. Any other comments on this on this first task. No, I think that's good. Okay, so, so task one introduction to Jenkins to pipeline to blue ocean to the syntax generator and to get your Java installed. Step two introduction to building a Jenkins plugin. They're going to need to make changes to Jenkins plugins and in order to make changes to Jenkins plugins they've got to be able to compile them. Yes. So what this does is this is the starter for a novice in working with a plugin so confirm you've got get and clone the repository and. So now this did. Yeah, oh, this is. Oops, oops, that change. Right. So I've got a mistake here. We need another case of fork. And clone, we lost something here and made it. Okay, got it. So if they hadn't already forked. Tell him fork it again. All right, so then compile the plugin. Now this one may surprise us there may be problems. It's going to download dependencies and if they have notoriously poor Internet. That could be a challenge for them but they'll just have to wait. You know if their internet access is slow, low performing. There's not much we can do to fix that except tell them run it once so that it downloads those dependencies and now you're ready to go. Yep. So then one more step in this in this build a Jenkins plugin is upload it to your Jenkins. So do what a developer might do of upload it to your Jenkins restart Jenkins and confirm that the new thing you just built is now visible. The idea being they're going to have to do this whenever they make a change they've got to be able to see yes did it work. Okay, so next step, change something in an existing pipeline in an existing plugin and see that you and confirm you can see your change. So in this case, it's also teaching them some command line get tools. It's highlighting to them. Hey, here are the things you need to do. Some of them I assume will have no get experience and we may have to coach them on get during the mentoring sessions. Right. Others may already be quite skilled at it and we'll just scoff and laugh and walk past it. That's great. And so here we have them compile the plugin with the changes upload it and restart Jenkins and now confirm that the modified help is visible and then throw it all away. Okay. Now this okay we've now taken them to two preparatory steps now we're ready to do the real thing and the real thing uses much more, much shorter, more concise. Do this do this do this without saying you need to show somebody this you need to show somebody this. I assume this is where they will encounter the first set of significant problems where they say, I don't know how to do this I don't know how to this your instructions for here what do I do next. Right. Okay, so, so again and this takes them all the way through submitting their poll request. And that includes hey loaded into Jenkins compile the plugin locally confirm that it's the help you add it is there, and off we go. What I was not talked to them about and I haven't found a place to do that yet is how to how to find a good location to do that addition and so that's a piece here that that is missing. See how do we for example, yeah, see some place there is find the location. See there's something missing here Meg hang on just a minute. Okay, find play a place that's missing help. Got it. Here are the hot, hot pages from the this pivot table. Where's my pivot table. Just a minute. I want that pivot. Oh there is this pivot table link. So, wildly cool this was here we've got a the sheet, a copy of the sheet that contains. Feedback from the last four years almost four years of Jenkins documentation. And here is a pivot table that shows us which plugins have had the most comments. So, so this pipeline build step has had 86 comments in that that period and of those over half were either unhelpful or not that helpful. So, so clearly there that's something to improve. Yes. The idea was, okay that pivot table lets them choose something like the build step or the SCM step or whichever. And now I've got to see where is yes there is pipeline input step. There's a good example of yeah plenty of things where we we've got lots of feedback that says hey this documentation is not good enough. How can you help me. Right. I'm going to pick that out of the pivot table rather than just say here's your choices. Well, actually, I, I list the choices in order here so they can, they can choose them. And if they then say I don't want to choose that one I want to choose another one. Okay, that's fine too. Yeah, okay cool. Go ahead. No, it's just junk. Okay, got it. All right, it's but I've got three landline heads and say it's in my bedroom and they all play different music. And it makes a lot of noise and it isn't like your cell phone where you can just press decline. Right, got it. Okay, sorry about that so. No problem. So, as, as you had suggested, propose that they create an issue that they report the issue. And then have them forked repository clone it create a branch compile it locally. This is the piece that's missing here is create a branch for the change, add the missing pipeline help by finding the Java class that implements the pipeline step or argument. Adding the a resource, a file, a help dot HTML in the resource directory that matches the path to the pipeline step. That's an awful lot of words. For example, here and this is where for example, yeah, the. And I'll put this in separately I think the get step is implemented in Java at and documented in HTML at this. Right. Okay. So note the note the similar paths has between the Java code and the documentation, all of the same pattern is the plug in your, your improvement. So does that any any so any concerns there. So much to do that. Now, do we want them to do one PR her class. For initially, I think we should because we want I think we want to get them to this point as rapidly as we can once right once we've gotten them to this point as rapidly as possible once. We can look at, okay, our is this too small a poll request, add more. We can steer once we get them here my worry is, if we don't get them here before the end of the four weeks, we will get no net value as a project out of their work. Right. And they will not have felt like they accomplished anything either so. Right, right. Yeah, exactly. So something I see up above create a branch. We are not explicit since we're being very detailed that they need to create that branch off master. And they need to do a poll before they do it. Oh, good point. Yeah, that's and that's a very good point over the course of the four weeks. They need to be sure that they. Right, very good. Okay, based on the current upstream master branch. And there we now need to do a series of steps so it's get pole. See do we have the fork, we don't have the fork added to their remote. Oh, make you have found a very challenging issue. So we need to add get remote ad upstream earlier. Oh, no, actually, it's just right here. And add the upstream repository. Yeah, add the upstream repo repository. Okay, that's a remote. So now that means I've put additional description there. That isn't in the first copy of that where it said clone the remote repository. Okay. Okay, that's, that's going to have to go someplace and needs more documentation needs more detail. Good. Thanks. It just, and I did it early on too. I finished working on one PR and I'm in my branch and I just go get checkout dash B. And I finally stopped doing that I was just stunned at how often I get somebody and they come in with a PR that has the last four projects they worked on. Exactly. So that it's that's very healthy that we, and Xenov made exactly that mistake early on in her experience as a Google season of docs contributor. Once you get it. It's just doesn't make it make sense but until you do it just seems why do I have to keep going back to master. Right, right. The whole. Oh, I'm trying to keep up with the other people who are advancing around me this is not a centralized source control system this is distributed. Yes, exactly. Okay. Okay, good. So, we need more detail there I'll put that in later. The next topic was is sort of a more aggressive thing I'm not sure we're going to get there in the four weeks with them. If we do I'll be delighted. But this is just a textual change saying hey, promote the use of the pipeline syntax snippet generator and tell people. The one I used was to get plug in documentation as a suggestion here's a technique that's that I use that I think is helping users by saying, remember when you use the syntax generator this is how it looks and when you use the syntax generator here, this is how it looks. Right. So, now, oh, that's right and this one is only in the plug in doc so this is introducing the documentation as code, and to writing the documentation in the plug in read me. Great. The next one is adding that same kind of hint into the, the, the online help that shifts with the pipeline step. So we've got somebody who's really advanced this last thing is a really bold step. And what this one does is makes pipeline editing much prettier for pipeline developer for for people who are developing pipelines with Jenkins either through Blue Ocean, or using their own text editor or the snippet generator. Okay. So this one is feels to me so aggressive so bold. I'm still working on stuff for this in the get plug in, for example, right. Okay, so we're at 40 minutes and I desperately want your feedback on another piece. Okay. Are you okay if we switch, switch tasks, focus. Great. All right so this piece is Google season of docs 2021. And the idea there is that our application is due to them March 26. So we've got about 11 days. Yep. And my task today is to prep a draft of the application form to them. The, the crucial steps here are that until 2016. The the actual writing process is is can officially begin and we have to have hired and chosen our technical writer by May 17. All right. In June 17 we submit monthly evaluations, July, August, September, October, and then November project is done. Okay. And, and so, so the challenge there is got to get all of the, the phases, or got to get this application prepped, according to their ideas, or according to their concepts. And they suggest project ideas that hey they might look like this. They might look like that. Okay, see. Here we go. Okay. Choose the most promising idea for each organization may submit only one proposal okay so that's different we only want. We want one and it will need to follow this template. So crucial that I read through these and be sure I understand what the plan is. Okay. And then you have to choose the one thing to. Okay, so what, what it is is the, the, which project idea do we want to submit is a is a good question that will raise to participants in the office hours in the doctor's office hours and probably I may bring it also to advocacy and outreach saying hey here are here are two or three different project ideas which one should we submit to Google season of docs. So do you have ideas in mind already I assume. Document Jenkins on Kubernetes is still hot on my mind. We started it last year with Zina, but there is still so so much to do on it, but that needs a lot more thought about what should the content be and who who does it, etc. If that one is bigger than I can squeeze into the time we have the 11 days we have and this technique we're using with with she code Africa could also work for a season of docs writer saying hey sweep through 100 or more plugins or 20 plugins in the course of four or five months of writing and improve the documentation. Yeah, because this does seem to be I mean a lot of the guide material is weak you see there's a lot of stuff on you know, this wasn't that helpful, but the steps are where it really comes together aren't they. Well, well there's there's plenty of, and that's that's another right we had a we had a project idea in the past to Google season of docs which suggested that we should improve these things called the solution pages. These are is these are application or system centered pages focused on hey if you're a Java developer look at this. And it takes you through very, very Java specific things and it's this one is quite weak actually. If you're a GitHub user do this. We could have a page like this for bit bucket, we could have a page like this for giddy. If you are a Docker user. Here's this and there are lots of things we could talk about with Docker. Right. So, so the solution pages was one from last year and significantly improving them, but in that case we really need. We need a technical writer that is willing to do lots of exploring to find out what should be done here and why. Right. Yeah, so here's the one we call it continuous delivery up at the top and it's all about Jenkins pipeline. Okay, cool. Yeah. So, so we have some project ideas actually let's look at the project ideas from last year, because it's probably another those are good candidates for things we could consider this year so for instance Google season of docs in the documentation dig. Google season of docs here we go. So, plug in documentation on GitHub, GitHub was one this is where we've transitioned about 600 600 650 plugins from documentation on the wiki to documentation inside their GitHub repository. This would be a great thing to have more of it. User guide rework. This, I don't think I can be ready to have it be a viable one for next for in 11 days. This one really says use the thing that we had proposed we had started the idea of propose a better structure for the documentation. And in order to do that we need experts and lots of time to consult. Right. 11 days isn't enough. Now, same for administrator guide but the solution pages. This is one that that there are lots of solution pages that could be improved and much better. So, plug in documentation solution pages, and, and the pipeline examples thing that we're currently working. Would a, would a solution page for Kubernetes make sense as sort of a high level overview because that's the thing even if we get all the other stuff done, then you had the solution page because how do I get started. Absolutely, and a solution page for Kubernetes was very high on the list that was that was already discussed last year as part of the solution pages one of the suggestions was. Okay, we need, we need a solution page for Kubernetes just like we need one for bit bucket, and we need one for giddy, and we need more in the solution page for GitHub. Right. Yeah, so absolutely. I think that takes me through the, the, the idea so that's the application is due is due March 26 2021. And project and writing starts. I think we say 16th, 16th April. Thank you very much April 16 2021. Yeah, that's right. But given that they're hiring deadline is is May 16. The practical reality is they may not start writing until they've been hired. Right the way this works is Google gives money to the Jenkins project, the Jenkins project then uses that money to pay a writer to do this work. Right so we say writing can start. Right. What it does mean I mean a way I see it. The day we hire somebody, if it's after April 16, they can start working immediately. Correct. We don't hire somebody and say well now in two weeks you can start. Right, exactly. And then start needs to be singular. May start. Oh, oops, yes, thank you. Good check. All right. So, so Jenkins on Kubernetes solution pages, including Kubernetes pipeline examples the other one, what was the other one that we said it was solution pages. Oh, all right, and plug in docs as code. Actually, what should that be? I know they're the steps are part of plugins, but plug in documentation to me, it's a steps documentation that needs to. No, no, you're talking about that. Never mind, you're talking about the wikis. Never mind. Yeah, so this is really the this is the transformation of existing plug in documentation creation of new in the GitHub repo instead of how we used to do it in the past where people would write it in the wiki and then hope that somebody else would revise it and help them make better documentation that those hopes just didn't pan out typically. So we go so is another one to continue the step, the step documentation from she code Africa. Yeah, and that's that's this one right here. Okay. Do we have those. I was wondering, we have a lot. We have a lot of repos that all have their own Jenkins file in them. Could we pull some of those for examples rather than going, you know, asking people to write there to create their own pipelines for the examples. We could, but most of the work or not really. Well, most of the most of the Jenkins files in Jenkins development have a single line in them that says build plug in. And they use a pipeline, a shared pipeline library to implement build plug in. So, so the, I intentionally stayed away from the Jenkins files in plugin repositories because they are they are not representative examples of the kinds of pipelines that new users create. Right. They're they're created by experts. Is there anything in the shared library functions that we could use. Oh, yes, yes, lots. But the, the stuff is exotic enough that I think it's beyond the depth of this group. So for instance, the pipeline that pipeline shared library understands that sometimes it will run on an untrusted machine and other times it will run on a trusted and it adapts itself based on whether it's on a trusted or an untrusted machine. And that's a really cool concept but I think that is beyond what we could hope to achieve in four weeks with with these, these new contributors. Right. I'm getting there thinking, I mean, if, if I'm a person and I've got to deliver software and I've been building it stuff I've got something that I can start doing a pipeline. I don't know what it's like to come in virginly and just say oh I'm going to create a pipeline for pedagogical purposes. And I'm pretty new to this. I'm kind of wondering where, where they get the information to do that. I hope that that's part of the, that's part of their, their initial, you mean the, if you're talking about Google season of docs, I would love to reuse this as a way to get them started right and at least say hey, here are the kinds of things that you're going to need to do because you'll be involved in in parts of these. Right. I don't know if that this, this document will actually be reusable in Google season of docs or if I'm just dreaming a pipe dream. Yeah. If all it does is serve us for she code Africa that's great. If we get some reuse from it for other things, even better. I think that I mean, using it in she code Africa will be our beta test I'm sure we'll be fine it afterwards. Right. Exactly. But yeah, cool. All right. I think that covered all the topics that run my list anything else for you make. Nope. All right, let's call an end to this thanks very much. Okay, I will respond to Melissa to. All right. Great. Thanks so much. Well, when's your snow going to melt is it going to melt soon. We hope with well it's supposed to be 60 degrees by Friday. So we expect the snow will be mostly gone within a few days. Yeah, I just that much snow takes a few days to melt. Yes. See you. Take care. Bye.