►
From YouTube: Jenkins UX SIG Meeting 1 Mar 2023
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Welcome
everyone,
it's
the
Jenkins
user
experience
special
interest
group
today
is
March
the
1st
2023.
great
to
have
everybody
here.
Topics
that
I've
got
on
the
list
for
today
include
keyboard
usability,
UI
improvements,
recent
UI
improvements.
What's
coming
in
UI
improvements,
deprecation
of
Jenkins
JavaScript
libraries
work
in
progress,
let's
put
those
as.
A
And
user
feedback
had
a
good
post
from
Jerry
in
the
community
on
on
usability
and
usability
concerns.
Are
there
any
other
topics
that
need
to
go
on?
Oh
and
one
more,
which
is
that
I
need
someone
who
is
willing
to
take
over
the
meeting?
I
can
stay
for
about
20
minutes,
but
then
I
need
to
hand
control
over
to
someone
else
to
take.
Take
the
leadership
of
the
meeting.
Do
I
have
a
volunteer
awesome.
B
A
A
A
C
So,
due
to
some
other
priorities,
I
haven't
made
as
much
progress
on
this
as
I'd,
like
so
kind
of
where
we're
at
is.
We
need
to
at
cloudbase
at
any
rate,
I'm,
not
sure.
If
the
accessibility
work
done
was
in
the
community,
we
need
to
achieve
wcag
level
AAA
compliance
to
do
so.
There
are
some
major
kind
of
issues
within
the
open
source
code
that
we
need
to
fix,
which
are
easy
enough.
C
C
We
need
to
kind
of
patch
our
process
for
merging
things
into,
say
the
unified
release
Branch,
because
otherwise
we're
always
going
to
be
chasing
this
and
we're
not
going
to
be
able
to
say
like.
Yes,
we
have
a
process
in
place
that
makes
sure
that
any
new
changes
are
accessible,
so
I
kind
of
need
to
touch
base
with
some
people
internally
to
figure
out,
like
kind
of
a
best
practice
that
we
could
set.
C
But
I
can
walk
you
through.
If
there's
interest-
or
maybe
this
warrants,
is
there
an
accessibility,
Sig.
C
There
an
accessibility
initiative
on
Deus
they're.
C
C
D
A
C
Think
go
ahead.
Okay,
all
right
so
obvious
I
mean
I'm
sure
you
all
have
like
some
baseline
familiarity
with
with
accessibility
kind
of
until
now.
The
way
we've
tried
to
tackle
it
is
like
here's,
a
laundry
list
and
an
Excel
file,
you
know,
hit
stuff
and
and
try
to
you
know,
fix
fix
the
broken
without
really
like
building
a
process
and
I
hate.
C
So
currently,
there
are
some
issues
with
kind
of
all
all
areas
of
the
main
navigational
area,
like
the
the
main
nav,
the
breadcrumbs,
the
sidebar
kind
of
the
way
I'm
choosing
to
tackle
this
is
when
it
so
we
have
customers
that
are
asking
for
it
and
when
it
comes
to
accessibility
audits,
like
intent,
really
matters
right,
so
no
one
will
care
about
an
old
tag
on
a
spacer
image
if
they're
stuck
in
a
keyboard
trap
in
the
breadcrumb
navigation
and
they
can't
get
out
so
I
think
that
you
know
it's
far
more
useful
to
fix
the
foundation
like
the
bigger
issues
which
are
the
scarier
ones,
but
they're
not
and
get
those
working
so
that
at
least
a
user
can
navigate
through
a
page
from
start
to
finish,
using
an
accessible
device
if
they
need
to
and
then
the
lower
hanging
fruit
we
can
tackle
kind
of
as
we
go
so
I'm
kind
of
breaking
up
my
plans
into
like
a
phase.
C
One
phase
two
phase
three
phase
one
is:
is
the
the
kind
of
the
framework
navigation
around
everything
else,
so
the
main
nav
breadcrumbs
and
sidebar,
especially
if
you
have
a
build
in
progress
I.
Just
you
know,
if
you
go
through
with
your
keyboards
you'll,
find
all
kinds
of
traps
and
I
mean
we
tend
to
do
like
the
ideal
path
with
like
no
opening
of
sub-menus
and
things
like
that,
and
it's
like
well
I
can
get
through
open
a
sub
menu
and
you
will
get
stuck
or
have
a
build
in
progress.
C
C
Sure
that
what's
getting
done
is
is
up
to
those
standards,
accessibility,
standards,
but
I
would
kind
of
like
to
get
our
internal
merge
process
sorted,
and
maybe
that
can
happen
concurrently,
maybe
I'm
overthinking
that
I'm
a
little
reluctant
to
just
throw
tickets
in
the
queue.
A
So
I'm
not
sure
Christina.
So
your
concern
there
of
if,
if
you've,
found
a
keyboard
navigation
issue
in
Jenkins
yeah,
it
seems
reasonable
to
me
at
least
to
say,
hey,
submit
an
issue.
Then
anybody
could
potentially
pick
it
up
and
work
it.
It
is.
Can
you
tell
more
about
what
your
concerns
are?
Why
you.
C
There
would
need
to
be
an
approver
on
the
ticket
that
probably
myself
right
now,
at
least
who
can
make
sure
that
when
the
ticket
is
done,
it
is
actually
functioning
as
intended
according
to
breast
best
practices,
and
that's
not
just
the
keyboard
navigation
that
would
be
making
sure
that
all
the
area
tags
that
are
in
place
for
that
block
of
of
code.
Things
like
that.
A
Okay,
so
so
so
what
you're
saying
is
if
a
jira
issue
is
created
in
the
Jenkins
jira
you'd
like
to
have
you
or
somebody
somebody
you
you
assign,
would
also
be
involved
in
assessing
hey.
Did
that
achieve
the
objective
that
yeah?
That
sounds
like
a
real
positive
actually
to
me.
I,
don't
think,
there's
going
to
be
any
complaints
about
extra
testing
from
people,
okay,.
C
A
C
A
So
so,
if
you
wrote
If,
you
raised
a
a
jira
ticket.
That
said,
hey
there's
this
accessibility
problem.
If
you
watch
that
ticket
you'll
see
when
someone
submits
a
pull
request,
because
they'll
usually
link
to
the
pull
request
and
then
you
can
go
watch
the
pull
request
and
actually
mention
yourself
on
it
or
or
make
your
own
review
comments
on
the
pull
request
as
well.
That
also
gives
you
a
prototype,
build
that
you
can
use
to
perform
testing
so
so
I
think
I
think
the
process
we've
already
got
can
work
for
you.
Okay,.
C
A
Yeah,
so
maybe
maybe
what
you
and
I
could
do
is
let's,
let's
plan
some
time
where
I
can
talk
you
through
some
of
those
steps,
so
that
you,
you
don't
run
into
unnecessary
bumps
and
bruises
I
think
that'd
be
great,
yeah,
great
okay
and
once.
C
Going
to
be
subsequent
phases
like
right
now
with
the
level
of
of
issues
in
in
those
areas,
a
user
realistically
using
adaptive
technology
could
not
get
to
the
plugins,
so
I
kind
of
want
to
fix
the
pathways
first,
and
so
first
phase
will
be
the
navigation
areas,
and
then
we
will
start
to
get
into
plugins
and
things
like
that,
and
those
will
probably
be
its
own
thing-
that
we
have
to
work
out
too,
since
the
responsibility
for
those
areas
may
be
distributed
right.
C
You
know
like
we'll,
we'll
have
to
kind
of
figure
that
out
as
we
go,
but
if
you
ever
are
being
scrutinized
for
accessibility
compliance
issues,
if
we
kind
of
tackle
it
this
way
it
demonstrates
that
we
have
an
understanding
of
the
major
issues
and
we
are
making
like
an
honest
attempt
to
rectify
them
versus
if
we
fix
something
that
you
couldn't
get
to
anyways.
It
kind
of.
C
We
want
to,
we
want
to
be
out.
We
want
to
be
on
the
good
side
of
things
where
we're
demonstrating
that,
like
hey,
we've
got
a
meaningful
path
and
we
get
it
like
we
get.
What
the
issues
are
versus
kind
of
going
backwards
like
that,
but
it
will
happen.
Yeah
and
it'll
probably
be
similar
perfectly
fine
and
and
others
where
you
know.
A
Okay,
next
topic,
I'd
put
on
the
agenda,
was
what's
happened
recently
in
UI
improvements,
specifically,
the
one
I've
seen
is
pipeline
graph
viewer
Tim.
This
is
this
one
that
you
wanted
to
talk
to.
You
want
me
to
talk
to
it.
I
think
the
the
additions
you
that
have
been
made,
the
the
changes
in
log
viewing
and
whatnot
are
really
brilliant.
F
F
So
we've
had
a
few
contributions
recently
on
the
pipeline
graphia
over
the
last
couple
of
weeks
going
back,
yeah
yeah,
so
we
can
now
transition
between
previous
and
next
Builds
on
the
graph
and
console
views.
I'll
show
I'll
show
them
all
in
a
second,
the
logs,
very
complete,
rework
from
a
tree
on
the
side
to.
F
And
this
sort
of
thing,
scripted,
parallel
stages,
have
been
improved.
F
The
same
behavior
all
this
and
this
and
declarative-
and
there
was
some
special
hacks
stopping
networking
and
stage
labels
in
the
tooltip
now
show
the
full
text.
F
So
here's
an
example.
So
this
is
the
next
build
and
previous
build.
F
You
can
open
and
close
all
the
logs
here.
If
I
go
build
you
get
all
the
output
in
here.
If
I
should
be
a
button
for
swapping
in
between
them.
Is
that.
F
And
so
yeah
you
scrolling
here
and
there's
a
lot
more
output
and
you
can
also
request
more
output,
so
you
can
previously
you're
stuck
if
there
was
any
if
there
was
any
logs
missing
here,
but
you
can
now
click
to
get
the
rest
of
it
so
yeah.
Basically,
a
major
rework
of
the
of
the
logs
for
the
pipeline
graph
view
plugin
anyway,
still
more
work
to
be
done,
but
it's
a
lot
better
than
before.
A
F
Yeah
September
under
the
core
work
and
I
think
Stuart
Road
did
this
and
Mike
Calvin's
has
done
a
bit
of
cleanup
as
well.
F
C
B
A
Yes,
others
confirm
as
well
that
they
can
see
and
so
you're
scrolling
up
now,
March
1
20
23
is
roughly
at
the
top.
There.
A
B
C
E
E
F
E
F
The
only
one
he's
opened
recently
is
the
simplify
settings,
name,
which
I
was
posted
in
the
chat.
That's
as
a
follow-up
to
the.
F
F
There's
a
screenshot
on
the
pr
we're
just
waiting.
It's
I
think
everything
on
that
page
is
on
that.
Pr
is
fine.
It's
just
who
want
to
check
that
the
acceptance
tests
passed,
but
the
exception
tests
are
broken
at
the
moment.
B
F
That's
the
list
of
all
the
powers,
it's
quite
there's
quite
a
there's.
A
few
open,
I
think
at
least
a
couple
of
them
are
waiting
on
Daniel's
feedback
or
someone
to
investigate
a
couple
of
issues.
F
I'm
not
sure
if
you
can
see
the
chat
Christina
that
might
just
be
worth
opening
up,
that
pull
requests
and
having
a
scroll
through
see
what
people
think
sure.
C
E
Do
we
have
so
many
users
that
are
looking
at
Jenkins
using
the
mobile
phone.
C
Do
you
guys
have
analytics
about
that.
F
C
E
E
F
E
D
G
E
Yes,
I
I
looked
at
this
yeah
a
couple
of
things
and
I
think
for
a
lot
of
them,
I
think
yeah,
that's
really
a
problem.
We
need
to
change
that
and
I
I
commented
this
one
a
little
bit
deeper
in
the
list
here
and
yeah
I'm,
not
sure
how
we
can
handle
these
making
jira
issues
like
for
excessive
accessibility,
I'm,
not
sure.
If
that
helps,
I
think
the
main
problem
is
we
have.
We
have
not
enough
developers
to
fix
these
things,
I
think
so.
G
D
Yeah
I
am
Bruno,
but
only
is
one
who
knows
everything
about
that,
so
I'm
just
shut
up
and
let
julito.
E
G
E
I
think
you,
you
have
a
lot
of
points
which
are
really
correct
and,
for
instance,
making
the
icons
themeable.
This
is
the
thing
we
we
talked
I
think
almost
a
year
now,
but
we
actually
found
nobody.
Who
is
you
know,
making
progress
on
this
thing,
because.
G
E
E
G
Graphics
images,
yeah
yeah,
bitmap
images,
yeah,
PNG
or
G4,
whatever
yeah,
the
new
icons
are
SVG,
vector,
graphics
and
I.
Don't
know
if
it's
the
same
process
to
replace
them
within
It
theme.
E
E
G
What
about
in
general
should
I
trade
Chira
tickets
for
each
of
the
points
and
somebody
or
a
group
or
a
meeting
decides
yeah
rejected
or
yes
will
be
implemented
somewhere.
E
E
If
it's
makes
sense
for
every
point
but
for,
for
instance,
the
second
Point
here
with
the
drop
downs,
yeah.
B
B
C
G
C
Yeah
sorry
I
can't
speak
to
the
icon.
Question
number
two
is
definitely
almost
completely
covered
by
the
accessibility
work.
That's
going
to
be
that
a
ticket
will
be
created
for
this
month,
along
with
a
few
other
things
anytime.
There's
a
inconsistent
browser
Behavior
those
will
be
captured
in
the
accessibility
work.
That's
going
to
be
underway.
E
Oh
sorry,
I
I
mean
the
two.
There
are
two
twos
the.
E
Let's
see
yeah
I'm,
not
sure
if
it
helps
to
to
show
it
actually
on
screen,
but
I
think
there
are
a
lot
of
points
which
make
sense
to
write
to
jira,
so
we
can
discuss
it
in
jira
and
maybe
we
can
get
some
works
as
well.
So
we
see
this
is
a
common
sense
or
is
it
just
a
single
opinion,
so
some
butter
I'm
not
sure
if
it
there.
E
Issues,
and
normally
we
just
need
someone
to
to
to
look
after
them,
and
currently
we
don't
have
someone
looking
after
them,
so
I'm
not
sure.
If
what
to
do
actually.
G
Okay,
I
can
offer
to
solve
some
of
these
issues,
points
which
can
be
solved
with
a
theme
Yeah
by
myself.
By
creating
a
theme
that
looks
more
like
the
classic
view
yeah,
but
maybe
it's
it,
it's
just
a
rough
guess.
It's
a
threat
of
the
points
could
be
could
be
handled
by
a
theme,
an
according
theme.
B
B
G
Matter
of
taste
yeah,
but
other
things
like
yeah,
hidden
action
items,
actual
controls,
widgets
yeah,
which
popped
up
on
whole
via
and
then
I
have
to
move
to
them
in
another
step
and
keep
them
yeah.
This
cannot.
This
is
yeah.
Css
selection,
yeah
selection
of
diseases
like
Library
behind.
B
B
E
G
If
if
the
process
has
to
be
followed
yeah,
then
the
Cure
issues
are
needed.
Yeah
I
know
that
because
I
work
with
children,
my
job
as
well
daily
I,
don't
want
and
putting
all
these
this
nature
points
into.
Jira
issues
is
quite
a
black
yeah
and
I.
Don't
want
to
avoid
investing
this
work
and
then
nobody
looks
at
it
for
months
or
even
years
yeah
and
finally,
they
are
closed
automatically
because
of
will
not
be
implemented.
Yeah
then
my
time
is
wasted
for
me
personally,
yeah.
E
E
So
I
think
for
each
of
these
issues
you
need
someone
driving
them
and
we
currently
don't
have
someone
driving
them.
The
only
one
really
working
in
ux
is
Jim
and
Jan,
at
least
for
core,
so
I'm
not
sure
what.
G
B
G
E
Yeah
the
actual
work
we
currently
have
nobody
doing
extra
work
in
Jenkins
anymore.
So
sorry.
G
For
being
that
open,
but
I'd
like
to
be
the
gear
in
speech,
so
this
can
be
summed
up
to
if
you
would
like
to
have
it,
do
it
yeah
yourself
yeah?
G
G
Job
which
is
challenging
itself,
but
I
I'm
allowed
to
withra
to
retire
in
six
and
a
half
years.
Maybe
then,
and
then
at
least
then
I
have
I'm
going
to
have
enough
time.
Yeah.
E
Yeah
so
yeah.
G
G
E
Yeah,
the
clues,
we
don't
have
someone
who
is
responsible
for
it,
so
the
best
thing
is
to
post
to
the
ux
group
in
in
the
Gidget,
Channel
and
I.
Think.
The
best
thing
also
would
be
to
pick
your
most
important
point
and
try
to
start
with
that
and
leave
the
others
on
the
left
for
the
for
the
moment
and
just
start
with
one
point,
and
then
we
can
get
a
discussion
about
this
point
in
our
ux
meeting
notes:
okay,
most.
D
The
easiest
decision
is
proposing
in
the
chat
to
create
an
epic
ticket
to
summarize
all
those
points
and
each
of
them
in
a
separate
ticket
on
their
jira.
If
you
know
how
to
do
that,
please
get
it,
don't
hesitate
because
guitar
is
fine,
but
the
thing
is
information
tends
to
be
lost
because
it's
not
really
well
structured
and.
E
D
C
E
Yeah
but
I
think
it
it's.
Okay,
if
you
have
an
epic
but
I,
think
it
would
work
with
labels
as
well,
so
I
think
don't
put
20
points
in
it
now,
which
will
never
get
finished
because
nobody
is
there
just
start
with
one
and
then
maybe
you
can
provide
some
yeah.
Even
if
you
don't
provide
the
code,
you
can
provide
some
sketches
or
screenshots
or
how
to
make
it
better
or
you
can
investigate
how
to
yeah
to
replace
spgs
in
a
theme.
For
instance,
these
are
things
yeah
which
need
to
be
done.
G
G
Okay,
because
I
have
my
experiences
in
life,
yeah
and
I
had
so
many
ideas
and
I
went
to
the
the
powers
to
be
yeah
and
they
didn't
say
great
yeah
that
you're
interested
this
time
to
create
for
your
for
internet,
for
your
cooperation,
yeah
yeah,
but
sorry,
no,
we
don't
implement
it
yeah
and
all
the
time.
Okay,.
D
E
E
G
E
Yeah,
so
that's
a
good
point,
so
I
think
the
best
thing
is
to
start
with
this
one
topic
and,
first
of
all,
before
you
implement
something
discuss
it
on
guitar.
So
we
can
have
a
discussion
around
this
point
and
if
a
lot
of
people
agree,
then
we
can
start
with
an
implementation,
and
maybe
it's
a
draft
pull
request.
So
we
can
get
feedback
very
early
and
then
you
see
before
you
spend
too
much
time.
You
see
if
it's
yeah
the
right
direction
or
not
yeah.
G
E
You're
right,
it
does
not
make
sense
that
you
are
now
taking
a
break
of
two
months
working
and
presenting
everything,
and
then
we
say:
oh
no,
this
doesn't
make
sense,
so
I
think
early
feedback
would
help.
So
even
if
you
don't
Implement
something
and
provide
screenshots
or
mock-ups
or
whatever
it
helps
to
discuss
the
topic.
E
G
G
G
B
C
From
our
side,
yes,
it'll
be
implementation
like,
if
not,
if
not
exact
but
heavily
guided,
so
that
we
can
make
sure
that
it's
it's.
B
G
My
points
is
screen
State
yeah,
which
is
wasted
Yeah
by
vertical
spacing
yeah.
That
means
increase
scrolling
yeah.
G
It
means,
if
you,
if
you
in
the
in
the
sidebar
menu
yeah
on
the
dashboard,
there
are
the
big
cues
and
the
build
Executives
below
the
bigger
the
menu
or
the
thought
of
the
menu
is
above
the
less.
These
two
items
are
displayed
below
and
and
directing
the
company
where
we
hit
so
many
that
I
had
to
scroll
to
see
all
the
the
ceramic
Bills
currently
running,
Pizza,
yeah
and
scrolling
is
bad
yeah
if
it
is
avoidable
by
a
contains
menu,
for
instance.
In
this
case.
G
E
Thank
you
I
think
the
sidebar
is
something
which
is
Young
also
trying
to
improve
and
to
yeah
to
restructure
because
yeah.
Currently
there
are
too
many
items
in
the
sidebar
and
I
think
he
made
already
some
progress,
but
currently
the
progress
is
only
visible
in
the
Jenkins
Administration
section,
which
I'm
not
using
at
all
and
so
I'm,
using
configuration
as
code
so
I'm
just
going
to
see
the
build
results
and
yeah
nobody's
working
on
that
topic
currently
so
yeah.
This
is
something
we
can
improve.
I
think.
C
Okay,
do
we
want
any
follow-up
on
this
or
just
leave
it
for
discussions
and
getter,
and
then
ticket
creation
for
now.
E
C
All
right,
thank
you.
Jerry
Jenkins,.
C
Resolved,
that's
good
anything
else.
To
add
to
that.