 Okay, we should do it now. Yeah, now the recording is running. So welcome to the regular GSoc meeting. Well, now it's not that regular, we skipped the recording class being because there was no students participating in the call. Today we have Abhidhya and Parichay on the call and you all have several of them. So basically we can just have a quick discussion of what's going on in the project and then have a colleague here who's all interested students. Jason Mastrin? Yes, I do. Yes. Okay, so some updates. Yeah, right now we are in the middle of the second coding phase and basically we are going to have another round of evaluation presentations on the week of the second evaluation. So between July 23rd and 25th, we will have interim evaluation presentations. The format is pretty much the same like we had previously. The difference is that now we will be doing the Jenkins online meetup. So basically there will be more exposure and more people participating and hopefully more questions. Now the difference is that it will be not only Google Summer of Code, but also all other summer projects. So it will be a joint meeting where I use other projects. So we have already been invited to outreach here. We have already been invited to other GSOC projects related to Jenkins. And if somebody else wants to present his or her work related to Jenkins during the summer, we are also more than welcome to participate. So we are likely we will have maybe eight sessions, maybe 10 sessions, let's see. And yet soon I will be sending Google not to schedule the date, but yeah, I believe it will be the same as before. So two sessions for my agent in Pacific region and for America's and Europe is more or less convenient to use both. Okay, any questions about that? Okay. And basically that's all updates we have. We have meetings with our convenience to discuss some bits in private. But yeah, all other things are going well. So right now we have five effective projects after the first relations. Yeah, hopefully we'll have four or five projects after the second relations. And we're looking forward to see more demos. Does anybody want to add something? I have nothing to add in terms of status from mentors, but I would like to say that I've been watching everything from a higher level and I do think everybody is doing a phenomenal job and I really would like to just congratulate everybody for making it this far and continuing to put in the effort. It is not, it does not go unnoticed. Yeah, that's possible. All right, we're over today. We ended four blog posts related to Google Summer so for working house planning and then for planning management from multiple branch pipeline and for Minecraft management and framework for removing all Apache Kafka we have a station blog post. It should be a lens soon. In addition to that, we should also have some other blog posts in common. For example, Mark is working on the blog posts for external workspace manager project. Now there are two blog posts right now. Maybe we will also have some kind of summer for promoted builds. So yeah, stay tuned for the updates. But yeah, basically if you have something more to it if you want to post a blog post to summarize your work as a part of the second coding phase just feel free to do so. And now we can integrate blog posts quickly because yeah, all automated data is updated and we have a lot of people around the copy editors side. So if you have a little bit of a blog post that you may have seen that there are more reviewers at the Jynx community that work on the speed and couple the review process. Okay, thank you. Mark, yeah. Okay, so I tried adding blog post to the Jenkins IO infra. So what I found is when people are adding blog images there is no proper guideline for that. So it's just scattered around in different kinds of folder which do not follow a pattern. So maybe we can add it or something. Yeah, we had the same feedback at the docs submitter. So if somebody should write to these guidelines. So I can probably put an action item for me to go through this topic. Because yeah, we definitely have some guidelines. Our original guidelines, so you're saying that when you submit a blog post please add to date to the folder image. So if you go here that there is content images, post images. Here you can see folders with dates. This approach was not very convenient for people because each time you need to move the date for blog post publishing. And it happens often then you need to rename this folder. You need to rename all the references in the blog post. So basically it's plain. And you may see that many other blog posts actually opt it out. And I guess that we need a policy for that. Yeah, right now there is no policy. Advice is to not use this format and use something like that for now. Or maybe something which is convenient to just meet in the middle because you may see that there are some blog posts which just reference the months. For example, if you submit a blog post now you can make a safe assumption that it will be landed in July. And hence you can put July here. It's a mess right now. Does it address your comment? Yeah, thanks. Okay. Any other comments or proposals or topics to discuss? Can I ask a project specific question? Yeah, there is no other questions left. So I had sent an email to the developer mailing list yesterday and there was no feedback and there's no feedback yet. So should we proceed with making it a separate plugin or continue with it in those strategy? Yeah, that's a good question. So I blocked this that right now. So for example, if you don't need the decision by tomorrow morning, I would try to facilitate it a bit. But yeah, if you need decision right now then you probably, you don't need to wait for the feedback. So basically it's what we were discussing yesterday at the meeting. Yeah, yeah, so I'll put my comments today because yeah, my beta didn't comment. My preferences actually have a standalone plugin now. Yeah, let's see. I'll try bumping the question a bit. So let's see. Maybe by tomorrow morning. Yeah, so when you send in the questions to the developer mailing list, it may take a while to get feedback, especially if you're working week because people might be busy. And sometimes takes several days to get feedback. But yeah, I think that here we can facilitate it a bit. And yeah, if any of the co-participants or viewers uses a role strategy plugin, please comment in this discussion so that we can decide what is the best approach. Yeah, thanks. Yeah, thank you, Tom. So yeah, I'll try to pink it a bit. Anything else for today? I think we're good. I just want to mention one thing. As I wrote in my proposal that I needed a 10 days break since my placement session of college would be starting from July 20th. So it wouldn't be a complete break. So I'll just have some other commitment during that time. So maybe there would be some intermittent work during that period. So I just wanted to mention that. Yeah, so basically, yeah. I was saying thank you for bringing that up, Prachi. I completely forgot. And also to add to what Prachi has said, we will still be doing our evals for the July 23rd through 25th timeframe. But right after that is when Prachi will be taking a break through school. Yeah, right. So basically, yeah, even if we have these days, so basically these days are just for doing a presentation online meetup. Then yeah, you can prepare everything in advance. So it takes just one hour of your time, maybe two hours of your time. So, but yeah, again, university is a top priority. So if you can dedicate a couple of hours, you can find the solution. What's your state, Prachi? Okay, so I do not have a schedule at the moment. So I'll keep it, keep you guys updated with that. But I do not think there would be like much issue if it's about the dates, because maybe timing could be an issue that we can fix it on the due date. So I do not think that preparation for the evals would be an issue, but my commitment to the work between this period could be an issue, that's it. Yeah. I think you're gonna be largely okay, Prachi. I think what we, as we discussed in our weekly meeting, is that we'll do a dry run prior to the eval, and then you will be able to just pop in for the eval. And then we know that you're gonna be, your participation will be sporadic after that. But if I do understand correctly, and correct me if I'm wrong, that you will be able to do the eval, but not much else. Eval demo, excuse me. Okay. Yeah, that's what I meant. Yep. Yeah, I think that's fine. And yeah, as long as your mentors are fine. If it's required, then I can work like little extended time on the project. Well, just discussed with your mentors, because as long as Marky and other stakeholders are fine, we is an organization of fine as well. Thank you, Oleg. And yeah, Prachi. Yeah, we've discussed this and we're completely fine with this. Yeah, right. Or from a mentor standpoint. Yeah, so, yeah, that's fine. So now we need to schedule additional overtime right now. Yeah, just coordinate everything with mentors and if the project is successful, yeah, you can be successful with one coding phrase and two coding phrases. Sometimes projects are complicated by then to the second coding phrase. And then the rest of the project is quite relaxed. So just talk to your mentors and have everything is fine. That's okay. Okay. Okay, thank you. Yeah. Anything else to discuss today? Oh, nothing for me. Okay. Thank you. So then I'll just stop the broadcast. Thanks a lot to everybody who participated. If you have any questions, let's use my name please and I will make sure that we send updates and doodles this week. Okay, I'll stop the broadcast.