 Welcome. It's the 20th of July. This is Google Summer of Code. Get cash maintenance. Ruchikesh, what topics would you like to go over? I know we've got upcoming the presentation that you'll be doing, looking forward to that. Do you want to review your slides with us? Would you like to talk about your demo? Do you want to test drive your demo? Are there other things? I just wanted to talk about the slides, like what I have made and what exactly is important because I've made a very big presentation. So should I cut short it or how do we do that? That was great. There was another concern. So basically from August 1st week, I have my exams up here. So you will be unavailable during that period? Yeah, but then I've received a mail from Google that if you're busy in the middle of the coding phase for a week or so, you can extend your GSOC period towards the end for a week. Oh, I didn't know about that. Now is that your preference? Because my assumption was their expectation is you'll spend about 175 hours total. Yeah. And if you take a week for exams, so long as you spend the 175 hours across the project, we don't have to change the schedule. If you feel a need to change the schedule, I'm fully supportive of that. But the goal is be sure that you've done the effort that you intended and spent the time that they mandated. So I'm okay if I can certainly ask our org admins if they're willing to allow us to extend, particularly if Google will allow the option. That was something I was considering. If first you were in the middle, I don't need it sometimes. So that's an option, right, is what I wanted to ask. Yes, absolutely. If Google allows it, I have no problem allowing it. Absolutely, I'd be happy to do it. Okay, because they were like you had to ask your mentor. Now, the scheduled end is sometime in September, right? And this wouldn't change it. It would still be in September because the last week of September, I'm in Orlando, Florida for DevOps World. And so that would be a difficult time for me because I'll be very busy. And shortly after that, I'm going to take two weeks of vacation to go with my wife on a special trip. I think it would be in September. And so long as we don't spill into October, no problem for me then. That's great. Full support. Yeah, that was one thing I wanted to do. Also regarding the second phase, like when do we start about it? Do we start over like, you know, implementing the things from next week itself or how are we going to proceed? And that was what I thought. If you'd be okay with that, I think next week is a great time to begin the second phase. You'll have done your presentation. You'll have been able to, the presentation is also a chance for you to organize your thoughts, right? It helps you think about, hey, we've done this, we've learned these things. Here are the things that we've found are important. These are the things that we made mistakes on when we did the initial thinking. We're going to go better now and we're going to lay out now the plans for our next, and I think starting next week would be great. The presentation actually helped me revise everything. What you did, you do some very serious things. At least I do. When I'm creating a presentation, I do some very serious thinking about how should I explain this and the act of explaining it makes things much clearer for me. Yeah, that means I need to do this. You know, I forgot about that and while preparing the presentation, I was reminded of this thing has to happen and this thing and yeah, very good. That's great. Now I understand the project even better because I had to explain it to others. Right, right. Okay, it's, now wait a sec. Why is it that because it works? It does. Absolutely. Yes, yeah. So did you, you had mentioned your slides. Do you want to share your slides or are there other topics before we do your slides because if there are other topics that are on your mind, let's be sure we get them as well. No, there's nothing, nothing, no other topics. Like most of them are related to, you know, the next phase of scoring. So I think yeah, very good to go. I think, can I share my screen? Yes, yes. I think, well, let me, let's see, maybe I haven't allowed it. Sometimes I forget to grant permissions just a minute. See if I can find the security thing. Yes, you should be able to share your screen. So on the bottom menu, there should be a share screen button. Okay, and then yeah. Oh, one minute. So, can you see my screen? I can see it just great. Looks wonderful. Okay, so this is how this is the theme of, you know, how I'm going to start my presentation. First would be, you know, the intro page. Then I will talk about myself. I was, you know, glad to see a Jenkins art logo about Hyderabad. Okay, I am from Hyderabad. Yes, the Hyderabad. That's the Hyderabad Jenkins area meetup logo. I know that logo. You know, I stay very close to this building. So yeah. I'm going to, you know, the second page is about introduction. So I'm going to introduce myself. This was, this is like, you know, a gender of what, what am I going to talk about? And this, this is a general overview of how it works internally. So because I was not sure like if everyone knows how things work internally, so I thought I'll give a basic overview. And about caches, okay, how exactly caches works on the Jenkins controller. You know, a basic overview, like what, what are caches, what are the disadvantages of caches on Jenkins. Okay, then this brings us to get maintenance, which was introduced in version 2.3. So I'll be, should I explain each one of them was what was my concern, because I made slides regarding all of them here so I wouldn't just because merely the fact that you're saying these things exist is already enough and and you're probably at this point already one or two minutes into your presentation. And, and so let's let's see first because I think you still plan on a demonstration right you're not just. So I would not meant I would not describe what each one is, unless there's one where you say this one is so crucial for instance for me, garbage collection. I would have been astonished at times when I discovered a, a, an unoptimized repository, and how much faster it was after we optimized it. But, but even that, it may not be because most people will probably know oh yes garbage collection collects garbage. Yeah, so, so, so do I like skip all of these slides I think it would take a lot of time explaining all of them so. I would think you would skip them. And maybe you put them. I would like to see how it feels to you as you go forward because for me, I wouldn't, I don't think your audience cares as much about the details of each, each maintenance tasks as, hey, how are you approaching it what's the, what's the experience going to be for the user and what were the design problems you encountered and what are the complexities you found this piece they can learn they could go study the get maintenance command and they could learn that for themselves whereas your project is something they can only hear from you. So then I think I will skip these these things that explanation for all of these. Okay, and then we have the demonstration. So, yeah. And then this was this is a simple, you know, high level overview of the architecture. Good. Yes, so, so I assume your demonstration will already probably be three to five minutes talking about, hey, watch here I'm going to we're going to show you this debris filled repository that starts with. I'm going to schedule it and then and while while you've scheduled it you're probably going to talk about it and you made that maybe the place actually where you might bring back one of those slides and say hey, while this garbage collection is happening. Let's talk about what garbage collection is. And maybe that's the place where you insert because you need you may need filler. This runs right it's, it's not a it's not a zero time process this is not a super fast process on large repos even so, so there is your maybe your place where you can say, yeah let's talk about what GC is here's this slide that talks about it. Remember, the process is running now I'm talking to this slide because you need we need to, I want to have something yeah. Do you understand what I'm saying. Yeah, yeah, yeah. Okay. I thought I'll display the comment graph command because that that is going to have that is actually a very beneficial maintenance task, and I can even display the performance gained using a comment graph. So that was something I thought I'll talk about. So this was so this is a high level overview about architecture. And these are the challenges encounters. Yeah, and the next phase of like what I am going to talk about, and yeah, that's it. I, I think your presentation is spectacular. That's you hit exactly the right topics well done. And you've got relatively few slides, and they've got interesting imagery on them. I'm impressed once again by somebody using Canva you're the second person in about 10 days that's shown and shown me something in Canva and wow that's really quite elegant it you look like a graphic design professional Russia cash well done. So, yeah, I spent my entire weekend doing this, I am my mom okay so both of us spend a family time doing this. Well, so you be sure you tell your mother thank you. Yeah, that's it really is a good looking presentation well done. Yeah. So that's that's what is what I'm going to present tomorrow. I'll have to give you trial runs again last night I sat in this view. It's coming around seven minutes if I speak for you know, all of us. So the demonstration is seven minutes or the total slide seven minutes all the slides without, you know, G describing GC comment graph. It comes to around seven minutes. So I didn't do the you know trial run for the demonstration but I'm assuming it would take around five minutes. Well, so so the every bit as much as you want to practice the practice the presentation. It's even more crucial that you practice the demonstration because demonstrations have this terrible habit of going very badly if you don't rehearse them. Okay, yeah. I'll have to try that out once, because I have to, you know, I'll try and packing all those so back files once and copy paste them into the gaseous folder and I'll do that once today. Exactly. So, yeah, that that was all about the presentation. So, I'll stop sharing my screen notes. That's great. Yeah, thank you. Would you would you like to work through your demo as well do you want to show the demo now because for me the slides that you presented look good. And you've got you've got a total of 15 minutes right that's all they've allowed you is 15 minutes and there are four, four presentations and it's a one hour webinar so it's probably even slightly less than 15 minutes because there will be some intro and there'll be some end. Yeah, the thing is I've written all of them down on the paper. Okay, so I'm not sure like if I have to give it right now I think. No problem if it's not helping you for me to have you do the demonstration. That's just be sure that you've practiced multiple times. Yeah, I'll do that. I started recording myself and you know, checking whether I'm messing things up or not so yeah. Okay, and do you find recording yourself to be annoying like I do. It's, it's, oh, I'm annoyed at this. Oh that I said that wrong I said that wrong. I paused here I said a lot I see. Yes. Exactly it's oh, I'm supposed to sound like I'm a TV announcer, meaning I never make a pause and I always say words perfectly. And no I'm not. I'm just me. So yeah. Is it fine if I can you know read it from a script. There's nothing wrong with you reading it. It's, it's better for the audience if they see your eyes staring at the camera so if you can put your text somewhere near you as you're reading it, then they're there miss there they can be misled call it what you will just like TV TV news people. So the words that they're reading are right next to the camera why because that way they're staring at the camera when they're when they're saying. Okay. So, because this is one of the, like, my first presentation ever so I'm kind of nervous and excited so. Great. Any, any other topics then that you want to go over. There's nothing right now what that was one thing which I've stated earlier. I was about the G so. Other than that. By that when you mean the potential extension of a week or yes and and so that one so long as we don't spill into spill into October, no problem for me. Well, this just something off topic, which I wanted to ask, is there any like, like a future working like with Jenkins, like after the G so face is there something that I can look into. Is there something like that. Yes, we have, we have many, many places where you can contribute. If you if you're interested in contributing to the get plug in there are several additional things that it needs. If you'd rather broaden yourself and you say oh I want to learn a little bit more about other things. Maybe you want to learn something about front end. Maybe you want to learn something about databases and back ends, or if you're interested in, I've got a particular research project or a particular project we're going to need help with, which is related to languages that are embedded inside Jenkins, in this case, it's the groovy interpreter. And, and if you're interested in sort of linguistic challenges, you know, logic, logic kind of things. We've got some very interesting things in that space so yes we've got lots of places that you can help the Jenkins project lots and lots. Okay. So, yeah, that was something I wanted to know. Yeah, so, so, well, for instance, and it just depends on your on which things you find interesting right because we've also had Google summer of code project ideas that were not adopted by anyone that we would love to have done. For instance, you know we've got one project going right now pipeline steps improvements right pipeline doc generator improvements. One that wasn't selected was the rest API generator. And if you're interested in rest API is this is this is a particularly interesting challenge because the Jenkins rest API is generated dynamically from the from the the Java code itself and annotations on the Java code. And because of that, it's not that you can read a specification and say what it is it's that you have to read the source code and extract the specification from the source code. And that's really cool because that means. All right, I mean I can I can look inside the source code with Java and you know Java reflection techniques. Look inside the source code and use that to decide and if that sort of thing is interesting to you where a where a language looks at itself right if a language is looking at itself that's that's an interesting kind of topic and computer science. Yeah. So yes, just, just no question there is lots and lots of there are many many things that the Jenkins project would love to have you your help on and if you find something that's of interest to you, I am sure we can find a way to let you help on the project. Charlie. All right. Anything else. Oh, that's it. That's from myself. Well, then, if you're okay with it, I propose let's call it done, and I will attempt to upload the recording. And again, like I noted earlier, if there was something objectionable in this I apologize I will make it available in Google Drive if YouTube rejects it. I think from our side as well right if we, I have no idea. Right. I mean, who knows what they thought was said or done I just don't. Yeah, so I look forward to this. Thanks very much for your cash. Thank you so much.