 Welcome to Google summer of code office hours. It's the 14th of July reminder that we abide by the Jenkins code of conduct as we as we interact with each other in these meetings and face to face and otherwise. So, thanks very much again for for all that you're doing congratulations on the conventional commits plugins I continue to see releases being delivered. Are there any specific topics that you wanted to discuss today or any things where you wanted to raise a question. Yes, so I specifically joined this meeting to ask about the presentation that we are supposed to do next week. And regarding that, I wanted to know whether there is a particular slide template or anything that Jenkins would like the students to use. So any particular template to present or is there some is it something that we can decide on our own. As far as I understand it you can decide on your own. I'm, I tend to be a lazy slide creator, and as a lazy slide creator that usually means I go grab someone else's slide deck that was on a somewhat related topic or in a related theme, and use it as my basis but you can use whatever slide template works well for you. One of the things that has. If you were looking for hey what what basis could I use, you could grab the slides from one or more of last year's presentations and use those as a starting template if you'd like. That's a wonderful idea, I would do that. Yeah, I was thinking to use our newcomer tracks side from contributors of it. So I wanted to ask you shall I reuse that. That isn't and that's a great choice that for me using using somebody else's deck as a starting point helps me not have to make all sorts of choices about design and layout that I don't I'm no good at making those choices anyway. So, so yes, you are welcome to use the newcomer track slides as a base absolutely. I don't remember where I stole them from but I think I think it was from another presentation on contributing to Jenkins and they are certainly all open source and you are welcome to. Thank you for the information I was easier and it has all sorts of Jenkins mascot and logos so I don't really have to worry about making it. Right. Well, and okay you just you just highlighted my reason right is someone who actually has more visual hints than I do. So I started to place images in the slides and thought about putting interesting images and that reminds me oh yes people like pictures slide should not just be words. What picture could I put here that would help people remember they should look at this slide. So yes very good. Yes. Okay, so base my presentation on that. And I'll definitely have a look at last year's presentation to get an overview of what's expected. My understanding I talked to Carla DeLaMark earlier today and my understanding is it's roughly 15 minutes of presentation and five minutes of Q&A. And so, and they'll allow that you could do the presentation live, or you could record it for me, it usually works better if I do it live because I don't spend a bunch of time then trying to create a really good recording but if you're more comfortable creating a recording then you're welcome to record it, but we still need you live to be ready to answer questions, questions and respond to people. So about that I was thinking to do it live so that it is more interactive. I can explain the process when doing it so. Good, very good yeah and that that works that certainly works very well for me so by all means do that. So like one more question regarding the feedback this time. I did not actually receive any email from Google so and I remember Cara told me that there will be an email or Google form to fill from Google so shall I wait shall I ask them. Well, so you may have missed you may have misunderstood how the what happens in Google summer of code. The, the phase one evaluation is provided by your mentors not by you. They didn't open the form until the 12th of July and they will not close the form they will not end the submission period until the 16th. After the 16th, I believe there is an optional segment that mentors are allowed to place where you will receive that text that they put in there. So, so in, in my case, I just submitted yesterday, my, our mentoring teams evaluation of our project, and it included a number of questions about hey, is the is your student on track are how often do you interact with your student have the how the interactions ban those kinds of questions, and I don't know if those the answers to those questions will actually be shared with the students. But there was a segment at the end which said, what would you like to tell the student or something like that and then we I filled that in with hey how pleased we are with our results and how delighted we are with with the students interactions with us. So you may receive something from Google Summer of Code but I would not expect you to receive that until for sure, after the 16th of July when they close the, the period where mentors submit their evaluations. Oh, okay. Because I remember reading an email that students are also to submit an evaluation of the whole process of the organization and the mentor. Oh, well then maybe I'm wrong. Let's let's let me check hang on just a minute. Let, that's a very good question. So student evaluation. Okay, so Google coding phase one evaluations and student okay I'm going to look at cars email so she says, oh yeah she says mentors and students begin submitting phase one evaluations. Okay, let me let me look at the at the Google Summer of Code guidelines then because they should say that I thought it was only. I thought it was only the mentors that submitted phase one evaluations, let me look and see just a minute. Google Summer of Code 2021 phase one. Okay, first five weeks of coding. Okay, so on find is. Reading 16. Oh, no, no, you, Kara is correct. It says so so you probably should contact Google Summer of Code then because it says on their here I'll paste the link into the chat. It says here on their timeline for July 12 mentors and students can begin submitting phase one evaluations. And then July 16 is phase one evaluation deadline but you say you have not received email from Google Summer of Code, inviting you as a student to provide your evaluation. Yes. Yeah, go ahead. Yeah I was saying I just logged into the dashboard and I do submit evaluation button so I think the some email might have been missed but then I can see that I have a button over here that says complete evaluation. So I missed that I guess. Okay, all right, all right so well so I'm going to make a mention of that in in the in the CDF slack channel for GSOC that the phase one evaluations in office hours today. He sees, he did not receive a link to the to submit the evaluation, but does see the evaluation, or what you said it was an evaluation button. Yes, complete evaluation button. Complete. Would you be willing to capture a screenshot of that, just the segment of that screen that has the complete evaluation pasted here so I could put it or, or maybe you could reply to me in this in the slack channel. Yes, I can do both. I took the screenshot. The same experience. Be sure that you complete the evaluation by July 16 by the July 16 due date. We do not want to miss submitting about and about all evaluations. There. Okay. So you should be able to see that I received the email, and we've submitted the evaluation for our project. Yeah, great. This is also a good excuse to remind others that they need to be sure they get their evaluations and I'm not sure that we can. I think such a thing as reminding people too frequently to complete those evaluations on time Google, Google seems quite serious about it if we miss an evaluation deadline they consider that a negative negative for future applications from the project to join Google Summer of Code. Yeah, I can understand. It was like for everything they did send an email so I was like okay I'll get an email but then 12th past today is 13 I was like oh am I dropped out of the mailing list or something did others get and today I was like oh I can just check the dashboard before actually writing an email and I saw the button. Right, exactly. So, and I'm going to paste into the chat thread on the CDF slack is at here. Yes, I am under. Great. Thank you. Okay, so you and that and that yeah so you have that I think is the same thing I saw where I have a big button that says complete evaluation and the countdown timer that talks about that shows you only have this much time left before before you've run out of time. Very good. All right, thank you. Thanks Aditya. I don't have any other questions for now. Okay, well then let's, let's, you're welcome to, you're welcome to drop off if you'd like, I will remain on the call for another five minutes just in case someone else joins. Thanks very very much for your contributions to Google Summer of Code into the Jenkins project. Thank you I'm really enjoying contributing to the project and learning a lot. Well, I'm delighted that you're here thanks very very much Aditya. So I would drop off and fill the form. Thanks. Yes, that's high value. Bye bye. Bye bye.