►
From YouTube: Jenkins UX SIG Meeting - Jan 22 2020
Description
This is a recording of the 4th meeting of the Jenkins UX SIG. It included updates about development progress for the revamped Jenkins UX as well as discussion about the using Gitter vs Slack for communication and the potential adoption of the Jenkins UI Themes plugin.
B
B
A
C
Joe
I
did
need
to
ask
for
a
revision
to
the
agenda.
I've
got
a
drop
off
at
30
minutes
into
the
meeting.
I
put
an
item
as
the
very
last
item
on
the
agenda.
If
we
could
sneak
it
in
before
I
exit
I
would
much
appreciate
it,
but
it
doesn't
have
to
be
immediate
just
if
we
can
sneak
it
in
before
we've
completed
30
minutes
no.
A
B
A
B
A
B
For
anybody
watching
online
I'm,
Felix
Cayuga
from
cloud
with
independent
developer
who's
participating
of
this
on
this
sig
and
who
is
developing
the
UI
changes,
so
the
attenti
for
today
is
to
well
talk.
I
would
like
to
talk
a
little
bit
of
house.
Luck
is
working
for
us
how
everybody
feels
about
it
our
to
see
and
to
see
if
everything's,
okay,
we
will
continue
to
use
it
and
it's
hard
to
learn
if
any
feedback.
Basically,
after
that,
we
I
will
give
a
brief
update
of
what
we've
been
working
out.
This
past
15
days,
hey.
B
Now,
I'm
moving
it
myself.
After
after
it
I,
we
will
be
talking
about
abducting,
were
retiring.
The
Elife
in
plugging
after
that
quick
development
update
and
then
we
will
talk
about
Joe
will
give
us
another
update
on
the
header
bar
on
the
header
bar
bar
designs.
We
leave
it
right
based
on
the
community
feedback,
so
yeah
you
will
see
so.
B
First
of
all,
it's
okay
for
everybody.
I
will
start
so.
First
of
all,
we've
been
using
slack
for
almost
two
months
here
now
or
four
month
and
a
half
so
and
I
think
it
was
great
when
in
for
having
those
long
discussions
and
the
squeak
and
the
chat
format,
work
really
well,
especially
when
talking
about
some
plugins,
but
some
people
did
complain
did
say
they
feel
it's
not
an
ideal
tool.
It
does
have
a
that
does
have
disadvantages.
B
D
Yes,
for
instance,
I
can
say
a
little
bit
about
my
experience.
Iii
think
it's
a
little
bit
complicated
I
have
so
many
channels,
but
actually
I'm,
just
using
one
channel,
so
I'm
not
sure
if
it's
configurable,
typically,
we
used
IRC
or
we
use
guitar,
but
now
I
haven't
yet
another
tool
which
I'm
just
using
for
user
experience
group
so
I
think
it
would
make
sense.
We
either
use
all
groups
in
slack
or
we
move
to
something
else.
D
D
In
I
think
I
have
about
20
channels
in
github
and
one
in
IRC
and
now
I
have
yet
another
in
slack,
so
I'm
not
really
sure
why
I
should
just
use
slack
for
a
user
experience
group
and
everything
else
is
in
Keeton.
So
it's
just
another
open
that
window
and
and
I
don't
see
that
there
are
many
different
features
in
slack
which
are
not
in
Keita.
So.
A
A
E
Get
us
free,
it's
kind
of
like
it,
just
behind
version
of
slack,
so
it's
got
something.
It's
got
some
great
benefits
for
open
source
that
you
can
just
sign
in
with
github
and
it's
all
public.
But
do
you
thought
you
don't
even
account
to
see
it,
but
it's
quite
it's
great
far
behind
in
usability
and
mobile
spit
mobile
is
the
biggest
complaint
that
it
has
and
also
frequent
disconnection.
E
This
being
threat
has
been
more
than
one
three
Donna
Jenkins
developer
mailing
list
ballots.
The
last
one
was
started
around
new
years
kind
of
got
to
hang,
really
saying
it's
on
his
list
of
things
to
look
at,
but
it's
not
very
high
up
there.
Everyone
knows
that
get
is
not
great,
but
it's
it's
an
OK
solution
and
satisfies
most
people.
A
Yeah,
there's
definitely
not
going
to
be
a
perfect
fit
great
I
get
wanting
to
have
it
all
in
one
place
for
sure
like
that
makes
good
are
very
appealing
to
me,
even
though
I've
never
used
it
before,
but
the
like,
if
you
like,
if
it
is,
if
we're
not
able
to
pop
in
on
the
phone
and
just
see
what
the
conversation
as
it
does
seem
like
a
disadvantage,
I
don't
have
super
strong
opinions
on
this.
Does
anyone
else
want
to
chime
in,
for.
E
A
C
I
I
echo
Tim's
observations
that
the
user
experience
in
Gator
is
far
behind
the
user
experience
in
slack,
but
the
community
is
far
ahead
in
Gator
compared
to
slack
right.
We've
got
as
Uli
noted,
one
slack
channel
for
UX
and
and
we've
got
many
many
getter
feeds
many
get
ur
channels
for
obscure
little
things
for
large
things
and
so
I'm,
hesitant
to
say
to
go
with
slack.
Considering
what
our,
how
much
critical
mass
we
have
around
ghetto
right.
A
Now
so
how
would
this
seem
as
a
as
the
next
step
for
everyone?
If
I,
just
every
cell
has
been
capturing
all
our
notes,
they're
in
the
pros
and
cons
of
both
and
then
I'll
remember
what
we
talked
about
your
tea,
so
maybe
I
can
consolidate
these
these
pros
and
cons
it
into
our
current
solution,
which
is
our
slack
channel,
and
everyone
has
been
part
of
this
thus
far
and
do
a
quick
vote
on
it
in
slack,
and
then
we
can
remove
it
or
not.
D
A
A
C
Sure
so
so
there
is
a
plug.
Well,
the
catalyst
event
that
caused
me
to
put
this
agenda
item
on
as
I
received
a
notice
from
github
saying
that
the
UI
themes
plug-in
has
a
known
security
vulnerability
and
the
vulnerability
is
it's
depending
on
Jackson
2.4
I
looked
at
the
history
of
this
particular
plugin.
It
doesn't
seem
to
have
been
through
many
releases.
It's
been
inactive
for
many
years.
My
thought
was
retired,
so
I
asked
the
maintainer
Tom
family
they're
less
committed
to
it.
C
Tom
fennely
said
yeah
I'm,
not
maintaining,
it
could
be
retired,
but
there
might
be
concepts
in
it
which
would
be
of
interest
to
the
UX
special
interest
group
I
have
I,
apparently
was
just
granted
or
have
been
granted
merge
permission
so
I
merge.
The
security
fix
onto
this
thing,
so
I
will
no
longer
get
email
from
github.
Therefore,
my
actual
personal
interest
in
this
plug-in
has
ceased
to
exist,
but
as
a
UX
cig,
if
you're
interested
in
it,
you
might
want
to
be
aware
of
it.
C
B
Okay,
okay,
so
yeah
I'm
new
to
the
project.
I
would
say
that
anything
that
causes
increases
the
complexity
on
yeah,
it's
not
for
the
best.
Only
if
it's
not
being
used,
I
would
say
it.
Maybe
it's
worth
considering
by
well.
The
most
active
contributors
to
doing
is
right,
I'm
maintainer,
to
maybe
to
do
something
about
it.
I
think
it's
worth
researching
I
will
I
will
do
research,
how
it
effects
to
see
if
it
affects
the
cig
work.
So.
C
And
FedEx
I
would
I
would
Lobby
that
keep
that
research
intentionally
unlimited
all
I
think
you're
looking
for
is
ten
minutes
of.
Is
there
something
wildly
interesting
in
this
conceptually
because
usage
in
the
community
is
a
good
indicator
and
simple
themes,
as
noted
by
Tim,
is
much
more
heavily
used
than
this.
Plugin
ever
was
yeah,
indeed
great,
so
I'm
gonna
leave
it
as
open
for
now,
not
archived,
because
I'm
satisfied
and
if,
if
any
additional
investigation
happens,
great
I
tried
to
build
it.
It
fails
one
of
its
tests.
B
B
How
to
for,
if
you
recall,
from
last
meeting
Olek
raised
some
points
about
how
we
could
merge.
Some
parts
have
enabled
some
parts
of
the
changes
but
stuff
like
the
header,
colors
and
the
logo
section
should
be
behind
the
feature.
Total
we've
been
looking
into
how
to
do
this.
We
will
probably
use
a
java
property
at
first
and
then
we
will
research
a
better
way
to
do
it
from
the
to
the
user
interaction.
B
But
first
we
will
just
you
know,
protect
property
at
the
startup
time,
and
what
we've
been
working
on
these
past
weeks
were
words.
The
work
on
replacing
the
J's
builder
front
completely.
The
tool
chain
based
on
J
is
builded
by
one
based
on
what
book
I
got
to
say.
Thank
you,
everybody
who
took
the
time
to
review
it
paid
attention
than
two
comments.
Thank
you
very
much
appreciate
it.
B
I
think
it's
it's
an
important
change,
because
all
day,
yeah,
basically
all
the
NEEMO
you
I've,
worked
and
expand
on
this
one,
even
though
Heather
once
is,
if
it's
March
I
can
apply
me,
there
are
some
optimizations
like
added
to
the
header
straightaway
so
other
than
that.
Not
much,
and
not
many
updates.
Basically,
okay.
A
A
A
This
will
probably
be
the
last
time
we
look
at
that,
but
we
have
some
updates
there
from
from
the
last
one
sorry
bear
with
me
I'm
just
looking
around
here,
then
we
have
the
opportunity
with
its
interactive
States
and
what
those
are
about
and
how
those
will
help
us
long
term
and
the
beginning
of
our
UI
color
palette
for
Jenkins,
so
yeah
you're
on
the
first
slide
there
all
right
so
basic
details
here
that
you've
seen
before
you
can
go
to
the
very
next
one
actually
yeah.
That's
me.
C
A
These
are
the
changes
since
the
previous
meeting,
so
following
feedback
that
we
had
going
on
there.
In
slack
the
placement
and
visual
treatment
of
the
admin
warning
indicator.
There
has
been
reconsidered.
It
also
has
a
text
label.
The
feedback
was
that
previously
it
looked
a
lot
like
a
lot
like
a
field
input
just
like
the
searchbox
did
it
wasn't
something
that
I
personally
found
super
concerning,
but
you
know
if
it
was
gonna.
A
And
so
yeah,
just
just
a
pretty
small
modification
there,
but
that
came
from
some
feedback
and
slides.
So
thank
you
and
then
the
second
thing
is
we
pared
back
the
aesthetic
changes
to
the
bread,
crumb,
bread,
crumb
bar
they're,
a
bit
more
ambitious
before,
but
something
we
realized.
Thanks
to
your
feedback
was
they
were
sort
of
making
a
certain
feature,
less
discoverable,
which
was
that
ability
to
to
use
the
be
dividers
there
to
hop
to
certain
pages.
So
now
it
should
be
a
little
bit
more
familiar.
A
There's
some
type
adjustments,
but
it's
not
quite
has
changed
and
we
can
go
to
the
next
one
Felix
and
the
last
little
note
there
is
that,
of
course,
whenever
we
make
a
change
like
that,
the
design
is
reconsidered
for
all
our
viewports.
So
that's
an
updated
view
of
what
the
tablet
size
and
the
mobile
size
would
be
similar
to
and
next
slide
Felix
alright.
So
this
is
just
I
wanted
to
take
just
a
moment
to
to
mention
sort
of
the
special
power
of
a
special
interest
group.
A
This
is
the
first
one
of
these
groups
that
I've
been
involved
with
for
Jenkins
and
I.
Think
this
is
a
really
interesting,
tiny
case
study
of
what
can
be
achieved
so
obviously
we're
just
getting
started
and
we're
just
a
few
meetings
in,
but
even
though
we're
just
ramping
up
and
in
the
big
picture,
this
is
having
a
pretty
big
impact
on
on
how
this
will
be
designed
and
how
we're
creating
these.
These
changes,
thanks
to
your
perspectives
and
your
feedback,
so
this
header
bar
might
seem
pretty
inconsequential.
A
A
So
this
is
where
the
design
of
it
was
two
sig
meetings
ago,
and
there
was
some
internal
deliberation
here
on
my
side
about
improving
the
design,
but
for
the
most
part,
thanks
to
your
feedback,
if
you
want
to
go
to
the
next
slide
Felix,
this
is
where
it
has
landed
and
for
some
reasons
that
are
obvious,
and
for
some
that
are
less
obvious,
it's
a
much
stronger
design.
So
thank
you
all
once
again
for
your
feedback.
I
think
this
is
just
a
cool
little
example
of
what
the
sink
can
do.
A
This
answers
a
lot
of
questions
for
for
the
design
of
future
components
and
will
help
speed
things
up
in
that
regard.
So
if
you
want
to
go
to
the
next
one,
if
anyone
wants
to
look
at
this
after
the
call
you're
welcome
to.
Of
course,
these
are
all
the
interactive
States
for
that
header
bar
component,
so
like
Hauer
I,
don't
have
to
explain
this
to
you
all,
but
basically,
how
does
the
design
change
aesthetically,
based
on
how
the
user
is
interacting
with
it
at
what
point
in
their
their
interaction
and
that
behavior?
A
So
this,
hopefully
just
gives
a
little
bit
of
context
for
two
things
which
the
first
one
is:
how
we're
thinking
about
these
components?
Sort
of
holistically
how
they
feed
into
this
long
term,
vision
for
ejectment
design
system
and
then,
secondly,
how
they
all
connect
and
inform
one
another,
and
this
will
solve
a
lot
of
the
problems
that
we'll
face
for
designing
future
components,
hopefully
speed.
Some
of
that
up
too,
we
can
hop
back,
but
I
want
to
be
mindful
of
the
time
zone.
Let's
go
to
the
next
slide.
A
We
can
come
back
if
we
need
to
the
last
thing
we'll
look
at
for
today
is
a
UI
color
palette.
So
a
lot
like
those
interactive
states
right.
This
is
something
that
needs
to
be
defined
in
order
to
have
a
successful
design
system
long
term.
Alright,
we
got
a
search
somewhere.
This
is
something
that
will
evolve
over
time
for
sure,
but
designing
that
first
component
allows
us
to
establish
a
lot
of
this
now,
which
is
pretty
cool.
A
So
a
consistent,
color
palette
throughout
Jenkins
will
help
create
more
consistent,
visual
affordances,
of
course,
and
this
will
improve
feature
discoverability
and,
of
course,
the
big
another
big
game
here
is
improvements
to
visual
accessibility.
So
all
these
color,
the
common
color
combinations
that
we'll
look
at
on
the
next
slide,
have
been
checked
for
visual
accessibility
in
line
with
I,
always
call
it
W
CAG
guidelines,
but
I
guess
WCAG
guidelines
and
let's
look
at
the
next
one,
real
quick.
A
So
that's
a
little
bit
more
in-depth.
Those
are
that's
the
palette
as
it
stands
today,
with
a
little
bit
of
logic
behind
all
of
these
color
combinations,
how
they
should
be
used,
and
as
I
mentioned
this
will
this
will
evolve.
You
know
this
is
not
set
in
stone
and
how
this
filters
out
to
people
who
are
creating,
who
are
creating
plugins
and
contributing
UI
is
something
that
we
will
still
solve,
hopefully
in
the
long
term
here
with
a
UI
toolkit.
A
C
It's
it's
terrifying
for
someone,
who's
never
done
UI
design
work
before.
Thank
you
very
much
Joe
for
showing
it
that
scares
the
daylights
out
of
me
to
see
all
my
sakes.
There
are
so
many
sophisticated
things
happening
here.
Thank
you,
I
I'm,
happy
that
have
somebody
who
actually
knows
how
to
think
about
these
things.
The.
A
A
You
know,
there's
obviously
a
lot
here,
just
as
there's
a
lot,
because
a
lot
more
that
goes
into
implementing
these
changes,
but
yeah
we're
definitely
trying
to
think
about
these
things
holistically,
and
that
means
sometimes
spending
a
little
more
time
to
solve
for
this
stuff
before
we
can
just
crank
out
more
designs.
But
these
pieces
help
us
get
to
that
point,
and
these
are
big
steps.
Even
though
there's
small
screens
do
you
have
any
other
thoughts
or
feedback
for
today's
call
on
the
stuff.