►
From YouTube: Jenkins UX SIG Meeting 26 Apr 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:
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.
A
Okay,
then,
let's
get
started
so
Jan
I
think
the
what's
happened
recently
between
your
work
and
Basel
Crow's
work
and
Tim
Jacob'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
of
issues
that
are
open,
but
a
number
of
them
are
green
right.
A
number
of
them
have
been
closed
out.
B
Nothing
it's
looking
really
good,
though,.
A
B
Yeah,
that
was
the
drop
down
improvements
that
that
made
it
for
2.402
I.
B
You
checked
out
the
latest
weekly
on
weekly.ci.
You
should
see
the
drop
downs
there
now.
B
Yeah
so
they're
powered
by
Tippy,
so
the
same
as
the
two
tips
as
well.
A
B
Sorry,
no,
that's
nothing
from.
A
A
B
Just
to
show
a
screen,
so
the
first
one
is
related
to
the
login
and
register
flow,
got
a
PR
open
for
this
and
there's
also
a
post
on
the
community.
Forum
just
get
some
discussion
so
if
I
hit
login
instead
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.
B
B
If
I
go
to
a
project,
yep
hit
configure
yep
hit,
this
project
is
parameterized.
This
Branch
replaces
the
previous
heteronist
button.
B
Previously
it
was
like
a
UI
button
and
the
drop
down
is
also
you
who
you
buy.
That
replaces
it
with
the
new
drop
downs
that
we
have.
B
Before
and
we
also
have
the
search
bar
that
we
had
before
so
this
is
kind
of
consistency
really
so
yeah.
That's
that's
already.
I'll,
probably
open
a
PR
for
this
moves.
I
kind
of
got
rid
of
PRS
they're
in
progress.
Yeah
looks
like
so.
A
B
Search
was
there
previously,
okay
with
the
Yahoo
venues.
It's
just
been
introduced
into
the
new
world
of
of
movies,
really
just
to
demonstrate
how
the
features
that
are
carrying
across
not
losing
any
functionality,
but
it's
a
kind
of
changing
framework.
B
So
that's
that
really
for
me,
hopefully
have
that
up
relatively
soon
Ash.
A
A
So
Christina
did
you
want
to
do
you
want
Are
there
specific
things
you'd
like
to
highlight
in
terms
of
what's
coming
there,
we've
got
an
a
jira
ticket
that
Christina
has
just
recently
created
here
for
compliance
or
for
for
keyboard
navigation
Christina.
You
want
to
talk
further
about
where
this
is
going.
A
Yeah
so
you're
still
muted
Christy.
There
we
go.
D
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
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.
D
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.
D
So
if
somebody
else
wants
to
pick
something
up
later,
we've
got
a
kind
of
documentation
Trail
for
for
things,
Mark
shared
the
there
was
an
accessibility
report,
the
German
one
I've
uploaded,
the
English
I
ran
it
through
a
translator,
and
the
English
is
a
little
funny.
D
Is
enough
to
to
get
a
point
across,
it
was
actually
really
good
because
their
findings
were
very
much
in
line
with
hours,
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,
I
couldn't
so
that
was
great.
So
this
is
kind
of
a
nice
comprehensive
report,
but
yeah
we're
on
the
we
had.
D
We
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
going
to
be
devoted
to
this,
so
that
I
can
actually
just
I'm
suffering
a
little
bit
from
like
one
human
in
one
book
Etc
but
like
Fridays
are
going
to
be
my
like
headstand
accessibility
time.
D
So
hopefully
the
navigation
stuff
gets
wrapped
soon
seems
fine,
though
I've
done
it
I've
I've
dug
around
in
it
and
played
with
it
a
little
bit
and
I
think
I'll
be
able
to
to
do
what
I
need
to
do
to
fix
it.
D
There
was
a
usability
report
as
well,
and
I
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.
D
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
non-accessible
just
best
practices
perspective
or
not.
A
C
D
So
I'm,
just
ignoring
that,
but
I
will
document
what
I
mean
we'll
talk.
We
documented
in
the
code,
but
it
I'll
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
so
it
exists
somewhere.
D
D
B
D
I
was
just
wondering
we
were:
there
was
a
discussion
about
hiding
it
and
I
really
I
don't
like
to
hide
it.
I
know,
that's
already
done
elsewhere
and
there's
kind
of
a
president
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.
Kind
of
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,.
A
D
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.
There
was
just
something
that
came
up
this
week.
That
I
wanted
to
know
if,
like
that,
something
actively
being
worked
on-
and
you
know
but.
A
A
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.
A
You
need
to
get
off
this
thing,
so
my
my
notion
was
extend
the
concept
of
an
of
an
admin
monitor
to
allow
us
to
store
definitions
of
admin,
monitors
inside
Jenkins
itself
and
say
if
the
file,
slash,
Etc,
OS,
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?
A
C
What
difference
exactly
do
you
make
with
implementing
an
administrative
monitor.
A
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.
C
A
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,
if
they
dis,
if
they
they
just,
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.
C
Yeah,
that
would
actually
be
very
interesting
yeah
that
that
whole
concept
we
I
mean
beside
on
some
proper
reactor
stuff.
We
already
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.
A
Good,
okay,
so
so
I'll
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
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
3.14
isn't
supported
anymore?
A
A
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,.