 Hello, good morning, good afternoon, good evening, everybody. Welcome to this Jenkins Google Summer of Code office hour. So currently on the call we have Chris, Org Admin and the mentor and myself, Jean-Marc Mason, Org Admin and mentor and we're waiting for people to join to answer any questions. Okay, I see nurse. Somebody else joined on the document. Okay, he's going to post a link on the channel. Chris, oh there, okay. Hello, hi everyone. Good afternoon, Dirage. Yes, I'm going to follow you. Well, not too bad, not too bad. Nice to have you, we have you here. Okay, then I will start. I have a first point on the agenda. It's not next week. I have a doubt now. Oh no, there is one of the office hours that I will not be able to manage next week. This is the office hour on the 21st of April. So in two weeks, I will be in Paris where I'm giving a talk in a conference there. So I will not be, and it's about the time where I'll be talking. It's not twice. So I will see if we can organize it. Somebody will, I will first see with Marc if he can handle the call and the recording. Otherwise, Chris, are you available in two weeks and we see how we do the recording? I think I am, but I like, yeah, I think I can do it. Okay, so it may be that if Marc is busy, he comes in, starts the meeting, and then Marc's you as a host and gets you started, and then you can drive. So you need to get that organized. Okay, that's the first point. I see a first question from Dirache. Do I read a question or do you want to explain it or are you still writing it? Yeah, I think that's it. So it's about can we choose not to receive the GSOX stipend, just sort of curiosity. The context here is that since we have, like, if a person has an employment in a company, they cannot, there are some rules like they cannot have another source of income. So I was wondering, like, can we refrain from getting stipend here and just make it like purely open source kind of contribution? Well, not receiving money is probably always an option, but I prefer to check. Chris, do you have maybe informations? Yeah, I think I remember it used to be, like, you can choose not to receive stipend, if you want. Yeah. Yeah. And maybe another option is to donate it to the Jenkins community, so that we can use that money then for sponsoring other activities. I will raise that point during the advocacy and outreach meeting. But you're not stuck and don't put yourself into problems. Sure. So I think then I would need to plan it from my end force. I was just trying to understand, like, do we have an official channel for this? So if it's an option, then I would need to talk with my employer and try to see whether, how their situation and then accordingly decide. Okay. Good. Here, I'm going to talk to the Google Summer Code organization and I'm going to talk with Mark who has more experience with that. And we can then eventually come back to that subject later. We're still in the selection period. So I asked this right now. You're on mute. You're muted. You're muted, Drash. Oh, sorry. Sorry. So I asked this question just wanted to be sure, like, what's the process, even though obviously it's a selection process, I'm not, just wanted to be clear. That's all. Yeah. But normally it should be allowed. I don't know about your employer. I don't see a reason. The only person that could not be happy with that is the tax collector. You might run into tax issues. I don't know how you declare it or how you do it. I don't know. Probably different from one country to the other. And even I don't know. But I ask your employer, ask what is there. They maybe have advice for you there. And I'm going to listen. And maybe we can reach out to previous years contributors that were from India. They maybe worked it out. I don't know. Yes. So another reason for asking this right now, even before the selection process was not to, like, if there's any problem ahead, I just wanted to avoid any problems. So just wanted to be clear so that your time is also not wasted moving forward. That's why. Yeah. Well, I appreciate raising, but the probability that this will give you a problem that would prevent you from participating is very, very low. So we'll find a solution for that. That's good to know. You're feeling good with your proposal? So far, yes. I'm actually enjoying writing the proposal. And I'm looking forward to the today's session as well, because I do have some questions. And when they get answered, I would be in a better position to, you know, combine the final draft. Yeah. Okay. Good. But we're making good progress there. I like it. Good. Are there other topics? Otherwise? I don't have any other questions for the only one. For the people that are listening in, so we are currently, so registration on the Google Summer of Code site is open. So you can submit your proposal as a PDF. I've already seen a couple of proposals. We wait until the closure of the submission period, which ends April 19. And then the mentor community from Jenkins will review the proposals. And we are going to first request a certain number of slots based on the proposal and the mentor capacity we have. Say, and ask Google, okay, we would like to have that many slots. And these are the candidates that we would like to propose. And then Google is going to acknowledge that and approve. And then the candidates will be announced. And then we start the second phase of Google Summer of Code. But this will come back. So we're now in the last run for contributors finishing the proposals on time for the 19th. And then you will all be able to breathe, rest, finish the exams if you're still at school and prepare for the next step. Durage, I see you were not able to log in, register on the Google Summer of Code site. Yes, I'm not sure why. Even other participants had that issue, but I think for them it got resolved. But for me, when I click on login and choose my Google account to authenticate myself, it says one minute please and it shows a loading screen and then nothing happens. So no login. Yeah, it is important. We need to get that going. So open a support ticket. There is an option. I know that Christine, as a mentor, had also issues to log in and the support from Google had to look into that. So open a ticket on time for Google to sort it out. It would be really, really a pity to miss the deadline because you could not log in. So about that ticket, do I find its link on the Summer of Code with Google website? I think so. Okay, so I'll do the research. Do the research. If you get stuck, call for help and say here I'm stuck. Normally you should be concentrating on finishing your proposal and not sorting out these login issues. Yes, maybe the other participants who had that issue earlier might be able to help me. Yeah. So I'll post a question later on Gitter. Yeah, do that and if they solve it, yeah, do that. We're good to know. And Drash, maybe once you get it sorted, maybe upload already an initial version of your document so that we see that, okay, you're in and this is sorted. So I think we have now five proposals registered. Chris? Yeah, I just posted a link on the chat because they have a help section. Have some links being used. Thanks, Chris. Yeah, I'll go through it right now and I'll reach out to them. Yes, thanks a lot. Okay, good. So no more questions from my side. Yes, that was all. Then we can close the call and have a cup of coffee or tea before the brainstorm in 15 minutes. Chris, is that okay for you? Yeah, sure. Okay, so thanks for joining. Good luck in finishing your submissions and talk to you later then. Bye-bye, everybody. Yes, thank you. Bye-bye.