 Welcome everyone, this is Jenkins UX Special Interest Group. Today is November the 8th, 2023. Topics on my list, Jenkins contributor summit for FOSDOM. What's happened recently in UI improvements and the Jenkins 2023 board and officer elections. Any other topics that need to be on UX SIG meeting agenda today. All right, then let's go ahead. So first one is just an announcement, but especially to our European contributors, February the 2nd, 2024. In Brussels, there will be a Jenkins contributor summit. It's intended to be an all day event. We've got a location already reserved. It'll be the day prior to FOSDOM. FOSDOM will be Saturday the 3rd and Sunday the 4th of February. And I'm actually hoping to be there personally as well. So John Mark Mason will be coordinating the agenda. He started the gathering. He'll do some announcing, but we would love to have other contributors join us. And hopefully it's not too long of a trip from wherever you are in Europe to Brussels. Any questions on the contributor summit? All right. Sorry, do we have any additional things on FOSDOM itself? So we will have a booth at FOSDOM. I believe that's been, that's our table. Like calling it a booth is, we'll have the thing that we usually have at FOSDOM as far as I can tell. So the request will go out. I assume there will be a dev room on continuous integration again, but... More or less. I've been told that it has been merged with testing and automation. And we don't know yet if we will have a full day or half a day. Okay. All right. So that's fine. It's, we certainly are evolving as an industry. So they're matching that. Any other, any other things you need to share? Thanks very much, Bruno, for being involved there. You're welcome. I don't know anything more than FOSDOM for the time being. Thank you, Mark. Okay. Great. Next topic then was what's happened recently in the UI improvements. So first topic, Prototype.js has been released to be, it's gone as of weekly 2.426 about one week from today on the, in fact, one week from today on the 15th, we will release it in the LTS that drops it as well. So thanks very much to Basel Crow, to Tim Jacom, to so many others who have done the changes and nice positive, very, very nice positive. Any questions or concerns on Prototype.js? Okay. Next topic then is Java 11 end of life administrative monitor. So Java 11 will no longer be supported by Eclipse Temeron and the other open JDK providers as of October 31, 2023, or in one case with Microsoft, it's September 30th of 2024. So September and October of 2024 will end support for Java 11. The Jenkins project will not support a JDK that is not supported by the upstream provider. And therefore September and October of 2024 are our transition period. And so we're announcing to people a year before that their Java 11 will be end of life. Now there's a Jenkins Java support plan, enhancement proposal here, that has a description of this, but it needs more details on the transition, what steps we need to take, which components need to be upgraded, how do we do those upgrades, those kinds of things. And so I'm working on those details. Just be aware that in, and I think it's actually October of 2024, we will switch the minimum required Java to be Java 17. I'll have to look at the, yeah, I'll have to look at the dates to see which one it is. Any questions there? Okay, so next topic then is, we've got a proposal for the replaceable log visualization or let's call it console log is ambiguous there. So a console visualization pull request, what it's trying to do is allow plugins to say how they want the console link to be handled. And the pull request has been submitted. It looks like it's ready to merge. The last comment came about a week ago. And so I will probably go ahead and propose it as ready to merge after I've had some time to look at it a little bit more myself. But Daniel Beck has said, he feels like it's looking good. And we have three approvals already, Fran Fernandez, Jerome and Daniel. So I think we're ready to merge. What this does is this allows pipeline graph viewer, blue ocean and a CloudBees proprietary product also to do replaceable log visualization. Oh, Daniel, you've arrived at the perfect time. I was just showing this pull request on log visualization. I think it's ready to merge based on your comment here. Let's make that readable. And so I was going to go ahead and flag it as ready to merge and start the 24 hour clock. Is there any concern from you, Daniel, if I were to do that? If you scroll down, I hope this pull request. So, I mean, I have no objections. Okay, great. Yeah, sorry, it was this one where you had optional thoughts. And I think you specifically said optional. So I think that means you are okay if we go ahead and start the clock on this one to prep for a final merge. Right, great. Because in particular, it's not blocking the core implementation. It's mostly about establishing standards for plugins implementing this extension point, have consistent behavior that also makes sense in context. Now, in response, Devin's comment pointed out that it's difficult, that it's not really possible for plugins to determine whether the link needs to be shown to the custom implementation or not. But I also don't think this is a blocker. It can always be enhanced. So as a first iteration, this looks reasonable and everything that I asked to have addressed has been addressed. So yeah, this looks definitely mergeable. Great, thank you. So I'll start that clock then and that's good. So, excellent. Thank you, thanks very much. There have been several other UI or experience related improvements that have been proposed by Marcus Winter. And sorry, I know I should say Winter. Marcus is German if I remember correctly. But that word looks to me like Winter in my English pronunciation, I apologize. So he's got one on disk space monitoring, on agent status monitoring, and on configuration as code support for monitors. And in various varying stages of review, Daniel, I think you'd actually reviewed the prevent reinstall and it needs some additional work, but good progress on all of them. Any comments from others on things that we need to do on any of those? Okay, good. All right, then the item on cloud management, as far as I can tell, this one's somewhat quiet, quiet recently. There haven't been any further things arriving, but more changes I believe are still coming. And Tim last time we met had shared that he was continuing to work on trying to find a way to better display configuration as code errors in the UI, whereas right now when configuration code as code has an error, it stops the controller and you have to go read the log files. Any questions or concerns there? Don't we have a new boot failure type for that? I thought I saw a poll request or something. Maybe that's Tim, what Tim was talking about on this core change, I'm not sure. That's a good question, yeah. Yeah, there's a draft PR for core that would allow plugins to override the boot failure. Okay, so it seems kind of in progress although the poll request was opened in late August. Okay, so that maybe the poll request he was referencing and then configuration as code once that's available could use that poll request to say, hey, on boot failure I need you to display this message or I need you to say, and that I assume then would still be inside the web user interface so it's not stop the controller or is that it's actually stopped the controller and I've still got to read log files. I guess I can read this. Jenkins will have failed to start but it shows an error on the UI. Ah, it does, okay. So there is a responding HTTP server at that point. Good, okay. It's a bit like while Jenkins is starting or restarting the entire UI is replaced with something different and at this point the Jenkins singleton is shut down but something else responds and that's the boot failure view. Got it, okay. So that allows consumers to see what's happening without having to go to the log files on the disk of the controller computer, good. Anything else on that topic? All right, so last topic and Uli with you here I'm going to boldly dare to share and so the Jenkins 2023 board and officer elections current status, nominations have closed and voter registration has closed were after the November 5 date but as far as I understand it Uli there was only one person nominated per position that was available. Can you confirm that's correct? Actually, I'm not sure. I haven't looked into it recently. Okay. I should do that. So sorry that I didn't prepare it for today because I thought this is something for the other meeting for the governance meeting. So yeah. And no problems. So if you could just double check. For me, I think that was the last word we had but if that's not it then we need to get the election started. I think for the board, it's correct but for the officers, I didn't look good. Okay. All right. Great. Thank you. So postpone this to Monday. Perfect. That's no problem. Thank you. Any board yes. Yes, got it. So board yes. Well, so actually I'm just going to delete this because that's yours and Alex is to announce. So let's leave it to the two of you. Great. Anything else that we need to discuss in user experience today? Good. Let's call it a done session for today. Thanks very much for your time. Bye. Stop recording now.