 Okay, and now we are recording. Hello, welcome to the advocacy and outreach special interest group meeting. Today is May 7th, and we will just go to the topics we have on the agenda. So we have Google summer updates from me, and then this question is your UX hackathon, discussion about EPFAE videos by Alisa, and also some topics about roadmap, some line meetups, and et cetera, et cetera. So let's just start. Yeah, we had discussions about the Google summer of court at several meetings this week already. I'll just spend some time for those who didn't participate in previous meetings. So on May 4th, we have got announcements by Google about the selected projects. And we're proud to announce that we have seven projects in the Jenkins organization this year. Six projects will be focusing on Jenkins. One project will be focusing on Jenkins X. I still, it's a good number. It's exactly the number of projects we asked for. All these applications have been suggested by students who have already contributed to the Jenkins project during, and to Jenkins X during the selection timeframe. And we're looking forward to work with them. So we have already posted some announcements in social media. I plan to make an official blog post early next week. So once we get all profiles updated, because yeah, right now, if you go to our page, you can see that there are mentors listed. Some mentors have profiles, et cetera there. But for students, we still need to make some updates to have everything in place. And once it's ready, we will just kick off the announcements. And Oleg, so from the CDF side, we are also writing a press release to include all the Google Summer projects. So Tara is driving that. Not sure exactly what the messaging is gonna be around it, but Jesse's gonna ghostwrite it. So I'll also make sure that you're looped in so that you can provide feedback. Yeah, we have already received a request from Tara about the list of projects. Yeah. I provided this list, but if additional reviews are needed, I'm happy to help. No, I just want you to just give it like a final look, just so, because like I said, he's gonna be ghostwriting it. So I just wanna make sure it aligns. Okay, that's perfectly fine. Okay, I'm happy to help with that. So for us, as usual in previous years, we will have a lot of other social media announcements, hopefully starting from the second part of me, we'll start getting a blog post from students and mentors. And likely we will have a lot more content for them, because some projects already have proof of concepts, which we could demonstrate. And we will keep facilitating that. So in total, we have around 30 contributors in this project. So it's a good number. Okay, so I think that's all from the JSOX standpoint, because we basically used the same framework as before. So we will have online meetups. Once you have evaluations, we will also request additional blog posts and we will be trying to facilitate discussions through special interest groups so that we can onboard most stakeholders in this project. Okay, any questions before we move on? Then yeah, that's it. And yeah, once we talk about Google something, there is a Google season of documentation. So for Google season of documentation, we have applied and the results will be announced next Monday. So here's our landing page. You can also find our application somewhere in these documents, second, which should be here. Yeah, our application. So if you're interested, you can find all the information here. And we are just waiting for the feedback. If you are lucky, we will also get additional slot for a technical writer who would be working with the Jenkins project on one of the suggested project ideas. And yeah, another update is about your UX hackathon. So we had a discussion before in Brussels about doing more one hackathons. We had a hackathon for Java 10 plus support, which was a great success. We also had a hardware first, where we pushed a number of contributions to the record high numbers, which we are hopefully going to beat this quarter, by the way. But yep, online hackathons proved to be pretty efficient. And we would like to use these hackathons in order to drive our roadmap. So we have a roadmap, which includes many stories. But historically, when we were doing surveys, this Jenkins user's one of the top feedbacks that Jenkins user interface is dated. It's hard to use that. It's hard to find proper documentation, et cetera. All of that boils down to user experience. And what we want to do with this hackathon is to specifically focus on user experience, and in particular on three areas. So it's user interface. On the roadmap, we have stories for Jenkins look and feel updates. We also have the discussion about accessibility in the previous UX meeting, and there are other stories. So this is from the technical side, on documentation, we want to put solution pages, tutorials, and user documentation. And we also want to work on the marketing, because for us sharing stories, it's also a good opportunity to get feedback about user experience and to share it with other users. So Alisa has recently started the Jenkins in the Way program, which is currently online, which we are promoting. There are stories here. Right now there are eight stories already, or something like that. And we want to actually push it a bit more. The hackathon will offer contributors to write user stories, and also to just post their stories in whatever social media is Jenkins the Way hashtag, similar to what we use currently is promoting the content. And hopefully it will help us to promote what we are doing more among users. So that's the idea for this hackathon. And actually I wanted to spend some time to discuss the framework to get feedback from SIG members, but we don't have so many people on the call. So do you think it makes sense to discuss now? I do. At least I think it would benefit because Alisa and I will probably be actively trying to promote it, help people know it. So if we talk about the framework now, it gives us a sense of what we are doing. It gives us some notes we can take and some ideas to capture. Okay, so yeah, briefly describe the framework. We actually had hackathons before, like our 10 plus support hackathon. It was a 5D event, and it was not a hackathon per se, it was a hackfest. So it's not something like for five days, people were just working 24 hours per day, depending on how much sleep you need to hack something, then to demo it and get the prizes. Our approach was quite different. We invite everybody regardless of how much time they have. And in order to make it possible, we prepare new befriended tickets, we prepare some onboarding events, contributor materials, and at the same time we have advanced topics as well. So basically it's hop-in, hop-off event when everybody is welcome to participate. Usually we have people who just do a couple of contributions. We have people who spend almost full-time driving particular stories because some people with a couple of us from companies and we are preparing for that. So right now we have some new befriended stories. We still need to create G-requires, et cetera, but these stories are more or less confirmed. So for example, thanks to Mark and documentation for working on the user documentation, same for user interface. Yesterday we had a meeting to discuss new befriended tickets we would like to create and also new befriended tickets. So we will be pulling it together. Yes, Jacqueline. So there is a question, but we will submit it to the event calendar. We will do that. So what? Yeah, I plan to do that, Jackie. Okay, cool. Cause I'd love to also make sure that the CDF promotes it on their channels cause this is like something that the CDF like hasn't been a part of. It'd be like the first hackathon for our project. So I think it'd be, we definitely want to help you guys wherever we can. And I also want to make sure that you guys, like we've got socks. So if, I don't know if you creating like custom swag for this, but we can also help with some of the, we have a ton of socks for Jenkins. So. Oh, that'd be great. Yeah, we can provide socks and we can provide decals cause I ordered about 3,000 of the Jenkins decals. So we are stocked up to provide it for you guys. Just let me know. And yeah, or I could have, for example, the codes created and then we just give it to every attendee and then they go and order it themselves. So. Okay. Yeah. So what we had with regards to swag before. So we have called this sponsor in the event and we will be using the same Jenkins as the weight teaming. So it allows us to use the same t-shirts which have been created. And yeah, these t-shirts are really cool. I'm looking forward to receive one. Yeah, me too. Yeah. So yeah, stickers. We also discussed some special prizes which is currently TBD. But yeah, hopefully we will have some. So, and if we can get some from CDF as well, it will be awesome. We can, for example, if you, one of the things that we could give you is some of the CDF hoodies, I believe we still have some. And then we are, we did create Jenkins, but it's the original, like the Butler. So we could give, give you guys t-shirts too. I just need to see, I put in the order back in March, but because of Corona I, they haven't put it on our store yet. So I'm assuming that it just, they haven't received it depending on where it's coming from. So let me check in on that. Actually, it's a good topic to discuss today if you have some time because we have other events like cool summer off code where we would also like to distribute swag. Yeah, just give me numbers, send me an email, give me numbers, how much you need. Like I said, I ordered a, I ordered 3,000 stickers. So I'm stocked up for, for that kind of swag. And I also have, we also still have plenty of socks. I think we had around 200 socks. And then t-shirts, I think about 200, so. So Jackie, how would it work if I was to give you, because we have Jenkins is the way t-shirts that I'm producing at the moment. Okay. What if I send them to you or to whoever the vendor is. And then, and then I think it's easier if we just give- They send everything out at once. Okay. Well, would that cost us anything? Like in terms of for CloudBees or the Jenkins project? I don't think so. So let me ask, I do have a phone call with Pinnacle. So what I was thinking we could do is just have, once you're done with all like, once you get a confirmation, hey, your t-shirts are done. Why don't we just ship them to the Pinnacle's warehouse where they ship everything out. So depending on how you guys want to do it, you know, we could do something like they get a Jenkins is the way t-shirt, they get a Jenkins socks and they get a decal and have them ship everything out together. Yeah. That would be great. Yeah. So I think, send me an email, Alyssa, and then I'll ask them and then we can, I can ask them for their address. Yeah. So that you, then I can give you the address. Okay. And then we can have all that stuff. Yeah, it would be much appreciated. Yeah. Cause then it'd be easier to just put everything in a, like in a package. Yeah. Yeah. And also it would be really helpful to use logistics system because before that we were basically sending Shvaka on our own. Yeah. Well, it requires so much time from contributors and definitely if there is a vendor who we could use. Yeah. So I'll ask, I mean, I'll just send an email right now and I'll copy you, Alyssa. Okay. That'd be great. And they, they are pretty, they're a pretty good partner. So I'm hoping they'll say yes. Okay. Okay. Cool. Yeah, that's pretty good. So I will also follow up with regard to GSOC then. That's great. So let's go back to the event. So yeah, Shvaka is something we will be coordinating. We will be sending them after the event. So there is no time pressure to get it ready right now. And we will also continue the promotions. So my target is to officially announce it on Monday or Tuesday next week. So, Oleg in terms of back to the swag, is there a threshold that you're envisioning setting? And I liked Octoberfest's technique of must have had five accepted something or others. Are you envisioning something similar for this right? Yes. So what we discussed is Alyssa. So we have some both part estimation for the budget. What I plan to say in the announcement that top 50 contributors will get t-shirts, et cetera. And for the rest, it really depends on what actually you'll be able to facilitate. And for example, this help from continuous delivery foundation, definitely we could do more on this front. So. Great. I love the top 50 because that assures we won't overrun Alyssa's budget. Great. OK. Thank you. If you get to 50 contributors, it would be already a good achievement. But let's see. So really in Octoberfest, we had 127-week contributors. So those who registered in the program, let's see what we could do something like that. OK. So going back to stories, accept advertisement, we will try to put everything on our side. We also need to facilitate more project ideas. So yesterday we had a discussion at the UX meeting. And we have some stories added, which are marked as advanced topics. So for example, it's system read and read only UI, which is important for configuration as code stories we are working on. Then the solution pages are considered to be a rather advanced topic, or maybe it's not. Also, another advanced topic we put it is installation guides taking our first discussion of platform seed. I'm not sure, but yes. Agreed. Yes. Yeah. And what else we have? So yesterday we had the idea about credentials plugging UI, also creating new UI samples for developers. I'm not 100% sure about that, because we rather want to focus on user experience. So yeah, obviously it also contributes to that by providing developer tools. But yeah, maybe we should focus on user features. Git plugin, especially multiple Git actions. So when you use multiple Git steps in pipeline. Yeah, definitely an advanced topic, but yeah. Advanced, dark, and very good topic to have. Yeah. OK. Yeah, but for that I am definitely willing to print issues on my own. Also some site panels, et cetera. So we will be refactoring the stories. Hopefully, tomorrow I will meet the pull request using initial listing for the website, these queries, et cetera. And we will keep updating that. But yeah, that's the plan. What we also need to do, we plan to have at least one online meetup in the beginning. Just a second. So on May 25, I tentatively plan a grant opening meetup. Maybe this morning and evening session. And for that it would be nice to have some overviews for all these three areas. So all right. So morning and evening session. So does that mean that it's the same session that we'll run both in the morning and in the evening? So usually, or not usually, what we did previously, we were doing grant opening on the evening. So basically when we have overlap between United States and EMEA time zone, and also still a park, because it's a bit late, but it's possible. But for those who want to start earlier, we were doing a session earlier, something like nine AMUTC, whether we were doing basically the same, but maybe just less contributors. So it's what we did before. At least then we can adjust. Okay. But for evening session, which we definitely need to have, it would be great to have presentations for all three trucks. So I'm currently working to get somebody for UI, also for documentation, and for whatever promotion. So Jenkins is the way social media. And it would be great to have multiple presenters there. So for example, if your mark is available for documentation, it would be great. And same for UADC, if you're able to speak about Jenkins, it's the way how to submit the stories, how to share them, it would be much appreciated. Okay. So welcome words, like to bring here. And Oleg, I think you mentioned that you will write a blog post about this hack fast, right? Yeah, so we will have at least two blog posts, one early announcement on Monday and Tuesday, where we will basically have some top-level overview and the registration for it, because we will need the registration for shipping details, et cetera. Well, or if we use CDF resources, just contact information so that we can send out codes. Okay. But yeah, so it's something we will need to figure out. But it will be initial announcement. And the final announcement will be just on the day of the hackathon beginning, or maybe on Friday before, so that we list more stories, we list more examples there. And yeah, it will be a longer blog post with all this information. Yeah, it will happen just on the days of the hackathon. Okay. Okay. And so Jackie, it's okay that we cross-post this on CDF website as well? Sorry, I was multitasking and was not paying attention. That's okay. So we're gonna have about two blog posts before the hackathon, before the hack fast. And we'll have it on jengens.io, but I wanna make sure that it's okay for us to cross-post that on. Yeah, yeah, please submit. Yeah, please submit. Yeah, absolutely. Yeah. So I will do that, Oleg. Okay, that's good. So, well, I will be still sharing this information on CDF Slack, but we'll see if you could help with it. Yeah. Okay. Yeah. So after the first day, we will also try to facilitate some developer meetups. So for example, how to develop front-end, maybe how to write Jenkins documentation. I'm not sure, but I think it makes sense. It's really easy, but yeah. Maybe we could just match it in the opening session actually, but let's see. Yeah. I think you're right, Oleg, that I'm not sure it justifies a full dedicated session. Let's see. Yeah. And after that, we will have some closing events and we will try to process this information. And once the hackathon is over, to prepare a hackathon results blog post earlier. Because for us, historically it was a problem to have a closing blog post because everybody is so exhausted, everybody is sweet to start the tasks. So for some events, we just didn't have once, but this is something we need to fix. Okay. Okay, so yeah, this is the plan. And yeah, I will try to share more of it next week. But yeah, so far there is support in the community. So everybody is finally doing that. Nobody was against, I think we just roll forward. Yep. Okay, any questions? A lot to do between now and then. We can do it. Yeah, I can show my Friday schedule to you later, but I didn't get almost all the time to the hackathon tomorrow. Okay, yeah, that's. So yeah, some heavy lifting needs to be done, but I'm confident it can do that. And the reviews will be much appreciated. And new befriended tickets, yeah, this is the most important thing. Because during October 1st, we lost something like 300 new befriended tickets. And we still didn't replenish this number. So yeah, time to do something about it. Okay, well, first of all the problems, I know, but we need more. Okay, so yeah, thanks for making a meeting with us. Okay, the next topic was Jenkins, the preferee video. So could you just talk about that? So we have, the Jenkins project has been given some money to do, buy CloudBees to do an Epifio video. And I put a link there with the example of the video. The video is about, it's a less than three minutes video, but my, I'm here to ask for guidance on how do we want to approach with this. So before starting working on this video, we need to answer the such questions as what is the audience base that we wanna achieve with this video? What is the messaging that we want to achieve with this? And then what is the, what does success would look like for us in terms of the Jenkins project with this video? So I'm looking for guidance in terms of should I, should I start a document and get people on the SIG to add input, or should we build a smaller committee, a smaller group to work with this? Cause I would love to get more than just myself working on this video. Personally, I think that advocacy and outreach would be a good venue because we already have a quite a small team here. And we could also outreach to wider Jenkins community once we have something to show. I mean, in terms of documents so that we could collect more ideas. Okay, so just use the mailing list for, okay, okay. Maybe you may need to use a Google Doc to collect ideas. Right, right. Now, Alyssa, are you looking for the conceptual things, high level things, are you looking for script proposals? Both, any of the above? So the script will be done by the folks at Epithio. Okay. So right now we're at the very beginning stage. So before going to them or meeting with them for that first initial meeting, we need to let them know, okay, who are the audience that we want to get to? What is important to us in terms of messaging? You know, what do we want to get out of this video? So those are some of the questions that we need to answer before I can go to them and that's how we start the process. Okay. So yeah, this is definitely something we could discuss on our site in other work as an outreach. Okay. Okay, I will start in email thread. Thank you for that. Yep. Okay. So anything else about this video? Not for me. Okay. Let's just quickly talk about Roadmap again. So we made some updates for coming to marketing for our official programs Roadmap. So based on the stories we even got recently. So Jane can say that the web program as it was confirmed yesterday, the governance meeting is officially in the part of the Roadmap now. Same for new online meetup platform. Same for UI UX hardware. We kind of agree that we do that. So we just put the new stories here. What else we added? Jenkins on Kubernetes online meetups. We just put it as an additional item because it looks to be an ongoing program. I have something like five more online meetups in the pipeline. Oh, nice. Yeah. And we already have four scheduled to happen next week. So, yeah, I think it would be good. Yeah. Also, I added Jenkins on LinkedIn because our experience looks to be pretty good there. Just look at these numbers. I literally spent one hour last month on LinkedIn, but still it helps us. We can visit more contributions through this channel. We can just have more please because, yeah, you've got this blog post, for example, a Google Summer of Code announcement. So here you can see that basically 170 people clicked and went to our website on this blog post, which is basically just two minutes of work. Same, we also promote Jenkins' other way here. I did that for Farm. Let's see. So basically it was more than 2,000 people who viewed that. It was a 5% click rate. So 5% of the ones who clicked to get more details. Well, 135. Also, nine people shared that. So I would say that it's still below Twitter account, but firstly, the audience is different because LinkedIn, for example, has small reach in some regions like India, for example. It's very popular there. The same also we post in different time zones. So we again get more follow-ups and basically it goes almost for free because we duplicate the content. Yes, sometimes I extend the content because in Twitter we just have 280 symbols. We are not really limited. Well, we are still limited, but yeah, I just copy a section of our blog, et cetera. So again, it's not a big deal and it helps. So it's also on the roadmap now and yeah, I think we will be pushing it. And thanks to Continuous Lira Foundation to reposting some of our blog posts, we will do the same. So yeah, but I think it's overall a good experience. Yeah. And later we will return more content managers there to set up automation. Oh, but let's see. Okay, so yeah, thanks Mark for adding the Jumbotron. So as we agreed yesterday, we will be changing the Jumbotron. We will be also updating our Twitter logo for one month. And this section item is on Alisa. Well, basically on Alisa to contact Tyler, so that Tyler changes that. Yeah, hopefully it will help us promoting the program. Yeah. Okay. Now we, oh like on that screen, I realized we had talked yesterday about changing the avatar. We did not talk however about changing the background. That big, the wide image that's right behind the avatar. Fine, we're changing everything. So yeah, the problem is having a contributor who would change that. Got it. So Tyler will definitely help us, but we need to propose exist the exact content to put there. Yeah, and for now it's fine. I just realized, oh, hey, there's more to it even than just the avatar. Yeah, we can put some text, for example, after the account name. So some people do that, something like stay home or it would have a cube con. So we can put the jinxes the way we tell it. Well, yeah, these things could work. I'm not sure how far we want to go with the official account, but in principle, we can do that. Okay. Anything else? Okay, so another question is basically to SIG members. We have a new page for online meetup which documents our online meetup platform. And one of the sections today is about how to apply to speak at our online meetup or how to host an event. And basically all boils down to please send a message to our advocacy outreach mailing list. And we had an example of one email coming from third party contributor. So there is, oh, actually now there is another one from Nikolai. So Nikolai presented about Kubernetes and configuration as code. And yeah, there is now a proposal from about job user. So my question to SIG members, are we fine with such kind of code for papers format? I am. And this particular by Nikolai, I'm very interested in personally. So yes, I like the format and I like the topic he's proposed. Yeah, so Google Doc should be commentable as documented. So we can easily review it here. You have mailing please, so we can discuss that. So if everybody is fine, let's do that. And I don't expect a huge traffic here. I love the idea that we finally have a forum for people to submit their speaking. Yeah, so no more Google forms, no more whatever, just drop it to the community. Yeah, love it. Yeah, same for hosting meetups. But yeah, it's specific to Jenkins. We already have redirects to continuous delivery foundation on our local meetups. I think we should add something like that here because now there is official webinar program by CDF. So we should add the link in here. But yeah, for Jenkins events, we can use our online meetup platform. So I think this should also go on the continuous information and the CDF newsletter, Oleg. Okay. So I can help with that. I can help with that. I can reach out to the appropriate folks to get that on there. Thanks to CDF. Yeah, and actually, while we speak about webinars, the NAPI is still online. I have a question to you. To who, Oleg? Me? Jackie. Yep, yep, I'm here. So we are starting Jenkins room meetups. So basically meetups in Russian. We will be using Jenkins online meetup platform in some way to post them. But we have a discussion about meetup, which would be rather a bit more generic, not really related to Jenkins. And I wonder what is CDF stance about meetups, which are healthy in different energies? Would you be open to host them, or should we seek other alternatives? You know, I don't have anything against it. I wouldn't see why the organization would have anything against it either. But I'll ask just to make sure, but I think it should be fine, Oleg. Yeah. So for English, we definitely want to use this CDF platform. For Russian, we have a couple of other options. So we can see how we do that. Okay. And definitely we will cross reference to these meetups anyway. So hopefully within one week, we'll follow up on the story. So if you ask whether it's possible to do meetups in Russian, it would be much appreciated. We plan to rename some of Russian Jenkins meetups to CI CD meetups. Okay. And with the current situation, we can use CDF platform for them instead of using Jenkins online. Okay. Yeah. I don't think we should have an issue. So, but I'll confirm that I think we should be good. Okay. No worries. I can fix it. It's too late for me. Okay. So, yeah. Moving on. So regard and comment strip. All right. I guess. Do you have some updates? Oh, for the comic strip. Yeah. So I guess same question. A comic strip. Yeah. So, so we have a Jenkins comic. What Jackie? Yeah. My God, that is so cool. Could we share the image or? Okay. Yeah. Yeah, we can share. Do you have it? Or I need to find it. Yeah. Or we can wait. Or we can do it of the records later. If you prefer. Doesn't matter to me. We can share it. It's, it's, it's available. So in May, Jackie, we came out with our first Jenkins comic strip. And the plan is to release a Jenkins comic strip. Once a month, every month until the end of the year. That's awesome. Yeah. So I need a place. To post it. Yeah, we can make a page on the CDF. Okay. Page. Oh, you know, website. Okay. I'm how I want one for each of the projects though. Oh, cool. Okay. That is really fun. Yeah. Okay. Yeah. So what we have on the Jenkins page now, you have artwork. This page needs some redesign because it's already. Well, it means pagination. Definitely. So we'll somehow rework later. But yeah, for example, now we have. We also have for the model edit there by Adrian. So what we could do, we could just create a section on the artwork, for example, for comics or something like that and put it there. Okay. And then we can ensure that they didn't from right places. So this page gets enough traffic. Okay. This is one of the ways you can even create some navigation. So. I like that idea. Yeah. So, for example, you can take it. So he basically, it's just separate pages. So something like that. Oh, okay. So we can do something like that on Jenkins. It's easier. Okay. Yeah. We'll handle that. But yeah, let's see. It's so fun. I want to include it in the newsletter. Oh yeah. Absolutely. So I'll send it to you, Jackie. Cool. Yeah. That's a really great idea. I love it. Okay. So, oh, like, so who would be able to help me with, with Jenkins.io? And I am able to help. Okay. Mark. Yeah. Mark. Yeah. The structure. Yeah. Yeah. Yeah. Yeah. The structural piece Oleg's certainly much better at than I am, but the, the content and trying to do pull requests. Those kinds of things. I can certainly help you with Alyssa. Okay. And then I think we, we had talked about doing a blog. For, for this as well. So then. That would be Mark to help me. Yes. Okay. I got it covered. So your artwork comics, right? Right. Okay. I can get the framework done. Yeah. Even. So for example, even if you look for Jenkins comics now. I hope that all content is appropriate. Well, it's, it's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. It's wrong. Well, it's wrong. It's wrong. It's wrong. Oh, it's wrong Jenkins Comics. But still there are some. And yeah, you can find more. But, yeah, there's. Hey, there's, there's one with the DevOps world, thing that used a, yeah, I was looking at the one. Plutura pipeline newsletter. They, they combined a, I don't know if it's legal, not. So, yeah, if you want to have some content to just start it, we can definitely Google some. Probably this one isn't really about Jenkins, but yeah, whatever. Right. Well, and it's probably a glaring copyright violation. So yeah, let's try to avoid that. I already had to deal with a member already violating. So, I don't need to, I don't want to deal with another lawyer again. Okay, just follow the rules. Okay, so anyway, we can just put whatever. But yeah, once we have first comment strip one already, I'm definitely happy to create a prototype for Jenkins. So, all like in the past at DevOps World, Jenkins World, we've had like each year we would have a a mural done by a comic strip. Do you want it on that page too? That would be cool. Why not? It's a artwork. Yeah. If we've got photos of the murals of past murals, and if we're allowed to share those photos, I think I have photos of one or more of the murals. That's a good idea. I believe we have images. Okay. So, before having murals, there were also images, which we were reviewing, but advocacy and outreach meetings. So, yeah, we can definitely get them posted. Okay. So, whatever artwork called these or other vendors would like to host and to donate to the community, we are happy to accept it and publish. Great. That's easy. Okay. All right. I will gather that and send it over. Okay. So, I'm happy to post that. And, yeah, we will set it over to this page a bit because, yeah, it's a bit, well, it's not obsolete, but it still looks pretty bad on the mobile screens. So, if you tweet this page, it will look terrible. So, now it's time to apply my new CSS. Okay. So, let's see. Okay. So, yeah, that's okay. Yeah. And blog post, Mark, to help you with it. Thank you so much. And I guess we, for Jenkins, the way we all expect blog posts to be posted eventually, right? Yes, as the stories, as new stories arrive, I assume we'll eventually select some of those stories and blog post them or maybe all of them. Yeah. But this is a great way to collect more candidates for the blog. So, Mark, we have one case study from, is it D4 Science? I don't know if you want to post that as a blog. It's, so last week we posted a blog talking about the initiative, the program itself. And then, so, I don't know, this week you want to post about that user story, the case study that we got from that. So that maybe like once a week we have something. I think that's a great idea. Let's talk about it. And yeah, let's talk some specific details, because those would be good if they came from the original author as though that were the person submitting, I'm happy to go straight or to copy and paste to facilitate that. Yeah. Yeah. He's, we talked to Manuel and he's more than happy to help us get this on jengus.io. Great. Okay. Okay. That's great to hear. So, yeah, I guess May and this summer will be quite packed with content. Because, yeah, last year on average we had 10 blog posts per month with JSOC. This year if you get jengus in the way and other programs, okay. Originally when Tyler introduced the new website he said that he targets daily blog posts. So maybe we'll get to this goal. Okay. Cool. Yeah. Good news that we extended jengus.io copy editors team couple of weeks ago. It will help us. Yeah. Okay. So last story we had in the list is a CDF virtual booth. So, yes, CDF ambassador, I got invitation to actually organize something for the jengus project. And we had a follow up conversation with Mark and we are ready to amend this booth. And for us it would be a good practice because we have other events like KubeCon, like DevOps world and basically almost every conference in the world is the console that goes virtual. Yeah. So having some experience with staffing virtual booths would be useful. Also, Oleg, if you guys have like spec sheets or data sheets or white papers that you guys want to submit to us, send that over so that we have that we can start sharing that like that collateral with the community because I don't have any for Jenkins. Yeah. We have some materials. I wouldn't say that we have that many, but we definitely have some. We also have rolling decks and whatever which we could convert to booth materials. And actually this is exactly why I put this item to the agenda. But if you want to have this material, so the design is my sentence. Yeah. I mean, share with us whatever you have. I don't want to add like new like more work to your play. I think, but I think for the future, like you said, it'd be good for us to just have that stuff. So it could be easily distributed. And then Mark, I totally, I'm going to drop in the application for the ambassador program. I think you should definitely apply. Okay. Otherwise we will eliminate you. And Oleg, is Oleg an ambassador? Oleg is an ambassador. I just, I'm actually, that's what I'm working on right now is the page. So I'm looking through my email to see who sent me their bios and their photos to update it. I haven't, but I promise to do that. Yeah. Just send it whenever or even if you have like a profile already created somewhere else, send that over and I could just copy and paste it. Okay. Okay. I will do that. And yeah, thanks for inviting because of course, it's really a great opportunity to try it out and see how it goes. Yeah. And if you guys also have other folks from the community that you think would be good ambassadors to represent Jenkins, please refer them. Because I'd like to, my goal is to have about a hundred ambassadors for the CDF by the end of 2020. And we're at 35. Nice. So I think, I think we could definitely get there. But we just, you know, like I said, we just need to evangelize the program a little bit more. Right. Do you have anybody for Jenkins acts yet, Jackie? No. And that was the other person I was going to go bug was Kara. Yeah. And then who else? Oscar, maybe. Oscar definitely. Victor. Yes. Stratkin. I'm not sure they'll say yes, but why don't you send me a list of folks and I'll go bug them. Okay. And Rowling better say yes. I mean, he's an excellent speaker. He better say yes. Isn't he one of the co-creators of Jenkins X? Yeah. Yeah. Okay. Yeah. On the Jenkins site, we will also look for more people because we have a lot of community members. We tried to launch Jenkins ambassadors program a couple of years ago. So maybe there's more people from. Yeah. Or maybe. And who's driving that program, Oleg? It was me. So is it still going or is it? No. No. Okay. Yeah. It was superseded by your program, Jackie, whether you knew it or not. Oh, I'm sorry. That's not, that's not a sorry. That was an intentional and a delighted. Okay. Yeah. So if you get that, we could do the same thing we did with the jams where we just transition everybody over. But let's put a community. No. I wouldn't worry about the transition. Yeah. Keep doing what you're doing. Right. Okay. Okay. Got it. We will just nominate the right people or ask them to self- nominate. We nominate and that's a good choice. It is really. Yeah. I mean, or have, yeah, nominate folks or just let them know if they want, if they want to participate, they have a place. Yeah. And thank you. Yeah, absolutely. Okay. So yeah, it was quite a packed meeting, but thanks a lot for your time. And yeah, I'll try to get a video of this meeting published by the end of the day or maybe the other tomorrow. Yeah. Yeah, let's follow up on all the items you have. Thanks all. Great. Bye, everybody. Bye, Liza. Bye. Bye.