 Here we go. Good evening. Good afternoon. Good morning, everybody. This is August 18th, GSOC office hour, global one. Hello everybody joining. And let's start. So the first point I wanted to discuss or to raise was that I think now is a good moment that the projects are advancing very well and we're slowly reaching the end of this campaign is that it would be a very good idea that every project would write a blog post on the Jenkins IO community blog to describe in short format what the project is about to give some explanation about the project. This would be a compliment to the Jenkins online meetup we had some time ago. I have some suggestion for the topics. So 500 words depends how you count them. This is about a page, a page and a half maximum. And the besides describing what the project does, it would be interesting to explain in a couple of words why the project is important for the Jenkins community or what it brings to the community. And another topic idea is why is it or was it important to you as a contributor. So a couple of words what you learned or what it is what you're learning right now as we're still busy with that with the projects. The purpose of that is it's a way to communicate and explain a couple of things to future GSOC candidates because we start to have people interested in the next GSOC campaign. These blogs are useful for them to understand what kind of project have been done, what it is and how it all works together. Are there questions, clarifications regarding this recommended blog post? Yeah, I do. Should the contributors include the coked products as well? I didn't catch that again. Okay, should the contributors include links to the coked products as well in the blog post? Why not? Why not? Everything that could be useful for the community and the passerby to learn more. So to go deeper. We don't want to scare the people by having three or four pages to wade through to understand what it's talked to, but it's always a good idea to have. This is what I want to say and here are links to further discussions or documentation or to look at the code or things like that. Good point. Okay, for how to proceed, what is the magic required for proposing a blog post on Jenkins.io? Your mentors can help you with that. There's also the contributing page on the Jenkins.io page or repository. Other questions or comments? Okay, good. We have two projects being present here, three, which is third one. Oh, who's she cash? Okay, good evening. So we have three projects and we'll start with Vian. Vian, tell us, where are you standing? What you achieved and where are you heading to? So the usual roundup? Yeah. Hi, everyone. So this week, I was able to create a draft build request for the changes that I proposed last week and the changes are getting built nicely. So no errors with that. And for the draft build request, you're also planning to add the instructions for the review to be so that I've done today. And along with that, we also throw in some tests that will test the new processing layer. And that would basically sum up the entire build request and then it would be merged. And after that, we plan to add the last feature that would be to get the plugin names from which each parameter of a step is coming. So for example, if we have an SCM, we have something like it SCM. So once the user clicks on that, so now it will be a clickable link, which leads to a new page. So once we click on that, the user should see that, okay, yeah, this parameter, this class is coming from the good plugin. So we are working around the ways to do that. But other than that, I think as far as our goals are concerned, we are pretty much on our track and we're almost done. Okay, good. Sounds great, Fian. Happy to hear that. Next project is yimming with his Jenkins file runner action for GitHub. Tell us what's happening on your project. So recently, I worked mostly about my documentations and use for examples. So firstly, I created the documentation demos and detailed the plane and how I will develop with my documentations, which includes user guide and developer guide or something similar. So because we decided to host all the documentations in the GitHub pages, so I need to write a detailed plane and a demo and about how I want to implement it. So secondly, I created several useful examples for the users, so they can get started in our actions quickly. So it is those examples are stored in another demo project. That's my work recently. Okay, and no impediments. I think everything is under control for your project. That's very good. Okay, that sounds good. Thank you for the update, Yimming. The last one we have, unless somebody else sneaks into the meeting, I'm teasing you, Koshikash. So it's your turn. Tell us what did you achieve, what you're working on, what is brewing on your site? This week, I worked on persisting the maintenance records into an XML file. So after each maintenance task is run on a cache, I store all that data into an XML file on the Jenkins controller. After persisting the data into an XML file, I also created a table. I also created a table to display the maintenance records. So this table contains pagination, sorting, and also a search functionality. So that's what I've been, I worked the previous week. I'll have to improve the performance of how things are being done because behind this was only a way to connect things and integrate and finish the functionality. But behind the scenes, the performance isn't that great. So I'll have to create, think of a way to improve performance and improve the overall functionality of this feature. Jumping on that, Koshikash, a good advice, and I hope you will remember that, is when you're working on something like that, first, implement the feature. Note that the performance is not as expected and then only work on improving fine tuning and eventually refactoring the code to improve performance. It's a pitfall to start while implementing the feature to start immediately working on tricks or thoughts on how to improve performance and speed. Believe my long experience. And you're doing this on that way. Yeah, this is something I have to consider because I spend the whole two days just reading about how things, how do I improve performance rather than completing the functionality. So yeah, this is something I have to think of. It's a lesson and you experience that and think about that tip. But try to do it sequentially. It's a general advice that's very often given. People get lost in trying to improve performance while they're still building and they lose oversight. Just a small tip based on my experience. Do you want to add something else Hoshi Cash? Nothing. No, it sounds good too. So I'm very happy to hear these updates. Well done. Congratulations, everybody. Vihan shared the link to the contributing document of Jenkins.io and how to add the blog post. And I added it to the meeting notes here. So the link is available there. Is there another subject, question, comment that somebody would like to discuss or raise? Nothing from my side. Thanks. No, okay. I've done, so let's do the countdown. Three, two, one, no subject. So enjoy your week, wishing you a lot of progress and a lot of fun. Bye-bye everybody then. Thanks everyone. Bye-bye.