 Welcome, everyone. This is November 16 2023. This is Jenkins advocacy and outreach topics today include the contributor spotlight project, Google summer of code guidance on tweets and LinkedIn and DevOps dozen award nomination. And then next week is a major holiday in the United States so discussion there any other topics that need to go on the agenda. Okay, good. So let's let's talk about the contributor spotlight Chris. Thanks for joining us and Kevin. So tell us what there is maybe Kevin you want to be the voice first or Chris what do you prefer Kevin. Okay, Kevin you have been nominated. So things are going really well we're moving right along with contributor project. Chris submitted the ticket to the info help desk so air base been helping us get that integrated and set up in the system. So this is also been I've been working with Chris to get the smaller points finalized in this couple little things that hadn't considered before but everything's going really well we've got the first contributor story to be published has been merged. So, really, it's just a matter of making sure that the contributor site is live and then at that point we'll have everything going out. I met with Alyssa yesterday to discuss the publication schedule. Right now I think what we're going to go with is one every two weeks or every other week or so, just to make sure that there is space, time to highlight the contributor. And that also gives us time to discuss other things and highlight other topics in between the two so nothing's overloaded. And then it gives us a little bit of leeway with publication schedule in the sense of right now we've got 10 or so responses all together. With that schedule will have content for a few months and that will give us time to get more responses so we'll have even more after the fact so going really well. Everything's moving along. Chris has been an amazing help with just getting this put together and kind of getting us to this point. So, all the thanks in the world to Chris, by all means. And yeah, really excited really looking forward to getting this published and really excited to have the spotlights on the contributors. Great. So is there a prototype that we should look at together or is that still being evolved. There is a prototype site that Chris has put together and the infrared contributors spotlight repo actually has the, the, those instructions but I can do, I think I can do it really fast because I'm already in there if I'm not speaking. So I can share my screen. Let me just be up real quick. Yeah, so let me stop sharing. Go ahead Kevin. Okay, let me just make sure I have the right site. So, yeah, let me go ahead and share my screen. So this is the prototype site that Chris is, again, taking the time to build and create. So there is some placeholder information still right now since it is the prototype stage, but we've got really nice highlight cards here. So we've got a couple and Alexander Brandes are two of the first responses we got so they're going to be two of the first publish to the first published. So we've got a really nice page we've got screenshots or headshots from folks if not we're going to be working with them to do that. We've got really nice layout here. Again, I can't say enough thanks and appreciation for Chris for all work. Like this is just fantastic and looks lovely and just it's going to be a great representation of what we're looking for. So, yeah, we're putting together pull requests and working with the contributors to make sure that everything's correct there. We're working with the my fellow writers to help with any docs reviews so we're getting a lot of eyes on this and a lot of review and a lot of a lot of excitement and a lot of great positive things are being said so far so yeah. Excellent that looks great. Thank you Chris. Thanks thanks to I think it was Christina Pizzagale who did initial design for us right so thanks to Christina. Kevin thank you. This looks wonderful Chris any comments you want to make. Oh yeah do you guys want me to follow the temp that design 100% and add to it. For example, on the contributors page. So add to it like a link to like we are like something like it was there before but I didn't implement it because I wasn't sure if I should put it. But that was something like, well, are you interested in contributing if you do like here's the information you can follow. Oh, okay so so what you're asking is, should we have. Do you want to help, do you want to help out somewhere on the page is that what you're thinking. Yep. Like, linking to the participate and contribute stuff saying hey if you want to be a contributor as well here's how you can kind of thing. Yeah. I think that would be, I think that would be nice but I don't think it's mandatory. I mean it's that is already accessible from because you've already integrated the top bar. Right, Kevin I see the top bar already there and the top bar on its community overview has exactly that page already there. But no harm in adding an additional link hey do you want to be a contributor like this click here. So I think that sounds like a good idea as a sort of a closing closing item. Yeah, I can go back for to the first page. Yeah, of course. I think it's like, Oh, so I should I have to fix it then, because Alex image is not here. Right, nor is Alex's Alex Earl's nor is Alexander brand is so this page needs need image corrections somehow, right. And that might be something that I missed Chris because I put I had put Alex's avatar image in, I think two out of the three places I might have missed that third spot. Because I hadn't realized that there was the SRC the static and then there was like a third place for that all to go so let me make sure that I've uploaded everything correctly and put everything where it needs to be and and check again. Okay, because I think it's me probably because like it's supposed to be just one image with the length and they should work like on the box, but I think I highly courted the image and so it's what I can. Okay. No worries. And so Kevin, could you go back to that page back to the is the per per contributor page. So there's a Twitter link and a GitHub link so that's because they provided social social contact information for those, and that takes us right to Alexander's page. Yeah, it is accurate. Okay, very good. Perfect. Yeah. And, and then Chris was really, really helpful in the last day because this is one of the things that I just noticed was, well, if the contributor doesn't want to provide their LinkedIn or doesn't want their email connected directly to this we need to be mindful of that and that so Chris has helped with making sure that if that information is not there the icons not showing up so for instance if we go to Alex or else his is going to be different because he only provided his LinkedIn or his GitHub rather. And then I think someone else had brought their threads handle. So, that's a totally separate one that we haven't accounted for we might need to add that but yeah outside of that everything is. Really fantastic and presented and linking up and connecting everywhere that we wanted it to. Great. Thank you. Excellent show. Thanks very much. Any that's so back to sharing my screen and let's take a look at the next topic on the agenda unless there's something more on contributor spotlight. I think we covered everything that that I had on month on what we've got worked so far this I mean this week and everything the last couple weeks just kind of syncing up so yeah. Great. Excellent. All right next topic was Google Summer of Code and here, Chris, I think you're the you're a strong voice there we had a note that CDF is writing a blog post, and that they want our review is there more that's happening there on Google Summer of Code at this point. I am like, I'm preparing to submit PR to add all the ideas of the next few days by next time. Oh good okay. And those ideas to Jenkins.io right so to the to the top level website. Now Chris, I had offered some ideas do you want me to put mine in there are you going to put them in there for me. We did it for you already. Oh, oh very good. Thank you okay. Alright so already did the work for Mark. Thank you very much. Anything else that you want to highlight there on Google Summer of Code Chris. For Google Summer of Code like, I think we have to make an effort to attract mentors because I, we didn't see any. As opposed to made on those goals. So it's kind of like, I'm not ideal. Because I normally that there should be at least one or two inquiries where I don't see any. Yeah, so it makes no sense to have projects without mentors assigned right really doesn't so. Yeah, maybe should hurry up and like put up the idea so like people can tell like what kind of projects we have. Right post post the ideas quickly. And then start recruiting mentors, recruit mentors just as quickly immediately thereafter. Good. Any, anything else on Google Summer of Code. I think for now is just ideas we're collecting ideas. That's the most important thing we're going to do. And I guess one thing to warn you about is Chris asked me hey should we continue the Jenkins documentation screenshot project and my suggestion was no because I'm just not passionate enough about it personally to do the effort for it. And, and I didn't detect that others who are willing to be mentors were were somehow passionate in ways I was not. So that was one that it was an idea last year. And it's not not on the list for this year. All right. Great. Next topic then was the tweets and LinkedIn guidance. So we had a we had an ongoing discussion in the Jenkins governance board. Jenkins governance were discussed. If we need to if we would be helped by with some sort of a policy and didn't come to a final policy, but guidance from the board suggested that developers are more interested in developer topics than they are in social topics. Therefore, how to write tests is more interesting than happy new year, or happy, whatever. Right. So the idea was, as Alyssa noted here focus more on developer technical tweets, we've just just started a little bit of an extra work on that two tweets in the last two days with technical topics. Right. And then tweet every blog post is a is a good thing and LinkedIn and, and this is one I think we all ought to remind ourselves LinkedIn has a far higher impact for us than Twitter does. And, and it's a little bit surprising I'm used to thinking of Twitter as the way to do social. But as it turns out LinkedIn has has more subscribers. It's more to the Jenkins project, it gets more responses to any posting we do. So, so LinkedIn is, and it's also actually a better place for the kinds of things we want to describe because it doesn't have arbitrary limits on the length of the content that we post. So it's actually the better place for social posting on technical topics, oddly enough. Now Alyssa noted, we'll probably steer away from us only holiday us only social posts so we did one on Veterans Day. And that was what sort of the catalyst for the whole discussion. The discussion was hey not. That's not a common holiday outside the US us and in fact in some countries in Europe. It's almost the day of morning, because of the terrible impact of World War one on that on those those environments. But then the question from Alyssa was do we want to do some holiday posts intermixed in. And should we consider for instance, happy holidays on the 25th of January, a happy New Year Chinese New Year Chris I think that's February of 2024 is that right. Let me check, because I got not sure. It was February 10 of 2024 but it's like it's fabulous. Okay. And then one of the ideas that Alyssa suggested to me in a conversation was focus all posts on Jenkins related things related to the, the topic of the post. For instance, if we did one on happy holidays it's hey it's the end of year for Jenkins Jenkins end of year. We're skipping two weeks without a release. All right, now they got something useful in it not just happy holidays. I thought you would say something like it's almost Christmas season what will you get under the tree maybe a new Jenkins instance or whatever but no yours is much better. Well but but that's that's it's an excuse there. Now for Chinese New Year. I'm not sure what event we've got in that period so we'd need to think more about it what thing could be attached but that was sort of the idea. Any comments or concerns. Bruno. Yeah, maybe just a comment about the Chinese New Year. It will be after the contributor summit in Brussels. So maybe we could send a blog post if we do it quickly with a summary or what happened in Brussels. So what happens in Brussels doesn't stay in Brussels but go to China, China. I like that that's very good. Very good. Very good. Anything else on tweets and LinkedIn so one of the one of the points I guess I have one more which is, we need help from others to flag relevant articles into the advocacy and outreach get our channel. This is not something that is well suited to one person being the soul individual who proposes them so keep your eyes on social keep your eyes on places and be ready to propose tweets into that group so that we get get more and LinkedIn posts so that we get more traffic. Okay. What about retreating or reposting on LinkedIn things that we find interesting but are not written directly by the community members. Because for example on LinkedIn, I have subscribed to a virtual channel called Jenkins hash Jenkins, and I have quite a few articles popping up from time to time so some of them look interesting to me so is there a way to report that or should we put it in a. Sorry, in the Gitter channel or enter it into Google sheets so that other can vote. Yeah, so I'd say propose it in the Gitter channel. Okay, and, and particularly if you found something interest interesting we want to share it. It's a way to increase people's awareness of Jenkins. And so why not yes propose it in the Gitter channel to share and then then we repost. I'm going to repost more widely. Just a minute. Okay. That's, I have no idea what gauravs tease note taker is so I'm removing. Interesting, not removing when I say to remove. Oh, I guess it's in the eye client. Okay, put it right put it into the waiting room I don't care where I just don't want. We don't need it here they're not part of the meeting. All right. Anything else on the social media topic. Okay, next topic then DevOps dozen award nominations. So Jenkins is a finalist in the topic in the category for most innovative DevOps open source project. Please encourage your friends and colleagues to register and vote. It's a long list. Go find Jenkins vote for any questions there. I've tried to but there were so many options so can I just go to Jenkins and just submit for Jenkins and forget the rest. Yes. Oh, great. Thank you. I do it. Well, I admit there were some others there that I actually wanted to vote for because I recognize some names Victor farcich for instance is there in the list I think Darren Pope maybe in the list as well. And I think those I wanted to but it I felt I did not feel duty bound to vote for every item in their list. I thought I had to and I was very embarrassed because I didn't know, you know, the four choices. Who should I vote for I don't know them. Exactly. Yep. So the answer my answer on that so many options. Mark voted only for the ones that he knew. Good. Anything else before we close for today. Okay. Let's end the recording. Thanks very much.