 321. Great. Thank you, Mark. Hi, everybody. Thanks for joining the Jenkins Advocacy and Outreach SIG meeting. Today is August 11th on the agenda. I have the GSOC update, scale 19x recap, and DevOps world update. Is there anything else that we should add to the agenda? So I've got a subtopic under the scale 19x thing that, just to be sure, scan names, you've got it already. We'll just talk to it there. So it's already on the agenda. Okay. Anything else? We're good? All right. Let me scroll back up. So G, yes, Mark. Let's see. Oh, yes, I take it back. I do have, maybe it's under the DevOps world topic. So put as a sub bullet there. Ah, got it. You've already got it. So you've covered all the things that I was worried about. Awesome. Onward. Great minds, think alike. Cool. So for GSOC update, the weekly GSOC roundup meetings with John Mark has been going well. This is where projects provide their status update on a weekly basis. They let us know whether they're running into obstacles and such. So projects are progressing very well at the moment. The weekly recordings are on the Jenkins YouTube playlist if anybody's interested. So I thought I also mentioned some upcoming timeline for GSOC. Right now we are in the coding period until September 4th. So that is progressing well. And then from September 5th to the 12th, that is the final week. So that will be very exciting time. So GSOC announcement went out. And thank you to CDF for that blog highlighting Jenkins and Jenkins access part of the Google summer of code for 2022. And special thanks to Chris Stern for making the update with regards to content to that post. On the GSOC project that I've been mentoring, our contributor took as we planned a week off or a week and a half off for exams. So we're looking to get back online shortly here. Grateful to have those contributions. Thanks very much to everybody on Google summer of code. Yeah, indeed. I think they're doing a fantastic job. And I think they're having fun as well. Or at least they mentioned that on the call this morning. Okay, so Mark and I were at scale the end of July. And I think I was pleasantly surprised by the amount of attendees I think I was expecting less people, but we had a good show of people. It seems like it's a similar crowd that we are familiar with in previous years. Kosuke joined us for I think it was for some a little bit of time when he had a talk there and so he kind of hung out with Mark and myself for a little bit so that was really nice. And you know, we get the same we get the same thing as previous years where people come and they tell us like, I use Jenkins, I've used it for for years, you know, 10 plus years. I love Jenkins, and what's new, so that Mark will go into the demo part and show them what's what's latest and greatest and you know, talk to them about how they can solve certain situations and such so it was quite engaging and I think it was good. What do you think Mark, are you on mute. I admit that I haven't, haven't taken the follow up yet we've got roughly 40 email addresses of people that we're going to try and experiment. I'm going to send them a personal email one to one, inviting them to contribute to the Jenkins project and start a conversation with them in specific ways they could would be interested in helping. I, if I get 5% response rate, I'll be delighted. If I get better than that. That's great but they each agreed to let me send them an email so I'm not violating any, any agreement anyone had they specifically said hey yes you can send me an email. Yeah. I've been doing a lot of the I still, so matrix every month, I think sends out a post a newsletter, which is just things that happening around the community. And I think they have one major section, and the each section head puts in their little update. So all the clients, all the sub projects I think just in most, some of the times it's like no update some of the times is like we release a new client. And I'm thinking that, you know, that's different than the upgrade guide, which is very technical or change log which is very technical. Just here's some cool new features here's a cool new plugin. You know, it, I do kind of want, which is what we sort of been doing on the, the governance mailing list which is just have a section that highlights new things. I still kind of like to see something a little bit more formal that people can go back and look at, but I don't know how to really approach it yet. Yeah, I wonder. I mean one one format might be a blog post. A little more daunting to create another might be a post to community Jenkins.io that we then invite edits from so can SIG, can SIG leads edit somebody else's posts I know I can but I think it's because I'm a maintainer. Yeah, you can turn a post into a wiki post and then everyone, well I don't know about everyone but more people can edit it. You know, I was just, yeah I was just thinking it's something that, you know, our, our SIGs are somewhere in the not quite active mode, a lot of them, some of them are active but a lot of them are not. And I'm wondering if we just want to be like once a month we ask all the SIG leaders to submit an update any update whatsoever they want. And we just put that out of the, we could be a blog post it could be a community post, but start there. And then, once we start getting in that habit, then we can get plugin maintainers to submit an update they're like, oh you know, configuration as code is on a major update or after directory is doing this right plugins don't have to come in every month. But if we start getting that cadence down, then plugins maintainers can submit any extra things they want. I like that, I like that idea. So is there a, I mean community.jenkins.io for me is more accessible. I think Alyssa finds it more accessible as well as a way to put place content. I'm blog posts is just too high a barrier. Could you see a way that we could use community to do that where we would honestly, we could just make a new post and have people post to the bottom of it. Okay, just post replies category or something. Yeah, that only certain people can post to or something I don't know. I figure it's not really worth locking it down until it becomes a problem. Right. I agree with that wholeheartedly so if we just if we as an experiment said hey, I don't know hot topics or monthly, monthly refresh some some title that would catch people in yeah. I'll update the the meeting notes later with one of the matrix ones. You can see it see action. But yeah just thinking the SIGs for now is a good place to start you just reach out there's only like seven SIGs I think, just reach out to the one the person who's recorded as the leader and say hey do you have any updates for this month. You know you X SIG is probably going to have a bunch, you know, platform SIG, probably a little bit more sporadic, you know, right. So a while ago cloud bees develop these, the Jenkins newsletters their monthly newsletters and that has stopped. And I'm thinking it's either that we want to pick that back up, or leverage what CDF is still also doing because they send out I believe that they have their newsletters, and we can also leverage that. It sends it out to a broader audience. That sounds good. I was just thinking specifically from our comment about people coming up and saying, what's new in Jenkins and we're like stuff stuff is new, you know, and it'd be nice to be able to point to something and say hey, this is the last year worth of updates if you want to look at them or you know if you want to, you want to look at what's new once a year. This is where you go type thing so I was just thinking of something like a little bit more persistent. I also won't don't want to be volunteering for most of the work so I'm also open to whatever ideas come up I just thought I'd pitch it again. Yeah, I think it's great. Well, so and I mean we've got. Is this a place where we could, we could borrow something we've already well, you use the phrase what's new and Darren and I do a what's new every month video broadcast where we. And for instance, put that in there but for me that's, that's almost a little more polished I think then we want this thing to be I think this thing is more. Let's let each sig specifically call out their things and not not overwhelmed with a video that was trying to lead. It could be both actually, you know you could say okay I'm doing a video once a month on on second Tuesday. And then you send things to reply to us by the Friday before that what's new, and then you can do the video, and then you post all three together on the forums on the following Wednesday or something like it just, you know just like we're doing with the, the meeting minutes for these things is just have your video and then have a text version, because I don't watch videos very often videos require me to have sound and quiet space and it's just sometimes like the skin that the, the, the post, you know. But again I'm just throwing out ideas I don't have an actual like this is how we do it or anything. I like it so I think what I can do so Gavin went after the meeting just go ahead and post that sample for us. And then Mark I think what I can do is take this up with Bruno and Jean Mark and come up with something and then we can take it from there. That sounds good. That sounds really good. Yeah, so Bruno's Bruno's actually going to take more active role in the platform SIG. So he's, he's probably going to end up leading the platform SIG. And I know Kevin Martins is taking the lead on the docs docs office hours right now so we've got multiple voices that we can involve and why not. I like that. Yeah. Okay. So Mark and I had a session at the conference and it was called expanding open source in Africa. Well, it, it, there wasn't much in attendance, which was consistent with the other sessions that we heard as well from their speakers. But the people that attended they were very engaging with regards to asking questions and suggesting ideas and hopefully they'll be more involved in what we're doing. So, anything to add there Mark. No, we had some we had some suggestions that I thought were a little bit on the fringe. One of the people asked, Hey, what if we did something, could you be willing to go on site in Africa. And the answer was, No, I can't see that working in this case. But, but the, the concepts that it was well received. We had a good time presenting it. And, and we're going to do something. I'm going to do something similar with Xenob and with a metola at DevOps world. And then next year's conference is it's going back to its original dates and location so next year's conference will be in March, and it's going to go back to Pasadena in California. Hey, moving on to DevOps world so the contributor summit. I haven't made much progress on it, but however, the good thing is that only is going to be speaking is going to have a speaking slot there at the contributor summit, as well as Alex he has agreed to be speaking about the, the internationalization, and then we do need for those people that are attending we do need them to sign up so that I've created the form for it so the form is on this link here. And seedings are limited to capacity of 30 quick form. What else, and then the Jenkins plugin health scoring system blog has been posted thank you so much Mark for that pull request and so we're going to continue to work off the list of our Jenkins sessions that are at the DevOps world so to help promote the sessions and the conference. And I will be tweeting about Jake's blog post and posted on LinkedIn after this meeting. Okay, so I guess this is your question right here mark Twitter as code. Okay, so I know I'll like started the process a long time ago. I know he did it for the meme, the meme Twitter account, but I was wondering if this is worth setting up so essentially, you can see in the channel quite a bit of someone posts like hey we're going to tweet this, and then you may or may not get a plus one and you may or may not get it done. And then people have other external parties want to tweet something they have to ask for request. So the advantages of the Twitter, Twitter is code thing is essentially make a markdown post so a dot md file with the, the tweeting in question, and then it, you make a pull request, and then you can say approve or deny emerge and then when you merge it it goes live. Right. So the current version that I've seen does not support like retweets and stuff so there's still be manual effort, but I think it would. It could have advantages of more people being able to write social media stuff, but it also could make it more complicated. But yeah I'm volunteering to set this up if this is desirable. I don't think it would negate people who want to use Twitter manually but it would be a step for people who don't want to use Twitter manually. Okay, so so that was an important one for me so that it would not override or prevent. Okay. Good Okay so it. So this would be purely an augmentation this be an additional way of doing tweets and merged pull request says hey somebody approved it. And there is a draft PR for the actual tool to support media and retweets and stuff like that so someday down the line that could be done. And if we start using it I might be more willing to go in and help them fix finish it, but this would be a start. So media retweet code is not in the in their Twitter's code plugin yet or whatever. So, so one of the things that, at least when I post the security advisories I find that I get better response if I have an image attached. So I would not be able to do an image attachment in this initial round. I don't believe so, but the actual draft PR or whatever is pretty far along. There's neither the maintainer nor the contributor was able to finish it. But I'm, I know actually know the contributor so I could kind of see if I can step in and help. So, if, if you're willing to implement, I'm certainly willing to be one of the experimenters trying to use it. That would be a great excuse to do more systematically. Hey, we've got a blog post. I'm going to publish a blog post. I do that by merging. I also merge a tweet to the Twitter is code and we get the blog post in the tweet at about the same time. Yeah, so I can champion this. I gotta go figure out. I know I did it once. I'll see how you did it once. And I might need help getting like the access keys and stuff because I don't necessarily want Twitter access. The more access they get the more scared I am because that means I'm more of a target for hackers and stuff. But this will still help because there's a lot of people who, you know, request a tweet and can't get anything and yeah. Right. I like it. I like it very much. Thank you. Yeah. Okay, that looks like that's all we have on the agenda. And I'm going to throw it out there just because I'm still slightly working on it. I still think vendors vendors portal will be is a good idea. I just don't know what we want for it. For the most part, like I said, in the in the in the thread in on the community forums is my goal is to have somewhere I can escalate harder problems to, you know, at one point there was a release of Jenkins core that when people were getting a lot of performance issues. And no one in the community has the time or energy to help you walk through stack stack dumps stack traces core dumps whatever. You know, and I'd be like, a lot of times I'm like, this feels horrible but just go talk to cloud beats, you know, and I want to be able to say, go find a vendor that is specialized in core traces or can help you with something. You know, so this is a purely selfish goal of mine but I think it's a community win, especially because I think there's only like four of us actually on the forums helping people and sometimes be like yeah I'm sorry. No one can help you anymore. Right. And I think, I think that's very practical thing that, hey, I'm not going to, I've reached the point where I'm not going to help you further. And in fact, in my case you can't even pay me to help you further. Yeah, I'm not, you can't offer me a bounty. You can offer me a paid bounty you can't do any of those things but there are people who might be willing to take a paid bounty. And here's a list of people who who you might be able to pay to get more support. Yeah. So I don't really know what we want from this so like I've been doing prototypes, just idea and concepts. But I'm a little bit out of ideas. So we definitely need some more eyes and ears about this one. So and I still I still owe the prototypes and you have like 400 things on your TV list so I don't want milk mark to help anymore for that reason. Well, and this one I have to apologize I'm going to ignore it until after my vacation I'm out of the office next week. And I will, I won't even take a look at it until again until next week or till after next week after I get back. Until my AC gets installed next week I'm pretty good too. Thank you. Stuff. Yeah, thank you. Anything else Gavin. Just chatting. So. All right. All good stuff. Thank you so much. All right.