 Hello, welcome to the Jenkins-Google Summer of Code of Sours. Today is May 26th. We don't have any specific topics in the agenda for today. So I suggest we just focus on the Q&A and then sync up on whatever logistics activities. And the main question is, do you have any questions? Yeah, we can just discuss whatever you wonder about the GSOC process, your particular projects and so on. So these questions will be on the call. So no questions. Then I have a question to students. Have you already established regular meetings with your mentors? Yeah, so like we have and it's we're meeting every week, once every week. And then moving forward if we need, we talked about maybe setting up twice a week. We have also decided to meet once a week but then are you meeting that's not yet decided. We are finding a time that is okay with all the mentors and then we'll go. Yeah. Now project remote monitoring also chose to proceed with one meeting per week, at least for now. But we may adjust but my recommendation as we discussed last week is to focus on asynchronous communications when possible and when convenient. So don't rely on meetings as the main synchronization point. You have chat and you can drop any questions there at any moment. Yes. Okay. So then just quick updates of what happened over the past week. Apologies that things do not go as quick as a good like. We've had some escalations and more escalations. So what has changed? Firstly, we started sending feedback to the rejected students. I still have a few emails to send but I hope to complete this part tonight. So that you get it over the line. We also updated the GSOC landing page. So if you see my screen, you can see that now we have all Jenkins project service here. So yeah. And there is also a step so for any student including Shruti and you can have these pages. And this we invite you to actually update these pages because they were created just basically quick happen slash based on what we had in the project ideas. So this information is fully owned by you as a student. And you're welcome to adjust it as much as you want and you're welcome to keep it up to date. So for example, you have to find the office hours. Please put them here so that there is some information you have for a meeting notes document in place at the link to that. And same if you see any changes in the background and project deals and status you would like to put here, or if you would like to put some screenshots, video recordings, you can totally do that. And if it's needed, it's actually quite easy to do because even if you don't want to check out the repository, etc, you can improve this page. Well, depending on your experience and currently in the browser which is not locked into a GitHub. So let's try again. Just soak. Okay. So, here should be locked into GitHub and here, for example, if I want to update this page, I can just click improve this page. You can see information there is preview. So basically, we're under a ski dog, there is some data which would be rendered, but the rest you can just see the text. For example, if you want to add a link to office hours, for example, the week, let's say, on my UTC. So it's just an idea. So here, for example, you say one team UTC. So this will render and also what we recommend. There is Google Calendar. So if you go to Jenkins your events, you can see that there are meetings listed. So basically, there are all meetings, including this GSO course hours. So it's called the Jenkins calendar. This Jenkins calendar. Yeah, it's just a Google calendar. You can ask one of the orphan means included me to put it in. And then you can just navigate to a particular meeting. For example, he is a meeting. Okay, I can show you a real example. So we have created a project for a meeting for James remote monitoring. So there is a meeting now calendar. Hope. Yeah. Okay, so this is the meeting. And here, for example, you can see that you have it announced we have a link to the Zoom chat. Later, we'll also Google Doc. So this is a meeting and everyone can see that. And for example, if you want to share that, for example, you click publish event link event and you can put it directly into the browser. So for example, here you can see something like that. And then you can go with your set the meeting. Okay, something like that. And then when somebody navigates to your page. There is metadata, etc. You can see that there is a page providing a link so you can click on the calendar as a visitor. You get. So I might have to cut this moment. No, you basically just can add this link to your calendar. You can also add more information and who's doing his state to edit your pages as much as you want. So these pages is basically a front page for you. So when you will be referencing your project or making it into the jinx community outside once I mean your evaluation. So, yeah, it's your best interest to maintain this page and to improve it. I highly recommend that you just try it out because everything is enabled so you can just submit your pull request. Questions. So, again, this page is owned by you as students, not by mentors. And basically it's your responsibility to keep it up to the, to some extent be expected from the students working on the jinx project. It doesn't mean that you have to put daily update there. But when you reach major milestones, for example, the reservation where you do a demo, or you have released your first feature, made it available to users. We recommend to update this page gradually so that everyone navigates this page and in Google, some of course there is a lot of promotion historically happening. So just keep this page up to date and help others to discover that. So that's what I wanted to ask. And yeah, this is also something you should actually consider doing during the community bonding phase. And another thing as we discussed last week is working with your mentors to create a coding plan for the first coding phase. So what it means that by day one of your coding phase, you expect to be able to actually work on something that might be some flexibility in the plan, etc. It shouldn't be a situation when the first day of coding starts, you open your integrated development environment and see, okay, I need a repository and you don't have a repository. Or I want to do something I'm not sure what to do. So your main goal for community bonding after discussions with mentors is to enable yourself to work with during the first coding phase. And use it this time wisely because it's really important to have everything in place. Christian Jeff, would you like to add something? Nothing for me. Nothing on my side. I do agree with the making sure we have everything in place for the coding period that really helps make things go smoothly. So my advice to everyone also to do the first pull request as soon as possible. For example, if you create a new plugin, you can start from creating a skeleton. So there is a project called Jenkins plugin archetype, which basically creates a skeleton for you. So the first pull request you could do is just using this plugin to generate a skeleton, maybe a few hello world actions. Just to try the development flow in your environment, maybe add some read me a link to the project page. And then when I meet that, and then you can gradually expand because when you have skeleton, you can deliver the rest of the features in a continuous way. And since we are talking about Jenkins project, we really advise doing so. Yeah, creating the first initial pull request with initial data and then creating a small full request as possible so that you can continuously improve your project. I have a question about like, meetings are absolutely essential for, you know, anything that's related to plugin development in terms of what can be needed out of the project. For example, the one. So we started working and we have the recurring meeting set up, but also there are some things about the UI UX side of the plugin and understanding the jelly files much better system things like that. What meetings would you suggest that we should definitely attend. So we can organize not transfers on demand. Again, as offered last time. You can take a look at the recordings we already had. There is a lot of reviewer guidelines. Have you found this information already. Yes, yes, I found the developing plugin and a bunch of videos that are on there and also, I think some blog posts which I haven't read yet. There are blog posts like we discussed last time that is a tutorial on Jenkins, a developer where you can basically go step by step create your first plugin. If you haven't seen that I can show it to you. And in terms of learning jelly what I'm not an expert in it but what little I know what was helpful for me was finding a simple plugin in the Jenkins IO repo and just kind of copying it and it was a little bit of struggle at first and until it clicked. So that's that's one one suggestion and you can reach out to the mentors via the slack between between meetings I would recommend not not waiting until the weekly meeting if you're stuck. Is that would that be helpful or. Yeah, yeah, definitely I am working on, you know, like the jelly files from I think the Hello World plugin and also understanding I went to the GitHub plugin and I was just like trying to understand these kind of so confusing. Yeah, yeah, pick a smaller one, because I think the GitHub may plug in may have a lot of a lot of you if I recall. Yeah, there are many plugins. And yeah, jelly is a quite complicated framework. Well actually it's quite simple but it's not something you would see every day in the world, because Jenkins was created 15 years ago so jelly is let's see more legacy. Yeah, you may have seen that many modern plugins actually use JavaScript mostly plus REST APIs. For example, two years ago when she was working on code coverage API. He used some jelly code, but the most of your complexity actually went to JavaScript. So if you create plugins with rich UI, I think it would be the best approach. If you're interested, there is user experience special interest group. We can continuously discuss this UI and also development of UI for Jenkins, so you can join it. And just run from others there. Thank you. Yeah, so it's Jenkins, your six UX. Yeah, so they basically meet every week or so at the moment. And again, if you're interested when they meet on this page, they also have meetings. So just here you can click on meetings on this page. It redirects you to the Google document apparently in this case. But yeah, there is all the schedule below. So on every Wednesday, every two Wednesdays for PMUJC. There is a meeting and today, it's today. So right after this meeting you can join and just ask any questions or see what people discuss. Yeah, but because I haven't joined the last two meetings or so, but I can go to the agenda. Okay, you can see that. Okay, you can see that the agenda it's, you know, much 17s because yeah, there was an issue with Google Docs ownership and I believe that the calendar link wasn't updated. And here, for example, when things don't quite work, but in theory, if you go to this page, you should be able to see the recent documents like for example, if you go here, you open our meetings notes for JSO. And as you can see, I also didn't make any notes for today. By the way, yeah, all our Google Docs, etc. They should be available for contribution by anyone. So you when you participate in meetings, etc. You, you're welcome to just suggest changes. So there is the review modes. So something going on with the Google right because the request me to reload the page to times already. But here. So what I wanted to say that there are multiple modes, anything suggesting and viewing. So you can figure documents in a way that anyone on the Internet can comment. So what it means that even if you have no permission to the dog, you just open it, I think suggesting. And then you're in the suggestion mode so basically you can say that. That was lazy to be easy. Didn't create it, but you can do it on your own. So, for example, you go to a Google document. For example, you can say that we had funny. And we discussed, for example, Norwich transfers, again, development. And if we discuss any links, etc. Again, you can follow that information. And he's going to contribute because keeping this meeting notes, etc. is also a type of contribution because somebody may read this document or we can wait and use them to improve our documentation, which is not awesome. It would be improved a lot as in the much every other open source project. And you're welcome to contribute in such way just by helping. What else we discussed status check. We also discussed the updating project pages. Does it work for you. So, again, any questions, any comments and sorry for long detours, but I'm just showing how particular things work in the Jenkins community. And this is to us because you did try to improve where we can. And yeah, what I said, if you need a specific knowledge transfer session. So this year, we didn't fly upon any session yet, but we can do it upon request. So if you see a particular area, which you want to get more expertise, if you don't see information if you members don't see information. I just raised a question and we will try to help is organizing that. Yeah, and basically the same for any page on Jenkins. I also, for example, if you go to the through the tutorial, you will go create a plugin, etc. You see a mistake there or you want to extend it a bit. You can always click on the same page through this page and edit everything you can check out the site you can build it locally if you want. And you will need to do that when you work on complex updates. And for example, when you work on blog posts, we expect you to write. And you can find all the information here how to get it running, but if you have a doctor it's actually just a few commands. If you have windows, and if you need to get this ecosystem running, you will like to need windows subsystem for Linux, because I'll make files on the platform independent. And if you need such assistance, please contact me. There are four common cases. Yeah, there are just two make commands. So you say make prepare and then make run. And you get the website of development mode running. I'm not sure what it's not trying for me, but it takes a few minutes to start up because everything to be raised and relatively slow. So that you can do life changes and verify your content in the browser. Similar to how I do it. But you can view real website then any patches to the communication center would be much appreciated, because we as experienced contributors, we have so much sacred knowledge. Sometimes we just do not see your obvious gaps in our documentation, especially for newcomers who just added the project. So any feedback about that would be appreciated. And even if you do not fix the issue, there is another magic button called the report the problem. For example, here. So it's, again, it's semi automated. So you report the bug for the user experience page automatically puts the links, etc. The rest you would need to fill in. But, yeah, for example, you can say that there is no longer for your C, you can just say that there is a task. If you are sick with update and somebody will eventually triage that and maybe even implement that. So, if you see some significant issues you're not ready to work on. Please submit tickets on the top wishes. If you see something which you can just fix the minute like a type of fix, then he said to submit this request. It takes, takes less than one minute but it's available contribution. So just, yeah, just do that. Any questions comments. I haven't put the recording of the previous meeting here, but usually what I do, I put the recording things right inside the agenda notes. You always find that the recording, they will also publish recording for this meeting. Anything else for today. We don't just thanks everyone. So we usually keep these meetings open until there are any questions. And if there are no questions that you just closed down. If nobody joins the meeting usually I leave for the meeting at the top of the after 10 minutes. You are always welcome to follow up in the chat if needed. And again, please don't keep the meetings. Now we have slug channel in this day of workspace, we also have guitar channel. So any of these channels is totally legit and feel free to ask any questions there at any moment when you need assistance, and somebody will be around to help. We have something like three or 400 participants in the guitar channel for JSOC and some of them help. Thanks to them. If nothing else, I guess, yeah, thanks everyone. Thank you. Thank you. Thank you. See you at the next meeting, Kristen. Yeah, thanks.