 Welcome everyone. This is the GitLab plug-in modernization project meeting. It's the 12th of May 2023. And thanks for being here. So items on the agenda that I had, progress on Harsh's exams, preparing for project project plan review and then harsh had asked a question questions from harsh availability of notes, and I'll put one more availability of meeting recordings, because I have not done the upload of the meeting recording yet. Any other topics you want to put on the agenda harsh. Not yet. I'll think during the meeting. We also had two preceding action items harsh to complete his author page, and complete the project and those are both done or project description page and those are both done as far as I could tell harsh is that correct. Yep. Good, we were the first by the way just so everybody's clear, ours was the first to get those two things done. Well done. Correct. Okay, so then let's take on the question your question harsh so could you ask your question again. What was it it was the meeting note were uploaded on the project page. Okay, so let's and so let's look at that so first things first let's find the project page and we'll put a link to it in. So the project page I think what you're referring to is this page. Is that correct. Yep. Good meeting notes right. Okay, so on the project page. Alright so and what what we've done in the past so this links for meetings just goes to the same page so I don't think that's what we want. What we I think we should do is update it. And let's just put an action item for me or for you harsh, whichever is fine. Update the project page to link to this Google Doc. Yeah, the meeting notes are actually there but I did not add it in the meeting tab. I think it's there. Go go back again because I think I saw it's there meeting document. There it is. All right, so we've got it. Okay, good. So we don't have any action item. Perfect. That's why he was confused, I guess, sorry about that. Well, and and I think it may be that this indicates this thing linking here indicates that we've misused the structure of this page slightly. And I'm not sure what that means in terms of our misuse of the structure of the page because there's office hours over here. But there isn't a link on the on this page section for for for links. All right, so we see on this page we've got abstract. Yep, we've got rationale and we've got implementation and we've got office hours, but oddly enough, we don't have links. And so I think we may need to do a little bit of structural work on this page to fit whatever it was the original page creator had envisioned, because this one. So links to the, I would, I would expect that one to link to the Google Doc, not to the to the to this to this bottom page or bottom section here. So harsh if it's okay this is sort of a documentation site structure question. I propose that I take the action on that one because I'm not sure I want to have you spend the time figuring out how to build the documentation site locally in order to test the changes. I'm already busy with my examinations. Oh, you say you are finished with your exams. I'm not. I am busy with my exam from okay good so so then let's leave it okay so mark wait to revise the project page. The reason for me to do it as well as this can help the other three projects know how to structure their pages for best success so to move to place the meeting notes link in the expected location. Chris are you okay with that. Yep. Okay, good. All right, so let's do that then. Good. Okay. So harsh did that answer your first question the availability of meeting notes on the project page. Yeah. Okay, so then the next one was meeting recordings and I believe in our last session we agreed that we would use community Jenkins.io. Are you is, did we agree on that I'm looking now to see if we've got notes that remind me of that immunity. No we didn't okay so I have a proposal then. So on the data channel. Oh is that where it was okay thank you harsh that that's great so. So the idea was place the recordings on a community page. And are you still okay with that harsh with that that being the idea. Okay. All right, very good. Okay so. And what we got then is one more action item, which is Mark wait upload create the community page and upload the recordings for the most recent two meetings. And the reason the reason I put that one on me and not on you harsh is because the upload the recordings requires permissions on the Jenkins YouTube account. And you don't have those permissions and probably wouldn't be granted them even if asked. Okay so. Does that answer our questions on meeting recordings. Okay, great. All right, the next topic was progress on your exams harsh how are you doing. I'm pretty fine. Don't worry about that. Regarding the project plan, how much details are you expecting in the project plan because I want to go all in. I'm literally like how what changes are going to be done in every class and how things are going to be executed I am. I think I want to write them so that we could, we could discuss the complete migration with a bird's eye view in 19 so what is the level of detailing that you would like. I think I mentioned, oh go ahead. Chris mentioned it should be like the project proposal that I gave to Google, but a better, better version and more detailed version of it. So what's your. I agree it's, I think we want even more detailed than the project proposal with you giving more thought to how you approach it. I like your phrasing birds eye view of the migration plan because I think that is that helps Chris and I and frame. See, okay, this is where harsh is going he's going to do this first and then this and then this and then this, and it helps helps you think about the incremental steps you will take along the way because now. Certainly we know that reality inevitably surprises us that's okay right we don't we don't give up in dismay when reality surprises us and something we didn't know comes arrives but your your ideas of I want to do this. Then this then this are really good things for for Chris and me and frame to be able to review and coach and encourage. Yeah. Now in terms of, of, I think I would think in our next session we do a, if it's good if that document is available before the meeting. I plan to make it before the meeting. That just helps Chris and me and frame do a review in advance so that we can come with questions to ask you questions and to have a conversation about what about this and what about that. So it has to be uploaded on the wiki page right that. No you can you could you could just do it as a Google Doc. Okay, that's fine. That's better. In fact, I find it easier for these kinds of back and forth conversations if we do it in a Google Doc that way you can you, we can make revisions you can even if you decide to allow us to revise it right at right there. Good. All right, so anything anything else on any other questions or topics on the preparing for the plug project plan review. Yeah, so after the project plan, like we discussed the project plan, the blog post has also like, I'll have to submit the blog post also right. So, what do I, is it fixed that I have to submit a blog post in the last week or like, can I submit it before that yeah I can submit before that. Yes, absolutely. So blog questions. I want to start contributing before hand before the coding phase actually begins, because I'll have to take a break for my examinations in the coding phase one so I have to cover that up in the community learning phase that's what I was thinking, and the related to the project plan I'll try to finish it as fast as possible after my exams get over. Good. And the for your exams that if I remember that's at least a week you would I outlined that in the, in the project proposal already so it will take a week off for exams. And that was during the sort of during the summertime during during the project to just call it that. Yeah, what it was one July 6 to around 13, like that. Very good. I don't really remember the date you have to put a particular proposal for that. Right, so roughly. That's that's more than more than fine just telling each other. Good. Okay. Now Chris had reminded me in a meeting in a separate meeting that there is an upcoming community bonding checklist. Yep. From the organization admins so Chris is that something we would review in, we could review in our main 19th session or what what do you recommend. I think, I think it should be ready by May 19. Great. Any other topics we should be sure we discussed today harsh are their topics that are on your mind. I'll discuss in the project plan is submitted so that we can discuss it all at one other than that I don't really have anything. Okay. All right. I think that covers everything we needed to do then I've got two action items Oh, and I guess really the re the biggest action item is harsh prepare for prepare the detailed the more detailed project plan. We'll have a discussion at the May 19 meeting. And then we'll do it during the project plan review next Friday. Yeah. Chris Chris anything else from you. No. All right then let's call it well done enjoy your Friday evening harsh. Thanks very much for joining and we'll good luck on your next exam on Sunday and we look forward to seeing seeing the ideas. And then we'll talk about your bird's eye view of the of the plan and then we'll talk further next Friday. Thank you. Thank you.