 Hello everybody. I will not do the time zone thing. Welcome to this edition of the Google Summer of Code 2023 edition. Thank you to be here. The purpose of this meeting is to do the usual round of what's happening with people, what fun they have with their projects, what were the achievements. Another important topic is I want to double check whether the proposed date for the presentation, so June 6, is going to work for most of us. So I know that Harsh is going to record a presentation and I heard rumors that Vendit will not be available. The six Vendit, will you be able to present in person or will you need to record? I have my exams from three, but I think and Chris also suggested that I should present it in person and I think I can do that. I have managed my studies in that way. So I think I'll present it in person. Okay, good. I appreciate the effort. Very good. We'll come back on that to double check that all balls are tightened that we're good for that. So first of all, let's walk through the project and see where we're standing. First, I don't have my list because I don't have, I don't know, I'm going to start with Chakruti because she's upper left and please yell if I mix the things up. Chakruti, tell us what fun did you have this week? What happened? What can you share with us? Hello everyone. So this week I have a good news to share. It didn't tell me just now that my first cheese off broke will be live in production. So this is something I have to share. So it's so it works fine. And second thing, the probe I was working on last week, the third party repository detection probe that probe actually requires what I could say that probe is a little complex for me in the beginning because it has different because a child can have a parent form in different ways. So I discussed with them in class and the best solution was to actually make an effective form that we can decide which child has which parent. So this project, this part of the project is on hold now and I just suggested that we do it in the second half of the season. So now I started working on Jenkins security scan program. In this program, I have actually based a branch by a past contributor and I'm working on writing. So most of the code was done by them already and I'm working on writing the test cases for the probe. That's all the data has. Good. Hey, that sounds interesting and good, good success. Can you just remind me when is your probe going on production? He didn't told me by the end of the day. Shortly. Yeah, shortly. Shortly. So the drinks are on you, Chakruti. So you have to send or open a virtual bottle to everybody and congratulations. Very good achievement. Thank you. So very good. Adrienne, do you want to add something? Yeah, the fact that we postponed the probe that Chakruti worked on from a week and a half was due to something that I've seen and that I made a mistake on my side making an assumption where the project structures are identical everywhere and so on, which is not the case. And because of that, what Chakruti did was not wrong, definitely not, but was assuming the structure and trying to deduce some elements from the structure, which is wouldn't give us a proper result. So we decided to postpone the completion of that probe. We are definitely not throwing away what Chakruti did in a week and a half. We are just trying to come up with a service that will provide us the effective pump. So that's what Chakruti did. We'll be able to, rather than just reading one pump and trying to deduce errands and so on, we will provide the real pump that Mavin is using to resolve many dependencies and plugins and so on. And so based on that, once we have that entry to feed Chakruti's probe, our work will be able, we will be able to resume what she's done and it will be a better solution. So really, we didn't postpone because Chakruti didn't come up with a good solution, is just that the requirement for the probe to be successful and more than successful to be complete, to be trustworthy, was not met because of me. So things happen and it's good experience to see real life projects going like that. I'm really happy to do it because we saw that on Friday morning, my morning, so few hours from now, it was before or now, that's on last Friday. And Chakruti was able, we found a profile for Chakruti to work on during the weekend and so on, and she managed to switch context and so on really quickly. So that was nice to see. I like to hear these stories. That's very good and confirms why Chakruti has this smile. I always like the Chakruti smile. This said, do you intend to do some buzz about the first probe? Let's first see if it goes in production without problems. Normally, it shouldn't be a problem. I'm just waiting for a pull request on the Kubernetes management project to be merged, which should happen shortly. Technically, it's not Chakruti's first pull request on the project that lives in production. It's the first one in the JSOC project, in the JSOC context, but it's not the first one to live in production. Suggestion, the two of you, eventually you can liaise with Alyssa there, thinking would be worthwhile to either update the project page on Jenkins.io or look if a little tweet can be generated or a little blog post. I was thinking along the line of a blog post would be good, detailing your progress and what you've done. Then I can definitely send out a tweet and a LinkedIn. I think that would always be good blog post. Okay, especially as we're slowly reaching the midterm presentation and doing some public relation there, it's also a tip for the other projects. Bragging is something that our parents told us not to do, but let's be proud of the fun we had and what we've done. Thank you. By the end of this meeting, the probe will be live in production because the full request was just made. Good, so even we have it live here, so good. Modern technology. If somebody wants to add or ask something on Jack Ruthie's project, just leave a little blank and then we'll move to the next one on my screen here being harsh. Harsh, what happened? What did you have fun with this week? I created the plan for the second milestone and I discussed it with Mark and after creating the plan, I tried implementing it, but I faced some problems because of the difference in design of the old GitLab plugin. So the new GitLab 4G library has implemented its webhook quite differently because of the difference in class hierarchy that it has and the GitLab plugin is quite different with it. So I had to struggle a bit to try to get it work like I had to adjust some meetings with Chris just to discuss what the problems I was facing and the design problem that I was facing. So I'll have to work a bit more on this thing. 40 to 50 percent I wrote the code, but after that it got quite difficult. So I'll have to discuss more technical problems because in the previous project meeting, only Mark was there like Chris and Basil were not there unfortunately. So I was not able to get confronted with the project design. Like I thought it would be very good, but it did not because of the complexity that I had to face in between. So on that part I was not able to get the work done, which I wanted to do this week. Other than this, I don't have anything. Okay. I forgot what I wanted. Do you still have problems with your teacher? Giving you assignments, unexpected assignments in the middle of your work? No, it was not. I was working on that, but the difference is quite big to be honest. The problem was every hook even that was there in the GitLab plugin used was coming under the single umbrella, but what GitLab did was it divided into multiple parts and I have to change the design of the plugin itself for it to work, which is quite a cumbersome task. Harsh, it was more last week you complained that your teacher at school was giving you assignments, unexpected assignments, and that drove you crazy. Did he do that again? No, no, no. Or he's now happy. It was not academics. Like I was not able to get it done. It was not academics. Oh, okay. Good. Mark, do you want to add something to what Harsh explained or somebody else on the project? I don't have anything to add. Thanks, Harsh. We'll plan to talk further on Friday and I've still got more testing and more exploring to do. I feel like I'm behind schedule. So thanks for Harsh's patience. Interactive testing that you were doing with other plugins also. Good, but I like hearing these good stories and good mood. So also very good. Now let's move to Vandeet. Hi, Mark. Hi, Haridhar and what fun do you have and what can you share with us? Yeah, I had some fun this week. I completed the developer section completely with the images and all the broken links. I have completed the user documentation completely with the links and we had some issue with the data table API in which Chris helped me a lot because I don't know much jQuery and currently I have completed the guides, tutorials too. I'm currently working on the solutions page because it has a different layout and I will update the UI according to that and yeah, this is all I did. I completed most of the scripting part. All the links I was struggling with, I didn't have to actually use scripting to fix them. Okay, good. That all sounds good. I think Chris is the lead mentor on that project. Do you want to add something? Yep, so I think we have good progress and with other tutorials as well this week. So it was good to see. I think last week it was added but I'm still working at this week. So now we have users documentation, we have developers documentation, we have tutorials. Don't forget to brag about what has been done up to now. And I was not in the last meeting. We also have the demo site on GitHub pages. Why? Okay, I need to be careful. I have local interference here. My granddaughters just came back from school and I hear so. Let's continue. So we had jQuery, we had Harsh, we had Bandit. I fear that Harsh Uthosh is not on the meeting. Bruno, do you have a little summary to do? Otherwise I can't do it. We can do it together. I think the last week we had is the best one. We had to this day, we saw quite a lot of progress on the very first example. Well, but it's now well defined. We have beginning of script that do most of the tasks automatically instead of doing it by hand. So yes, it's showing up good progress and showing that just about everything can be automated before going to the next step. What else could I say? The next step could be difficult. We'll see. We are still trying to replicate what will be, what already exists on the Jenkins IO documentation regarding to Docker. So we'll see if Harsh Uthosh can make it easier for new commerce into Jenkins ecosystem. We'll see. Jean-Marc, what would be your input because you're an admin. No, you nail it. Very good. So we start to have automation. We start to have the pieces that start to fall together. We're still not there yet. But we're making progress. But I think you and I have the same problem bit. We are in a very exciting part of the project and we want to get it to progress faster. So we are very tempted to put some code with our own hand, which is bad. So we have to be very careful about that. Give some directions and not give the final code that already works. That's not the goal of Google Summer of Code. And I played guilty. Okay. No problem. So all four projects are making good progress. I think we're reaching a good point for the midterm presentation. Currently planned June 6th. So I'm going to do a round call to double check. So Jakruti told us and if she can confirm, she's good to do in-person presentation on Thursday afternoon evening. Right? Okay. Good. Harsh is not able to do it and he will record. Harsh, do you still hear us? Okay. Good. So it's because one recorded session is okay. Two recorded session, I'm going to lose my hairs and this is going to fail. Bandit said in the beginning, and you stop me if I say nonsense, although he has exams, presenting personally is much better and he's able to arrange to have an in-person presentation. Yeah. Correct. And Hashutosh is able to do an in-person presentation. Yeah. So we stay then with our current schedule for making the presentation on June 6th. Why do I always want to say June? July 6th. So Alyssa, do you need more information to set everything up? No. I think I have everything I need. So I will set up the meetup page for us. I'll set up the Zoom page, the Dalin information and I'll get the slide deck started. So I will be sending out the slide deck to all of our GSoc contributors to add their slide information to the deck. And yeah, we should go from there. And should we do a dry run, a practice run the week before? So I mean, oh wait, hold on. Let me take a look at my calendar before I open my big mouth. Oh, so perhaps next Thursday, we can kind of do a, you know, a quick dry run. Just see that the tool is working. And so, okay, it's so not the content. It's just you see the mentees are going to say this now comes an awesome presentation. But just to check that the video and the sound works correctly. So not a rehearsal of the presentation itself, but the technical setup for that. Is that correct Alyssa? Yes, that is correct. I will work on the page, the both the media page and the Zoom page today. So I'll send that information out. Okay, we'll do a check or we follow up for questions with the lead mentors to set up. Harsh, we just need to know what form will your recording be. So try to decide that. As soon as possible, the big question, because I'd like to try it out. So if you can just record with your tool of choice, a one or a 30 second video, so they can see that I can play it correctly. Is that okay for you? Will you be able to manage that in your planning? Yeah. Okay. Harsh, would you be okay if we took the easy way out and just had you do the presentation to us on one of our Friday sessions? And will they record it for Zoom? We could try that. Yeah. Then you then you have an audience. The benefit of that is you have an audience. And the audience will interact with you and ask you questions and give you something more than just, Oh, you're talking to a camera. There's the power of power in an audience, even if it's not always a perfect audience. I will need some rehearsals for the other. Oh, don't be shy. We're, we, we, now, so July six is the July six is the date. So that means it would need to either be this Friday or next Friday, depending on your schedule. So tomorrow or a week from tomorrow, or we can schedule a separate time. Maybe we talk about it tomorrow in our session then. Yeah. In the project meeting, we can talk more about this. Now we're putting pressure on everybody, but the calendar is ticking. The time is ticking. So we need to get that doing here. Thank you very much for attending this meeting. Thank you very much for sharing the good news and in the progress in all that. Always a pleasure for me. We'll meet next week, same time, same place. If you have worries or things you would like to discuss, don't, don't hesitate to ping your, your lead mentor or anyone from the organ main team if you want to discuss a point. Thank you very much. Have a nice rest of the day and see you another time. Thank you. Bye bye. Bye. Bye. Good day, everyone. Bye.