 Hi Jackie, how are you? I'm good. How are you doing? I am doing well. I think Oleg and Mark is just getting off. Another call. So they just signed off. So they probably went to take like a little break, but I think they'll join soon. The agenda has not been updated. Yeah. Okay. Okay. Oh, you know what? I think, um, for DevOps world, let me ask Sasuke, how many submissions will we see for CDF? I've only seen two because I was getting. You might. I got two notifications. Oh, you did. Okay. Yeah. Let me check with Sasuke just to confirm because, um, one for me when I checked yesterday, I had three and she's this morning I checked with her. Like, did I do something wrong? She's like, you have 10. I have 10. Let me check with her. Sorry. Sorry for arriving late. I was running another meeting and I ended on time, but I was a little slow getting here. Hi, Mark. What was your agenda agenda agenda agenda agenda agenda agenda? So what was it? Uh, with that meeting with that webinar. That brown bag. Excellent. So I had not put anything on today's agenda. I, let's, I assume we want to talk briefly about what should be on the agenda. And then let's go. This week. So. I think that's data you can see and I'm not sure I can see it. Yes. Okay. So I was going to put that and just proposed one topic for the agenda contribute on registration status. And then we had talked about CD con last time and it seems like we, we may need more there. Okay. It's on the jumbo Tron. So is it okay if we put CD con on the agenda again for today? Yeah. Yeah. Yeah. Yeah. We're regarding CD con. Unless there's specific things that folks want to know them, you know, happy, happy to answer questions. Yeah. And I think that maybe just to, to be sure it's, it's briefly discussed to see if they're questions for you. Okay. Yeah. Absolutely. All right. And outreach programs. Yeah. I think, okay. And on, yeah, outreach program updates. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. All the time just to be sure I, we know where we are. And. Oh yeah. The DevOps world. Ask me anything of this. I assume you can share a status report for it with us on how that went. If there's a recording of it, right? If there's anything on swag. All right. So I was going to just start sharing my screen and we walk through the agenda. Is that okay? Oh, and I would just go ahead and put where did it. Oh yeah. Okay. Just a minute. Oh, and I should probably start the recording too. Oh, recordings already started. Good. Okay. So big enough to read. And share my screen. Okay. So. Let's see. So on in terms of contributor summit, Jackie. The document is evolving. Number of registrations. Sorry for being quick. So we were just, just forming, forming an agenda. Are there any topics you want to be sure we put on the agenda? We had these sort of four or five. Yeah. So many threats. Maybe one threat, which we could discuss is. The Linux foundation policy on shared channels. Because we hit it two times already. But yeah, I'm not sure whether it's ready to discuss this topic. This is shared slack channels. Yes. Okay. Great. Thanks. All right. So let's. So Jackie, back to you on, on contributor summit last time. I think we had 217 registrations. Has it gone up since then? Do we need to put some additional. Does the project, the Jenkins project need to put some additional emphasis on that. We may have lost Jackie. Hang on. And once the legend is formed. So I don't really think that we need to expedite anything right now. Okay. Great. So we're. Excellent. Next topic then Linux foundation policy on shared slack channels. Oh, like, can you give some background there? I'm not sure I'm, I'm fully, fully informed. Jackie is not around. It doesn't make sense to discuss it right now. Ah, okay. All right. Oh, Jackie, are you there? Hi, can you hear me? Yes. Yeah. I can't hear anything. Okay, so then let's. Okay. I'm going to defer this one, shall we? Well, I need to resolve this question quite fast. So let's take it. Okay. All right. I can't hear you. Yeah, so. Okay, I can hear you now. Sorry. Oh, okay. There we go. Yeah. So, um, the contribute contribute on is at 302 and registration. So I don't think, honestly, I have barely done anything. People just have been finding it on their own anyways, when they sign up for CD con. So, um, if you want to do some extra promotion around it, you're more than welcome to, but I think the caveat is, um, if we get to, do we have a cap? Will we be able to support it? Cause I think using zoom, I think the max is like 500. But also who, you know, TBD on who shows up. Right. Great. Okay. Thank you. So, and since your audio is working, like you want to describe more on the shared Slack channel question. Yeah. So currently we are setting up a joint project together. We sneak and the Linux foundation team. And the desire is to use a public slug so that we could onboard more contributors. So the proposal to sneak that we create a shared channel so that this channel is hosted on the sneak Slack and hands and has infinite history, et cetera. But to map it as a shared channel to the CDF workspace to do that, we need one of, uh, admins to accept the request, which I sent to Jacqueline and Tracy. But yeah, it was three or four days ago and we still kind of get to the infinite response where the, the next foundation would accept that or not. Yeah. So did you see my response? Sorry. I've been traveling. So I've been catching up on stuff. Um, if you sit, I think why my reply was to submit a ticket through the service desk. Nobody reported that. Okay. Um, I'll bring it up to Tracy and to, um, Gail, who's the program manager and she'll help, but she helps with a lot of that operations, um, stuff. So I'll, I'll let them know and see what we can do. Cause honestly I have, um, I don't know what the, on the Linux foundation side, uh, if, if that they're going to allow us to do that, that's why I need to understand what that, um, path of, of permission request looks like. So, um, yeah. TBD on that. Yeah. It's just clicking on the link and clicking yes when you're admin. Yeah, I understand that, but I don't know if that's something Tracy wants to do. And also if the Linux foundation is going to have an issue about it. So I need to ask for, for permission. Um, if, if that doesn't work, do we do this? Slared shared Slack channel somewhere else. Or I mean the, what's the alternative if we can't do it there? I don't know. But like I said, let me, let me just ask for permission. Cause like I said, I don't know if there's, I don't think there should be, but I just don't know the rules. So that's why I just want to ask. Yeah. So I was, I was asking Oleg to see, are there alternatives if we don't do it that way? And what's the timing? Is this a matter of a day or two? And then we need to have a channel established or is it more like a week? Do you have a sense of it, Oleg? So for us, it would be rather preferable to do it quickly. Because basically this team was already waiting for us to coordinate and we lose time. Okay. Thanks. Great. All right. So Jackie, it sounds like you've got the action item and thanks very much for doing that. Jackie, you mentioned not much, not much to talk to on CD con, anything that comes to mind or from others on as a CD con topic or just on track. Yeah, no, we're pretty healthy with CD con. We actually are officially sold out of all of our tiers with the exception of end user and startup. So that's really exciting. And then like I said, the registration for the contribute contribute fund is really healthy. So I know that we had set at least a target of 250 and we've been able to surpass that. So that's, that's doing well. I think the next thing we'll do is Roxanne's just working on some blogs. So any content that we have around the contribute fund, please, you know, send it over the fence and we'll make sure that that gets published. Great. All right, then Oleg, I put terminology updates. Is there anything you wanted to share to this group? I can repeat what we had at the yesterday's governance meeting. So we agreed on some terms for some entities of the Jenkins controller, because even if we agreed on the controller term and formally approved it in August last year, we still have terms for example, Jenkins master node or Jenkins master port, which appears sometimes in the documentation and the web UI. And we needed to clean them up. So it was a long-standing action item, basically as a part of advocacy and outreach seek. We started this effort last spring. So finally, I just took it over in order to get it over the line. So we haven't agreed on all terms listed, but we agreed on the critical terms, which were blocking contributors who are currently working on the technology. So there is a long discussion with the developer manager, so we finalized something like seven terms and we are more to come. Our main problem is that we still need a lot of contributions to clean it up. So like we did in previous years, it should be rather a dedicated program to that. Maybe October 1st or other when it's on Schwag. But yeah, right now it's a question of when would we need it because everyone is busy until the end of JSOC at least. And it also, yeah, budget projects applied because we're doing logistics for Schwag business fund. Thanks. All right. Anything that we need to do update wise on outreach programs? Alissa, anything? Oh, JSOC, yes. Yeah, so for JSOC yesterday we received a number of slots. I can just, well, I can send this close to the number and the acceptance projects. But yeah, basically we did, we got the minimum slots number we asked for. We are currently mapping projects and we are able to say that we will have JSOC projects this year. The exact projects that we announced on May 17th. We're still forming some mentor teams, but yeah, I'm confident that everything is okay there. Speaking of that, I just want to try to share email as soon as possible. Okay, other outreach related to other updates. So yesterday I was invited to join the open source design meeting because there were some discussions about potential joint programs. So, well, it was a nice meeting. Basically they do monthly meetings similar to how our Jenkins governance meeting worked. We discussed the peer opportunities, shared experiences. Right now, no immediate action items, but yeah, the Jenkins community is welcome to post their design projects and also various requests like creating stickers on the open source design website. They get hundreds of views per day, these pages, and there are many active projects. So currently they're working on, well, republishing some of the initiatives on the job board of an open source design, but we definitely can post some of our efforts. And we do have some, because for example we just had a design, some design projects like pornography updates, which was told by now and it will be great to renew them. Plus, yeah, some communities still need logos. Yeah, I've been leading Jenkins through meetups since 2015 and we still don't have a logo for Jenkins through, for example, we only have logos for 16 meetups. So such activities could be submitted there. Same, for example, for conference logos, if you, for example, the app will contribute some of that silicone. If somebody has a piece, we still have time to create logos and maybe produce some custom swag. They'll be delivering them with a nightmare. So probably it will be printed on your own. So, like I had a flawed perception I think of the notion of open source design. So in this case, it's not just the design of web pages, it's any graphical element. They do logo design, they do... Yeah, so basically it's a community, whatever about design. And when we were doing productions because there were many new camera contributors, everyone talked about their design experience. There were many PhDs in design. And yeah, I was also happy to say that I'm a PhD in design. The problem is that it's a hardware design, but generally, yeah, they do whatever design. So the community is like basically by a few consultants who work on design projects. Also people who contribute to artwork. And the job support also includes multiple kinds of design work. So for example, if you wanted to hire somebody to work on a community, on an effects mentorship like project but for design, you could also post it on the open source design as paid offering. Because they support gratis and paid, but yeah. Okay, so it's not just all gratis. It really is that we could bring Jenkins Project funds to the open source design community, and they would then... We discussed that. So basically, they do have a concept of small bonuses. So for example, like freedom sponsors and other such sites do when you resolve an issue and get $50, $100 or so. And many design freelancing sites all separate like that. For example, create logo with 50 bucks. They don't have that. They either have gratis or they rather expect it to be a major thing. And they kind of offer to start the thread in their discourse channel to discuss the idea of small monetary bonuses because they find it interesting, but they haven't discussed that before. Thanks. Okay. So yeah, maybe I'll have a better summary for the next user experience seek meeting. Yeah, now basically that's what I've got. Excellent. Yeah, they're also interested in various outreach programs, though they don't have much of their own budget. I would say their budget is comparable to Jenkins one, but yeah, in our case, we mostly exist thanks to sponsorships. So yeah, they're basically interested in various, if you want to organize anything like a joint activity, for example, let's say another Jenkins UI UX hackathon, but with more emphasis on design this time, it could be a good opportunity. Ah, right. Okay. So that focuses on, focuses more on design than on, got it. Thanks. Alyssa, anything that you wanted to share there on Jenkins is the way or other efforts that you've got going on an outreach? Yeah, so Jenkins is the way we're, we're still writing stories. We are still receiving stories from the community. We did get a couple of stories from IBM, which we will be pulling together to create and a dedicated IBM red slash red hat. Book or ebook. So we're working on that. That's for Jenkins is the way, and then another project that I'm embarking on is the, and you guys all know this, which is the Jenkins education outreach. So I'm working on, creating a plan on how we want to approach this initiative. I will share it with the, with this group as, with the SIG as soon as I have things that I can share. But the goal is to get Jenkins awareness and visibility, visibility with the, with the, with the, with the Jenkins awareness and visibility, visibility within the education system, like the colleges and stuff. So that's, that's, that's what I have for right now with regards to the Jenkins outreach initiative. Thanks. And then DevOps world, the call for proposals, ask me anything meetup. So Oleg you and Alyssa hosted that recording is available. Any insights you'd like to share there on. Yeah, one thing before we move on. Oh, yes. The way. So I asked you somewhere in the chat, Alyssa, but yeah, there are some big labels in stories. So IBM, Red Heart, Apple. So can we put them on the list of adopters now. So if they explicitly confirm to that, we can use their logos so that we don't repeat stories with other companies like we had before. Can we go ahead and add them. Let me check with them again, just to make sure I'm doing my due diligence, but when we do, when they fill out the form, we do ask them that, you know, we're going to be using your logo. Are we allowed to use your logo? And if yes, these are the certain places that we will, we're planning to use the logo like Jenkins.io, possibly CDF, you know, via tweet and possibly via cloudbeast.com. So if they put Chuck, yes, then that's how we go ahead and we, we use their logo on the, the, the, the user story or the case study. But let me just, just to run this by them one more time, just to make sure. Yeah, I think that would be possible to it. Jenkins.io to the list of approvals. It would be also great. Jenkins. Yeah. Oh yeah. Yeah. Oh, definitely. Yeah. Jenkins.io. And I thought she had said it was already on, on the approval list. Oh, yeah. Yeah. For sure. Jenkins.io. That's my number one. That's where, you know, we, we want to, where we, it's kind of like the home where we want to promote these stories. Yeah. So I'll let me get back to you. Okay. I like. Thank you. And yeah, one, but it's a long shot by now. We might try to run a documentation outreach program. Yeah, you know, Tom, but the G spoke completes because we see we haven't been as up to Google season of dogs. But yeah, there is a consensus that would be nice to have something about documentation. We have a lot of stories and from there. We have some budget. So in principle, we can run one or two. LFX mentorship programs in autumn. If somebody has ideas, etc. You can start the discussions. Right. And then back to our DevOps world. Ask me anything meetup. Thanks very much for running that Oleg. Thanks, Alyssa. So mostly a question and answer session is that was that the sense we've got a recording of it, the recordings available. We've got slides. Yeah, so it was firstly overview of the community agenda. And the second day call for purpose overview and ask me anything. So this session could be somehow repurposed later for community events, promotion, etc. Some additional work would be needed, but we can use this materials. And we've got quite a number of questions. These questions also recorded. So anyone can go and take a look at them. I'm not sure whether we would be doing a transcript of these questions. So maybe if Alyssa has somewhere in white for that. So for example, doing transcript publishing for the kind of blog post. But yeah, I definitely don't have been wet for that. So the idea there was questions and their answers as a blog post. So here's something like that. So just putting frequently asked questions. So whatever written form. Yeah, I can start the blog for that. Oh, like, and then. And then I can share it with you and then you can add your input as well. Does that sound okay? Yeah, it does. Yeah. Our only problem is timing because if the deadline is 20s. It's not that much time left. But yeah, if you publish it next week, it's perfectly fine. Okay. All right, I'll shoot for that. Yeah, anyway, it's nice to have. If you could do that by not. And so, yeah, so. LinkedIn product product page. Great story to tell there. Oh, like, can you share? Yeah, I was about looking for links just a second ago at them. What is it? Oh, yeah, just a second. So yeah, I just spent some time, you know, to register a Jenkins project on our LinkedIn page. There are two reasons for that. One reason is just preventing squatting because it happens on LinkedIn. Secondly, for using Peters additional engine for listing Jenkins users, Jenkins feedback and getting some promotions. So I submitted the request to LinkedIn team maybe three weeks ago. We could finally approved. So now we have a product page. Just a second, I will share the link once LinkedIn find the loads for me. That's not that fast. Okay. So yeah, I'll put the link here. So Mark, if you could share that. It would be nice. So basically we just took official page and yeah, the foundation has ticked on product page. What we did by basically put some media content to the some summaries, some texts, including skills. It's useful for quick search. And also you can see that there are reviews. So now there are eating reviews. It's basically 17 reviews more than a GitHub actions, get lab ticked on and many other projects combined. So why is because I posted in LinkedIn that we posted the product page. But that's the only thing I did for now. But it initiated some content. And if you scroll to the bottom, you can also see list of user companies. Basically it's the same as on Jenkins, slash project slash adopters, but you put on the link in page and you can click see more and there are more of them. So that you created that list or is that list self-assembling? This list is not self-assembling. So you need to put companies there basically, but it's quite easy to remove this part of the video. Oh, why is that? Is there something? Oh, oh, whoops. Yes. Okay. None that I can see and forgive my showing my chat. That was a waste. Well, no worries. Oh, like this page link from the main product project page? Yes, it is. Okay. So basically, if you navigate to the project page, then every organization can list the number of products. I'm not sure exactly what's the limit. For example, we put it more products like, let's say Jenkins file runner. I'm not sure what would be exactly the purpose, but in principle, we could do that. Or for example, Jenkins Kubernetes separator, which was quite separate at the moment. But yeah, users can navigate and when they navigate, they explicitly see the button at Jenkins to your skills. And then when you navigate the Jenkins skill on any profile you also get these pages pop up. So well, maybe it will help us to get some traffic, maybe not, but while I spent 10 minutes on that, maybe a bit more. So I think it works there first. Yeah, for me. So the product approval process, you submitted a request to LinkedIn to be allowed to create a product. Did you have to give them the proposed content of the description of the product? They verified it because there are cases of squatting on LinkedIn. So basically, they verify that you're actually eligible. Now it was a bit tricky because we have two Jenkins organizations. This one is Jenkins project. Another one is just Jenkins. Yeah, I still didn't delete the latter one because initially it was a problem. Now when the Jenkins organization is 10 times bigger. And actually nobody cares. But yeah, maybe we'll still integrate that organization inside. So the approval is mostly for that. And yeah, it takes some time, but yeah, now I can edit the page without additional approval. That's great. That's excellent result. Thank you, Oleg. So Jacqueline will miss the most important update of today. Absolutely. Menkens, go ahead. You've got to share this one. Yeah. So we just started it. We discussed it more than one year ago. It's probably one April's Fool's joke. But yeah, finally I just went ahead and created that because yeah. Well, I had other things to do, but yeah, there was in the mood to just start something like that. So again, there are multiple editors invited and yes, the director I have maybe 20 or 30 images. So I'm prepared for the next week. So it just started. And so how does how does forgive my being so old school? How do I go about creating memes? There are facility tools and facilities that help me do this. Yeah, of course. There are millions of my generators though. I haven't generated any memory yet. I just use existing ones. And there are plenty of them. Okay. All right. So I'm old enough to remember sites like tomorrow, which also have communities like Deverell, reactions, like way reactions, DevOps, the reactions and the resilience gifts about Jenkins. I just need to extract them. Well, it's again a low effort fun activity. I would say that I plan to keep it borderline near the code of conduct. But yeah, they will be more self-criticism than in the Jenkins account. So yeah. I like that. I like the sense of humor. I think that's great. I don't like my sense of humor, but everyone is welcome to contribute because it's also shared account on Twitter. So instead of the mailing list, and you can share that if needed. And so the approval process just, just post to the usual technique then, because I assume I've probably got access to do this and, and likely to make mistakes on my first several attempts. Therefore it's okay if I ask in the advocacy and outreach, get her channel. Hey, I'd like to do this or how would you. Yeah, sure. So in this case. Yeah. So basically it's also an opportunity to promote some events through memes. Because for example, there are so many memes about Jenkins being down. So next time when it's a Jenkins sale goes down, I know what to post. Okay. All right. So my goal is to not allow that to ever have to happen. And your goal is when it happens to immediately post a meme. Yeah. All right. If just in case we run out of members, we can always ask some Australian contributors to help. So. I get ready to that. But yes, speaking seriously, if you take a look at other channels, for example, memory net is this list there from Jenkins, because it has quite good outreach. Secondly, they also shared good practices about Kubernetes. Sometimes. And yeah, I think we should follow this youth. So it's not on the education, not on the funding, but also sometimes educational. Sometimes, sometimes ago there was a tweet from somebody that should be edited as official. Since you have training partner to this. So, well, come on. I love, I love this one. So I think these kinds of things are brilliant. Wait a sec. My dryer is my clothes dryer is, is now requesting a gigabyte a day. Okay. So, so lost mark for another week because he will be reading tomorrow, right? That's great. Okay. Yes. Okay. I'll send you in to tomorrow as well. And then I will never get my quarter review, I guess. Any other topics for today? Not really. So yeah, next week we will have another meeting about the default call for papers. This meeting will be likely hosted by Rick, me and maybe Victor Martinez. But again, it will be just a corner session. Oh, like, so you think Rick is going to be speaking Chinese? Because I know that when I was in China. For a cube con. There was a lot of people that do not speak English. So luckily we had Chinese speakers at the booth. So Chinese translation was really helpful when we were there. So just the thought. Well, I didn't talk about it with Rick. My assumption was that the session would be in English. But if there is interest to do sessions in other languages, it's possible. I also for the session in Russian to the Jenkins through community. So Jenkins through community is more hardcore. So unlike they would be interested in such talk. But yeah, let's see. So yeah, anyone can just take slides and do a session and whatever language or create new slides for what it was. I put a lot of pictures there from previous events. So yeah. Yeah. I'm using face events. Great. Thank you. Any other topics there? I don't think so. Okay. So let's go ahead and call an end. I'll post a, I'll post a recording of the session in an hour or so. Thank you. Thank you, Mark. Thanks everybody. Thanks. Thank you.