 Hello. Welcome to Google Summer of Code Office Hours in the Jenkins Project. Today is December 2nd. We have several contributors and students on the call, and we have a short agenda for today. So let's just go through that. Again, we are in preparation stage. Google Summer of Code applications open in January for organizations, or even in February of this year. So we have plenty of time to prepare, but we still do office hours so that students can ask questions of our organization, and at the same time we can prepare project ideas and application in advance. One thing I wanted to discuss before we go to Koneir with the students is actually a team, because in order to run JSOC, you need multiple people as awkward memes etc. I thought a bit about this year and I decided that I wanted to keep doing awkward meme work in Google Summer of Code. I'm not ready to do it alone, so I'm looking for more participants. So Kara was in last year. Kara, do you want to continue? Yes, I would be very happy to be an org admin for Google Summer of Code. Okay, and Mark, if you recall correctly, you prefer to stay a mentor at the moment. I would like to stay a mentor. If it turns out that we don't have enough org admin depth, I could consider it, but for right now I would like to just mentor if I can. Yeah, that's perfectly fine. So anyway, Mark, you likely spent those are good meme, you had chat but it's to be seen. Martin, he has already sent a message that he would prefer to step down this year. So he will be able to help a bit here and there, but not in the official capacity of our company. So we have up to five, we can have up to five for the application. So definitely we have quite a number of slots and if somebody wants to join, but you need this. Okay, so another open question we have is collaboration is continuous delivery foundation because last year we had two organizations. One is Jenkins organization which hosted Jenkins and Jenkins X projects. And another is continuous delivery foundation which hosted the projects for the rest of the continuous delivery foundation. So for this year we have an open question of whether we want to price it as before as to organizations or whether we want to join our center just have one organization. We discussed it briefly at the previous focus and I appreciate it. And the agreement was that Jacqueline and Tara, they will schedule a separate meeting. And this meeting, we will just try to align how you do that. So there are all those advantages in having one organization. There are also concerns like, for example, how we distribute a project slots, etc. And it needs to be discussed. But I believe that the meeting is in mid December and it has been all of the schedule. So what it means for students that if you do not see the Jenkins organization next year, it doesn't mean that we don't participate. We might just participate in the umbrella of continuous delivery foundation, which is a current parent organization for the Jenkins project. But yeah, basically it remains the same for us so project ideas and information, our website remains totally relevant even if you participate in the umbrella of CDF. Will, could I as an org admin be having an invite to the meeting with the CDF in December in mid December. I will invite all of our car means. Thank you. I want to discuss that. Okay, other related topics that we also need more mentors. So for mentors usually start call for mentors in December. It's about time. My plans to do it once I finish the elections work and the Jenkins elections are finishing tomorrow. So after that, I will start working contributors to find more project ideas and mentors. Yeah, I think that our target for this year is to have approximately 15 project ideas. Let's see, maybe 20 or so. But yeah it's to be seen because this year GSOC will be different in terms of organization. We have already had some discussions with mentors. Some of them you're concerned about having smaller scope projects. Other cities, an opportunity. Let's see. When you said this year would have a different organization is that in terms of how the Jenkins project is handling the organization or is that a difference in organization on the part of Google summer of code. You mean for collaboration with CDF. Oh, if we collaborate with the CDF. Okay. No, I think you were asking a different question based on I think you were asking all legs based on all legs comment about differences in GSOC projects. And they've changed the structure of Google summer of code significantly. Oh, like maybe you could summarize that. Yeah, we had a quick discussion. I'll show it. And by the way, for students who are on the call, these students on mute and ask any questions. So it's office hours and everybody can interrupt the discussion at any moment. So we can discuss it. So, if you take a look at the timeline, you can see that you have the patients opening in late January is the blind February so it's later than usual. And actually, everything is later than usual except the final date because coding phases are shorter. So they will be only two coding phases is one evaluation of the middle. It's approximately how GSOC was organized in 2016, but coding phases are so smaller. And there are some clarifications why they want to make this change but basically to give all organizations and students offering them in terms of how they spend time because GSOC is historically quite time intense initiative. And yeah, this year it was difficult for all parties. And GSOC 2021 is expected to be a bit more relaxed. But still it's Google summer of course, so they will be able to work together. So timing. Yes, May 17 is a set of project. May 17 is coding. So there are almost three weeks of community bonding instead of one month. And then the first coding phase, the second coding phase. So they also approximately one month. So, yeah, that's the only significant change in the process that also changes in the eligibility for students, because they made adjustments and students who've been able to participate in the previous year. But they could participate this year, even if they wouldn't be eligible according to common goals. So basically if you graduated in 2020, you are still eligible to participate in Google summer of course. There are more detailed clarifications about how it's organized on the GSOC website. So this refer to GSOC website for the official information. But there are also changes in the eligibility. Does it answer your question? Yeah, it's great. Thank you. Any other questions before we move on to other topics? Okay. So, yeah, still we need to send call for mentors. I mean, at least things are quite slow right now, but it's rather better to do it now than in one month when you have Christmas break. It's just an interesting time. One question to you about Jenkins X. I would leave that as an open question for now. I probably need to speak to the James's about it. My main concern with that would be mentoring capacity. So I, yeah, I'll put a feeler out into the Jenkins X community and discuss that further with the James's. I am not sure. So we'll leave that open for now. Yeah, let's see. Anyway, taking the timeline, we would need to have answer. Well, preferably before March, so that when students start exploring to their separate organizations, we have some details about Jenkins X. Okay. And so from my understanding of your question, then, from the point of view of the Jenkins project, as with last year, if need be, we would be very happy to have Jenkins X within the Jenkins or umbrella again, or within the CDF or umbrella, depending on which way we go there. Is that, is that a good understanding? Okay. So then it's an open question, and I'll ask the James's. Okay. Yeah, so, even if not Jenkins, so CDF for sure. So basically, it for it also falls into this question, how we organize. Yeah. But yeah, Jenkins X is definitely welcome to join one of these organizations, depending on how we agree. Okay, great. Okay. So that's it from organizational part for me. So, we can proceed with Kony with students. And if you have time, we can discuss Mark's project ideas. I guess, yeah, both me, Mark and Kara, we have to drop in approximately 15 minutes. Yeah. So let's start this Kony. You know, like, so this time Jesus has also changed. And the last time I tried to participate, but I was not able to clear. But this time, even the smart poets are also allowed and having plenty of time to prepare. So I want to get some clear idea, like, because we are not, this person, we have not been an organization, right? So now we are in this place. So that can you help us in for a newbie? Because to start with Jenkins like small, small changes or small, small. So there's some tasks, which can, which on, on which we can work so that we will get some idea about it. Because even the small parts are also allowed. We can get. We're having enough time to prepare for all the things. Yeah. Yeah, we had a long discussion about it at the last meeting. So you can just refer to the recording. Yeah, I will show some examples. So, yeah, as in the previous year, our project ideas, once which are published, they include references to some. They provide getting started guidelines. And since you participated in the previous year, basically these are the same guidelines as before we still need to refactor them. But yeah, there are new different issues you could take a look at. There are some quick start guidelines you can start from. And in addition to that, you can also just explore Jenkins explore errors using existing guidelines like getting started with Jenkins. Also, there are contributing guidelines for drinks participate. So you can go here and you can find some references to new come offering tasks by explorer, for example, Google somewhere of course is about code. And here. So you can use for new commerce, for example, maybe a friendly issues, good first issues on the top, etc. So you can just take one of these big worries and there will be some issues you could start from. That's great. I will start. And if I have any issues, I will be contacting you. Yeah, it will be good if I can make some progress or some comments on what the new family. We recommend it, but again the goal is to explore the project. So there is no objective to fix as many issues as you can before the application phase, because whatever you do, the goal is to prepare your proposal. But for getting the project so we can't make ourselves some ideas right because we have not but specifically on this domain right. So if you can provide some ideas or some small project ideas on which we can work and explore specifically. So that would be great. As a student perspective, you have not done hands-on on Jenkins, right? Last year when I have run the Jenkins and I have seen how the exported annotation is working and how the rest of the way is working. So I've seen that, but the remaining like all the functionality of Jenkins we have not explored. So that's why you understood my point of view, right? Yeah. So yeah, again, in particular ideas where to get started. Again, you can refer to project ideas. So for example, automatic specification generator. The best starting point would be to create specifications for a few plugins and to actually see how it works. This was my last year project proposal. Yeah, it's still an opportunity to do that. Or for example, if you talk about a plugin installation manager. So what you can do, there is a plugin installation manager repository. If you go here, there are some open issues. Actually, we ran out of good first issues but there is still one left and we can definitely create more. If you need to explore it, the best way would be to actually to use the tool to see how it works, maybe to do some improvements. For example, in documentation based on your experience to create some tests because any company needs more tests. And if you see some patches, which you would like to do, you're also more than welcome. So for this project, you can just start using it to go through guidelines and try to improve something. Last project idea we have published at the moment, the Jenkins remote and monitoring. So there if you want to start my recommendation will be to start from Prometheus and Kubernetes. We have a Google Season of Doc project this year and this project targets creating a new documentation for Kubernetes and some documentation has been already published. So you can go through this documentation and just set up Jenkins and Kubernetes and then configure Prometheus to monitor it. And it will provide you some insights about how the systems work. And also that you can explore what would be good to monitor on the agent communication side. Because many things can be done using these plugins. But you can just see what else could be improved. Does it make sense. So to further support Oleg's Oleg suggestions. We had good success last year with the get plug in the students that were considering applying took one of their tasks as right more tests for the get plugin. We had a, we had actually a transformation story that we were a ticket that we were working on so writing tests for whatever target is a good thing. Yep. So yeah, I'll put some notes there later but again, you can just see the previous meeting. Okay. Any additional questions from other students. Mark, you wanted to discuss project ideas. Maybe you would like to summarize what you have in mind. Yeah, so I've got, I've got five different ideas that are on my mind right now. Top priority one is use get credentials in a pipeline task for the with credentials step. We have a lot of people to use the get command from an SH step or a bat or a power shell, and still do it with credentials. It's a way to allow a much richer set of actions inside pipeline get related without requiring that we do implement those all of those in code. There's a number three and the most requested features so it's it's very, very popular right now embarrassingly popular it's so so much interest in the community wants that fix that change. Yeah, I was just, I just started talking about solutions, because the potentials binding plugin I was just wondering why it's not enough. And that's the one and I think it, as I've been detailing it. I think I've detected that credentials binding is exactly the way to do it. And, and we just need to refine and adapt it slightly to do to do it so it looks very very probable that it would be done using a credentials binding plugin technique. Okay. But the challenge there was I guess, well, let me go through the topics first really quickly and then then we can guide. The next was add pipeline symbols to the get plugin. And the benefit there is users will get a much simpler presentation of their pipeline as they're editing it as they're looking at it instead of these big long class references they get nice simple keywords. And third third is use clover open clover a coverage tool to reduce test time by optimizing test selection. This is completely independent of the get plugin but it's using something that open clover offers as a way to use diffs to decide which test to run which to not. The fourth is get sub module improvements. And the fifth is get LFS improvements. And my thinking is the top two are the most interesting to me and I'll do more detailing on them. The, the third is an almost a research project it's not really it's not been proven that would even work. And therefore I'm not sure it fits well with Google summer of code. Is it okay to do research style projects in Google summer of code or advised against for pipeline symbols. The use open clover thing. Well, research projects make sense. If there is a clear goal. Okay. Yeah, the research project may mean that there are some uncertainties, but still the main focus is creating content solutions. It wouldn't be a research project as let's explore the area and summarize the results would be rather let's create a prototype of a particular idea. Well, it's still a research part to some extent but the goal should be still to produce actual code and the news something can be delivered to Jenkins users so developers. Okay, so that's good guidance that means I think what I'm going to do is likely work on the top three most focus on number one, because it's detailing is is crucial. I'll put some focus on item two and just a little on three accepting that the project idea review process may reject it as insufficient information. Thank you. Thank you. That was that was the kind of guidance I was seeking. Yeah, for second issue. My, well, it's just a hunch but my impression that it's rather a bunch of small tasks. It's unlikely to be a full fledged GSOC project. And my problem with not making it a GSOC project is all my attempts to test it have proven that it's not as small as I hoped it was. Okay. But it's it's much more heavy test focused than it is writing code focused right so it's maybe a bad choice just because there's not enough code to write, as there is a whole lot of testing that has to be done automated and interactive. Yep. In our cases code as well, but still. Anyway, it's a good approximation. And we should keep talking about these project ideas and will also prepare my list for the next week. I don't mind. Thank you for the honor and other things. But yeah, not ready to come up with a particular project description. Okay, so, yes, we discussed in the beginning. It should be rather short. So, if there are any questions I could answer them briefly and your marker, you could probably drop and I will join you as soon as I can. Yeah. Sorry about that. Just company meeting. Yeah. Question to all students. Do you need any additional clarification on details. You will play to discuss now. Look, can you repeat the question once. So do you have any additional questions or do you need additional information for now. Nothing for myself. Nothing from me as well. Okay. So then we can just think about synchronously. So if you have any questions just ask in the chat. And next week we will have other office hours sessions where you can discuss more details. Thank you. See you next week. Thank you. Bye.