 Okay, we have been recorded. So hi everyone, today is March 4th. So we have a regular Google code office hours and yeah, my introduction was almost the same as before. So quite regular. And yeah, today we will discuss few topics. Most of you will run the common agenda. We will discuss what's happening around GSOC, discuss open action items, project ideas status and then we have questions and answers. Today we don't have all our communes on the call. So Marky and I cannot join. I believe that Carter cannot join as well because she attends one of our Google community events. Marky and I guess is busy as well. So we just have me on the call and we also have several mentors and students. Okay, let's proceed with news. So not everybody is involved in the discussion but is my screen visible? Okay, so last week we had a discussion about the Jenkins and Continuous Delivery Foundation because there will be two organizations which reference Jenkins as project. So we are going to have a meeting tomorrow with CDF to discuss it and to address. The problem, so if you will have been here and could understand the location of the outreach slow start, so we believe it's by PM UTC now. So there is an effort from someone. Oh, I see, I saw that it's normal, but. What is, I'll mute you. Okay, so yeah, if you want to participate, there is a location outreach page and here there is a link to meetings. But it's mostly for all companies, but interest mentors also welcome to participate, especially if you're interested in interoperability in other projects because there will be projects for all the CDF members like Tipton, Spinnaker, maybe Screwdriver, maybe there will be some interoperability projects including Jenkins, let's see. The meeting is open. Another thing which was mentioning that we started doing Condemn Project Syncups. So last week we had at least three Syncups, one for customer Jenkins Goal Service project ID, another one for electronic design automation, there was also Syncup for machine learning and if you as a student need to get more information, please ask your mentors to schedule such a Syncup. As we discussed last time, it's on demand. So we do not schedule them by default, but if it helps, we can do that. Okay, let's go next, new mentor introduction. Do we have any new mentors on the call? I guess not. Mike, did you introduce yourself last time? Maybe, and this last meeting so maybe not. Okay, so maybe not. So if you could introduce yourself briefly, it would be appreciated. My name is Mike Cerioli, I work at CloudBees. This is the first time I've participated in Google Summer Code, doing software development and design for most of my life. And I'm looking forward to you, I enjoy mentoring people and so I'm really looking forward to participating and mentoring. I tried to do it last year and I just didn't have the time. So this year I've made it a priority. You can find me on GitHub, Mike Cerioli, and get her the same ID. Thank you. Yeah, Mike contributes a lot to Jenkins Projects now. For example, I'm in the Schecter mission subject, which was launched just a couple of weeks ago. If we're very near projects with the Jenkins Covarrant Security, Mike could provide a lot of expertise today. Okay, let's move on. Open Action Items. So last week we had a discussion about how we could promote Google Summer of Code. And again, like we discussed last time, another section item for everyone, promote Google Summer of Code. So whether it's Jenkins Google Summer of Code or just Google Summer of Code in general, please do that because we need to gain visibility. And again, we also depend on mentors because as Oracle means, we have limited capacity. We also already have some parallel discussions, like funding, payments, also some cases we handle in the background, which are not visible by the team. So any promotion you could do would be much appreciated. On the side of specific topics we discussed, I have an action item to publish a blog post. It's a bit overdue, but I hope to get it to you. And there is also a German throne on Jenkins I.O., which I would like to publish. So since we have Mark, wait on the call today. Mark, what do you think about putting a German on there? So similar to other topics we have. I like that a lot. I think we should, absolutely. Yeah, so the German throne would mostly target students and mentors. Now it's much false. So we don't actively seek project ideas right now. We would still accept project ideas. They're prepared and submitted, but we mostly seek students and mentors if possible. So are you envisioning Oleg that we would do two pages on the German throne, one for mentors and one for students? I think it would be a single page. Yeah, it would be a single page. Okay. Well, it's an overkill. And yeah, I'll finally kill that one because yeah, I added a temporary image and well, nothing more permanent is temporary. So it's time to remove it. And yeah, speaking of that, if you have something to put on the German throne, please do so because yeah, right now it's a bit obsolete. So, okay. And regarding the rest, mainly please, we did announce one thing. In all my meetings, we've got some follow-ups, but again, raised visibility is rather subject for project meetings, et cetera. So if you participate in regular Jenkins meetings, please do that. And then that's all. So there are also things like going to new universities, local JSOC communities, if you have ones, but it depends on your capacity and your interest. Yeah, one topic about that is about online meetup. So would they really like to do one? For example, in a week, Matthew, I'm muted. I have a proposed meetup for next Wednesday to talk to the developer team, to developers about spot bugs and fine sec bugs. Would be happy to host an additional JSOC meetup. Just would like to avoid colliding with that when it hasn't been published officially yet, but I'd like to get it published today after the review is done. Okay, that's fine. So yeah, let's continue it on the time, but we can do it on Thursday or Friday next week then. But yeah, basically it's simple. That may be with some slide bags. Let's see. Okay, that is a lot of minor things. But yeah, let's just go to project ideas. So our project ideas, they're basically the same status as before. We still have a bunch of projects in the draft state. I have an action item to move some of them. For example, automatic specification, I'm an engineer and pipeline-stabilization generator. I started writing quick start guidelines. This is a topic which blocks them, but I haven't finished a bit. So I'll try to do it tomorrow. Code coverage, API, and Jenkins remote yet to be seen. Yeah, I hope to get it over the line. And the last one is Jenkins pipeline is YAML. My understanding of the current developer, is that it's going to stay in the draft. So there is a second reviewer item who actually works on the project. So we need to do some alignment there. So it's definitely not going to the accepted state right now, but it shouldn't block anyone who is interested in this area from applying and from reviewing that because yeah, there is a quite a developer million piece. Okay. So yeah, there is some from somebody, okay. Yeah, let's see if it's project ideas. And I think we can just move to questions and answers. And if there is not so many questions, we can just call to the meeting caller. Okay, any questions? Yeah, with respect to the GitHub checks API, I guess, I guess I wanted some sort of, could we have some sort of a project mentor sync up? I guess that would be cool for the GitHub checks API. I guess I put in the developer mailing list and I guess one more student was interested. I mean, he was contributing the GitHub API. So yeah, if we could have a sync up for that, that would be amazing. Okay. So since I'm not potential mentor, I will just take the section item. Okay. Thanks. So I guess I have a question to launch that is not so much a question. I'm gonna be gone for the next four days on business travel. If there are questions related to Git plugin project ideas, I would welcome feedback from others or help from others while I'm traveling. It's not me asking for asking a question per say, just noting that I'm unavailable somewhat for the next four or five days for business travel. That's perfectly fine. And we hope you will be able to promote you so you can travel. I'm having a question. The question is about the organization specification agenda. What is to be on? So there is like a different app to write when you need to confirm products. I have difficulties understanding. Could you please write your question? So that you have a question. It is in draft credits, right? Projects is in draft, right? draft credit ideas. Hello? Nandish, while your audio quality is quite poor, all they get suggested you should type your question so that we can all hear it. Yes, I will. I'll read it. I'll type the question. Just in the chat. So we're in Zoom and there is a chat where you can write your question and you will be able to answer that. We'll not keep traveling until Wednesday, right? So I'll, I travel, I fly home late Sunday night and I'll be then offline or probably available Monday and Tuesday of next week. So I'll be traveling through, I'll be available again the night. Yes. What was the question? So the question, Nandish, is about automation specification generator is in draft, right? Will the project continue and present the work number? Oh, like I can't hear. So your question is whether automatic specification generator project is going to continue. So the answer is yes. It will continue. So the only reason why it's in the draft state is because I haven't finished the quick start data on this yet. Okay. So it's a minor thing, but the overall description is good. And yeah, since we discussed it a lot in the chat, I believe that you have enough information for quick start. Okay, but okay, Oleg, I'm right now working on that. I'm having those small doubts on that. The doubts are like, so I have gone through the, some of the APIs provided in the links in the docs chat. So I have found the how to go through the links and how to go through the code and how to get the annotations. In Java, there is an option in reflection that getting annotated class of specific type. Like if we give cost type or get type, we'll get annotated class exactly or the method specifically. So I can parse it. Is this the correct way to do that? Well, in Jenkins, we usually use another library called sysposs. So JC is one of active Jenkins code reviewer. Yeah, there is an annotation processor, which we widely use inside of the Jenkins code. So if you need to process annotations, if you want to fetch them, it would be the best project to look at. It's embedded into the Jenkins core, so it's available to all for you inside of the box. So what this will plug in, but what this will exactly do, means it will fetch the API calls? No, it won't. It can fetch annotations, et cetera. Okay, okay. Everything is automated already, right? Kind of. Yeah, for annotations, yes. Okay, it means I have got some reflection of Java. So in that I got a method like get annotated type call, from which we can specify post.class. Well, you can try that. The problem is the approach that, if you use row Java reflection API, you won't get cache and other things. So sysposs improves performance significantly for such common operations because it was designed for Jenkins use cases. So my recommendation is to use that or just to consider using that. Yes, yes, I don't know about this, right? So I'm asking, so I will continue on this and I will read this code and I will understand. And one more thing is like about the proposal thing. Should we plan the sessions of the eight weeks or will you plan for the work? What do you think? Well, we could definitely organize one. So I'm not sure, Kristina, would you have some availability like this week or maybe next week? Yeah, I do. So maybe Kristina, if you could send a, either you develop a mailing list, discussion about this project. Okay, I can do that. So yeah, if you could start the discussion. Sure. Yeah, I will do my best to attend, okay? Okay. I have a question for the mentors. Yes. So if I want to show prototype code in a proposal, what would be the best way? Would it be through a PR pull request or screenshots for that code? Pull requests button. Okay. So yeah, you operate in the Jenkins community. If you want to show a prototype, you can do that. GitHub, there is a feature draft pull request. So if you want to submit a proof of concept or whatever, which you didn't consider ready for review, you can submit it as a draft pull request. I'm not sure what I'm doing, but yeah. I'm even less sure what I'm doing, but there will be definitely a draft pull request button. draft pull request option. Okay, I'll try that. Okay, thank you. So if you write code, don't spend time on converting it to other format. It's fine. Applications are for us and we can review the link. Okay. We'll try to close it for now. So any other questions? If not, I have a question to you. So I raised the question in the GitHub chat about having office hours in the Asian and Pacific region. So something like eight or nine AMVTC. My question to participants is whether you would find it useful and whether you would be interested to attend these sessions. Because yeah, sometimes it's more convenient for people to attend on the evening of the study, but if you want to have something earlier during the day, I'm ready to do that, but I need to know that there will be people participating. Would anyone be interested? Probably not me. Everyone, I think for me it's irrelevant. I'm mostly in Europe or in Moscow. So maybe other guys. Okay. So yeah, just for your information, I keep this option open. I will probably send it to the GSoc mailing list. But yeah, we will organize these meetings only if there is somebody interested. I can participate, but I don't think I have any questions specific for that. Bring to that. Yeah, we can use at this time to discuss project ideas and project application drafts. So if it helps. Yeah, I can participate as well. Yes. So, okay, let's fill up in the mailing list. There are more people who are interested. We will do that. I guess there will be not so many mentors on that call, but we can still discuss project ideas as we know about. Okay. Anything else for today? Yes. Hello, Alek and everybody. I have a small question. I just noticed that there is a student who can take ownership of the YAML project. And yeah, from the previous year, I slightly take a site project on this topic. So the question is, will it be possible to like make something collaborative or, so it will be not fully aligned with the project ideas. Maybe it will be the new topic which I will propose with further investigation, of course. What do you think about this? Yeah, so project ideas are just project ideas. Potentially we can have two projects, three projects or more projects for project idea. It really depends on what is the content. So in Google Summer of Code, we expect each student to work on a more or less independent project. What it means is that each project can be evaluated separately and it can be delivered separately. So if you collaborate with another student, it's fine and we encourage you that because that's how open source work works. But at the same time, you need to ensure that the project idea is independent enough. And since you know about other students applying to the best way is to just sync up and to discuss potential areas so that you keep your project separate. And it's a fine approach and this is one of the reasons why we recommend for project discussions to have in Pagodal because we had such cases before. Wow, thank you. Thank you Oleg, it's a good idea. We will discuss this issue with that student. I will contact them as soon as possible. Thank you very much. Okay, thank you too for bringing it up. So I just made some notes. Okay, anything else today? No, so you've got something like 15 minutes of your life back from this meeting. Thanks everyone and looking forward to meet you next week or maybe at one of these project discussions. And again, if you want to discuss your projects specifically, please raise a question because yeah, that's how it works. Please ask your mentors and do hesitate to ask in the chat if you discover any obstacles or have any ideas, it's perfectly fine. Okay, thanks everyone. Thanks all, bye. Thank you. Thank you.