 Here we go. So welcome to this August 24th GSOC office hour for this 2024 edition. Nice to see everybody here on the line. So big news of this week is that two members of the adventure requested to have a little bit more time to complete their project. So Vendit and Jakruti and it has been agreed by the whole team. So we'll have two projects that complete at the expected schedule. So I think it's next week. Now I don't have the dates should have written down them and the two others will complete their project on September 19. So a couple of weeks left to complete that. So that was the important news will keep unless somebody has a problem with that the public presentation of all the project for the 4th September 14th, because we have such a hard time to find a date that suits everybody. I'm looking at you harsh. So, does somebody have questions or comments about this rescheduling of two projects. Or are we good. I don't really have any comments as such, but I wanted to ask that in that case like we have got an email from chiefs of that will be that says that we have to submit our like they really want a kind of description of our work like what we did and how we did everything. So do we have to do when they ask us to like, I think they want us before the end of September to submit everything. So do we have to do it then or project dates. So check out the dates on your project. So because now it's not common to all projects. I remember 19th and the master of the dates currently is Chris. Chris drove the effort asking everybody and I think Chris very much we have done that. Do you have any additional information or pointers. So I think for jacuzzi is the 19th, but forward and it's one week after. Oh, because, like, because I stuck to like the recommendation of Google so so they want even number of weeks, instead of like our number of weeks. That's 26. Yeah, it's for stipulation distribution because like they're they're complaining like if you if you chose odd numbered weeks they might have some issues with it. Okay. Yeah, I don't know why but here on the other side. I think he said it after the 19th. He has no more time left or or she needs to start something new. So unless Google yells normally everything is set right Chris. Okay. So, to be 100% sure jacuzzi check in the description of your project. And there you have the different milestones and deadlines for your project. Okay, if you still have doubts or so reach out to Chris or to myself to clarify any doubts about that. A pro tip. Yeah, a pro tip. Ask Chris directly, because he's the master of deadlines. Okay, good. Thank you, everybody. So if you have doubts, problems or worries. Talk to your mentors in if it's more administrative. To the organ men's to exactly know this said, keeping an eye on on the watch. Let's see what is happening in a different project. If everything is going smoothly, or if difficulties are are rising or need to be to be tackled. Okay, you first on my screen. I don't know how you managed to do that probably by by joining earlier but here. Yeah, that's right. Okay, so, jacuzzi tell us what happened the week, the last week, and what is happening in the coming days. So, last weekend, I actually made a new book request that is I started working on a new pro that was to detect incremental build in the plug in. And about the previous task that I was working on the old ropes they are almost ready to merge they are just some last minute final touch ups left. So, this week, my main focus would be to come to get, I mean, and one has already reviewed it. So I just have to implement his suggestions and review whatever he's saying. And I hope I will be able to complete it by this week. This weekend I also have already my next plan for this weekend is to start on the next group because I have already discussed the approach with and one. So, that's, I have to say. And I want to share that you also bought some interesting books to help you be more stable and on on solid ground for some important concept in Java. Did you start already reading so it's the head first series of books. Yes, I try to read them as much as possible like at least one to pages at a time do the exercises like they have said in the book that you should do the exercise and think about it before looking for the answer. So I follow the approach. It is interesting like some things it kind of makes sense that okay this is why they had said me already. And because I told me this to follow I should have done it this way and that way. So yeah, that is it. That does help. But then sometimes I think it's okay so this program that it was very complex based on the examples they are showing and what is happening. So now at least I can, gosh, what is the difficulty level of the world that I'm doing. So now we also understand why Adrian wanted me to follow the sequence of the probe to work on because they're based on difficulty level and say, like for example I can say that okay I have to implement an abstract class so abstract class difficulty level one. And then next I had to do was abstract class difficulty level to maybe something like that yet adjusted. Okay, good. So I'm, I'm, I'm happy that you have these additional sources to, to better understand the game. You're playing. So, but you did not tell them that you were the one who recommended the books. So again, I'm saying that you were the one who recommended those books for me. I like the pictures of the book and the humor in it. Does somebody else know the, the head first series? I have, I have read some chapters. Okay, so, so you agree with me they're fun to read. They help me probably a little bit outdated or year 2000s style but they're good. Anyway, thank you very much for the update. I think you and all 12 are moving. So no problems there or we have a close eye on whatever could get us into difficulty. So walking through Bruno. Yeah, now it's harsh turn. Harsh, what's happening on your side. So, in my project, like what has happened is the blog related to the final blog of the project is completed and it's deployed on jenkins.io. I've also submitted my like last, like submission to Google about Google summer of code regarding the plugin. It is not like it is not totally completed yet. Some tests were not working and they were notoriously hard, but I, I, I thought that I would be extending the like program for a bit, but Mark suggested not to so we skip the idea. And sometimes, like I made them pass of course but it's not the best way to make this pass that's what I did I just, I just made them pass. You understand what I mean, and like, and, and it was some, some interactive testing was also left. So yeah, we'll have to like see what will happening what will be happening to the plugin after the project gets over, but officially the project is over from like from our side, I think it was starting to interfere with your, your studies right so there was, there was also we had to balance their various things, the various elements. Do you want to add something you're done. I could have managed an extended project to be honest because like it's kind of weird living it in between I just don't like like living things in between if we when we are so like I think 95 96% of the project was done like it was just some part of the project was which was not done. So it could have been given me a better like a wholesome experience a completed experience, but it is what it is. I'm going to make. I don't know the English word for it but I'm going to be not politically correct here and say, here, if you want to complete it afterwards, you're welcome to continue as an open source contributor and finish what you started when you have time at a different rhythm, the people you worked with Chris and mark will be around to help you. So, well, Google summer of code is a very good structure, but now that you have the momentum, you can, you can continue. I think the same. Like, it's just a different kind of joy seeing your work in production like it's just a different thing. So you have the full, the full story and also the kick when you know your piece is used by many people is now in production. Hey, well done. Okay, very, very good. Vendit, what is happening on your side? Yeah, we are extending the we are extending the program time coding time. So we are the we are working on the Gatsby part of things and I just raised the PR today about strappy strappy plus Gatsby blog. We still have to we still have to I have raised the PR but still needs to be reviewed. After that, I'll be working on implementing the singular pages with Gatsby, like the download page, the home page, but the main the main the main milestone is the blog section. If we complete that, all the other pages will be done in two, three days. And after that, since Jenkins.io is really vast, and it has changed it has it has changed from the point where I started porting things. So we have given ourselves two weeks plus more than more two weeks. So we can check that everything is ported or some things that are that was changed after I phoked that from Jenkins.io and started working on it. And some and also test if all the links and things are working. So because since it was more about on the user experience side, I don't think so if links don't work user experience would be good. So yeah, we'll be yeah, we'll be doing that testing since Jenkins.io has so many have so many pages. So we'll be manually checking for each link. If it's working on the on the browser and after that will be done with a finished product that are dropping replacement of Jenkins.io. Basically, there will be a big chunk in this basically the the reason I think Chris can extend on on that that we we need a ready completed product. So not this detail or that detail needs to be done. Otherwise, people will will not be happy. Yeah, here we would really like to to change it. Chris, do you want to add something and also ours? Go ahead. Before even this project, we're going to have a demo tonight. Yeah. Yeah. Yep. So and for harsh, I think so, I think so according to Mark, he thinks is like his face like satisfied with a progressive project, even though it's not completed entirely so we'll continue working on it later. I'm very happy with the project. So to watch both projects are doing great. Okay. Good. It's nice. Really nice to to hear. Thank you for the insight. Chris. Okay, good. Now the last one. I don't know how you managed to always be the last one. Go ahead. Tell us what happened. Block post. And another big thing is we got a chicken and egg problem again again. Right now the infrateem doesn't have the enough bandwidth for shifting from shifting the testing and updating of Docker Docker Docker compose files and images to Jenkins or Jenkins CI so and we need that in the documentation. So, and we don't expect they that they will get the bandwidth during the GSOC period. So, right now we have a tricky situation because we in for documentation we'll need the infrateem and infrateem will not be available this month. So we are hoping that infrateem will be able to merge it before HectoverFest because we want to get this repo merge before HectoverFest so we can integrate Hectover, apply this report my work in the HectoverFest too. It would be very helpful. Yes. I also wanted to be like a maintainer for HectoverFest. Okay. Sounds good. And you know what would be really great is that you're able to show and promote the sets of tutorials to would be GSOC candidates and that you all here around the table here can help explain and how to prepare how it works what is important and especially I like the expression but you can maybe explain in your own word what it means to build the Jenkins muscle so to get prepared and learn what it means. I try to explain maybe you're better than me to explain it but it's a long, long run and you're well placed to know that but you can eventually also on Gitter or other channels explain because now the young students are curious want to know. Good, Ashutosh, is there something you wanted to add? Yes. From now on I was thinking that I will be I will attend the infra team meetings too but Bruno said that it will be and not be enough. It will take time for them to get the bandwidth to integrate it. At least attending the infra team meeting will help you to understand what is going and just by listening you will learn a lot. If the time is still convenient for you a very good source of knowledge and so you will have this production vision that interests you. I hear good music here at the end of GSOC. You all four don't look the same as two months ago. I can definitely say that. I see different people and I'm happy and proud to see that evolution. Good. So I wanted to conclude but I already said it so don't hesitate if you have time to give a hand to the people that start to show up with questions. Let's continue. Let's do the final mile or some have a few other laps to run before we can say that. We'll keep the office hour open for a couple of weeks even after the first will have finished just to check and follow but slowly we will decrease a certain moment we will stop with the office hours to say that. Do you have any comments or if somebody wants to add a comment or clarify something here? I do want to say something though. Go ahead Chris. I just want to congratulate for completing projects. It's a great achievement. I'm proud of you. We will have either a beer or a cup of tea or whatever but we congratulate each other together. Indeed Chris, well done. I agree. Great achievement. Although Chris, we're not there yet otherwise they're going to sit back and so no. They still need to work very hard. They're reaching the end. Let's finish that. Okay, great. Leaving blank if somebody wants to ask or say something else. Go ahead Arsh. A lot of people are actually DMing me about GSOC on the Gator channel so I think we should be telling them not to directly message the contributors, maintainers and the mentors because it's just and when I cross message them they don't even reply so that's kind of a creepy experience to be honest. That's a very good point and a very good advice you're giving. One of the principles of open source and what we do here is to keep one-to-one conversation as low as possible because only two persons are benefitting from the conversation. Making it in the open makes it much more efficient for everybody. There's some subjects and some discussions that need to be one-to-one but these are very point-to-point. As a principle I personally don't take any one-on-one conversation and I advise you not to do that and to redirect the people either not accept the one-to-one discussion remember how you felt at the beginning it's very intimidating and so you think that you will not make a fool of yourself by asking directly a one-on-one question maybe get some head start from the others remember that so help that tell the people here don't be afraid we're there to help say it openly and stay kind but I think you know the music but it's very good observation you made harsh they're actually pretty scared about it they're either over-excited or over-scared about stuff because they are intimidated and the projects for GSAP 2024 are not released yet so they're thinking like what the hell am I going to do with this complete Jenkins and they want to learn plugin development and my project was all about plugin development and even if I want to teach them it is impossible because there's a lot of content and there's a lot of projects very true reflect on your experience and although I will not be directly involved anymore I'm interested to hear your experience and you sharing that experience so at least telling the people this is how you're going to feel and it's okay and this is how you prepare this is a methodology and this is something that also outside of GSAP is valuable so for you it's fresh remember how you felt four months ago or in October I remember the conversation I had with Jakruti after Hacktoberfest last year and as I said you're not the same as four months ago there's a huge distance you can be proud of that so share that experience with others so I think it might be a good idea like one of our last office hours that we only have our four GSAP contributors talk about what are their lessons learned tips and tricks for the new contributors I think that will help set the expectations, set the stage for our next year's event and I think that will help us as mentors and Oregon admins out a lot as well so we don't have to keep repeating the same thing over and over yeah maybe if mentors are also willing they can also share their experience there but here you as mentee this is you're talking to your peers so very good idea Lisa we're going to organize that so that it's hey good I'm two minutes over time I'm sorry about that so but interesting topics great to see you great to see a lot of smiling faces so go go go as I used to say it's not my word but somebody I know who says that and final stretch now final stretch let's show them what we can do okay have a nice rest of the day enjoy it and have fun bye bye