 Hello, everyone. Welcome to the Jenkins Governance Meeting. Today is January 27th, 2021. So, we have a few topics in our agenda. Let me share the screen. Do you see it? Yes. Okay. So, yeah, we have news. So, two releases. Actually, we had to do two releases also after the previous meeting, right? So, yeah, we released, yep, you're right. So, it was accurately on the other meeting. Okay. What do you like to talk about the reviews? Yeah. So, we were resolving some regressions that had inadvertently been introduced in 2.233.2. 3.3 resolved those. I see some feedback there that looks like noise, but there's one report there that I've got to investigate on the, yeah, that one. So, haven't looked at that yet. I'm not sure if it's a macro. No. No trigger and jobs for pipelines. I've seen it, but yeah. Yeah, so, so it needs some further investigation. Yeah. So, it might be related to the changes. No, no. And so, for quick to see, you also had the new release with additional patches. So, this upgrade to the latest version. And here we have our regressions, but all of them are reported to the token macro plugin. And yeah, this was actually fixed long ago. I didn't quite get what happened, but yeah. Oh, so the issue there was somebody failed to upgrade a plugin and, okay, interesting. But anyway, this reports are not relevant. Got it. It was related to smaller release with a few bug fixes. Thanks to contributors as always. Okay. So, any other news? Oh, LTS baseline release baseline selection. We'll start the discussions today. I'll send an email today proposing that I chatted with Tim Jacome and private email about it. He's okay with me sending the email to start the discussion. Yeah. So I guess it will be 77. I believe that 277 seems like the logical choice. It has several important fixes in it, and is the best in the tables to divs evolution that we've got. That's great. Thank you. So, any other news? Yeah, we have for them starting in just one week. And that for them we have developer stand and we have CCD room. So everyone is welcome to join. And he's looking for more participants. I think Olivia invited me to a stank and stand room last night. So, oh, like, we still have two more slots that we need help with for the stand. And that's, let me take a look at the specific timing for that. So for Saturday, it's from three to 6pm. And then Sunday, three to 5pm. That's where we need help. UTC. So, yeah, I'll try to join if possible. And if not, we can just call for more contributors. Yeah, that's a little early for me. Yeah, and the Sunday three to six or Saturday three to six. Alyssa, I'm available if needed. I'll be covering the one to three already, but if we don't get anybody else, I'm happy to cover Saturday. I'm not available for the Sunday. Got it. So, I'm already in for Sunday in the morning, but I don't have any other things on Sunday. So maybe if nobody else is coming, I can take the afternoon session as well. Okay. Thank you. I'll let you know, I'll give it an until this Friday. Um, but I'll reach out and confirm with you both, whether that, and we're going to save those two slots for you both. That's okay. Super. And the worst case, we may have two people there. Just definitely not the worst case. Anything else about for them. Not from me. What exactly are the plans for this room? So, should we prepare something or. Yeah, so, so really a good question we've got. Olivia Barney has outlined that the stand has a website that we can use to place some content on. He recommends that we have an agenda so that we can invite participants for specific topics. So during your session, for instance, it might be a great excuse if you'd be willing to talk about warnings and how to use, I just had a request today on, Hey, how do we use static analysis and how do we present results and if you would be willing to demonstrate that during your time, we could put that on the agenda during my time I proposed, Hey, I'm going to talk about the get plug in things that I already know and we can, we can discuss. And the idea was that way they have agenda items. They're people know, Oh, go there to talk to someone's this person about this specific topic. And Alyssa I think you're capturing those topics in the outline document if I remember right. Yes. And I put a link in the chat window as well. So if you scroll down. Oh, like, we have, see, we have three, I think three demos lined up, and I'll get those on on the, the conference website soon. Okay, thank you so much for this. You remind me I may ask, even Fernandez, he's got a technique that I also use that I want to make him to come in. He and I will have a conversation back and forth about it. This is for the demo mark. Maybe. Yeah, it's, it's using using Jenkins pipeline to test Jenkins pipeline. Okay. Yeah. Yeah, I'll discuss it. No, if I get even, I can do it myself, but I would love that even there because I've seen evidence he's using the same technique. He's using Jenkins pipeline library to demonstrate anything else, but for them. Then we have city corn. Would you like to summarize it. Yeah, sure. Yeah, so city corn, we pretty much getting all set for that. So it's June 23 and 24 virtually for those days kind of pegged on Eastern time, but we might start some sessions a bit earlier to accommodate folks in Europe. And the main thing to know right now is that the call for papers is open. So we're looking for good talks, and particularly Jenkins talks. I was going to come along to the advocacy and outreach sick tomorrow, maybe to get into more details about like how we can ensure we've got some good Jenkins content, maybe see if there's folks from the community who want to be involved in, in picking talks, shaping a birds of a feather session. And then we've got some other options as well if there's interest from the community to go beyond the normal CD con and do something like a contributor summit. And I bring that up because we're working with the spinnaker community and they're going to be doing a kind of spinnaker summit. We're going to have a follow up with CD con. So, yeah, for now, I just encourage folks to register submit talks and then maybe tomorrow's advocacy and outreach meeting is a good place to get into some deeper discussions about Jenkins presence at there. How can we make sure we're working with you to engage the community. Having the Jenkins community select the talks and things like that. Let me know if any questions or thoughts and happy to just get into a little bit now if you wish. So call for prepers is open for until the end of February, right. I think a little longer than that. March 5. And we have an early bird deadline so we'll be like promoting maybe five talks from the program, just to encourage folks so if you are fond of leaving it to the last minute. I think it's worth trying to go for the early bird deadline just in case it gets extra chance to have your talk highlighted. Okay. And yeah, the news updates. Okay, so contributed some it. Thanks to Mark for driving to this year. Yes, so the concept with the contributor summit is has to be different this year we've, we've loved meeting together face to face at FOS them. It's very, very well for people to be face to face to talk about things to scribble on whiteboards to get ideas. We just can't do it with COVID-19 so we propose the difference scenario here where we start with an intro meeting 90 minutes introduces topics summaries from the various six and projects, then break into a series of tracks, decided during that initial session for specific focus that those tracks will decide when they meet and how they meet. And we recommend zoom, but they meet when and how works best for them over the course of the next two days, then on day three we do a closing summit. So this is the concept and the idea. What I'm doing now is actively recruiting people to first attend, take specific roles or assignments in it and sort of topics and themes I'm starting to see if there are themes that are naturally flowing out of it. So I'm coming to suggest the document is open for suggestion would love to hear ideas. If you're concerned or got objections. Also, those would be fine to express also. Yeah. And just for the last contributor summit there was some really good topics and it would be great to be able to have those follow ups of one year later where where does everything stand what progressed what didn't. That's a good thing for the intro I hadn't thought of that for the agenda Tracy very good I'll put that in. Thank you. That's one was 2021 planning, basically what we discussed in the previous meeting to just summarize what would be our main items on the roadmap. I've never actually made it to one of the contributor summits. So, when you pitch the idea of doing it, you know, the concept or sorry, pitch the idea of, and the suggestions of people to do them know that's backwards. He suggests the topics that people might want to do is what you were talking about. I actually really liked the idea of doing the communication channel I just don't know what that means. And I don't know if anyone like I don't know if you can, if you have a better way of explaining that so that we can get more people to do them, because there's probably a lot of people like me they're like, Oh, I've never been how do I get involved. Good point. And so Gavin, if it's okay, let me take that up with you. I'll try to outline it in the in the document here. Frame in what I think is a rough agenda and then I may ask for some of your time one on one to help me refine it better so that you as my first test can tell me mark that didn't help me at all I need this other information. I know I could be dropped in last second and be fine because I'm one of those people that can do that. But I suspect a lot of people that are not like me so I'm totally happy to be here getting big and provide feedback where I can. Perfect, so I will I will engage with you for that because that I wasn't sure that the communication channels topic would be selected, but I thought you're a great candidate for that would love you as my test drive even if we don't do that topic. You're a great test drive to see that I get the right instructions. We'll do that. And once you settle on dates, feel free to let us know at CDF how we can help promote it and just make sure folks see it and join in. I have not seen any objections to my first preference so I think I'm within a few days of declaring that February 23 through 25 are the dates. So you say first in the list not first chronologically. Right, exactly. First in the list is my preference. It makes sense to do some more time. Right. And really that's, I think all like that was the general concept is there and specific ideas for topics there's a documentation track that I've inserted that the documentation CIG is actively working to prepare. I think there's a concept that I'm not sure how to express it yet which is securing the delivery, securing the delivery pipeline, if you will, which is sort of a combination of security and infrastructure and release. And I'm still trying to work that up in my mind. I'm open to others having ideas about how we might talk about that and how we might plan it. There is an email read about that. But it's mostly about the delivery pipelines. Right. Right. And then there is a, I drafted a security track that for me wasn't so much about pipeline as about general security topics and that I think securing the pipeline is probably going to get more interest and more attention. And that's really set aside the notion I had of a security track and those, those are all fine. That's why this agenda is there is a rough draft and we'll continue to refine it. And that's, that's really all that I had on the topic for contributor summit. Great. So, what are you planning to do it mostly like what platform are you using as a zoom or you're going to experiment with anything new. Which is at least my assumption is that the, the opening and the closing will be zoom sessions. And I'm assuming most of the sessions during will also be zoom, you know, most of the tracks will be zoom. For instance, I'll probably put the documentation track on my personal zoom account, just to make make it easy for me to administer. And the, the opening and the closing will definitely use the Jenkins the CD foundation zoom account. And one of the, I guess one of the other observations was that the results of this may be a good topic to do our good series of topics for Jenkins online meetups to summarize what comes out from this I'm not sure we would make the concluding session and online meet up as much but some of the other things probably are great topics for an online meetup as we're making progress on them. Generally, it's fine to post it there because it's online event. Okay. So anything else about the computer. So, again, thanks to mark for organizing it. Yeah. Okay, so the last topic we had in the list is 721 planning. So basically follow up to the topic we had at the previous meeting where we discussed your items. And then we had is your contributor on board in the Jenkins security, you became a part of the contributor summit. Then we have six communication channels and terminology. So this what we discussed as priorities. So, I wonder whether we see any other priorities we would like to facilitate and to highlight the fun. I didn't I thought the list we assembled from last meeting was all was sufficient. I haven't found any additional ones. The consolidate communication channels actually fits nicely with the topic that I put for Gavin on on on a possible meet or possible contributor summit topic. And I also don't have many topics to it. So just wanted to say thanks to everyone who contributes and who wants some time to drive the community events. Yeah, one thing I was just going to add I see the point about working closely with CDF. I think to maybe just try and facilitate that, as we're also kind of doing our planning for the year. At the moment is maybe at the next board meeting. Well, we'll have a survey, which we'd love to form out to to maintainers and contributors, and just hear individuals feedback on what programs of CDF are useful, what people are aware of and what other things like Jenkins folks would like to see from CDF. So, yeah, maybe at the next governance meeting will bring that along and provide a link and ask that you share with the community or certainly feedback from the governing board so we can plan accordingly. That's definitely a good thing. And maybe one question you're mostly related to advocacy and outreach is what is the plan for events for the next year. Because we still have a few topics hanging, for example, meetup.com and other things. Yeah. Are there any plans to get in there? They are rough ideas that have not been like I don't know when we'll prioritize them. But I think the general sentiment is for existing meetups which are happy and kind of active, then they can keep using meetup.com, any meetups that are dormant, we will at some point want to get those kind of cleaned up. So two events were likely to kind of follow CNCF's lead and switch to Bevy as a platform. So we'll be encouraging anyone who wants to adopt it. The folks who are using it says there's a bit of a, like it's a bit of a step to transfer meetups. You know that will be optional but folks who want to start new meetups or kind of meetups focused on a slightly different angle. It's pretty good and I hear it's got some really nice features just for community building and bringing folks together that are good for this new virtual world. I think you said that we don't really have a clear picture of why not timing will be around that there's a bit of focus now just getting all the CD con planning done once that's in a good good state. I think we can afford to focus on on the meetups. Let me drop you a link to think is Bevy. Early in the year. Oh yeah. Bevy. Victor. I don't know what the phonetic for why is. Yeah, who. Yeah. Yankee Yankee that's the right one. So it's not a part of the Linux foundation ecosystem right. So, oh, actually that reminds me. The LFX. I don't know if folks have seen that and that's probably a conversation we should have with the Jenkins governing board. So links foundation has this set of tools that and some of those are company tools and some of those are project tools. They are I think launching it imminently like relaunching it even though the tools have been around for a while, but we'd love to have a conversation about like Jenkins on these tools. So let's see as part of that sweet. There's the insights, which you know Jenkins already has a page but we need to kind of sync with you to work out if that's useful or if there's stuff you'd like to see there. And then there's a link to community events and under the hood that's just going to be baby. I was asking because yeah, it would be the next foundation tool. Yeah, so that I think it's got a you can like list it so. But yeah, I think this is something down the road, I haven't really dived into it too much so that's like at the moment I could funnel any requests straight through to the team. But I think there's going to be lots of powerful things there for communities to take advantage of. So if anybody does want to start looking around and playing with stuff. We love to kind of work with you to map out which, which bits you care about which bits we should make more useful and and kind of get that feedback to the product team, working on it. So I'm definitely interested Tracy both in the insights because I still I continue to use their their metrics to decide how we're doing, and I'm very interested in the security thing. So, so sneak looks very interesting and so sneak you also discussed the last meeting when you're talking about security. So it's definitely something we could include in our pipelines, especially since, yeah, they scan us anyway, and you're taking the numbers, I have something to say but yeah. Yeah, I think definitely we've had lots of communities feedback about the way the security stuff is presented so it would be good. And we submitted the request security scans we removed but then they came back. Okay, interesting. So, yeah. But yes, Nick and generally is definitely useful for us. And we can make it a part of our pipelines. Yeah, also for us easy silly is useful because our current silly processes. Firstly, it's, it's still reliant on the SPI. Secondly, it's semi broken and hard to manage. So, we would definitely could adopt the mentorship crowdfunding we already do it. Yeah. And, yeah, what else. There were models before, maybe somewhere on the top. We're already registered with their crowdfunding solution right that's the. Okay, great. Thank you. Yes, so crowdfunding space there what you get if you go to Jenkins say you're the need. Yeah, that's our collected last year to. Oh, you still go to meet you. I hope it redirects so like. Yeah, I thought we fixed to that. Yeah, looks like not. Basically, you can. It still refers to this commune fridge but generally it's affects crowdfunding now. Great. Okay. You can see that we have some money actually in the coffers. So just in case we just walk or other things. I asked a little bit about this last time. But is there APIs for this? Can we make this public on any of this data public on the website? Yes, actually, they should be because we're also looking to redo the CD foundation. Website and I have been led to believe we can kind of pull stuff from LFX. And particularly the insights. So I was specifically talking about crowdfunding, but the crowdfunding. Yes, if you want, you can shoot me an email and I can try to find out. Any, let me know the specifics of what you want to pull out and we can feed that into the folks. You can see the projects are doing quite quickly there. Especially once you promote donations. We don't promote it heavily because we still have no straightforward plan of using the donations. But yeah, we could do that. A lot of donations come from small figures, which is good. Okay, anything else for today? Okay, I have actually three small little topics I was thinking about as we went through. There's a kind of doctorate this one. So there's a thread this week about on the dev mail list about people doing one off releases of plugins that are maintained. I think we should probably get a formal policy involved with that. So we had a discussion about the last contributor summit. The idea was to have a kind of file. Somebody call them Jenkins angels or whatever but actually just people who can release a plugin is some public track. But without being 20 years. So I guess it's something which falls into this category. And then wait. So there was one where I think it was the GitHub pull request builder this week. No, specifically like I'm, I was against it. I documented it but I was against another people for it. If the plan is to allow it, I think it needs to be communicated in that in a normal in a like formalized way. This the discussion. Should I do it shouldn't I do it type thing is kind of weird. Yeah. Basically, you have no policy which would allow anyone to release a plugin without becoming a maintainer. But historically, it hasn't been a big problem because every time we end up is taking ownership to do it release. So if we change the policy, it would be helpful. Yeah, I'm, there's definitely good and bad on both sides of the argument, but I do think we do need a formal policy for this. And then the other. Well, no, that one I'll do with the docs. I guess the other things this was. Yeah, I don't think it's a government issue, but because we did the video this I just got another Twitter alert that reminded me did the video last week with cloud is TV. Do we want to start making sure that any of that kind of marketing is is live on our blog, you know it's done by the other company. And then do we want to make sure that our blog gets auto. I talked to again it's probably an advocacy thing but I talked about earlier. Getting like RSS feeds into the various channels or into the Twitter thing so that we make sure that we're making noise or possible, because I saw again on the threads about Jenkins 3.0. We're having a marketing issue. We don't make enough noise about Jenkins and I don't. I don't feel that's true. I think we make a lot of noise but I can see the point of view where we're not doing it. So do we want to make more noise. I'm not very active at the moment. No, yeah, I was pushing it for a while. Yes, we should do slightly different tasks and no time. But yeah, I think that it would be really important. So at a minimum and this is again this might be a different city. I'm going to try to set up a bot that takes the RSS feed from Jenkins.io put that into the Jenkins getter channel. That way it gets a little bit more ice. Do we want to do the same with the Twitter as well every time a new Twitter post goes up we put that in that thing. We had that it wasn't very efficient, but it's definitely more efficient than no post at all. Yeah. We basically had the auto automation which that are implemented. It was dormant for a while it got recovered in 2019. For a while, but the rest of it's your handcrafted. I'm not talking about automating adding tweets I'm at it I'm talking about automating sharing them with the other channels. Okay, so I'll do that. If everyone complains will shut it off it's easy to do so. And then at the top of the document you had open, you talked there's a link to the Jenkins meetings, IRC channel is all that data on the top still true. You mean, I wish me that documents very top. You have links to the document that. Yeah, because I noticed this page is. There's a bunch of small things like if you, if you're later I'll make a PR for it. Okay, she wasn't even the page looking at but if you go to the actual document you had open the actual docs. Right there it says links to this document and then direct IRC web chat I see we're not using that anymore because no one's in this meeting pre node. Yeah, okay, so I'll make a PR that updates some of the links, because I was trying to find this document earlier and struggling so. Yeah, thank you. I'm good. Okay. Any other topics. Thanks everyone. Thank you. Thank you so much. So next. Oh, yes, oh, just started one topic. Next meeting time is two hours later. My apologies. I goofed. I'm sorry that I made that mistake. I will correct it on the Jenkins calendar immediately after this meeting ends. So mark that will be our new meeting time going forward or correct. The new meeting time as agreed. And then this time. Got it. And sorry, I didn't correct it already. Okay. Yeah, thanks for doing the poll. All right. Thanks Gavin. Thanks everyone. Bye. Bye bye.