 So, good evening, good afternoon, good morning, everybody, and early morning for some of you. So this is the GSOC Global Office Hour. It is June 30th, 2022. And we're going to do a small roundup of the project and where we're standing. First thing is, I need to do this before so first thing I had a very interesting personal chat with all four contributors, very interesting, very pleasant. So I thank everybody for the time. It was very interesting for me. Second point is, I did not see updates from all projects. So the project page on Jenkins IO, I think I've seen an update from the plug-in health score for the meeting in the note page. So that's okay. They have been quite some updates on a Yemmings project. So just a reminder, check if your project page is up to date that everybody can find all necessary indications. If you have issues to update the project page, just ping me or ask your mentor. But sometimes updating Jenkins.io can be a little bit tricky, but don't forget to update that page. On the same page, I also sent a small mail to the various mentors asking just confirmation that all the goals of the bonding period were met. Now I'm convinced that they were met, but if the mentors could just check that they confirm that everything is rolling, but don't stay awake of that during the night. I consider that no answer is a positive answer. Okay. So these are the introductory notes. I plan to do now a roundup of the different projects to see where we're standing. And then we'll talk about the midterm evaluation online meetup presentation, have some discussions around that. Is there another topic that should be added to the agenda? Sounds good to me. Okay, let's roll. So projects roundtable, so usual questions, what were the important activities? Were there any reached milestones? Are there impediments or things that are preventing you or worrying you in the process of your development? Who wants to start? On my list, I have Diraj, so do you want to start, Diraj? Good afternoon, Diraj. I didn't say hello yet. Go ahead. Yes. Hi, everyone. So about updates from our project. So this week, we were able to do quite a lot. So for example, now our project can be built using dockers. So it has been completely dockerized. So PR for that has been merged. And the second big thing is that, all thanks to Adrian, he worked with Jenkins Infra team trying to set up a CI for our project. And that has also been resolved and merged in our project. So what that means is whenever you send a PR to the project, it's going to run a Jenkins pipeline, which constructs the application and checks whether the new addition of the code is actually a good one or not, and will produce the rebuild reports as well. So it's very cool. And all thanks to Adrian. So it builds the applications and then deploys it to a test environment? Did I understand that correctly? I don't think it deploys it. It just spins up the application and then runs one in a test that's written there. That's all. And that test is just checks whether we are able to reach the database container or not. That's all. So checks that are able to communicate with each other. So that has been written by Adrian. So big thanks to him. And other than that, the things that are in progress right now is one of the PR. It's like an enhancement PR. And I'm aiming to work on it and get it merged this week. And after that, there is another PR in line, which is also, it's a bug, actually. It's a bug reported by Adrian. So that might take, I think sometime it might be completed by next week's first half. And after that is where the fun begins. There's a very big issue that Adrian has created for me. And that requires me to think about the whole designing aspect of the probes. So that's going to be the fun one to work on. And it's going to take the major part of July for me. So that's how it looks like. Good. And then big issue from Adrian will be away for a couple of days, if I remember well. So are you all set where Jake is there anyway? But in the detail. So you're OK. You know what to do. You know where to go if you're stuck. Yes, totally. If nothing works, you just stand on your table and just yell help. And somebody will come in just a joke, but no, just go on the help channels. And if you're really stuck, you can come to me. But Jake is there to see that everything goes OK. So you're set. Moving along. Yes, so that's OK. Great. Jake, do you want to add something? No, I think the garage covered it well. We're making good progress. And as he said, the real fun will begin when we start working on the actual design of the the rules engine and the probes and things like that. So really looking forward to getting that started. And I think we're in a good spot as far as deadlines go and all that good stuff. So. Great, that sounds really good. Thank you for the update, Rosh and Jake. So next one in my list is Jenkins file runner action for GitHub. Yiming, tell us. Yeah, OK. So. Let me see. So last weekend, this weekend, I made a decision on which Jenkins file runner actions will be preserved and iterated in the future. So they are Jenkins container action and the Jenkins static image action. So and I also asked, I also developed some optimizations such as dependencies caching and pipeline log downloading service in these two actions. So although there are still obstacles in this project. But I think I think I need to stop. I need to stop them quickly. So later in this week and next week, I will update some content or descriptions in the Jenkins I.O. project page and repository page. So I think the progress is good. OK, good. I so you posted some questions and you proposed a review from the community on Jenkins.io. You had the first answer that was not really an answer. I've seen it was a second one. But I didn't read it. Did you have feedback from the community on what you did up to now? Oh, I didn't receive the email spotter in this course. I received the two feedbacks. Yeah, I read them carefully. OK, good. Then you're probably going to integrate them in. So you're good. Yeah, I'm good. OK, sounds good. Thank you for the update, Yeming. And next one in my list is Automatic GitCache maintenance. Oh, I see a message from Dhrash. Do you want to interrupt before we go to? Yes, yes, sure. So I forgot to mention one more thing that this week we shared our community survey with the whole community on Jenkins Dev mailing list. So purpose of the survey, purpose of the survey is to get their feedback and try to find out bits of the probes based on those feedbacks. So we have finally shared with the community and big thanks to Jake for working on the whole survey. It's really beautiful. So if you receive it, please feel it. That's all. Did you already publish it? Yes, he has an email. Yeah, Dhrash sent it out yesterday. And it's really just to get a general sense of where people's priorities are on the different areas of the probes. So that's good. OK, I need to look at it. So and I also want to give a feedback on Yeming's thing. But so things piling up here. But OK, good, good update. I added that to the note. If the notes are not correct, you can update them too. OK, thank you. Thank you very much for the update. So let's get back to automatic get cash maintenance. So this, Hora Cash. Oh, hi. Hi, everyone. So last week in this week, I worked on integrating, you know, the get maintenance on Jenkins. So now for get versions greater than or equal to 2.30, you can run all the maintenance tasks on the cash is present on the Jenkins controller. That is pre-set GC incremental repack lose objects and commit graph. These all have been added. I've even added log log. Like, you know, I've even added logging into the software. So whenever there are problems that whenever administrators face any problems, they can go through the logs. Next week, I'll be adding the get maintenance for get versions less than 2.30. So hold on. I did not write. So you have the first maintenance functions for what version? 2.30 get version 2.3.0. And so next week. You go on older version. Yeah, I'm just working on older versions of it. Okay. Okay. Good. Making good progress. Nothing special. Yeah. Good. Okay. Thank you very much for the update. So last one is a pipeline step. I'm going to go through the documentation. So this Vian. Hey, everyone. So last week, two of my full requests were merged. One for the Jenkins.io sidebar and another one for separate separating the declarative steps from the main class pipeline step. So those two are merged and then I created one more pull request to get the data type thing going for the parameters of the pipeline steps. So with that, now you'll be able to see that the types of the parameters are not present under the help content, but they are present right next to the heading itself. So I noticed that on a larger page, the size got reduced by a sixth, which is quite helpful. So that is not yet merged. We are still working on refining the logic flow. So, but the entire thing is working then. And the next thing that we have started is separating the plugin manager from the pipeline step documentation. And all that code is now being maintained inside the pipeline metadata user repository. So our plan with that is to maintain the entire plugin manager with that, and we will publish it as an artifact to work to Maven, which can be imported in any of the Jenkins projects, whichever require that as a dependency, and then we can use it. So the same will be done for the pipeline step docs. And so the big thing for here in this process will be releasing it as an artifact. So getting the first release done in this week and the next week would be the biggest goal for us. And you are configuring the Jenkins file and everything. So that is something that has to be done. What is the name of the artifacts just for the record or the new artifacts? It's, is that the... Should I read the link in the chat? Yeah, or add it in the notes. Oh, sorry, I'll do that. So I'll share the repository in which we are maintaining it. Yeah. And is that the one where you have discussions where the mechanism is not working smoothly or there's some issues? I've seen some questions from Christine about that. Are you stuck with that or are you moving? I think that is with the one on the plugin list, the Jenkins attire on which we had discussion with Tim and Mark. So we are actually holding that pull request for now because we think that the benefit compared to the amount of content that is increasing in that page is not really well balanced. So I think I move over that because it's not good to spend more time on it. And we will basically land back on it whenever we think that the other things are sorted out. Okay. And the meta-itals is actually just created, I think, five years ago. So all the code is outdated. And I have created the pull request today. It's a draft pull request. I'll just share the repository link. And once the artifact gets going, I'll share that too for the feedback and link. So maybe because I'm not quite sure how releasing it under the R.Jenkins CI group works because I don't have the credentials and I have this Christian. So I'll probably take some help in the docs office today from Mark. Okay. I'll review exactly where we're standing with that because Christine pinged me about that. I have a meeting with her on Monday. A general one-to-one meeting with her just to listen. And she raised that point. I will read the conversations in details. I'm going to go on Gitter and see if I can do something to help or at least get the right persons involved there. I also have a chat with Mark where we're standing. Sure. That would be helpful. Okay. Just give me the name of the artifact you're creating. Sure. I'll add it as a comment over there. I think you can supply it. Okay. So I'll probably give the artifact name as well. Well, this is good. Okay. This works. This is good. I'll update it afterwards. I'm not good at taking notes while talking. I apologize for that. It is quite tedious actually to be honest. The artifact name is just the repository. Yeah. Yeah. Yeah. Yeah. Right. Okay. No problem. So that's good. But there we need to keep an eye that this new dependency can be, can be released correctly. Yes. That is the main goal for next week. Okay. That sounds good. What's happening there? Did I remove one too many lines for it? Yeah. I don't know. I change. I'll do that after the meeting. Is there something to add about the projects? The several people are working on the document. So anyway, just. Resending the question. Anything to add about the projects. I hear you all busy making progress. I like that. So normally. The next milestone. Is that we have to supply with Google who is sponsoring a Google summer of code. For end of July, the 29th. We have an evaluation of where we're standing and. They want to have a formal. Reply for that. Now. If you go on the document. So I supply the link to the document that will be used for this evaluation. Now, as I said individually. These are general questions. It's not an exam. It's not. Something horrible. It's just to check that. The contact is established that you're doing work. And that's. Google can continue to. Provide you with a stipend. For your work during the summer. You can have a closer look on the document. So no worries about that milestone. But I'd like to have during the summer about that period as we discussed. Presentation. For the community and it will be in the form of an online meetup. Of what is the purpose and what you plan to do with your project. Where are we standing in the project? So are we at the beginning? Are we nearly done? And eventually a preliminary demo. Of if you have something to show already. Now this presentation would be. 15 minutes. No more. Your mentors can help. I don't think that you waste too much time. In preparing it. So. It doesn't work for, for this, but generally I count for the preparation. Of such. Presentation. About three times to four times the time of the presentation. So quarter of an hour. Put aside at least two hours. In these case because the shorter it is the more work. It is. You can count of my experience on that. So you need to be able to put about two hours side. And if you want to train yourself. To do a dry run of it. Do it with your. Mentor during one of your weekly meetings or I'm also available. To help you. If you feel uncomfortable for that, but here we're talking. We're talking about a couple of slides. So if you want to get together here in this meeting, it works quite well. Do it the same way, just a little bit more organized. A couple of slides so that you know. Where, where you're going. So don't. Be too worried. My initial proposal knowing that in India school. Doesn't start the 1st of September. Well, who are cash. No. I think it's Vian. Yes, I think we discussed about it. Yeah, Vian is, is a little bit. So he needs to start a school. So my proposition was to hold this presentation. The 21st of July. So to do it on Thursday. So first question. Is that okay for you? Is it, is it not too early? Or does somebody have an alternate alternate date. To propose so. Who has opinions on that. My college business started 27 July. So if everyone wishes, we can put it up slightly later also maybe on that coming Sunday, which I think is 24th. So 21st for you is okay. Yes, 21st also works for me. The thing is I'll be having exams during that time. So I'm not sure about it. The college hasn't released any dates yet. I remember that. Was not sure that I wrote it down. So you would not be available. It depends on the time of, you know, if it's in the evening for me, I think it would be fine. Yeah, but you also need to prepare your exams. Yeah, that is there. So. You would prefer after. So beginning August. I prefer it in July only. That's fine on 21st. I'm not sure, but even if it's on 21st, it should be somewhere in the evening because if I go to the college in morning, I can attend in the evening. Okay. We can eventually do the following. Is that I find it much more difficult to do it that way. Is that you provide me with a recording. That I could play because you're not available. At that moment I could play it. In, but somebody should be there to answer questions. From, from people. So if you give me a week's time, I can confirm the dates and, you know, and then get back to you if you don't mind. Okay, good. But 21st might work for you. Yeah. Yeah, it might work. Okay. Good. So we have the harm that voted. We have a holy cash. Drash would do 21st work for you. Time wise and content wise. I believe so content wise. I think it will work, but just to confirm. Since it's on Thursday and on next Thursday from that date would be 28th July. So that's not feasible, right? Because the college is starting. That's the reason, right? Yeah. We cash. Yeah. This is the reason. Okay. Sure. It's not a problem for you, right? Yeah, it's not. It's not a problem for me. 21 works. 21 works and what would be your preferred date? Preferred would be as late as possible. So. 21 works after that next week. Yeah. 21 works. Okay. Let's keep it that way. What is your opinion? I don't have any preference. So you can. You can, you can make it priorities for others. Because of my, my. The first day of my next semester will be at the end of August. August. Okay. So. So you mean your goal. So you. Okay. So. We go ahead. For the 21st of July. We keep. Okay. Bye bye Jake. Is there other questions about the content? Because it will be a month that you will be working and coding. Do you have worries about the content? Any. Duration of the presentation. Did you say 15 minutes? I think I missed that. 50. I plan 15 minutes. No, it's 10 minutes. It's okay. So in one hour. So make it between 10 and 15 minutes. And so in one hour. We'll have the four projects presented so that they. And give them the chance to the community to ask questions and. And so. 10 to 15 minutes. But okay. Yes, perfect. And the, the, the three points that you should answer there in the meeting notes. So what is the purpose and the plan of the project? So it's very important that you rephrase exactly. What is the purpose of your project? What, what, what is it about? People don't always read all the online documentation. So it's always better to explain them verbally. So where you are in the project. It's always good if you're halfway or you still solving problems or so. And it's always good if you have already. Some prototypes or if you have something to show. By sharing your screen. Is that clear? Yes, pretty much actually. Okay. You have doubts you have, you don't know exactly where, how, where you are in the project. So I'm just giving too many details. Discuss that with your mentor. And, or. Ping me directly. And we can have a little chat. About that. So, Alyssa, we're going to prepare the, the meetup for the 21st. Yeah. And so just to confirm that we are scheduling it at the same time. Yeah. Yeah. Okay, great. Okay, are there. Questions. Points announcements. To share. With a group. So let's conclude then. I see you're in the middle of it. You're making progress. I'm going to start to see interesting results coming out. So. Well done. Continue that way. And talk to you then next week. Thanks. And show your evening day. And talk to you next week. Bye everybody. Bye.