 All right, allow us to share and then, okay, can you guys see my screen. Okay, great. All right, hi everybody so welcome to Jenkins GSOP 2022 office hours so today is April 15. So, pretty much we're going to leave it open to, you know, the rush since you're here. Ask us questions. So, it's pretty much open for questions. Yes, sure. Thank you. So, I wanted to know like basically check if Jenkins is able to see my proposal that I've uploaded via GSOP registration. Yes, I believe we have your, your proposal submitted. Yeah. Awesome. That's the most important thing I wanted to make sure. So, other than that, I was requested for review and I got the review. So, that's a good thing because I got coming from Jake and he says to that he has reviewed the proposal so it's pretty much it. If there's any other reviews that can happen that also would be helpful to make changes to resume and make it more better. Okay, so I know that I'd reached out to the mentors for your proposal draft and they have given me like the thumbs up okay yes I will give it a review so that was done. I think it was like two days ago so hopefully you know what you get now it's what you get. Probably don't, you know, you probably won't get any more reviews from here on out. So you'll get one more review because there's one person riddled with shame who is attending the meeting today, because I haven't done my reviews yet and I will do my reviews but. I will, I will yet I apologize for the late, late nature of them I'll do my best to get them to you. It's, it's a little complicated with with the things that I need to be doing elsewhere, I'll do my best and I will get them to you. Please don't apologize I understand you have a lot of things going on at the commitment as well so it's also fine if you are not able to do it because review windows already been passed so even I am late so no problem at all. And now I did have an open question that I've seen dirage specifically related to you that that I was watching in the org GSOC org, org admins list, as they were discussing back and forth about what the what the rules are with what the rules are to have, have you have experience with open source projects, and, and I'm still not entirely clear and so I think it's it's going to have to take some thinking and pondering because one of the, one of the rules in the GSOC things is you need to be open source but then they allow several different ways of being new. And as far as I know you haven't done any significant code contributions your contributions to the Jenkins project up to this point have been in documentation and blog posts and things like that. Exactly, I totally agree. So if I think about my contributions, what things comes to mind are change logs and documentation related contribution and the only the significant I would say contribution I did related to code to Jenkins was last year when I was applying for custom distribution build service project, and even that code was related to react jazz so it was not like very specific to Jenkins core, or any plugin changes that I did. So, that's what I see when I look back. Excellent. So I think, I think that gives reasonable justification that, that you are new to open source, particularly for code contribution. Great. Thanks. Now Alyssa and Chris are the org admins along with john mark so they'll, they'll have ultimate decision authority there but I think that makes sense to me. Yeah, that sounds good. Okay, great. Yes, so I was also wondering like, since we have time so can you explain like, if a person gets elected, then how would they utilize the time of community bonding. I read the documentation on the stock as well so I just wanted to know what we think about it. Yeah, so past community bonding experiences have been configure the environment be sure you're ready to do development be sure you can run the run the code that you're that you're using as your basis locally. Be sure that you've got a working debugger or working compile environment that you can run tests there that you've got a working Jenkins environment that you understand how to deal with pull requests how to submit them how to interact with the mentors set up the schedules for interaction. Those kind of things were typical for, for my experience during community bonding. Chris. Now you've got the benefit of having been an actual on the other side participant to basically a student. Maybe you've got a different view of what worked well for you and in community bonding. Basically I said having up and then I could start early if I wanted to. That's what I did. So you set everything up prior to the bonding Chris I'm assuming during the bonding period or during the bonding gotcha. Yeah. Yeah, so and, and that matches with what I saw in the two years that I've mentored is the, the new contributor was already getting started, working through things like okay what are the what are the phases look like and what are the most high risk things. Let's explore those can I get something going here, and community bond makes a great time to do that because it lets us practice review processes and practice coding discussions practice those kind of things before the project itself starts. Yes, that makes sense. Other than that, I think I do not have any significant questions for now. I just only had a few questions I asked that's all. Okay. Great, so I guess we can call it a day and we have more questions feel free to put it in together. Okay, DeRosh. Yeah sure thing. Thank you. Thank you. Thanks Chris. Enjoy your weekend. Thank you. You too. Bye bye.