 So, and we're recording. So, hello everybody. Thank you for joining this Google Summer of Code 2023 office hours. I don't have any general subjects to share here with the group. So what we're going to do is do the regular rounds, what people learned the previous week, what they achieved, what they're working on, what are their worries. And at the end, we'll keep it open for any other any other question. Yeah, if indeed is also missing. So we'll start. We have so top most on my screen here is Jakruti. So your turn. I don't know how you end up at that place. So, tell us. Tell us. Yeah, hello everyone. So last in the first part of the last group I was working on security sample, which is merged into production right now. And the second group that I started working on the first group is a part of second half of GSOC, which is also complete and merged into production. And right now I'm working on SCM link validation. So that is my update. And also I have added the blocks for the first time but there's just one left of the way. I just don't get it about the global model. That's my update. Having some difficulties or? Yeah, I'm not sure you're using the microphone or your headset. Jakruti, you sound a bit far. I want to add a bit more about what Jakruti is doing. The SCM validation link validation probe that I mentioned is a bug that we found in the past weeks. And so Jakruti is working on fixing it. It's not a technical bug. It's more of a conceptual work. And so the difficulty is the bug itself is used by other probes. And so fixing it in one place, we need to fix the behavior of the other probes. But it's not something that is really located. It's located. We know where it is, but it's prayed a bit across several things. And so Jakruti has to fix the bug and adapt the tests that exist. It's not like creating something new like she did before. So it's something, again, it's something new to her. OK, good. A question that I'm going to ask to the other mentors, Alyssa, being the outreach officer for Jenkins was suggesting and recommending if you have time to do and is a polite way to say it. Are you able to write a small blog post summary of what happened in the first part of Google Summer of Code? Is that planned? So I have already started that document, John Mark. And I already have input from Harsh and Vandy. OK, so you're building a single document for all contributors, right? Right. And I can put a link in the chat window again for the GDoc. But yeah, I'm hoping. Well, I gave our GDoc contributors the deadline of tomorrow to give me their input. But here is the link to the GDoc. But yes, we've started already. OK, that's good, because it's useful and it gives a good picture of what we're doing. So who didn't give you the input? So I still am waiting for feedback from Jagruti and Ashutosh. OK. Good. But they're not late. We still have time till tomorrow. Right. OK. Is it a long document? Or does everybody know what's required? You know, I'm hoping that it's not a long document, but it's going to be. It's just a blog post that we recap what was done for that first half of GSOC. So two paragraph or three paragraph per project? Yeah. Well, as long as the GSOC contributors wants it to be. But then I'm also going to include the link to the slide deck as well as to the recording in case people want more details. Right. OK. Sorry to have jumped, but just wanted to check about that. So tomorrow evening, your time is a deadline. Morning my time. And I'm hoping one of our GSOC contributors can do the pull request. Would that be? What do you think about that? Oh, I can do it. Oh, awesome. Thanks, Chris. Right. That's great. So we have good teamwork there. Thank you. So next one on my screen is Harsh. Harsh, I'm wondering what you have behind you. Is that a thermos bottle or a pipe or either? It's a bottle for my water. OK, good. So as we have water, so what else happened on your project and what are you doing right now? So like in the coding phase, one I was stuck because I was not able to get the milestone to code working interactively. But now I am out of it like the code is working interactively. So I can officially say that now the GitLab plugin does not use rest easy at all. It's completely based on GitLab 4j. And I am currently working on the test cases for that. And other than this, yeah, I had to go through a lot of debugging into the Jenkins code and into the stapler requests and responses to get it functioning right. But yeah, it's fine right now. And I think it's on a good track. OK, good. It sounds like a great adventure in nice results. So very good. Somebody wants to add something, Chris. Maybe would you? Hang on. Yes, just me and Mark. OK, so I think the progress is very good. And we have made some really, really, really good updates this week or these two weeks. So very good work indeed. Hey, very good. So starting well here. The last one I see in who turned his camera on and is preparing himself for the show. So Vendit, tell us what is happening on your side. Hi, John Mark. Yeah, I have completed all the migration of the documentation that was written in ASCII Doc. So now we'll work on blogs and some pages that are to be generated with Gatsby. So I think we have officially completed two milestones of migrating the documentation. Now we'll only have to work with Gatsby and integrating doc search on both Entora-generated and Gatsby-generated pages. OK, sounds good. Yeah, we are in the ending phase, I guess. But I have my exams. I have my exams and I just got to know that they have been postponed a little bit. So I think I'll be able to do some work or I won't be able to do much work because I have to prepare for them. We'll see. OK, these are the kind of things you need to discuss with your mentor to organize. But it's important that you find a good balance, especially as you're making good progress. So, OK. Maybe Jeff can say something about the course. Yeah, so yeah, I mean, Vande is doing good. I mean, I'm meeting the requirements. So I think, yeah, I said, like, he's working on doc search and the events and calendar pages. So I saw the, I didn't join the last meet, but I was following the chats and then getting that alternative channel thing. So I mean, it's good. I mean, OK, very good. I plans to show the results to some SIGs or to the other. Yeah, OK. So that we plan to show it to the docs of Zara, Asia one, maybe over next week. And also we might join the UX co-later, but I have to talk to you and do about it. Very good. So here, that sounds very good progress. I hope that Ashutosh's power problem and water issues. Bruno, can you eventually do a very quick stand, point or tell us? Yes, I was lucky enough to have a short meeting with Ashutosh before the power outage. So I know a few things. We had for the time being three simple tutorials, the latest of them being Maven tutorial, which works pretty well. And this week we wanted to work with a Python tutorial. And it's working. It's not yet merged, but it's working, which is a good thing. And there was a major step I had Ashutosh to do. It was about the first steps of CI CD for our project, which means using GitHub Actions to test our Docker compose instance of Jenkins. And it's kind of difficult. What is difficult? It has to learn about what is a GitHub action, first of all. How does this work? And it also has to learn about the REST API of Jenkins and the Jenkins client jar file. And so that's lots of things to learn before knowing how to get it to work. We have to start Jenkins. We have to check that Jenkins has started. We have to check that it has finished starting and ready. We have to log in. We have to seal the name of the jobs. We have to launch a job. We have to check if the job is running. If it has finished, it's difficult. That's why it's quite extensive. So to explain to the others in case people are wondering, because I worked a little bit on that, why using GitHub Actions and not Jenkins immediately. GitHub Actions is quite cheap and easy to start with. Doesn't require heavy infrastructure. And so you can experiment on your own. Build your CI tool chain. And as Bruno said, validating that the demo works is there, that the jobs are. This is the major work and problem. And once a project has something to work, moving over to Jenkins is the easy part. We just need then to apply with the Jenkins infrastructure to have the Nest 3 setup. You nailed it, John Mark. Yeah, but I just wanted to have it on record, because people might ask why. But GitHub Actions is a very good platform to learn and have, I won't say quick and dirty, but easy way to start CI. Jenkins is the heavy duty one, the professional one. Difference between Markdown and ASCII Doctor. You can do much more with ASCII Doctor than Markdown. OK, finish that. Is there somebody who would like to add or raise a point? So next week I'll be back in Brussels. It will be easier. We're going to see how we can organize that with you. I might have reorganized a small chat, one-to-one chat, with all contributors just to see how things are going. But I see a lot of smiles. So my opinion, things are moving good. I also have chats with mentors to see that we're in line there. OK, unless somebody has a remark to do a point raise, and I leave a couple of seconds for that, we can. OK, I didn't hear anybody interrupt. So I wish you all a nice evening, morning, and see you then next week. Have a nice rest of the day. Have a nice week, everybody. Bye, everyone. Bye, John Mark. Bye, everyone. Bye.