►
From YouTube: Jenkins UX SIG Meeting 25 May 2022
Description
01:00 - June LTS backport review
04:30 - Keyboard shortcuts prototype
16:55 - Accessibility report on Jenkins (German language)
20:55 - New login screen
23:40 - Theming
26:25 - Open pull requests
A
Topics
I
had
on
the
agenda
for
today
include
oh
good
john's
here
excellent,
so
I
had
preparing
for
june
lts
as
one
topic
to
see.
If
there
were
additional
changes,
we
need
to
discuss
here
that
should
be
backported
ui
improvements,
jan
and
tim-
wanted
to
allow
time
here,
particularly
tim.
If
you
wanted
to
highlight
the
new
login
screen
or
any
other
topics,
and
I
had
included
a
topic
for
localization
and
crowd
and
enterprise
if
we've
got
time
any
other
topics
that
need
to
be
added
to
the
agenda.
A
Okay,
great,
so
then,
then
for
me,
the
first
topic
was
prepping
for
the
june
lts.
There
are
some
some
things
that
were
mentioned
or
are
open,
as
poll
requests
to
jenkins
corps.
That
tim
I
wanted
to
use
is
a
chance
to
check
with
you
and
with
yon
to
see.
If
there
are
things
where
you
say:
hey,
this
should
be
backported
or
that
should
be.
A
B
A
A
A
B
C
A
A
D
B
D
Awesome,
okay,
so
the
whole
idea
is
just
to
kind
of
improved
navigation
around
jenkins,
with
the
use
of
keyboard
shortcuts
and
say.
If
we
go
to
open
up
a
project,
you'll
now
see
that
certain
actions
have
little
keys
assigned
to
them,
and
so
you
can
press
these
keys
on
the
keyboard
to
actually
activate
those.
So
if
you
press
w
goes
to
your
workspace
press
b
to
build
a
job
and
if
you
press
s
to
go
to
the
configure
screen,
so
it
just
works
like
that.
D
D
D
So
if
you
hit
the
keyboard
shortcuts
in
the
footer
you'll
get
this
small
little
model
will
just
explain
the
different
keyboard,
shortcuts
and
they're
available
to
you
and
you
can
kind
of
interact
with
them.
Whilst
this
dialogue
is
open
about
actually
interfering
with
the
page,
so
you
can
try
them
out
without
doing
any
damage.
So
if
I
press
command
k,
you'll
notice,
the
search
kind
of
option
highlights
press
c
console.
Does
it
then
j
or
question
mark?
Let's
show
the
keyboard
shortcut
dial
up?
That's
that's
just
a
really
simple
look
at
it.
A
So
how
do
how
do
we,
how
do
we
referee
or
control,
who
adds
which
shortcuts
so
b,
feels
like
a
great
shortcut
for
build
now,
but
I
happen
to
be
named
bob
and
I
think
bob
should
be
the
preferred
shortcut
and
I'm
going
to
create
a
plug-in.
That
makes
bob
no
sorry
bad
example,
but
you
probably
get
my
idea
yeah.
D
D
A
E
A
That
looks
great
any
any
problems
you've
encountered
or
things
where
you
saw.
Oh
hey.
This
is
a
risk
for
this
area
that
okay,
the
search
dialogue,
for
instance,
is,
is
far
from
far
from
the
capabilities.
I
would
dream
we
had
there.
You
know
it's,
it's
not
quite
doing
all
the
things
we'd
want,
but
are
there
other
things
that
you've
seen?
Oh
here
are
potential
struggles
or
challenges
with
it.
A
F
So
just
the
four
points
I
have
concerning
data
approach,
so
first
one
thank
you
for
the
proposal
in
terms
of
accessibility,
user
experience
for
power
user.
It
seems
to
be
a
very
nice
approach.
I
will
say
the
drawback
is
that
we
will
have
to
increase
the
performance
of
jenkins
to
suit
this
kind
of
feature
we
are
proposing
to
the
user,
but
that's
the
more
interesting
aspect.
I
have
three
questions
concerning
this
feature:
could
you
just
open
one
page
with
the
the
shortcut
being
visible
with
the
keystrokes
yeah?
F
F
F
My
gut
feeling
with
what
I
have
seen
in
the
past
is
that
this
kind
of
feature
is
very
good
most
of
the
time,
except
for
some
pages,
where
the
javascript
is
perhaps
a
bit
not
really
good
practice
following
good
practices
and
interacting
with
expected
feature.
For
example,
if
you
are
starting
to
write
something
in
the
search
bar
and
the
javascript
is
perhaps
not
written
correctly,
your
keystroke
inside
the
search
bar
could
trigger
some
shortcut.
F
F
D
Sure
so
that
first
one
was
really
good
about
the
kind
of
tool
tip
or
title
showing.
It
could
totally
be
confusing
if
you're
not
sure
what
these
little
keys
mean.
That's
really
awesome,
so
I
can
definitely
add
like
a
tooltip
or
something
or
I'm
not,
maybe
if
we
just
even
removed
them
and
relied
on
the
the
modal
could
be
an
option.
D
I'm
not
too
sure
what
the
best
kind
of
approach
is
right
now,
but
it's
definitely
worth
exploring
as
for
say,
you're
typing
in
the
search
bar
and
you
press
one
of
the
keys
that
are
kind
of
assigned
to
a
say,
sidebar
item,
for
example
the
library
we're
using
for
this
disables
the
keyboard
shortcuts.
If
you're
entering
into
an
input,
that's
not
an
issue.
Thankfully
I.
D
And
then
for
the
last
point
yeah,
I
think
we're
gonna
need
some
sort
of
maybe
alert
system
in
the
in
the
console,
for
example,
to
kind
of
flag
if
a
shortcut's
been
kind
of
overwritten
or
if
it's
being
used
twice
now.
You
certainly
wouldn't
want
to
press
the
button
and
have
two
different
things
happen:
that'd
be
pretty
horrific,
so
something
that
could
flag
to
say
a
plug-in
developer
before
they
tried
to
release.
It
would
be
really
really
helpful.
F
A
Now
now
to
to
sort
of
as
a
counter,
though,
to
vodak
your
point,
we
already
have
symbol
annotations
that
have
the
risk
that
users
care
that
a
plug-in
maintainer
can
just
like
mark
wait
made.
The
mistake
of
doing
can
define
a
symbol,
get
that
in
fact
overrides
a
pipeline
step
get
and
is
not
a
good
thing.
So
so
so
this
collision
thing
we've
already
got,
but
I
think
it's
it's
worth
if
there
are
ways
to
avoid
hitting
the
collisions
or
warn
people
about
a
collision.
That's
that's
certainly
healthy.
A
D
D
The
input
would
have
a
kind
of
modal
will
pop
up.
You
could
kind
of
search
on
the
screen.
I
was
basically
extending
that
to
be
more
like
a
command
palette
that
you'd
find
in
kind
of
visual
studio
code,
or
something
like
that.
It's
quite
easy
to
find
different
actions
on
jenkins,
but
I
hope
you
have
something
to.
A
A
Okay,
no
objections
good,
so
I
was
contacted
by
a
person
from
I
believe
check
the
czech
republic
or
from
croatia.
I
do
forget
exactly
where,
but
what
they
were
suggesting
was
hey.
They
did
this
60
page
assessment
of
jenkins
accessibility
as
part
of
a
company
requested
company
purchase
thing
from
some
someone
and
they
they
they
asked
us
hey.
Are
you
interested
in
this
report
and
how
is
the
best
way
to
bring
this
report
to
the
jenkins
project?
If
you
are
interested
it's
right
now,
german
language,
it's
right
now,
private
to
them.
A
So
it's
it's,
not
a
public
document
yet,
but
they've
offered
to
translate
it
to
english
and
to
be
available
now.
My
question
to
to
the
ux
sig
was:
is
that
of
interest,
and
how
would
what
would
be
the
most
approachable
way
if
it
is
of
interest
to
bring
that
report
for
for
discussion
and
consideration.
A
B
A
So
so,
if
we
started
with
attach
the
the
master
pdf
file
to
an
epic
in
jira
and
then
create
sub
items
as
we
as
we
need
to
as
we
feel
to
based
on
those,
because
none
of
these
things
are
a
commitment
in
any
way,
they're
all
hey.
What
can
we
do
what's
of
interest,
etc?
But
you
would
be
okay
if
we
put
an
archive
a
copy
of
that
pdf
on
that
top
level,
epic
and
then
used
issues
in
jira
to
report
record
things
or
if
someone
said
hey,
I'm
gonna,
I'm
gonna
try
to
improve
this.
G
Yeah,
I
think,
that's
a
good
place
to
start
and
there's
probably
a
lot
of
low-hanging
fruit
that
we
could
find
in
that
report.
I
imagine
some
things
will
be
easy
to
fix
and
others
might
be
bigger
projects.
But
if
there's
things
that
are
easy,
then
it
would
be
good
to
make
you
know
bite-sized
tasks
in
jira
and
we
could
even
advertise
those,
as
part
of
you,
know,
future
hackathons
or
contributions.
A
Great
all
right,
thank
you.
Okay,
so
I'll
I'll
talk
with
them
talk
with
them
see
if
I
can
persuade
them.
I
think
they've
actually
shared
the
german
language
document
with
me
and
have
stated
that
they're
willing
for
it
to
be
made
public,
but
let
me
double
check
with
them
and
if
so,
then
I'll
likely
upload
the
german
language
document
and
and
see
if
they're
willing
to
translate
if
they're
not
willing
to
translate,
we
still
have
the
option
of
using
the
german
language
document
as
as
it
exists
great.
A
B
B
Inputs
are
consistent
with
the
rest
of
jenkins.
Now
check
boxes
actually
have
a
focus
state.
Previously
they
didn't
have
a
focus
state,
but
it
wasn't
really
noticed
because
you
had
to
tab
off
past
the
sign
in
button
and
there's
no
sign
up
enabled
in
this
instance,
but
similar
sort
of
things
applied
to
the
sign
up
page.
B
B
So
that
was
the
reason
to
do
that.
But
then
I
found
that
the
focus
state
didn't
work
and
I
think
there
was
another
issue,
so
yeah
should
just
be
a
lot
more
consistent
with
the
rest
of
jenkins,
okay,
also
paul.
I
think
that
code
now
was
was
completely
isolated
before,
but
it's
now
pulling
in
the
list
files
for
the
components,
all
the
components
that
we're
using
are
imported
in
those
files,
rather
than
copy
pasting,
a
css
and
using
different
css.
A
A
A
B
B
This
is
because
we
also
want
to
use
this
in
the
configurations
code
plugin,
which
is
very
dependency
light,
and
even
if
those
differences
are
kind
of
fine
it'll,
be
nice
not
to
include
them
but
yeah.
So
that
should
be
coming,
and
so
people
using
their
dart
theme
will
no
longer
be
blinded
with
the
code
blocks.
I
know
yarn
tried
to
hack
that
into
the
plugin
as
well
just
with
some
css
overrides,
but
hopefully
we
won't
need
those.
A
B
A
B
B
B
A
E
B
E
B
Yeah
and
one
problem
we
have
is
that
there's
no
easy
way
to
override
plug-ins
and
acceptance
tests,
harness
it
doesn't
increment,
it
doesn't
integrate
with
incrementals
at
all.
I
think
we
could
add
some
hacky
code
with
the
current
setup.
We
could
add
some
hacky
code
to
the
jenkins
file
to
download
the
plugins
and
put
them
in
a
specific
directory,
but
it's
not
very
nice,
so
we'd
either
need
to
come
up
with
a
more
generic
handling
of
it.
B
B
We
can
handle
core
changes
very
easily,
but
we
can't
really
handle
plug-in
changes,
at
least
by
running
the
whole
suite.
Someone
can
locally
run
it
and
do
what
they
need
to,
but-
and
so
that's
the
problem
at
the
moment,
because
a
lot
of
plugins
depend
on
matrix
earth
and
because
the
matrix
and
the
matrix
earth
part
of
ath
is
failing,
and
that
causes
a
lot
of
tests
to
fail.
So
we
don't
know
if
those
tests
are
impacted
until
this
is
released.
A
B
B
But
yeah
that
was
so
that's
one's
quite
good
one,
because
I
think
it
should
fix
cross-site
scripting
issues
like
generically
across
tooltips
anyway.
So
it
removes
the
problem
by
not
executing
html
in
the
default
attribute.
You
have
to
supply
your
own
attribute.
You
have
to
explicitly
opt
into
it
so,
rather
than
the
default,
it's
an
opt-in
behavior
to
be
able
to
supply
html.
A
A
B
A
B
A
B
Yeah,
so
so,
bomb
tests
are
failing
and
a
few
plug-ins
not
very
many,
with
some
weird
undefined
error
when
it's
trying
to
add
the
event
selector
but
like
it's
hard
to
tell,
because
I
think
it
only
gives
the
line
number
of
one.
But
it
looks
like
it's
saying
basically
window
is
undefined
because
it's
literally
accessing
window.
B
B
A
G
There
anymore
action
items
for
the
the
changes
to
adapt
the
folders
plug-in
and
work
in
the
workflow
job
plug-in
to
display
the
new
ui
features,
because
we
had
some
pull
requests
for
those
that
are
not
just
they're,
not
blocking
this
change
but
they're
related
to
it
and
that
they
would.
They
would
allow
other
plugins
to
use
this
new
feature.
B
G
G
Really
all
I
was
asking
was
well
whether
there's
any
any
additional
action
items
for
those
it
sounds
like
it's.
It's
not
like.
We
just
need
to
wait
for
core
to
be
released
and
for
the
plug-in
maintainer
to
be
willing
to
adjust
the
baseline
and
then
those
other
two
can
be
released,
which
sounds
great.
B
B
Think
we,
I
think
so
the
next
one
ath
tests
are
failing.
So
I
think
I
think
some
ath
tests
have
started
failing.
So
we
need
to
check,
we
need
to
fix
them
and
get
them
passing
again
and
it
kind
of
comes
back
to
basil
some
of
the
ata
stuff
from
the
mailing
list,
but
yeah.
I
would
be
good
to
have
a
way
that
it
doesn't
randomly
break.
A
B
And
straightforward:
there
is
something
like
12
tickets
failing,
and
so
we
need
to
check
if
they're
legitimate
failures
and
if
they're
and
well
either
way
they
need
fixing.
We
don't
really
want
to
be
making
judgement
calls
because,
as
has
happened
previously,
they
were
just
shadowing
so
when
those
tests
were
fixed,
they
actually
failed
later
on.
So
I
don't
really
want
to
be
accepting
things
with
the
tests.
Failing
that
vector.
B
B
A
B
A
D
G
B
D
D
So
after
the
kind
of
symbol
pr
went
in
that
kind
of
broke
a
few
areas,
a
bit
kind
of
hesitant
to
kind
of
open
it,
but
I
can
definitely
kind
of
bring
it
up
to
date
with
master
and
see
what
it's
like
now
or
we
could,
alternatively,
just
do
about
the
refactor
and
just
replace
the
symbols
in
the
svg.
If
that
makes
sense
directly
yeah,
whatever
makes
sense,
I
guess,
but
it
would
be
nice
to
have
the
kind
of
weather
icons
accessible
as
jenkins
symbols.
D
A
D
A
D
It's
a
weird
kind
of
we
used
a
ball
back
in
the
day
and
there's
a
whole
component
based
around
it
and
it's
all
kind
of
hierarchy.
It's
all
a
bit
weird,
so
I
looked
at
replacing
that
make
it
a
bit
simpler
and
also
integrated
with
the
new
symbols
that
we've
got,
but
just
a
bit
hesitant
if
any
plug-ins
use
it
and
whatnot.
I
don't
want
to
break
anything
touchwood
all
right.
A
Okay,
next
topic
I
had
was
localization
and
crowd
and
enterprise
just
to
to
give
thanks
to
alex
brandos
who's,
been
doing
wonderful
things
with
crowding
thanks
to
crowden
enterprise,
for
donating
the
license,
and
thanks
to
translators
like
bruno
and
alex,
and
chris
stern
we've
got
translations
so
right
now,
we've
got.
Is
it
seven
or
eight
different
plugins
that
are
working
through
here,
and
we
hope
soon
to
do.
Some
highlights
on
how
you
internationalize
jenkins
plugins,
to
encourage
more
of
this
sort
of
work.
B
A
G
Yeah,
I
think
that
existing
plugin
has
25
000
installations
or
something
around
that
order.
So
you
know
updating
it
and
releasing
a
new
version
would
essentially
expose
tens
of
thousands
of
people
to
this
new
crowded
website,
which
is
a
lot
more
people
than
you
could
expose
than
just
by
advertising
on
a
few
mailing
lists.
Right.
G
A
Then
I've
got
one
more
item
that
I
wanted
to
add
to
the
agenda,
just
to
ask
for
advice
and-
and
I
this
is
piracy
of
the
agenda,
but
I
wanted
to
ask
about
a
ui
thing
that
I'm
considering
doing
to
one
of
my
plugins,
but
I
wanted
yon
and
tim,
while
you're
here
to
guide
me
on
this.
So
I've
got
a
plug-in
that
I
maintain
called
job
priorities.
It
puts
itself
over
here
on
the
left
hand
side
in
the
sidebar.
A
B
Of
points
one
avoid
sidebar
links:
if
you
can,
they
just
take
up
space,
they
make
you
scroll
down
and,
and
then
a
lot
of
them
aren't
used
very
much
two
sometimes
they're
there.
If
non-privileged
users
need
to
need
to
use
them,
but
you
can
also
change
that
so
that
privileged
users
see
it
on
the
managed
jenkins,
page
and
non-privileged
users
there.
C
B
A
C
B
A
So
the
credentials
plugin
is
an
example
of
that.
So
it
does
that,
oh
good,
so
I
can
look
at
somebody
else's
code.
Good
all
right!
Thank
you
so
so
for
me.
Similarly
lockable
resources.
Now
I
don't
I'm
not
a
maintainer
of
lockable
resources,
but
lockable
resources
has
has
this
this
same
kind
of
it's
right
there
and
I
never
use
it.
I
don't
know
other
people
who
use
this
this
sidebar
link
it
could
conceivably
move
to
manage
jenkins
and
and
then
for
non-admin
users.
If
it's
needed
be
placed
here
as
well.
Great.