 So here we are. Good afternoon. Good evening. Good morning, everybody. So this is the GSOC office hour for today, June 8. We're now in the middle of the, well, the first third of the coding periods. We have all projects represented. Only one contributor is missing. Ashutosh couldn't make it on time to attend the meeting. I've seen the message Bruno. So I take my lists so that we always use the same order. So as usual, we're going to ask what happened, and I'll be a little bit more specific and a little bit more open or less formal. And the question will be, what did you learn this week, which is an introduction to what happened? Okay, so first on the row is check crew team with the plugin health score. What did you learn? So I'm working on third party package section this week. So I learned new thing about parameterized test cases, like when we should use parameterized test cases and then we shouldn't. I did make some save but thanks to agent who was able to come out fast. So I think this is progressing like little better from the previous step a lot. And I'm writing a new test case that is to check the if the third party package is present in the child or the parent. So that is something new. I'm like learning. I'm learning about. Okay, what did you learn how parameterized testing right and yes learning more about me. And before that I learned about check it in my previous book. Okay, so learning quite a lot of things new things. Which is a person I'm learning. I'm learning is writing test cases. What kind of scenarios to test. How to figure out is that we have to test this out. Okay. Good Adrian, do you want to add something. I think Jagotty as well. So, yeah, might not be interesting for everyone to see that Jagotty is learning about tests, but it's because I ask a lot of tests on new products. So she's learning new more than the skill is more behavior about how to implement things so that's coming together really well and because this week. And the week before this week we worked on something that is rated to Maven asked Jagotty to learn a bit more about Maven about its behavior about how it's working. And so she, I hope that she's learning a bit about that and everything's coming together very well. Obviously she's learning and enjoying it when I see the smile. Okay. Good. Next one that has also a smile van deet. So, who's going to talk to us about the Jenkins IO with alternative tools. So what did you learn what happened. Yeah, I learned about regular regular expressions and the rolling scripting because I learned that I learned it in theory at my college this semester, and I implemented them in some scripts. But yeah, what I exactly wanted to do with my script wanted my scripts to do. Well, they didn't exactly do that, but yeah, we were we were 60 70% to the goal. So, I wrote some scripts and I ported, I ported the developer documentation on and Dora. Okay, so you're, you're moving ahead and regular exceptions now you start to know the start to have practical I wanted to say now you know that you don't know nothing. So this is the first important step of being wise. Okay. Finish learning with reggae. I've been doing reggae for 25 years. And this week I've been struggling like mad with reggae I can't get right. Yeah. Do you know reggae 101 online tool for that. Yeah, that's a very handy. Do you know that van deet that site. No, I will check that out. Okay, I just referenced my notes I made in college and I was like, yeah, I can do this. Okay, so you're learning it the hard way. So reggae 101.com or I don't know is a very neat tool to explain you the structure of the reggae you're doing and Yeah, okay, good. But just a tip. And I also enjoy reggae. So the very powerful when they work. Yeah, when they work always work. It's like taming an animal. I love coding when it when it does what I wanted to do. Okay. Chris, do you want to add something to when it's report. Yeah, probably is good. And I accept. I am not sure at what stage the project is in. It seems like we're not doing PRs yet. So we'll move toward that direction later. We need to. Okay, this is an important tool or technique that's using open source that that shows where you are what you're working, what you what you change. Not all the projects are using that technique yet. I think she's using PRs. To show to Adrian is very strict on on that. They're starting. Go ahead. We are in the beginning itself. As soon as I start. Okay, but there's a discussion you need to have at project level. It's it increases the visibility and very good. Okay, sorry, once again, it's none of my business, but yes PR are very important. And it's not a problem if they are depends on the project, but it's not a problem if they are draft PR we still failures. This can also be seen as a discussion, you know, to see with the mentors, if your PR is going the right way or if you should change it or a mark way that you may know is somebody who I respect a lot and his work is really good to me. You know the other day I saw PR of his regarding the procession of old containers and operating system for Jenkins, and it took him more than 100 commits to get it right. So don't be afraid to make draft PRs which are not finished. So the mentors can see where you are going to and give you some feedback, even if you did not request a review yet. Very, very good advice. I'm pushing to the main branch right now because like I just test that too often and I just push it to the end I'll start making PRs. This is this is run it learn like you're not used to do it that way when you work on your own as a college college you're not trained so this is why we also insisting to start using that because this is the way. The way of the open source I'm going to put my helmet on this is definitely. Okay, very good. Vendit. The next one is. Ashutosh was not in Bruno. Can you give an update where we're standing. Standing is the right word. We're not progressing that much. I'm afraid I hadn't realized that the first step was so high so difficult to climb. The thing is when you want to make things simple for the end user. There is a lot of work ahead to make things complicated look simple. So Ashutosh is struggling with getting the first example up and running. He's progressing slowly and as maybe other contributors he has to learn about good practices with PR issues. Everything I know there are lots of things to a lot of things to to learn. So it's difficult the first week must be a torture. Time will come when you will smile again and look at what he has accomplished and be proud of the journey. But first time being, yes, the progress is kind of slow. But I hope next week we'll find the second gear and go faster, hopefully. Let's make sure that Ashutosh doesn't get discouraged. Yeah, I hope the tone I use is right and not discouraging him. We're going to take that offline or later. Good, thank you and as he's not in, we're not going to spend too much time on that. The last one is Harsh. Harsh is there. Why did you move? Oh, Rajiv joined. Oh, that's a like Rajiv. Because everything moved on my screen it didn't find harsh again so harsh your side you're smiling too so that means that you learn something this week. Share with us. Like, there is a lot of things like the draft PR which I made regarding the first milestone I added the Docker based functional tests for that, even when it was the like a scratchy goal for the project I still added the thing which was necessary for it and I am waiting for the review from Chris that the tests are right at least the tests are building fine that the milestone is working perfectly I have made the draft PR and I'll soon make a normal PR for Basil to review it. Other than this I also had to make a snapshot of get lab for Jay library that I was using so I already added some changes to the library itself so that it so that we could use it in our project. But what was happening is it is not released yet so we'll have what we are trying to do is we are trying to get a snapshot and in deploy and deploy it in the Jenkins. Artifactory and now we are in a mess because like I again changes I again did some changes to it because it was not supporting my m one chip, like I use my book so it was not supporting that so I again did some changes. And now again it is failing so I have to I think I increase our working towards writing the test cases for the library. And the get lab instance that I use is so damn slow like I have to wait a lot like 30 minutes for for it to just start and then it gives me a lot of 502 errors and I just have to struggle a lot for that, other than that get lab also released its new breaking changes get lab 16 which I also have to work upon you having far too much fun. I'm having a lot of fun like Chris is really helping me a lot, otherwise I would I would have been a dead meat by this, but yeah, like regarding the project, it is fine like I have almost completed the first milestone like I have migrated all the resource calls from rest easy to get up or do other than this I'll be what the next milestone will be that webhook thing and the third milestone will be the proxy, almost, you can say one third is almost completed, but I'll have to wait for the review that has to do. I already made the PR but it was something wrong like you just said that draft PR is an important I this is my second draft PR my first draft PR failed because I broke the backward compatibility now this time I have the backward compatibility. Correct. So yeah, long journey. Okay, I see that where you have tough times but you're progressing so that's good. Chris, do you want to add something to harsh report. I just want to say good work, except like we went into a lot of technical issues that outside of our control so it's like it's, I think it's just life. Okay. Good. Talking about making progress. We're moving ahead in G Sock. I don't want to scare you guys and girls. We have a milestone mid July. And so I'm going to tell I need to validate that with the other arguments, but part of the mid term evaluation is a presentation to the community of where you standing that you could demo demonstrate explain what your project is about. And we're currently looking I need to confirm the especially with Alyssa was our grand master of meetups. So we're looking at organizing that presentation the week before the evaluation so we would do it at this time. On Thursday, July 6. I'm going to send a mail to everybody or notify that so that you have the date in written if somebody has an issue about that or or so. Let me know let us know I've seen a message from jacruty relief. Oh, okay. No, I see it was related to previous discussion. Okay, so if I'm not following the chat so please excuse me if something is important in the flow of the discussion, please raise your hand. And share that. Yeah, do because I think that on July 6. I will be out. Okay. Is that is that a problem or should I find a solution to be able to. I'm looking at jacruty. How scared are you to do the. Please don't don't put more pressure on jacruty. The presentation will be prepared in advance. I will be working with her for that before is just for the presentation. I don't know about dirage or mustafa or jake if they will be able to attend. Normally. There are some questions to be attended to be to be expected. Should we expect some questions should we are an explanation about the progress of jacruty or things like that that things that jacruty might not have a way to answer. And now in this presentation, it is okay to say that you don't have the solution or the answer and yet you will look it up and come back. So this is perfectly okay. So, it's, so jacruty will be fine. And I can understand that you want to attend and to see the presentation. I don't think that it is required. So, maybe we can discuss that offline and especially if you prepare that early enough. Yeah, we'll do that. Don't forget, and don't forget, nobody is going to kill you. So you're not going to do up so die. If you want to ask something. Yeah, I have my end semester exam on 6 July so can I be faster like a week before it or something because I have an exam. That's a good point. I'm just from 16 July to 12 like 13. Oh, that's that's no that's important. That is the most important thing. So that we do that. Could it be recorded. Yeah, what. It could be recorded we did that already. Does anyone else have exam during that, during that period or things that will prevent you from preparing the presentation. I'm thinking about two at least two weeks ahead. Or two weeks later, if you know one one week earlier would be June 29. And this is this is getting near. So I want to give enough time to harsh. How about recording your presentation so we're talking here about 1010 minutes presentation. Yes, yeah, I can record. Yeah, I can record it's no problem for me but I will try finishing up like. Till milestone towards right finishing up before the 28th or 29 like I'll try my best it's it's going a bit slower than I expected because of those random issues that I get into. But yeah, if I am able to do it then it should be fine. Here harsh at this stage. Can you discuss that with your mentors. And see and the mentors or yourself will come back to us as organ men's and see what we can do. For that. Okay. Yeah, I have a meeting tomorrow I will discuss that. Raise that and see what other the alternate a recording is okay is is Adrian pointed out. Vandita are you okay. I'm completely okay with that. I think I'll have my exams in around third week of June, third week of soon. Why shouldn't why. There will always be exams somewhere. The only person who will not have exams I think is the cruelty. She has other types of exams is worked complete. Just a proposal with your, your mentors. Go ahead, I dream. I was thinking to third week of June that lets two weeks to prepare the presentation. Let's say one week, just to cool off after the exams, maybe, maybe not enough. Could we do the presentation then the week after the second week of July. I think that will the second week is July 13. Yeah. Could it work. No, it doesn't have to match the milestone of harsh over on 13. Well, yeah, and he needs to study. Yeah. Yeah, I need to study. Okay. Yeah, but I'll manage that. That's my problem. I don't worry about that. Here, discuss it with the mentors and I'll do a round. The other thing is I have one on one meeting with all the men, all the contributors beginning of next week. So there we can clarify. So if you have time to discuss it with your mentors. Before, otherwise, we'll look to do it later. Lisa, we also need to look here, we'll discuss it afterwards. So I didn't expect. Why do they do exams at college? Why, why? I am asking that from my college. Good. So, thank you for sharing the reports sharing also your difficulties. But also good progress. I see smiles. So that makes me happy. We'll have a one on one discussion beginning of next week. All the meetings are set. And the presentation for to the midterm presentation to the community. There we need to navigate between different dates exams and things like that. So we'll find a solution. Is there a subject that I didn't cover or is there something somebody would like to raise? Three, two, one. Okay. We then go. We're on time. I wish you then all a nice rest of the day. A lot of fun solving problems harsh. I expect you to go with your machete and starts solving all those those problems you have. Jack Ruthie continue to learn about the testing and the secrets and of Maven and all these kind of things. So thank you everybody for joining this meeting for sharing the updates and have a nice rest of the week and see you next week. Bye bye everybody. Bye everyone. Thanks everyone. Have a great day.