 Great. Okay, hello everybody and welcome to this Jenkins advocacy and outreach meeting. So good to have you, Mark Mocchi and welcome Summit. So I think we can start with maybe looking back at any actions we have and let me see if I can share the agenda, share my screen here. So if folks do have specific agenda items which you'd like to discuss, please let me know. Otherwise, Alyssa has gone ahead and put one item in there but I'm not sure she's able to attend and yet we'll go ahead and look at past actions. So first of all, any pressing issues people would like to use this time to discuss or focus on? I don't have a pressing issue. I do have an update on two items. They can go at the end or I can do them now, whichever. What are the topics? The first topic is in regards to the documentation for describing the voucher use and distribution. I have not completed that. That is on my list to do. Work has just drowned me a little bit this week. And secondly, there is a CDF ambassador update that I thought I'd just update the team about. Oh, actually I have stuff on CDF ambassador too. So let's put that as a big topic and I've noted sorry, I'm not writing this. Okay, so that action is still to do. So Jackie, create a tracking sheet. I think that one was done. Yes, that is done. And then this one is still to do. That's fine. The zoom accounts, I'll put a note that I have done some, it's kind of done in a to do, let's say ongoing a Tracy highlighted zoom problem still working with CDF to get solution. And we'll say Mark to provide stuck up meeting, which only works until Mark can attend a meeting, I guess. So Mark will always be there, right? I'm just looking for other to do's and GSOC, I believe the Jenkins X GSOC, this action here was resolved. This item here Marky, was that done update status of Jenkins X projects or is that still to do? Nope, that's completed. And yeah, I understand there was a discussion last Friday and things are resolved and it's all very positive. And actually, we've got a bunch of people stepping forward to be support mentors. So that's good. Okay, I'm going to leave that there for to do certainly the ones I could pick out easily. Okay, so let's go on to the topic of CDF ambassadors. And Marky, why don't you do your update and then I'll go ahead and share what I know. Yes. So I would like to let everybody know that I have officially become an ambassador. And I believe if we go to CDF foundation, we have, I think I've seen you. Yep. I believe there will be a blog post coming out. I know the CDF media marketing team is working on that. I've already sent them a draft. And yeah, congratulations. And I think for one, I'll say that I think you will be an amazing ambassador for the Jenkins project and for CDF. Thank you very, very much. I appreciate that. Very lucky to have you. There will also be a, on April 17th, there will be the first, as an ambassador, one of the things you do is meetups. And we will be doing a meetup on April 17th, where I will be presenting Jenkins on Kubernetes. Oh, sorry. So April 17th, you're doing a Jenkins on Kubernetes meetup. Perfect. So just going back to the ambassador program, I believe there was also a review of the CDF program. We, Jack invited a number of project folks from Spinnaker and screwdriver and Jenkins and other projects to just review the outline for the ambassador program. One of the things that will come out of that is we'll have a GitHub repository set up similar to CNCF, which will outline the process for ambassadors, you know, how often they do them, which people they're looking for, all the kind of nitty gritty process around that. Just writing some notes. And the other thing we talked about was making sure that this ambassador program run by CDF is becomes the successor to the Jenkins ambassador program. And specifically, we sort of said, you know, if any project from the CDF ambassadors from the whole pool, if there's a subgroup of those people who we consider experts in Jenkins, then that list of people would go to the Jenkins board. They would give a thumbs up and then sort of anoint them with the Jenkins status as such. And then they would have special benefits, perhaps in the Jenkins community, which would be being invited to specific meetings or when we go back to having events, trying to get them passes or discounts or whatever in inviting them as speakers. So it would just be like an extra level. And then similarly, you could do the same for Tecton or you could do the same for Spinnaker, you know, they'd invite you to their meetings and they just get you more and more involved and give you special status in those communities. So I think the next action there is to get that list from CDF to the Jenkins board and just have them officially sort of say, this is good, and then just communicate to the Jenkins community. Hey, remember that ambassador program? This is now the set of Jenkins ambassadors and maybe we could do some publicity around that, some blog posts or yeah, some tweets. So what do folks think about any communication we need to do on that front? I definitely think we should have a blog post that maybe it doesn't have to be a full blog post, but something that links to the CDF's announcement for the ambassadors. And then we could have sort of the same tweet campaign doing the same thing. Okay. Okay. Yeah, that sounds good. So let's leave this as an ongoing topic for these meetings. Let's say the next step is I'm working with Jackie and the project outreach at CDF to get some of the repos and some more things set up. And then maybe in a couple of weeks, there should be enough sort of public links and things that we can then put together that blog post and just talk about how this is going to be the new program. Excellent. Great. Okay. Anything else on ambassadors from anybody? I did have one actual thing for the ambassadors in, when you had said it during our last meeting, Tracy, something about a May ML Ops communication that would be good to sort of come from the ambassadors. If you have any more information about that. Yeah, so I can show you what's there now. So there's a repo. And it is at the moment, we're still focused on the newsletter. I don't think we've broken that out into more things. So that's still the intention. But the newsletter page here captures the topics. So actually this month, we bumped the names of the month. So this month in April, we're collecting interoperability that will effectively be the May topic. And then during May, we're collecting people who can speak or write about ML Ops. So that gets published at the end of May. And that will be the June topic as such. Beautiful. I will start getting working on that if you'd like me to take that up. Yes, I would very much so. So if you, like a very beginning thing, propose a talk on something ML Ops and Jenkins. And then we can start also pulling, deciding, I think Jackie's trying to pull together a webinar, or a crowd chat, which would be a set of experts or kind of people who could lead, sorry, not experts, actually the opposite of experts, but knowledgeable folks who could lead a discussion and engage people to do some peer to peer sharing. Got it. Okay. So let's see monthly CDF themes. Okay. To drive ML Ops topics. Propose, I'll put down to propose a talk. And sorry, I cannot talk and type at the same time. Okay. Any thoughts, questions on that summit? Does that all sound good to you? Please feel free to speak up. If you want to ask anything, no question too small. Thanks for coming to okay. So this one, I know Alyssa put it in, but you could not make it to the meeting. So Jenkins comic strip. She asked for a general feedback to initial ideas. So I don't know if folks have had a chance to look at this. Maybe we could do so quickly now. And if you have any thoughts, I can get those back to Alyssa. Is anyone a fan of the Mandalorian? Okay. Right. Particularly your one. Okay. So number one was that you can deploy often. I don't feel qualified to comment how on point these are. I have not had a chance to look at this. That's been an action for all two. Yeah. Action item, all to review and post feedback comments in the doc. And I'll also, I'll ask for feedback in Gitter. And then I think this comic strip idea, Alyssa was kind of open to where we could put it on Jenkins IO. That would make sense. Is that go on the artwork? Does it go on the blog? Do we just have it in tweets? So if anyone has any thoughts, just please let me know. Right. Let's move on to Jenkins roadmap. Mark, do you want to go ahead and take this? Yeah. It was just to say that Oleg has done a brilliant job of this is me being a poor approximation for Oleg summary. He's done a brilliant job of collecting and presenting roadmap ideas here in this draft of the roadmap on Jenkins.io. It's reachable through the governance and structure link at the bottom of the page. One of the pages from that page is the roadmap. So you pick structure and governance under the project column at the very bottom there and structure and governance. It's not yet on the Jumbotron. I think we'd want some more time to refine and evolve it before we highlight that it's to a much broader audience right now. It's just a very, very good working prototype showing evolution and thought processes. We've got lots of people contributing in many different ways. Great. And ultimately the contribution from this SIG falls under this category. Is that right? So all the events. So contributor guidelines, refresh, Google some of code, which is ongoing. So that falls in the current and then near term, Google season of docs, community bridge and later hacktoberfest, which sounds like a fine list off. Yeah. I will say, I think I'm seeing a lot of communities doing lots of figuring out virtual strategies, virtual events and different things we can do there. And one of the things I'll mention again, CDF is looking to drive will be helping all our meetup communities pivot to having virtual events. So both giving them the knowledge of, you know, how would you use it? What are the pros and cons of each platform? And then building on that saying, can we offer them platforms to use for free? So maybe people don't have to pay for them. Can we figure out the zoom thing, make that more accessible or even platforms like Crowdcast? Can we share them in some way? And, you know, just try and help with the heavy lifting so folks can focus on the content and focus on the people. So we might see some more from CDF, I think, either a webinar about it or a general meetup with meetup organizers to do a joint brainstorm and possibly get some folks who are really doing this in a very top notch way to come along and help like with advanced streaming stuff. And I'm hearing like, we're getting into gamer level goodness stuff that we could potentially do that could be pretty exciting. But I went along, I think that cloud native had a recent virtual event and they had some pretty slick things happening there. So yeah, they just did it the day before yesterday. And it was for pivoting from an in-person event. They did a bang up job. Great. Do you know what platform they were using? Was it Zoom? It was Zoom and they used breakout rooms and all kinds of things. The contributor summit is going to be like that. Yeah, that's cool. I'm actually running a social event tomorrow where I'm going to use breakout rooms and that's going to be fun. So I'm going to have a lounge breakout room, a dining room, a kitchen and we're going to put people into chat and stuff. That would be a good experience to see how it goes. Yeah, so anything I think, I don't know if we'll put that into the roadmap, but yeah, just reminded me of that. Any questions, comments on the roadmap? Perfect. And next agenda item is LinkedIn experiment and Mark, this one's take it away. So Oleg reactivated the Jenkins or gained control of the Jenkins LinkedIn account. And as part of that, we decided, hey, let's try an experiment. So I wrote an article on LinkedIn, haven't written one of those, I think in a very long time. And it was inviting people to come help mentor with the get plug in and Google summer of code. The article had 87 views, not a huge volume, but some views and lots of interesting traction on Twitter. Thanks to Oleg's having shared it on LinkedIn. So did I get what I ultimately wanted? No, unfortunately, I haven't yet gotten the extra mentors that I was looking for. But I did raise the awareness of many of my contacts that yes, I'm actively involved in the Jenkins project. And yes, they could help too. Great. Yeah, I think it might be a slow burn on that one. But it's good to hear that there's some engagement, even if not quite spot on for what you needed. Okay. So that reminds me, I'm going to add another item here, which is we talked about the Twitter calendar. I think we had a bit of this in the mailing list. So I had this doc. And I didn't know if we did want to update it to use it as a way to schedule, schedule tweets and in until we get our full kind of docs as tweets, but a way to be aware of what other people are scheduling or wide overlap. But when I had originally planned it, I think I had this idea that, you know, in a buildup to an event or for big news, you might want the tweets to go out three or four times across a couple of months. So I would just copy it and I'd paste it across different dates and say, here, here, here and here. We're going to have that. And then just to make sure other people want doing the same thing, I thought that was a way to avoid clashing. So what do folks think? Do we want to use this? Is it too heavy weight? Should we just? I think I'm a strong plus one for this format. Okay. Any thoughts from anyone else? So, so my problem is I'm, I'm really fine. I'm fine at seeing this, but really terrible at actually actively using and implementing it. It will do me no harm, but I tend rather to periodically just go in and and retweet something from the Jenkins account that I think makes sense or after a discussion. So, so this looks great to me. Unfortunately, my past behavior shows while it looks great, I probably won't do a lot with it. And yeah, yeah, I wouldn't expect people if you're just retweeting really good tweets, I wouldn't expect you to necessarily put them in. But I think this is more, hey, I've got this plan. I want to promote this specific thing like let's say we throw in the roadmap, like how many times we could talk about the roadmap repeatedly. So maybe we think once and we schedule it. Well, and the Jenkins and Kubernetes upcoming webinar that Markey had mentioned is a really good fit for something like that where every three or four days or are with compressed where four or five days, then two days, then one day before actively promoted systematically. Yeah, that's, I think that's a good use for this. I don't think we should change our habits in, in what I think you're saying, Mark, and please correct me if I'm wrong. I don't think we should change our habits in the sense of if we know there's good content or you know, if Mark, you tweet something out that you know is good and you want it to be retweeted from the Jenkins account, I don't think we need to schedule things like that. I think those are definitely good to keep going. And I don't think we've had any problems. So it's not broken. I don't think we need to fix it. I do like the idea of using this for very detailed things such as the meetup that's coming up and the ones that we will be having. Yeah, I think this is good for very large announcements. Yeah, so I agree. And I think that's a nice way to use it. So how about, can I just do a fill on this? I'm going to create this one for the next three months. I encourage folks to go in and put tweets in. But what we could do also is every advocacy and outreach thing, we could do a quick review of it and we could say, hey, all these cool things, let's schedule in tweets. And then so if we are all looking at it at these meetings, then maybe that's just a nice way to get some eyes on it and make sure we're not clashing or we're not kind of just doing anything we shouldn't be with respect to each other. Yeah, I think that's a great idea. Okay, so let's just fill this out all the way through to end of June, which is somewhere around here. So yeah, if anyone wants to go put in tweets and then duplicate them and then you can say whether they've been posted or scheduled, please go ahead and do that. And I might do a few on the roadmap. Yeah, and in the spirit of continuous improvement, let's see how it goes. And if it's working for us, if it inspires us to come up with a better solution. Yeah, I will add the upcoming meetups. Anyone with the link can add it. So that's great. And I think, yeah, this had a nice, we could say what kind of thing it is. So give us a bit of a picture of what we're pushing out. Okay, that is good. So anything else? Anyone? Nothing for me. Yep, I've got nothing. I think that's been more than enough for today. So that's been pretty good. Okay, so let's leave it at that. The next meeting should be in a couple of weeks. Thanks, everybody. I'll see you all online. Thanks. Thanks. Coming. Bye. Bye-bye.