 So, here we are. Hello everybody. Welcome to this Google Summer of Code 2023 office hour. It is until tonight, the 29th of June. And today we'll make a very short project update. Try to keep it very short. We'll discuss about exact timing of next week's presentation, because Jack Ruthie has some timing constraints. We'll find a solution for that. And we'll and now we need to see that we don't slip too much and we stay in half an hour. There, Alyssa is going to walk us through the technical tricks and secrets of the meetup setup. Hi, Adrienne. This will already be a busy agenda for today. Is there another important topic we'll have to discuss today? We'll walk immediately and project status will keep it to two minutes per participant. That's super short. You can go a little bit further then. Everything's good. It's a catastrophe. But let's try to make it short. Harsh is on the top left of my screen. So, we'll start with him this time. Go ahead, Harsh. You're on mute. I've made the slide for my midterm. Yeah, you're hearing me, right? Yes. Yes. Yeah. So, I made the slide for my midterm presentation. I'm also I've also made an initial draft PR for my second milestone. I am trying to make it work interactively. It's not working right now. I'm also working on the test cases for both of the first milestone. Like, I'm adapting the test cases, the bugs which I was having in the first milestone test cases. And I'm also working on the second milestone test cases. So, that's the update related to the project. And other than this, I think like my examinations, like my intermediate examinations have shifted a day. So, I think I'll be able to give the live presentation on the midterm live presentation. So, yeah, that's also good news that I have for you guys. Even better. Don't forget to study your exams. So, long memory. Okay. Thank you for the update, Harsh, and wishing you success with all you're currently doing. Moving, Bruno is not talking. Next one is Vandeet. Hi, Vandeet. Tell us. Yeah, I solved, we solved many issues that we were facing last week, Chris and me. We fixed the redirecting of the pages that was not working previously. And I just raised a PR few hours before the meeting for the solutions page. And I have completed most of the interface linking that was giving me a hard time last week. So, yeah, that's what I did. Great. Ready or getting ready for your presentation? Yeah, absolutely. Okay, good. Ashutosh, you're the next one on my screen. So, go ahead. So, this week, I created scripts for starting Jenkins. So, first milestone, first milestone, both are, first milestones PR is still open. It will need some changes and hopefully get merged soon. So, content for the midterm presentation is almost complete. And I'm working on slides right now. They're getting reviewed. Then I'll rehearse for the midterm. From this week, most of the things will be related to midterm. Just going to add that Ashutosh already ran some demos of what he did during the office hour Asia. And there were some very positive comments on the work done up to now. So, thank you for the update. Last one this time, Chakruti, I don't know why you're on the bottom of my screen here. So, you're the last one. Go ahead. What's happening on your side? Chakruti, I will have to stop you. The sound is quite poor. I think for others too. Do you have a mic? A boom mic? Or is it integrated in your headphone? Yes, it is. Okay. So, let's try again. But it's picking up noise around you in the room. So, for the presentation of next week, either you kick your neighbor out of the room or maybe like a while. So, we need to look for the mic. I interrupted you. I'm sorry for that. So, can you start again? Okay. Did everybody understand what Chakruti said? No, I didn't get much. I had difficulties. I can try to explain a little bit if you want. Basically, we have... So, Chakruti last week, since last week, she finished a probe that is looking for a specific GitHub action workflow. And we had a similar probe in the past. And the idea is to deduplicate the codes that are shared between the two. And so, we asked Chakruti to redesign the class so that they share the same ancestry, a semiarchy, and so that we reduce the duplication, sorry. And that's what Chakruti has been working on. Doing so, it's... As per what she told us, it's something that is new to her. And so, she learned how to think about that kind of refactoring and how to think about class hierarchy in that regard. So, it was a bit of an architecture... It was less of an implementation and technical week. It was more about an architecture redesign week for Chakruti. Very, very good there. So, Chakruti, I'm sorry. I hope I didn't scare you away. But the sound was difficult. And thank you, Adrian, for having explained. Maybe the... Okay, we'll fix that afterwards. So, I lost the track of what I wanted to say. Just to reassure you, Jean-Marc, we plan to have a dry run of the presentation with Chakruti next Tuesday with other mentors on our weekly meeting. So, we will try to cover that kind of potential issues for the big day. Okay, great. Okay. So, no stress there. We plenty of time. Just... This is some friction. I'd like to understand what Chakruti will explain next week. So, just pointing that I had some troubles there. Good morning, Marc. Thank you for joining the call. So, we had the short roundup of the projects. Second topic is Chakruti said that there might be time constraints for next week's presentation because it will take an hour. Let's face it. Let's plan that. And it will put some people into trouble because it's quite late. Discuss the matter with Alyssa. So, she can open the meeting earlier. So, there's not really an issue. But we already announced everything. And so, it will be quite difficult or error-prone to start changing it to everybody. So, changing the time of the meeting is only a last resort option. So, we propose the following is that as apparently Chakruti has the biggest issue. I propose that she starts if she's not too intimidated by that. So, that she starts on time and can drop then whenever she has the problem. So, first question. Chakruti, is that a solution that will work for you that you would be the first one to present? That is welcome. The sound gets better. So, let's hope that it's still improved. So, I understood that it was a yes. So, and does it work for others? There were some approvals on the Gitter channel. Just want to make a full check. Harsh wants to say something. Go ahead. Like, I would like to be the second one because I have to study for my exams. Like, there's a very big difficult exam next day. So, I have to prepare for it. So, I'll just make the presentation, like give the presentation the second after Chakruti. And I'll leave the call after that. So, is it fine for you guys? Perfect. But for me as an organ man and I think nobody's objecting here. So, from the non verbal it's better than a video recorded in any case. So, but Harsh, if video recording is needed in order to let you do those exams, that is also an option, right? Don't be shy. If we would love to have you present live. I think a live presentation is much more interesting for others. But if it's going to jeopardize your examination, let's do it recorded. No, it's not. Like, I'll have, I'll be having the practical examination. So, I'll be learning before that only. But the thing is like the presentation is just a 15 minutes. Like, I was, I was unavailable because I was having the presentation in the middle of, mid of my examination. But as they have shifted, like I can manage like it, it is possible. And it's actually correct. Like the live presentations are much better for me. Like it feels kind of great. Now, one thing Harsh is I'm going to time box it because you and I are big talkers. So, I'm going to stop you after 10 minutes. So, be prepared for that. Okay. Thank you for making the effort and looking forward to see your presentation is, I think for Vandeet Shrutosh, it's okay. You want to say something, Vandeet? Go ahead. Yeah, I have my exam to end the next day. So, I will leave the meeting too. I can go last, I can go last, but I leave. But I leave. And I would like to go third, if that's possible. And it's okay. It's not fun. Just checking with a shooter. Are you okay for four? Sorry. You're good for that. Okay. So, we have a natural order there. I thank you very much for making the effort and find the solution for everybody. I really appreciate the mood and the way it's done. I'm really looking forward to hear all four of your presentation. Just a reminder, format is 10 minutes presentation. It's part of the exercise being able to convey the important things in 10 minutes and that people listening don't fall asleep with it. And then we'll have five minutes for Q&A and so on. This will make one hour. Are there other questions, general questions about the presentation? If not, I'm then going to ask and give the word to our Philharmonic conductor of Meetups. And Alissa is going to explain us how we're going to to test or what did we plan to do technically. I didn't prepare that part. That's okay. Thank you, John Mark. Mark, did you have something to say before I start? You're good? No, I was going to heckle John Mark about the use of the word Philharmonic in this group. He's pushing my education level, thinking that I actually recognize that word and know why it was used. Well done. I'm not that cultured. They continue, Alissa. Okay. All right. So I went into the slide deck and I will share it again here. Thank you, everybody. Everybody's done their part to add their slides. So I ask that the mentors please review if you haven't. I'm seeing a couple of comments from mentors already, but if you haven't reviewed it, please give it a review. So next Thursday, I will start the Zoom 30 minutes early. Well, I won't start it. I will join it and you can join as well. And the purpose for that is that we will do a quick run just to make sure to test your audio and visual because, you know, all it takes is a couple of seconds for us to lose that and then we would lose, you know, people would drop. So first thing is test before you join and then we will test again. Make sure that your audio and your visual works and then you can start sharing your slides. Well, actually, I will share the slide and then you just let me know when to move forward just to keep things clean. And then make sure that, you know, do a couple of tests run of your demos because we have seen where that doesn't work when we want it to work. So and it happens to the best of all of us, right, to everybody. But, you know, just do your due diligence and test it all out. Jean-Mar, did you have your hand raised? Yeah, I'm not good at these new technologies, so I'm mixing everything. Alyssa, am I wrong in thinking that for the meetup setup, we're going to send a dedicated link to the participants or do we keep it as a regular Zoom meeting like we have here? Yeah, it's just, well, if you, I think I added everybody on, it's on the calendar. The invite is on the calendar on the Jenkins.io events calendar. But I will also put it into the meeting minutes for today. I'll make sure to add that link there, but that's the link to join. Okay, it's specific for that webinar. Okay, and it's not a big room Zoom meeting. It's a webinar. So it can hold up to, I think it's 500 people, Marc. Yeah, okay, so you did create it as a webinar, not just as a Zoom meeting. Right. Excellent. Okay, good. So that means the threat to the rest of you of being interrupted by people who are, who are want to disrupt us or be annoyances is now zero. We have much better control. Thank you. We've, we've in the past gotten lucky and use Zoom meetings for our webinars, but we don't like to get lucky. And we don't like to rely on getting lucky multiple times. Thank you, Alyssa. That was, that was perfect. So I'm glad you did it as a webinar. Thanks very much. Yeah. So just to explain to everybody that's not aware of that, this is a special type of Zoom meetings where there are the organizers, Alyssa, for instance, and you would then part, you will be invited and the link there, and I don't know if it's individual or global, you will be there as panel members. If I remember, correct. Yeah, that's correct. So you will be able to speak and present. Yeah. All the rest of the audience is like in, in a meeting room will be sitting in their chairs in a supposed to keep quiet. The only way to ask questions is by typing the questions and Alyssa and myself will read them. Harsh has a question. Like Alyssa will just display the slides and like we will not have to control over our slides or something. Right. So I will, I will share the slide and I will move them along where you will be, where you will be sharing your screen is when you guys have your own demos to present. Then I will stop sharing. Yeah. So I cannot move the slides according to my way. I'll have to go through the flow that I have created. Okay. You have to ask, you know, something like next slide please or something like that. Yeah. So, you know, the deck that you had put your slides in. So whatever order you want it to move, do that now or right after this meeting. So then, then we just move according to what you have on that deck. Like I'll have to just ping you again and again to move the slide that that's kind of unprofessional. But you know, you just, you just say this next slide. And as part of your presentation, you just say next slide. Alyssa is very attentive. She'll hear you and advance the slide. It's actually a lot better to do that than it is for us to have change who's got the controls for each presenter. It's, it becomes very distracting and very probability, high probability of failure. You can even manage to introduce, to use next slide in your stories, telling, asking Alyssa and you can see in the next part and so on. So you can even, you can even have that request inside your, yeah, the queue in your, in your discussion. I agree. It's not, it's weird, but it's the best compromise we have. I have the slides in order. It's just like I have to ping her again and again to move to the next slide. That's, yeah, just say next slide. And we all do that. We all do that in our professional career. So it's, it's for us, it's normal. It's business as usual, how it happens. There were other comments or things. Oh, yeah. Go ahead. So I have added some minimal animations. So should I remove them? Because like, if Alyssa will be the one handling the slides, so removing the animations would be right because I added them according to how I would present. That's a limitation. Okay. I'll remove the animations that I want. That's what I wanted to make it clear. Alyssa, what is your point of view? Does it work or not? So they have text flying in and so? No, just appearing on click. Up there and on click. Oh, I saw that. Yeah. I tried y'all. Yeah, this is, it's error prone. So this is, so I know I use these technique quite a lot, but in this setup here, in believe me, switching presenters is something that costs at least one full minute. Yeah. And I was thinking of the, you know, the screen sharing because Alyssa will share the slides and from time to time, when it's demo time, when you're on the slide, we say it's demo time, you have to give the right to the other person to share a screen. And yes, one minute can go between the moment we decide we have to change the screen sharing. So. Yeah. And no, no where you're sharing and stop sharing button is because you will have to stop sharing and then you have, you know, then we have to give it to the next person, but just play, play around with it. Very important thing. I'll remove the animations. So very important thing. Don't worry. If you run into difficulties, you're not going to die because of that. It's, it's part also of the learning process. So don't start not sleeping because of that for a couple of days before. And it's just risk management and learning. And after it's done, you will reflect on that. How can I do it better? And so try the best. It's a given way of working. And let's enjoy it. I'm looking forward to see, I hear already good ideas, good thing. Be proud to show what you've done and you can be proud of that. So here, we were nearly at the conclusion of that. We don't do a test now, Alyssa. No, we're not ready. No, yeah, we will have time next week. So like I said, I will start 30 minutes early. So join me and then we can start testing things out. I think that's appropriate. We've done that in the next hour. Alyssa, I'm a little bit worried. So apparently Chakruti had some worries with time. So because people have other lives than GSOC or working. So we'll meet earlier than the start of the meeting. Is that going to be okay for everybody to connect half an hour earlier? So and it is okay. Ashutosh is okay. Harsh, okay. And Chakruti, if you're doing a thumbs up, I don't see it. Will it be okay for you? Okay, perfect. So we're all set. I think we covered all the subjects. I leave a couple of seconds if I forgot something important. Otherwise, I wish you not good luck, but all the best for your presentations, for your projects, for your exams, and looking forward to see you next week. Thank you very much, everybody. Bye-bye. Bye. Thank you. Thanks everyone.