►
From YouTube: Jenkins UX SIG Meeting - 14 October 2020
Description
This edition of the UX SIG meeting featured more discussion about when to merge the Tables to Divs transition for forms. The consensus was that this should land just after the LTS baseline had been selected. Felix provided an update on the focus on updating JQuery since the current library is very out of date and could pose vulnerabilities, though none have been proven.
A
A
Go
ahead,
felix
yeah!
No,
no,
sorry!
Sorry,
please
go
ahead.
I
was
just.
I
was
just
saying,
welcome
small
group
again
today
everyone
has
access
to
the
agenda
here.
Let
me
move
this
zoom
bar
out
of
the
way.
Of
course,
we
can
add
things,
but
it
looks
like
we're.
Gonna
have
a
little
update
on
tables
to
divs.
If
going
to
update
up
on
some
jquery
work,
and
then
I
have
some
icons
to
run
by
the
group
as
well.
B
A
C
Yeah
and
so
there
are
some
plugins
that
are
still
broken,
whether
we
care
or
not
to
the
artifactory
and
what
plugins
are
the
two
that
I
know
of
that
are
broken
artificially
one
system
yeah.
I
think
we're
probably
just
going
to
leave
it
to
jfrog,
it's
a
huge
plug-in
and
they're
very
slow
to
review,
and
they
suddenly
come
back
with
an
issue
and
you
fix
it.
C
B
B
B
A
B
Yeah,
no,
I
I
it's
everybody.
It's
already
there,
it's
the
consensus,
that's
that
was
my
impression
as
well
cool
yeah.
So
I
also
wanted
to
give
an
update
of
some
introducing
work.
We
are
doing
with
jquery
in
cloud
is,
and
why
we
will
have
a
bit
of
reduced
velocity
of
on
actual
development
work
for
ui
stuff,
so
in
class
we
are
focusing
at
the
moment
on
upgraded
jquery
and
the
dependency
of
jquery
across
the
many
plugins,
because
most
of
them
use
really
outdated
versions
and
insecure
versions.
B
So
it's
important
project
for
cloud
is
the
upgrading
and
display
in
screen.
Protocol
cloud
is,
and
it's
also
part
of
ui
modernization,
even
though
it's
not
visual,
so
we
expect
it's
to
take
around
a
month.
I
have
already
already
created
a
vr
against
jenkins
core,
which
is
waiting
for
until
next
year's
I'm
working
on,
for
example.
Tomorrow
I
will
try
to
update
it
on
pipeline
stage.
V.
Plugin.
C
B
Workflow
cps
some
plugins,
so
there
are
not
many
of
them,
but
we
are
focusing
on
that
right
now
and,
for
example,
we
will
not
be
able
to
work
on
iconography
until
that's
done
and
of
course
we
will
keep
involved
on
the
cx.
Joe
has
been
doing
amazing
work
on
iconography
and
he
will
keep
doing,
and
I
will
also
be
on
top
of
the
community
prs
and
everything
table
studios
emerging
is
just
that.
C
F
B
Blue
ocean
did
use
a
version
of
jquery
the
touch
it
had
it
on
the
palm.
It's
it
wasn't
it
wasn't
using
it.
So
I
have
created
a
perks
blue
ocean
for
that
it
shouldn't
have
an
impact
at
all
and
by
the
way,
regarding
blue
ocean,
I
was
taking
a
look
at
cliff
meyer's
spr
point,
a
proof
of
concept
and
for
the
pipeline
visa
is
visualization
and
equivalent,
and
it
looks
good
but
needs
more
back-end
work.
C
A
Okay,
well,
thanks
for
the
update
felix
yeah,
we'll
continue
to
be
involved,
but
as
far
as
pushing
changes
out,
it
will
have
a
slightly
reduced
philosophy
for
sure
cool.
I
think
that
brings
to
the
next
item
felix.
Maybe
you
could
drop
some
notes
on
this.
One
yeah
had
some
awesome.
Had
some
quick
icon,
update
proposals
here
I'll
share
these
in
getter
as
well
right
after
this
call,
since
we
do
have
a
small
group
here
and
what
I,
what
I
mean
by
icon
proposals,
is
just
trying
to
find.
A
Excuse
me
parody,
where
possible,
between
material
design,
icons
because
they're
easy
to
integrate
and
the
classic
jenkins
icons
and
updating
some
there,
but
then
also
creating
some
custom
solutions
where
necessary
and
in
this
case
also
leveraging
some
some
icons
from
the
neo
theme,
where
applicable
or
where
beneficial
so
we'll
look
at
those
and
just
to
clarify
that
these
would
be
three
distinct
sort
of
phases
in
icon
improvements
right
this.
This
would
not
all
be
one
pr.
A
This
would
be
a
gradual
thing,
so
some
some
general
icon,
replacements
and,
of
course,
there's
a
lot
more
icons,
even
just
within
managed
jenkins
page.
For
example,
that
would
need
consideration
here,
but
we're
trying
to
be
as
resourceful
as
possible
using
material.
We
all
know
materials
widely
used
and
widely
recognized
around
the
world,
and
so
has
a
lot
of
familiarity
that
we
can
kind
of
leverage
there.
But
a
lot
of
these
icons
may
also
have
distinct
meanings
in
like
an
android
environment
that
could
be
confusing
here.
A
So
so,
there's
a
give
and
take
I
imagine
more
of
these
will
need
to
be
custom
than
than
we
are
realizing.
But
but
here
are
some
proposals
for
how
we
could
map
a
few
of
these
common
ones,
and
we
can
come
back
to
this
in
just
a
sec
I'll
run
through
the
two
more
two
more
screens
here
and
we
can
talk
about
them
for
our
build
status
indicators.
A
A
There
is
not
really
a
good
parity
for
what
material
design
offers
here,
and
we
have
some
issues
in
the
current
icon
selection,
where
a
lot
of
these
colors
are
very
close
to
one
another.
We
have
like
the
light
gray.
We
have
a
darker
gray.
We
have
a
deeper
gray
even
than
that
which
present
a
lot
of
visual
contrast
issues.
A
The
blinking
in
and
of
itself
for
builds
that
are
in
progress
can
be
problematic
for
some
users,
depending
on
the
tech
they're,
using
to
to
look
at
their
at
their
jenkins
instance.
That
creates
a
lot
of
issues
if
colors
are
not
configured
the
same
way
that
they're
being
configured
for
developers
contributing
to
jenkins-
and
I
think
you
get
what
I'm
saying
these
these
could
use
some
more
love.
A
Some
pictograms
to
kind
of
represent
in
case
color
is
is,
is
a
real
problem
for
a
particular
user
and
they
have
another
indicator
they're
beyond
color,
and
so
these,
of
course,
are
from
scratch.
These
are
not
for
material
or
anything
like
that,
and
so
these
would
be
a
different
implementation
process,
but
we
would
merge
them
in
separately
and
I
think
we
need
a
lot
of
feedback
on
these
icons,
but
I'd
love
to
hear
y'all's
feedback
in
this
call
too
we'll
jump
right
back
to
those
the
last
one
was.
A
A
A
A
A
A
B
E
B
A
A
C
A
I
think
the
thing
the
thing
about
trying
to
be
resourceful
with
something
like
material
is,
of
course
these
are
all
designed
for
very
different
ecosystems
and
carry
different
meetings
as
a
result.
So
I
think
that's
a
good
point.
That
would
be
one
where
I
would
probably
try
to
create
something
in
the
same
style
as
these
material
icons,
but
that
is
more
appropriate.
D
I
mean
I
I
do
think
this
is
a
huge
improvement
over
the
existing
ones.
So
that's
clear
on
the
modernization
there
is
is
clear
as
well,
but
yeah
some
of
them
are
tricky.
I
I
do
like
this
particular
page.
Maybe
the
unlockable
resources
are
steam,
pointed
it's.
It's
one
of
the
more
difficult
to
find
the
equivalent
to
the
other
screen
on
the
on
the
build
statuses.
D
That's
that's
a
bit
tricky
because
there
are
lots
of
things
to
lots
of
states
to
represent,
so
I
I
would
try
to
give
it
a
thought.
I
I
I
do
like
the
rotation
for
that.
You
just
mentioned
for
the
the
things
that
are
in
progress,
but
the
others
I
I
will
try
to
give
you
a
thought
and-
and
if
I
come
up
with
some
ideas
I
will
let
you
know
sure
yeah.
A
Definitely
open
very
open
to
feedback
here,
because
it's
a
very
constrained
small
space
here.
Each
of
these
shapes
inside
of
these
circles
carries
a
lot
of
meaning
and
that's
different
to
different
users.
So
I'm
going
to
post
this
and
get
her
do
take
your
time
and-
and
you
know
whatever
feedback
you
have-
would
be
very
welcome
for
sure.
A
F
A
No
switches
yet
no!
This
is
just
a
just
a
pitch.
I
think.
There's
let's
say
my
blue
balls
are
going
yeah.
I
think
there's
a
lot
more
connotation
with
green
as
a
color
that
we
could
do
there,
and
then
that
gives
us
the
chance
to
kind
of
leverage
that
jenkins
blue
in
a
different
place
rather
than
having
so
many
grays
in
this
particular
set.
F
B
B
Well,
I
mean
that's,
that's
for
you,
that's
what
I
review
what
the
reviews
are
for,
so
something
I
definitely
wanted
to
mention
about
this.
Is
that
the
reasons
these
are
separated
into
three
different
blocks?
It's
something
I
suggested
to
you
is
because
I
think
the
implementation
should
also
be
separated.
B
C
F
C
F
So,
for
example,
yeah
there
is
new
item
page,
which
uses
relatively
high
resolution
icons.
There
is
also
ticket
for
actually
replacing
words
describing
job
types
by
icons
and
yeah.
These
ones
are
quite
big,
so
at
the
same
time
there
is
no
need
to
replace
them
immediately
because
they're
already
quite
fancy
so.
C
B
E
F
So
there
is
no
item
for
run
the
build,
etc
because
yeah
the
problem
isn't
with
items
on
their
own,
but
with
combinations
of
items
in
jenkins
we
still
have
a
side
panel
with
quite
a
number
of
items,
sometimes
a
dozen
of
them.
So
we
need
to
ensure
that
any
item
will
be
quite
distinguishable
from
each
other.
B
B
Definitely,
what
I
was
planning
wasn't
just
getting
into
the
a
l
icon,
jelly
helper
hijacking
and
hijack
it
and
inside
it
detect
if
the
class
is,
for
example,
for
context
for
context.
The
way
many
icons
are
set.
There
is
a
jelly
template
and
that
if
it
receives
a
css
clash
class
corresponding
to
the
new
item,
it
will
show
this
icon.
It
will
have
different
based
on
the
css
class.
It
receives,
will
map
it
to
different
icons.