 Thanks for joining us, for watching us on YouTube. Today we have a regular JSO coffee service. It's just one week left before the student application deadline. Today we are running a common agenda. So we will discuss news, open action items and if there are any other updates, let's also discuss them. And I believe that the most of time today will be spent on Q&A, so that we can answer questions by students. That's the plan. Anything else to discuss today except what we already have on the list? Okay, so let's proceed with news. So yeah, the first thing, I'm not sure what the students have already received the notification. There were some changes in JSOC timeline. So basically the selection phase will be expanded, same for community bonding. And now after the changes, current period will officially start on June 1st. So basically it will start two weeks later than it will be reformed. So these are good news. Bad news that application deadline is till March 31st. So in one week, so nothing really changes in the current phase and it implies some obstacles. So example for us, as we discussed in the mailing list, we try to do the most of the reviews during the student application phase so that we can provide feedback. We can get more insights about students and for us we still have one week as mentors to do so. So my ask to everyone for mentors for students, if you're interested, please submit your project proposal drafts earlier. For mentors, please dedicate some time to reviews. I know that maybe all these lockdowns, the situation is not really manageable. Sometimes people don't have time, but all of us do the best effort. So if you have any opportunity to submit your proposals earlier, it will definitely help. And yeah, after that, specifically for mentors, we will have three weeks to review the proposals. To be honest, I have no idea what exactly we will be doing because, again, we review the proposals now, but still we have a bit more time for this phase. So probably we'll spend more time on project mapping. And if you like mentors in some projects, you'll spend these three weeks to find them. And again, we received a message from Google that we should ensure that all mentor teams are more strong than it used to be before. So because of coronavirus potential changes, the recommendation from Google is to go with three mentors project two or three. So this is something we will be trying to implement for all projects we accept. So I guess these three weeks will be spent well. And yeah, I guess this is all with timeline changes. Any comments before we move on? Yeah, he also wanted to say hi. He's busy destroying other stuff in my apartments. Okay, so the next update we had last week instead of common office hours, we actually organized Jenkins online meetup in order to summarize the application process and to talk about expectations to go through the application process. So if you just join GSOC and if you want to get more insights how to start, I believe it would be the starting point for you. And we already added that reference to this recording to some of our materials, a bit if you'll edit the student application guide. So please use it as an additional source of information. Okay, any other news? Any other updates? Yes, not. So business as usual. For open action items, we cleaned up our queue. So I've did the automatic specification generator proposal. Now it's officially in the accepted state to whomever is interested. There are some quick start guidelines, but basically they summarize what we discussed at the dedicated project meeting. Then we had online meetups, some are published recording for the previous meeting, which didn't go exactly right because of the stuff. So what we have left is basically promotion of GSOC. So again, if anyone is interested to get more students and their proposals, please use social media to promote the projects because it's the way how we raise visibility of our organization. This year, we have around 200 organizations participating. So it's a big number. And you should use an opportunity to be more discoverable. Speaking of that, both Jenkins and Jenkins X, I get to publish a blog post, because we delayed it a bit due to uncertainty. And now it's a different time to do that. But for Jenkins, if you go to Jenkins IO website, it's one of the previous section items, we now have a jump bathroom. So whomever visits at the site, they will basically see this page after five seconds. So at least something is highlighted. Okay. And I guess that's it. So should we proceed with questions? Or does anyone have additional topics to discuss? Students, mentors, anybody? So like, actually, for me, any, any recommendations on ways to encourage further mentors, I've one of the get plugin projects has only two mentors, the other one has three potential mentors, but I'm feeling like you're right, two may not be enough. And so if two is not enough, is it just a matter of socializing with folks to suggest, hey, come come join or looking at previous contributors, any other ideas? Yeah, that's a common approach. So you can take, for example, if you create a project based on your issue, or user request, you can invite these users to be stakeholders or potentially mentors in the project. If you know active contributors who might be interested, also invite them, it wouldn't hurt. And yeah, that's how we improve the situation. Later, after the application deadline, we will still have three weeks to form mentor teams, because we will be requesting project slots after we already have a draft of teams you want to have. So these three weeks will be spent to get proposals mapped to filter them and also to find mentors. And even if there is a need to have more mentors for good plugins, I think we will be able to help. But yeah, we do not promise magic there. So we do best effort like everybody else. So yeah, it's sometimes it's difficult to find mentors, but for good plugin and confident that we can have some great. Thank you. Thanks very much. Any other questions? Okay, if there is no questions, let's approach from a different side. So I believe that everybody on the call submitted their proposal drafts. Is there any project where you need feedback as soon as possible? Or are you more or less fine with the feedback? I definitely know that I still also meet details, detailed comments for the project. But Yeah, and I still all reach out comments for his project he and I have discussed it. We had it in office hours yesterday, but I owe it. So still still has to happen. Okay. Anyone else? Liga, for me, I'm not sure I can be the man mentor of my project proposal. So I'm wondering if we can invite another one mentor. There are two mental potential mental in this project. I'm afraid I can't understand every sentence of from the students like last year. So I hope in this year I can push this proposal better. So currently I'm calling for a hack. So regarding that, one of our approach we had a meeting with Chris Kidang. So maybe inviting him would be a good first step. And regarding the rest, I think that we could socialize this proposal, because I believe that it will get a lot of interest. So for example, you could just send a message to the developer, mainly saying that, hey, this is a story. We want to achieve that. We have students applying, we need more mentors who is interested, something like that. Yeah, because yeah, this project will definitely have some interest. And for example, what else you could do? There is custom work packaging. So for example, here we could, there is not so many watchers, but just putting a plug there that we want to have basically custom work packaging as a service. Well, it's, it's probably not true, but it could, in principle, it's what we want to achieve there. So just put in the reference to this project here and there could help to attract more contributors. Yes. Or maybe what else you could do? So we have this docket zh project. So I think that even in the current state, it already could be for example, posted as a blog, especially on the Chinese version of Jenkins website, but maybe also on the Jenkins IO. And we could also use it for additional promotion of the JSOC project. Yes, I try. I will take your advice and try something. So anyway, for finding mentors, we still have a lot of time. It's better to start earlier. But the other side of this question is that we have one week left for finding students. So not all proposals have active students engaging with potential mentors. And if you're looking for more students, definitely try to spend some time and to socialize your project. Okay. Yeah, with respect to reviews, I guess, I submitted a proposal for the Custom Service Distribution one. So I guess that is spending some reviews because it just hasn't enough reviews. I'm not sure whether the reviews that I got are enough. But yeah, that could get I think since Reki isn't available to be a mentor this year, maybe that's the reason for the less number of reviews. But if you could get more reviews on that. So if you're waiting for feedback, and if you don't get that, don't hesitate to pink sometimes. So for example, pink in every few hours is definitely not a good idea. But sending a reminder, let's say once per week, or now maybe once for two days taking the timeframe is something reasonable. Okay. Also, if I'm happy with the reviews that I got on my proposal, is it a good idea to just hit the submit button as a PDF or should I still wait for one another couple of days because for the Docker polling proposal, I guess the reviews that I got are enough. So is it a wise decision to just hit the submit button for that particular proposal or should I still wait for it to review? If I recall correctly, you still can edit your proposal after the submit button. I might be wrong. But from what I've heard over past years, submit button just says that your proposal is submitted and will be reviewed draft. If you don't change it to submitted state, you don't want to be accepted. So it won't even reach our mentoring organization. So I think that after you submit, you still can edit that. And yes, if you feel it's ready, just feel free to submit. I think you can submit until the deadline over your previous proposal. I've heard the same as well. Okay, thanks. So yeah, if you feel the proposal is in good state, feel free to submit anything else. Does the same mentor problem I think exists for fingerprint storage also as of now? Could I help somewhere in that? So yeah, I'm aware about fingerprint storage. I will make sure that they gets fixed during the project selection phase. So yeah, I'm already in the discussions with some core maintainers about having this project. And also we had some mentors from 2019 who were interested. So yeah, I'm already working on that. Thanks. Yeah, so regarding mentors, yeah, the situation is a bit chaotic nowadays, but we will do our best to get mentor teams formed. And for some projects as we discussed, we can potentially have two students working on the project idea areas, assuming that the projects are aligned between each other. So for example, this is a case for GitHub checks API. Because we have five mentors here. So we can potentially scale to two projects. Well, I believe this topic will get a lot of potential mentors if we reach out in the community more, because it's really important project and assuming that everything is submitted, right, we can have two projects there. Listen, anything else for today? Any requests to be addressed? Do we have questions from potential students on the call? So since the proposal, submissions will be done in a week, and we'll have a month before the selection announced. Is there anything as potential students that we could do to I mean, we contribute to the corresponding projects or maybe build proof of concepts or anything? Would that help or would that be in violation of the Google conditions that a project shouldn't be completed before its initiation? So I'm not sure is that a gray area? Okay, yeah, let's split it to two parts. Whether you're allowed to contribute? Yes, you're you allowed to do anything within the Jenkins any time of the year, regardless of JSOC. We invite any kinds of contributions. If you complete your project during the project selection phase, it's a bit different situation. And my advice there would be to focus on the discovery phase on studying, but not on doing the final implementation. Because yeah, if you start doing final implementation in the middle of the application phase, it may cause a lot of complications. Prototypes, yeah, sure. But just keep it in mind. Yeah, I would like to add something here. The idea of the summer of code program is to work with the developer community with the community of Jenkins. So if you go off and do all the work in isolation, then it's not really in the spirit of the program. Yeah, thank you. I got you. So isolation or not, it's a separate topic because yeah, somebody can start working in April, get feedback from maintainers, get things integrated. But so yeah, this question, these topics may be a bit orthogonal. But in general, JSOC is about community experience. And it happens on summer. Yeah, sure. It's very difficult. Because nobody wants to say no to someone who's enthusiastic and contributes to the project. So yeah, it's difficult for us. Yeah, yeah, got it. No, I just wanted to be sure that I mean, as long as I can contribute to the organization, that would be more than enough. So yeah, I'll target other areas possibly. Yeah. So I mean, you could something that's not part of the summer of code program as much as is documentation. So we're, it's a it's a program about writing code. It's not a program about documenting. So if you have time before you start a project, you could work on the documentation and explaining how it's going to work, and explaining like things from the user perspective, like if you're really, really want to contribute something that's not code, you could, you could do that, I suppose. It's a really, really interesting suggestion. Thank you so much. No, no shame, contributing documentation and no shame contributing fixes on the newbie friendly issues, right? They're most of the projects have a newbie friendly issue list. It's a great way to contribute. Have good discussions. Yeah, thanks. Okay. So so one thing which makes sense to mention that we still will be still doing our evaluation based on the submitted proposals. So yeah, we understand that contributions done after the submission deadline may cause some bias. And we will try to mitigate that. But yeah, make sure that you submit everything important in your proposal, or respects by the application deadline. Because before that, you can technically work on that. But it also goes in a kind of gray area. So we will be evaluating the proposals submitted JSOC website, the final PDF versions. Yeah. So if there is nothing else, everybody could get 30 extra minutes to do some reviews of proposals. Yep, we could switch to that. So final call for questions. There is a comment in the chat. Oh, yeah, for automatic specification generator. It's also in my queue. So I thought that I provided the request feedback. If not, yeah, I will double check. Thank you. Thank you, too. Yeah, sometimes requests got missed. Because everybody of us receives hundreds of notifications from different sources. So yeah, we may miss something. And there is no problem if you send a reminder and pink sometimes, preferably on public channels. But we are trying to catch up with all these reviews with you. Okay. Anything else? No. Okay, then thanks everyone. And thanks a lot for joining this meeting. See you again in one week, even if we so the application deadline is on Tuesday, we'll still run a regular office hours. But for the record, we won't be discussing the application results there. And we won't be discussing and disclosing anything in public until the subject projects are announced by Google. But if there are questions, for example, technical details of process questions, we can still discuss it during the public meetings. Okay, that's it.