 Hello, this is the regular Jenkins governance meeting. Today is January 13th. We had a break again Christmas holidays, but now we are back. And there is a number of topics we have to discuss today. Do you see it? Yes. So we have a few news and we have a planning for 2021. Mostly defining key priorities and other things. We started doing that for the new year blog post. But yeah, this is a good place where we can discuss what else we would like to see happening next year and what would be the priorities for the governance board. In addition, yeah, for the information, I dumped feedback we've got during the elections about what would be the priorities for the board, etc. So you can take a look. This feedback has been filtered. So there is no sticker requests. But in general, there is some summary and people will mostly expect us to keep driving initiatives, to set up technical direction, and of course, to keep expanding community and getting more contributors involved. Okay, so let's go to news. One fresh news that today we had a security release. The security release involves multiple fixes in the Jenkins core, including XSS, and where there's a serialization error, potential past driver cell and access files. So if you use Jenkins, please update. And we have both LTS and weekly released. So all the packages are available now. Other news that we have FOSDOM as usual. So this year FOSDOM will be virtual. We will have Jenkins developers stand there. And the CICD room, we will have a talk by Victor Martinez about Jenkins. And probably there will be more talks at the conference. So please check our agenda. And if you are interested to participate just by the Jenkins booth, it will happen on the weekend. And we will definitely have someone available. Any other news updates anyone would like to share? Just a reminder, we'll be using advocacy and outreach to encourage people to assist just with the Jenkins developer stand. And we're going to send some directed emails to specific individuals asking if they'd be willing to help us. I gave a list of possible of some suggestions to Alyssa Tong and she said she was going to reach out to them. Also speaking of that, there is a message in the developer mailing list about the budget and if I recall correctly, maybe an advocacy and outreach. Yeah, it's advocacy and outreach mailing list, I believe. So if anyone has ideas about what would be sponsored in terms of events, et cetera, please bring it up in this thread. There we have some Jenkins project money, but well, this is really to sponsor community marketing activities. And yeah, this is a great opportunity. Once we're completed with Bosdom, I had a chat with Alyssa to start seeing about scale. I believe scale will be virtual this year as well. I haven't seen any mention of scale on their site. So I am interested in that, Markey. Thanks very much for doing it. I will make sure everybody is in the loop on that. But if scale happens, it's great. Okay, any other news? It's a Christmas break. Okay, then 721. You have a few topics. In the message about the governance meeting, I wanted to specifically talk about the contributor onboarding and security. But yeah, this is a place where we can discuss other topics. If you have anything in mind, because we still have documentation, we still have events we need to organize and other things. So we can just discuss what would be the priorities. Why I put contributor onboarding to the list is mostly because of this graph. We've discussed it a few times before. But this year, when the COVID situation started, we have seen quite significant deep in terms of company contributors. In June, we sent a request to the Linux Foundation to verify whether this data is actual and my understanding that yes, it's actual. So how it gets generated, there is in the bottom link to the file. And this file is basically JSON. You can download it from GitHub FS. It's quite big, but I'm not showing it because it includes emails in plain text. Well, emails which people share in GitHub profiles, but I still want to show that on the record. So you can take a look and but I verified a number of Jenkins contributors and basically it represents the list correctly. So yeah, there are some contributors listed as individual contributors, but I believe that this graph is relevant. Oleg, in terms of my interpreting this graph, so the darker color that's in the back is associated with the axis on the right. That's developers. And the lighter color is associated with the axis on the left. Yeah, it's right. Okay. Okay. So basically, if during the momentary period, 20 days, there was one contributor from the company, it counts. Okay. So what? Compared to other projects, we have a big number of company contributors, but yeah, there was significant decline. So I tried to do some analysis. Firstly, we had less hosting requests for plugins. And yeah, it's natural for companies to create their plugins for integrations. It's not like we didn't have them at all, but compared to the previous year, we have less of them. And yeah, secondly, it's contributing patches back because yeah, it's one of the ways how we get the company contributions as well. You run a Jenkins instance and yeah, something breaks, you submit a small patch, and basically you get into these statistics. So what it means is that you should definitely work on improving contributions and seeking contributors. And of course, it's also related to Jenkins promotion, especially for modern platforms. Because other adopters and hackers are the common personas who contribute better. Do you think it might have anything to do with all the new CI platforms that have been added in last year or so? Of course, there's a lot of them now, right? Yeah. Yeah, it's a case. And what it means for us that we should do better outreach to users for different platforms. And yeah, of course, this also has offerings. Now the situation becomes more complicated in terms of attracting contributors. It's not a surprise. We've been discussing that contributor summits before. But yeah, we still should work in because Jenkins is used in so many areas. And yeah, there are so many sources of potential sources of contributions we cannot get. Because yeah, of course, many people would move to SaaS and to other offerings. At the same time, many other companies become more open to open source contribution. So it's opportunity for us to facilitate contributions. I've definitely seen companies that previously were not doing any continuous integration looking towards it. So I think there is still an opportunity for us to have new people arriving, even with the increased competition from SaaS providers and others. Yeah, but it's we need to we need to actively work on board contributors. Derek, and here come events and other activities. So again, you can split in October first, October first helps here, no doubt, getting individual contributors. I believe it helps less these company contributions, though particular initiatives could help as well. For example, targeting custom platforms is one of the areas which we discussed before multiple times. And I think you should do within that. I got kicked out of my Zoom account. So I think it's one of the priorities for the next year. And yep, it's not like anything green. It's what we need to do. And yeah, that's why you have links going for we have an opportunity to focus on that. I think it's I think the corona problematic is, for instance, in Germany, nobody has really time for anything for free time. So in my spare time, I need to care for the children more. So maybe this is also a problem. I don't know if others also have the same problems. Definitely. Yeah, it's definitely this, I think. So just when I look at my contributions, I had, I think three months, no release of my plugins, because I need to make this and that and then care for the children. And so I think we need to wait a little bit longer to say that everybody is leaving Jenkins. No, I don't say so at all. No, it's, it's proportional looks like the number of individual contributors is going way up while companies are going down. So it's companies are not helping out. It's not that, yeah, not even not helping out. That's the wrong word. Yep. Any contributor has full freedom to do. But yeah, what it means that, for example, your student on the lockdown, then you can go participate. But yeah. So that is a good observation that the, what looks like the average number of individual contributors is roughly the same from 2019 to 2020. But there is a, there is an observable difference between contributing companies. So do we need to consider a way to reach out to companies to encourage them to motivate their, I don't know how we do that even, but I think, Oleg, I think that was part of your point was that it's not, it's individual developers were relatively flat, but companies are the thing that's down. Yeah. So firstly, it's stewardship for contributions because we know that for many plugins basically contributions and get stuck and providing the family feedback. Assistant to this, getting changes in is one of the key opportunities to onboard and retain contributors. So this is one area and second area again, focusing on cases which are important for bigger contributors. So for example, yeah, finally making official armed support and docker images, et cetera. So these are cases where we could make a significant difference. Well, go ahead, Marky. One question that I do have is with the list of, are we going to create a list of action items for 2021? I think we can just dump it here in the meeting notes. Okay. About what we could do because I have some ideas in regards to corporate outreach because we've seen this, you know, in other open source projects and I've seen sort of ways they've worked on that, that I think I could apply here as well. Can I just have a link to the notes? I can't find them. I'll get them to you, get you the link separately, Olivia. Yeah. Anyway, we should keep doing all the things. But the company contributors are important. At some point, we had a discussion at the UPS World Contributor Summit, how do we retain and increase company contributions? I can also pull the meeting notes, but I think we should dedicate more time to that. And do you have already an idea how to proceed on that topic? Because something that we did in the past was to identify key areas that third company want to promote and maybe trying to find a way to promote those areas. So for instance, I know that Rodat is interested with the Jenkins community's operator and this is going to accompany, can't remember the name as well. So maybe it is the kind of initiatives where we can help. Yeah, that's one of opportunities. So cloud means Jenkins is there where everyone is interested. Platforms are there. Cloud providers as well. Sorry for the interrupt. That's fine. We can also fix the blog sharing thing because right now I realize I haven't been reading the blog because we're no longer posting to Twitter. I realized that early last year, but at least then it would encourage people to post because then they can get a bit of traffic. Yeah, it's a manual process. Well, I've been spending significant time over the past year to just 15 minutes on the morning to capture a few tweets, etc. and schedule them for repost. Okay, but now I don't get to that. But I mean, this is something we could also just automate, right? So every time a new post goes up, shove it into LinkedIn and shove it into Twitter type thing. Yeah. Yeah, Alyssa is doing a great job for Jenkins in the way. But we know that there are more stories being shared. You just search for these cases. Yeah. Anything else on this topic? Again, it's something for us to consider. Contribute to the on-boarding has been always on our list. I think that this year it's just important to keep doing things and expand. So, Oleg, is this a place where it's okay to note that I'm going to try to take the lead to convene a contributor summit either in around the FOSTA time or in the March time. I'll start the proposal. I've got to still send out the draft proposal. I was thinking advocacy now it reaches the place. But just so people here are aware, I think we should do a contributor summit in what Northern Hemisphere might call the spring. FOSTA February or March, that kind of time. It definitely won't be before FOSTA and it won't be during FOSTA. So, do you plan a contributor summit or how we used to do it before when it was rather a user summit? I was thinking contributor summit but I'm open to input there. That's a good question. I hadn't thought of a user summit. I was framing it more around the kind of event we did last year after FOSTA in Belgium where it really was developers and people who were contributing to the project. I'm open to suggestions. I would also be more interested for the contributor summit because the FOSTA, the booth at the FOSTA allow us to highlight improvement in the Jenkins project or at least things that we want to promote. So, in terms of reaching to users, I think the FOSTA would be a good place. In this case, we are more interested about how we federate about all the different initiatives in the Jenkins community. So, to me, I would be definitely more interested for a small contributor summit than a user. Also, the other reason why it would be easier is because, depending on the technology that we would use, I mean, it's easier to target a smaller audience if we want to have something interactive. So, we have some account. We can support breakout sessions and other things there. So, up to 50 participants is what we can easily host. Yeah, after that, you will get more people participating in the same time zone. Right. And time zone is one of the complicating factors there. So, that's a good thing to note that I think it needs to be live and therefore, time zone is a challenge. But it's worth the challenge because we then have more communication. And yes, I think we should use breakout rooms. I've liked how they've worked in other environments where I've used them and I've been impressed at how helpful that is to do a breakout room. But something that we also have to keep in mind is since we are not in the same location, we don't have to do the contributor summits. I mean, the same day, we could split the contributor summits on different days and say, let's say on Monday, we want to focus on that area on Tuesday and this area and so on. And so, we have smaller periods where we have to focus and maybe it will be easier for people to participate. Yeah, good suggestion. Yeah, I agree. So, let's see how we're going to start, but definitely two time zones. Are two happening? It's in mind? I don't. I've got to start the proposal there, Oleg, so I don't have great dates yet. I'll suggest them through a separate proposal and we'll start that conversation by email. Okay, thank you. Also, just for the date, I would also not suggest to use a date closed or neither for them our scale because one of the reasons why we did that during first them or any other major event is because everybody was there at the same time. But on the other side, we already have plenty of things to do for first them and other major events, which means that it's maybe easier to just find a moment where it's more calm. Agreed, particularly since FOSDM in order to participate in the stand, I'm going to be giving time Saturday and Sunday and that'll make it more challenging for me to say, let's do something immediately after that. Yeah, I will probably ask for a little bit of gap time-wise between the FOSDM event and when we do this summit. Okay, so then moving on. Okay, so other, I think we should double down on this year is Genki security because all the recent events with solar beams, et cetera, there are much high expectations from all components participating in software delivery cycle. They've already some questions coming about security and I think that we should facilitate this discussion in the community and to see what we could improve. Actually, there is a lot of improvements happening. For example, last year I published some stats, so there were 19 advisories, almost 200 fixed vulnerabilities, but some of which were just disclosed and this fixed. So it's a quite high number and there goes two improvements. So now many plugins have dependable, including Potomac security scanning, Github for QL, mindset bugs and other components. So still there is an open question about what we could do more, for example, how we deliver to the components, how we help maintainers, how we grow security awareness in terms of contributions, because many common practices could be either enforced by tools or could be promoted and it would improve overall situation. So I think that this is a good conversation we should have over the next months so that we can actually define better practices and ensure that the key components are much more stable and they get enough attention, not only from functional standpoint, but also from security standpoint. It's a wholehearted agreement there, so yeah, there are definitely opportunities for us and I think that we can collaborate more. Yeah, there is a security team and security team is doing a great job. More members, they could also help, especially getting more vendors participating because right now we have basically only two vendors represented the security team and there is a lot more. So I'm not sure what exactly they deliver in terms of security or what it's always, but yeah, it's up to them. Yeah, so even if there are any particular ideas what we could improve there, I'm happy to discuss that, but it's one of the topics I would love to drink up on the mailing list. I could offer some help there. I have some insight into scanning vulnerabilities, especially using GitHub Actions from a previous life. This is an area that interests me as well. I never really had the time to work on that, in fact I also have mid-id's, so let's find some time. Thank you for the interest. It's probably worth, and I know I'm throwing it into other people, but it's probably worth putting up a blog post about this because it's one thing for the people who are already involved to get more involved, but this would be a great opportunity for a lot of people who are not involved to get involved. There's a lot of new security analysts out there that are really excited for a project to get working on, and then there's lots of security companies out there that could get involved and we could get our graph to go back up. Yeah, also there are formal opportunities. For example, last summer we got a CI batch and what it means that now we are potentially eligible to get access to tooling, pro-core infrastructure initiative if needed. Well there are tools like SneakAvailable there, and also you can probably even apply for an audit program. The audit program doesn't seem to be really active, you know, and we can also continue our certification because even if we have 100%, which we have 133% in Jenkins now, there is still 178% more we could achieve, and there is a lot of additional security practices which we could adopt, so of course we could have. So yeah, all this activity is also a good opportunity for us. Yeah, so yeah, this is basically our CI, and yeah, it's 100%, but for example, we can click on the golf level, and for example, the risk security section. Full disclaimer, we haven't fully processed that, so zero or five means that we just didn't process that actually. But yeah, you can see that there are some requirements, like using basically the graphic practices, which is slightly okay. Yeah, some software delivery requirements, protection from the middle, some additional requirements like security review within the last five years. Yeah, so of course there are some items we could consider for these levels. Here, secure development knowledge, the project must be secure design principle, we are applicable. Yeah, multiple graphic cardings. Again, this hasn't been really processed, so yeah, likely we comply with many of these items. I think we should keep this conversation, and that we should add more topics to the agenda, but yeah, my next step is to actually bring it up in the developer mine in the east and start making these other stakeholders, specifically with the security team. Okay. Are there any other priorities for the next year we could add to the list? Nothing for me. So the special interest groups, I don't know that they need to go on this list, but I think our special interest groups are good indications of places where we've got more work to do, platforms, documentation, infrastructure, but I don't know that we need to list those hero leg as much as just be aware that keeping our special interest groups vital and functioning is very useful. One of the things that I would like to see this year if possible is special interest group leads. Maybe it doesn't have to be all of them, but maybe they rotate in once a month they come to this meeting to give us a SIG update. That's an interesting idea. Well, and that's actually that's part of the SIG Charter, but I've been using write an email or write a blog post, but yeah, that good good insight, Marky. Yeah, it was a part of the original job for a bit at least every six weeks. Then you said that you would be rather doing it over mailing lists or blogs. Right now it's not really active. One thing for 2021 and it probably won't get dealt with, but it should at least get thought about is trying to consolidate some of the communication channels because we are spread out very, very, very thin. And it's interesting, we actually had a request this week for an info issue on the UX mailing list. We have people popping into a different SIG Gitter channels asking general support. I think we should try to at least consolidate a little bit. I kind of like the idea of maybe moving everything from mailing list to discourse, so it's all in a nice one spot or formalizing and saying, hey, we're dropping IRC from the official list or it doesn't really matter, but just consolidate. Yeah, I can't spell that up either. So I totally agree with you, even though I feel like everybody wants to use different tools. But the problem is that we let everyone use different tools, which means that the, so there are complaints that in the, that used to be able to talk to, quote, developers in IRC, but now you can't anymore because they're not there. And that's the problem is everyone's in different spots so that nobody's in any spot. Yeah, I definitely agree with you. It's hard to keep up on all the different challenges and communication tools and so on. That's right. Perhaps it would be beneficial to put out a blog post, just have to be a short blog post that basically is summing up, hey, the best way to communicate is through mailing list and this is what you do. You may get some people here, but you may not. Maybe something just as a reminder to the community, you know, the ways to communicate. This is why Matrix is the best. Everyone should use Matrix. Yeah. No? Okay. Yeah, I definitely agree. I mean, that's a great tool. Well, at least it closes the problem using Gitter because it's not. Yeah, it's definitely improved my user experience together. So as a non-Matrix user, would you be willing, Gavin, to do a demo sometime of how that works for you and what, because for me, I'm definitely not using that tool and would be interested. Is that something you're willing to share in terms of showing us how? Yes, but I don't think, I mean, yes, in the 2020 and goals thing, yes. I don't think it's really a short-term goal because I was going to take a little bit of time for it to solidify a little bit. I also kind of think maybe we want to look in running Jenkins's home server, so then that might be the way to wait for as well so that, you know, use your LDAP credentials or whatever else you log in and you get access to Gitter, you get access to all the chat rooms, they're all very easily searchable. So there's a few things I think it might be worth deciding, maybe not implementing, but deciding before we do a demo. Okay, thanks. Thanks for the clarity. But I haven't pushed in them yet because it's been a busy couple of weeks. So what else do we still have pending terminology cleanup? In this situation, it's significantly improved over the past year, but I think we should keep pushing that. Yes, I agree. Yeah, so we had two bumps, one October 1st, another one your UX summit, there was a lot of cleanup here in this time frame. Still, if you run GitHub queries, you can see a lot of occurrences, even in user-facing things. So we need to clean up. Anything else we would like to add? Nothing for me. I think this is basically to keep growing. So it's likely a foundation for the contributor summit. Yeah, definitely some initiatives we could facilitate now. And then, you know, there's things I want to do to improve the plugin site, but I don't have specific plans. I do want to make sure that, you know, again, super spreading out. So issue tracker is my big one right now. There's plugins, some plugins using Git, some plugins using Jira. I want to make, it's hard for the end user, but I do want to make sure that it is clear for the end user where to go. But I don't know if that needs to go on the roadmap. Well, some items could definitely go on the roadmap, maybe just keep on growing plugin site or plugin site 3-0 if you foresee any major changes. At the moment, we're, I think I'm good, but yeah. So let's see. But yeah, any of these gradual improvements finally help our users. So the new plugin site was really well accepted. Yep. And we're looking at the, between Tim and I, we try to share the stats every month. So it is kind of interesting to see which plugins it's really the big ones. I mean, Git is always at the top of the list. But it's not always the top top, but it's always in the list. Could we, could we maybe start publishing those via social media? You mean trends? Maybe once a month or every other month. Well, which trend are you, this is just a search trend, right? I'm talking about, so Google every month sends us a report to say what your top search results are. Oh, I'm sorry. I'm sorry. I thought you were talking about the plugin stats. I mean, the plugin, those are, I would say those are more useful to publish. I think the, which plugin is getting searched for in the most, it's probably less important. It was in docs. We have some stats about how many times a specific plugin is download. Yeah. So we could already, basically everything is available through JSON. So we just have to, to serve for every plugins and some visualization. Yeah. It's also in here as well. Oh, I didn't know you could actually get that in here. Yeah. The data is all there. It's all indexed and merged in. Oh, okay. That's awesome. Today I learned. Yeah. And if you go to the actual endpoint, the actual API endpoint, it actually has all the data as well. So slash API, slash plugin, slash checks. No, no. Oh, yeah. Same endpoint. Yeah. API, slash plugin, slash, and the single, singular. So plugins. Check plugin. Working a single plugin. Yeah. So it has all the data here as well. That's awesome. I can parse that easily. Yeah. Yeah. So it also returns basically. But yeah, better somebody to improve it. And then I think the plugins, I mean, we can go with later, Mark, but the plugins endpoint has all plugins. This one just has a specific plugin. Yeah. I think it would be beneficial to maybe once a month or something. I'll, I'll get an email drafted up to send to the advocacy and outreach to get every, solicit every button's thoughts. Yeah. Okay. So let's move it. It might be worth. I would be curious to know, to have the visualization of what's the top 10 plugins that people are looking for information? What's the top 10 plugins of what people are contributing? And what's the top 10 plugin that people are using? Well, I've been studying over the past months. The sad thing right now is if you look at the trending graph, all the API ones are the ones of the top users because every plugin or a bunch of them need to solve them. So it's not very useful data, but I'll think about it. The other way is, is to know which plugins are worth contributing to, you know, it'd be nice to see which ones are having an update in a while in a public list. So people can be like, Oh, I want to maintain this. Great. But it's also difficult because some plugins are more stable than others. Plugging that hasn't been touched in seven years is probably not a stability thing. Yeah. So anyway, promoting is important. And we know that we have a lot of plugins up for adoption. Yep. And we can improve the categories and tagging support right now. It's pretty... Oh, yeah, it doesn't work that way. Yeah, I was like, I didn't know that I did that. Yeah, I tried to implement it at some point, but I haven't really submitted the request. But yeah, that was quite a list here. And definitely, there is a lot of things when the camera contributors. Yeah. Okay. So do we have anything else for today? As far as I can tell, the next meeting is in two weeks, as usual. And yep. So by this time, we can start the discussion about priorities on the mailing list to see what would be the user feedback. And probably try to do as well as that, but we can almost approach this maybe late in February. One more topic. Do we want to continue with this meeting time? Is this working okay, Gavin, for you and Markey on the West Coast and Olivier, Oleg and Uli in Europe? I mean, it would be better if we have it later or before this time, because 7 o'clock here is the time when I'm bringing kids to bed and... Yeah, same, exactly the same for me. Okay. Maybe two hours before or two hours after would be fine for me. So just seven is a little bit hard for me, because... I am very open to changing the time to whatever works for everybody. I can make myself available. Earlier is a little rough for me, but I'm sure we can figure something out. Later is rough for you, Gavin? No, earlier is rough for me. Oh, earlier is rough. Yeah, good. Okay. So yeah, but later would... For me later is easier, because once everybody is sleeping, it just is easier to go back on the computer. This is normally my working time when the children are sleeping, then I'm already working hard. So this would be better for me too. Okay. So Oleg, would you like me to send out a survey? I know you had done the last doodle poll. I'm happy to do this doodle poll if you'd like, or you can do it. Feel free to do that. Okay. Do we want to do a lazy consensus that two hours later than this time is agreeable, at least with everybody here? And the doodle can still be sent out, but we could just have a lazy consensus. Yeah, for me. This later works very well for me. Oleg, how is two hours later for you? Is that harsh on you? No. Okay, so I love lazy consensus. I'll send the doodle poll proposing two hours later amongst a few other options. Beautiful. Thank you. Do we have a list of major donators or contributors anywhere on the website? Yes, yes. Company contributors or sponsors? I guess sponsors is probably more accurate of what I'm thinking of. When you say sponsors, are you? Oh, go ahead. So we're just wondering sponsors in terms of your price, sponsors in terms of everything on the organization. It was something that came up on the board, mailing lists earlier. And I was just thinking about when people do donate what we do for them. And I was wondering if there's a list of, you know, like some, like if you do like a patron or something, some people have like a little icon at the bottom of their page that says these are all the donators. So currently we have it on the community bridge. So I mean, we should automatically list all donors. Okay. Yeah, yeah, yeah, yeah. Okay. Examples here, sponsor and categorization, Linux foundation, as you can see in this course, Thrive Tech and Jenkins project. It's what we so funded from SPI. And yeah, of course we can add more there. Also there are individual contributors, but yeah, I wouldn't say that it's so visible on this site. Yeah. Because I was thinking about, you know, like this donations is always a good way to get people to be like, you want some marketing to people who use the product, you know, having Jenkins.io sponsors with a list of all the people that sponsor in whatever way they sponsor it could be in for it could be other things, you know, and then people would be able to be like, Oh, look, they're friends of Jenkins. We should give them more money because Jenkins is awesome. Well, to be honest, I'm a bit concerned about it because the most precious thing people can donate is a big time. Yes. It's not money. Yes, I agree. But yeah, but yeah, but at the same time, money means you can rent services. So for instance, we mentioned discourse, discourse, if we don't want to maintain it by yourself, you could have the money to spend there. Yeah. So time and people are always good, but money is also really good. It's better than nothing. Nothing is really bad. Well, nothing is an option because it's open source. Yes. It's free and available to anyone. Yeah. But yeah, I was just thinking out loud for that. So it's all good. So let's definitely keep it in mind. And if you want to propose a new page, just do that. Yeah. If I recall correctly, Olivier had the idea about the work and infrastructure on such a so that we would have at least these small details. I open an issue on Jenkins.io on the GitHub issues for Jenkins.io on GitHub history. Yeah, it was just like we have quite a lot of infrastructure sponsors and it's easier when we can say if you sponsor the projects, how we can put your logo here. And in fact, we have a lot of sponsors in that. Yeah. I think that would be nice to highlight their contribution. Yeah. Agreed. Yeah, it's not something I'm going to get to anytime soon, but I'd like to see that as well. Okay. So any improvements? How much appreciate it? I need to run because I got another meeting to go to. Yeah, we have other time. Okay. So then thanks everyone. And yeah, thanks for your ideas. Let's keep working. Thanks. Have a good rest of your day. Peace. Bye.