 Welcome everyone. This is the Jenkins governance meeting. It's June the 16th, 2021. Thanks for being here. We've got agenda items, including news, contributor summit, deprecating Ruby runtime, Jenkins funding updates, plug and end of life policy possibly. I had put LFX mentorship budget, but I'm not sure I've got anything to talk to it and discourse any other topics that need to go on the agenda for today. No, that sounds like we're done. Okay, great. And let's keep it brief and to the point. So by way of news, contributor summit is coming June 25. We'll talk about it in more depth later in this meeting. End of the month, we've got Jenkins 2.289.2 coming. And we've switched from FreeNode to Libra for our IRC chat system and the discourse proof of concept is ongoing. Can I just ask one question regarding IRC? If my understanding is correct, we updated the documentation on Jenkins that I knew, but we did not send the blog posts. So most of the people are not aware of the fight that we are moving IRC network. I don't think anyone who goes to FreeNode will be checking either their website or the blogs. So I mean, it's good to do, but I don't think anyone, they won't change anything. I know at least some people with cloudbies from time to time go to IRC channel to ask questions. They were surprised last week that nobody was answering questions anymore and they did not follow all the drama around FreeNode. And so that's what I mean that we shouldn't write a small blog post. I mean, it doesn't have to be really big. Just like, goodbye, FreeNode is dead and we are moving. Yeah, no, I'm not saying don't do that. I'm, oh, like did, excuse me. Oh, I did comment on Twitter about it. I don't know anywhere else. Sorry. No, it's common on Twitter, but there's no blog posts and all the documentation was updated. So for about half there, I could annoyed it half done tests. I also don't know how much we wanna support IRC anymore because it's getting pretty dead. Yeah, so it feels like no harm for us to blog the change. I'm happy to do something quick and easy. Any objections from others if I do that? I think that would be nice. I remember that we wanted to discuss about switching from IRC to something else. I think the first move was first to leave FreeNode and because of FreeNode, next, I mean, we can then introduce a discussion about if we want to use metrics or something else. Great, but yeah, at least for now, we just want to be sure that we leave FreeNode and everybody's aware of that. I think, yeah, say where we've left, throw in a comment saying there's also Gitter and there's also Dispers. Great. Don't direct them there, but that way if there's only 10 people in IRC, they have other options. Right, okay, Gitter and discourse. Good, all right. I'll do it, you should see that later today. Okay, Gavin, anything you want to report for us since we've got you on the hook there for discourse? How's it going or Olivier? My perception is it's just great, what? So, Gavin, maybe you want to share that? Yeah, I mean, there's not a lot to share. It's going pretty well. We have, I don't know, I haven't looked recently, but like 40 or 60 users, about 20 of them are posting stuff. So it was pretty good. As Olivier pointed out in Twitter, I really like to show off category because a lot of people are posting all kinds of things like the books they've written and upcoming plugins, Tim did the blue ocean thing. So generally I'm pretty happy with the way this is going and I'm hoping we can cut over more and more things to it because it does work really well. Excellent, yeah. So here's a trend chart posting from Olivier. All right, great. And I think we'll cover a little bit more about discourse, the regular, the contributors of it anyway. Great, all right. That will be part of the decision. Okay, last item of news, not a big news item, but just be aware that my thing that was going to take me out has been canceled because of health quite concerns. Next topic, so contributor summit, Olivier. Sure, let me share my screen if you want because I would like to share the schedule. You bet. So if you're new to the discussion, so next week we'll have a contributor submitted and we are still discussing about how to organize today. We want to obviously add that some major changes in the Jenkins project, I mean, initiatives that are running right now. We would like also to have a decision in the, so let me share my screen so you can see the schedule first. Where is this? I hope you can see the screen here. So yeah, before I introduce what the schedule is, so we would like to cover different kind of area. We would like to highlight project updates. We would like to update highlights, seek updates. We also want to take this opportunity to discuss major changes that we want to bring to the Jenkins projects. That's something that we usually do during the contributor summit. And we would also like to save some space for highlighting some specific work like on a specific plugin or whatever. Something important to keep in mind is the time is aligned with the Silicon, which is East US time zone. So I created a draft for the day. So the first thing is obviously because there are a lot of people on different time zone. I just put the major on time zone. So just to help you identify if it's possible for you. And then we would have four main categories. The first one is project update, as I said. There you can expect updates from board members, officer of the Jenkins projects. I was thinking to have a contributor track. Initially, my understanding was we were on the PDT time zone. So we were with West Coast, which was a little bit more difficult for people from Europe, but we don't have that constraint anymore. So something that I would like to suggest is we first do the project update, then we do the seek updates, and then we continue with the contributor track. So we have more people from everywhere in the US. So that's the main categories. And then we would finish the conference with various presentation, many different topics. We can have a presentation with let's say Jenkins, Jenkins X, open to a pedometric plugin. We have many options there. What I need right now is to finalize the schedule. So I'm really looking for feedback on this schedule. And also I'm looking for people to either talk or leave description. So for instance, in the case of the project update or seek updates, the idea is to have someone who can do a quick update, five or 10 minutes. But in the case of the contributor track, the idea here is more to be a moderator and to drive a discussion. So we would like to have as many contributors interested by those specific topics. So those topics that we identify, I mean, you can still change those topics, but one of them is plugin end-of-life policy. Several people bring, that they would like to introduce, that's a policy to deprecate some plugin. And I think that's a good place to discuss about that. We always a session on contributing to Jenkins. Mark will lead that session. He does a pretty good job on that area. Some people reported that they would like to discuss about how to upgrade Guava in Jenkins. I'm not a Java developer, so I cannot go too much into the detail there. But I know that Baptiste was interested to lead that discussion. Alec requested a session on the outreach program that we would have in the coming months. It's something that I have to identify if someone else can take the lead on this one. We would like to have a discussion on Java 11, Java 8, and obviously Java 17 because Java 17 will be the new test. Java 8 is released in September. So if you are interested by that topic, feel free to manifest yourself. And finally, another session that I would like that I would like to cover is governance because we will have governance around October and November. That would be the third time that we organize the election on the Jenkins project. We organize two time following two different processes with different kind of results. And so I would like to go back in time to understand what we did well and what we want to change based on our last two attempts. So those are the contributor tracks. If you have any other topic you want to bring, feel free to manifest yourself, you still have one week to change. Seek updates, I'm still trying to identify people to do an update here. I'm trying to convince and try to find a way for people from Asia to participate as well. So yeah, I'm trying to be to find a solution for them. And yeah, any question? So I'm interested in the Java 11 topic. If Tim doesn't feel like leading it, I would be willing to lead it. I don't want to let that one drop from the agenda. Okay, good to know. Thanks. Question for you, Ulavik. And Kevin, if you have a specific topic that you want to cover during the contributor summits, yeah, perfect to manifest. We also have to work on the slide for the project update and the seed updates. Yeah, I myself can't participate because I have lectures the whole day. And that's almost this, the whole time slot is during my lectures. So I'm sorry that I can't help here. At least I can't speak. That's fine. There are always solutions. So it's also 6 a.m. for me. So I... For you beginning, I know it would be difficult. Well, I mean, on a good day, I get up at like eight. So I mean, I can get up early, but that's getting for those two days. Either way, I'm not totally interested in presenting anything right now. So if I don't have to, I'd rather not. Okay, good to know as well. Yeah, that's fine. I just needed your confirmation. Otherwise, we have another Google Doc. Do I have a link to this one? Let me see if I can find it's... So I'm also looking for feedback on this one. So... I'm gonna put the link to the agenda. So here. So what I'm looking... So we started when Google Doc to explain the more in detail in a Google Sheets to have a big picture ID of what we want to do. If you have some ideas for the unconference part, so let's say a small presentation on Jenkins or no people who would be interested to participate, I'm looking for speakers in the last session. So right now we have... I'm looking for Jenkins and Tecton interoperability. I got confirmation that we can have a session on Jenkins and Jenkins 6.3. Jenkins and the open telemetry plugin and the work done by Elastic. And yeah, I'm looking for more to pick here. I think that's all for me on the... So Olivier, one of your questions was okay to... Is it okay to switch the order as you proposed? I'm just gonna call for a vote. Any dissent or plus one from everyone please? Is it okay that we take his agenda as he's proposed it? So the suggestion to move the contributor track a little bit later is that it will be easier for giving to participants. Uli? Fine for me yet. Okay, fine for me. Randall, thanks for joining us. Want to express your opinion? I'm Eastern time, so I'm usually up at five o'clock in the morning to feed my cats, so time is not really a problem. Great, all right. And Gavin, you okay with that? Yeah, I'm okay with that. I don't know how much I can participate anyways, but yeah. Understood, thanks Gavin very much. Okay, so we've got a plus ones all around for the schedule as proposed. So that's great because then tomorrow I finalize the schedule and start promoting it. Excellent, thank you very much. Any other topics we need, let's see, a draft email, invitation email has been posted. Olivier gave some feedback there suggesting we should use discourse as the contact point. I'll create a new topic under the contributing on discourse so that people can reply there. So that way we'll try to motivate them if they have some issue and they receive the invitation email, they'll go to the discourse community and post their question there. So yeah, that's one of the things that's still to be done. And another discussion which is happening at the moment is how we manage the swag and how we send them swag. So I think we still have an open question on who will pay for the swag and how much we have to pay. It's difficult to know in advance how many swag we want to send. But yeah, I don't have the answer. I'm just sharing that we are discussing with Alisa and the CF and other people. Great, thank you. Thanks very much. All right, anything else on contributor summit? No, that's all for me. At least for now. Okay, the deprecating Ruby runtime, I'm not sure there's anything we need to report there. We had an item for Daniel to continue reviewing it. I have to review it. I assume that I've not seen anything indicating that's been reviewed. So I think we're still on hold there. Jenkins funding updates as far as I understand it, Gavin and Evelina both have access to the, to the funding system. So that's in progress. Nothing other that I need to report unless someone else has something they need to report. Okay, great. And I understand we've got plug in end of life policy. As a topic for the contributor summit. I don't think there's anything more we need to discuss here, except being aware that it'll be a topic at contributor summit. Prepare ourselves. Be sure we're ready to discuss and have good plans. If it hasn't been released in three days, it should be deprecated. Okay. Thank you, Gavin. This is continuous delivery. If you don't have to download it every five minutes, it's dead. Okay. Thank you. I love an aggressive policy. Boy, that would be a winning aggressive policy. Okay. That one scares me. We haven't done an update in four months. I understand Randall. Yep. That's there. There are plenty of surprises to be found. I think all my plugins are at least a year. So yeah, I know. Okay. Last topic I put on the agenda weed, I think already discussed briefly, but anything else that needs to be shared with regard to discourse and our progress there. I think it's working great. People can register an icon can ask questions and participate. We already saw nice demo. In the show off section that Garrett created. I get it. Giving created, sorry. Yeah. So I think it's working well. The only thing that we may do. You may have is more option. Like being able to use Twitter. Or whatever. That's something that we can improve in the future. But for now, I think we already have something working pretty well. Yeah, as much as I think the single sign on is with Linux is a good idea. I don't think very many people have Linux foundation accounts. I only got one in the last year. So I, the more options we have for social logins, the better. I'm going to send out. Another blast old email list next week. Probably maybe a week after. I want to make sure that people have time to not get it too often. And then I've been talking to advocacy, CIG, UX, CIG, and. What did I say the other one was, oh, and Mark was talking about doc CIG about possibly moving the majority of the communication to discourse to try it out. So I don't know how much we're going to do that. But I. Oh, okay. That's a zoom be having the dots. Yeah. I don't know. Like I said, I don't know if they're, they're. Really said UX is interested, but, and Mark said docs is interested. We haven't moved forward to any of them yet. And would that be done with a category? How does, how, how do you envision that working? I don't know. Honestly, I don't know. Okay. Because this is one thing. What I'm a little bit missing currently from this course. I'm opening this web page and. And there are all messages and what I would like to expect is, where is the UX CIG button? And then I see all the message from there. So there is a category. So maybe, maybe, maybe I can show. Mark, you can show your screen. Yeah. And I can give you a quick overview. So Olivier. Go ahead. Yeah. I'm doing it. Sorry. Can you see my screen? You should. It needs to be, I'm going to get rid of that better. That better was an accident. So when you arrive, when you arrive on community, that's usually the view that you see, you have, I mean, you, you see the active discussions. Something that we, we started to try to understand. I mean, I mean, I mean, I mean, I mean, I mean, I mean, I mean, I mean, I mean, I mean, I mean, I mean, I'm just going to talk about the discussions. Something that we, we started to try to understand how we do is the category. So we can organize discussion by categories. That's one way. And so if we think of the categories, you have different, I would say major categories, that's something that we started working on. It's still, I mean, we still have to improve, but for us what we thought was to have one major category with Jenkins use, Jenkins. Community. for language group, Spanish, French, and so on. And so for instance, if you go to contributing, we could add a subcategory. So right now, we only have in the subcategories infrastructure and GSOC. So let's say we could imagine UX if you want. And then when you create a new topic, you just start a discussion and then can specify the different categories that you want to have. So you can, for instance, specify the top category which is contributing. You could specify contributing infrastructure. And the way it works is, as a user, you can have filters. You can say, I'm uninterested by the topic in infrastructure and the contributing. And so it's really easy to identify what you want to do specifically. So that's how it's working right now. Does it answer your question about having a UX category? So the biggest challenge that we have at the moment is to have enough categories so we can organize the discussion, but not too much so people are lost in the different categories because you can have level one categories, then you can have level two categories, and level three, and so on. You don't really have a limit. It's just like level one and level two is really easy to see from here because the top level is the big box using Jenkins community contributing. The level two is, let's say, infrastructure, GSOC, announcement, event. So those are the blue box that you see. And then level three categories, it's a little bit harder to identify quickly. Oh, no, so I know we have the calendar enabled. So when you create your events for the contributing summit, you should make sure that the post has a date set to it, the hamburger at the top right. Okay. That way it'll show up in calendar so we can start seeing events that are happening around as well. Okay. Thank you. Is this course only available in the browser? No, they have an application for Android and iOS. So it can also work. But not on native, but not on Mac OS or on Windows and Linux. It's just... Yeah, I think it's only web browser. They have a very rich API, so I would bet you someone has made a client for it, but it is a web app. So I've been looking. I mean, we can create a new, a new, actually a new wiki topic, where people can add clients and tooling their views. So that might be a good idea as well. Yes, someone should make a Jenkins plugin for that. It had occurred to me. I'm going to make an RSS plugin soon. So when I do that, I might make one that we can, I don't know, do something from Jenkins into discourse. So yeah, we can do a lot of things with discourse. We are still at the beginning of the process, so we are still learning. And so we are open to that as well. It looks like there's some activity on GitHub around it. Around it? What do you mean by that? I assume you're muted speaking in a Jenkins plugin. Sorry. Yeah, there is some activity around application building for discourse on GitHub, but I don't know how far it's gone. And I must say goodbye. I've got another meeting to go to. Goodbye. A pleasure seeing everyone. Finally putting a face to the names. Thanks, Randall. Thank you very much for joining us. I'll try to do so again. Great. Look forward to it. So we have covered all the topics that I had on the agenda. Are there any other topics? I don't think so. All right. There is one last thing that I would have loved to review before the contributor, Semik. I mean, that's a roadmap that we use in Jenkins.io, but I don't think we'll have the time to review that here. Yeah, I think we would want a larger group and a more detailed review. How about we propose that asynchronously? Is your worry that the roadmap may be outdated as published to Jenkins.io? Because we reviewed it two or three weeks ago in governance. Okay. So yeah, I have to do the check. So maybe I was wrong. Okay. I just wanted to be sure that it was today for the contributors. All right. Then I propose that we stop the meeting here. All right. Thanks, everybody. Thanks to you. Thanks, Gavin. Bye.