 Welcome everyone, this is the 26th of April. This is the Jenkins user experience special interest group. Thanks for being here. So topics on my list, I had improved keyboard usability. Christina's not here yet, so let's move this one down. Then what's happened recently in UI improvements? What's coming in UI improvements? Were the two hot topics for me? Are there other topics you'd like to be sure are on the list for today? Okay, then let's get started. So, Jan, I think the what's happened recently between your work and Basel Crowe's work and Tim Jacome's work, prototype JS is at least for me making really quite good progress on the removal process. There, okay, there's a lot of work to do as people can see from this list of issues that are open, but a number of them are green, right? A number of them have been closed out. Anything that others want to note in terms of, I'm assuming this will be a multi-month effort, possibly all the way into Oktoberfest and beyond, but are there any concerns or hot spots that people want to flag around the prototype JS project? Jan, anything you wanted to say there? Not anything, it's looking great to get there. Okay, well, so the next one then, Jan, this one is the one that you've started on the removal of Yahoo UI. Do you want to tell us something about how that's going? I think I saw that the tooltip improvement has merged. Yeah, that was the dropdown improvements that made it for 2.04.02. I believe that should be in the latest full weekly. Excellent, okay, so, and yeah. So if you checked out the latest weekly on weekly.ci, you should see the dropdowns there now. Oh, all right, so let's do a demo. I like demonstrations. Okay, so here's weekly. If I log in and the dropdowns, for instance here, are now coming from not from Yahoo UI. Yeah, so they're powered by Tippy. So the same as the tooltips as well. Excellent, oh, that's marvelous. Look at that. Notice everyone, yes, modern, no, it's not Yahoo UI. Very nice, anything you need to highlight there or any important points that you'd like to denote? No, it's been a multi-month effort, so thanks to everyone involved for it. Yeah, congratulations. Any other items you'd like to highlight as recent activity, Jan? Sorry, Jan, any other items you want to highlight? Oh, sorry, no, that's nothing from me. Okay, all right, so I haven't done a recent survey of the pending pull requests. Jan, do you have a summary you want to share or ideas of things that are coming and are actively being worked? Yeah, I've got a couple of them I'm sharing, that's okay. Great, so you okay if I stop sharing and we'll let you share? Sure, yep. Okay, it's all yours. Cool, so show us screen. So the first one is related to the login and register flow. Got a PR event for this and there's also a post on the community forum. Just get some discussion. So if I hit login, it's kind of a lot more colorful and bolder than what we had before. And it also carries across the branding that was kind of introduced with the design library slash about page. Also has a dark mode, which is quite nice. And if we go to register, kind of follows that similar pattern. So if anyone has any feedback, I'm always really, and then the last one, I'll just change my branch to this one. If I go to a project, yep, hit configure, yep, hit this project is parameterized. This branch replaces the previous heterolist button. The previous it was like a UI button and the dropdown is also UI that replaces it with the new dropdowns that we have. So I tap that. So I've got kind of keyboard, something like this before. And we also have the search bar to be helpful. So this was kind of consistency really. Yeah, that's that's that really. I'll probably open up a PR for this. Once I've had a proper deal of PR, it's the room progress. Yeah, looks like so. So then not only you've added that search facility inside the dropdown and keyboard navigation now is simplified, you said? Search was there previously. Okay. With the new venues, this has been introduced into the new world of non-Israeli. Just to demonstrate that features are coming across not losing any functionality, but it's the kind of changing framework. So that's that really for me. Hopefully have that up relatively soon, Ash. I'll stop sharing with that, sorry. Excellent, thank you. Any questions from others for Yan? All right, thank you, Yan. So next topic that we had was on keyboard usability and let me start sharing my screen again. So we've got a record here. Where is my zoom control panel? There it is, share. So Christina, did you want to, are there specific things you'd like to highlight in terms of what's coming there? We've got a JIRA ticket that Christina has just recently created here for compliance or for keyboard navigation. Christina, you want to talk further about where this is going? Yeah, so you're still muted, Christina. There we go. Awesome, okay. So yeah, I threw that in today. I have to flesh out the description though and make it a little bit more verbose, but long story short, that's just gonna be where I house the individual tickets for the bits and pieces. I'll create a ticket for just the navigation issues in the main nav breadcrumbs and sidebar. I've taken a stab at it. It looks like I can fix it easily enough myself. I just need to carve out the time to just do it. It's been a little bit nuts with some other launches that we've had. So I will, but I also kind of want this to, I'm not sure how y'all work, but if this acts as like kind of the home base for all of the accessibility work going forward. So if somebody else wants to pick something up later, we've got a kind of documentation trail for things. Mark shared the, there was an accessibility report, the German one. I've uploaded the England, I ran it through a translator and the English is a little funny. I don't think there's as many pregnant women having issues using it as maybe the translation, but it's enough to get a point across. It was actually really good because their findings were very much in line with ours. So it didn't change the prioritization of the issues now that we have to look at. But it did, they were able to access areas that I couldn't. So that was great. So this is kind of a nice comprehensive report. But yeah, we had identified the major things and had made our plan for that. So it was kind of nice validation there. Yeah, so my Fridays now are gonna be devoted to this. So I can actually just, I'm suffering a little bit from like one human and one body, et cetera. But like Fridays are gonna be my like heads and accessibility times. Hopefully the navigation stuff gets wrapped soon. Seems fine though. I've dug around in it and played with it a little bit and I think I'll be able to do what I need to do to fix it. There was a usability report as well. And I didn't look at it in terms of what they found for the nav and sidebar and all that. It's kind of outside the scope of the accessibility piece. So maybe I'll just document. Maybe once I'm done, I'll put some comments to kind of what has to happen in any future updates to make sure that those areas remain compliant. If there are any usability changes that come as a result of that report. Yeah, that's all I got. So when you say there was a usability, there was two documents there. There was a, in that email this morning, there was like a usability report and then the accessibility report. So I don't know if the usability one was just kind of like from a non-accessible just best practices perspective or not. Well, and given that their sample was taken on 2.319, we're a long ways from there, right? I mean, there've been significant changes since then. So a usability assessment may need to revisit anyway. So I'm just ignoring that, but I will document what, I mean, it'll be documented in the code, but I'll put some notes there as far as like, kind of what we need to make sure is there for any future updates to it. So it exists somewhere. So that's my accessibility update. I did have something else to just a question for the group just as an aside that came up this week. Is there any plans or has there been any exploration in the ability to collapse the right, the left sidebar in the Jenkins? So I think that's a yawn in your prototype, in your division prototype. I thought I think something. It did collapse it, didn't it? You collapsed the left-hand side panel. In the prototype, you can remove the side panel together on one of the screens. I've done a little bit of... Something, yeah, sorry, go ahead. Sorry, I've done a little bit of, like, playing around with, like, hiding on mobile, because right now, like, the content is pushed a mile down the page due to the sidebar, which isn't ideal, but I've not taken it anywhere really. Okay, I was just wondering. There was discussion about hiding it, and I really don't like to hide it. I know that's already done elsewhere, and there's kind of a precedent for it. I thought if there was the ability to collapse it, that might be nice to get some screen real estate, but also, like, leave people who wanted that context and don't leave, give them the ability to access it easily. But that's cool. I just wanted to know if there was any thought happening towards that right now. So I'm not sure I understand the distinction between so I think I understood Jan's remove the side panel entirely. It's live without a side panel at all. Yeah, my question was, like, can we collapse it down to, like, you know, icons or, like, so that it's kind of like, it's still there, they can expand it if they want. But maybe that's not desirable. I don't know. It was just something that came up this week that I want to know if, like, that's something actively being worked on and, you know. Yeah, and as far as I understand, it's not being actively worked on Yana. Is that match for you that that's not a place you're not looking at finding a way to make this the side panel narrower or anything like that. No, it's not. Okay, great. Any other, any other items for, I guess I've got one. If if others are willing to tolerate me borrowing a topic that I should have put on the agenda. So notifying users of end of life. Are there other topics or could I take a steal a little bit of your time here to talk about a concept that I have. Okay, so, so one more topic then this notifying users of end of life. We've got a number of things that happen in the context of a Jenkins controller like, Oh, I'm running on Ubuntu 18, but the Jenkins project stops supporting Ubuntu 18 because Ubuntu stops supporting Ubuntu 18 at May 31st of 2023. And my thought was, I would, I would love a way to tell people, you're on something that is going to end of life on this date or after that date tell them. It has ended life you need to get off this thing. So my, my notion was extend the concept of an admin monitor to allow us to store definitions of admin monitors inside Jenkins itself and say, if the file slash etc slash OS dash release exists and contains the word Ubuntu 18, then show this message before this date show this message after this date. The idea being that Jenkins would carry within itself. Some knowledge of its of what should be support what what it should warn you about based on the environment where it is running. Any comments from others, does the idea sound plausible does it sound like it could be worthwhile, or are there things you'd say no that won't work for the following reasons. So what's the difference exactly do you make with implementation administrative monitor. Well so for me the difference is administrative monitors typically don't have a date an effective date as a concept. And so that's a that's a new concept, the administrative monitor would have before this date it should say this message after this date it should say this other message. Did that answer your question Antoine or was there something more. Okay so it would be like one administrative monitor, but several messages. Like with conditions to display those messages. That's what I was thinking right that was my mental model was, and the further thought was that maybe the monitor should become active again. If they dis if they dis they cleared the monitor before the due date, and it still passes the check, and the due date occurs I want that monitor to reappear and say okay you have to clear it again because before we warned you it was expiring now we're warning you, it has expired it's no longer supported. So that was another concept for me that's that's a little different than the current admin monitors. So Antoine did did that did that make sense to you what I've described. Yeah, that would actually be very interesting. Yeah, that that whole concept we, I mean, on the B site on some proprietary stuff we are relying on the administrative monitors as well and having possibility to define several messages with different steps like one warning and one like final warning and one it's too late but it's time to fix stuff would be very interesting. Good. Okay. So, so, I'll continue that I think I can just do it as a pull request to Jenkins I don't even think I need a Jenkins enhancement proposal this the more I've worked through it it feels like it's just pay propose it and a data file that we use to define these things and we can extend the data file adding more, more things to the list. This would solve for me the how do we notify people that Alpine three dot 14 isn't supported anymore. How do we notify them that it went to 18 isn't and in a future day how do we tell them Centos seven is dead. Those those are all things that matter to me deeply. It won't solve things where they can't be represented as a file on the file system so for instance the end of the eventual end of life of Java 11 doesn't fit this. And so I've got some more thinking to do about how would we do end of life of Java 11. When that day comes. All right, that's all that I had any other anything else on any other questions on that topic. Any other topics we should discuss here. All right I'm going to take the quiet is the assumption we can go ahead and close the meeting. Thanks very much everyone. Have a good night everybody.