 Hello, Alissa. Hi, Mark. How are you? I'm good. How are you? Just fine. So let me get some notes started here. Just you and I today. It may just be you and me. And if so, we'll just remind me that I'm behind schedule. I'll give you a brief status report on some things that Darren Pope and I have been doing that seem to be generating really positive interest. But it's, and it's good to talk about those, I think, because that way you're aware what we're doing and why we're doing it and etc. I suspect Oleg's unavailable because he's probably taken care of his little boy. Yeah. All right, let's see. So, October. Oh, I know what I wanted to put on the agenda. It was adopt a plug in adopt a plug in initiative. Mark, and that would be live streams with Darren Pope. Yeah, I'll just put, let me put it up and we'll start the meeting. And then I assume, is there anything you wanted on the agenda for DevOps world, any summary you want to give there more details anything like that. Yeah, we can do a quick recap. All right, so DevOps world, Alyssa contributors summit October to me October nine me, Hacktoberfest progress report. That's a good one to talk to. I think that's okay good. So I think I have a draft agenda. I'm going to start sharing my screen. And then I will turn on the recording. So I think we're already recording it's for me it says recording. Oh good. All right, we are already recording very good so we're we've already got it. Okay, share my screen. So I think one thing we might want to talk about is so planning for the last quarter of the year I know that we have foster that's going to be towards the tail end. Well, beginning of next year. And I, I need to fine tune my budget for q4. So if there's anything that we want to contribute to, you know, or be part of that involves some budgeting, then let's discuss that, and so that I can make sure to put aside money for it. All right, well and so one topic for me there is possible Hacktoberfest swag or adopt a plug in swag I realized today as I was thinking more about this that we might get better retention for our for people who adopt a plug in if we sent them a T shirt. Then take a picture of they got the T shirt and because adopt a plug in is actually quite a bit more effort. Hacktoberfest swag it may be good enough to mail email or physically mail them a sticker, but but the adopt a plug in they're really signing up for to help us in a bigger way. Okay. All right so let's, we got that their upcoming events and planning. All right, anything else, anything else you want to put on the agenda. No, I think that's it. Okay, so what I'm going to do is share my screen and we'll look at the agenda and take notes there. All right, so here we go. All right, can you see the screen okay. Yes. Super. All right so first topic was this adopt a plug in initiative. Thanks to the DevOps world funding of fun DevOps world and so basically I say it differently cloud these funded me to develop a workshop. The contributing to open source workshop. Yeah. And we're reusing that. And we're reusing it. We're using extending. Etc. and the extensions are. We've done two live streams already a series of live streams of one hour live streams with their and Pope. Showing people how easy it is to adopt a plug in. for www.jenkins.io with Diraj Joda. So Diraj Singh Joda has agreed to help create that tutorial. So and me. And we'll actually embed Darren's videos into those tutorials. So not only will we have tutorial steps on how you can very easily adopt a plugin, help it in a way that actually matters, but also here's a video showing you how we did it for a sample. Okay. And I'm delighted to share that Mads Jacobson has adopted a plugin as a result of that effort. Oh, nice. So we've got one example of success. Yeah. And one is much better than zero. Absolutely. Okay. You want to share a DevOps world status? Sure. So DevOps world had a total of 18,000 registrants. I'm trying, I'm going through some of the data's right now. We had, most of the registrants came from the US, India and Europe. What else can I share? And most were in software and technology. They were practitioners as such. How did the community do? Let's see. We had sessions. Sorry. There's like a deck that was sent to me and I'm scrolling through it. So one of the sessions that did really well was called from big and slow to small and agile, splitting monolith Jenkins controllers for increased performance. I don't have the data of who is the speaker for that. That was, what's his name? Here in Colorado. That's really embarrassing. I've worked with him. I'll have to look it up. But yeah, that's... That did really well. Dylan, Dylan. Dylan Durst. Oh, okay. Got it. Yeah. 100 deploys a day, five steps to success. That was the next one that did well. DevOps culture at AWS. Was the third one that did well. Digital evolution of migration. And the last, so the last one that did well, this is like the top one, two, four, five sessions that did well was managing multiple Jenkins instances at code. And these were the ones that did well during the live sessions. Great. Good. Okay. We also got some really good data with regards to the number of attendees for the community track. Enabling finance grade DevOps, automated governance and audit that did well within the community track. Speeding up Jenkins and Maven with build cache. Optimizing continuous delivery pipelines is another hot topic. Visualizing Git forensic data in a Jenkins plugin. Oh, good. Uli's presentation. Yeah, that was on the list of the top four. Great. Yeah. I can send you this list if you like, Mark, but it's, I mean, it's great. We had 23 sessions total for the community. And I'm glad that there were lots of, it shows me that there's still lots of interest for Jenkins. So that's good. Excellent. Yeah. I don't have data on the workshop. So I will request for that data. No, no, no worry there. The workshop itself, at least my workshop was tiny. We had a total of seven participants and that's fine. We got enough value out of the exercise of creating it and the interactions with the people who were involved who attended that it was very, very worthwhile. It had been worthwhile if there'd only been one attendee. We were getting so much additional value out of it. Right. Other workshops I can't talk to, but the workshop I ran, it was a great success, not because of the number of people that attended, but because of the results we got from the workshop. Excellent. Excellent. And that's what we wanted. Right. Yeah, that's it that I have for DevOps World. Okay. And then, so Contributor Summit, we hosted the Contributor Summit October 2nd associated with DevOps World and it was a Hacktoberfest launch. So what we did is we had three presenters that shared how to approach different ways of contributing to four different ways to contribute to Jenkins. And so there was, let's see, there was migrating docs to GitHub that I presented. There was improving the UI presented by Oricofner improving better securing JavaScript in Jenkins with content security policy. And that was Vadek, follow me. And then I did one on some other topic. I'm sorry, I forgot what topic it was. I'll have to look at the notes. But those four different things that we had 20, what was it? 25 plus attendees. And then for the Contributor Summit on the 9th, we had, I believe it was 45 plus attendees and project update was presented. And Oleg led sessions on Jenkins file runs. And Oricofner and on several others, several other topics. So both were good experiments. That's the attendance is about what we got at other Contributor summits, but we got a different audience this time. So it was very much a strong audience from India, some attendees from China. And so very pleased that we reached Asia like we hope we would. Nice. Well, and this aligns with the interest that we're seeing at DevOps World because there's a lot of interest from India. Right, exactly. So that's great. And we should continue encouraging contributions from people in India and Africa. That's those are great places and great places for us to welcome their help. All right. Let's see, next topic for me or any questions or comments on Contributor Summit? No. Okay, next topic was Hacktoberfest. And there we've got strong progress marked to create a blog post highlighting some of the areas. And I've got to show you one of them. You should just be charmed as can be by this one. Look at the artwork we received. Here we go. Look at this. Do you see Duchess France? Yes, yes. Yes. That's our first female. Exactly. So we have a logo and that. So that for me is that's brilliant. We've wanted for years to get a logo, a female logo and there we've got it. So we've also got, let's see. So Duchess France contributed logo. We've had French localization improvements. Nice. And from multiple authors, multiple contributors, we've had, I think we're now at 15 plus plugins migrating their documentation to GitHub. So that thing that I launched at the first Octoberfest session at the contributor summit on October 2nd has borne fruit and we've got several plugins that are making the transition. So special thanks to contributors there and more work to be done. Are these the ones that's mostly being contributed by folks within CloudBees? No, no, well, no, actually. So the Duchess France one is outside CloudBees. Right. The French localization improvements is a hybrid between CloudBees people and non-CloudBees people. And the 15 plugins migrating their documentation is also a mix. We've got one strong CloudBees contributor and we've got three or four non-CloudBees contributors that have been working on that particular set of things. Great. So it's a good mix of all sorts of people from all sorts of places. Cool, okay. And then I know that what Deck is working on the or somebody else is working on the t-shirt design for the Octoberfest, but that's, I believe that's within CloudBees, Mark. Oh, yeah, see, I haven't heard anything about any attempt to do swag to people who were Octoberfest contributors or anything as big as a t-shirt anyway to Octoberfest contributors. If you've got funds for that, we could certainly consider it, but I was not, I was assuming we needed to keep this one less expensive. Right, well, I do have funds for that and I am planning to at least do, according to what Deck, at least 40 t-shirts. I love the design. It's got the bees and the CloudBees and Octoberfest since we can't use the Octoberfest logo, but if we want to give these t-shirts to external to non-bees, then yeah, I would love to know it so that I can make sure that we send them some and that's what we decide to do. Okay, so that's a, and that's, maybe that's a conversation I need to have with Vodek to see how he, I'll talk internally at CloudBees about that, discuss with Vodek. So you've got funds for up to 40 shipments of shirts, custom shirts as designed by Vodek. I can do more if we need to. Yeah. Oh, okay, all right. All right, the reason I ask is, for instance, I would love to get a shirt to a Octoberfest thank you shirt to some of our contributors on these docs migration things. It's great that they've done it and the localization improvements very much so would be a great way to send them a thank you. Absolutely, yeah. Yeah, and well, this kind of leads to the next question that I have. It's not related to Octoberfest, but well, probably a couple of months ago we had talked about doing a Jenkins fleece. Oh, all right, right. And so let's, yeah. And I, well, at least I know the governance. There's a lot of people that are contributing their time. People like Uli, right? Who contribute so much of their time to the project and has been around with the project for so long. I'd like to also send them a thank you for something warm and fuzzy. Right. So if we want to develop a list for that for this quarter, for Q4, Mark, I'd be happy to send them something. All right, okay. Well, so let me, let me, so, well, let's talk about what criteria we might use there. So significant contributors, significant contributions would be a great thing. And so there I can already call out several, but I think of, okay, Tim Jacome, Oricofner, Gavin Mogan. Yeah. In my case, he's been at Konechny, Konechny. And I'm missing all the accents in his, oh, like Ninashev, yes, absolutely. Oh my God. What is her name? Oh my God. Evelina. Yes, thank you. Evelina, okay, Vilcos, WIK, yes, I think like that. Yeah. Okay. And then, oh, Olivia Venin, Damien DuPortal. So these are. Mark, wait. Okay, yes, Mark, wait, absolutely. Yes, yes, absolutely. Sure, why not? Okay, so, but I think that's already a great, a great way of telling them, hey, thank you. And what an opportunity to say thanks to them. How about giving, let's give it up to a week to think about others. I need to be sure that I'm looking for more of those voices because this is just an immediate quick run through, not as much a, oh yeah, here's this, this and this. Yeah, so we do have time as long as I set aside appropriate amount for it, we would be good. So let's circle back. Let's give this a couple of weeks, Mark. All right. And then I'll send a reminder for me and then we can talk more about it in a, say a couple of weeks, because I know we will probably need some time to think about it. All right. And I'll actually, so what I'll do for the list that we have right now, so I'll start this list on a document and I'll start collecting their addresses. Okay, great. And then we can continue to add to that list once we think of more. I'm sure there's more and it's fine to have more people. Absolutely, that sounds great to me. So I'm gonna put this one earlier. I still wanted to spend some of your time to talk about the Hacktoberfest swag topic just to be sure that you and I are aligned there. Okay, so the fleece sweatshirt sounds really great, absolutely. Good. Okay, then in terms of the next one, I would love to have an excuse to say thanks to people who are willing to adopt a plug-in. Can we, can your budget stand? Jenkins is the way T-shirt. Let's assume we get 20 people that adopt plug-ins between now and end of the year. Yes. Okay, all right. Up to 20, good. I would love to have 20. I don't know that I'll get 20. We've got one right now and I hope for more. Okay. And then on the Hacktoberfest swag, there because of the worldwide nature of it, I was assuming we don't want the added cost and shipping challenges of sending t-shirts all around the world. Would it work for us to just do Jenkins stickers, that sticker or two in a regular size envelope? And I'm happy to be the one who does the sending. I'm willing to lick envelopes and post stamps kind of thing. Hacktoberfest. So we have been sending t-shirts out for, we have been continuing to do it. Okay, even internationally. Yes. My only beg is that they give me the correct address. Oh, good luck with that. The challenge, and so we can say upfront, if you don't give us to correct your address, correct phone number, you're not gonna get one. So basically I send this list to my vendor, they send the list to FedEx. And FedEx comes back and say, some of these addresses are bogus, they're not correct. And I end up, so then it falls back on my lap. I end up chasing after these folks and I'm finding that I don't have the bandwidth for it and the browse is dropping there. So that's my only beg is that if it's your correct address, we'll send you something. But if you don't, then it's not gonna make it there. And I'm not gonna follow up. No, yeah, so that's a good one. So no follow up if you give us a bad address. Yeah. I mean, even just one number is off, Mark, it's... Right, well, and I understand why you can say, I'm sorry, if FedEx says this is not a valid address, there is nothing we can do to fix it. We can't afford the personal time cost to do that. Right. Great, okay. So that's a must, give us correct information. All right, well, so that's cool that if we're willing to send a t-shirt. So that Mark or others can collect names and addresses and names, addresses and phone numbers, right? You've gotta have... I need the phone number. Just that's not for me to call them, but it's for FedEx in case they get lost. Right, well, and they are free to choose not to share that. And if they choose not to share it, that means they choose not to receive the swag. Right. That's perfectly fine. We certainly don't require that kind of thing from someone if they would rather not share it, that is their right, we don't mind. Yeah. Okay. And how many t-shirts would you do anticipate for this October Fest? Looking at the current pattern, so we're at the 21st of the month, we're 10 days away from done, and I would guess we've already got 30 or 40 participants that I can identify. Okay. So I would guess double that. All right, doable. And if we assume 60 participants eligible, probably 10 to 20% of them choose not to, so we're still at 50. And that's workable on your budget. Yeah. Okay, great. All right, excellent. That's great, okay. So the next related topic to this, Mark, is the design for the t-shirt. Are we using the one that Wodeck and team created? And that I've got to understand what, if his design is prefer Wodeck's design, if it's not CloudB specific. And that I don't know if it is, so that was- Wodeck's design is CloudB specific. Ah, okay, all right. It's very cute, it's very cute, but it's green, it's CloudB. So, well, so maybe again, that's a great way to say, hey, look, this is CloudB saying thank you. Yeah, that's completely fine. So why not? Let me check with Wodeck to see if Mark checked with Wodeck if he's okay with that. Yeah. Confirm with Wodeck that we may reuse it for people that are not at CloudB's. And I guess whether the recipients would be okay to be- Actually, if they are not okay with it, we assume they'll discard it. I'm not worried about that. Okay. Someone's saying I don't want a t-shirt, no problem. Got it. Okay, so prefer Wodeck's design and we acknowledge that it includes CloudB's, that it is CloudB's theme. Great, yeah, excellent, okay. All right, any, let's see, I had Fosdom here as a topic as well. Is that a- Yes, please, let's talk about that. Okay, good. So my working assumption right now is it's still undecided if it will be a physical event. Right. I'm hoping it is because I am really desperately wanting to go to a physical conference and see human beings. Agreed, agreed. Yeah, I've been checking their website so far this week. I've checked like three times a week, but it seems like they haven't really decided for 2022, but it seems like 2023 will be in person. I think that is more, there's more assurance there than 2022. Okay. Yeah. Great, so in terms of our involvement at Fosdom, there will be, I believe, there's plans still for a CI CD dev room, just as there have been in past years. Olivier is likely to be one of the coordinators again for that. Oh, great. And so we probably want to be proposing talks Yes. For that dev room. Now, if I remember correctly, last time they did have booths. But it wasn't very active, if I recall correctly. And that is consistent to like DevOps world as well. Right, yep. I wonder could we use some swag technique to increase traffic? I don't know what it would be. You know, do we offer a sticker? Come to us, ask five questions and we'll physically mail you a sticker, something like that. Yeah. Yeah. We can put that down as- At least for discussion, right? Yeah. We certainly use it when we're physically on site, right? Definitely. Come talk to us at the booth. Ask me a good question. I'll give you a sticker. Yeah. Yeah. We can do that. Okay. But scale for sure will be in person. And that's early March. So let's make a note of that one. That's a good one. Scale. And that's probably now, I don't know what number they're at. Early March. Do you mean the date? No, no, they've got a number they associate. In fact, I had a scale shoot on earlier today. March of 2022 in-person conference in Pasadena. Is that where it is? Yes, yes. Okay. Great. All right. Plan to travel there. Booth Jenkins Booth on site. And is that one where we want to attempt the workshop? Or are they allowing workshops? I think they are. I have not looked into details, but I think they are, Mark. And yeah, if you just let me know whether we want to do that again, what the workshop would be about, I'm assuming pipeline still? Yeah. And that's, I think there are two choices, right? We could attempt a contributing to open source. The problem is that one assumes, I would expect low attendance, whereas Jenkins pipeline, people say, oh yeah, I've got to use that. So we may want to just do a Jenkins pipeline variation. Okay. All right, I'll look into that for a training room. Okay. And then I'll set budget for that too. Great. All right. And let me just put Jenkins pipeline as the preferred, because just as I think about it, persuading is going to an open source conference and inviting people to contribute is a nice delusional attempt, right? It's a nice way to think, gee, yeah, people will be, no, they're there to learn and to grow. And if they want to contribute, we need to find other ways to get to them. Yeah. So this, so this, the March 2022, that will be 19X scale and 19X. Oh, thank you. Good. Okay. All right. Excellent. Okay. All right. And I should put for CA, California. That's right. There we go. So I heard, so KubeCon took place, I think it was last week in LA, Mark. Right. And I heard that there wasn't a lot of people in attendance. There was a lot of social distancing. So that means even the boots are social distanced. Oh, okay. All right. Yeah. So getting, they said, getting from one booth to another was quite a walk. Oh dear. Okay. Just getting to anything is quite a walk. Right. Yeah. And so that means the impact to that is less leads were able, were being scanned and just a lot of less people, you had to be vaccinated or shown negative test result. Yeah. But yeah, I thought that was interesting. The booth were also social distanced. Yeah. Well, and understandably. So KubeCon, KubeCon last week, low physical attendance. Yeah. And that's the complication of welcome to COVID-19, right? Right. Okay. Right. So I think, I think for us to, at least for me, it's good to have that kind of information in mind. And I'm thinking as we go into more in person events, just expect a gradual growth. Not, it won't be the same as it was before. Right. Yeah. Okay. Good. Anything else we need to discuss on those upcoming conferences? I think that's it for us, for me. Okay. Let's call it good then. Thanks, Alyssa. Thank you, Mark. Take care. See ya. Bye.