 Okay, good evening, good afternoon, good morning everybody. This is the GSOC 2023, first office hour for the selected contributors, the team setups were in the middle of the bonding period. So the date of today is May 11th, for the record. So welcome everybody and everyone who attends who will listen to this recording. We will not, so it's in a loose format, but generally we go in these meetings around every projects to see how people are doing and remind of the deadlines and listen if there are any impediments or worries around there. So let's walk through the project. So we started the bonding period there. So the bonding period is that everybody can put a face on the name, know each other, setting up regular meeting, communication channels, so there's a lot of work to do. So it just started and I just would like somebody from the plugin health score project. I see that Adrian turned on his camera. Is there somebody else from your project there? No, I think that I'm alone. Okay, you're alone. Can you tell us where you're standing? I believe it will be a little bit short. Yeah, it will be a little bit short. We have a meeting set up just after this one. So I will jump right away to a bonding meeting that we set up. Not me, Jake set up with Tiraj, Mustafa and Lagruti. I believe that will be the first meeting. I think so. I just come back from a vacation. So I'm just also trying to figure things out. We're sorry for you. We're sorry for you. No, no, yeah. But no, so yeah, we have the first meeting set up and we'll have more things to say for the next office hour. Great. So as you it's just starting, you have no issues or worry? No, no, not so far. Everyone accepted the meeting. And I think we will use it to also figure out what time schedule is best for everyone and so on. So even I believe that the first one is not great for anyone living in India because time zone there. But it's the first one. So we'll figure things out and so far not great. The next project is building Jenkins I.O. with an alternative tool. So Chris is the lead mentor. Is there somebody else from the project on there? But Chris, you can take the word and go ahead. Maybe, but Jeff, do you want to talk a few words about, do you want to say something about the projects progress? Yeah, so we set up the meeting. With Vandit. So I think this Sunday we'll be having it and we decided the time zone and also it's good to go. We'll be having the first meeting this Sunday and I think night it is. So other than that, there's no extra update. Okay. Good. Thank you for that report. Everything is going well. Don't forget to update the project page at least with a reference with your meeting notes and all that. So that if other people want to know where you're standing and what you're working on, we can have a look there. So, and I guess, Rajiv or Chris, any worries right now? Well, we made it to worry about how to communicate, how to coordinate efforts with the community. And that made me take more time than we have. Let's see what we can do. Okay. Good. Here, if you run into bigger worries, we can discuss it either here or in one-on-one and see, but I have noted it down. Good. The next project is Docker-based Jenkins Quick Start. And we have Hashutosh with us. Yeah. And we have the, hey, great. Welcome aboard Hashutosh. Congratulations for the selection. Thank you. How are you feeling? I'm feeling pretty good. And scared? No, I don't know, but intimidated. How about the exams? Oh, yeah. The exams are going well. And they'll be over tomorrow. Okay, fingers crossed. Okay, great. Bruno, do you want to make a summary where we're standing? On the middle of the bridge, I guess. It's still difficult to find a time slot compatible with the mentors myself and Hashutosh. We don't have the answer yet of all the commenters, so we don't know. Hashutosh is planning something tomorrow, I think, after his last exam. Hopefully, we will make it. Hashutosh created a Slack workspace. Also, we have something on the Gitter. But we haven't planned yet a regular meeting. I think we'll do that from next week on, because Hashutosh has exams this week, so I won't put any pressure on him. Hopefully, this week. We'll see that later on. Would you have anything to add to that? I have one point. We are thinking about meeting tomorrow. Leo also said he will be available tomorrow, but he won't be available between 13 and 17. So tomorrow seems like a good time, but he didn't say anything right now, so we don't know what to do. Don't wait too much on Saeed. Go ahead with... Yeah, we'll see that tomorrow. I guess, Jean-Marc, you wanted to talk about Slack. Yes, so you've seen and it's good that Alyssa is on the call. So it's a very good initiative, Hashutosh, that you created a Slack workspace. For the team, I've made some comments. The biggest comment I have is that the conversation will be in a closed circuit, which tends not to be positive. Because when people don't know what's happening, then you have suspicions that build up. So my suggestion is Slack is a perfect good tool. Don't forget that the free version, unpaid version of Slack, you can't keep the history of conversation longer than 90 days, three months, I believe. So this is one of the advantages of GitR, but here Slack is a handy tool and we use it. My recommendation for the team is to ask to open a dedicated channel on the CDF, Slack workspace. It makes it also easier visibility. A lot of us are already connected to that. And so it's one less Slack workspace to monitor. Hashutosh, what is your feeling about that? Yes, I also think it's better to have a channel on CDF Slack. Yeah, okay, good. Alyssa, do you know how to do the magic to have a public channel created on that? So that would have to be created by somebody in CDF, so I can reach out to them and ask. But what do we want to do? Do we want to create, is it just one Slack channel for all of us, mentors and org admins or do a separate project? So no, it's just one project here in this case, the project from Bruno. So and use the project name, well I can suggest by we can use the existing chat Slack channel for that. So it would be gsoc underscore and what is it? Docker Jenkins, Docker based. Yeah, Hashutosh had a good name for that, just make it. I'm going to, I think you're on the Hashutosh Slack workspace, Alyssa? Yeah, I invited her, but I don't know. Yeah, here, we're just going to have the conversation about the naming convention, so that Alyssa knows. I've just created a channel for, I was able to create a channel on the CDF Slack space. So it's called gsoc-2023-darker-quickstart. Okay, so you were able to create it? Yeah, we could, I'll see you too. Anyone can do it, I think. Okay, yeah, because in the past it's somebody from there that would have to create it for us. Okay, but that's good to know. Yeah, I can create it. Even simpler, and then I'd really invite Hashutosh. Is, are you in the Slack space yet? I see you, I see you, hang on. But I invited him. Yep, I've just invited you. So Bruno, we have, like... Said you probably don't have. I'm not sure if he's here, he probably is. There it is, there it is, there it is, present in that Slack. I think it is. Okay, good. Anyway, I'll leave you, check it out Bruno, go ahead. So it's just a channel, and it's not as detailed as the workspace you had created Hashutosh, but we'll have to do with that. But it's not have to do it, it's all the functionalities are there. The only additional thing that the workspace created by Hashutosh was that you could create several channels, which is for me overkill for the project. Okay, fine with me, thank you. It just, don't forget, we need to make sure that we work in the open. It gives on the positive side the ability to whoever is interested in the topic to know what's going on and eventually to suggest directions or that. On the negative side, hiding things generates suspicion. Yes, but I guess that was not the initial goal of Hashutosh. Hashutosh will have to have a link to that channel workspace in the GSOC documentation. In the GSOC blog post, you will have to write, I guess, in the coming weeks. Yeah, and also on the project page, on the project page. Anyway, so if you have questions, go to either Chris or myself. Okay, there's this problem solved. Bruno, are there questions, impediments, worries or Hashutosh? Not yet, not at all. We just said this. Thank you. But you're all starting great. You're, I see, a lot of energy. The last project is the GitLab plug-in modernization. We have Harsh, there he is. Nice, and turning the camera on. Oh, thank you. So I can put the name. Congratulations. Yeah, we can keep the congratulations aside. I have completed the project description page and also set up the profile thing. And I'm currently working on the project plan. And the blog post will be written in the last week of the community bonding period. So that's where we are. And the meetings are going on pretty well. We have decided to keep the meetings on Friday. So that's what's happening right now. Very, very good. I have a few, I've seen your project page. Your project page is up. That's very good. I have a few suggestions of improvement, things that, but we have the time to do that. And basically the link to the meeting notes. I don't want to, I want to reassure myself that everything is going well. And I do that by browsing through the meeting notes. The link is... I think the link to the meeting notes was there. I added them. Okay, so probably my mouse was not correct. I'll double check that. If I have a worry, I'll contact you. I'll check. I think I added it. No problem. These are just details. It's because I'm lazy. Yeah, if I found it, then I'll add it. Don't worry about that. Right. No problem. Do you have worries, impediments? Not yet. I'll ask more on the Gitter channel. I cannot have technical doubts here. Okay. What I'm very happy to see is that the contact is established on all teams at various paces. Discussions are starting. There are also things that start to be written down. So making great progress. So we're on the right track. Based on our experience of last year, let's not waste the bonding period. The bonding period flies by quickly. And we can prepare, set up the project so it can be used. And I see it's moving along very well. Okay. Great. Are there more general subjects or stories to share? Yeah, kind of a general question. Go ahead. So can we start the coding before the coding phase in the community bonding phase itself? Like simple adding code, like adding dependencies and stuff like that. We can start way away, actually. I'm serious because that's what I did when I was doing GSOC. I started doing the bonding period, not after. So you can start before. So just make sure to discuss it with your mentor so that you put your energy at the right point because I see that you're moving forward quite well. And it would be just stupid for you to sit down on a chair. You see me maybe turning my thumbs here waiting. And good question. Good question. My exams are currently working. So I'm quite slow with it. Things will be faster. And I think I'll be able to complete the project plan till 19th. So I was thinking of starting to contribute faster. That's why I asked. Right. Good. Don't forget, studies for first. So the exams have priority. No, it's going well. I'm not going to, I'm not having any problems. It's going well. They are mid-semester exams. So I have less syllabus to cover. Okay. Well, just a reminder. So if you're running into troubles or also, let's discuss it either here or one on one. But I'd like to emphasize the priorities and no late night working. It's the father in me. I'm calling it that. Okay. Good. Something else, another comment. I believe that we have a great start for this GSOC and a bonding period. Very well. Then I wish you all a nice rest of the day. And we'll meet, we'll meet next week. So we probably will have less attendance from Europe. I'll be there next Thursday is a festival here in Europe. And so it's a public holiday. But let's keep this weekly rhythm. And if nobody shows, it's okay. But let's share the progress and seeing the others moving. It's always very, go ahead Bruno. Stupid question, but have trouble distinguishing from bond holiday, public holiday, festival. How do we know when it went to use what word? Yeah. Just use a word and see if people are frowning. So I don't know. I don't know. I use festival because I believe this is a word used. Maybe we can use to our Indian colleagues. In India, yes, for sure. Festival is religious related, which is the case of next Thursday. Which is mainly not only Catholic, but also in other Christian religions. It's also an important. I'm not sure. But so using festival holiday, bank holiday is just, but Chris is in a country with, or at least in the city with more British culture. Yeah, we do use bank holidays. Yeah. And when do you use bank holiday instead of festival alone? Well, it's kind of weird because in Hong Kong, public holidays are not the same as bank holidays. So it's like for some people that only get bank holidays, which is like some days less than all public holidays. Well, Bruno, you asked an interesting question. I believe I'm going to read a little bit tonight. Sorry, another night reading instead of sleeping. Well, no, but I'm, these are interesting subjects and show the international culture and being aware of the differences. Anyway, this is not a super important topic, but just be ready that next Thursday, the full attendance will not be there, but I'll open the meeting anyway. Okay. Yeah, I have, I have a problem here. It's marked back from the city con because the community bonding period meetings are not uploaded and I will love to see them if I could. Good point. He just came back. He came back yesterday. And by the way, but he's been awarded as the community MVP. Yeah. So at CD, at CD con, he got an award and a well deserved award. I had a meeting with him a little bit earlier. It's still very early his time. So reach out to him to ask and he has a lot of catch up to do right now. But ping him. No, no problem. Yeah, I'll ask him the next community bonding period meeting. Yeah. Okay. No, no problem. Okay. Good. Let's stay here. Thank you for everybody to attend. Good work. See you then next week or early. Bye bye everybody. Bye. Bye.