 Here we are, so starting to record. Good evening, good afternoon, good morning everybody on this call and listening to the recording. This is the Google Summer of Codes office hour for this August 25 or 25. So, let's go first. I have some communication where did I write them down there. So we're slowly approaching the end of the summer. Meaning that we're slowly wrapping up. And so reminder of the deadlines and then when we do the round table. We're going to check in particular debt. So, from September 4. You can start submitting your, your questionnaire and no leaders also link to presentation or no I don't remember when did I read that, but you have to fill in your application for the results. The deadline is September 12. So keep that in mind. Now. So just for Drash joined. So reminder, we're reaching the end. The, you can start submitting your results. September 4. And they're due. So the final date is, is September 12. This is important. This again. You mean the final blog post. Not the blog post, not the blog post. So on the Google Summer of Code application. This is where you fill in. I forget the name. I need to, I don't want to move the screen here. But there's a special name for that is where you we're going to conclude and where the mentors are going to make the final review. And say, did you did it work? Did you achieve the goals? And can we conclude the experience and I think you're going to rest to receive the last part. Of the stipend. So question to you. When we do the round table is so the usual question. What happened last week or this week. What is ahead of you for next week. And how do you feel with ending your project for. September this when you have to submit the final report. I know that Russia cash had some impediments during the summer and had to stop for a while this was planned, because he had some exams to do. And there were some doubts. Would who she cash needs some additional time to complete this discussion is open. Okay, Dr. So, we cash made a request. This is the discussion is ongoing on this project. So, when we do the round table just tell me if you need additional time to complete so that means that we're going to shift the deadline by one or two weeks for completing the work. The point that I will ask you to report or discuss is so I strongly hinted or suggested that you write a blog post about what you did. It crashes a little bit with the end of the project so now. Are you feeling with that. Are you ready do you have already something or you're rushing to complete your project and see where we standing there. So three question usual question that we have every week. Second question is, do you need to feel that you need extra time. Second question. Where are you standing with the blog post about your project. Okay, so let's start. And let's start with who she cash was first top left on my screen. So let's go. Good morning. Good afternoon. Good evening. So this week and last week I made a so I created a UI table where I can show the maintenance results, like which was stored in an XML file. So that week, the UI wasn't that good. It was a very terrible UI. So I, so now this week I'm planning on improvising the UI making it better and easy to read and understand analyze it. So that was one thing. And second thing I'll have to document the things like the entire code which I've written and you know update me as well. There are a few bugs in the code so I'll try you know, I'll have to be fixing that as well. So that is this week's agenda. Okay, good. So I heard some good comments about your demo. So, don't forget to engage the discussion with your mentors to see do you need more time, how much time and so on and come back to me so that I can fix that. So the thing is right now, like we are going as per we are like going according to plan, but you know still I've you know taken the step you know just to be you know safe. So I think I'll discuss with Mark once and you know, get back to you. Yeah. Good point. Third, were you able to do something about a blog post or where are you with that task. I forgot about it so don't worry, don't worry. It's, it's an important part. It's nice to have, but I'm not going to India to kill you if you didn't do it so I'll be doing it. I'm joking. But, okay. Try to put it into your planning. It can also be done after submission. But here, don't forget to keep that on on your, your radar screens. Is there a link, you know about how do I do it or something, you know how steps. The easiest thing for you to do is write a document as a markdown document, write down. Yeah, Yiming is sending the link. He's faster than me. So he's pointing to the, the exact truth about that but write a markdown document as a work document. And from there, there is only a little bit of cooking required and you put some salt here and there to have it as a pull request in Jenkins.io. And these are things where it can help you so that you can keep concentrated. Most important thing is prepare a markdown document with the ideas. This is where the big work goes. Okay. Yeah. So and follow the link from that the teaming gave this was very wise. Thank you for sharing that. There you have all the details. It sounds good to the cash. Discuss with your mentors to see if it's required because I need to do some paperwork to get it done. Okay, do you want to add something or discuss something else. Nothing. Great. Good. This is Fian. No, it was. Anyway, let's start with the. So what happened, and what do you do you plan to do. Yeah, and we have troubles to hear you. And so answering some progress. We have problems to you to hear you. Do you hear us. I'm sorry. Sounds like an internet issue. Okay, that's too bad. Let's try again. Hello, I think my internet is a bit dodgy right now and I'll just. Yeah, okay. I will see. Here, let's let's try again later in a meeting and see how that goes. Yiming, because although you're in a noisy surrounding as you told us, can you try and give us an update on where you're standing and what still needs to be done. Sure, of course. So, so firstly, I add more demos in the exam posting my demo project in the second I added the developer guide to the documentation page. So, so someone who is who are interested in can contribute it. And then thirdly, I already created the GSOC blog. So this blog will be submitted later, as I needed some references to the new actions pages as deliverables because I want some URLs, such as the repository after the migrations. Finally, I submitted the migration requests for the current POC project and for requests has been approved and three has some naming issues and I need to fix it. Yeah, that's my work. Hey, that congratulations so you get that going so. Hey, moving well ahead. So that's that's good. And so don't forget to yell or contact me if the hosting gets stuck, but apparently it's running very smoothly and you get the necessary help. Yeah, exactly. Well done. Okay, that sounds like good story to. Okay, the rush tell us what's happening on your side. Yes. So on my side, what we did in the past week is we just I submitted my first probe and in that we are fetching the is like my first probe but there are already two probes in the project that have been submitted already which I worked on with Adrian. So coming to the probe which I just submitted it's what it does it fetches the most latest commits date and time and then stores it into our database. So it does it for all the plugins. And with that in mind. So with that in place. I would be able to write the other probes at a much faster rate, because with this one I needed to study about j get like how it works what is it why do we even need it. So with that done, I would be now able to use it for more ropes which are like kind of similar with this one. So I'm very positive about adding more probes, even though the deadline is approaching, but we would be able to add in many ropes in the database. At least that's what we hope for. And, and also Adrian has put in some few PR, which are like enhancement tasks. So I also reviewed them and started some discussions on that on our data channel as well. So we have discussion is ongoing on that. And now to okay and the plan for ahead is that I would be as I said I would be working more on more probes and yeah that's about the plan for it. And to answer three questions, first one is like do you need extra time. Now, I would need to discuss it with a mentor like we had some we discussed some deliverables that we will be doing. So I need to understand from them that would we be able to do it before the deadline or not. The last time I remember my mentor said that we would be able to do something before the deadline. So I'll confirm it and let you know by next week that do we need need extra time or not. And second one is the block post. Yes. So I have not started working on it. I would not be able to work on it for like two weeks. After that, I would be able to start because yeah, there's no block. Awesome. That's no problem. So yeah, don't don't worry about that first complete your project and make it in in in a peaceful manner. Now if you can squeeze in between or when when walking outside you can think about that. And use the method that I suggested to who she cashed, write it down on on a markdown document and started that way. So it's, it's important. But it's not blocking for the for September 12 and I don't want you to work during the night, not at all. Just to complete your project and the block post the block post is something I'm going to request afterwards because it's we're talking to the future. So, okay, a little question. Yes, go ahead. So I would be just completing it for sure because I understand how important it is for new people to know what happened in this project. So I will definitely do that with with interest. Yeah, good. Okay. Just by curiosity as you're wrapping up your project and you try to squeeze other important things in the project. How about documentation about the project. Your good has this been planned with or discussed with Adrian and Jake. Is there documentation to be produced contributing or read me to read me or these kind of public documentations. Like, like for people to contribute to this specific project, some developer guide something. Okay. Yeah, these kind of things. Okay, so there is an open issue that Adrian created previously. So he already knows about it. Just I need to reprioritize it with him to understand when should I be working. So, I will work on it but I'm here to discuss. Okay, so don't forget to discuss that with your mentors. This is something important. So look at the priority and wait if it's not better to drop a probe. But you have something that's wrapped up correctly. But I, my little finger says that you want to continue afterwards to contribute on that project with what would be really awesome. We know and we can complete things afterwards, but it would be nice that we have a wrapped package, something where we can say, okay, this is generation one of that and then you can be proud of and then you can continue working. Don't forget to discuss that with with your mentors. Yes. And also, Jake helped me to remind that I also need to work on the architecture diagram. So I will be working on that as well. So thanks for that. Yeah, be careful. This sounds like a lot of small tasks and so so discuss with your mentors that you have a precise plan. I think there are things that you need to drop. We prioritize don't try to do everything at the same time. Okay. Because otherwise I knowing you you're going to work until two o'clock in the morning. And this I don't want. Jake, do you want to add something. Nope. Yeah, that was one of our topics of conversation on Tuesday was work in progress, controlling the amount of work in progress. Okay, Jake, you're aware thus that we wrap up so the Raj will have to fill in his final report application deadline being September 12. Sounds good. Okay. Great. Something to add Russia Jake. One last point. And I know this might sound a lot, but this is for just next week, what we will be doing in our next meeting you will be discussing about the map behind calculating a plug-in score. Yeah, it's like, we were discussing if the initial plan that we had is it still feasible does it still make sense. Accordingly, we'll try to think about it. That's all. Hey, great. I like I hear all those projects are really doing well and are ripe now it's like an apple that is ripe on the tree and now we can pick it and show it and sell it. So okay. This said we'll try again with Vian. Vian, do you hear us and can you try. Again, as my voice isn't audible the same. Much better. Yeah, fingers crossed. It doesn't go this time. Okay. So yeah, answering your questions. The first question about the progress. We're almost in the winding up pace so completing the tests. The first set of tests that Christian asked me to write their complete and she came up with a couple more this week so I'll complete them before the weekends. And I'm planning to start working on finding the plugin name for the classes that coincide the parameters. So this is something that that could be a bonus add on task. But other than that, as far as the G so present project is concerned, we are pretty much on track so that separating full request is complete now. And once that gets merged, I'll start working on my blog post so which was a second third question I guess so I've not worked on it yet. But once that gets merged, I'll have a lot of my tasks really and I can focus on the blog post and I think I'll be able to pull it out before 4 September. So nobody's and second question, do I need extension. Most probably no. Everything seems to be on the track. Okay, here that sounds it was short report because you feared that your, your line would drop, but it was efficient. So you got the message across here, you like the others, you're, you're nailing it you're making very good progress. So, very good. Okay, I think we, we went round. I have nothing to add is there another topic to raise to discuss worry anything. I do the countdown. Two. One. So I wish you everybody a good night, a good afternoon, and a nice day for them for those that I'm not a time zone. You too, John works they cool. I hear it's it's it's what you know. Okay, bye bye. Cheers. Bye everyone.