 We are live. Hi everybody, this is a regular Google Summer of Code meeting in the Jenkins project. Today is April 17th, and we just have a regular sync up between mentors, org admins, students, and whomever is interested in JSOC. I believe we don't have a specific agenda for the today's meeting, but yeah, let's check. We have Jeff and Martin on the call, the JSOC org admins. We have Nisart, who is one of the students, and we also have Rick, who is one of the mentors for the GitLab ACM project. I'll share my screen. Do you see it? Yes, yeah. OK, so we have a Google, it's just empty. OK, so what do we have? OK, so regarding current status, currently we are reviewing the proposals received from students. The design for slot number applications is next Monday. So by the next Monday, we need to agree how many project slots we are going to request. There is a lot of private meetings and discussions happening between the mentors and org admins. This phase of JSOC is not public due to various reasons. But once we have everything set by May 6, they will be announcements of the projects we accept. So everything is going OK. We had some discussions. We already had one meeting with mentors. And yeah, Martin wanted to say some words to other mentors participating in the project. Yes, so I would like to remind mentors that we are expecting active participation at this time for all mentors to review the applications because we're trying to form potential mentor teams. And we need their participation before the slot application deadline. Yeah. That's what I had to say. I'm trying to work on some emails to get those discussions started for those mentor teams that have not had a chance to look at the applications yet. Yeah, we have quite a number of such mentors. So in some cases, we have preliminary feedback from mentors. We got before the final applications got received. But we still need to get more information and more confirmations, especially because some student proposals have changed. We also want to know about mentor availability. Because in a few weeks, we need to decide what will be the student projects we accept. And it's not only about student applications. It's also about mentor availability mentor teams because we want every project we accept to be successful. And it means that if there is a high chance that the project is not successful, then we would like to avoid accepting it, even if the risk comes from the mentor side. We disable sound from notifications right now. And from the check, we just disable a Gitter for a while. So yeah, regarding other activities, we also need to do something about swag. Yeah, we will be doing it, I believe, in the next few weeks because now we have information about the active participants this year, including students and mentors. And of course, we need to just do the distribution because this topic got delayed significantly. It's mostly my fault. Yeah, so something like that. And I guess there is no major activity that is happening right now, except the reviews. So do we have anything else to discuss now as a part of the project meeting? So we have Nisar, we have Supurna on the call. So if you guys want to ask something, just go forward. Yeah, so like I have only one question to ask that if there is a project and if no mentor is interested in that project for mentoring, like any mentor haven't given the feedback on that proposal, then what would be done with that particular project or proposal? Yeah, so in this case, it's a responsibility of all carmenes to try finding mentor teams. So if we think that the proposal is generally OK and that we would be interested to have it in GSOC, in such a case, we try to reach out to potential mentors outside from the original list. So if we are successful, then we can still have the project. If we are not successful, then unfortunately it happens sometimes because, well, mentors are just potential mentors. Some mentors may decide to go to other projects. And sometimes it happens that we cannot accept projects because we finally just cannot find mentors for this particular project proposal. It happens. It happens not that often. So as Orca means, we will do our best to prevent it. OK, thank you. Thank you, Tom. OK, anything else? If not, we can probably just stop the broadcast and then spend some time with Martin, Jeff, and Supun on another call to do some scrap of the mentor applications. Yes, I'm in favor of that. OK, Justin, somebody is interested. In one hour, in 45 minutes, we will have initial meeting for Google Season of Dogs in Advox, Sianandri, Outreach Special Interest Group. So if any of the mentors are interested to join, feel free to do so. But yeah, right now, I'll probably stop the broadcast unless Praspeak, Nisarkovs will have other questions. So here you go, Justin. Hello, sir. Yes, sir. So actually, talking about documentation, I just wanted to know if there's a certain sort of blog that is dedicated to Jenkins. If I wanted to write something about Jenkins, some sort of plug-ins. So is there any special type of blog that is dedicated to Jenkins? Yeah, I can show it to you quickly. Yes, yes. I can just post my articles related to the software. OK, this is my screen? Yes, I can see. OK. OK, creating a blog, so I'm creating a blog post. We have a Jenkins website, Jenkins.io, the same site where we had all of the JSO resources. And here you may see that there is Jenkins.io slash blog or slash note. There is a list of blog posts. And there is a lot of blog posts happening now. If you want to contribute your blog post, actually, everything is powered by the configuration that's caught on our website. So there is a project called the Jenkins, and Jenkins.io. So it's a configuration that's called for our site. And it includes contributing guidelines. So these contributing guidelines explain how to propose a change, how to test changes for the website. And they especially include an entry for creating a new blog. So if you want to post something technical or something community-wise about Jenkins, it would be one of the ways to do that if you are interested. Otherwise, just post on whatever your blog post, a blog, and then Jenkins, we can use our community resources to post your blog post, to tweet there, et cetera. But if you want to have something on Jenkins.io, there is an opportunity for that. OK, and before posting that, would there be some sort of editing or that I should be showing to the mentors, showing to the maintainers? Should I show them before releasing? Yeah, so blog posts, these blog posts actually, they're just being created as pull requests. So here you can see some examples. So open pull request, you may see that there is a template in Jenkins plug-in blog post created by Steven Tirana, something like two days ago. So here you can just remind me. So here you can see that it's just a pull request. There's one file in a ski dock, which includes all the information. OK, I need to submit it as a PR. Yes, everything is submitted as pull request. OK, thank you, sir. Thank you. OK, you're welcome. OK, anything else? No, sir. OK, thanks for the interest about your blog post, by the way. So if you want to share something, it's something we will definitely welcome as a project. OK, OK, I'll surely do that. OK. So if there is nothing else for today, I'll stop the broadcast. We will have another meeting next week. But in my case, I will be traveling. So Martin, Jeff, would you be able to run the meeting? I'll be here. So Martin's not. I'll be second. Have you got permissions to run YouTube recordings, Jeff? I don't think so. I'm good for next week. I can be there next week. That's perfect. So I'm not sure whether we will have much things to discuss. We probably need another meeting with mentors for the next week. I think that we can submit initial application for project slots without additional meeting with mentors. But once we have project slots communicated by Google, we definitely need something. We can just chat about it later in private. So I wanted to run something by you. I had sent out a couple of posts looking for a backup mentor for my project. And I got one or two people that I didn't know saying that they were interested in being a mentor. I don't need them for my project. Would we be interested in having them? I guess my only hesitation is it's somebody I don't know. I don't know if they'd be a good mentor. But do we want to give them a shot anyway? Yeah, so if I recall correctly, you got a response from Christian and from Keith Rosento? Yeah, there was another guy too. Sagar Uttakar. He says he'd like to mentor Jusak students. Yeah, so my advice would be to talk to them directly. So Christian is an experienced mentor. Keith, he was also mentoring community activities because he works for CloudBees and we had some projects. So I'm confident that he can be a good mentor, especially in JavaScript and React world. But if you want to have a mentor team, it's still something for all of you guys to just chat with each other and to agree how you would approach in this project. So yeah, just reach out to them and maybe set up a short meeting to get introduced with each other and it would be a good first step. So I've chatted with Keith and Kristen already, but there's this third person that said they were interested in mentoring. So I don't think I would need them for my project, but would it make sense to encourage them to find another project? I think we can discuss it in the mentor menu, please. Okay. Yeah, so definitely it won't hurt to have more mentors. I mean, organization-wide. But yeah, it's hard to say whether all people would be interested to mentor many projects. We have a lot of mentors who are interested in just one project idea, which is perfectly fine. But yeah, that's why we have work meetings. We will do this coordination. We will do this mapping. And yeah, for us, right now the main objective is to get an approximate number of projects we can have because we need to send a request to Google. So maybe I should ask them to see if there's another project that's interested in that? That's one of the options. Another option is to just see how it goes because we still need to coordinate projects. I'm not sure whether it would be a first choice for Chris, for example. But yeah, it's something we should really discuss in private. So let's start the discussion in the mentor menu, please. And then let's just press it from there. Sounds good. Okay. Anything else for today? If no, thanks everybody. And see you next week. And again, if you are a mentor, please spend some time to review proposals in the area of your interest, provide feedback, and respond to our mentor forum which we sent on Monday because we really need your insights about the projects you would like to take and what would be the priorities for you. We will use this information to draft the mentor teams and then to send out these drafts to mentors so that we can continue the discussion. Okay. I have kind of a question. So I'm not sure that even... So none of the students that I kind of was hoping to write a proposal wrote a proposal which I think there was some confusion, but it's fine. I think I'll be doing more school summer of docs stuff or season of docs. But what if there's no proposals that need additional mentors? I mean, I'd be fine with mentoring, but I'm kind of more helping out any of the other mentors who are already mentoring. And I don't know if there's too many people on one student if that's overload for the poor student. But I really don't remember a year when we had enough men, to be honest. Okay. And yeah, even if... So this year we have not only mentors, but also a technical advisor. So people who are not directly involved in mentoring students, but are more able to answer technical questions, maybe provide some reviews, et cetera. So maybe if you're interested it would be also an opportunity. So if you don't want to strongly commit to one particular project, but if you're still interested to participate somehow, with your experience with Jenkins, it may be a reasonable approach. Okay. Great, yeah. I would love to be involved and I would help out any way I can. Yeah, thank you. So anything else to discuss today? Martin, you have to drop in a few minutes, right? Yes, I have to go in two minutes. So probably there is no need to have a private meeting right now after this call then. But we can just discuss everything in the meeting, please. Okay. Let's just do the meeting, please, the discussions. Okay. So yeah, thanks everybody. Thank you, Oleg. Yeah, thank you.