 There we are. So, good evening, good afternoon, good morning, everybody, word for this GSOC global office hour. And let's start immediately. So I'm just going to see, I have a general, information to give, but I don't find my notes. Hold on. There, I am an old man, so I tend to forget. Here we are. Okay, hey Chris, that would be a great help if you can write the name, just in the document. So the first question I have, a lot of documents have been produced during the bonding period and currently project plans, planning descriptions. Don't forget to update the, your project page on Jenkins.io with the links to these documents. A lot of good work has been done and if the community wants to learn more and follow, an idea is that you create an index page as a Google doc and you put the links in that Google doc document. So you have only one link to update in a project page. You name it, useful documents and then you can update the links in the Google doc document. But don't forget to do that. Speaking of that, we're just to be sure that all the projects are okay and we didn't forget anything. I'm going to ask the lead mentor of each project to see if all the tasks in the bonding period face, especially project plan, describing what is, what will be delivered, what is the timing, that all that is defined and everybody agrees with that. So I'm going to send a survey to the mentors to check that. A little detail for Adrian and Deraj, I'm missing the link for your office hour. So this will need, it needs to be updated in a project page. Sure, no problem. I'll send a PR, sure. Okay, no problem. So this is just housekeeping. So let's start with the status of the different projects and let's start with the first one because Yiming was ready to start immediately. I think he's done quite a lot of work this week. Yiming, the floor is yours. So what did you achieve this week? Okay, this week and last week, I created a proof of concept repository and developed several draft Github actions for Jacking's File Rounder. Yeah, you can see it in that proof of concept repository and I also send out the messages about this project in the developer mailing list and discourse. So I think the progress is good now. Okay, yeah, I agree with you. So there are a lot of documents that were attached to that. How many reactions did you get? You had one from Gavin on the developer list. Did you get some answers there? No, no further. Okay, don't worry with that. It's not that people are ignoring you. It needs some time. Mostly the people will look at that during the weekend. So and maybe after the weekend, we can send a small reminder. And we say in French is no objection means they agree. So no comment and you can continue. Yeah, I understand. Okay, do you have some impediments or things that are not working or that could prevent you moving ahead? I don't have further problems now. Thanks for asking. Yeah. I forgot to say in the entry entrance miscellaneous points. So I organized a one-to-one meeting with every GSOC contributor one-to-one so that we have a free discussion. I had already a good discussion with Deraj and the three others will have the discussion next week so you know that. And what's discussed during these meetings stays between each other but other things to share. So good. So Yeming, we're going to have a chat together, free. Nobody else listening. Yeah, you confirm that. Yeah. Okay. So just to listen if everything is going okay. Okay. The next projects, do we have, no, we have Deraj. Deraj, tell us what has been happening last week. I know one. I'm going to tell it immediately. You had your first PR merged. Yes. Tell us about that. Tell us what happened this week. Sure. So this week I got my first PR merged in and it was a rather long PR and we decided that there are some things that we will be coming back to later in time to improve a few nits and gits. So that has been decided and now that we have some like some part of the application in the repository merged, then we started to work on dockerizing the whole application. So I put up a PR two days ago and I got very great review comments around that like how can I improve the Docker file creation and all about it. So I'll be currently working on it and on a side note this week, I was a little less available due to some other work commitments. So that's why it was a little slow. So I'm aiming to compensate, not compensate but just really excited to work on it this weekend to dockerize the container, the project and get that PR merged as soon as possible as well. So that plan. Deraj, can I say what you did today with your other commitment? Or you had your presentation. Was it today? Yes. Go ahead and say. But Deraj had a presentation at a conference in his company today. So first time he did that. So he has a good training for the presentation and end of the month of July. But congrats Deraj. Very good. Thank you very much. That's a good excuse. No, no excuse but a good thing that way. You couldn't spend as much time on the GSO project. So that's good. Comments from the two mentors. Jaco Adrian, you want to add something? No, really. Deraj has been very good at answering comments on the previous PRs and he's learning a few things. That's what we try to learn. So not only saying no, that's not correct, but pointing to the correct direction. I think that's the whole purpose of this GSOC. So we're trying to do that. But no, Deraj has been a very good answering comments in the past. This week was a bit different but we knew. So it's not a problem at all and it's understandable. There's no problem on that point. And so yeah. And a congregation on your first presentation. Always a milestone. Okay Aditya, do you want to add something? No, everything is covered by Aditya. Congratulations, Aditya. Okay, good. Any impediments or problems? Is the infrastructure part solved? Or did you get the answers? There were questions how you would run the application or questions or at least an issue that was raised within Khatim. I think I want to shut down Deraj. I will be working on that. I don't see that as a requirement for the moment. We are not in the deployment phase so far. So there's no problem for that. And when I see that we are close to something we could deploy on the Jenkins infra, I'll be tagging that. So I don't want to disturb Deraj with that kind of questions and requirements and meeting people and getting details and so on. So I'll be doing that part for the project so that Deraj can focus on the code and on the actual project but not on how to deploy the project. Of course Deraj will be doing the deployment and making sure that the project is deployable correctly and so on. But all the infrastructure questions, I'll be tagging that and so Deraj won't have to ask questions or to figure out how to deploy. I'll be able to help him do that and have all the requirements. Okay, good. So lesson for me, I shouldn't go and fish for potential problems. People should... That's good. Also I think that's one of the first, from my memory, it's one of the first JSA project Jenkins has that will not blend in Jenkins all in the existing infra. So we are a bit on the side from different other projects from the past. So no, no, that's a very good question and we haven't forgotten about that and it's just it's not a priority for the moment. There's a bigger fish to fry as we say. It's very, very wise here. I'm an old fox so I know where the pain points are in these kind of projects but I shouldn't start poking around to know things. There's no problem here. It's not the problem you're looking for. Very good, great. Chris or Jake, do you want to add something to the discussion? No, I think everything's been said and I would just echo what Adrian said about Deraj. It's been going swimmingly I think so far so looking forward to the rest of the project. Okay, great. Chris? I think you mean is making good progress so far so good. That's what I want to say. Very good. Yeah, I've seen that a lot of progress done last week. Great. So we missing no, Vian is there. Vian, you're in the corner of my screen. I apologize for that. I'm awfully sorry. No, no problem. And you were one of the first to be there. Oh, I'm sorry about that. Vian, tell us, where are you standing? What was done this week? Sure. Hey, everyone. So this week, I went ahead and did the second request first, which was about the plugin list on the pipeline steps reference page. So that has been done and Tim was quite skeptical about it, whether it is required or not. But then we had a nice discussion about that in the project meet and then we thought that it's nice to include it and then we'll see if we have any feedback regarding that, if there's a need to alter it or maybe remove it in the future. So that can be seen because there is no specific feedback about that particular page as of now. So we actually don't know what the user will be getting benefit from. So that was the first half of it. And then in the pipeline, like the step talks of us, we had a pretty long discussion where Christian explained a lot of the code to me and we came out with some great ideas, how to improve that particular piece of code. And with respect to that, she suggested that we can separate the declarative steps generation from the main class, which would be actually very helpful if in the future, we decide to exclude the declarative altogether from the steps reference. So today I separated that and there's a request in the step generator repository for that. And in this week and till the next next office hours, the target is to work on the steps, details that are generated and shift the data type from the body to the heading. So that is some because So can you say the last phrase again? So add the wording to the Can you say that again? The data type thing? Yeah. Okay, so for the steps reference, for every step, the parameters of every step, the data type for them is present under the content. So for example, if a parameter has a lot of explanations, so there's a the user need to scroll a lot to see the data type. There's a link in the heading as it is done in other documentation. So that is something that will be done. That is slightly challenging to do because there are two or three variations of how that is done on the page itself. So we can go towards that in a bite-sized manner. So one by one. And that is what the pull requests are also about. So Christian and I both agreed that it's better to keep the pull requests bite-sized. So one feature at a time. Okay. So the third pull request was created today. So far, none of them have been merged mostly because of the security release that was coming for Genkizotio. So Genkizotio pull requests are still there, but I am hopeful that they'll get merged within this week or so. So no problem. Very good. Any problems, worries? No, I think everything is going great. From what I see from it, I can confirm that. Good. I think we went around. We had a good overview. There is one project who she cashed in didn't join. Don't forget as there's been quite some interesting and good project documentation that has been generated to add that to the project page. So the people when they join later in the project can see what, how, where things are done. Okay. Last questions, remarks, wishes, three, two, one. Then wish you all a nice rest of the day, night, evening, afternoon or morning to everybody and see you either individually or at the next global office hour, GSOC office hour. Okay. Thank you. Bye bye everybody. Thank you for joining. Bye. Thanks everyone. Bye.