 Hello, so just started the recording here. Good afternoon, evening, morning, for whoever would join the call later. Welcome to this June 16 GSOC office hour. Thank you for joining for some people. It's already late. So besides the heat, which is a subject here in Europe, but I think that in India, you're playing in a different league where you use too much higher temperatures than what we complain here in Northern Europe. So I just would like to go round as we go usually. So we have several people. I wait a couple of seconds. So we have three projects, four projects being represented here. So let's go round, round, stand up style and see what has been achieved done during this last week. And are there any impediments preventing to move forward? So let's start with Roushikash. I hope that was nearly good. Roushikash, go ahead. Yeah. So last week, I worked on building the UI where administrators can take throne syntaxes as input provided as input to schedule the maintenance task. This week, I worked on adding form validation and which throws errors on the UI if an invalid throne syntax has been entered. Then there's a save button on the UI. Once the administrator clicks on the save button, the data is saved internally in an XML file. So that whenever Jenkins is restarted, the data can be retrieved from this file. So that's what I have done this one week. So the next week's agenda is to schedule maintenance tasks by adding it into a queue for Git version greater than 2.30. Okay, very good. Is everything running as you expect? Running into troubles? No, no. Okay, big question. Having fun? Yeah, yeah, full fact. It's always important. Okay, nice to hear you. To hear that, thank you for the update there following the order of... I can't watch the chat together. So if there is something I should know, say it's nothing. I'll call it out. No worries. Okay, thank you. So let's go, let's listen to what Diraj has been up to. What happened last week or this week? Yes, thanks a lot. So in last week, I published... I pushed my first PR to the project repository. And I got to know that it was a rather long PR. I realized it later. So I feel bad for the reviewers. It's like, very long. So Adrian, they made some comments and I'm working on them. And they were very, very useful review comments. And so it might take some time. And after that, Adrian has also created another task for me and added it to the milestone one under the GitHub projects section that is there for planning. So another task awaits me when this one gets completed. So going good. Great. So there is always a question I asked, do you have any impediments or things that are preventing you to move forward? Currently, I don't think so. Not really, because all my questions are answered by Aditya and Adrian and Jake, my mentors. Okay, great. I'd like to pick one of the points that might be of interest to the others. So you realized that your first PR was quite long. Yes. And it was not easy to review. Can you give us a few details there? And maybe this could be interesting for the others? Sure. How long was your PR? It's 985 lines of code. 925, to be exact. I can give you the link as well. And so it actually sets up the project, then fetches the data and populates it into the database. So this can be divided into three parts. First, setting of the project, PR for that. Another one, fetching the data from somewhere from an online service. That can be PR2. PR3 can be populating that data into the database. So that's how it should have been. So it would have been easier to review. And so you had everything in one big pot. Exactly. I still do the mistake myself. And this may be something interesting to do or to know is it's like when people are eating, you don't load your plate too much. So it must be in eatable chunks. Otherwise, you end up with a pile of things and the people that are going to review would like to help you on that are going to say, okay, I'll never go through all that. So it's sometimes interesting to discuss with the reviewers, your mentors to know what is an adequate size. And the other hints I can give there, but discuss that with your mentors is you can create several PRs one after the other because each item, you can do as many PRs as we don't pay for PR. And I like the comments that you made. You felt sorry for the reviewers. And this is a very, very valid point and very good point. Thank you, Doras. Thank you for sharing also your experience on that. That was good. Thank you so much. Okay. The next one in the list, Vihane. Hello, everyone. Hello. You know the questions that are going to ask you. So just a reminder. What happened last week? What do you plan to do? And do you have any impediments or difficulties or worries? Yes. So I started working on the task one, which was to create a sidebar, a separate sidebar for the documentation. And that has been going quite well. So I have put up the first pull request of the project. And there have already been a lot of comments about it. And I have also pushed another commit to address those. So yeah, I got some help from Tim as well with regards to what can be the possible ways to do it. And today I think I was able to get a more finished version done and pushed. So I think in this week, we can, if the reviewers agree, we can close the pull request and I can move on to the second task next week. Okay. So I see that you're progressing. That's good. Any worries or difficulties that we should know about? Not really. So any things, any worries, issues I've already asked on the GitHub or GitHub. So I think everything is going smoothly. Good. Okay. Nice to hear that. So good progress there. Yiming, so you know the ritual, stand up ritual. So nice to have you on boards on this call. So what happened last week? Oh, okay. Thanks for asking. I finished designing the function structure last week. But it seems that I need to redesign the feature now because I didn't meet the need of the project maintainer. Our expectations are pretty different. So but now we just came into agreement at the channel discussion about what the feature needs to be. You can see it in the, in our channel. And I'm coding on based on the expectation. So I will start a proof of concept project firstly to show that I understand the concept completely. Okay. Thank you, Yiming, for sharing that. I've been involved in that discussion. So and we'll have a discussion tomorrow there to make that progress. There are a few lessons that I'd like to share about that and things to know. The first one, there's no wrong answer. So we're working together and what is very important is that you share what your intention is, what you want to do and people can react to it. It can be discussed and negotiated. And see, I see it more like this. I see it more like that. Need to think now. What I'm cautious is and what I react to in the way you explain it is I did not meet the expectations or the requirement from I'd like to put some, some, some a grain of salt there and say, don't, don't stop to that. It's important that we listen to each other and that we correctly understand the various arguments. Do you understand my point, Yiming? Yeah, yeah, I understand. The reason why I say like that is that our expectation is on totally different directions. So that's all I want to say. Okay. And this is perfectly okay. It's not because somebody else has another opinion and view that your view is wrong. It's only let's discuss it together. And in Chris, your one of your mentors is also there. I can join into the discussion. Let's put our heads together. And what my goal is, and I shared that also on some channels there, my goal is that you learn how it works, what is the process of thinking together. Working on open source is not as when you work in a company or in a paying company. It's a different process. And this is what I want. I know who am I, but that we want that you experiment learn there. So do you understand that point? Yeah, you're right. The processing in the company is different. So most of the design works can be done by the product manager. So in the open source program, it seems that the contributors need to take care of it. And we're going to see I will discuss with Chris and the rest of the team. I will also discuss with Oleg. I'd like to have a compromise there and that everybody agrees on what to do, the objectives. And don't forget it's your project. It's with your mentors. Okay, let's see in practice how it is, how it goes. In the case of Oleg, Oleg has some very strong opinions because Oleg is joining right now here. So hello, Oleg. You can listen to the recording afterwards so that you know what the point is. So in a summary, what I said is that it's important that the opinions are shared openly and that you find an agreement together. And I was just going to add that for you, Oleg, this project is very important for two reasons. First, because Oleg put an immense amount of energy to make that project achieve that result. And the other thing, Oleg has very high standards in quality. Now, as I said before, this is your project. And there may be differences and let's discuss them together. And tomorrow we'll have a meeting where we'll find. So what is very important, and this I agree with Oleg is, the idea is what you intend to do, the plan and all that needs to be written down so that everybody can see, discuss, eventually advise you and guide you where to go. Is that okay, Yiming? Yeah, I also want to make this feature have a high quality as Oleg, that's right. Okay, so don't worry. We have a discussion tomorrow between mentors. And I want to have first between mentors that we have a consensus that we know how we're going to steer that for the best of everybody. And then we'll have a discussion or your mentors will have the discussion with you to see how this will be done. Okay, great. Don't worry. The purpose is to have fun and to learn things as the others have had. I think we went now round the various projects have the status. Are there general questions, comments, or statements to do I open the floor to anybody? So I have one point that I'd like to add. I leave a few seconds more. So if somebody wants to speak up so well, I will basically have three. So first thing is that I'm going to reach out to everybody. So to contributors and to mentors individually, I'm going to set up a one on one with each of you and we're going to set up and that we can have a private conversation together. I want to be sure that there are no worries or you know, I'm looking for stones in the shoe. You might not realize that the stone is there. But if we don't remove that stone during the summer, you're going to end up with a very sore foot and this is not what we as or admin want to have. And I think it might be easier for you to have this one on one conversation. I will organize that at a convenient time for everybody. The end of June start of July. And so this one point reminder, we're going to have and discuss that with your mentors. We're going to have end of July, an intermediate checkpoint. There's one that's formal for Google that needs to be done. And the other is we're going to have an informal checkpoint. As I said, I'm going to ask every contributor to make a small presentation of his project, what has been done, and eventually a demo or so. It will be a 10 minute presentation. Don't be scared because I know that it can be as scary, especially if we open up the audience. So don't worry. Your mentors are there to help. I can help you also for that. But your mentors are there to train, to know what to say, how to say, and so on. It's important for two reasons. One reason is it's part of the training, of the GSOC training to learn how to do these kind of things. And the second thing is to draw attention from the community on the work that you're doing. Because you can be proud of what you do and you can honestly brag about it. And don't be shy about that. But the other thing is also to attract support and also ideas or recommendations. And it happened already previous years that some project got attention and some very useful ideas were added to the project. Last thing, important takeaway that I liked very much in what Raj raised on the thing is a very common mistake that I do myself to is don't overload your PRs. Don't make them huge. Just envision a plate where you have a lot of food on it. It will fall off and when you bring it on the table of your guests, you're going to scare them. So as you're a good eater, like I am, but this is another story. But trying to make small PRs, this gets it really very efficient. So let's share also these kind of experience what works and so on. Last call, is there somebody who wants to add something or needs to add? Then we're going to end the call and I will request the help from Alyssa that's on the call to process the video recordings so that we can put them online after that time. I can't. You got it. I will work on it later today. Great. Thank you very much, Alyssa. I wish you all a nice end of the day, a lot of fun with your projects, and continue like that. Looks really, really great for you. Okay. Bye-bye, everybody. Thank you, Mark. Bye-bye. Thank you, everyone. Bye. Bye-bye.