 Here we go. Hello everybody, welcome to this Google Summer Code 2023 office hour. Welcome everybody. We're here to round up where we're standing with Google Summer Code. We're also going to propose a date for the end of GSOC presentation of what has been done and check if all is okay. So first of all, what is happening on your side? What were you able to achieve, learn, or have trouble with? And what is ahead of you in the coming week? I think you know how we handle that. Jakruti, you're the first one. I'd like to know why is it because of the alphabet? No, I don't know why. So you're always the first one. And with your smile, I like it very much. So Jakruti, share with us what is happening. Hello everyone. So the task I was working on last week has almost been completed. And this week since most of my mentors are on vacation, so I really am reading mostly about Google's concept. And also I was thinking of the next task that I have to work on. I think in one is back to be able to guide. So maybe by this weekend, I will complete one of the other tasks. That's all from my side. Mostly I'm self-learning this week. Okay, good. Yeah, a lot of things to discover. Well done. I wish you a lot of courage in to enjoy what you're going to learn. Thank you. Antoine, do you want to share something on your side or was a resume from Jakruti? Well, enough. Go ahead. Yeah, everything looks good. I was in it. Okay, so I was not able to like provide that much information. But I did review some code and I need to have a look for the next task. I saw the question on Gitter, but I didn't get time to answer yet. So I'm going to do that as soon as possible. Okay, so everything is moving, work to do. And with this period of holidays, we need to organize things. Good. I need to tell people not to message me while I'm on meeting because it's disturbing me. I'm a single threaded computer. So okay, next one in a row is Harsh. Harsh, you also have a nice smile. So how are things going on your side? Yeah, I have a smiling face. What to do? So yeah, for my project, like the production code is almost like almost ready. Mark is currently on a vacation. So the interactive testing has stopped. Like I myself interactively tested some bit of it, like the proxy ones using the CLI, but yeah, it's fine. The production is fine. I and Chris are working on the automated tests. They are getting fixed, even if they're quite hard to fix, but they are getting fixed by time. And I hope that I'll be able to fix the automated tests before the project like deadline. That's that's it. That's what's happening. There was a stretch goal for you, right? No, like the Docker based tests were the stretch goal, not the unit tests like the automated unit tests. They are the Docker based tests are based on GitLab 8 and they are. Okay, good. So, okay, interesting, interesting thing. Chris, do you want to add something? I think we we might need more time to work on the fixing the automated tasks. But I'm trying to help out. So hopefully with the two of us working together, we can can play on time. Okay, I forgot to research what was required to give some additional time. So like the issue with the the thing is like the GitHub, the GitLab plugin, people who are using the GitLab plugin are complaining because of the things which have which have which was broken due to the due to the GitLab 16 changes. So we need to do the automated test before releasing the plugin. And once we release the plugin, we have to like do some changes in the plugin so that it's compatible with GitLab 16 so that people stop complaining because we are getting issues and it's Chris is a maintainer. But that means that there are real people using these plugins, which is always interesting. Someone's life is hell because of that, like he was writing that his like his pipelines are broken or something and he wants things to be faster and GSOC is like blocking him. So we are kind of sandwiched between maintainable food and the GSOC. So yeah, but automated tests are important. It's actually quite difficult to fix them because it takes time to figure out what's wrong, but I and Chris are trying to do it as fast as possible. Majorly like four or five classes of tests are creating the major major cause other than that. If if we are able to fix it before the deadline, then it's then it's great. But if we are not, I don't know. We're going. We're going to see. We're going to discuss that with your mentors. Great. Thank you for the update. See, you have a lot of fun and especially you're learning quite a lot of new stuff with that. The next one on the row is Ashutosh. Yes, we can hear you. Tell us this week. I had some assignments to do for college, so I wasn't able to put that much hours, but now it's done. So I should be able to put the right now today, tomorrow and weekend. And I was working on updating the plugins with data actions. And that PR is almost completed. It's working correctly. I've just tested it. And last week, I had a meeting with Mark and Docs Office Hours on how we expect me to integrate the project into the Jenkins.io. So he told to create separate PRs for different tutorials for this week. So for that, I had to ask him in this week's meeting about how it will work because right now we are using my own credentials in Docker Hub and are there to help credentials? That was the purpose of this PR to start that conversation, to know what is required. So you started that. So first, we also need to work with Infra Team. And yeah, so first we have to decide, first we'll do it with Infra Team or Docs because Docs can't be done without Infra Team points. But right now, Harsh mentioned that Mark is on holiday. So I just remember that this week there will be no meeting. The period is a little bit weird because Bruno, myself have been off for some time. So also the meeting you have before this meeting here, I couldn't make it. So it's a little bit in between. But I see beside your college work, you're advancing. That's a good thing. Chris, you wanted to add something? Yeah, I just wanted to add that the Asia Docs Office Hours is cancelled this week. Oh, yeah, Mark is, yeah. Is the European time one on? I can attend that one. I think so, yeah. So that one's hosted by Kevin. So it's still on. I'll attend that one. Thank you, Chris. Other than that, I will also be working, I will be testing if I can use Update CLI or Defender War 2. Just how they work. Good. That sounds, yeah, great. So that sounds really good. Next one is Vendit. Hi, John. What's happening? Yeah, I've been here. I'm here after a long time. So hi. I have my exams going on and I still have my exam on 19. But I had a really big, I had a really big preparation holiday, you can say around eight days. So I started working there. So yesterday, yesterday, we had a meeting with UXIG. We had a meeting with UXIG where we demonstrated the UI exchanges to the team and they were really appreciative. They were really appreciating it and they liked the design and the UI exchanges I did. Other than that, Chris and me had a meeting before that regarding how we are going to use Strapi CMS with Gatsby because that is something that we changed during the, during, while this was progressing. So we now know what we need to do. We'll be publishing, we'll try publishing the blogs on Strapi admin dashboard and we'll create roles there. So people like authors and editors, which will be maintainers can submit blog posts there. So there was, there's that also currently, currently we have an issue we are facing. On Jenkins.io, we have over 20, we have over 12,000 links and we have over 12,000 links and Austria and Tora references links completely differently. So we need, so and that can't be automated. So I'm manually doing that. I'm like, I'm copying and replacing it in, I'm copying and replacing it in every file, but how, how they are written, like some have, some have backslashes, some have not. So I have to do that manually. So because of that, maybe like, I think we would require more time to complete that because we want to, we want to, we want to like give a finished product to Jenkins. I want, I and Chris want to and other mentors too. So we'll be doing that. And I think we will need to take around three more weeks for it. And I think the blogs and Gatsby part would be completed by then, but the and Tora, the linking part is the most difficult we are facing right now. No, Vandit, you will have to work hard to convince me that it can't be automated. You sure of that? That it can't be automated. Do you discuss that with your mentors? Yeah, it can be automated, Mark, because and Tora does not use the slashes as like you can't just copy path for the links, you have to, you have to reference the link, reference the page interpage linking a page that exists in Jenkins.io. You if you want to reference another page to in your page, you'll have to do it something like we have components and components colon the module in that component colon the page name dot ad hoc. And if it contains us, if you want to like if you want to redirect to a fragment of that page, we'll have to add an hashtag and the name of the fragment and you'll have to add that fragment on the page where you will have that we'll have it as an ID to like reference it. So it like there's a there's a lot of work. I have completed user documentation, Google summer of code pages, six, but here and there, there are still some links that are not working. And last I checked it was around 1500. It was it was it was 12,000. We are down to 1500. Now, I have completed 500 this week. But and I'll complete the rest of the thousand this week. And after that, we'll have to see the links that are not working. That is the main problem. We'll have to check each and every page and fix that. Yeah, you probably discussed that with your mentors, but I I have a natural reaction saying when hand work or manual work is you're too clever with that. No, I'm not I'm not manually doing that. I'm copying and replacing the links that like if we have a link to six index page, I'll yeah, I'll fix that. It's automated. Yeah, okay, automated. But then I'll have to check if it's working because sometimes sometimes I sometimes I mess up things and like sometimes it does not work or sometimes I tried using I tried using regular expressions to like do automate it. And I think I created a test branch, I did that and everything broke locally on my machine. It like all the links, it became a mess, entire pain. Okay, now I trust your judgment. I trust the judgment of the mentors. Just it's it's a spontaneous reaction. So we'll fix that. We'll definitely fix that. Since we are down to 1000. So I think we can fix that. Okay, just remember if you need to do the same tasks three times, then automated that automated. So yeah, so yeah, I'm I'm I'm literally I'm literally copying and replacing it everywhere in Jenkins dot are that the repository I'm I'm doing it everywhere. Then when I check, when I see, oh, this link is only getting used in this page, I'll have to do it myself. That that is. Yeah, yeah, Arsh, definitely completed, we completed the events page. Previously, we did not have the events calendar on the repository on the project we are working on. But now we have it with the help of with the help of Chris, he's a really help when things come to Ruby, because I don't I don't know anything about Ruby. I can understand it. I can understand we have classes there. But when if you ask me to do it in JavaScript, I won't be able to convert it. Yeah, okay. So you heard the message that I had. So it's looking good. You're making progress. Chris, is there something you'd like to add about that project? Yeah, I think there's some features we still need to convert from a Ruby to JavaScript, like the major and section, because like the card like used, it's kind of different. And the setup we have is different previously. So we may have to think of a way to like, implement it realize it. Good. Well done. So I see you're having a lot of fun. Arsh is jealous of your project, indeed. Yeah, when you when you have a lot of work to do, you learn a lot, be jealous. You should be. Okay, no problem. Now, we discussed Alistair and myself about a possible date for the interim presentation. Currently, we're looking at September 21st. I like the Thursdays. So it's this time slot. And we would take one hour at that time. So the question, what is an expression in French? I'm not going to repeat, but the question or $1,000. Does that date work for everybody? Or does somebody have an exam? Arsh has exams at that time. Go ahead, Arsh. Is it September 21st, you said, right? Yeah, I have an exam. Ah, is there, so Ashutosh, it works for you? Yeah, okay. Vandeet, it works. Okay, good. Yeah, it works for me. Jakruti, would it work for you? Okay, so Arsh, you're in minority. No, no, we need to find, especially as you want to do it live now. Do we have an alternate to propose Arsh? Earlier or later? Or another day in a week? Like earlier, like if you can before 15th, I would say, because like before 15th, I'll be having exams, but it will be quizzes. And like quizzes don't have much weightage. But between 18th and 24th, I'll be having the main examinations. They have more weightage. So I need to study for that. I can manage the quizzes. Even if it clashes, I can manage the quizzes. So you can keep it before 15 if you can. Otherwise, it's kind of a message situation I am in. Like I have exams all over the place, like literally all over the place. I have the impression trying to mix oil and water. It needs a lot of shaking before that works. So yeah, I just can't help with examinations. Like what's up? So the 14th would work for you, Arsh? Or is it earlier? It should work. Again? It should work for me. Yeah. Yeah. Okay, let's do a round again. Ashutosh, would the 14th work for you? Yes, it's fine. Okay, Vandeet. Yeah, it works for me too. Okay, good. Chakruti? Yes, yes, it works for me. Sold, sold. Now, I hope the other one, so don't move. Alissa, is 14 okay for you? Yes, the 14th works for me. Okay, then we'll set for the 14. We'll discuss now the organization. We're now, it's in one month. So for me, that's good. And discuss with your mentors how to organize that. Good. That was work to settle. Is there another subject? We have a pending subject that I need to work on is the people that need more time to complete their project. So we need to check with Google what can be done there. So we check. Are there other subjects that need to be clarified or Arsh, go ahead. Yeah, so like regarding my project, like it involves like getting the GitLab plugin to the production, right? So with when the like project deadline, according to the project deadline, it should be deployed till like till the deadline, right? Or am I responsible only to like, like migrate the plugin and it can be deployed afterwards to the production? I need to check that with the mentors, raise that with the mentors. The mentors are responsible for approving that the project is done, completed or achieved is its objectives. So please raise that discussion with your mentor. And if you have a problem or conflict reach out to me there. Okay, another subject, another attention point. No. Okay. Well, that was also a busy session today. I wish you then nice work, nice learning and success for for next week then and talk to you later next week. Okay. Bye bye everybody. Thank you. Bye everybody. Bye. Bye.