Jenkins User Experience Special Interest Group, 30 Sep 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Jenkins UX SIG Meeting - 30 September 2020

Description

The table to divs PR is ready to merge. Some discussion about whether this should be merged before the LTS or not. The consensus in the meeting is that it should be after the LTS. Joe Brueggen discussed formalizing the language used to discuss UI elements e.g. the navigation bar.

A

A

So welcome everybody I don't know, hopefully we'll get a few more people to hop on we'll see. um 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 um felix. Do you want to speak to that? First, one.

B

Yeah in case you, 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 um because well, I just wasn't able. So I understand that team considers that they are to be ready. Is that correct.

A

That's my understanding from from reading this as well.

B

Yeah mine, as well so yeah team, prompted the suggest we discussed in the sig meeting when we we are going to merge, uh but this suggested that we merge it. uh We we are choosing an lds baseline in exactly three weeks or more almost exactly three weeks and but he suggested we postpone and we we delayed the merch until then- and I agree with that- I I fully agree with that.

B

So I think only olaf voiced some okay that 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 him other than what he just just mentioned. He got some likes some thumbs up on. The comment show.

C

Yeah I mean even given the the owner for this pr himself uh summed up my comment. I'm going to consider this is what we do until today.

C

Obviously, for leg insists he will have to obviously discuss with the team first, which I guess makes sense.

C

And what daniel said or so kind of is going in the direction again. Daniel is very surprised. Oleg is saying this looks very sorry. 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 until now. You know waiting two inch weeks, three ish weeks more because technically we don't actually need to wait till really the 21st.

C

We could release it a few days before the only goal here we would be pursuing is uh as you, if it's not obvious, is that we won't. We don't want this pr to be stopped, just stopping my baby to break the door so um yeah that we don't want this pr to be eligible to the next lts baseline selection. Basically, so uh how does it work in general?

C

For anybody that we don't know is that uh when we consider a news baseline, we look at the past releases on the weeklies and we choose one that looks like okay, ish from you from a standard feedback standpoint and uh yeah anyway. That's a kind of a detail um so yeah.

C

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. But.

A

Okay, so we'll follow up with oleg after this, since he can make this chat, um 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 um that this is close. um So.

A

Anything more to share on this on this item fields.

B

A

It's really, okay, all right. We might just speed through today's session. um I had a couple of items here, but they're not items. I can oh. Thank you for doing the minutes. I feel.

C

A

That I meant to cover um a couple of items here, nothing to show on screen per se, but uh here on the cloud b side, I've been talking with a couple of people inside copies who have 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 um how we talk about, describe and actually uh name the different elements, whether it's individual components or like regions of the ui throughout jenkins.

A

So, for example, if we just looked at that left-hand panel, some people will call 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.

A

So the idea here is that having consistent nomenclature around all these different aspects of the ui could really help. Just the global work being done by our global community here um to improve jenkins, helps people collaborate better and helps make clearer documentation, so all that to say that um I'll be sending out a form to everyone who has been in involved in the sig.

A

Obviously small group today um and then also posting that in our different communication outlets in getter, 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 going to update the jenkins glossary, let's say or 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 so I'll, be sending that out soon any questions or thoughts on that one.

A

Cool pretty straightforward uh and then another item here is uh 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 item right.

A

This is a full page and I want to try 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 uh just a separate item, a separate form for gathering some input on how they use the page um if they use the page and what they would like to see and how they'd like to see it evolve.

A

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 and that's it.

A

Anybody have anything else for today's session.

A

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 cute, okay, thanks everyone for your time, appreciate it and we'll we'll talk soon. Thank you. Thank.

A

A