 Here we are. So, hello everybody. This is the GSOC 2023 office hour of today, July 27th. Welcome everybody. Here we have a limited audience today because it appears that either there are exams happening, which is predictable, but also power cuts that make it difficult for people to attend. So, I suggest that we do a quick roundup of the projects. We have two contributors here on board and then I have a couple of things I'd like to share with you and with the people that are going to listen to the recording. So, let's fly directly in. So, Arsh, tell us what happened last week. What is happening? What your worries are? So, like I was able to get the microphone to working interactively, but we have not really tested it interactively right now because we are busy on the tests part of both the milestones and the problem that we're facing right now is like because of the GitLab for J's design that the API is enforcing upon the plugin. We are not able to design the test properly and that's a major flaw that we are facing right now with the design that I've created for the plugin. So, like it is kind of blocking me right now and I'll have to discuss it more with Basil and Chris to see what I can do about it. So, yeah, like it will be discussed in the next project meet and other than this, like, yeah, everything is going fine. We'll get to it. Nice to hear that. Do you have just, you might have told me that. Do you have exams or school or whatever that's in the way? No. Everything, all my exams are over now. I'm quite free. Okay. And happily behind you. Are you waiting for the results? Okay, that is another subject. Okay, next one. Ashutosh, tell us you're now back to your university, if I remember well. So, tell us what happened. Yeah, so last week, last week was a little slow because I got stuck in an issue, but we have dealt with that issue for right now. So, this week was relatively good. So, Node.js and Python PRs had been merged and I also created a PR for removing the back script. So, our setup can work with Windows users too. It's working for me right now, but the PR is still open. So, it should be merged within this week. So, yes. Right. Okay, it looks good. Your semester started? Yes, my semester started, but it's not that hectic because it's just started. So, it's a slow in the beginning. Try at least to see the teacher once, so that when you go to the examiner, who is this Ashutosh? Never seen him. So, okay, don't see that. Great. Chris and Iranj, I'm going to start with you because your contributors couldn't make it to the meeting. Is there something you want to share about your project, starting with Chris? Okay. So, I think we have been making good progress for EventDit, but I still need to try some improvements, final touches on the previous one and I think that's about it. Okay. Duraj, is there something you would like to share? Yes, sure. So, in the recent meeting we had with Jagruti, we noticed that we suggested her to work on one bug that she's working on right now. She already put up a PR for that and we suggested her that let's just focus on this instead of also working on another PR that she has open for another PR. So, that's under review. She got really good comments from Adrienne and Antoine and that's all. I think we'll get it merged soon. That's all. She's doing great so far. Okay. Good. Thank you for the update, Duraj. So, well, we made the roundup in five minutes so we can be all proud of us. So, that's very good. So, now I'm going to take all the time. I'm sorry. Harsh, if you have still a second to stay. First thing is I am going to organize and I want to have a one-on-one chat with each contributor to see where we're standing and that we reach a positive end. I'm going to send a mail to each other but you have time to react first, come first served. I'm proposing two dates. Tuesday, August 2nd, between 1.30 p.m. and 9.30 p.m. Indian Standard Time and Wednesday, August 3rd, same times. So, 1.30 p.m. until 9.30 p.m. Just choose again. The second day is on Wednesday. Yes, correct. And if you tell me I can't make it, I'll propose other dates. So, Tuesday and Wednesday. Half an hour will be sufficient. First come, first served. So, if you already know, let me know. Immediately I'm going to send the mail in an hour. Also, I need to finish the meeting with Alisa. So, I'm not going to send mail while we have meeting together. But it is an important discussion. I'd like to have that one. I'm also going to organize a meeting with the mentors to see where we're standing. First point. The second point I wanted to make, I could have started with that, but it's harsh. It's short on time. I'll come back next week on that. The message is we had the midterm evaluation. It was hard work to reach that and required some tuning and everybody made it. GSOC is not finished yet. So, there's still work to be done. Stay focused. There are some of the contributors where improvement have been requested and so on. So, don't be distracted. It's important that you stay focused on the goals. One of the important thing I wanted to because I had some discussions with several people and this is one of the subjects I will have in a one-on-one. Don't forget that one of the goals of Google Summer of Code is to learn the open source way. It's not a professional internship. And an important thing is to learn autonomy. So, we're achieving results. We're achieving goals. We're building things and this was important for the first milestone. What we are expecting especially on the second part is autonomy. So, reflect on your work and the way you're dealing with things. So, don't wait to be told what to do. And you need to learn. I observe and this may be the drawback of that. I observe that mentors are very committed to make you succeed and spend a great amount of time doing that. And this is important as part of the mentorship. But the other reaction is I'm waiting to be told what I should do, how to do it. And this is a pitfall. So, be careful about that. So, when you have a problem or you want to ask a question or so, research for the answer. Do your homework on it. And when you're asking, explain clearly what you have tested, what you explored and give the details. A work relationship is you do what you're told to do. And generally, it should happen. So, this is open source. It's completely different. So, we want to make you grow in your autonomy. So, and this can be discussed with the mentors or with me or other admins to know it. But think about that. Just don't say, oh, it doesn't work. I don't know what to do. Explain the problem. What did you try? What is your theory? And so I said you start this spiral. And one thing is what might explain that I see a lot of people waiting to be told and getting into that work like. Well, you had a hard time to arrive up to here midterm. And you probably received your first paycheck. I hope and I'm going to check. Congratulations. Good. Have a beer or whatever on us. It's not a work relationship. So, autonomy. Just remember that. This is what I wanted to share. If there are questions or if people would like to discuss that, you can do it now or we can do it one-on-one and just remember that. We've done good work up to now and we're satisfied. We're only half. We're still in the middle of the stream. Okay. Leaving you might open now for questions, comments or clarification requests. If you want to have more than a half an hour, just ask for it. Okay. I'm good. So, Harsh, I hope I didn't take too much of your time. You're still okay. I made it very condensed. So I achieved my goal here. So thank you very much, everybody. Talk to you next week. If you can choose a time, let me know immediately. Otherwise, I'm going to send a mail and you can reply on that. You still have time to think about it. Okay. 14 minutes. Great. Bye-bye, everybody. You made it. Cheers. Bye. Thank you.