 Welcome to documentation office hours. It's the third of March 2022 topics that I've got on the agenda news. Let's see we had interactive tests as our sorry it's the fourth of March, because in India it is in fact already the fourth interactive tests I brought it forward from last time in case we need more discussion of it. Linux installer switch this one I definitely want to spend some more time on. And then Google summer of code, if there's any topics we need there. Other, oh she called Africa yeah we can talk that other topics troubleshooting and change log okay this one I actually want to pull up to the top. Because I've submitted it and wanted to invite everybody to please review it as your time allows. I just started looking at it in the last 10 minutes while I was waiting for this meeting. And I have one issue that I'd like to discuss because we. It looks like this does have I we knew it was coming that you can that the ability to turn off the agent to control or filter on the UI is gone. Right right it does absolutely that is correct. But in Daniel's notes there was another piece of it that I didn't know was going away and I want to make sure that that PR in case it ever gets merged is still accurate so. Oh okay good well so then let's let's be sure that we take that up during that segment. Any other topics we need to bring into today's agenda. Yes, I wanted to, I have one question regarding the weekly change law. On location on that as well. Great so let's put that top of the list weekly change log discussion. Great. Okay. Anything else. Good to go. Okay. So we have news Jenkins 2.337 released and thanks very much to those who reviewed the change log fixes for several image and icon issues still one or two left. So that's in progress. There's coming in happening in core in particular said there's some interesting fixes around remoting and establishing restart behaviors that that it's good to see Jesse Glick and Basel Crow and Jeff Thompson working together on some things that we didn't quite understand what was happening and I think they've got a better idea now on what's happening with certain restart cases. And the release candidate is out and testing is happening. I've submitted a draft pull request and on Thursday, the 10th of March, Darren Pope and I will do a live stream introducing what's new in Jenkins 2.332.1. It will highlight some of these things. We've still got an open question whether or not we'll include the Linux installer. I'm more and more persuaded we should but I've got to reopen the conversation on Jenkins.io or on on the Jenkins developer list. Any questions on those two items of news. Okay, the next topic is change log and upgrade guide so Meg you had a question what was your question about. In the into the file it is line 6799. I think I'm just showing the rendered version so agent to control security subsystem. Yes. And the admin customizable allow list for colibers and file callables and file has have been removed. Now, those are the things that we say. So we've got this filter. If it's what if it's filtering out something legitimate that I need. I thought this meant you can no longer do a callable from the from you can no longer call from the agent to the to the controller to read a file. That's what I was reading the pros and I just wanted to see if it was there. So I'll go back and check. Because I think somewhere in the docs there's, it's not in the section that I was mucking with but there is a link to the docs about how to change that. So that is so that probably needs to be filtered out as well then let's read the original pull request just to be sure because Daniel. Daniel is really good with his pull request to whoops. I'm going to put Jenkins in for just a minute. Sorry, just a minute. There we go. No. It would help if I remember the name of the organization. Okay, this is better. Okay, so it says it really does remove the callable allow list and he says default entries has our long obsolete everyone else had seven years to adapt their plugins. Removes the custom file axis. Yeah, so I think I think he means it. Okay, let me go in because I'm not next. It's one of those things I knew it was over there and I just referenced it never. Let me go look at it. And I'll send a link back to, to make sure that this, and I suppose actually, people don't upgrade that fast that we probably should not delete that doc immediately but we should put a big warning at the top that, as of release such and such this no longer works. Right, right. Absolutely. Yeah, this is this has been removed this has been removed from Jenkins 2.332.1 and later. So, so that way we tell people outright this, this used to work and then we probably ought to put it to do in it to remind ourselves a year from now to delete it completely. Yeah, those kind of antiquities don't usually help help readers after about a year. Right, right. Because that's what because I did not. This is all about plugins I was under the impression that people in there that maybe might in some of their old installations for something that was not a plug in that was their own stuff. Be mucking with this but this sort of sounds like it was only the plugins. Okay. So, I, you know, not my area of expertise. All right, but So, did that address your concern on agent to controller. It did. It did. The category really not my problem, problem except to make sure that the docs are sort of close to truth. Good. All right. Okay. So, anything else on that change log encourage everyone. I did sorting and sort of grouping of things from based on my own taste. If you are welcome to dispute that you are welcome to disagree with it. Please don't be shy if you find something you think would be better done better a different way. Yeah, there's a couple of just I that said, that's where I was just at that point when you pinged on the system. And I stopped looking, there were a couple of above there were the pros I didn't really know what they were saying but, oh good well and so that those are good things to have somebody else read them and then see is there a better way to phrase it. You know, so can I just leave a note that says this needs to be right. I don't know what you can absolutely. Yeah, just, hey, I don't understand this is a great comment. Yeah. Okay, cool. All right. So, do you guys you had a question on the weekly change log what was your question. So my question is the comments that I'm leaving every Monday, is it helpful to you, because I think that I'm already commenting things that you already know. So just wanted to know actually quite the opposite. I'm, I'm, I'm relying heavily on your reviews and making a much, much lighter review myself because of it. So, so I'm delighted with your reviews. Yeah, I'm, I'm absolutely thrilled with the reviews from others, because it lets me put much less, much less worry on to that that thing before we publish it. So guys, please keep doing it if you've got time. Now if you don't have time I also understand that it's a busy. We're all busy. No problem. Just wanted to make sure it's helpful so I'll make sure it happens. Thanks. Thank you. Yes, I am noticing that some of our frequent contributors are learning from this. So I've seen phraseology that we have put in on old PR showing up on new PRs. Right. That's good. And Basel, for instance, has Basel Basel wrote a pull request template change that notes that the phrasing is imperative. It's like, Oh, well, thank you, Basel. Yes, that's in the style guide. I put it into the pull request thing so that, Hey, yes, please say it in the imperative voice. So nice. Yes, it means I have to remember what imperative means. I just Google what imperative means. All right. Well done. Well done, dear eyes. The danger of not being a professional writer. Yes, in fact, that is a serious danger. Well, it's people who only know English don't know what cases are. Yeah, that's also true. Yeah. All right, what Latin teacher who taught me this stuff so only place I learned it. Anything else on the weekly changelog. Yes, just trying. Basel wrote about pull request template that wants to be used imperative phrasing. So can you tell me like what does he mean, what do you mean by this statement. Instead of saying, you should always name this with prefixes of breed of dog, just say name this file with a prefixes. So it's all it's getting rid of a lot of the soft all the, you really ought to do this you should just say do it. Rather than saying you should walk to the store stay walk to the store. That's imperative. Yeah, so the way he describes it is the changelog should be in the imperative mode. In other words, right. Do this return that rather than does this returns that. It shifts the sense of the sentence. Oh, and there's a link to our old changelogs that's probably helping people to to because they can see examples of the people who are already writing. Right. Yeah, now the daunting challenge here is far too many people see these comments and just ignore them. I had a pull request so so but nonetheless, there was there are some who read it and we hope that that will be a positive for them. Right. Yeah, so I understood like what he's trying to say here that it should be like do this return that not does this returns that. So, can we look at an example and translate it into imperative mode just for my help. Sure, sure, that's I think that's a great exercise let's do it. So let's look at the pull request pending review and the changelog here open up that one because that one we hope is already an imperative but let's look at 2.338. This one. Okay. Let's see if we get a sample here. Nope, those all look like they're an imperative voice so how about. So, can you scroll down. So this one that is this ad Brazilian Portuguese translation property finds. So this is a this is an imperative mode, but it would have been like non imperative mode if it read something like ads Brazilian Portuguese translation right. At least I think that's what it means. It's also that we we write it in present tense, not past tense. So instead of ad present, instead of saying added happened in the past, we say ad. That's what this release is doing is it add it will add Brazilian Portuguese translation property funds. I'm not actually sure that's technically imperative imperative is an order. Okay, so guy guy this is good. This is why we like having a professional writer who in general, you know, life is sweeter if you say keep us isolated. But it's but it's good pros. It's well, the contrast there is so much stuff that says, because we used to do such and such and it caused this and this problem I mean and you get in the regular doc, you have to read three or four lines before you find what they're doing. So you could almost say use Chris direct present tense or something. It's like get to the point. So, and if if calling it imperative is making it happy for everybody else I'm good because I don't know what else to call it so simply. Great. And for me, the examples are the thing that we I okay keep keep the pros tight and simple. So dirage does that help or still not. Yes, it helps. Yes. Okay, all right, anything else on the weekly changelog. All right, so then. I can keep an eye for we can continue to watch for samples like that and then discuss them here I think that's a good thing to do. All right, so next topic was interactive tests. I think we had, we had brought this one to a conclusion last week. Is there more that you wanted to discuss there dirage. No, nothing else. We had a really good discussion. Okay, so I'm just great. Except wait a second. What, what was the end result of that discussion that it would be nice to have these things do we have issues filed for them. We do not have issues filed for them. We have any hopes of ever doing them or I have, I have hopes of asking some particular people to help be more involved in interactive testing of the most recent UI changes. So I'm running an initiative myself amongst some fellow developers to say hey, this is a precious time for us to be doing more testing to explore these UI changes. And I think I'm getting it across because I've got other people who are interested so I think we will see additional what it will be as additional review of pull requests. Okay, so that's happening it. I think so. Yeah. Okay. I and I think I think that's the best way. As I've looked at what, how much progress, young fire chick and Alexander Brandes and Tim Jack home have brought to Jenkins in the three months since the last yes. It's impressive. I do not want to slow them down I want to help them go even faster. But I think in order to do that we need more testing, and that testing right now is best done by human beings looking for surprises and oopses. And then we may eventually get to the point where automation would help us but for right now I think it's human beings looking for to be sure things are behaving and our structure the way we want them. Cool. All right. Anything else then on the interactive test topic. Okay, so next topic is a is still open it is beginning in 2.335 continuing 336 and 337 the Linux installers now use system be as their way to control the process, rather than using the system five style in it. That has the significant benefit that now we have one way of describing how to configure services on any machine that used a Linux installer whether it was Debian or Ubuntu, or red hat or sentos or open Susie or Susie. Anyone of those six or Amazon Linux for that matter, or Alibaba Linux. So, many of these vendors have a system be based configuration and by us now you switching to system be it's easier to describe how to do those kind of changes. Now the challenges, shall we make the switch now. 2.332.1 or wait three months. So another way of phrasing it is, is three weeks of testing in the weekly enough to switch and my sense based on bug reports. It is, is it getting extensive testing for all sorts of different distributions. Good question it's getting. Oh dear moment. Okay, sorry didn't mean to have to cough there. So, it is getting as much testing as a weekly gets with installers. I don't have data yet. I was thinking that okay I could go try to find some data to see how many installations we get of a weekly. And that would give us some approximation okay if there are 10,000 installations of a weekly within the first week of its install. That's, that's an interesting piece of data compared to if there are 100. For each install do we know what platform it's on. We, we have some data. I've seen data with regards to operating system but not with regards particularly to installer. But if we know operating system do we know whether it's just, we've got a guest and we've got a reasonable guest then that if they're installing it on a Debian Linux for instance, they are probably using the Debian package installer. Most people do not bother with using the war file when they can use a package installer. Right. And that would include you but yeah that's what it is. If we found out that we had very small coverage well like some of these less freak I'm I'm going to assume that a bunch of Debian and red hat are pretty infidora are pretty well tested. I think I think that's a safe assumption but but I think it's worth how much do we care. Like, I don't know how much open Susie and Susie is out there right now. And I don't, I don't know. I know that we don't have documentation on our official documentation page for open Susie or for Susie. Right. So I'm not terribly worried about that one. I'm glad we've got the installer but it has some oddities. That, that I, I'm not ready to worry about at the moment or at least it did before. And so it was, it was a different thing for me Susie was sort of a, I'm less worried about it than I am about Debian and red hat. Right. Okay, so, so we do still need a documentation page on managing system D services. We've got an agreement from last time on what topics, etc. So, I feel really good about that and I'm comfortable that I think I can get that done before the Wednesday release. So that it would be ready to go. So you're now the number one writer here huh. Well, I think other things. So why you're exhausted by Thursday. Well, the, the challenges, the challenges that we've got lots of writing to do and not a lot of time to do it. So, right. But I guess, I guess what I'm, what I'm, are there any strong objections or any objections to the notion that hey let's make the switch now, or things where you're saying no I'm concerned about that that's too risky. We've got to, we've got to get it out there, you know, it's, this is the future. Yeah, and it's going to blow something up. Now's as good a time as any to blow things up. Yeah. Well, and another way to say what you just said Meg is that will three more months actually surface the classes of problems that we will likely see when we do it in LTS and I think the answer is no because LTS users are more than weekly users and therefore we may not get any, any, any significant amount of additional reports between now and three months from now and which would be our next window to do a change like this we shouldn't do this kind of a change on a dot two or a dot three. Right. So, so the next dot one would be June. Um, would we would it make any difference if we put out, I don't know, bulletins or whatever in the community, alerting that this is about to happen. Oh, oh yes. And it would be in the upgrade guide. This would definitely. What I think is that there, there's probably a lot of people who sometimes test get around to testing and sometimes they don't to alert people that this is coming and if you think it might be a biggie for you you might want to test. Oh, oh, or the LTS. Yeah, and we actually did that with people who had expressed interest in system D, and they did test it. We were really grateful for them during the development phase before it was ever released in weekly. We had reports from several users of positive testing. So, so we were very, very grateful for that. Yeah, so maybe that's already been done. Maybe just, you know, not the normal sort of testing that most of these get to alert people this is a special one that could be big. Right. So, but okay. Yeah. I'm going to assume that given that I haven't heard any strong objections I'm going to assume it's okay with those of you who are here, and I'll continue the conversation in the developer mailing list. That one, that's where it really needs to be final, because yeah that's that's where we started a week ago. Yeah, sure. Next topic I had on the list was Google Summer of Code any questions or concerns there. The, the office hours start in 30 minutes there so we will have time for an office hours discussion if there's something office hours related. That is, are we starting to see candidates who are interested in this. Yeah, we've had we've had we had 20 people attend the webinar that highlighted highlighted the talked about project ideas we've had from three to six attend every office hour session and different people at different times. So, so yeah it looks, it's, it's I'm not sure it's as heavy an involvement or as deep involvement as we've had in past Google Summer of Code episodes but it's been good. It's positive. Yeah, and the channels seem very active to so like people are asking questions on like getter. And I'm mostly focused on the getter stuff I haven't really checked the community channel but I know the getters like fairly active so that's a big positive to right because it means that people are asking questions and trying things out, which is always a good thing, and then, hopefully picking up some of the good for first time users. Right. So it's like a chance like even a chance to explore open source stuff. It's exciting. And I, I know that I'm seeing seeing friendly issues are being addressed, because I've seen or being attempted maybe is the better way to say it. And, and I've seen it with two, two, two different people attempting a friendly issue on the get client plug in. So, that's great. Fabulous. Maybe one of them would like to work on the system D documentation. It's like maybe we should have put in for a Google season of docs, but no, I'm not ready to Google season. That's a busy project. It's a very large effort. Yes, it is a very large effort project. All right, next topic then she code Africa contribute on. I submitted three project ideas, inclusive naming screenshot updates, and the one other was pipeline docs improvement pipeline help improvement. Is that similar to the one for last from last year. Yes, yeah. Okay, and what I what I did was offered to people on this one proposed we would accept to mentor to on this one. And two on this one the idea being that we can probably find mentors to support one mentor could support two people, and we won't be overwhelming anybody, or if we get two mentors for two people even better. Sure. What about the first bullet did not submit that one I want to talk to Zenab about it before. Okay. I'm going to submit the test the tutorials. Yeah. And that covered the topics that I had on she code Africa troubleshooting section. Oh, go ahead, Dirac. Sorry. So, the third point, the screenshot updates for Jenkins.io. That's the manual one right. Correct. Yes, this is the interactive one. Yeah, not automated. Thanks. Yeah, and when when I look at the the idea at the idea that Gavin Morgan offered of hey automate that thing. I think that's a great, great idea but I'm not sure it's given our experience last year with the contributors. I'm not sure that that's the kind of project I would drop onto one of them. I guess that's a lot of Java code and a lot of things that could go wrong. Very, very quickly and need a lot of interaction. I could see you might be able to be successful at it because you've had already months of experience in test automation. I'm not sure that these these first time contributors have that benefit. Yep. I also researched on it and I found a very nice article from CloudBees itself, which is titled automating screenshots in documentation. So it's exactly what we are looking for. Oh, cool. It's written by Chris Wald. So, very, very helpful. Oh, interesting. Very. Okay. Very good. Very good. All right. Anything else on she called Africa. Yep. What's the timeline timeline. Good question. So timeline. Oops. My understanding is it's April. To mid May. With two weeks of, of community bonding for weeks of development. Selection, I believe is happening in, in, in March. Is that what you're asking with regards to timeline? Yes, exactly. All right. Last topic on my list was troubleshooting section and I don't have anything additional there are there. Z knob was going to submit a poll request and I haven't had a chance to have any conversation with or haven't seen the poll request. So I assume it's still in progress. We should address or do we want to call ourselves done for today and we'll meet again in a week. Should I ask about the PR from a non Mormon, but from heck. I'm not supposed to laugh so loud. That's great. You probably should go over some of it if there's anything else that's open. Okay, let's do it. That's, that's, let's go ahead and take a look at open poll requests. I like that. I have my old list. There's actually a couple of others on there that had notes actually if you want to go down in the agenda. Okay, let's do a couple others that I made notes on. I can't remember. I think there's something we hadn't discussed. Okay, tell me when to stop. All right, so open PRs. When did I stop doing here we go. I think these are it right. Right. Yes. Okay, any particular ones you want to take first. Um, Well, I mean all of it, we had the discussion for 3392, but where are we is that. Let's take a look and see. So, what, what are the comments and checks have passed editorial changes made in January. The original author seems to have disappeared from the. Yeah, yeah, this was, I think this was, was this came from. Yeah, was a contributor contributed to some things to you two years ago, and we can either, we could either continue it or close it and reopen with somebody else either is fine. Now I don't see, I didn't all I guess the one who requested changes what changes did he request. Oh, that didn't help. I need to see which changes he requested so. Oh, oh, he's saying that this is in the wrong location. Got it. Okay. Yeah. Well, structure this doc said it's so bad I don't care anymore. Okay, so so well okay so saying part of not part of the okay but the managing page this is part of the user handbook. So, so I'm not sure I understand his objection there because it's, it's all part of the user handbook then the user handbook includes things that it's got a section chapter on system administration and a chapter on managing Jenkins. So, now maybe he means that this should go in the, not in the, not in the managing section but rather in the pipeline section maybe. Maybe is that what he means by user. Don't know. Okay, so let's read it so user. Yeah, Jenkins users who develop pipelines not admin so let's look at, let me just remind myself of the structure. Okay, so what we've got here is using Jenkins. And then we've got the pipeline section. Is this the place where spawning is the information about spawning processes well, but it's more than just pipeline that does this right freestyle jobs also do it. Right. I mean, they're the doc said, I don't know if we never have resources of priority but the, it's, you know, we're saved by search the structure has all sorts of problems in it. Right. I don't think I would hold out information just because it's submitted to the wrong place when we don't have a writer who can convert it to put it into the right place. Are you still getting your writer eventually. I am. Yes, I have confirmed it we've got it. We've done a plan on how that writer will, what how will successfully onboard them and they're coming soon. This could be a good, good project, you know for somebody like that who can actually devote to it. Right. Yep. If this is good information, I put it in even if it's not in the perfect split. But that's me. Yeah, and I think. Yeah, I think you've got, there are plenty of things where we should we should probably just accept that we're going to apply your, your proposed changes and be done with it. Yeah. Yeah, I think I agree with you here I don't see any value in saying talking about a Jenkins version that was released five years ago. Right. We support current current LTS and current weekly so talking about things that are that old doesn't help anybody. So, so we could go back wait a minute where that where did it go. Let's can can you edit that comment. I can. Yes. Okay. Um, let's just say Jenkins detects this situation. Right. And that's good, isn't it. It is. I think that's very reasonable. Okay, here's another one we can include in the batch this is sentence per line and better phrasing. Yeah, describing. No, that's not what I wanted. My mistake. I'm going to go for a process. Oops, okay. What are the standard air what did I do there. It's just got a back quote in the wrong location. Okay, okay. Do people actually understand it. I don't know. Yeah, I'm, yeah, I agree to file as much better. Or, well, they may show up as the EOF parent and the file or I don't know where. Oh, yes. File EOF or something. Because I think the EOF I think does show up in the air. Right. Make sense. Okay. Okay. Forking and processes. Oh, that's fun. And HTTP link. Really? Come on. It's got to be HTTPS seriously. To run a command is a demon. Well, Yeah, this and this is the one we use on on. Red hat demon. I don't know. EPL is actually that provides it. But you know, it's information. So it is. It needs to be through that. So this is. This is the description from the red hat from the fedora package sources of the same thing. Yeah. Okay. And this one is still still valid. I think so. How sad. Okay. Yep. Okay. Yeah. Yeah. Yeah. Yes, that's accurate. Thank you. Since XP is dead. I was going to say, is it just another work around? Yeah. Now I don't remember the last time somebody talked to me about ant. That's very impressive. I use it. Use it very frequently and test automation. Something else big in Jenkins uses ant syntax. It's like, it's sort of like in no way really to ant. Wild cards. Yeah. File file matching wild cards. Yeah. That's everywhere. Yeah. Also. The ant, the ant class loader is actually used. So they're all, yeah, lots of places. All right. So Meg, we've reviewed them. I'm going to commit the suggestions. Cool. And then does that leave the only open issue. Yeah. Yeah. Yeah. I think this belongs in a different section of the docs. Yeah. Then it's just, then it's just Oleg's feedback. And, and we could truthfully just decide we're going to override it. Oh, like right now it doesn't really have time to, to contribute to the Jenkins project. And I understand that. How well I know. Yeah, exactly. No, no shame with that. I have authority to override that and just say, Hey, we're going to go ahead. I would like to have it build first, but I don't know what to do with that. Okay. Oops. Why did I not get this one included? I'm not sure I understand that I made some mistake. Just a minute. I want to see this page. Oh, it's an outdated suggestion. Okay. So it's somehow already noted. This will set. Hmm. So I don't know what on that one. It's complaining about, but I can. Yeah. I don't think that we're going to get any difference. Truthfully. His question is still, where does it belong? And the answer for me is we want the content. The location. In the managing chapter is not bad because it's, it's at least general purpose. It's not limited to pipeline. Right. And if they search, they'll find it. Right. Okay. So we'll let that one run for now, see if it passes the CI. And then we can come back to it. Okay. I don't know. Can we get rid of another one in 10 minutes? We can try. Let's see. Oh, 33 81. Looks like it might be one that goes fast. It's been a while. I don't remember these, but just reading that note. Agents with wind. What was that? I don't know. Okay. So my comments were all handled. Oh, like requested changes. He approved. Oh, it needs to have conflicts resolved. Oh, and that's a large conflict. So this is, this is going to need me to do, I've got to have a real command line to do this. I can't resolve that level of conflicts from the, the GitHub UI. So this one just conflict resolved. I will. What is this? 33 81. Let me look at it because what I think that is, is something new that I shoved into that chapter, which is basically my definition of all the components. That's conflicting with this. It may be one of those where we want to keep both. Yeah. So let's, let's do a, let's see what we can do. Okay. Let's do the conflict resolution while we've got time. Oh, okay. Unless others object. I don't see any. Let's do it and see if we can get there in the time we've got. So GHPR check out. Was it 33 81? 33 81. Okay. Get merged. Yeah. Let's do the conflict resolution while we've got time. Oh, okay. Let's do the conflict resolution while we've got time. 33 81. Okay. Get merged master. And it's going to say conflict. Okay. And the one file that has the conflict is right there. Okay. So there's the middle of the conflict marker. Here's the start. This headline line right here, Meg. Do you see my screen? I do. Okay. Let's see. I think so. And the existing content is from, is components of distributed bills, which is that stuff that I added. Remember, I put all of this into security and it was too much. Okay. Good. So, so we want to keep both of them. Yeah. Okay. Good. Well, that's easy. Monitor and restart offline agents is right here. Uh-oh. Something just went funny just a minute. Yeah. Okay. So monitor and restart. Offline agents. So components of distributed builds probably belongs very early in the file, right? Right. That's what I want. I'm thinking that maybe should be before this. Great. Okay. So let's. Do that. Like this. Okay. Components of distributed builds. Yeah. Launch inbound agent by a window scheduler. Oh yeah, that's much more obscure than. Monitor and restart offline agents. Okay. Why did the indentation of that change? It should be level too. Yeah. Creating agents. Is it like a tab that got converted? Yeah. I think it's at the right spot. Okay. Now let's see how it looks. So it has the section components of distributed builds. Meg, this is the section you had added, right? Right. Okay. And then it keeps. Okay. And previously it was three levels in. It really was. So now the question is, is this. So creating agents is the level two head. Uh huh. Is, and then it's gotta launch inbound agents via windows scheduler. Another level two head. Monitor and restart that really should be at level two. This is a different thing. Okay. So that change is intentional. It's correct. Right. Oh, I think. So if we do a diff against the master branch. Okay. Okay. Oh, shame on us. Just a minute. Now I have to fix something. We have trailing white space. Oh dear. And I did that to you. Oh, my, my, my. Oh, it's easy to fix. Yes. Okay. So. Okay. Now we'll look at the diffs. Could we really quickly build it? I want to make sure something is going by. I had it. It looked like maybe that stuff that I put in there had gotten out of the way. That some of those components are being described after. But that's. Sorry. You say, say that again, Mac. I was reading, reading. Oh, I'm sorry. Um, could, could we run a make. Uh, Make and take a look at the format. It's going through quickly. I had something look like part of what I'd written. Got separated from the first part. Oh, okay. Good. This is a good thing to check then. It was six 58. You guys got to go. So. Here it is. Oh, well, no, maybe it's not, not yet. Patience, patience, patience. On one clock. We've got three minutes. So too. Okay. So. And this was documentation managing. And it is. Nodes. You're going right by managing notes down about. Two thirds of the way. Got it. Okay. Right there. Oh, it's got the work in progress. I think that. Well, let's look at see what we've got. Okay. Well, and we can take that out as well while we're here. Okay. So we're, okay. So we've got. Components of distributed builds. And then we've got Darren's creating agents. Launching an inbound agent. Yeah. And then monitor and restart offline agents. That's not bad. Okay. So. A couple of months ago, all we had was monitoring the, and restarting the offline. Well, and with components of distributed builds in there, I think we are perfectly justified in saying this is no longer work in progress. I agree. So let's. And Darren's between that and Darren's video. We've got pretty good content there actually. So let's edit that. Remember, I'm not any max. Okay. There we go. Okay. Okay. Okay. Okay. Okay. Is it time or ready to go on? I've got to end because I've got to get into the next session. That's right. I think it looks good though. I think it's close enough. Yeah. All right. I'll push. Thanks everybody. Okay. And going to merge later then. Yeah. After it passes. See you. Okay. Take care. Good meeting. Bye.