 Here we go. So, good night, good evening, good afternoon, good morning, everybody around the world. So welcome to this Google summer code office hour for today, September 1st, start of the autumn here in Europe. And we're going to first go around the different projects, and I have three announcements to do. So let's first listen to Vian. What's up on your side? What's happening on the project? What do you still have on your plate? And I hope you're slowly reaching the end. So Vian, go ahead. All right, so my last report is complete now. So I've added the tests that were remaining in the last office hours that is done. And my progress is merged a couple of days back, but it had one inconsistency that caused the site to crash, and it was reverted and I fixed that issue and now we're going to merge it again. And after that, we'll be able to see some results. And I've also added the configuration that I mentioned in the last office hours. So I've spent some time on figuring out a configuration. So those are basically like those for my project. And getting that done would show me the result, the actual result of the project. And that has given me some really nice results, which I'm quite happy by. So the multi branch plugin page that was four MB long has been reduced to 700 kbs, and so on, so on for other pages as well. So I've added some 35 to 40 configuration names in that, and we are able to see that result and the loading speeds are much faster now, as well. So that is done. And other than that, we are planning on aiming at one more particular plugin page, which is build steps from JSON, that is the ASCII doc. And we think it requires some special programming, it's hard-coded processing for itself, because that page in itself is quite unique. And if we're able to get it done before GSOC, it's very good because it's not a part of the sprint that we decided, but as far as the GSOC sprint goes, we are all set. Okay. This, that sounds, that sounds good. Okay. So maybe should have started with me. No problem. Okay, thank you for your summary. Well done. So Drash, your turn. Do you hear us? Yes. There you are. Go ahead. So update from my side. So what we did in the previous week was, in the previous to previous week, I created a PR based on a new probe, and in that I got some very helpful review comments. And then my mentor, Adrian, helped me to resolve those, all the comments by himself. So then I focused on understanding the changes that he has done, like how did he solve all those comments. So that was one of the things that I did. And then I was also thinking about like writing an integration test, but that took a little bit long time. It, it was delayed by like two days from my end, and I still could not do it. So there's like, I need to think more like how to write tests. And I discussed this with my mentor as well. And it's, you know, we can get better at it by doing it. There's something I need to work more on. And I am also started writing my blog post on my GSOG journey that which is going to be published on Jenkins.io. So that's, that's still in the progress right now. And what I plan to do next is to make the changes to one of the files that we have, it's called update center service file. And I need to take out some code and do some refactoring in order to make some sense. So Adrian has also created an issue on that, which I will be referring and working on it. And from a project perspective, what we are doing right now is, I mean, there's one more addition that I want to share is that we are also working on to updating the architecture diagram, which did not take much changes. So it's for Jake so that he can submit it for his presentation. And I personally also spend some time thinking about what exactly is happening. So I made a rough sketch for my just mind map. So we I don't necessarily need necessarily need to put it out there. But it just for also for my own understanding what exactly is happening. So that's all. Okay, great. So I see that you're making good progress. The project is taking shape. We knew that it was a big one. So it was a huge one we know there's still work to be done about about that. So I hope you will still stick around to help continue and contribute the same message to the others is not because Jesus is completed. We don't need you. It will be at a different different place. Thank you very much to rush for, and thank you for for starting about the blog post. Yes, thank you. Jenkins is home now like that. I like that. Here I should maybe have started with with that in the beginning so general announcements are. I'm meeting who she cash was not at the meeting now no problem. Discussed with his mentors, and to be more comfortable because he had exams at the start of the of the school wanted to have one more week to complete his work. He has now been done and acted so the paperwork is now a file so just for your information. The deadlines are so forth. So September 4. This is where you can start submitting your report and your your final so there's a set of questions that you need to fill in. The deadline is set the September 12. So you will receive the Google reminders for that only for who she cash this is shifted by one week. So it has time to complete. She's not there. So I don't need to tease him about there. We're planning, or I do so we would like to make when the submissions are completed to do an on Jenkins online meetup for you so that you can do the last presentation. They they wrap up the story of these three months of active work. And now it's a pity that we don't have a lot of people around the table, my suggestion, and going to send a post about that my suggestion is to do that Thursday. September 22. At about the same time. So, just one week before DevOps world. I see at least. I'm being worried. Just one week before. And if somebody has a problem for that time. Let me know we'll look for another date that proposal is to have the online meetup with the final presentations or September 22. I'm going to be traveling on that day. Okay, good. So you'll have to leave me the keys or yeah, and you will have to brief me. Okay, not how that how that goes. What is second. This is the, the Thursday before. I think beyond has a conflict on the 22nd as well. Okay, now. Can we do one one week before then. Yeah, that's much better. Yeah, it's much better as well and I think for Veehan it's the same. So it's better. Okay, I need to ask you mean and so. So that would be September 15. So it has to be on Thursday right. No, it doesn't have to. Because we have the habit of having the meeting there. You have another date. Well, otherwise I send a doodle when it fits people. My timing is as late as possible. Don't don't dare me don't dare me I'm going to do it three o'clock in the morning for you don't just teasing. How late this time or later. Oh, timing. I mean the dates date dates as late as possible. That's fine. Timing is perfect. This one. Since behind us exams from September 22nd before that any day works. Okay, otherwise we can shift it to October. Okay, Adrian is suggesting 19. That's Monday works for me. September 19 Adrian. Can I suggest on a Tuesday. Because Monday is just this. I know that will be much later in the day for everybody else but I think for if somebody from the US wants to join that's probably going to be early. It's just maybe like a Tuesday. Tuesday, 20. At the same time, although it's end of September that we changing time. So here, okay. Let's work on that idea. I'm going to post a message on conflict, not conference on this course to propose these dates and see if we can get. You seem to to indicate that you would like to have it as late as possible in September. Is that late enough for you or do you want later. About the timing. I'm very happy with this timing and for the dates. I think what Adrian is suggesting around 19, but that's Monday. So Tuesday would work. So 20. Okay, that's that's okay for you. Okay. Yes. And Vian said it was okay for him. But here I'm going to send a mail I'm not reading the chat so you have to. Okay 19. Yeah, okay. Sure. Here I'll propose I'll propose that and we settle later. It's just doing the presentation you had already a good, very successful try before of you before so just doing the same with additional, additional details stories. Good. This said, so online meetup with the online meetup. This is the deadline for having the blog posts. I've heard that rush started the blog posts. Now I know that the people in India have their the semester starting. But I propose that. Jean-Marc you propose the blog post when before or during or after. I prefer before. Well, we hold them and we publish them with the online meetup. So I propose a little bit after. And the reason is that so that we also can include the recording and it's also a follow up to the to the online meetup just to get a little bit more traction. Yeah, it will will get more traction very, very good very good idea. That's one drash you want to say something. Yes, so what was the conclusion about the timing will you be posting a poll on discord discourse. Not for the date where I propose for the date and time for the online meetup with the presentation and the blog post. We will publish it after so that we can include the recording of your presentation. Sure. So we're not going to publish before is, but it must be ready before so that we can. It stays as a draft request. Is that okay for you to rush you already worked a lot on it. It's just, I said Tuesday previously, but the Aden would be on PTO so maybe we can look for the date. No, no, it's fine. I'll join my phone. And I'll find a quiet place for that. I'll meet myself most of the time. Okay, thanks. Good. Thank you for for for that so that that's good will will will verify on the discourse. Sure. So we I thought that we could publish the blog post now. But here you have too much to wrap up now and things to complete so we'll get it prepared it must be done. As soon as the online meetup is done, and that Alyssa has done the necessary magic with the recordings. We can link that on the blog post. Okay, so these were my points. Is there something else that needs to be addressed or shared. And to ask one thing it is about updating the project page. So could you suggest some possible things that we can link on the project page as an end to the project to change the project page on Jenkins.io right. Yes. Okay, you just do a pull request on it. No, so basically asking what all can we include in that so for example the repository in which we made a change for the presentations that we made water can be linked on that page. Whatever you feel and your mentors feel useful for the people that want to know what you have done. So, just avoid put your credit card number on it. I think that's. No, but put yourself at the place or at a place of somebody coming so the biggest audience will be a people that would like to apply for next year's edition. And they want to see. What did you do what did you proceed produce and how did you work. So these are the traces. The other type of audience are people working on on Jenkins contributors and these and I want to have a better idea. It's like an interesting project, the good things have been done. I want to learn more I want to dig into it. So, where do I need to start. So these are the type of information you can should add on your project page, but discuss that also with your mentor. Okay, sounds good. But you know how to do it. Yeah. Yes, sure. I also think I also think we have samples from previous years right so we can use that as inspiration. Yeah, you look into the historical documentations, the previous years. Good point to listen. Other things, other points. I like to rush your suggestion there something like future aims. I like that. Yeah, he continues putting in a chat. I should read the chat. I'm not used to do two things at the same time. Yeah, okay, we're here to help you. Good point yeah. Good, good idea. Yeah. Okay, then I think we can wrap up for for today for tonight. All pretty rest of the day. Enjoy it. And talk to you next week then. And good work for completing your projects. Yes, indeed. Okay. Bye bye everybody. Bye everyone. Bye bye. Here we go.