 Okay. Okay, recording is on. And let me go back to sharing my screen. Okay. Hi, everybody. So it's this is Jenkins gsoc 2022 office hours, and today's March 18. So we're going to start with any questions are on it looks like you're the only one on the call with us today. So I figured we'll cover questions from you if you have any. And then if not there, I went through the q amp a on the GSOC, Google GSOC site, and I thought there were questions here highlighted here that might be helpful to our participants, as we are approaching the opening of the submission period. Right. So, I'm going to leave it here and let our participants or GSOC participants open this up and, and let you guys ask us any questions or mainly Chris questions and we'll try to answer them. If we don't know the answer, then please go ahead and put your questions via in a comment via the comment option. And then after the call, I will chase it up with the appropriate project mentors and find out the answer for you. Okay. All right, so let us know what questions you have. Yeah. Yeah, so I had a question which I already posted in the get a chart. But I think I'll just bring it up here because I don't have any other questions. But it was, it was regarding that Mark had mentioned that the get prune command is it can only be used in the context of the fetch operation. So I did some reading on that and I found that there is a get that the prune command has a get fetch command and it also has a generic get prune command. And I've sent some links regarding that on the data chart if you want to check that later and if you want to respond back to me later. But that's what I wanted to ask that like when well, like did Mark mean that I should be using the generic get prune command and not the ones and not the get fetch prune command. Okay, and is that the one that is currently is the get fetch prune command the one that is currently implemented over there in the extensions. Okay, yeah, thanks. Thanks for sharing that so. Mark isn't here on this call so what I think what I suggest that you do because he he hops in and out throughout the week sees he's on vacation but he's still online sometimes. If you can just like, you know, post your question at Mark wait, and then clearly state your question on there and then he'll he'll hop on and he'll answer for you. That's right. Thanks. Hi Kristen. Thanks for joining us. Any other questions. If there's no questions that you can't have any questions at the moment. Just feel free whenever you know your questions you have a question just pop it in the getter channel, and then one of us will respond to it. Okay, so if there's no other questions and I thought maybe I again highlight some of the questions in the Q&A from the Google document that I thought might be helpful. So with the applications being open soon. I thought that where there were some questions that might be helpful like how does the proposal. What is the proposal look like and I put the answer the response from Google here. The proposal is directly to the mentoring organization so the answer is absolutely not. Please make your submissions through the Google portal. If you send it to us it's it's it's going to be late and the end and GSOC is pretty adamant about sticking with the schedule. So there is no leadway if you're late so make sure that all submissions goes through the Google summer of code web app. If you submit more than one proposal, yes, but you will be if you submit more than one, and you get accepted, it will be just for one proposal for one project. Okay. What should I do to improve my chances of being selected as a juice GSOC contributor. The answer is here. It's basically interacting with the mentoring organization. Submit your draft proposal for to the organization for reviewed feedback enhancement and then make your submission to Google summer of code on time. And that's basically it. Last calls for questions. Okay. So, so hello everyone. Can you hear me. Yes, we can. Okay, great. So, actually, this is my first office hours I guess for Jenkins. So, I'm actually happy to be here. Thank you. I'm actually working on this automation specification generator for Jenkins REST API for like a couple of weeks now. So, I guess like it's this project where they are until like since 2019 I guess so I have been through the materials and resources available for this as like it's been existing for about three years now so I saw some like in the YouTube like after like you guys probably uploading these all these office hours to there so I was when I went to YouTube and like watch all these videos regarding to the automation specification generator and so I saw some like potential. These are participants as well but I don't know whether like why they are like proposal has been rejected and I guess like I have been through their drafts like proposal drafts as well and I found like is it okay if I ask a specific questions about this project. Yes. Yeah, okay sure. So, I actually like kind of like have a kind of idea like how to proceed with this project and mainly like I guess I have to write some kind of a library for like process the annotations inside Jenkins code and obviously in Jenkins plugins as well to like transform like actually like process the gate and paused API in points to some kind of a YAML file so if I can do that I guess it's pretty much easy for the next steps I guess from that YAML file I can actually generate the specification using open API. So my question is like inside Jenkins code you can actually process it and like capture these annotations because there are like proper annotations are there like you know the exported annotation and SLS exported beam and also in Jenkins code like there are gate annotations and paused and like for Jenkins code obviously like it's pretty much easy for me to capture this using a library but the problem is like for you know for Jenkins plugins if like if I'm going to write a new plugin I can actually like at these extension points like these annotations for my plugin but the case is like currently I guess like there are over 1,800 plugins over there like if I am suggesting to add a kind of a custom annotation for these plugins so that would be not possible I guess because I have to like go through all these plugins and the plugin maintenance hands to add these custom annotations for every plugin so I guess that will not work so in that case will it be possible for you guys to suggest anything for these plugins like for generating API endpoints for these plugins I guess like I know that these are kind of tasks for the participants I mean the contributors to find out but like right now I guess I'm kind of stuck on this plugin situation because I know like it will be easier for me to capture the annotations for the Jenkins code obviously but I'm kind of stuck at these plugins like how can we implement that kind of a feature so if you guys have any suggestions for this it would be really great for me to like straight going forward. So Kristen or Chris you want to take a stab at this. Sure I can I can help a little bit here so you're right like we it is it would be absolutely close to impossible to be able to go through and annotate 800 different plugins that's so many, which is a benefit of Jenkins that it has so much stuff but it does make it incredibly hard in these cases. So what you're going to want to do is look to see what's already there and I have to double check how to do this but and to see if I can find a good example of a plugin that does offer an API endpoint. But you'd have like there's already. There are already pieces inside of Jenkins that a lot like it have this type of annotation. So you wouldn't have to worry about scraping code. I think you want to kind of maybe deploy the same type of methodology is already used for generating the pipeline steps and I think that was maybe detailed a little bit inside the project proposal. So I won't get to into that here. But yeah like there are some pieces like Jenkins already has like some of this built in already and I think it's making sure that we can start to leverage those particular pieces so you don't have to worry about going through and annotating a whole bunch of different plugins with a custom annotation that would also then require new people who want to use rest like or expose some rest functionality to then also remember to put the tag on which if they don't have to in order to get it to work they're probably not going to just because it's you know you're you're not thinking about it you just like oh it works and so I took an example from another place and made it happen. So you probably would not have to it would just be difficult to get them to like to force a new tag on other people. Also, I do want to also address the comment about how it's been an idea for a really long period of time. So even though like so yes there's like every year we get tons of amazing proposals. And unfortunately there's only so many different student projects that we can take, and sometimes actually sometimes we can't pick everyone. So unfortunately, sometimes this project gets maybe shunt a little to this late years was kind of not chosen because like the proposals from other students for better, or we had more mentor availability for certain other projects and that's like another key to success is like, we want to set you up to be successful so we want to make sure that we're here for you and if maybe there were you know for mentors for another project that was just as good it's like that project may have been set up a little bit better for success that maybe like one person. It's just a lot of work for both both students there so yeah like that sometimes that's what happens with projects like it's the proposals are great. But it's just unfortunately we can't pick them all. Yeah. We move the this does that help. Yeah I understand. Okay. Thank you so much. Thanks Kristen. Are you and do you have any other additional questions for for our mentors. I don't know that that's all I really had, but I just wanted to ask the request if Chris could provide any, any like suggestions on it. If it's possible. Yeah. You mean, you mean the question you asked on a guitar. Yeah. Okay. I'm not, I'm not sure what Mark meant when he said like the point of action but it's probably better. I didn't wait until it comes back. Yeah, thanks. He was being kind of a I have to admit. Thank you. Okay. Okay. There's no other questions then. Let's call it a day for for this meeting and then if you have other questions just feel free to pop it in the Gitter channel and just a really quick reminder that you should get your proposal draft to the mentors for review and feedback as soon as possible. It's all of us we have full time jobs so it's going to take us some time to review your drafts so please get it out early. So we can get as many eyeballs on it as possible so that you can make it on time for the Google deadline. So if there's nothing else then we'll see you guys on Gitter. Thanks everybody. Thank you. Bye.