 Well, welcome to Google Summer of Code Office House. Yeah, we did present for the Jenkins Organization, and today we talk specifically about any questions related to Google Summer of Code in Jenkins and Jenkins X projects, and thanks to everyone who joined the call. Again, I do have a specific agenda for today. So, Mark, do you? So, I had one that I'd given more thought to. You had suggested in last week's session that one of the ideas I had might be a good Quick Start topic. And I'm not sure if any of the students that are interested are curious about possible Quick Start projects that they might test drive. If so, that for me would be interesting when the, is this a place where it would be okay to talk about possible Quick Start things to give people, give candidates an opportunity to experiment with something. Yeah, that's for sure. So, how we usually do it in project ideas, we have a Quick Start guidelines which are embedded in the project ideas. That's common here. So, and yeah, one of the options would be to just put your Quick Start ideas then, especially the specific to your project. Which they are, this would be a good point or so in my case what I should do is I've got a larger idea, start the draft of that and in the Quick Start section for that larger idea, it's still a draft, it's not ready for publishing yet on the page. But there I put the Quick Start in there and the Quick Start idea just becomes a sub-item underneath the project idea. Good, okay, thanks. Oh, okay, yeah, so this is the best way. Moreover, it's required for published project ideas. Any other questions, comments on Quick Start? In the previous meetings, there will be a lot of questions there. Yeah, there's also a self introduction from Sadat in the chat. Thanks for your interest. Thanks for joining the call. And since there is no other questions, comments, let's just proceed with Connie. We have three students on the call today. Do you have any new questions or do you need any clarification? So could I rephrase Sagar's comment as a question? Sagar, are you really asking how do I get started or what are some guidelines on ways to get started or is am I misinterpreting your message in chat? So text, text, by the way, you can just unmute yourself and ask the question. It's a public forum. Yeah, so the question is how to get started and for that, if you have some guidelines published in our community, so if you go to GSOC, there is a student guide. So student guide, so information application guidelines for students and there is also some information about how to apply, how to get started. But yeah, this is actually a good question. Maybe we need another guide which just focuses on how to get started for students because we discussed multiple times, but we don't have this guide explicitly on that page. So maybe I should get additional communication, okay, so again, I will just pass to what we discussed at the last meetings. If you want to get started, the best start is just take a look at the project ideas and explore the Jenkins in the same way. So you can, for example, if you want to work on plugin management, it would be good about you just explore this tool, try it out, most likely you'll experience a lot of different issues because documentation could be improved, also CLI could be improved. And if you see these issues, submitting feedback and submitting short fixes is the best way to start. And you can try it together with Jenkins and then study Jenkins. For example, Sagar asked about Android development and we have quite a number of plugins on Android, including Android link and other student plugins. So you can just try them out. So take Jenkins, install all plugins you need, configure them and try automating your project with Jenkins. It would be a good introduction to the tool and it can be also a good opportunity to get started, for example, with this project because you definitely need to manage plugins and you can explore it from there. Or maybe you want to trigger these plugins from test API in order to automate your pipeline. And again, you can adjust and go to the specification that you created on Android needs and see what test APIs would be needed in this use case. And my next item, I'll take a look, just getting started, please. I'll make it somebody else once furthered. Yeah, and that's thinking about that, getting started pages, that's different than the participate page for code or is it some derivative of that, Oleg? I'm trying to envision. I think it's a derivative of that because it should basically be like students, how to start with GSOC. Obviously, we need a reference to main participate guide to encourage students to just try contributing somewhere or to explore the projects, but I think that it should be a different exception. Okay, so it's not, because of the specific nature of Google Summer of Code, it needs to be more than just, here's the participate page, makes sense. Thanks. I will definitely create something. Yeah, just looking at the item below, actually, I can get up to the community agenda. Other questions? Can I know that by whom our proposals will be evaluated? I mean by your organization or by Google? Actually, both. But commonly, the distribution that Google focuses on eligibility check, so that they can ensure that you can participate in the project and projects focus on the technical part. So the project, we review the most of the proposal, including specification, timeline, it's also our responsibility to double check your ability when it comes to other commitments, because again, Google handles formal part and you handle the project part. Usually when we do reviews for the proposals, the most of the reviews happen during the application phase because we expect the students to submit proposal drafts earlier, so that they could get peer feedback. And it means that basically, any gentist contributor or, for example, other interested student, anybody can provide feedback and you will see who provides the feedback. And this is the key to the part. After that, yeah, there are additional reviews happening after the end of the application date. Usually it's ORCA means you're referring to that, you have explicit answers about reliability, et cetera, or again, ORCA means and mentors around in the project. But yeah, our experience that potential mentors already give their opinion during the application phase. So there are, it's rare that we just start reviewing the proposal in private after you submit the application. Yeah, then it is better to send a draft proposal earlier, right? Yes. When should we present that? When should we send a draft proposal? Well, when you're ready, there is no specific timeline. So on the Google Summer of Code, you can find that there is application software. So student application period begins on March 29th. So what it means that starting from this day, you can submit your application draft to Google. But for us, this date doesn't really matter because for us, you can submit the application draft once you're ready and be reviewed. And what matters is this deadline. I think that you should submit a final application before this deadline. Okay, thank you. If you have a proposal now, you can always start discussing it in the mailing list. Yeah, there is a lot of things to review and there might be changes in the project release by the beginning of GSOC. Definitely, there will be more project ideas. Nothing books you're from creating a proposal after the now. Michael, I have one question. So is it possible that we can contribute earlier than GSOC if we have the right skin set to get started? You ask whether you can contribute with GSOC? Yes, you can. You can contribute basically. Jenkins is an open source project. So everything is open. You have participation guidance available, for example, here, where you can find a lot of different domains where you can contribute. And as a student, you are totally invited to contribute at any moment when you're interested. And doing some contributions is, of course, a good opportunity to get introduced to the project and to explore the code base. Okay. Yeah, go ahead. Thank you. Yeah, there is a lot of components. So since you're asking about Android, you can just go and search for Android plugins and you can see that there are 23 plugins which are explicitly referenced on the road. So yeah, some of these plugins will definitely benefit from contributions and patches. So just take a look. Yeah, thank you. To further support Oleg's comment on encouraging students to contribute early, it helps build your skills. It helps build your association with the community and it helps others as they see your involvement. So yeah, and it helps the project. Please, yes, contribute. Are there any other questions? Yeah, probably we can take some break and just pick up some items so that we don't miss them. Yeah, we still need to make the CDF next week. Yeah, other action items is actually a sample for participation. I've written it out, but unfortunately, I didn't send it. I will do it if you have any questions. And your mark has an action item to actually send it to this project again. Okay, I see Oleg here on the call. Oleg, did you have any questions or ideas about GSOC? And that's, sorry, I'm just listening. That's fine. So I guess, there is no other questions that's all for today. If you have any questions, we still have time. Okay, then no questions. See you all next week. We will do the meeting in the following time. And if you're interested about participating in Jenkins, we have one friendly program, Google season of dogs. This was a program which ended just last week and our mentor will be doing Jenkins online meetup today. If you're interested, you can just join this Jenkins online meetup and get some insights about how the project went in the community and maybe you'll provide some additional information. Thanks everyone. See you later.