 Hi everybody. Thanks for joining today's Jenkins Advocacy and Outreach SIG meeting. Today is Thursday, March 21st. So on the agenda, I have Scale X that Mark and I was just at this past weekend. And then we will discuss GSOC where we're at right now. Next event and couple of reminders for things that's coming up. Anything else that we need to add? Good? Okay. So as I mentioned, Mark and I was at Scale in Los Angeles this past weekend. It seems like there was a smaller crowd this year, but the conversations that we had were of quality. I also noticed that Google had put out a full page advertisement for Google Summer of Code in their in the conference catalog. Mark, you probably, I'm not sure if you saw that, but it was a full page ad. So I thought that was cool. And then had good breakout sessions. Mark and I and Basil, who were staffing the booth, we had a chance to go to a couple of sessions. I attended more of the community breakout sessions. And then there were more AIs talks that I saw on the agenda. And Mark, did you want to share what your thoughts were for breakout sessions? My mind matched with yours. I enjoyed the one or two sessions I attended and the crowd was a little different this year than in past years. Yeah. And then Meta, GitHub, AWS were the large players in the expo hall this year and we were right next to AWS. Anything else you'd like to add there, Mark? Nope? Okay. No, that's yeah. Good conversations while we're at the booth with Basil and Alyssa and me. Cool. For GSOC update, so at this time, we have received 34 draft proposals. Nine applicants submitted two to three project ideas draft proposals. The top three project ideas with the most interest are cloud events, plug-in for Jenkins. We got four of those. Enhancing existing LLM model for domain specific Jenkins knowledge. We got six of those. And then implementing UI for Jenkins info statistics. I have six of those came in. So, we've got a very excited crowd who wants to know when are they going to receive their feedback for their drafts. So, there's lots of reading to do, folks. Alyssa? Yes. Hi, John Mark. Okay. Hello. So, just a comment here. Discussed with Chris just before. One of the observations is that applicants resubmitted the same document. With their update? Yes. So, instead of just updating the existing documents and using the commenting feature for the document, so something to know and maybe something to address in future additions that we explain them how to do it. Yeah. So, I wonder if they resubmit their draft proposal, does that mean that it adds, it makes it one additional draft proposal or? Well, it turns up as a separate entry in the tracking sheet. Okay. And some of them are a different document. And others, so at least I spot it once. And others are just the same document, so the same URL to the document, but a new entry. So, there's some potential confusion there. Okay. All right. Thanks for letting me know. So, for next time, yeah. And there are three mentors that didn't review any of the documents now. Yeah. And the other way around, I think there are a couple of documents that proposals that were not reviewed at all. We need to be attentive. Right. Right. I hope to do some of my reviews today. So, I know I'm one of the guilty parties who hasn't reviewed. You have a special status as representative of the Jenkins board. Yeah. Special status is hardly an excuse, but that's there. I've got reviews to do. Yeah. And Alex told me that he will also review after. After we close the form. So, after tomorrow. So, yeah. Sorry to interrupt. So, what you say, Elisa, is that the draft proposal is closed tomorrow. That's right. By draft proposal, you mean closing the Google form that allows to make some new entries into the Google sheet, right? Yeah. Cool. Yeah. So, by the time 12 p.m. UTC, that sets the deadline. We're not accepting anymore. We've got plenty to read. Yeah. So, that's a deadline for the contributors, but not for the mentors. Right. So, mentors may begin reading, you know, many of you have already started reading, but the deadline for that is here for the mentors. Yeah. Yes. And the deadline for the contributors regarding to Google is... That is on... Hold on. Let me check. I have a bunch of dates. April 2nd. April 2nd. Yeah. Okay. Yeah. And I put all those dates on the calendar invite, as well as the Slack channel for mentors. So, all of that has been listed out. Yeah. Okay. So, I have been misunderstanding. So, it's not that my reviews must be all completed within the next 24 hours. It's rather that I know it is... My fault, Mark. I gave you wrong information. Okay. But so, I've got a little bit more time. I may be able to do some reviews over the weekend. Good. Thank you. But Mark, there is... And the questions we're discussing here means that we need to inform all the mentors of what are the... I won't say rules of engagement, but how does it work now? So, there's draft reviews where we actively discuss with the candidate, and then there is the grading review where we keep our comments between us and where we are going to put a value to... Is my understanding correct? Yeah. And the grading review is on proposals that have been submitted to Google, not the ones that are submitted to us for review. Right. Okay. Got it. And they're frozen. With a little risk, they're able to resubmit. Okay. This is what Chris made me aware of, which I forgot. Yeah. So, it's shoveling snow while it's still snowing. Yeah. So, definitely, I'll send out another email with specific instructions just so that everybody is clear on what's happening now, starting now until the time of the grading. Yeah. Don't forget to mention the tracking sheet we're using because I fear some of the people are not aware of that. Yeah. I'll be sure to make that clear to everyone. But the tracking sheet, it's included in the calendar invites that I had set up previously. So, all the links should be in the description. Okay. No, this is all good. Good discussion to clear things up. But, Mark, you have for the draft proposals that you have now, the deadline for mentor to review that is March 27. Great. So, I've got a few days. Thank you. Thanks very much. To the middle of next week. Okay. Is there anything else that we should add here? Mark, Chris Bruno. Just my comment. It's looking good. Yeah. Yeah. Thank you to everybody who's been providing feedback for the reviews that's been really helpful. Okay. So, Mark is attending the next event, which is CDCon, April 16 to the 18th. Mark, I am working with Michelle to see if we can, I think, CloudBees would like to offer some discounts for the Jenkins certification program. Discount code. But more to come if that's good. We're going to go through with that. But just a heads up that you may see a postcard or something laying around at the conference. Okay. Because there certainly isn't a Jenkins table or Jenkins booth. Right. So, I'm not staffing a booth. I'm going as an attendee. And I'm delighted to admit that I will be face-to-face with one of our former Google Summer of Code contributors. Oh. Yeah. So, oh dear, his name now. Let's see. That's embarrassing. He was... Dheeraj? Yes. Dheeraj Singjoda will be presenting at the conference. Right. Dheeraj will be presenting at GitOpsCon on Monday, April 15. I won't be able to attend because they charge an extra $250 to attend GitOpsCon and I'm not going to pay to attend one talk. But Dheeraj has agreed to let me take him to dinner on Monday night and we'll have a lovely chance to connect. He is presenting with a colleague from Red Hat on the techniques they use as part of the testing organization in the OpenShift development team at Red Hat. So, talking about how they do continuous delivery and GitOps in the Red Hat testing organization that deals with OpenShift. And so, he'll be there physically in Seattle and I'll get a chance to talk with Dheeraj and say hello to him. I will certainly tell Dheeraj hello from all of you. I believe all of you interacted with Dheeraj in various ways during his contributions to Jenkins documentation during his time as a Google Summer of Code contributor. And so, thanks very much to everybody and I will certainly pass your greetings to him. And tell him that it's very gratifying to see him grow and continue the path of open source and sharing. I agree. So, it's a pleasure for me. Yeah. So, I'm truly excited by his being accepted as a presenter and somebody must be funding his travel from India to Seattle and back. So, that's very impressive. Yeah. Indeed. Good. Well done. Yeah. That makes my day. Yeah. So, just a couple of reminders. So, we have the Jenkins Awards. The voting is going to be open until tomorrow. So, I will be sending out a tweet to remind folks on that. So, if you haven't voted, please get your votes in. And then, again, I'm going to be out of the office the April 3rd to the 19th. So, I should be able by the time that I'm away, this is the period where the grading will take place. So, before I go, I will make sure that all of the proposals that we received within the Google portal is going to be transferred over to the spreadsheet so that mentors can just, you know, use the spreadsheet and grade from there and provide their grades on that spreadsheet. It doesn't have to go anywhere else. So, when I come back, I will review the gradings that come in and then I'll set up meetings for the following week so that we can determine as mentors, you know, we're going to determine who do we select, what projects, etc. Okay. So, that will be the week of April 22nd, 23rd, if I'm not mistaken. Listen, I already told a couple of people. So, I will be offline during that. I will really strive to really make an effort to actively participate to the grading and read all the documents. I will not be available for the meetings where you do the ranking. If it's needed just to have enough votes for that, send me a mail. Okay. Mails I'll be reading. All the rest I will be off the net. Okay. Sounds good. And then I think Bruno, you are off, Bruno's off on the 20th to the 27th. Yeah. Okay. Chris, do you have plans to be away? Chris does not sleep and does not go on vacation. Yeah. Okay. But yeah, so I think with us having been off, we should be able to manage and meet Google's deadline, which is the 24th is when we need to submit to them our final project decision and candidates. And I will be able to do that. So, we should be on schedule. And because most of us are going to be out, most part of April, so our next meeting is going to be May 2nd, if that's okay. Okay. If there's nothing else, thank you all for joining. Happy reading. Okay. Yeah. Happy reading. Thank you. Thank you. I start to mix. No, no, it's okay. It's okay. All right. Take care. All right. Bye.