 I'm doing fine now. Okay, there. Is it recording? Yeah. No, I. Yes, it is. Okay. All right. Good. Hello, everybody. Good afternoon. Good evening. Good morning. Okay, we're going to go ahead and get started given that it's it's it's time. So thanks for joining our Jenkins Google Summer Code 2022 kickoff. So glad to have everybody here. So all right, so we decided that might be helpful for us to get our thoughts together and put an agenda together. So on the agenda, we have congratulations and welcome to our GSOC contributors, some upcoming milestone, a bonding period checklist, communication channels, weekly office hours, and special interest groups. So congrats and welcome to Yeming, Diraj, Ruchakesh and Vihan. Thank you for doing your due diligence in providing exceptional proposals to the Jenkins project. We know that you have a lot of open source projects to choose from, but you chose Jenkins. So thank you very much. But I wanted to open this a couple of minutes up for you guys to introduce yourselves. Tell us one or two things about you that you'd like us to know. So I'll start with Yeming. Did I say your name right? And I apologize if I said it wrong. Yes, that's correct. Okay. So my name is Yeming. So I'm a graduate student in Carnegie Mellon University. And my major is electrical and computer engineering. In my free time, I like to play video games and writing some codes and anything else. I don't know. Okay, that sounds really interesting. Thank you. Just to be sure, I think I know the answer. You're located on the US east coast. Is that correct? Yes. Okay. So it's now middle of your day? No, the morning. Yes, correct. Okay. I need to sort out the different time zones. Go ahead, Elisa. All right. So next on the list, Dharash. Hi, everyone. My name is Dhiraj. And I'm extremely happy to be here. So first of all, thank you so much for giving us the opportunity. It's extremely amazing to be part of this community and be able to contribute to this project. So if I tell you about myself, I'm currently working with Red Hat as Associate Software Quality Engineer. And I graduated last year. And in my free time, I like to go for a run and bike riding. And I also started going for hiking. So kind of trying to go outdoors. And I like to listen to new music and meeting new people. I love that the most. So I'm extremely happy to be here. That's about me. Thank you so much. Nice to have you on board. Yeah. Ruchikesh. Is Ruchikesh on? I can't see. Hello. I'm Ruchikesh. I'm a computer science undergraduate. I would like to thank the mentors for giving me this opportunity to be part of the champions GSOC 2022. In my free time, I go out with my friends. I watch movies, watch some TV shows. That's all about me. Thank you. Okay, nice. They have you here. Thanks Ruchikesh. Vihan. Hello, everyone. This is Vihan. And I am currently, I've currently passed my sophomore year. I am a CSC undergrad at IIT Indore. And I live in Pune, Maharashtra. In my free time, I love to play music. So I am a singer and an instrumentalist. I love listening to music as well. So typically 50s to 60s American music, blues, and country and jazz. So yeah, I'm extremely happy to be a part of Jenkins under Google summer of four. And I'm optimistic that it will be a fun experience for all of us. Yeah, thank you for having me here. Great. Such a talented group. So welcome. Welcome to the Jenkins family. And we're super happy to have you all. Okay, so this part, Jean-Marc or Chris, would you like to take it from here? Chris, do you want to take it or do I take it? I can do it. Okay, so for your milestone. Next slide too. Yeah, go ahead. Yeah. Oh, okay. Okay. So Friday 20th, which is the past Friday, we have the start of the period which last three weeks. And the next milestone coming up is the Sunday one on June 12, which is the end of the Friday period, which is an important phase because it means the next stage, June 13, start of phase one, we'll start. And then we'll have to remind the mentors to remember like during phase one and phase one and then phase two as well, we'll have to estimate the evaluations. It's extremely important because whether the mentees, we would get stipends or not, depends on whether we submit like basic evaluations on time. So it's important to remember one, the first time we have to do this as to that line is July 29th on Friday. And the second time is on September 19th. So those two important days to keep at the counter. So couldn't face you, we started on July 25th and on September 4th. And after that is the last week of coding. So last week of coding is starts from September 5th and ends on the 12th of September. And an issue is always we'll be announced on September 12th for all the Jackets for Jackets. So next slide. Okay, binary check list. So we have some items we have to check on the list for the binary period, which so we have the first one, Mentor Step Day Project Detail, so Contributors on Jacket Style. So Jean-Marc, do you know like how do we locate the like which files to update? This is a very good point. I didn't prepare that. So the principle is that you do. So there is a placeholder for the project currently on Jenkins.io and it's a pull request process. So I'll send and ask Alyssa to add to the meeting notes and the announcement on community.jenkins, the link to the where the source code is the project located and so what you need to update. If you run into problems and normally the mentors should be able to help and just shout and we can help you what items need to be and I'll review or we will review the updates for the project. So exact link will be in the meeting notes. Okay. Okay, cool. So next point, checklist. Mentors to Guide Contributors to Become Familiar with the Contributing Process, which includes but not limited to get workflow communication channels. I would like to stress the importance of getting familiar with Git because like this year we started late so we didn't have a lot of like pull requests committed with Git. So this is an important checkup. And a third point. Mentors to Define the Profit Communication Channels of Contributors and clearly take such details on Jenkins project page and pull commands. I think we have two channels set up for now but we need two more channels. So Alyssa and Jean-Marc, do you guys know the arrangement for the remaining two channels? For the communication channels we have a separate slide where we'll discuss this topic and see where we're standing. So but the important thing is at the end of the period and as soon as possible this must be settled and this is something that we'll chase. So we'll discuss it just after that. So mentors also need to check whether contributors have set their own local development environment, which includes maybe an IDE, etc. So mentors to discuss with the contributors and other organ members about a formative project plan. So this might include the deadlines, milestones, publishing enough to with more details, figuring out potential issues, etc. So this is an important point because it sets up what will happen throughout the project. Also finally mentors to work with contributors on how the contributors will try their time over the next 10 weeks. So the scheduling and it breaks vacations, etc. So everyone in the project will know when everyone is at any stage. Mentals and contributors agree on their plan, preferably by email before it begins. I recorded somewhere. Yeah, very good. So I will share this slide deck with everyone after the meeting. This is the link to the full document. It's beyond, it includes milestones and deliverables beyond the bonding period. Okay, now communication channels. There has been some discussion and initiatives. And for me, it's not a problem anymore. So the different ways to communicate, I think either a Gitter or the CDF Slack, the choice is per team. So it's open. And it's like colors or text editors. It's a personal choice. So now what I would like to check and do a rundown now is do the four projects something ongoing and know what to do and what to choose. So I'm, I think the plug in health scoring a system. So Deraj and that maybe Deraj, if you can tell is the, the communication channels settled and Slack, the CDF Slack. Yes, it is. I've created it and we also have started to have discussions as well. But we might need to finalize or maybe discuss more on that because you raise the point on Gitter that there are some difficulties in joining Slack. So we need to discuss more on that. Okay, I'll come back. So I think there is a link. I didn't have time to look that up. A full disclosure. It is a public holiday in Belgium. So I was not supposed to start working on my wife was grumbling for that. So no, no problem. So normally there is a link on Jenkins.io that explains how other people can join the Slack channel. But it's not easy and simple and you need to install. So I researched that, asked the different projects that are using the CDF Slack to add a small note and or link to a more global documentation on how to proceed. But I will take care of explaining to people how to join the conversation. But you have Deraj, you have your channel running, right? Yes. Okay. And the mentors are on. And the Jenkins file runner Oleg created that. And I also saw that Chris and Yiming is already active on that channel. So the only two channels that right now where that's questionable are the automatic Git cache and the pipeline step documentation generator. Those two, Michelle from CDF has created those two sub channels. But because she and I could not add the rest of the folks on there because they're not CDF members. So what she did was she sent out invitations from CDF. So if you did receive an invite, please accept it so that we can hopefully we can add you to these subgroups in Slack. I think there is a way. I don't remember how it works. But this needs to be sorted out because it's very complicated to join the CDF Slack. But I don't think so. But just checking here, so automatic Git cache maintenance. Who's on that? Who re-cache? We have selected the Git plugin channel. So all the distributions will be happening in that channel. So you're going to use GitR? Yes. The GitR Git plugin channel. Okay. So the Slack channel is not required and you have a channel for that. So you have the GitR channel set up. So you're ready to go, Ruri Kesh? I find GitR comfortable. So we have discussed and we all agreed upon using the Git plugin channel. And Git does. Okay. That's good. So the channel will not be required for the Git one. So Slack is not going to be required? Did I understand that correctly? Yes. Okay. For that project. And now checking for pipeline step documentation. I know Christine is there. Who else is from the project there? What is the status for that project? Yes. So likewise, we also discussed and we decided that we'd use a Jenkins CIS slash docs a channel in GitR for this project. So Christine thought that it would be a good idea to discuss it out in the front of the community. And since it's a documentation based project, that channel seems to be suitable for now. So we won't require Slack either as of now. Okay. So that's perfect. I leave the choice to every... I have a personal preference for GitR, but don't listen to that. Don't forget to update in the project page. This is one of the first things that you can update on your project page is what is your channel where you're discussing. So this... And don't wait for having everything filled in all the questions, purpose, and so on. Add the information you already have on that page. Okay. And in every case, you can use the community discourse system to ask questions or raise and reach out to the community. And on the GSOC main page, just a reminder, we are starting, but if something is going wrong during the summer and you want to reach out directly in... What is the English word for it? Not discreet, but not in a direct... Private. Not in a public way, private. That is exactly the word that I was... If you want to reach out in a private manner with the org admins, there is a link to an email address where you can raise and ask. I'd like to discuss and talk to somebody because something is not working as expected. I don't want to discuss that in public. We want to have that possibility. Now, I will be available. My email... All our emails are flying around all over the place, so you can also reach out directly if something is wrong. And we will also... This is for the next slide. So we will hold a weekly office hour. So we'll keep that rhythm. We'll hold only one single office hour at about this time. So that's 3 p.m. UTC, a short Zoom call. So the purpose is that we have a quick overall global GSOC checkpoint where we can just report very shortly. This is where we are. This is what we achieved. We have some important roadblocks that are preventing us to move as we want. So this is a way to share to the community where the projects are standing and just to have a news report, I would say, anyway. So it's just to improve the communication and sharing of information, how others are doing. So to avoid that, every project now enters submarine mode and disappears from the surface of the earth. So Zoom, 30 minutes. We hold it at this time. So a question is this time okay for most of the people? So this is a compromise between US and Asia. Europe is in between. So Europe is good. But does somebody want to change the time or the date? Looks like we have consensus, Sean Mark. Okay, let's go on. So just for practical reason, I will be organizing and handling that during all the summer. I might not be in the usual place when I am be visiting my granddaughters in France. So that's it for me on that slide, Alyssa. Thank you. Is Kristin on? Yeah, I'm here. So Kristin, we're going to have you talk about this slide if possible. So it's special interest group. Sure. All right. So one of the really cool things about working in open source and kind of even Jenkins, when the project gets so large, there's these groups that kind of form around certain topics that are important to the project. So these are special interest groups. And in Jenkins, we have several, as you might see, actually Google Summer of Code is one. So you all are participating in this special interest group just by being here. So sometimes also you'll find that your project might fit within one of these groups. For example, like we're using the documentation channel, which is part of the documentation special interest group to talk about the pipeline steps project. And a lot of these other groups might be interested in what you're working on. And each of them kind of has a link here and you can go to the page. And they'll have different mailing lists or have getter chats. And then a lot of times also have meetings. And whether these happen every two weeks or every month or every week, depending, you can kind of attend one of their meetings. So this might be a really great place for you to find out more about like to be able to share your project as it's going and to be able to kind of get involved more with the community. So I highly recommend to kind of think about what your project is. And then to visit one of these to see if you maybe it fits in with the one of these groups, your mentors might be able to help too. And then this is a great place to be able to present different parts about your project. Usually they'll have a like a meeting agenda. Markway is like incredible at keeping the documentation notes and stuff, but you can put yourself on their agenda and talk about your project, maybe do like some presentations, but also to kind of get some feedback about what you're working on. So this is just another way to get involved into the community. Good way to test ideas or to to get feedback from a broader audience and get people interested. Exactly. So there your these will be great resources for you and will also help cheer you on with your project to help make you succeed and get the best possible stuff. So please check out these. It's on the Jenkins IO website. Just underneath you can go to community. And then there's a you can click on the special interest groups and it takes you to the main page. So I highly recommend checking this out and talking with your mentors to see if there's a good place where your project could fit in. This is a very good tip. Thank you for raising that. Thanks, Kristen. All right, so we're going to I'm going to check the time. Oh, we have about four minutes left. So I'm going to we're going to open this up for any Q&A. Like I said, I will update. I will update this slide with additional content. We'll we'll add our our emails in here. So feel free to contact us directly update the communication channels as well. And you can always refer to that or just reach out to any of us work admins or mentors and, you know, we can help out the question or doubts. I think since yes, thanks. So since all the mentors are here, maybe any one of them, if they're interested, can share any tips for us to deliver the project and make it a success. It's a good one. That's a good one. Yeah. Kristen, since you've had experience with this in the past, perhaps you can put on the spot. It's all good. I was like, this is a good question. I would I think the big thing is to make sure that you're staying in contact like constantly and even over communication is a great thing. So just sharing like sharing what you're working on that day, even if it doesn't feel like a whole lot or maybe you can say I'm struggling with something and it helps kind of unblock you. So I would say just kind of communicate more than you think you would need to or and just that way we can respond better or even maybe there's someone in the community who will, you know, if you join one of those channels or listening, someone else might have a suggestion, but it's just kind of like over communicate what you're doing, even if it doesn't feel like even if you think it's boring or not interesting. We want you to succeed and we want to help you and we don't know what that is if we don't talk to each other. So definitely everyone share as much as possible. If I quickly jump in here, especially if you're young and this can be intimidating, an intimidating audience, there is no harm to ask and say I'm struggling with this or that. I don't understand. It's not a judgment on your capacity or whatever. We all have been in the same situation as you are now and this is why we are eager to help you out. But the only way to help you is that you say here, I have a doubt or I don't understand or so. And the advice of Christine is to go ahead. Yeah, let's say like, no, I was like exactly at Jean-Marc because it's just, yeah, we want you to succeed and we want to help you. And the best way for us to be able to do that is to know what's happening. So and you're right, at least sometimes I can be intimidating and jump into open source stuff. But a lot of you have already asked questions on the channel and we're, the Jenkins community is really friendly. I've noticed that like very friendly, very willing to answer questions and help you move forward. So we want you to, we want these projects to be success and we want to be able to see like these really cool demos that you'll show off and so anything like that. That's it for me. Very good. Very good tip. Yeah. Awesome. Thanks a lot. Don't be shy. Ask for help. I mean, for me when I first started, it's, I felt, I felt intimidated, but I learned along the way that there's a lot of people that do want to help us and do want you to succeed. So use that, leverage that. We're all together and we want to brag about your work. So we need to be proud of what we did. Somebody else wants to ask, go ahead. I just wanted to give you the bait. Yeah, we have a question on the chat from Leon. Yeah. Oh, well, I have my opinion on that one, but maybe Christine or Chris can give your opinion, but I let the others say their opinion, but I'm very liberal on that. Chris or Christine? Yeah, it really depends on like the agreement between the mentor and the mentees. So it's like, it's up to like the individual project. Yeah, I'm pretty much think that weekends are an important time for you to be able to take time off and you do better working if you do take time off and have time to think in between. So yeah, this needs to be like every day, sitting at the computer, knocking out lines of code. It's like, no, no, no. A lot of it is going to, you need to be able to enjoy your summer. Exactly. And this is something where the mentors can help you to find the correct balance. So it's a mentorship relationship and this is why communicating and giving details about what you're doing, what is your next milestone, did you reach? Do you have difficulties in the communication, especially in this context, is very important. Life and work balance is very important and is part also of the training that you need to find and discuss it. I made my experiences personally, I have my way of doing it, find it, explore it, discuss with people and with the community. The most important thing is it's an important program. It's a program with a lot of visibility. It's not a death march, a march, so I don't want you to start working over time and so Christine really said it very well. So in discuss with the mentors and see, we're not in a factory here. We're knowledge workers. Work-life balance is important. Okay, so we're three minutes over time. Before we drop, I want to leave it for any last questions. Yeah, I had one more question left. For example, if you want to discuss any project related or a schedule specific thing with a mentor, so what would be the preferred platform for direct communication via email or anything else? Well, I have my point of view there but I will let the lead mentors or the more experienced mentors here or whoever has an opinion on that. How do you want Menti, is that the right English word or Menti, reach out to you for these kind of questions? I would say it would be up to individual project group. Talk with your mentors, see what is his or her preference and use that because every project group has different mentors and they have different preference, I'm sure. Yeah, there is a nuance and then I let Chris and Christine eventually chime in. So what is interesting in the community is to discuss in the open, meaning that people can share ideas and give their opinion and then and so for these kind of discussion and don't forget that openness is a critical mechanism of open source that we're going to learn together this summer and so use the Slack or Gitter channels for that so that you're using it openly. If you're more shy or introvert or so don't feel secure enough, you always have mail and direct contact with people. You will be more secure, you will not have the impression that you have so many eyes looking at you but you will be missing the eyes. Don't forget that emails, you're talking to one single person, this person might not be available, it takes time, it's done on the free time of the various mentors, so there's lag on that. We're using the open channels, there will be somebody monitoring, it might jump in and say, well here if you do it that way or this is not critical and this can be done later so it's a balance that you have to choose for that so Vihan, was that a useful answer for your question? Yes, sure. If I were also going to be opening up Kristen because she's my mentor which communication mode I would she prefer it would be great. Yeah, sometimes it's easier to hit me on Gitter, sometimes I'm like a little behind on my email because it's full of the GitHub messages all the time so Gitter sometimes works and it's very asynchronous so applying across cool things. I didn't want to have a strong opinion on or give a strong opinion on that but Gitter is generally the most efficient. I want to give nuance and I don't want to be too questioned. Other questions or points or point of view Chris or whoever wants to add something? Well I will conclude by saying I'm super happy of this this edition with the team and I think we're I'm convinced we're going to have a lot of fun during the summer and