 Yeah, we are. So good evening, good afternoon, and good morning in whatever time it is around the world where you're listening to this meeting. So this is the GSOC office hour on May 18th. We're in the middle of the bonding period. A lot of activity happened. And still ongoing. So we're not going to waste too much time in saying hello and telling funny story that's before the meeting starts. We're going to go immediately. I see we have, I believe we have all the projects represented. So what I'm going to do is ask, generally, I asked to the contributor or participant three questions. So what was achieved this week or the week that just was completed? What is scheduled for the coming week? And are there any worries, impediments or things that keep you awake at night where we can help? Good news is also welcome. But generally, that's before. So I suggest that we start immediately. On my list, Vendit is first. So Vendit about building Jenkins with alternative tools. So tell me what happened the past week. We had our first meeting on May 14th, and I have created my bio. We have set up, we have set up our project based details. My first contributor blog post and a public report for code development, where we will also set up the project wiki that will that will have the in depth project plan for the project. Okay. What do you plan? Go ahead. And an initial email to Jenkins.dev.googlegroups.com is still pending. That will be done by today or like tomorrow. I'll send that to Chris and he will send it to the group mailing list. Okay, that sounds good. And what do you plan for next week? Do you have still because I think you ticked most of the boxes for the bonding period? Yeah, I have my exams got preponed and they are now from May 22. So that was a nice thing that I take most of the boxes and all of the remaining boxes will be ticked by today. So I would start. I think I'll see you in when the coding period starts from May 28 because May 27th is my last exam. Okay. So a general comment here. Thank you, Vendit. A general comment here related. So I will say it often. So work and studies. Go first. You just need to say I have this this issue or this planning issue just say it and we're going to find a solution together. And generally the default value is anyway, exams, private life and work have priority. GSOC is important, but we'll find the balance together. This is very good. Vendit, any worries beside your exams? No, everything is going smooth till now. That's what I think. Does one of the mentors want to add something to Vendit's summary? Yeah, so yeah, everything is going fine. I mean, this is going great. I mean, I saw the initialization of the repository for Gatsby and Antora and yeah, I mean it's fine. Very good. Thank you for sharing the status of that project. So we'll move to unless somebody else has a question or so. We'll leave a gap of a couple of questions and we move to the next project. Okay, let's move to Jakruti. I have a doubt that I'm pronouncing the first name correctly. I apologize. So I need to learn the correct accent and the correct intonation. So anyway, bear with me if it's not correct. So this is about the adding probes to plug in health score. So tell us what happened the past week? The past week, I mean, before Jitok, I was already working on adding a new probe. So I'm continuing the same thing this week as well. I'm struggling a bit with the test cases. So I'm going to finish it as soon as possible. And I've already created my bio page and updated the project page and only writing the blog is pending. So I'm planning to do it by this weekend or by next week. We already had two meetings in which Adrian firstly the ground rules and in the second one he explained my mistakes in the test cases in detail and everything. So I think I'm progressing pretty well. Very good. What's what's planned for next week? You already mentioned it so you're continuing. Yes, I'm continuing the current work. I hope I finish it by next week and I will also make sure that the blog is completed. The blog about my project that we are doing. It's important to communicate correctly to the community. The community is now very curious. And so we need to show what we're what we're doing and so so and then we can move on to the coding. Very good Jack Ruthie something that keeps you awake or worries you how are you feeling. Thank you so much. It is just only that I'm so great that it might happen to you that I will not be able to manage my time and my work and so both at the same time. But for now everything is working fine. Let's see how it goes in future. Okay, don't forget to reach out and discuss that with your mentor. If you find you don't find there is no compromise or it doesn't work. You can always reach out to me or Chris or another or admin but I think based on my experience. It's never necessary to escalate but be careful to maintain a good balance. You will hear that very often from me. Thank you. Very good. Thank you very much for your report. Good work. So, I think you're all going very fast. Do you want to add something to Chakruti's report? Not really. I'm happy with the progress and we are moving forward by taking off the items that we're supposed to do during the community bonding period. Her PR just got merged about updating our project page on Jenkins.io and she's actually working on the blog post next and yes. So all the things are going great and she's also working on the code side by side which is not a priority but she is. So that's a good thing. Very good. For the others, the difficulty here with this project is that Chakruti is free during the weekend where Adrian is available only during the week. So there will really experiment asynchronous work and so there will be some challenges there but it really looks great because here this period now I'm impressed so this started well. Okay, we can now move on to docker based quick start with Ashutosh. I pronounce your first name correctly. Yes. Yes. So you already know what is the question I'm going to ask you go ahead. I have uploaded my bio on Jenkins.io and we had some issues scheduling the call and we have decided to schedule it for tomorrow. So we didn't have meeting yet, but we'll have it tomorrow. Okay, and this was mainly because you had exams. Yes, yes. And then one of the mentors was on PTO and one of the other mentor was not available until tomorrow. So that explains why we are so late. It's not true. Go ahead. I was wondering about said he hasn't confirmed if he will attend or not for tomorrow's meeting. I think I got an email from him saying he would be attending tomorrow at 3pm his time. Okay. Okay, so put that. I say it has been on and off. Yes, he just got off for my vacation. Yeah. So, well, let's continue. So, well, you're starting first meeting setup. And there you will discuss on the various deliverables. So, you're a little bit late, but no problem. We have Slack channel, which is linked to the CDF Slack workspace. We also have now a Gitter channel, which is linked to Jenkins. What else? Am I forgetting something Ashutosh? No, you got everything I think. I'm going to discuss all the details tomorrow during the meeting. Yeah. Okay, Ashutosh, is there something that worries you? No, not right now. Time will come. Yeah. Don't worry, just start. Hey, great. But it's a ritual question, but I it's also that the other the others here also what what's happening on a project. Next, the last one is a GitLab plugin modernization with a turning the camera on. Great. Now you need to help me. I is harsh. You're in is it pronounced that way? Is that you're the first name? Yeah. Well, I think we discussed that already. So harsh. Go ahead. Tell us what happened. What is going to happen? My exams are over. So I am going to have my mid semester breaks. So things will be much faster. Now I have to upload the bio. I did the bio. Yeah, the blog post. Yeah, the blog post. I missed it. So I will add the blog post and my project plan is going to be completed soon. So we'll have the discussion tomorrow regarding the technical details of the project plan. And I think from 22nd or 23rd, I'll start contributing to the project. That's why. And you had already meetings. Yeah, we had meetings. Tomorrow is our second meeting in which the project plan will be tomorrow is our third meeting in which the project plan will be discussed. Okay, very good. Do you manage with the time or you and mark because you're very far away nearly the other side of the earth. No, no problems at all. Okay, good worries. Nope. Everything is fine. Hey, good. Okay. Does somebody want to raise concern or want to share something globally. I think we're starting fine. Everybody gets aligned and have a nice week. Oh, I do. Yeah, for you for different projects. I'm not sure how, how the other partners are doing it. But I think we're supposed to engage the community more. So I suggest like, if, if like data projects haven't already done so, like, you should talk to your mentor and have either your lead mentor, or yourself, write an email to the community, explain your plans. And what you plan to do and, and also get feedback, because like the stakeholders who may want to know more before you proceed, and they may have like some suggestions for you. Very good point. Chris, what channel would you suggest to use for that. I suggest to use email to the developer. Yeah. And well, alternative, if you want to go broader, the developer list is, is great. The, the alternative, not alternative complimentary that would be on discourse on the main channel just saying hello. I think I think they're two main lists. So one is for users. So, and, and our for developers. So maybe if, if sent by email, both channels should be used. And discourse. It's a good challenge to both doing both will begin. Yeah. To discuss in the next project meetings. I think that the point raised by Chris is is to the point is exactly we need to engage more in a community to get them involved the blog post is important. And, but we need to do a little bit more. Thank you Chris for for that. Anything else. That's a very good question to crouty long enough. That was stupid answer. It just gives me a few seconds to think. The rule of thumb that I had was around 800 words, which sounds already a little bit long. What would be in the blog post is who you are. What's the project is going to be about giving a few links, or the people that want either to hear what's going on, or to have more details on what's happening. And then maybe a conclusion on how are you feeling about the, the adventure. So between 400, 800, 800 words one page. Does it sounds logical. You guys first like write it in the Google Docs and share with the community. Make a PR in general. Well, you can first discuss so make a draft in Google Docs and share it with your team. So the project team, but to publish the blog post is through the Jenkins.io. I'm not sure that understood the question correctly. Did I answer your question. Yes, yes. So you do a draft just to see is it too long or too short. You will, you will feel it in your, in your guts. In Jenkins.io, I think I have to use a doc syntax. Yeah, that becomes a little challenging when you write and also use the syntax at the same time. Okay, so here we all have to to learn quite a few things and and people are there also to to help a doc is an extension of Markdown. There's some characters. And here. This is something where I can help technically I can't. I'm too rusted for that but documents and blog posts and Jenkins.io. I know enough. Start with a draft in Google Docs and the rest we can help you. Okay. Great. Thank you very much then for joining this this meeting I'll, I'll keep it short that way. I think it's great to share where we standing and we grab ideas from the discussion. So, if you can't make it to the meeting is no problem, just make sure that there will be somebody representing the project, either mentor, or dog wants to come in, but he has to wait. Okay. Okay, thank you very much all have a nice rest of the day. Good work during the, during the coming week and see you then. Next week all. Thank you everyone. Bye bye. Thank you. Bye everyone.