 Here we go. Good evening. Good afternoon. Good morning, everybody. This is the GSOC 2022 office hour. Now on the regular schedule, but not on the regular Zoom meeting. I apologize for the inconvenience of having to change the meeting. So welcome, everybody. We have Vian and Chris on the call. And let's go round. So this is fairly open meeting. So let's make it a little bit like a stand up where you do a short summary where you're standing with your project. And especially do you have impediments or things that are preventing you to move as expected? So, Vian, let's start with you. So you're working on the pipeline step documentation. Tell us what's happening. Yes, so the project is going on great though. So within this community bonding phase, we were able to have a dedicated meeting towards a project along with Christian. So Christian had organized that for us. And we have set the regular project project needs to be at Tuesday for 600 UTC. And we have also decided to use the docs channel for our project. So we are able to actually also put up some requests regarding the same and get the feel around the project. So I think that as Christian asked me to do, I've written an epic on Jenkins JIRA as well for the entire project. So we'll be tracking the projects progress using that epic. And within that epic, we are creating two stories. So these stories would largely classify the work that I'll be doing for the two coding phases. So in that particular story, we'll have a list of tasks, which, which are, which I need to be doing, you know, to get that task completed. So I've also created a story along with that. Parallel to that I have also since the first house will be more UI related. So I also created a wireframe for the landing page of the pipeline steps, which I'll be presenting in the docs office hours today, which is at 1800 UTC. And so we'll just get to get an approval of all the community members, how they feel about that wireframe, but that they require any changes to that. And then we can go about thinking of a possible implementation. So there will be around two or three different layouts, one for the landing page one for the plugin page which has all the step details. And then finally, we'll have to come up with the page for the parameters of those steps. So this is a step by step process. So I'm like on the first step right now. Yeah, I think it's pretty great. Okay. Enjoying yourself. Learning. Okay, I see that. I've tried a lot of new things with this quality, like 10 days, just 10 days and already doing many new things. So yeah, it's great. A lot of time is spent in communicating, explaining, writing notes and things like that. This is important. So this that way you get everybody together. Are there things that are worrying you or that in this particular bonding phase or things that where you don't feel that easy. Yes, so the basic things that we were discussing for quite long about the changes that we have to make the content of the documentation so the changes that we need to make the generator, which is the main back end behind that. And to that, we have discussed some possible solutions. But the thing is that as of now, none of those will solve the main concern of the users which was regarding the examples, the presence of examples to the steps. And that is really hard to do automatically, unless we are able to emulate the snippet generator on the website itself. And that is something that is pretty much out of the scope of the project right now. As Christian said, we, there's a nice scope of research for that. So how can we get the minimalist element of Jenkins core, only the part that performs a snippet generation, the plugin manager tools, all those things. How can we capture that into a web based application so that the user can specify what plugins they have and get the steps according to that because as of now for example if a user has some seven or eight plugins. And according to that, they'll have probably 15, 16 steps for those plugins. They'll have to search for those tests within the 15 minute steps that we have on our Jenkins.io website right now. So it is quite hard for them to understand which plugin is providing which step. So for every step we have some parameters for example for checkout step for the SCM parameter we have different SCM providers get SCM, so for that it is very hard for the user to know which plugin is actually providing that choice of parameter to them. So that is something that we have to implement somehow. We have the summer to do that and to discuss in and see that so well okay that's why we have the confirmation that you have a very interesting project. We are not late at all but don't forget to update the project page on Jenkins.io, so that I have a good idea, so that the community has a good summary, and if people want to follow because I'm interested to follow the discussion. So that I have the references there, where do the brainstorms in these happen? I'll probably send up a request by tonight, so I'm ready with the draft, just adding some links and some content is there. So we have a document in which we'll maintain the notes of all our meetings and also the links to the wireframes and the epic on the Jenkins.io. So I will compile everything and then I'll put up a request by tonight or by like tomorrow. We still have some time for that, so don't worry too much about that, but I'll remind you it will help me. Okay, thank you very much for your update. Obviously nothing is blocking you in moving ahead, so this sounds good. So the next one, well no, I'll leave it. So Chris was earlier on the call but I'll move. Drash, Drash, do you hear me? Yes, I do. Hey, great. So sorry and apologize for the mix up with the Zoom channels and the way the Zoom channel works, not being as usual, but there were some technical issues to get it sorted out, but I'm happy that people were able to join. So happy to see you. We're doing some kind of stand up like roundtable to see where the projects are standing, what's happening, and particularly try to listen, are there any impediments or things that don't work as expected or are more difficult than expected. I don't think so, but just to explain the format. Drash, go ahead. What's happening on your side? Yes, so I had a meeting with my mentors and we discussed about the project as we planned during the proposal. And during that call, we went on some more detail about how we want to make it more concrete by adding few more details. So there were some changes and they suggested me to start working on an architecture diagram so that we have something on paper for everyone to see and they can contribute their ideas and discuss and come to a mutually decided architecture. So after that I started working on one and I posted link of it on our Gator channel, and I got some really nice feedback from Adrian, and he told me like you do this do that, then I made some changes and I updated the architecture diagram. And I'm waiting for him to tell me more on that like does it sound good and any more changes. Of course, there's going to be lots of changes. This is just an initial diagram. So this is where I am. And after this, when it gets like at a good stage that we are convinced that this seems like a good architecture to work on. Then we will be like dividing it in some workable tasks, which might not be difficult because most of that is done during the proposal phase, and then readjusting the timelines as needed. Before the contribution period begins. I mean the coding period begins. Okay, you have regular meetings. This communication channel is set up. Yes. Okay, it is going every Tuesday. And okay good so while I need to make a note and I didn't find the link but maybe I'll ping you directly because I'd like to I'm interested. The four projects are super interesting. So I'd like to listen in if my, my agenda allows me so I need to check if the link is on your project page. Obviously, the page is up and has sufficient details so everybody can follow up. Are there any worries impediments questions or things where you'd need more community I see you you're working very closely Adrian just joined. That's very well up to now. Sorry for being late I was in the incorrect meeting. No problem Adrian. So Drash for you are the things that are blocking you or where you need help on So currently nothing is blocking me, but I do need help in coming up with like some concrete architecture diagram and it's currently in progress. And I'm reaching out to my mentors and specifically Adrian is helping me right now to make some changes. Yes. I've I've seen interesting conversations going on there. Perfect. Good. Thank you Drash for the update. Thank you. Yiming on the call. Call you hear me. So the format is a quick stand up like update. Where are you standing what were the actions were where what's going on and what I'm most attentive to is but I think I'm worrying much for that is are there any troubles or things where you need help. Can you tell us where are you standing. Okay, I held the meeting with the mentors in a repository maintainer. We talked some details about the project, and then I wrote the timeline and the design doc in detail this week. I think I have finished there yet so I don't have any questions that have up to now. I'm good. I mean the project page has been updated. So you have a regular meeting. Yes, we have regular meeting in the on the Monday. On the Monday. Yeah, to check. I'm not sure that the link to the meeting is is on the project page. I've checked that. So big question you mean are you having fun. Yeah, cool. This is the most important thing for me so this is. Okay, that's good. So perfect. Thank you Chris and yimming and the other mentors for moving that forward. So great stuff. And let me look. There is the fourth project. Your cash and Mark wait but I don't think that we have somebody on the call for that project. Mark is currently having important conversation with his grandchildren. Oh, he's he's away. He's on holiday so we will not have an update on that. But somebody wants to add something ask a question or share something with a group. I think we also have a I don't know if so I dirage if you if you already said that but we also have a recurring meeting for the project else scoring system. That is just to have a check up. We moved the idea of using slack to having the Gitter channel so that it's more open. Easier for me to follow. Yeah, yeah, it's again an idea from from dirage so thank you dirage for linking that. Really, really nice. Really great to have you and thinking about that as well. So no, no. Everything I think everything's good for us we are starting so. Yeah, I wouldn't say when you said you were not blocked but in progress it we are just starting the first week so it's kind of normal having the starting the what we what we discuss on Tuesday so everything's fine on our end. Perfect. Logistics, I will talk with Alyssa, who is on the on the call here trying to fix the Jenkins zoom account so that we can use that and use the initial link that was done I use my my private account here for the meeting. Thank you and I saw for the people to share their camera a lot of smiles so we're moving we're starting the thing. The projects ideas are flowing all over the place so it looks really great from where I'm standing. So let's close the call here. We can meet next week to see where where we're standing. And as usual, if something is really bothering you you can reach out directly to me or to the arguments. Thank you very much. I'm leaving a little blank if somebody wants to add something and then somebody I know says always go go go. Nice rest of the day everybody. Yeah, have a great day everyone. Bye bye bye everyone. Thank you.