 we're going. Welcome. It's the third of May. This is the Inclusive Naming Project with the Sheikot Africa Contributon. Thanks for being here. So topics that were on my list was how is the search proceeding for inclusive naming targets, for inclusive naming repositories that need fixes, and any questions that peace or Catherine have that we can answer to help you on your way. And now I need to bring up that sheet that we use to track this. It is right here. Okay, so here we've got the sheet and that's widening it out enough. Okay, good. All right. So I see Catherine, you've already submitted several poll requests. Thanks very much. So this is one where Kevin, Bruno, and I can now go do some reading to be sure that those are ready to be reviewed. Are you okay if we spend a little time reviewing them now, Catherine? Yeah, that's okay. Okay, great. And peace, it looks like likewise you've done the same thing here. You've submitted some poll requests that we could we could check today and review if that would be okay. Yes, it is. Okay, so let's let's take one of each and we're going to go through them. We'll use this excuse me as a way to as a way to talk about what the changes and why. Okay. Good. All right. So this one says create a job that just builds the oh no okay so this one piece this one is a good one for us to highlight in this case the word master here is a reference to to a branch name of a repository. So rather than the word controller, I would suggest you might choose to use the word primary or main. And the reason I use use one of those two is is that it's it's the branch name of what's being done inside the inside the what do you call it inside the the test itself so now we've got to look at the test and see what the test is actually doing so this is consumer dot a doc. Oh good okay so this is documentation thank you so what this says is I think what you want to do here is you want to change this so instead of being controller branch it should be primary or default branch and now let's let me look at the text more broadly just to be sure I've got to be see the whole context so we click here open this to view the file okay so master there's a interesting okay so piece let's let's look to see I'm going to go I'm going to switch and look at the SCM API's upstream and the file you were modifying was in docs consumer dot a doc right yeah okay then we have three references okay okay so there's this one create a job that builds the master branch create one job each for each of the sustaining branches okay so now now the question is yeah so this one should be changed but I would change it from master I think instead of master I would make it it and it looks like your pull request did not submit to the upstream repository it's submitted to your repository sorry go ahead piece say that again I said it's submitted to I fucked the repository so I did the pull request straight from the one I thought already and and that and doing the pull request from the fork is correct but the the the error that's happened and we may want to actually have you to make this change here the the error that's happened is it's offering to merge into master of your repository so it's offering to merge into your own repository and what you want to do is you want the pull request to target the upstream repository not your own repository so it's it's tough to show the picture of this what that means let's let's look at let's see maybe it's easiest if we if we do that this way so let's look at find that file docs consumer adoc and and what I'm going to do the same basically the same action you did is I edit the file now I look for the word master and okay this one says builds the main or primary branch now if we look for master again should branch so here we could say main I think is that it there were only two hits for master in this file I saw three earlier yeah me too I thought we had three and yet I don't see a third match okay we'll be able to test it so so here I've made the edit and now when I do okay use main rather than master as primary branch name and the reason is command line get is steadily moving to use more inclusive branch names okay so and this the steps that I'm showing so far are steps that you probably already took the crucial one is it's now going to offer to let me create a pull request and up here in the top right hand corner you see this base repository that's shown it says base repository let's see if I can pick it right there notice that it says Jenkins ci slash scm dash api dash plugin that's the place we want to send this pull request to because if I send it to my own repository the upstream maintainers will never see it so peace did that make does that make sense to you yes now if you're at a computer we could switch and have you screen share and we could guide you through making the change to switch where to do this if you're willing or would you be willing to do that experience or are you not okay so so while you're so you'll work on that independently are you okay if I then continue and we look at some others let's do some more reviews or would you like okay we can look at others why I'm looking for it okay sorry I'm not sure I understood so are you at a computer that you could share your screen so if you are that would be best for me we then let you go through this and let's get this one prepared okay I said that we can look at other plugins why I'm trying to switch on my PC because my PC the batch is low now oh okay got it okay so you're you're you're probably just on your phone so then it's it's great let's go ahead with switch to another one and we won't worry about your PC for now that's that's excellent so let's go with that so there are several here where the pull request was submitted to your repository so those but we can still review them and make comments there to be sure that you have the right content so let's do that good idea all right so yes this one's perfect so the one that I see on screen right now as we are probably running on a remote agent and controller call back to the controller yes that's that is correct so that one needs to be submitted to the upstream but it is a correct change okay then let's do that again with the credentials plug-in pull request and here okay so this one I'm going to say no not because yeah not because it's wrong because actually the word master in this case is not Italian so so someone someone who ever did this translation into Italian put an English word right in the middle of the Italian so don't correct local language versions unless you are a native speaker of that language and I am clearly not a native speaker of the of Italian just so we're clear I still had it down okay so good so we've reviewed we've reviewed three pull requests excellent work piece thanks for submitting the pull request that's great mark I want to ask something if you did something the other one you after reviewing it I said it was correct you submitted it again to you you submitted it to the upstream yes why was that like you sent it back to the Jenkins upstream so that I could see it right right so what you would do I think what you would do in your pull request is let's let's see if I can let's see if I can simulate the same thing just a minute I'm not sure I can but let's try it let's I think I'm going to try the same technique so let's get a copy of this one and I'm going to now go to my fork just like you went to yours okay so here I am I am now going to bring in the upstream so that I've got all the so I click this fetch upstream button and click fetch and merge so that I have everything that the upstream has that's an important button to remember don't forget to use this fetch upstream button regularly okay so now I'm going to look at the docs consumer.adoc and I'm going to edit this we had found that the word master was absolutely master okay so let's just do this one change for now so I'm going to change that and use more inclusive language more inclusive branch name the git project is using more inclusive names for their default branches in new releases tend to prefer main or other choice from the user rather than the prior previous master okay so and I'm going to create a new branch and this we're going to go ahead sorry just a silly question of mine are you cutting your comments up to about 80 characters I am yes good good question and the github user interface doesn't make that easy does it but yes I am no yeah because you've got the eye you know how to cut when it's the right time okay cool I guess the display will be better later on if you cut it up 80 characters or just a good habit to have well it's it's different it's that that when I'm editing a commit message that's actually going to get commit messages there are conventions and standards that the people who use command line get prefer and their preference is this first line should not exceed 50 characters and these other lines should not exceed 80 and it's just a preference but it makes it easier for people to read when they're looking at a git log command makes perfectly sense thank you do you know if a plugin for chrome or all the browsers would exist so that you don't have to count how many characters you should have you know that's a very good question there probably is I've never tried to find one but I think that's a good idea because this this text reflowing that I did is kind of boring right it's much much easier if if there was a something that would do that for me yes good and I don't know of one but but I bet there is considering how wide the the set of things are in the world but do that so good good point thank you all right so I'm going to save save this so I'm doing a commit to my branch named inclusive dash naming I'm still just getting to the point where you were pieced notice what it defaulted to it says okay and and this is what happened to you piece I think is it says oh I'm going to propose a pull request to my master branch from my inclusive naming branch and well that's not harmful if this was the place I wanted to go it's not the thing that I want and so I need to find a way to get this thing to open the pull request to the upstream how do I do that it may be that it may be that github's github is not going to allow me to do it and I'm going to have to just cancel here and do it from the command line or I'm going to have to I don't see anything in the UI here that would let me switch to I was hoping this little icon there would let me switch to look at other things but it doesn't seem to so piece you may be stuck doing this from the command line if you'd like I can show you how to do it from the command line as well yeah I'd love to okay so I'm going to this remember that we're at this point where we're on my fork of the SCM api and I was trying to create a pull request but because I started my edits in my fork it defaults to putting me murder proposing pull requests only to my fork so I'm going to bring up a terminal window and we're going to make the text in the terminal window easy enough to read so do I have SCM api already I don't so first things first I'm going to clone that repository so gh repo clone jankin ci slash scm dash api dash plugin okay so I just cloned the repository and now I'm going to do a gh repo fork and it will say oh hey this already exists would you like a remote I would there I have it now if I say get branch minus a or yeah so that tells me here is my branch inclusive naming so I'm going to do a get check out minus b inclusive naming minus t origin slash inclusive naming so what that says is create a local branch named inclusive dash naming that tracks the remote branch origin slash inclusive naming okay so now if I do this I do a get if I do a get log minus minus graph it will show me here is that commit I made whoops and here is the upstream master so I'm one commit beyond upstream master mark sorry to interrupt once more yes what would have happened if you hadn't used the minus t uh on the git command you know without the tracking what in what state would we have been I think we would have ended up in the same state with this here and this at the same location but if there were updates on the remote branch you wouldn't get them I might not have received those so that minus t says try to try to keep try to follow the remote branch when updates occur good question oh because I tend to forget the minus t but that's a tie and in most cases it's perfectly harmless right so back to back to Bruno's comment on 80 character lines I can now that I'm on my local linux computer I can use the formatting tools that I have here and now I fit very nicely okay so now we've got if we do the the graph if we do the get log you'll see here's my change this is equivalent to what piece did right it's okay I've got and we look at what the changes were it says create a job that builds the main or primary branch now to create the poll request I say gh pr create and it asked me what title do I want it defaults to using the title of the most recent commit so if you choose a good commit message you get a good title use more inclusive branch name is a fine choice and then it opens up and offers would you like to edit the poll request template that is provided with this repository and I like to use those because the template has been provided by the plug-in maintainer for the things they want us to us to answer before we submit a poll request so I hit the enter here and I then says on the body do you want to edit it or you want to skip and I want to edit it and here's what it says now this is a fun difference that Bruno's earlier question is is a good thing to highlight inclusive naming in the github poll request interface it actually prefers long lines and so in that interface I will typically delete all the new lines so that it has these huge long lines because they look better and then I go through the checklist and you remember how we did the checklist before I put an x to say that I did that yes I'm on a topic or feature branch poll request title represents what I wanted yep describe what you did yep I described what I did link to relevant issues there isn't a relevant issue so it's okay that I x that link to relevant poll requests there aren't any so it's okay ensure you have provided tests this one I'm not providing additional tests so to help the maintainer I put these two tilde characters at the front and at the back what that will do is that draws the line as a strike through so that they know I thought about this and I intentionally chose not to do it so I'm going to save that and now it offers should I submit I submit it and it'll tell me the url now when I open this url here is my poll request it says all the text that I described the check boxes and here are the changes so piece in order to make the transition what you'll need to do is you'll need to check out the branch locally and then use gh pr create as a way to create the poll request are you are you comfortable with that yes I am I understand okay thank you and and sorry for that surprise but thank you for being willing that's great I'm going to close this one because I don't think that this one is actually I would much rather piece that your poll request be submitted so I'm just going to go ahead and close this lad y pr o w e s s is that right piece yes it is okay very good excellent thank you and I'm I'm going to delete the branch so that it isn't even around good all right so that's that's a good step so we've got several of those Catherine I propose we look at yours if that's okay we've we've got another chance to look at more yeah sure we can go ahead with my okay so replace master with controller in java doc yes that's correct yes that's correct yes excellent okay and submitted to the upstream repository oh oh no interesting this this is a fun one Catherine okay because I thought this plugin was just an api plugin that was bundling other plugins but bundling other jar files but what you've shown us is that there is obviously code in the io dot jankins dot plugins that HTTP client I you showed me something I did not know thank you very much so so I thought usually so these plugins that have api in their name like this one does are typically used to package something else that is provided by another group so in this case Apache HTTP components and usually this is just a bundling activity that something gets bundled and included into Jenkins but it's an easier way to bundle it but in this case I was wrong it is that this thing is really providing some of its own code thank you yeah this is this is absolutely correct oh I have a question I think that Catherine did something to the master branch to her own master branch shouldn't we have another branch instead of master it may be just a detail but no no you're right very good point that we missed this checklist item yeah because it's easier for the maintainers if we submit from a branch that is not the master branch good good point thanks Bruno you're like so Catherine do you understand Bruno's point yeah I understand okay so what I needed to do here is create create my own branch instead of committing to the master branch right correct right exactly what if we hadn't approved the pull request and just created another branch from her master how would Catherine would get rid of what she did to the master branch can she revert what she hasn't or not she she she could get rid of it pretty easily it usually revert is usually not the preferred technique actually it's a good Bruno makes a very good point Catherine in terms of one of the reasons why we don't commit to the master branch is because we want the master branch in our fork to always be either equivalent to the upstream master or behind it we never want to get ahead of the upstream master because if we get ahead of it we will have conflicts when we conflicts or problems when we try to bring in changes from the upstream okay so yeah good good point Bruno so thank you now is is it correctable yes it's easily correctable um you probably won't do other changes in this repository I assume this was the only change you found needed to be made Catherine is that correct yes it's the only change and I made it through the UI I didn't need to to create a local branch good good and so so that means when you do that all you need to do is choose that checkbox that says create a new branch rather than going directly to the master branch when you do the commits to me yes right when you do the commit so when you do the the step that we did here on this one there was a a box that said would you like to commit to the master branch or would you like to create a new branch and I created a new branch named inclusive dash naming yeah so that's what you'd need to do as well but but for this I think it should be okay the maintainers should be able to accept it as is good thank you any any other comments for this particular pull request before we review our next pull request I don't okay next one then token macro plugin oh this is this is a good one because one of the maintainers of oh and it's already been merged I made the same mistake all right I'm glad because the maintainer Alex Earl that you see here was one of the original people who promoted and actively encouraged us to switch to more inclusive naming so I'm proud that he chose to do that oh and he made a change okay good yes okay great excellent okay so let's look at next durable task okay eight okay so eight changes so did you do this one locally then or did you do this one from the github ui Catherine yes I did this locally okay good excellent thank you all right so let's look at it okay and this one I think I think this one we have to retain because I believe that's the plugin identifier or or oh no okay this is a changelog okay I would propose a different slightly different renaming for for for grammatical for linguistic reasons so they they the previous changelog used the plugin id which is not well known to users and is unchanging is unchanging even for yeah for inclusive naming let's use the plugin name rather than the identifier and when I say that what I mean is on plugins dot jankins.io so if I search here for ssh-slaves it tells me the current preferred plugin name is ssh build agents so let's put that like that now Catherine are you comfortable with why I I dare to make that as a suggestion and now that makes sense though I have a question okay the ssh slave it also referred to other sections of this particular plugin and and it referred to how can I put it I think it was java code if I remember correctly so I was having a bit of a conflict with this good well and it seemed like a leader to change but then again you have the code issue right so let's let's look at those and let's let's talk through them I think you've you've presented places where a human being has to think about these these proposed changes and has to make a choice right so so let's let's keep looking so now did you did you you are those included in this or is that one that you didn't make a change for as a result yes I did I did not make a change okay all right well so then then let's finish this code review and we will okay so here in we usually use a lowercase letter lowercase rather than uppercase inside us inside the sentence because in this case it's not in in English grammar it's not a proper noun so we want to use a lowercase there this one got it right this one lowercase okay okay this one this one because it's in the palm file that's a plugin identifier and therefore we need to keep that one as it is it's also not displayed to users generally so that's an identifier now we should have seen that the build failed on this the CI build should have failed on this one so maybe we take a look at that in a little bit just to confirm okay and one of the one of the benefits of the CI jobs is if you inadvertently make a change to something that shouldn't be changed oftentimes it will fail the the build process because you made a change to something that that was to had to keep be kept in that name whoops right here okay good yes yes there you go you did the exact right thing slave agent should we call it slave slave slave slave slave agent no it's enough to just say agent good very good maybe it's the master agent no there's no such concept it's just agent well done okay and here we switched to the lowercase now one of the one of the the benefits of these review comments is Catherine you can then go in once i submit the review and you can accept the changes it's actually pretty easy to accept the changes so let's do a finished review i think i should request changes in general i i don't i usually just say approved minor change minor improvements all right now Catherine you you said there was a case where you had seen something that was not that you did not make a change to it yeah um just such for slave i will get it okay so so this one could be changed but it's just it's a comment inside the code uh oh oh interesting this is a little scary oh that's fun okay so what this is is a test so it won't be shown to users so it wouldn't have to change but the danger is i'm not sure that that's the right name because we stopped using that name for agent images a very long time ago so so this one wouldn't change as part of the inclusive naming project what this shows is this is some really outdated code so it should fail when building well no because the the image still exists the image with that old name still exists but it it's really really old at least i think this is really really old we'd have to look more detail so so that one is okay but it's okay for the for the wrong reason so should we find the issue do you know the name of the new image that replaces a slave image yeah i would have to go do some research to find what thing would fit here because that i think this should now be the ssh-agent and it uses a different numbering scheme as well if i remember right for release numbers so okay we'll have to it will it will need some more looking the last time it has been updated was two years ago say that that makes sense right all right so so any questions so far so katherine did we detect the case that you were worried about in that search or did i miss it yes we did actually um okay yeah we did all right okay so we've completed the review of that one now let's go back to okay there's there's another one that uh i wanted clarification on if you could go back to the sheet the git plugin ah very excellent choice finding finding something that causes mark weight personal guilt i like that yep um you just pulled back up we're made um yeah the one that says this is a fourth uh plugin yeah right okay yeah so when i was trying to create a local copy um i was having issues with um with with aligning with uh with trying to fork it to my own github because as you can see the git plugin seems to have been forked from hadson correct good okay yeah so i was having issues trying to clone and forked from my local and now when you when you did the clone and fork was were you doing that from the gh command line or were you were you doing that from the github interface from the web okay so let's do that from gh if that's okay then okay so so and and because this may not match with with your experience because i've already got a fork of the git plugin that i can't delete but we're going to go ahead and do it from here for right now anyway so first thing was gh repo clone jankin ci slash git dash plugin is do you remember is this did you use a gh repo clone to get your initial copy yes okay good so let's do that and then i'm going to cd to git plugin and now i'm going to say gh repo fork and it's going to present a question i think yeah so and is this the question presented to you as well yes okay good all right thank you that's good i like that all right so so what that means is now i have to use the air the up and down arrow keys to choose which is the base repository and so i'm going to choose jankin ci git plugin and it says okay that exists would you like to add a remote yes remote oh okay oh that's cool so what you found is a bug in gh yeah so so so now what you need to do Catherine is submit a bug report to gh your gh is an open source project and they would be i'm sure more than happy to have your bug report what you need to do is describe the exact sequence of steps we'll have this on video so you can even if you want point them to the video recording of this exact point in the video recording and say look you can watch mark weight fail in this way i'll not do that but hey i i think it's quite persuasive when you can say look i failed this way and here's somebody else who failed this way and here's a video of them failing i mean the developers who see the bug report may say oh it's already a known bug or whatever yeah that's that's fine or or they may actually smile and say well why didn't you why didn't the jankin's project break that fork and then you smile back at them and say because it's hard work we have to beg your support people to do it for us okay okay all right so so now how do you want to know how to resolve this how to fix this problem yes okay so get remote minus v so it has origin and it has upstream so that's good and it's got the wrong upstream oh my six okay this is where got stuck actually and and well you should get stuck that's that's that's so completely wrong as to be dismaying how wrong that is all right so get remote so so what what gh did is apparently gh said oh you asked to clone a repository that has a fork therefore i'm going to give you the the clone and i'm going to give you the upstream automatically and so what we have to do is we need to fix this by first we're going to get remote rm upstream because we don't want that upstream at all that's the wrong upstream so we don't want it and then the thing that is our upstream is actually misnamed right now it's called origin so we're going to do a get remote rename origin upstream i think it's rename we'll see if it likes that now when i do a get remote minus v it says i've got a thing called upstream this now are you okay if i do an experiment just to try something that's okay i'm i'm gonna go back one step i'm gonna get remote rename upstream back to origin okay so now what do i have i have something that says origin is named this i'm gonna try to use gh repo fork now okay so in your bug report to the gh project you can also tell them and here's a workaround the workaround is changed to the repository directory and delete the upstream that gh mistakenly created and and they'll probably say hey that wasn't a mistake and we did it intentionally and i'm okay with that but but you're now giving them a workaround and other people who encounter the same problem particularly fatal remote upstream already exists that you put in your bug report we'll find with google search fatal remote upstream already exists and be able to see your workaround okay so did that did that answer the question yeah that did that did thank you good all right okay that was that was fun by the way thank you and now now you're reminding me i really do need to go ask them to delete this yes go ahead question please go ahead okay um i saw the method that was used just now to fetch that upstream to clone the repository is there any other method there is one yeah in fact the other one is the one i commonly use so so the other method of cloning the upstream repository is to use command line get directly and so that would be with get clone usually even when i'm cloning an upstream i'll use hdbs github.com jankinci get-plugin.get so now that i've done that when i cd to get get plugin if i do a gh repo fork it will ask me the same question which is the base repository i say jankinci would you like to add the remote yes and there it worked so because i did get clone instead of doing gh repo clone it didn't get clone doesn't know anything about github's concept of upstream and downstream so it just cloned the repository so yes get clone is another way to do it and in this case would not exercise that bug or that feature of gh did that answer your question piece yes yes excellent okay good very good thank you all right so are we ready to go on to review some more poll requests yeah just a heads up before we move on there is one plugin i i mentioned that that it doesn't have a github repo oh which one is that okay the ace editor yeah the ace editor oh interesting okay so that may indicate something's wrong with things because it certainly should have a so you're saying oh it does not cool wow oh now that's cool okay so there isn't a link here to the github edit to the github repository and yet i am quite confident that there is a github repository notice the how long ago it was last released it was eight years ago and so now the question is oh oh ah look all right this is somewhat exotic and sorry about something exotic like this it says here this is the ace editor module bundle c jenkins j s modules oh no i don't know i'm i'm not okay let's are you okay if we spend a little bit of time looking for this because something that was last released six years ago may well have many uses of master in it yeah sure okay so let's let's go looking let's see if we can find this thing all right so ace editor is the name of it okay so my first hunch is there is a jenkins repository named ace editor so i'm going to go searching for repositories ace okay there it is now it's not called ace editor i think that's it let's check it to see it's called jenkins ace it is now read only okay so we can't release a new thing from a read-only repository so we have four kids yeah yeah but where but but if we needed to do a release because there was a bug seems like there has to be and this is certainly a currently shipping plug-in so i'm i'm suspicious this may not be the thing we want so so i have to give you extra points catherine for finding an interesting problem that is probably going to need some more research to figure out what's going on so let's see what else we might where else we might find it okay so ace editor here bundle id jenkins workflow editor for okay so where is interesting okay so let's go look at the open issues in jira maybe okay the component here is called j s dash modules so there's the component so let's try j s dash modules as this thing so jenkins j s modules and do we have such a thing in jenkins ci okay so we do and it's not archived would it mean that it's the ace editor is now part of the j s modules that's my guess and and we should be able to we should be able to find that by looking for ace editor here now this is a fork and so it may tell me it's not indexed yeah okay so it's it's not written that it's not indexed it is not and yet let's go looking just to make some more wild guesses here okay come on come on okay here we are j s modules and module bundle jenkins modules i don't see it there okay i'm going to i'm going to fork and clone i'm going to clone this thing so that we can look at it locally because i truly don't know this this has me perplexed so get clone that thing get grep ace editor if this defines it nope so that's not it so Catherine i think we're just going to have to do some separate research to figure out where is the source code to ace editor okay i'm sure someone knows where it is but i don't okay good discovery good good good discovery let me put a note here mark wait to research where the source code is the source code location yeah very good excellent any other questions before we close we're almost out of time time here yes um mark please i want you to help me for something help us do something like um can you show us how to um comment on different um this thing what can we um can you show us how to drop different comment on different um file sure so comments in terms of comments on poll requests yes on poll requests you bet okay so so we just did that i don't mean locally i mean directly from the directly from the um gift of repository so using the web pages how to comment on a poll request did i understand your question piece i mean the gift of repository directly for me it's not i'm cloning it locally like directly using the gift of repository is there a way we can comment on multiple make multiple changes at the same time and then create one poll request for them ah i i suspect there may be a way to do that i just don't i am not i'm not confident that i can show you how um because i'd need to do some more research i've never successfully done a multi-file change from the github web page using a single using using everything from github but but now just to just to tell you that i believe it's possible let me show you a poll request where i think someone else did it so in jenkins.io there's a poll request here that was just merged yesterday that is the ci cd with postman in jenkins blog post this blog post was done by this user andy dash get postman and notice that the comment says add files via upload so i think this is a multi-file poll request that was created by this user andy dash andy dash postman or andy dash get postman from the github web ui because i would never put a comment on on my commits of files that says add files via upload i suspect that is a github edition so i think it must be possible but it may have to wait to show it for another session so i can learn how to do it would that be okay peace if we did it in another session yes it's real because i feel that would be much more easier when there are multiple comments to make on a particular repository good good point for these kind of text changes why not so let's let's plan for that is it okay if it waits a week or do you want to do you want us to to meet again sooner than that so that you can see it sooner yes if there is a way we can meet sooner okay so what if let's look for a time that would work for us what if we were to try to meet well what how would tomorrow at the same time work for you would that would that work for you okay peace if we did it tomorrow it's real it's real because i'm really interested in learning this particular set okay so let's plan for another meeting tomorrow at this same time i'm going to stop sharing my screen so i can check my business calendar so just a minute let me double check that i'm not promising to attend the meeting that my business schedule won't allow me to attend okay so if we meet tomorrow sorry i saw you changed that time to 8 p.m oh i did when did i change the time to 8 p.m oh dear i saw like you changed on the calendar oh maybe and if i did that would not be a very good thing so next week i've got us at 4 p.m utc and the following so i don't think i shifted them but but what i was going to do is i was going to schedule a session for tomorrow at this exact same time would that be okay for you katherine as well yeah that's okay and and katherine you don't actually have to attend if you're if you don't wish to there's no no in fact i need to make us start 30 minutes later and we'll limit ourselves to 30 minutes because i've got a colliding meeting tomorrow but what i'll do is i'll i'll create a i'm gonna actually adjust this well yeah i'll get us a meeting scheduled for tomorrow at the same time time plus 30 minutes so that we can go through it would that be all right that's okay with me yes great all right thank you to both of you so i'm going to go ahead and stop the recording