 recording is on a good evening, good afternoon, good morning everybody to this last office hour of the Google Summer of Code bonding period. So I think all projects are represented here, so we can go immediately. I have one general, no I have two general comments but I will make them at the end of the round table. So as usual the round table will be going project project to listen to you sharing what was done during the last week, what was achieved, what is planned in the coming week and if there are any impediments or difficulties or things that prevent you from moving as you would like. So first project on my list is a plug-in health score. We have Chakruti there. Tell us what happened last week and what is going to happen. Last week, like I said, I'm working on the test cases, so this week also I'll put you to work on them and I have almost completed the test cases. So if everything goes well before the bonding period ends, I'll just contribute one pro to the community. And about next week, as of now, I haven't discussed anything that I mentioned. Okay, very good. So I've seen that all the deliveries for the bonding period, everything has been done. Block post, everything is settled, and you are already with your teeth in the subject and going ahead. Great. I forgot to mention about the block post. I also had to complete that this week. Here there's no problem and nice work. Well done. Adrian, do you want to add something? No, not really. Everything was done when I asked Chakruti last week to do the block post and the different entries. The bio was already online, so that was easier, I guess. And I don't have any worries for what we do next because we have a lot of things to do. Already listed in the repository issues, but also in Chakruti proposal for JSOC. So there's plenty of things to do, but we take them one by one. So looking forward to merge the first pull request for Chakruti. Not her first pull request on the project, but her first in JSOC context. Well done. So that goes well. I had a more general remark or observation that I can hook in here instead of waiting for everybody to share. I've seen that for pull requests that are submitted for Jenkins.io, the mentors, so the block post, for instance, and that are not automatically notified by the system. And so a good advice is when you do on Jenkins.io or other repository, but Jenkins.io, make sure that in the comment you explicitly name the mentors. You would like them to review your PRs, so like the block post update to the project description and these kind of things. So it went a little bit fast. And Chris or myself, we got involved in the review, although it's normally the task of the mentors to steer that. So don't forget to mention explicitly your mentors on it. In your project, in your repository, I assume that there the notification go correctly, but here I wanted Jenkins.io is configured in a special way. Okay, good. Thank you, Chakruti and Adrian, for the good progress, good news, and for your report on that. Leave a little blank if somebody wants to jump in on that project. Yes, just want to say she's doing really great. She has this nice ability to be after the problem. We keep her giving her hint after hint, and she catches that and then finally delivers what we were expecting her at the first place. That is very nice quality. Good, well done. Now, Dhrash, don't say that too early. She has all the summer to perform in the same way. No, no, well, I see this project. That's a very high bar for herself. Okay, thank you for your comment. Very good. Building Jenkins.io will alternative tools. So, Vandeet, tell us. Hello, everyone. This week, I didn't do much because I had my exams. I have them till 27. But for the next week, we'll be doing a lot of stuff. I have already set up an experimental repository where we will start developing Jenkins docs.ginkins.io that was mentioned somewhere in the developer groups for to be the top URL and everything will be redirected to it later on. So, yeah, that I have set up that and we'll start working on that. The project structure and everything. Good. Beside your exams, you don't have any worries. Yeah, everything goes well. Everything is going well. Great. Rajiv or Chris? Rajiv, go ahead. Yeah, so everything is going well. I mean, last meeting, we discussed about UIX in this. And also, we replied to Gavin and Basil and Gavin, I mean, the comments, the very insightful comments on that, what we're building. Also, we discussed about some, we have questions like SEO and how SEO is going to affect the things we are making Jenkins.io. Mark has good view on like the search thing. So, we talked with Vandeet and I think he's doing well. I mean, also, we are like, I think Vandeet is connected with, I think, this Discord, I mean, Antora Discord. So, we are just like figuring out the MLS, how we can have plugins and all that. So, they might have a good insight, maybe. So, yeah, I mean, everything is going well. That looks good. Okay. Ready to go. I think all the bonding period deliverables are okay. So, I've seen the blog post, the project page is updated. I think we're good. Okay, can I say something about the project? So, I think the progress is good. But the thing is, we still have to finalize our project plan. That's something we could work on over next week. So, even Vandeet has like ended by then. And that's about it for me. Good. Good point, Chris. Yeah. Good point. And especially seeing that we have interests of some high profile contributors in the community. It's important that we are very clear in what we're going to do, what we're not going to do. Great. Any other comments on the Jenkins.io project? Good. The next one is Docker based quick start. Jenkins quick start examples. Ashutosh, you had late starts because of exams. Yes. We had a first meeting and the meeting after that. And I have created an experimental repo for the project. And the project page is updated. The blog poster is still in PR. PR is open right now. It will get merged tomorrow. By tomorrow. Yes, progress right now. Right. Okay, good. A little comment. I think you heard my advice earlier. So don't forget to put Bruno and other... And Said. Yeah. Yeah. And Said in the comment. Otherwise they don't know that the PR is ready. Yeah. Ashutosh is also communicating via Github. But yes, that would be better to be notified via Github so that I get even notification on my phone. So I can't miss it via Github. Yes, I'll remember it. Thank you. Ashutosh, are you blocked for the polishing of your blog post? Do you see what you need to do? How you can do it? Because I honestly, I replied very quickly to the PR and said, hey, hold on. I went and I didn't help you. So do you know how to move on? I think I get it that the people who don't know the before context can't understand it. Exactly. Okay. Try to read the text with the eyes of somebody who doesn't know the project and be sure that the subject of the phrase that we know what you're talking about. So this is going to be done on what? Because it can be in the circumstances. This was a little bit needed some clarification. Good. So this is going on. Moving. Don't forget to ping your mentors on that. Ask for help or for guidance if you don't understand the comments. I'm just watching. Bruno, is there something you would like to add? No, you said it all. Thanks for the review by the way, Jean-Marc. I would have said more or less the same thing, but you were quicker than I was. So thanks for your help. Sorry. And that's all for my side. Okay. Good. Hola. A big drink there. You need a big water of warm tea for that. I leave a little blank if somebody wants to add something for that project. So we're good. And we're going to move to the last project and hear what Harsh, yesterday. Yeah, there is Harsh, GitLab plugin modernization. So tell us what happened? So the project plan is completed. We are moving towards the first milestone and the community bonding checklist is also completed. So I think we are good to Ready to start. Yep. I'm working towards my first milestone. And which is what? I'm just migrating the rest easy to GitLab 4j. That's the first thing then I'll migrate the webhook thing and the proxy thing. It's discussed in the project plan. We are having technical discussions on the GitHub channel and things are going great. Okay, so I can follow. So it's a good point. I need to read the project plan. Good point. Any worries or impediments? Not yet. We are having technical discussions. So we have that in the GitHub channel most of the time. So I don't think I should be discussing it here. Not the purpose. But I like to hear here we struggling or it doesn't work. But here, like others, you're with the teeth in the subject and you're moving it. So very well. I like that. So as the general summary, a bonding period achieved the objectives. People know each other. Things are now settled, how to communicate, how to work. Presentation to the community has also been done some little details, but because of the late start for a shoot us. And everybody is ready to start next week with the actual coding base. Channel comments or reminders. So we're starting now you have your project plan. The next important milestone global milestone is that mid July. So that's in a month and a half. We'll have the first intermediate checkpoint where we'll have a review of your work and where we need to report to Google. Yes, the contributor is working as expected and we can continue to fund him. Everything is going fine. So there's a purpose of that evaluation. The second thing there is that we're going to ask the four of you to make a 15 minute presentation of your project and what you achieved in these first six weeks elapsed six weeks. So it's a small presentation. Think about that on time will give more details. Don't get scared about that. It's an interesting exercise in your mentors are going to help you also in that exercise. So this is around July 14. Second thing, just to be sure that we're starting on the correct foot. So I'll have one on one discussions with mentors and also with contributors starting in June contributors. I'm going to propose a one on one meeting with each of you. Starting the second week of June, third week of June and we're it's just for me to confirm the feeling that you're you're good. You're feeling well. It works well. You have a good relationship. It's also a way to share with me if there are some things that could be smooth or could be improved just to give an opportunity because I like talking to people and hear their personal experience and be sure that they're enjoying it. I want it to be a fun experience. But two, two important things I wanted to share. Are there questions, comments or can I just add with reference to the Jenkins online meetup for mid for the July timeframe, the midterm presentation. So we do have presentations from last year that you can use for reference or inspiration. If it helps you in any way. So I will include that in today's meeting notes. So feel free to reference back to it. It's it's also on our YouTube page. And it's also on our Jenkins online meetup page. But I'll reference it in our meeting notes today. Yeah, super tip. Yeah, that's true. Good tip. Thank you, Alyssa. You bet. Other comments, questions, stories. Then I wish you all a nice rest of the day. Thank you for attending. Thank you for sharing what's happening. It helps everybody knowing what's going on. So see you next week or during a meeting or enjoy the rest of the day and the rest of the week. Thanks, everyone. Thank you, everyone.