 Here we go. So good evening, good afternoon, good morning everybody. So this is today's 1st of June or June 1st GSOC office hours. I was reading the temperature. I thought this was the date and I was wrong. So Bruno joined. Okay, so hello everybody. So we're now one week, nearly one week into coding period. I think the engine starts to run. So I'll walk as usual through all the projects, do a round table and then open for questions, concerns or information. So the usual questions are, you will learn that I always ask the same questions are, what happened last week? Do you have good news to share or difficulties to share? What do you plan for next week? And are you facing difficulties or situations where you stuck that you would like to share? So we'll start with the first project on my list, which is the probe, the new probes for plug-in health to Chakruti's turn. Hello, hi everyone. So last week I worked on has unreleased production changes probe and we did a pair programming session. So with the help of that, the probe is successfully merged now, the PR is merged. And for next week, I'm going to work on third party detection, third party repository detection probe. For that, I'm going to start with test cases. And for the previous probe that I've completed, I also wrote around 450 word long just to have my changes and everything merged. I'm sorry, I have recorded like what I did and how I did. Okay. So you're moving, was the screen sharing or the pair programming session interesting for you, useful for you? How was the experience? It was interesting. I mean, Adrian was like telling me what to do and how to do. If I was able to tell the logic. I mean, he let me do it by myself. But if I wasn't, he helped me and he also gave me some tips about using IntelliJ better. So it was learning a lot of, because I was, this was my first time interacting with JGIT and I was finding a little bit challenging. So he helped me out there. Okay. And then also I got to meet our new mentor, Mustafa. Yeah. Okay. So he joined that session too. So I met Mr. Okay. Great. Adrian, do you want to add something to what Jack Ruthie shared with us on the project? No, everything's fine. The probe was more challenging than we expected at the beginning because of JGIT and so on. Next ones, I tried to create, I created a project on GitHub to list the tickets, other issues, what we want to work on and all of them tried to make them by difficulties, making the one that are less likely to be using a third, a complex third party library to interact with elements for later on the project. So I tried to make sure that we have challenges, but not right away, which was not the case for this problem. But yeah, no, it was, it was good. And yeah, the per-programmization was very interesting. So thank you for sharing that experience, Jack Ruthie. I like the smile you have. You made good progress. So, and maybe some ideas for other teams, although it's time consuming and difficult with time zone. So it's not, but I like when good techniques are shared. I would like also to add that Jack Ruthie offered to kind of do a post-mortem document on the probe. And so what you said, Jack Ruthie wrote that document and it was very interesting to see, because that explained also, it shows me what Jack Ruthie understood and how she felt about that implementation experience. So that also shows me what I did good or bad. And so I can improve in the future. So thank you, Jack Ruthie, for that initiative as well. Very powerful. Thank you for sharing that. So one idea was to share the screen and work together. The first was to start listing and having notes somewhere of the potential challenges and organize yourself and third, writing down the experience so that everybody, mentor and contributor can learn from the experience. So maybe not adapted to all projects, but a very good technique and thank you for sharing that. Just leave a few seconds if you want somebody wants to add something. Or if anyone has a question. No. Okay. Okay. Then we'll move to the next project being building Jenkins IO with alternative tool. We have Vandeet. Yes, he's there. Vandeet, you have also a smile. So what happens? What do you do? Well, I was working on the UI bundle for the entora site and I was thinking that it would take much more time than that, but it didn't. So I think I did much of the part that was implementing the look of Jenkins to the site and I sent a preview of that and I think next week I will start putting the actual documentation so we can work from there. And the heavy lifting part of the manual labor you can say is I'll have to shift, I'll have to move all the images into the right directory manually and I'll have to edit all the links. So I think it was a good week. Yeah, it looks like it. Vandeet, a good tip that I learned with all those years is if you need to repeat something three times by hand, it's worth looking into automating it. Automated, yeah. I'm writing a script, yeah. But be a good lazy developer if you need to repeat something by hand three times, stop and think and generally it's worthwhile. I'm planning to write a script for the links part but the images I'll have to do that manually and that is the manual labor. You can't automate. Look at yourself doing it by hand. Here I don't have to intervene this discussion you can also have with your mentor. Talking about mentor. Chris, do you want to add something to what Vandeet shared? I think we're making good progress like maybe I don't expect it for the first week is in the coding period and I don't have anything else to add. Great. Sounds good. So great. I like to hear that. Leaving a little blank if somebody wants to ask a question and make a comment. Gives me also time to read my notes. Okay, let's move to the next project being Docker based Jenkins quick start. So thank you for joining and thank you for the gods of the Internet that made it possible for you to join. Hello everyone. So we have decided to create a simple Docker compose file for this week's work and I'm working on it right now. I'm having I got some issues and it's getting fixed getting consulted by mentor to so by this week, I think it should be completed. And we are also discussed to start discussions with the infrateam and docs team for the next week. I think we'll schedule it for next week. Okay. Okay. Things done. Okay. Okay. Good. Ashutosh did I understand it right because I've seen, I look what's happening from very far and mentors do a great job so I just looking. But I've seen that you were running into some Docker compose issues and things where one flavor with no AES or whatever with the SSH protocols. Those are working with some Docker images but not working with others. And I was having issues with keys. Okay. This incorporate proxies. These are, are you still stuck or were you able to get the problem is solved. Yes. Okay. Good. So did I missed the answer in the Gitter channel or different method for generating keys so that solved the issues, but we still don't know why that was not working. Okay. So good. Well, I look into it because it is subject that tends to interest me so I still have some. Some good rests of knowledge about about that Bruno do you want to add something. Yeah, why not. I saw Ashutosh asked for help and thanks for asking for help by the way Ashutosh. It's always better than staying stuck at home and able to do anything so thank you for sharing that with us. I tried to solve Ashutosh problems and unfortunately I fell into a rabbit hole once more. It's my habit. Of course habit rabbit rabbit hole. Sorry for that joke. And because I was wondering, wouldn't it be nice if we added the jcast plugin by default without adding a Docker file just into Docker compose. And one thing leads to another to another to another. I now have an ugly and very big Docker compose file that we won't be able to use as is. But maybe it will be a source for a cleanup later on Ashutosh for maybe a more. Docker compose file we see anyhow sorry for not having been able to help you with that problem but yes we are working together which is cool. Well, which is cool and you obviously have a lot of fun digging into interesting problems and finding solutions so good. The important message here is if you get stuck. Ask for help, or at least mention it so that the mentor can start looking mentors. Don't have all the knowledge of the world. They you just ask and you're going to get the answer and no that's not how the world works. I'm sorry for that. But one thing is explaining the problem to somebody else that's called rubber ducking. Oh, oh, but that's obvious. I didn't know that I say it. The problem is now obvious. So that helps or at least making somebody aware that you're struggling or that you have difficulties. So this is an important lesson to have and now the cooperation needs to be set up. So for me, interesting lesson there too. Bruno, you would like to add something. Yes, rubber ducking works better when doing some programming or something. You know, even if the other one is not programming at all just asking stupid questions because doing that via chat or email whatever doesn't work that well. You know, it's better if you manage to find the time slots and work together. I don't look like a duck but I'm not a bad. I don't know now why but now I see you with a big peak of that. Anyway, here. Thank you. We're still at the start of it. Problems will come and go. Everybody will find this technique. Adrian has a lot of experience and we'll check through the solutions we've found here. No hurry. No panic. We're starting and I see good progress and I see smiles. So this is what I'm looking for. So that's good. Just leaving a blank if somebody wants to add something on that project. Oh, I have a little question for Ashutosh and Bruno. Bruno helps. He's available. He's on a completely different site. I don't see him. Ah, bad boy. Just kidding. We haven't seen Saeed for a while. I think we had him on the first introductory meeting. But on the regular meetings, correct me if I'm wrong Ashutosh. I don't think we have seen him yet. I don't think he's on the Gitter channel either. Okay. Bruno, I suggest that we have a little discussion about that and see how we move on with that. Okay, thank you very much for the update. Good work. And I'm jealous that you have good fun finding solutions. We still have one more project to get up. Yeah, but this was the fourth I was going to ask here. So harsh. They're turning on the camera. I like that. So harsh. Tell us what is your the last project there. So I hope you will continue in the positive moods of the three other projects and tell us what happens. Yeah, it's been a long week. I did a lot of things actually. So, so I made a very long draft PR literally so it got reviewed by Basel, and I made the plugin work like I migrated I almost achieved the first milestone, and I migrated it but the problem came like, I broke the record compatibility with it and basically pointed it out and we have to rework it, because what I did was I mixed two PRs in a single PR. And that's not what you do. Okay, something. No, I said well this is one of the pitfalls. I'm interested to hear Chris's opinion there. Can you explain what is the problem and what you should have done a technique wise not too much in the details but so that others can learn. Like, we, what we wanted to achieve was we wanted to remove some part of the plugin, and we wanted to retain some part of the plugin so what I did was, I did both of the things at the same time like we wanted to remove the version three of the lab, but we wanted to use version four and we anticipated the incoming version five also. So the problem was, we wanted to keep up the system that uses both that uses both the version, but what I did was I removed the system which kept both versions and I only, I made the, I made the plugin work just with one version, and I removed the second one. Now, I didn't really thought about the future thing like which Basel pointed out that someday the other version the more future version would also come, which will make the version for the older version and we have to keep that intact and thus I broke the backward compatibility with it. So that was the whole thing, like, there were two PR the first PR was to remove the version three and the second PR was to keep the both of the versions intact so I just mixed both of them and that was too much. So what I have to do in next week is just to make a single PR and in which the both plug in both versions of get lab will be used and after that in the latest stages of the migration I'll have to remove the version three and use version five instead. So, quite interesting thing that happens with me. Okay. Can I summarize your experience. Big PRs complicated PRs is a recipe for disaster. See a lot of people nodding there. Okay, it was a prototype PR actually, because we knew just this kind of thing would happen because the beam decided to migrate the thing but we couldn't do it in steps we had to. We had to take big PR for that, and we almost anticipated it and this was going to happen even mark knew that we will have we will be having compatibility issues. So what we decided to do was we wanted to try stuff. So we made a draft PR and now I will break the PR into smaller chunks. I think it should be it would be much better and more successful like the other technical problems that I have will be discussing in tomorrow's meet that we'll be having it's going to be interesting me because we don't have much information about the backward compatibility on Genkins. I have a little question for you harsh you you've seen that you broke the backwards compatibility so how did you see it did were the tests failing. No, did you test by hand. No, it was not about the test actually I got the plug in working. The problem was basically pointed it out that I didn't think of the future. I was, I was too much immersed in the present. And that's the problem. If I would have used my brain much more and thought about the future this wouldn't have happened. I should have used my brain. I know here. This is learning doing experiences. This is here. This is a very interesting experience and your difficulties are also useful to your colleagues and also for me so I always learn on that. So I still see a smile on your face. Because I know how to handle stuff like I've been into such bad situations I can handle anything. Okay, good. Chris, do you want to add something. Yeah, I actually have been worried about like we are how we kind of rush into things instead of like planning things and talking over first because that's most important to to reduce the chances of having to we work everything. I so I know that process maybe comes frustrating. That's why I wanted to ask for more plans for us, but it seems like that that didn't happen, but it should be fine. Okay, so and and here. Well, I'm sorry for that but here I use this meeting here trying to pinpoint some lessons that people learn so that we can share them. So this is why I generally pick up and Chris said something very powerful here that sometimes taking a little bit more time in planning, thinking the things over. You can avoid a lot of waste of time and toys over a good point. Chris, do you want to add something. Another thing is that I kind of want to do in a more systematic way. So it's like more, more like diagrams more chance to help visualize things so we can discuss together and agree on the plan that we all things we've asked for the project. Okay, good. Generally. Can I see a smile on your face like harsh. Everything's going well. Well, I don't need to turn the camera on that's no problem. It's more it's more generally information so project is going well. Right. Okay. Thank you. I can fully understand that some environments don't allow to turn the camera on. We reached the end of the meeting, oops, we still use nearly all the time I'm, I'm very interested in those conversations so thank you very much for sharing does somebody want to add something I have one point I just leave a blank if somebody wants to interrupt and go. So the point I wanted to make was just to so that you know I already mentioned it last week. I'm going to set up a one on one meeting with the lead mentor of every projects just to go around and having the that I'm, I'm not reassured but that I know that the projects are running. I have during this meeting but I want to one meeting there if there is a mentor that would like to have a one on one chat with me. He just needs to ask for it but I'm not going to waste everybody's time on that. I also going to send a date propositions to the contributors for you so somewhere. The week of the 10th, 10th of June so not next week but the week thereafter so that we have plenty of time to organize at a convenient time for you. So that's it. Thank you very much for sharing your adventures. I see good progress fun. So let's continue that way and I wish you all a nice and pleasant week everybody. Okay, thank you so much. Bye bye everybody. Thank you everyone.