 Welcome. This is the Jenkins user experience special interest group. Thanks for joining us today for topics we got the Jenkins contributor summit. What's happened recently in UI improvements. Are there any other topics that people want to be sure we add to the agenda. Okay. Great. Well then let's go through so Jenkins contributor summit is being planned with FOSDOM 2024 this will be February to 2024. In Brussels. We have space for 30. And we have five plus already confirmed attending. Including Uli Hoffner, Alex Brandes, Stefan speaker, several others. So if you're in Europe. You, it's a relatively low cost trip to Brussels for most people. I hope to be there still trying to get funding approved. Any questions on the contributor summit at John Mark Mason is is assembling the agenda. I'm sure I'm spelling as well. That's right to ease. There we go. See community Jenkins that IO for more details. Any questions. The next topic then is what's happened recently in UI improvements. And here, the, the key things I feel like we've got some, some improvements happening in areas that are not as typical. So the console visualization pull request has been merged. This one allows plug ins. Oh, come on. This one allows plug ins to use an alternate build log visualization. So things like pipeline graph viewer, or, or blue ocean, or other build log visualization tools can present their own link in the console. And released in I think 2.433 or 434 so we'll be first available in the first available in February. LTS, right, meaning it's already available in weekly first available in February LTS in 2024. Then Marcus Vinter of SAP has been doing this space monitoring improvements. And this one I yes has also merged, and I've been using it. And I'm really quite pleased with it. So it, it's helping us have a better experience for agent monitor agent management and monitoring any questions on either of those two. Okay, so then agent status monitoring improvements this one again from Marcus has also been merged. And if I remember correctly this one resolves a particular issue that he had found due to disk space issues where it would, if the disk space was freed it would not come back online. And now it will be brought back online if enough disk space is available and configuration is code support for node monitors. So thanks to Marcus Vinter for his work here. I've been using this one as well and been very pleased with it it's only available in weekly so next time it will be the first LTS that will appear in will be in February of 2024. Any questions on the node monitoring improvements that Marcus is implemented. The topic then was on cloud management interface improvements and here. I think that slowed down. I'm not sure unless others are aware of one that I've missed where cloud management interface has got has received significant new changes. As far as I know we're stable there and well behaved. There's still the open issue of the discovery of the cloud reordering, which we discussed a while back might have been in October. I think the result there was that Christina would look at how this can be improved. Thank you. Okay, Daniel thank you very much Christina and I had this conversation. A day or two ago where she asked mark I know there was a thing I was supposed to look at the UI on what was it, and I had completely forgotten so Christina I assume you haven't looked at it because I completely forgot. Okay, so mark to create a ticket. Oh, go ahead, but please. Perfect. Thank you. Thank you very much. Alright, for Christina to help us help with a UI proposal. Good. Thank you. I'm happy to prioritize that then since it's been a bit. Excellent. Thank you. Thanks very much. Thanks Daniel. And I'll I'll create that ticket Christina. Thank you very much for being willing. No, I'm happy to anything else on cloud management interface improvements. The next topic then was configuration is code errors and this one I believe is still an in progress poll request to Jenkins core right now when there's a configuration is code error. Jenkins core stops, it drops a core drops a stack trace and says, I'm exiting. And the desire is to have it instead keep the HTTP server running and present that to the user through the web page. We could look at that PR effect. Well, I'm not sure it will help to look at it. Any questions there. All right. Any other topics that we need to bring to you exit today. Thank you for joining. Was there anything that you you needed to bring to us as a as a UX sick. Actually, no, that's okay. Great. Any others. All right, then just as a brief status report, the, the, not UX related but developer experience related the brown out for Artifactory was successful in that it showed us we're in a really good place in terms of removing the repository that was requested. So, successful brown out Daniel, reverted. Have you successfully reverted or is that still pending. No, I reverted most of it. Excellent. Okay, so, so brown out has completed all post a summary later for others to see exactly what we learned from it. I've got some more log analysis to do to be sure that we understand all the things that happened. That's all that I had then are if there are no other topics I'd say let's call an end to this meeting. Recording will be available about 24 hours from now. Thanks very much.