 Roxanne, this is Mark. Wait. Um, I had, we'd had a, started a discussion in the online chat about possibly canceling this session. Okay. I don't, I'm waiting to see how that shakes out. We've got. Um, so since we're not recording yet, I think we're, you know, nope, we are recording good. I'm going to pause the recording. Okay. Okay, so. Pause. How do I pause? Oh, well, I'll just. The, uh, we've got an issue with our alpine image that needs our attention. And we're, we're working that issue right now. And I'd rather spend the time on that than worrying about the advocacy meeting today. I think we could skip this meeting safely. I completely understand. Uh, so I'm going to stay online here for just a moment, awaiting and answer a confirmation from Oleg, unless there are two specific topics that are of worry to you. No, it was just a follow up on like this month and what we did for the graduation and all that. All right, great. Thank you. And so Alyssa, I was just telling Roxanne that Oleg and I were having a conversation in the Gitter channel. We might just cancel today's session. Oh, looks like we may have Oleg here as well. Okay. Yeah. Well, I decided to just join for a second, mostly just in case that folks from CDF. Yeah. And I was just telling Roxanne that we've got, we've got challenges right now that working on the technical side that I think we would better spend our time working those technical challenges and skip today's advocacy session. That's fair point at the same time today we do technical challenges. I guess we'll have a lot of non technical ones, which we cannot really discuss at this call, but yeah. So we could still do a quick sync up especially in the terms of seeing Jenkins graduation and CDF to ensure that we don't have open action items where actions are needed from outside. Ah, good point. Okay. One question I had was if you still wanted to write a more detailed roadmap post Oleg, or if you were happy with just pointing to it like we did. I'm fine either way. I'm not happy, especially. Exactly. I would like to write a full blog post. The same time my responsibilities at the job point don't allow me to really get any significant time to that. Right. So the story is basically I didn't get heads up about the roadmap mini blog post. Yeah, I thought Tracy would have told you she just told me she forgot. I'm sorry about that. Yeah. Well, generally it's nice to have something complete. So it's not something like I had hard feelings about that. At the same time, I de-prioritized the roadmap blog post to focus on other things and taking other deadlines and yeah, I'm going on my security issue. I don't think that I will get to that right now. But if you ever do, we'll just publish it. Yeah. Yeah. Thanks for reminding me about that. So basically I'm doing similar presentation for DevOps world. So I would have to prepare content anyway. Yeah. Just too many things to handle at once and I think just good. Well, if we recorded the DevOps world. Yeah. It will be recorded. I believe videos will be published. So as usual. I would also point to that, you know, instead of an article. Well, let's see. I still need to write an article for Jenkins. Because it's also my checklist for it. So it's not something like I completely decided not to do that. I understand. Yeah. So actually I go to this in progress. So if I wasn't writing a blog post something like five pages, et cetera, and probably two would have been ready by now. Okay. That was it for my site. And Jackie's not here, but I assume if she had something she would ask. I have one item DevOps world Jenkins awards, as we've done in the past. We need nominations. I submit as my nominations. I have not. And I will I solemnly promise submit nominations. I had some great ideas. Okay, so I still so so like you submitted your nomination through the DevOps world website. Okay, so I submitted the three nominations for three Jenkins roles. I didn't get to anything else because I was also doing something like several hours before the deadline. Okay. Mark, what I can do is I can send you the spreadsheet and you can just add your nominations that spreadsheet. Okay, that would be wonderful. Thank you. Okay. And then the other item that I have was with regards to Jenkins is the way tweets. So ABC consulting is the vendor that has been helping us to write up the case studies and the user stories. So I've asked them to generate tweets for us because I know that everybody is so busy and they, and they did that that we have a rolling set of tweets that they have already created. What is the best way for us to, I guess to have the folks review it and possibly use it. That's also the question. So first, what Twitter account do you plan to use? Because right now there is Jenkins is the way Twitter account and to be honest, I have no idea who answered. Is it you, Alisa? Okay, so it's not Mark, it's not Tracy, it's not me, it's not you, Alisa. Is it Marky? It might be, but I would be surprised if it were Marky just because there's been a recent tweet from it and I didn't think he was actively tweeting on the, on Jenkins recently. Yeah, so, yeah, we can ask who is that. But yeah, the rest of Jenkins is the way Twitter account and I'm not sure who controls it. Jenkins is the way Twitter account. That one. So what happened was Tracy initially requested that Laura create tweets for us based on all these user stories and case studies, but Laura didn't have time. And so I had AB Consulting did that. And so we gave Tracy the tweets and I think it just sat with Tracy. So then AB Consulting felt like all this work that we've been doing is, you know, we didn't want it to go to waste, right? We want it to continue to give it visibility. And then they created just for, you know, the heck of it and see what happens. They created the Jenkins is the way Twitter. So it's AB Consulting that owns the, that has control of the Jenkins is the way Twitter account. Yes, but, but my preference is for these tweets to come out of Jenkins at Jenkins CI handle, because I really don't want to create more things for us to manage. So technically we can do that. Yeah, I just got a spreadsheet with tweets two days ago. I know that they were sitting around for months. But yeah, I have access to this spreadsheet now. We could set up tweets, etc. At the same time, it will need some reviews, etc. And yeah, I'm not sure whether we would have been white right now. Oh, you know, you know the context, Elisa. Yeah. So, yeah. Best effort. Yes, for sure. If we need to do a massive effort right now, firstly, I would suggest postpone it maybe for two additional weeks before the summer break is over. Because yeah, now is still a terrible time for promotions. But yeah, maybe in two weeks. So what we can do, we just, well, the dust settles, we schedule maybe one or two hours session together with Mark, maybe advocacy and outreach team members, we review all the tweets. Then we just put them in the system for schedule, for schedule tweets and then they will be just posted on an automatic basis. Yeah. Maybe it would be a preference. Because yeah, the content in there and they be cancel things perfectly right. It's a shame not to use the content that we created because we haven't really promoted managing the stories and we should do that. So, let's try to do that. At the same time, yeah, one of the ways, let's for example, if you're just, if you're willing to also join the editor team or whatever it's called, you're welcome to do so. Because currently it's basically down to me, Mark and Tracy, when you have some time. Okay. So, yeah, we can probably expand the team a bit. Find more contributors, maybe even to switch to Twitter as code as we were discussing. But ultimately we need contributors to push social media as well. Okay. Yeah, so I suggest that let's say put it on a whole for one week. Then we just schedule something and get it published. Okay. Great. Thank you. Yeah. Sorry if it's not the ideal answer, but yeah. No, it's not good. Okay. So, yeah, on a more positive note, we have the next bump for Google Summer of Code blog posts and coming. Also, we could use blog posts we have already published. So, for example, if there are plans to have a newsletter, etc. We have seven blog posts posted within last two weeks on Denkisayo just for Google Summer of Code. So, we could just get a newsletter just for that. And I know that CDF also has other projects. So, for Spinnaker, for Screwdriver, there are also projects. So, maybe there could be, for example, CDF newsletter just for that. The end of Google Summer of Code. So, yeah, if we can help with that, Roxanne, I think we have some content which wasn't published by CDF yet. Okay. We actually have a lot of content like this. We've also got this, we're three days away from Google Season of Docs announcing. We could consider using that as an announce, as another blog post or announce point, right? They're going to announce publicly, aren't they, the Season of Docs? So, for Google Season of Docs, we have two CDF projects, so Jenkins and Jenkins Sets. If I recall correctly, there was a CDF foundation also participating, but I'm not sure what they have been accepted. But, yeah, still, we will have two projects. We could promote from CDF. Yeah, that would be really cool. Who would rate that? Would you want me to rate it? Like, if you give me the content, I could rate something up or someone could rate it. Like, not the content, but the point. Yeah, how it works. On August 16th, we will have announcements. I mean, public announcements about the accepted projects. We know some details, but we cannot share them, neither these mentees nor these public. But once the decisions announced, there will be one month of community bonding. So, basically, mentees just get introduced to their communities, establish connections, also continue, etc. And inviting them to write a blog post or whatever could be a good opportunity. Yes. So, for Jenkins Sets, I believe it's approximately the same. Kara is not on the call today, but, yeah. And both Jenkins and Jenkins Sets applied for one project. Some secret information, so most likely we'll get one project and something goes completely wrong. Okay, good. So, was your sense that we should actively announce the once that Google has announced publicly Google Season of Docs selection. Do we announce that at the CDF level? Do we blog post it on Jenkins.io? Why not both? Okay, great. I don't think that there is much of concern about posting this similar content. Well, then it all would be different because it's rather about all CDF projects, rather about Jenkins. So, we can see how we match the content, but I believe that we could do some work. I didn't really think about the Google Season of Docs blog post and quite a number of documentation related announcements recently. Right. We can do more. I'm the official title document doc's officer, so I certainly could write a blog post, right? No one will complain if I write another blog post, I suspect. Yeah, that's for sure. So, yeah, let's see how we organize it. But yeah, we don't need to produce some more content. Right now, I guess for the next two weeks, everyone will be busy, but then we can see how we should get at least a post from our blog blog. For example, road map like sponsorships. We also have announcements to post about system with permissions, etc. So, yeah, we can generate additional content for both CDF and for Jenkins. Okay. So I guess we also need to report something for Jenkins, the way from the Jenkins Twitter account. I didn't do that before because it wasn't clear who owns the account, but yeah, since it's a big consultant, I believe we need to promote them. Okay. So, on a separate note, we are getting a bit more traction with LinkedIn. We are likely to hit 37 followers in the next week. So it's 10 times more than it was in May. Yeah, we just recovered our Twitter account and it helps to generate traction. So the next third challenge is to actually convert traction to contributions. It is something we should be spending a bit more time on. And yeah, another update, we actually got the control of the subreddit for Jenkins. So the history behind it, that there was a subreddit since 2011 or so. Three months ago, it was moved to the mediator state. So owners, Wilkozik and Taler, both of them had no time. So there was no pause for three months or so. And after some discussions, basically, Tim Jakam and me, we became mediators there. For me, they became mediator is also the name that they registered on Reddit. So please don't have so high expectations about me. But yeah, still, we now have control of Reddit account and also Facebook. So if we get automation, we can actually post to all these platforms. And if we have some bandwidth and not on, we really need to think about this automation. Because now we have Twitter and LinkedIn, and basically the format is completely different. So Twitter is a micro blocks and LinkedIn, you can post more or less full article, not a long one, but still. So, but if we do more systems, we don't need to think about automation so that we don't spend more time on it. So yeah, that's quick update about what happens here and there. But yeah, I don't think that there is much else to update regarding social media and other platforms. And yes, and for contributing guidelines and for the initiatives, we didn't do much changes recently. We will be definitely doing some communications and facilitating contributions towards October 1st in October. The effort is still yet to be seen, because it might be just to use stories like terminology, you know, like documentation, migration and other sources we have documented. Post them, get organized a few events, maybe something bigger, but it really depends on how many contributors we will be able to get from the community. We're planning a push from the CDF for Hacktoberfest too for all our projects and maybe a newsletter on the topic. And if we do that, then maybe Mark, you could write like how to contribute to Jenkins and where like what you want people to do. That's good. We're meeting about that tomorrow. So yeah, once there are more details about Hacktoberfest and CDF, we need to sync up because we've been doing Hacktoberfest in Jenkins for three years or so. It was still a kind of low-scale effort, but yeah, for example, last year we had 120 unique contributors and 70 of them were first-timers. So, well, it's a good number. Yeah, that's good. So let's see how we do it this year, but yeah, if you plan on some promotion, definitely you would be happy to participate as well, because I guess it's a win-win for everyone. And yeah, yesterday we finally made a decision on terminology. So now officially we have Jenkins controllers, not Jenkins master. That's great. And we can update the blog post because it's going out at the end of the month. You mean one by Alex? Yeah. Yeah, basically Alex is drawing this decision in the community, so I believe he will contact you about that. Perfect. So, yeah, there are some follow-ups, but we generally have a decision how we proceed. Well, we just confirmed everything yesterday. But definitely it's something we will be posting to the CDF and the Jenkins heterosources as well because it's an important topic. Yeah. Yeah, speaking of that, what content management system does CDF use? Is it just Drupal or what is... Weird word press. Oh, word press. Yeah. And then Salesforce to do like outreach and the newsletter and stuff, yeah. Yeah, that's perfectly fine. So, yeah, in our case, we use documentation as code. So there might be some difficulties with conversion. If we want to migrate CDF to Jenkins, but it's not like we haven't done it before. Oh, we do a lot of integration from Google Docs to AskyDoc. That's for sure. So, yeah, I guess Alex will be reaching out soon. Yes, not I will. Okay, thank you. Thank you. Okay, so anything else for today? I just have a quick one for Roxanne. Yes. When is the next newsletter going out, Roxanne? September 1 that week. Oh, okay. All right. So in case if you need additional content for the newsletter, so DevOps world is towards the end of September, 22nd to 24th. There's a lot of CDF and Jenkins content on there. So if you, you know, you want to take a look at the agenda. And maybe if there's anything that looks interesting to you. I'm sure they would appreciate a highlight on their session. Definitely. That's a good idea. Speaking of that, any plan for speaker blog posts or for the DevOps World Agenda on spontaneous. Yeah. I would love that. Oh, like, um, Yeah. It's time thing. It's such an issue. It's like, it's like asking for some time to track down everybody to get their, their, their, their time in to schedule their recording because all the sessions are being pre-recorded. And then, Oh, you got yours recorded, Mark. Done. Yesterday done. You are wonderful. There's a few that, I mean, the events team is just having, it's been a very busy week. I'm just, I'm just being, cause I'm the chair for the community track and the seat. Well, and I'm responsible for CDF as well. And so I'm tracking down person by person and it's like sucking up my time. Um, So I also was on a call with all this with most of the speakers. blogs on Jenkins.io. So that's on my to-do list. Is there any way or, because the conference now is called DevOps World, can we promote anything besides the blogs on Jenkins.io about the conference? Yeah, so we discussed it, if I recall correctly, in Spring. And basically, we could promote it, especially if there are some clarity about how we organize posts, whether we do contribute or submit and other items. We discussed that point in the SIG. So, a simple example for agenda, yes, we can post it, especially if there is significant amount of Jenkins content. And I know for sure that there is. But yeah, the problem is that somebody needs to prepare that. So for example, if you already tried a blog post with overview of the DevOps World content, I think we can easily put it on our event calendar. We could easily reference that. We could easily promote it in Jenkins social media. And I could link to it from the newsletter. Yeah, it means that somebody needs to prepare this content. Okay, I'll do that. Yeah, so this is totally possible if we really plan some community events. So I know for sure that there will be CDF booths. But for example, I'm not sure what happens with community booths. Will we have one or will it be just one? We will have one. So the discussion is actually I'm having the discussion with Jude later today. What is, so what is our preference? Do we want to have like a community pavilion where we have all the CDF projects in this space? Or do we want, you know, what we've done in the past, which is like just Jenkins booth and then CDF has its own space. I'm leaning towards a community pavilion with projects, individual projects. Okay, great. All right, we will do that. Yeah. Did you want a contributor summit or anything like that, Oleg? Well, even there is a way to organize it. It would be nice. At the same time, yeah, the more contributor summit, we still need to think how to organize that and take in the timing, take in other commitments. I don't think that we should schedule it. But yeah, even there is community booths, whatever, I think it's more than enough. We can probably do some community workshop, for example, how to contribute to Jenkins or something like that. Maybe same for other projects, maybe having some general contributing to open source, etc. And it could also count. But contributor summit, yeah, I'm not sure. It's just too much preparation and we don't have bandwidth. Right. So, yeah, for, well, I spent maybe one week for Brussels, preparing for the gender content. Yeah, for, of course, it was less, but still a significant amount of time we would need to find. Right. Okay, so no contributor summit at DevOps World in September and then we'll do a community pavilion with all the CDF projects under that. Now we may want some, does DevOps World, does the Jenkins booth at DevOps World have a way to let us put a poster up or something like that? It might be good timing to promote Hacktoberfest, right? It'll be end of September. And if we could sneak a poster in there somehow or, you know, a clickable link guiding them towards Hacktoberfest and helping the Jenkins project might be a good noise generator. Okay. And then we'll use the Jenkins needs you poster, right, Mark? Of course. We still have not thanked Xenia nearly enough for having created that image. I think that was her image still originally. Jenkins needs you. Yeah. I don't do the pointing finger nearly as well as Jenkins does. Well, I can send you, well, have you sent this photo from Lisbon? When basically we got Kiki, et cetera, to cosplay. Yes, I think I'm even in that photo, although I'm not nearly as good looking. Kosuke looks exactly right. That photo was just nearly the perfect thing. He looks precisely like the image that Xenia created. Yeah, I'll try to dig it up. But yeah, it's definitely some way in our Twitter. And somebody else. But yeah. So I think we really need to discuss how we organize the content for DevOps wall, though, since it's a virtual conference, we have opportunity just September. But yeah. Yeah. Let's talk. Let me figure out what, let me find out when the deadline for those items are. And then we'll, we'll work towards it. But I think we have some time. Yeah. After that, we will see the corner in two or three weeks. We're basically, well, I guess three wheels have a separate boost there, like any other project, maybe not. But yeah, I guess it's a good opportunity to prepare so that we use the same format to conferences. Okay. Yeah. Okay. So yeah, thanks for bringing in this topic. I really forgot about the boost and other things. No worries. So yeah, then if that's it, thanks to everyone. And talk to you in two weeks. Right. Yep. Okay. Thank you. Thanks all.