 So welcome everybody. I don't know. Hopefully we'll get a few more people to hop on. We'll see I think everybody on here already knows or has at least met everybody else. So we'll kind of skip past that And then we can jump right in obviously the way we do this is anyone can sort of add things as we go Felix do you want to speak to that first one? Yeah, in case you might want to open the hyperlink and scroll all the way down to the bottom So I've not been able to follow this really closely Because I just wasn't able so I understand that team considers that the art we're ready That's my understanding from from reading this as well. Yeah mine as well So yeah team prompted the suggest we discuss in the sick meeting when we are going to merge But he suggested that we merge it we we are choosing an ideas base lining Exactly three weeks or more almost exactly three weeks But he suggested we postpone and we we delay the merge until then I and I agree with that. I fully agree with that So I think only all that voice Okay, you know, he would be okay with merging it really soon, but he's not here, so I Don't know if we have enough to discuss Other than what you just just mentioned. He got some likes some thumbs up on the comments, so Yeah, I mean given given the owner for this PR himself Thumbed up my comment. I'm going to consider this is what we do until the other right Obviously for leg insist he will have to obviously discuss with the team first, which I guess makes sense and What Daniel said or so kind of is going that direction got Daniel is very surprised Oh, like he's saying this looks very sweet indeed. It's kind of going together Still, it's a very risky change. We all know that So, you know, given the time we've waited already till now, you know Waiting two each week three weeks more because technically we don't actually need to wait till really the 21st We could really see the few days before The only goal here we would be pursuing is as you if it's not obvious is that we won't we don't want this PR to be Stopping my baby to break the door so Yeah, that we don't want this PR to be eligible to the next LTS baselight selection basically so How does it work in general for anybody that we don't know is that? When we consider a new base line We look at the past releases on the weeklies and we choose one that looks like okay ish from me from a stand feedback standpoint and Yeah, anyway, that's a kind of a detail Yeah, I Think we can agree on doing that and and we see whether in the next three weeks we have somebody shouting Louder than the others which I don't expect actually So we'll follow up with Oleg after this since he can make this chat But it seems like there's mostly consensus there and we can kind of figure out which which path forward But I would say regardless pretty exciting that that this is close So Anything more to share on this on this item feel it's no All right, we might just be through today's session I had a couple of items here, but they're not items that can I would thank you for doing the minutes feel it Sorry about that. I meant to cover a couple of items here nothing to show on screen per se but Here on the clobby side I've been talking with a couple of people inside clobbies who have had kind of Mentioned, you know, hey, there there could be much more consistent UI labeling and I use that term sort of loosely and by labeling I mean how we talk about describe and actually Name the different elements, whether it's individual components or like regions of the UI throughout Jenkins So for example, if we just looked at that left-hand panel, some people will call it the left-hand panel Some people call it the sidebar. I've done that even though I know it's probably not the right name Some people call it navigation So the idea here is that having consistent nomenclature around all of these different aspects of the UI could really help Just the the global work being done by our global community here To improve Jenkins helps people collaborate better and helps make clearer documentation. So all that to say that I'll be sending out a form to everyone who has been in Involved in the SAG obviously small group today And then also posting that in our different Communication outlets in Gitter. I'll try and get on the Jenkins mailing list And it'll be a form essentially trying to collect feedback from people to understand better how everyone outside my limited perspective is talking about these things because if we're gonna update the Jenkins glossary, let's say or Formalize the different labels. I want to make sure it's in line with what everyone else is thinking instead of just picking something It's always sending that out soon any questions or thoughts on that one Cool pretty straightforward And then another item here is build status page rework. This is going to be an area of pretty heavy focus over the next month or so for myself Unlike in previous situations where we were looking at more individual components and I could Kind of create some mock-ups and some proposed solutions and bring them to this group and then we discuss and iterate this is a larger scale I don't write this is a full page and I want to try and a little bit more fundamentally reconsider what the build status page is So rather than just going directly into some of those mocks I'm going to also be sending but to a smaller group most of the people involved in the SIG Just a separate item a separate form for gathering some input on how they use the page If they use the page and what they would like to see and how they'd like to see it evolve So these last two bullet points are just items that will be coming throughout this week I'll share them in our getter and then this one here. I'll share in the mailing list Um, and that's it Anybody have anything else for today's session? Not everybody at once everybody calm down It's a short one then. Um I guess that's it unless someone has something All set Everyone's on mute. Okay. Thanks everyone for your time. Appreciate it and we'll we'll talk soon