 Recording is okay. Bruno, you lead. Why not? Let's go. Yes, that's why we had schedule. So let's go for it. Sorry. So this is Jenkins Advocacy in Outreach, Sieg for December 15, 2022. Today we have with us Chris Turnes or MacMesson, Mark Rait and myself. Thanks for being here. Now, first thing is action items. Just one item today, which is pretty cool. Scale 2820x. So Alisa has secured the boost for Jenkins. Thanks a lot Alisa for that. It's happening in March 2023. This year it was in July, if I'm not mistaken. Yeah. And you, Mark, made three speaking proposals. When is the CFP ending? CFP has closed. Okay. So we should know before March. We hope to know reasonably soon if any of the talks have been accepted. Even if they haven't, Alisa and I still plan to attend. It's not that expensive for us to get to Los Angeles. So we'll plan to be there and keep the tradition that we've been there for many, many years as a project. Cool. Now next subject is GSOC 2023. Mark, the floor is yours. Okay. So we're, the important message is we're on schedule. We're good. But still short on project idea and especially mentors. I'll come back on that later. So the next important milestone is that on Tuesday, December 20th, we will have first introduction, first webinar with all interested contributors called before students to get them oriented, give them advice how to get prepared, what are the next steps in the application process. An important thing for that is that without going into the details of the proposals, we need to show them and get them interested in the various projects that we propose for them to work on. Depending if you look at the half empty glass or the half full glass, depending how you see it, we have now a substantial number of projects, but I still consider that we don't have enough. We need to have others. We have quite a lot of what I call entry level, which don't require high Java skills. We could use some more medium complexity projects. I'm currently reviewing all the project ideas in discussion, updating them to draft. But what is more worrying at this moment is that we don't have a lot of mentors. So there is a group of core mentors. I would say Mark is one and the other one is Chris. Thank you for volunteering on mentoring one of the projects. So we need more, especially in the preparation part where we need to explain and coach students to build a successful proposal, but also during the summer. We had a CDF meeting yesterday, if I remember well, and we're going to reach out to the CDF ambassador to see if people are available there. So Alyssa sent a mail yesterday during my night, so during her day for that to see. So there we still need to do an important effort. So my past experience indicates that others may have a different experience, but the most successful things I've done has been specifically send personal email to exact people that I'm targeting. So Rishabh, will you please help me coach this project idea I've got on the Git plugin? And now that means I had to have a good project idea to start, right? And then, Justin Haringa, will you please help me coach this particular thing? And Justin then can say, hey, not interested or, oh yeah, I'd be willing to do that again. So for me, the exercise there is as we get more project ideas, I will, at least for the projects that the ideas I propose, I'm going to send specific invitations to individuals saying, will you join me in mentoring this? If only because that way they know there's somebody they can rely on. They're not alone as the mentor. And they know that there's a project and they can decide if they're interested in the project or not. Good advice. And it's a good point that you mentioned that having a strong or more substantial list of projects and have them correctly explained is the first step. Yeah. And we may not misunderstand my comment here. We're not at all in a crisis mode. So we're good. We're nearly two months ahead of planning right now. So we just need to stay focused. Yeah. Maybe people are in the Christmas mode, you know, thinking of their holiday and so on. So maybe on the first generation, they will wake up and say, oh, I might do something for Jenkins, you never know. Unfortunately, that's not been my experience that nothing gets them to come out, except me specifically asking them, will you, will you do this? And I think that matched with Oleg's experience as well that he found he actually had to personally recruit people. And it's, it's, it may be tragic, it may be whatever, but it was the practical reality he was observing was if a person is asked directly by individual email messages. Now that means I've got to have their email address. I've got to have interacted with them. Those are all complicating things. Yeah. Good. And I think we should change strategies instead of up to now as we did spraying our request for mentorship now being more targeted, almost focused recruitment. Yeah. Because I said, I saw the tweet yesterday, I think, or the day before saying offer the mentorship for Christmas. I'm probably brilliant, but I don't know if you got any feedback about that. I love the image, by the way. Thank you very, very, what a cool open graph that was. That was a beautiful piece of work. Yeah. I think it's, it's Alyssa and her son. Yeah. Well, I didn't want to mention him directly. You're right. But I would say the elves working with Alyssa. Oh, yeah, of course. My bad. Okay, Mark. So you've got a big list of people who could help us being mentors. Okay. Well, and I'm one of the dangers is I don't have a terribly big list. But I think, I think what we can do is start cultivating our lists to try to assemble more and, and accept that 80% of them will probably decline. Yeah. But personal invitation is, is more likely at least for me has been more likely to work than than a broadcast message. Yeah. Very true. Very true. Wow. So summarize summary. Next big milestone is webinar on Tuesday, task. Yeah, the 20th. We're cleaning up and making they have a clear view of the current project ideas and improve that. And on those two elements, we're going to build an active mentor recruitment campaign and more focused than we did. Okay, I don't want people to procrastinate, sorry to interrupt. But what is your deadline about new ideas for the GSOC 2023? The final deadline is when the, no, I'm joking. When I say that is when the students apply and send in their proposal. So even a student can submit his own idea, which we don't recommend because we recommend that now I need to get the dates right, but I think it's around March end of February, March for a month. We will help students to work on their personal proposal, review it, guide them so that they have a strong proposal. And that has been reviewed and discussed by with the community. I don't remember. I think it's late spring or March or something like I need to check. Yeah, I think it's March. Okay. Chris, you remember? Yeah, it's March. March, okay. So you should trust my memory more. So and in terms of back to the personal invitation thing, I think I'm going to send or one of us should send an email to past GSOC contributors and invite them to attend. I'm not sure they'll say anything, but they may be a good voice in case John Mark, you or Chris want want to refer to them and say, hey, Rishabh's experience was like this or Hrushakesh's experience was like this. Yeah. Or is that is that a waste of effort? Maybe I should ask rather than tell would that would that help the to have them present or not? So I think I think this where I will do it tonight. So there's a wonderful idea to have them on board during the first webinar. And especially the second one would add more power to our proposal and attract more students and hopefully strong students. So this is a very good very good idea. So we have the initial webinar where we explain how to get prepared and what are the next steps. And then we'll have one or two webinars where the projects will be explained in details. Okay. So the upcoming session is not going to be an awful lot about project ideas. It's how do you get involved in the Jenkins project and how do you start building the skills you need to create a successful project proposal? Exactly. Yeah. So more general in asking questions and guiding their energy in the right direction. Chris, you wanted to add something? Oh, I was just wondering if I should contact Yiming myself personally. Yeah, that's a good idea. That would be great. Yiming's certainly much more likely to respond to an invitation from you, Chris, than from me or Bruno, right? So Yiming doesn't know me, whereas he knows you and worked with you. Yeah, we're still in touch. So it should be fine. You're still in touch with him? Yeah, yeah. Okay, that's cool. And I will, oh, that's right. The other one, of course, I'll invite Dheeraj. And Dheeraj and Veehan and Hrushakesh, I'm comfortable in sending those invites. I think they know me well enough to say yes or tell me no. No, no, no, this is good. And if you want to know exactly so my my proposal for the attendance is that they will be able to give another lighting or or yeah, that's not correct English, but on answers I make or we may give as Oregon means they will give a practical feet on the ground feedback and maybe be able to answer in a better way to questions from the other side of the coin. Yep, right, exactly. And one of the questions I'm immediately going to ask them is why was it important for them? What did they learn from the experience? Why is it worthwhile to make the effort? I asked often. And I assume that part of that is telling the story that this is non-trivial effort. They are going into a competitive environment, right? This is a it's highly competitive to be accepted to Google Summer of Code and therefore they should not expect zero effort. It takes a lot of work to prepare an adequate proposal that then could be accepted. Yeah, and this is a message that the best people to convey that are last year's participants. Right. It's not an easy task, rewarding, interesting, but a long run. Oh, okay. That's what I can say for Google Summer of Code Bruno. I don't know. I don't have more to say on that. That's perfect. I think you said what had to be said. So that's fine with me. Thanks a lot, Jean-Marc. Now, the December newsletter is been three months, three months, I guess. Since we started the Jenkins newsletter, it's a blog post on Jenkins.io. And for the last months, I think Mark got the idea of creating a newsletter for the whole year. So talking about platform advocacy, all the six that we have so that we'll be able to make a recap of what happened for Jenkins in 2022 and lots of things have happened during this year. So we'll have lots of things to say about that. So what do we have? Alisa reached out to CDF and Design Open Source Design for the newsletter headline. I don't know if we have any feedback from the CDF Design Open Source. No. I didn't hear yet. I talked to Alisa yesterday evening, my time, and no. That'll come. I don't have the date, the deadline yet. So most of the time we do something at the end of the month and then it's published at the very beginning of the next month. Mark, I don't know. Should we target beginning of January or do you want it to be published at the end of December? I'm okay with whenever we would normally have published the December newsletter. I think early January is great. That's usually when we do it, right? We post the November newsletter was actually published in early December? Yes, indeed. Yeah. So that would be consistent with it. Now, if the three of you would be willing, I would love to show you what Kevin and I have framed as themes for that and get your insights on, hey, are there other themes? Are there themes we missed in our brainstorming? I know that Alisa had been working on that and is also leading the effort. Yeah. And I think there was also the yearly recap that she was thinking with Kevin. Right, exactly. And so in Docs Office Hours later today, we'll review these ideas and try to gather more as well. So the thought we had was themes included platform modernization. Oh, it looks like Kevin's actively editing. Well, sorry, we'll get to watch this. So platform modernization, user experience improvements, and this one is huge. We haven't captured all the many things that were there, but platform user experience and development acceleration was the way we phrased this one, which is many, many dependencies have been updated. We've got a new version of Antler. We got rid of Handlebars 3, a major effort, switched out juice from the old 5.0 to 5.1, and yarn upgraded across two major versions to three. Then we've got additional testing of installers and of the Bill of Materials, all sorts of cool stories there. So development acceleration was a theme. Website improvements was a theme. And this one's a Google Summer of Code result. So thanks very much to Veehan Thora for that. Localization simplification, thanks to the work of Alex Brandus. CrowdIn makes it much easier to handle plug-in localization. And it's easier to do Jenkins core localization thanks to the work on UTF-8 property files. Elections was a topic we thought of. Outreach and advocacy. So to this, to this SIG, we thought of, okay, thanks to the new release leads. Chris Stern, thank you very much. You've been release lead multiple times and much appreciated. Improvements to the community site, the deployment of the community site. Google Summer of Code 2022. And we've had four excellent projects there. So that's a good story to tell for projects. Successful, et cetera. And nice links. Actoberfest. Sheikot Africa and the stories site. So stories.jankins.io. Then security was another one and infrastructure was another one. And special examples, specific examples of sponsor contributions. Any others that you'd like to recommend or places or maybe corrections you'd suggest for the titles or themes of these big picture or summary items? We mentioned, yeah, we have the various activities we for outreach. We had to cancel, we had to cancel the not developer meetup, but the... Oh, Jenkins contributor summit, right? Correct, yeah. Jenkins contributor summit, we had the one in... Did we do one earlier in the year? So it was, didn't we have one sometime? So let me, Jenkins contributor summit in early 2022. So there was the one in Texas. Oh, yes, yes, right. You're right. CDCon. Yeah. Right, okay. And then the misfired one in... End of September, early October. Well, but now you've inspired one more idea here on UX improvements. It's the vision presentation by Tim and Jan at DevOps world, right? It's not an implementation. It's their picture of where they think it should go. So that's a really cool one, and we could link to their video even. I think we could link to their video. Good. More suggestions. Hopefully, Kevin's not panicking that I'm editing the document. He's also editing at the same time to Jenkins, Advocacina, Trich, Sieg agenda. He's everywhere. Very good. All right. If no other suggestions, are you okay if I switch back and back to you, Bruno? Just one note. Did we do something for FOSDEM? In February, I think they will... We have a stand, just a table. We didn't have it this year. Oh, this year? Oh, sorry. For me, it was small enough because of the nature of FOSDEM virtual that they did, that I didn't put it on the list. It was an intentional omission in this case. We were there, but there was a CI-CD dev room at FOSDEM 2022. But I didn't put it on this list because I didn't feel it was that big. I agree. Yeah, remove it. I hope that we can make it big this year. Right. 2023. Yep. Any other items that you think should be on the list? Not for my side. Jean-Marc, Chris? No? I'm out of idea right now. Really? So that can happen. I think Alissa was asking for some dedicated visuals for that newsletter. Good. I think that has already been said. Yep. Okay. So we still need to provide the next update to it. Yes, each person taking care of one thing is supposed to enter all the information. And there's also a call to the community. If they want to participate in the monthly newsletter, there is a Google form somewhere where people can enter what they think is important for the different SIG platforms, SIG docs, whatever. But I haven't seen anything yet. It's not an obscure link for Google Doc. It's of course published in the community Jenkins IO. Alissa does it every month. Kevin's and my plan was to put this kind of stuff into that Google Doc. We were just using this assembly point as our first place. But it will ultimately arrive in the Google Doc. Cool. Thank you. Kevin just added the next subject a few minutes ago, which is JFrogment non-blockboth. Because yes, it will be a downtime on Sunday. Nobody will be able to build a plugin if I understood correctly. But the end user won't be impacted if I'm not mistaken. Right. Although ci.jenkins.io jobs will also be paused. And they'll be paused because if they're not paused, they will fail to build. Yeah. I guess that there will be notifications on the site. Right. They're already there. Notifications. Well, the site itself will actually be down. Repo.jenkinsci.org will be down. And so it won't be able to notify, but notifications are already posted in the blog post and also to status.jenkins.io. Let's open that page so we can get a link to it. Jenkins.io. And is it possible to do something on GitHub? No. Oh, that's a good suggestion. We should put in the banner of Jenkins Ci and Jenkins Infra because Erwe did that a week or two when we were doing Hacktoberfest. He did that. And I think that's a very good idea, John Mark. So let's put a, yeah. So what I propose there is let's put an action item, pull requests, requests to Jenkins Infra and Jenkins Ci or Jenkins-infra and Jenkins Ci GitHub orgs to place the notice on the top page of each org. It's not that it's not that we can assure people will read that, but it's one more place for them to read. Right. One more chance. This is a natural go-to place where people will go if they start a build. They will submit a pull request. They want to check in there. Oh, yeah, it stops. Right. Exactly. So I think it's natural to have it there and then they will go to Jenkins.io to see what's happening. And so these two places we need to have. Well, and I wonder, should we also put a message at the top of ci.jankins.io because it will be up, but we could change its description to say, hey, it's up. It's, oh, yeah, the shutdown message, right? Yeah. Include more information in the shutdown message. And it's really not shut down in this case. It's paused, but message on ci.jankins.io. Very good. These are communication-related suggestions that we do to the GFrog maintenance project for people that are. Right. Good. Looking on that, just thinking. I think you covered most. And if we want really to go completely overboard, we could add something on the community, but I think this is a little bit too far. Oh, no, but that's another place where we should put it, right? Because if we don't already have it, do we, Kevin, I thought we actually already had a post on community.jankins.io for that downtime. But if not, post to community.jankins.io with a link to the blog post. When you say we notify on jankins.io, do we have something in the Turbotron or Jumbotron? Oh, the jump. That's another good idea, right? We could put, although that's an interesting idea. Will it, do you think it will help if we say, hey, we're doing an upgrade and put it in the Jumbotron? It's top-level page. Yeah. It's the first one, but as it's rotating, so I'm wondering. I think the most efficient place will be GitHub. This is my personal feeling. And I've put the link, the community jankins.io blog post already exists. It's not a blog post, it's a post. Yeah. Oh, good. Okay. So, and on community, it's already there. That's what you're saying, right? Sorry. That's what I guess. Great. Okay. So that's really good. Excellent. And Jumbotron, these are suggestions and we can, we can eventually wait. So Jean-Marc, what you call Jumbotron is the carousel with the images I'm thinking. Correct. Yeah. The problem of that one is that it's not static. It's rotating. So maybe it's. See, for me, the problem is contextual blindness. I no longer look at the carousel because I've seen it so many, right? I just stopped looking at it and therefore you could put dancing bears in that carousel and I would probably not detect them. Oh, you're scaring me now. Okay. All right. So we've got, those seem like good actions. Any other, sorry Bruno, back to you. No problem. So I think we're done with that part. Now the events, we already talked about first them. Alisa did. Go ahead, Jumbotron. One additional point. Suggestion for a GFROC communication plan. We may ask or organize that we have people looking at the dev list and community.jenkinsio during the weekend or during the heritage so that we can answer quickly and or Twitter, but Twitter becomes something of the past. But at least that we have somebody or rotation of that, but that we are aware to have a look to the social or communication. Yeah. And so we've now got a time from them. Let me look to see if it's the time that I think has been stated is the outage will begin. Outage starts at 11 o'clock a.m. Israel time. I don't know what that is in UTC. I'll have to do the math to figure that out in UTC. But that was the last best announcement I saw. So that's reasonably close to the time that I get up in the mornings. So I'll be available for part of that. And I think 11 o'clock. Well, it's earlier than there one hour before us. Only one. Okay. So yeah, for them, it's already so 9 a.m. UTC. Oh, no, I'm not awake at 9 a.m. UTC. So that's no. So that, okay. So let's get that into the notes. 9 o'clock a.m. UTC. So I will volunteer starting about five hours after that, but not right at that time. I need to check. We can organize that. Do we let it, I think it's important, but do we leave it to be natural or do we organize that? Do we have a role? I just tell people try to be available? Yeah, I'm okay if we just leave it natural. I'm not overly worried about it. We've done what we could to announce it. We are certainly not going to change that date. Even if people grumble and complain, we're not changing that date because this transition is quite important to JFrog's sponsorship of the Jenkins project. So even if there are, well, the security team might persuade a change if they had some disaster. But other than that, I don't think there's anybody else who has enough leverage with us to change that date. Yeah. And I heard that a few months ago, I think the system stopped for 24 to 48 hours and the earth didn't stop rotating. So that should go fine. Well, yeah, a good point. This is crucial. It's a critical system for us, but there are still plenty of things to do without it. Yeah. Let's keep the social media watch thing natural and we'll just say, well, if you have spare time, right, make sure that you have a look. And hopefully Jenkins maintainers, Jenkins plug-in maintainers love football. And I think there is something on Sunday. So maybe they will be busy watching TV or listening to the radio. Oh, is it? But we're talking about Saturday. No, no, this is Sunday. Oh, sorry. I know nothing about football. This is Sunday. So World Cup is on Sunday. There's some World Cup matches going on on Sunday. Yeah. The final is happening at 3 p.m. UTC. Okay. So should we consider a little bit of a parody or a joke thing thing? Instead of doing Jenkins development, get ready for the World Cup. Why not? Well, yeah, it depends on what part of the world. Right. Right. Exactly. So whether you're interested, yeah, okay, maybe not. But just for me, the smile part of, okay, watch the World Cup instead of doing Jenkins plug-in development just this once. That's some jokes that can be made about that. Twitter would be a good playground for that. Good. We'll think about that. Anything else regarding Jeff Rock maintenance? No, we already thrown so many ideas there. And we need to be careful that we at least execute one. You're right. But I like that. There is no such thing as too many ideas, except when you have timing constraints. Next topic then, first them once again. So it's 4 and 5 February 2023, I guess, in Brussels. And the first them Stan has been approved by the organizer. I think Stan is a big word for just a small table. But that's fine. We were pretty lucky because we got a stand and half of the people who wanted to get the table didn't get one. So, yes, Jenkins won the table and we're happy with that. I don't know, as any one of you proposed a talk to first them. I did not know, unfortunately. I don't know if the CFP is closed or not. I think it closed December 5. It closed a little earlier here. I think it is closed. So still an action item for Alisa this time. She will prepare a planning doc to see who will be at the stand when and she will share it via community Jenkins IO. Once again, scale 20x. So it has been approved by the organizer. That's fine. So even if we don't have any talk, we'll have a booth, which is better than a table, I guess. I've never seen this one, Mark. How many square meters? Oh, sorry. Yeah, so probably 10 square meters or less. So it's not a huge space. Yeah. Three meter by three. Thank you for us European folks. Three by three. Yeah, that's about 10, right? Nine or 10 meters? Yeah. So square meters. That's nice. And Jean-Marc, you already told us a few words about the CDF Outreach Committee reboot yesterday. So can you share some more things with us? It was an interesting meeting. Quite a lot of projects attended. They have various experience in outreach. So people were interested, for instance, in our GSOC experience. Some good ideas, a lot of good will at that meeting. There will be follow-ups. So on this, my personal takeaway, Mark, do you have others? Agreed. Yeah, so there will be later sessions. It's a challenge for CDF. They've got a very wide range of things, right? They've got very young, brand new projects with relatively small groups. And then they've got these behemoths like Jenkins and Tecton where, and they've got to span the needs of both those things, the large projects and the newly born projects that are just getting started. Good. They did announce... Yeah, they announced CDCon. Go ahead, Mark. That's all I was going to say is they announced CDCon. I hope, I did want to ask here, are people generally okay that I posted the content of that email message to community.jankens.io? I got that. I didn't see an easy way to make it as good looking as the message was, but I thought, you know what, other people in Jenkins community may care. Was that okay with people generally? For me personally, yes. Okay, great. Why didn't I think it before, but so you were faster with that idea and I think it's worthwhile information to circulate. So, Mark, how different is it from the CDCon we had in Austin, Texas this year? It's the very same thing or is it somehow different? I think it will be very similar. The one improvement they're trying to make this year is last year they made the mistake of having two conferences, but they spanned a weekend and because they spanned a weekend, people left and then had to come back for the second conference. And they said, that's nonsense. We're going to do a single week. In that single week, we'll start the week with one conference and finish the week with the other conference so that people who want to attend both travel for a week without spanning a weekend. So I think that's very wise of them. They've also chosen a nice venue. Vancouver, Canada is a lovely place and may the weather will be mostly okay in Vancouver. No more snow, maybe. Oh, Vancouver hardly ever gets. Vancouver is right on the Pacific Coast. It's on the Pacific Coast. Yeah, you'll have rain always and you just accept rain, right? That's the life there. And they're going probably to make some smaller events in Europe, in Asia. Oh, nice. Okay, it's good. So there was one, I don't know where I wrote that down. The one I spotted was in September, around September in Bilbao. And then during the winter, I think it's Japan or something like that. Nice. Great. Cool. Then I can't remember if you already read that, but yes, CDF sent a brief communication to find more ambassadors. No, more mentors through their ambassadors. So no feedback. Yeah, this is what I raised during my GSOC briefing. And so this is the exchange that happened during my night. Now, the CDF ambassadors are a wider-ranging group than Jenkins contributors, right? So I don't recall that there are many Jenkins active people. I think Oleg Nanashiv is a CDF ambassador, but I'm not aware of any others that I would call active in Jenkins. So I don't know, though, I haven't read their exact list of ambassadors. We don't know. We might be lucky in knowing that some of the projects are not 100% specific to Jenkins, like the static site generator and these kind of things, which is, although Chris already volunteered as a mentor for that one. So we'll see what comes if we wouldn't have done it in us for their feedback or help we would have regretted it. Of course. I don't know the term in American English, but we try to reach everybody. Yeah, it's not a trap. If you don't know, that's perfect. I don't know either. We use all the means. All available means. I don't know how you can translate that expression, but it's still a French idiom by a French idiot. Anyhow, does anyone have any other question we mark subject he would want to be addressed today? Kevin, Chris, Mark, Mark. Nothing for me. Oh, that looks like a wrap. We're done. And this was the last one for 2022. There won't be any meeting on December 29. So happy holidays to everyone of you if you have a holiday, of course. The recording should be available in 24 to 48 hours. So enjoy and see you next year. Thanks a lot for your time. Okay. Bye. Bye, everybody. Bye. Have a nice day.