 Here we go. So good evening, good afternoon, good morning everybody. This is the Google summer of code office hour for September 8th. I always need to think about how to say dates in English. So we're reaching the end. So a very busy summer comes to the end. We're wrapping up. I think Google opened up the final review form for contributors. So we come back on that later. If the question, the big question is we're struggling to find an adequate date for the final presentation of everybody's work. So last week we were proposing to hold it on Tuesday, Tuesday evening or night in India. So the same time as now. Yeming came back to me to me and saying that, well, he was sitting in a class at exactly that time. So it didn't work for him. So question to the group of people who are present does Wednesday, same time work. So John Mark, Yeming responded to my slack and he said that he's currently in class, but let me try to join. Give me one minute. Okay, he will, he will try. He told me that the new proposal is go for him. He gave me his timetable. So I know when he's busy. So, okay, so let me call up the calendar. So we're currently aiming at Wednesday 21st, the same time as now. Who can't make it? Um, actually, I had my examinations from Thursday. So I don't know if I can make it on Wednesday because just a day before and either two in the evening. So slightly dicey for me. So this is very good. I can manage, but if it is possible, could you please try to shift it a day before or two days before or maybe after September, like October 30th? Okay, we have the difficult task of trying to mix water and oil. If you ever tried, you know that this is nearly impossible. So to summarize to Yeming who joined, thank you for joining. On Tuesday 19th, no need to check the dates. So on Tuesday 20th, it doesn't work for Yeming because he's in class. Wednesday doesn't work for Vian because he has exam exams to prepare for the next day. So we have three possibilities. The first one is that we keep the Tuesday and that Yeming records his presentation, which is would be sent. Second opportunity or possibility is we do it on Wednesday and then it's Vian that needs to record his presentation, which is also suboptimal. And so third option, we push it somewhere in October or even later. What is the opinion of the group? Maybe we already asked that, but what about the Friday before all that Friday 16th? Is there any exams or a problem on that date? I don't recall if I'm sorry if I if someone said that that wasn't possible, but Friday 16th, would that work for everybody? What is the status there? I need to cancel the meeting there. So I could make it, but on Friday I have my October first preparation meeting, but this could work. So who is going? You made a plus one thumbs up. Is that correct for Friday? Friday is good for you. Vian said on Wednesday, Vian wants me to be killed by my wife. Vian also said on Friday works for me. Okay, good. Hoshi Cash also Friday, and Yeming is Friday good for you. I don't have your your timetable. You can ask. Yeah, it's okay to me. We go on 16th Friday. Yep, that sounds like it. Adrienne, you clear the log jam. Bright idea. So I will find somebody else to take my place at the other meeting, but great. Okay, Alissa, your go to organize the job at that time? Yes, Friday the 16th. Same time. Same time as now. Yeah, got it. Okay. Great. I apologize for the misery of I apologize for the misery of oops, I have a feedback. I have one comment. And John Mark, feel free to kill me because my option of Friday is a no because I'm going out. I'll be taking a PTO. This is as important as Adrienne, you missed it. Okay. Yeah, so close and so far at the same time. Okay, sorry. I cannot cancel that as well. I've been preparing for one. No, this is here. We need to keep a balance between private life and work. So this is very important. Yeah. But what about on Thursday in place of this office hour next week? Yiming is in a class. He sneaked out of his classroom in order to join this call. So and I thank him for doing that here. We'll have to look for October and but the Friday for me is a no go in October because of Friday I have the October first office hour. This is going to be hard. Difficult. So John Mark, maybe we send the contributors a doodle for October. So we give them more options to choose from. So hopefully one of those days will work for everybody. Yeah, we'll shift it to October. The week of the 30th, Alyssa and myself are at DevOps world. We're traveling. So making Jenkins online meetup from an airport is looking for trouble. No, no, but here we're here together to brainstorm and challenge. I need to have a big reserve battery with me to be sure. And I know I'm don't know. I will not try here. I think we'll follow Alyssa's very good advice to send a doodle, classical doodle and try to find the time in October to do that. You will have more time to prepare it. Now if you have blockers, Yiming sent me when he had classes. So normally this Yiming, can you answer me if the class roster that you sent me is this valid for October to probably. Yeah, yeah, exactly. Okay. Got you. So I know there so we can adapt the doodle better for that. Here I'm awfully sorry for the mess, but you now have a very active schedule. All of you and we try to accommodate that, but I really would like to give you a chance to present what you did and also send a message to the next generation of GSOC contributors. Okay. Thank you very much for that. Yiming, are you able to participate to the call or do you want to go back to your class? I can go on because I think my class will end in five minutes. So I don't think my professor will give something new knowledge. Okay. Good. Very wisely said. Okay. Good. Then very quickly. So can you give us an update where you are for wrapping up what is in front of you and you have the open question of publishing your GitHub action in the GitHub marketplace. Can you give us quickly the status where you are? I think most of my works of this project are done yet except the exact publishing the actions in the GitHub marketplace. So I cannot decide whether or not it is acceptable to the organization. This is still a discussion ongoing. Mark, Mark Wait, who is part of the board, acknowledged the question. They only skimmed over a subject in the last meeting. He will handle that. I don't think that this is blocking you to complete your project if you continue that a little bit. Yeah, already submit the final evaluation. A general note for everybody, I hope that you will not disappear suddenly in the fourth dimension or what it's called. You will continue to hang around, continue to maintain what you produce and continue to participate to the community once GSOC is finished. So I'd be looking forward to continue to interact with you. Okay. Yiming, something important that you want to share about your project, I think you're ending. Don't forget to fill in your evaluation and pointers to the work you did. Okay. Chris, do you want to add something? No. Okay. Just for your information as you came after the fund, we ended up finding no compromise for the date of the online meetup. And so we kicked the ball out of the field and are going to look for something in October. And we're going to do it with a doodle. Okay, I see. So, okay. Deraj, same question. What is the current situation? Were you standing? What is still required to do? Are you wrapping up things in a good state? Go ahead. Yes. Thank you. So the status of project is I'm working on one task and it's like, as per our discussion in the weekly meeting, it's like the wrapping up tasks for the project. And I spent time on it to understand how to do it, but I could not get the idea of how to do it. But then I put up a PR and asked for help and Adrian suggested me like, gave me some hints like you can do this, you can do that. So I'll be reading them and understanding them and working only on them and just pushing the comments and try to wrap this task by tomorrow. That's the goal. Let's see. About what time? You're not going to work the whole night on it, Deraj? Since these are the last days, so I might need to work the night. So that's not a problem. Here, discuss it with Adrian about the priorities. You know my standpoint on that. I appreciate the effort and that you want to wrap it. So that's very, very good, but please don't do silly things in not sleeping at night. You're still young. Good. Go ahead. Yeah. So Adrian is also helping us by deploying the project and he's working with the infrared team to do that. So that is also on track. That's all. Okay. It's a very big project and it's really great to start seeing the results and shaping up. So that's great. Okay. You are able to fill in your report, your evaluation. Are there questions about the form? If you need help, just give a shout. Did you look at the form? Did you look at the form? I'm sorry, but I did not. But I will after this meeting for short. I promise. Have a look so that you know what are the questions that you need to fill in. Okay. Good. For sure. Thank you, Derash. Keep on trucking and don't roll out of the road. So I'll stop here. I'm a grandfather, so I need to take care. This said, Hushikesh, what does the situation look like on your side? So hello everyone. So finally the project has come to an end. This week we have discussed and the Git Client Plugins PR is ready to, you know, from a draft PR we have changed it to, you know, ready to review so it can be merged. And then the Git Client Plugin also the work has been completed, but we have to test it rigorously because many people depend on the Git Client Plugin. So sorry, on the Git Plugin. So that has to be tested, but the unit tests have been written for all of them. But still, you know, it has to be used on different machines to check how is it working, what are the performance, is it impacting any, you know, having any effect on the Jenkins software that has to be looked into. Other than that, I think all the requirements have been met. So yeah. And so you're slowly getting prepared to do your presentation. Yeah. Okay. One question I had, I wanted to ask on this now because so basically in the first presentation, like I did my presentation, but I couldn't add my presentation into the deck, that presentation deck where everyone's presentation is there. So I wasn't able to add it because I don't have the permission. So if you could add it or if I have the permission to add it, you know, it could be added. Yeah, good point. Now I'm looking at Alyssa, do you know where what the presentation is and how we can help Hoshikash to merge his slides? Oh, the presentation for, are you talking about for the one in October? Sorry, John Mark. No, the one that happened in the end of July. Oh, yes. Yes. So I can send it to Hoshikash. Yeah, okay. Or help him because he tried to add it to it. And I think he doesn't have the update rights or something like that. If I remember, there was a there was a message on on the on the community.jenkins.io where he said I'm running. Okay. Oh, okay. So let me let me add him right now. Thank you, Duras for the link. Okay. Now Hoshikash, it's important, but it's it's not an emergency right now. So focus on finishing and remind us next week or later if we if we still missed the target. Also, regarding the blog post, I was working on the blog post. I wasn't sure about what the requirements are like when I have to submit my year, you know, when I have to finalize the GSOC form, which I have to submit next week, because it starts for me and on the next week, right, because we both wanted by one day. Here, the the blog post is important, nice to have, but is not tied to a date. What I would like is that if possible, but it's not blocking, that the blog posts are published on the side at the same moment. And it could be good that they're published together with the John with the Java online meetup. So as we're moving to October, we have more time there. So this is my opinion on that. And Alissa, do you have a different opinion than mine? We don't want to post. So the blog post is I usually do it shortly after if we can within that same week as our Jenkins online meetup. So we don't want to do it way out too long, but we want to do shortly after because of people who have just heard about it, so then they can follow up on it quickly and the content is still fresh. So this confirms and gives more details to the proposal. So what I propose, unless somebody has another opinion, is that the target is end of months of September. But for the 30th, the pull request is ready to be merged. So reviewed and ready. We need to put a note on it. Alissa, when the blog posts get ready, don't merge without or but I don't want to put them in draft. Otherwise, there is no automation for the preview environment. Anyway, Hoshikash, does that answer your question? We don't need to go into the kitchen details, but end of September is a good detail. Oh, yeah, that answers my question. Yeah. Okay, good. Thank you for the update, Hoshikash. Well done. I'm for all, but I will keep repeating for all of you. I'm impressed what has been achieved in the nice results. Pihan, your turn. Hi, everyone. What is the situation on our side? What can you update us on? So most of my work is done. So the request was merged for the docs office hours last week and the changes are live on Jenkins.io. After that, I have just winded up my work on finishing off the tickets closing them as required and also briefly project page. And I feel the evaluation as the first draft now. So I should not feel the non-deployed fields. I'll do that when I have some more time on the weekend and I'll submit that. I submit it now just as a failsafe measure. Other than that, I have some more changes that I would like to propose, but that would be outside of GSoc. And I'm already working on that, not very major, but just to fix a couple of pages on that. So yeah, everything is pretty good, I guess. Nothing else to say. Okay, good. Did you already look at the evaluation form? Questions about that? Yes, I have submitted that. Oh, you already submitted. So until you reach the closure date for submitting it, you can still change it and revise it. So it's still open. It closes at the date. Hey, great. I'm going to do that when I have some more time. The non-deployed fields. Good. Great. Something to add, Fihan? No, nothing to my side. Okay, sounds great. Does somebody else have something other to share, discuss, raise, camera on? I see them shaking heads to say no. So I do the count, three, two, one, and I then wish you all a nice rest of the day and continue like that. Have fun. Cheers. Bye-bye, everybody. Bye-bye.