 So, it started so good night, good evening, good afternoon, good morning, good very early morning to everybody around the world. This is the special Google Summer of Code office hours, just after the announcement of the results yesterday. It was late for many of you in India, but a lot of people were online to wait very excitingly on the results. Some were happy, others were less happy, and these are the kind of things I'd like to discuss today. And for that, I'm going to share my screen. I have a single screen here, so I will, from now on, have difficulties to bring in correctly. Oh, something went here. Bear with me, I need to open my slides. The slide deck was closed. Apologize for this. But here we are. Alyssa or Bruno, do you see my full screen? I can see it. Okay, great. So, I'm a little bit driving blind, so I have a hard time to see the chat or to see head movements or whatever. So, I'm counting on Chris Bruno and Alyssa to give me signals if there is something important. You got it. Okay, the first thing. I stole this slide from Alyssa because I like it very much. Some general information about questions and answers and a quick reminder to the code of conduct. This is the link we have, and I love this picture. So we're here to congratulate the contributors that were selected for Google Summer of Code 2023 and to discuss how we move ahead. So the people that were in the projects that were selected, we have the GitLab plug-in modernization with the harsh. We have adding probes to plug-in health score with Chakruti. We have building Jenkins IO with alternative tools with Bandit. And we have Docker-based Jenkins quick start examples with Ashutosh. So congratulations to all. Happy for you. Now the adventure starts. So if you remember the analogy I used with rock climbing, now we reached the Everest base camp. Now there are not four contributors there on the rock. We have five, but let's say it's four. Four made the long track to reach the base camp. We learned a lot. If you look back of what you now know and what has been achieved and the knowledge that you acquired, everybody had a great journey to reach this point. Now four people are going to continue the track and start the assails on the summit. We are now starting with those four persons and the mentor teams. We're now starting the bonding period. That means that we're going to plan what we're going to do, how we're going to do it. And yesterday evening after the announcement already sent some ideas, guidelines or recommendations on how to move on with the bonding period. We're going to let you breathe a little bit because there's a lot of excitement for that. Just a note for Jakruti. What's his name again? I'm getting old. Adrian is currently on holiday. I couldn't join the meeting so it might take a couple of days, but Jake will organize things and I will look up that we don't lose too much time in the preparation. But there's a bonding, this is what is for the people selected. Now I want to address mostly to the people that were not selected. The choice was not easy at all. So we had 62 proposals and 13 proposals made it into the shortlist where they were really very strong and we had to choose them. And we picked up four projects and ranked them saying these are the projects that we can do and support and we hope that we get them funded. We were lucky because the normal number of projects per organization is three and the majority is three. We got one more, so we got all the projects we asked for and that we were able to do. So we were lucky. I want to remind everybody that our ranking choice was based first of all on the proposals quality and I must say besides some junk proposals. People never attended, never tried and I want to emphasize here that all the projects that were or the proposals that were in the shortlist had drafts published and reviewed. So this confirms that this is a key for success. We had also to take into account the lead and co-mentors and to set up a teams as said we were short in mentors and some mentors had to hook off and this is something I'm a little bit sad on but it played an important role on our capacity. And then we also put into the equation before shaking everything very strongly and make a decision the importance of the project for the Jenkins project. Project messages, it's not a judgment on your capacity or skills, so this is important. Many, many parameters that play there. So I want to acknowledge this appointment is not easy. The people that already went through that process know what I'm and the people that are currently that were not selected know what I'm talking about. I have a few recommendations, a few things I would like to share. First, look forward. Don't look behind or have regrets. The only thing where you are the only reason you would look behind is to be proud of all the work that was accomplished, the things you learned during these long weeks and months of preparation. So look forward. Continue to learn. And the tip is build your open source or your Jenkins muscle in the same spirit as the discussion we had in December. They prepare, learn, get to know people. I am available for whoever wants to have a discussion with me on the experience. I'm interested to know how you feel and how you perceived what happened. So I'm ready to make my time available for that. I'm ready also to discuss with you individually so we can speak more freely. How to move forward. So I will not discuss any details on the ranking decision and how we made so there's don't try it. How to look forward. So please don't give up. And when you fail or you have a problem. Don't give up. Learn from the experience. Well, fast, but learn from it. Here you see a few comments. Some people that were selected were rejected several times. So you need to continue, improve, get stronger, get more experience. Continue to invest yourself in open source generally, not only Jenkins. It's the most important open source project that everybody knows, not serious there. But it open source is a great school and a great way to acquire new skills that are useful in life, but also in a professional career. The general advice I would like to give is observe. Look what's happening. Get in. So learn from what's happening. And this you can only do by getting involved. So participate to meet things, participate and I give details after. Get your hands dirty and this is the way you're going to learn. And forget it's not only hard skills programming and Java and these kind of things. It's also about soft skills that we're talking here in particular. So several people had very interesting to the projects and the proposal on these projects were very good, very strong, had very good ideas in them. A lot of prototypes and ideas were in these documents. And I know there's a lot of work and sweat in it. Submit them, just create a PR and have the people have the community discuss them, improve them. The best example I can give for that, now forgive me, I forget the names. So I apologize for that. But one of the projects we had that we had to stop before was about the user interface for plug-in health probes, the user interface. The project was dropped and one of the would be contributors for that project. When he just submitted the PR of start of his work, this PR was merged and was a huge improvement and also a first step in that direction. And it had a lot of positive influence, heard a lot of people talking in good about that. Don't let the effort get wasted. You're going to learn and you're going to get rewards for that. If you want to do that, just remember that you will be using the resources of plug-in maintainers or the community. It's less focused as the mentorship for Google Summer of Code. So you will have to find solution by yourself and it will be more slow and also more effort-intensive. But this can spread on weeks, months, so no problem. So it is the first advice. Second advice is to attend the special interest groups, so the SIGs. There is UIUX, SIG, for instance. There is also the platform SIG, there is also the documentation SIG. These are meetings that are held at very regular interval. They're documented on the Jenkins IO site. This is where you're going to meet or listen to other members of the community, more experienced, and you will learn there what's going on, what is currently important or useful for the Jenkins product, what to focus on. So, well, OK, I like user interfaces, user experience. I have skills there, but where should I work on? This is where you will learn and know, oh, this is important. OK, I can participate to the effort. So this is why I'm pointing to that. And also you will know who are the people in the community, and they will also start to learn who you are. So this is also very useful stuff for you personally, but also for preparing the next GSOC run. Stay engaged and active. One tip, so submit PRs and things like that, but if you still want to learn something that I find very useful is any of your subjects and the matter you're interested in, look at the PRs that are submitted by more experienced people. So try to understand it, contribute to the review, and suggest improvement or ask clarifications. I don't understand why this particular test is included. This is a very good way to learn how it's done. The easier thing to do and a very positive thing is you try out the PR. So you check it out, build it, and then you try to reproduce the problem and see if it's solved. And you find bugs or tests that do not cover some of the configuration or test case. This is a very useful contribution and will help you to move on in your learning path. The next great opportunity to learn is Oktoberfest. For people not familiar with Europe, so in October, there is a big beer fair or party, especially in southern part of Germany. It's known Oktoberfest and they changed the name. So look up on the internet if you don't know what it is. It's a great way to learn and it's also a good way to win some swags. So I'll be also doing some promotion and guidance during that event. Now, a big recommendation I have, we're outside of the scope of GSOC, where a lot of resources from the organization from Jenkins Project are mobilized. So be respectful and humble in your participation. So be specific in your questions. So especially as, for instance, maintainers or other people, are very busy people, are generally very focused on some of the issues. Be respectful of their time and do your homework. Do your homework in having looked on your own for the solution or why am I stuck and try to describe your problem, what you tried to do as precisely as possible. And be patient. Here for GSOC preparation, we had a lot of people involved. And I want to give a shout out to Chris Turn, who was particularly present in the presentation. And so I hope the noise of the rain doesn't get through the microphone. So be patient for that. So these are the kind of things, the things I wanted to share with you. So I open up now the discussion for the people that were selected, not selected to what I said. Elisa, is the rain getting into my mic? Not at all. I can hear you. For me, it's, for you, it's clear. I do not hear any rain at all. OK, so either everybody fell asleep during my talk or open for question. Don't forget to unmute. I think somebody wanted to intervene during my talk. I don't know if it was Elisa or Jakruti. It wasn't me. I was saying that Adrian had already told me that it wouldn't be available until 10th or 11th of May, something like that. OK, good. I'll leave more time then I have some practical details. Hello. Am I audible? Yes, go ahead. I wanted to say that my exams are shifted to they're started from tomorrow till 13th May. So I won't be able to give out in the until exams are over. That's OK. You should write it down somewhere so that everybody knows the other mentors were not there, for example. So should any mail or something so that we know that we can't expect to see you in the coming week? No, I'll try to attend every meeting and all that. But like I won't be able to research and study for the shock. OK, I exempt someone. More important than, yeah. Oh, well, you don't have to attend just each and every meeting. If we could just make one meeting with the mentors so that we can discuss the project, that would be enough. Don't stress too much on that. Just stay focused on your exam and just one meeting, half an hour at work, and that will be OK. Thank you. A lot of things can be done offline. So I think for the people that were selected, it's quite overwhelming because now you realize now it's a real thing. And especially with the mail with all the thing I sent yesterday. So don't don't get scared by that and ask for guidance. To your mentors, your mentors are there and share that with them. And I think one thing I learned from last year's GSOC is over communication is much welcome. So even if you can't attend meetings, keep the communication line open with status updates, questions via emails like, you know, Jean-Marc mentioned earlier that there's other ways of communications, but over communication is very helpful and it's key. Yeah, I would rephrase it. It's key and helpful to turn it the other way. It's it's very important. Who wanted to add something, Ashutosh? I'll try to over communicate. OK, good. Chris, you wanted to say something? Yeah, we have a question on the chat. OK, can you point it or maybe rephrase it or? OK, we know what it says. It's from Satak Mani. It says congratulations to everyone selected. What are some of the mistakes I've made personally? So any other mistake, improvements, suggestions? Thank you. That's what it says. This is something I prefer to discuss one on one. And these are not mistakes. And let's look forward and see it, General, but I'm ready to discuss it. I prefer to do it one on one. The general rule in open source is praise is done in public. Critique is done in private. And so take the opportunity to to have a discussion. OK, other questions? Currently, I'm already working on a PR, but since Adrien is not available, actually, so I need some help with the PR. So in the meantime, what other things I can do? You so I'm unmuted now. So the phone was ringing here. OK, the case of Adrien. I will look with Jake to see how we can jump start the preparation. There are few things that you can prepare and they can be prepared offline. So at your own pace. The first thing is, for instance, your biography or your presentation on the Jenkins IO site. This is a file and you can ask on the GSOC Gitter channel if you need pointers. It's a file you need to create on the Jenkins IO repository. That follows a certain format where you're going to give who you are, what is your background and show you look what the others did. A little picture or an avatar. And this this can already be be done. So the no GSOC contributor file. I'm seeing the chat here is not the file to update. It's a file to duplicate. So create one with your own name. And you submit a pull request. On it, and if the syntax is not correct, you will be helped. Then there is also the project page. And we can point to that where a certain number of details need to be filled in, added, for instance, an abstract of the project, some links and these kind of things. So you can already work on that. Submit a pull request and ask the mentors to review it. So this you can already do and will take some some time. One of the expectation is for the end of the bonding period is that you're able to do a blog post on Jenkins IO where you will describe who you are, what the project is about and what you're going to do. So you're going to address to the community to explain what you're going to do. And because now people that didn't participate to Google Summer of Code are eager to know what is this? What are the probes that are going to be added so you can do some publicity over the work? Does that answer your question, Jakruti? Yes, thank you so much. OK, so don't hesitate to ask the questions on the GSOC-SIG channel or on community.junkins.io. Working asynchronous is a perfect way of doing. I have a general detail that I didn't raise in my presentation discussion at the beginning. It was that we will continue to hold at this time an open office hour. It will be dedicated to the GSOC contributors, the mentors. It's a moment where we'll sit together and see where we're standing. The focus is on the people participating to GSOC. But if people want to listen in, there's no problem with that as long as you don't disturb the flow of the meeting. Now, if the time doesn't make it, it doesn't work and we have a majority for that, we can shift the time. But on Thursday evening at this particular time, it worked for the majority of the people. We can move it. If you can't make it once in a while, exams, work or whatever, we're not at school here. We're here with adults working together. This is a community. So we'll move forward. Last year, these office hours for GSOC participants were felt as being very helpful. And just creating a community was very interesting. Do we have other questions? Does it look like it, John Mark? No. OK. So if people would like, like Sartac, I've seen Mokul is also around, don't hesitate to reach out directly to me. And I'm ready to discuss a few things where I will not get and don't try to. So no complaining, whining, why I wasn't picked up. It's unfair. And these I will not go into these discussions. So, you know, we're here to think and build for the future so that you can make it in the future. GSOC edition. OK, John Mark, but how should they contact you? Yeah, email. Yeah, I edit the email. I'm going to get spammed. So the presentation slides will be published and. Well, OK. Yeah. My email address is already flying all over the Internet. So I think they can also find your email address when you send them send the the folks who were declined a personal email. Right. Yeah, have your email from there, too. I will I will reach out to a couple of. Well, whoever wants can can reach out. Or maybe via this course, you know, on community. Jenkins.io, you can send the DM. I don't know if you read them. No. Yeah, sure. Sure. Take some time sometimes. But I'll just just ping me. I'm ready to discuss. I'm also interested in these discussions. I want to learn what is your experience? What can we do to improve our handling of it? Well, it was difficult. So I'm I'm I'm and also as a human experience. I'm interested in that. OK. Good question, Chris. Other questions, otherwise we can. Close a call here. No, I we put in the and we put also in the meeting notes. My email address. Yeah, I can do that. OK, so congratulations to the people that were selected. For the others. Don't give up. Continue. And have a nice rest of the day and have a nice weekend. Thank you, everybody. Bye. Bye. Thank you, everyone. My everyone.