►
From YouTube: Jenkins UX SIG Meeting - Jan 08 2020
Description
Recording of the 3rd meeting of the Jenkins UX SIG. A demo of the new UI for the header bar with breadcrumbs took place and this was followed by subsequent discussion about how to move forward with the UI revamp.
A
A
A
B
A
A
That
case-
and
we
can
just
go
straight
ahead
to
point
free,
witches
and
updates
and
how
things
are
going
so
if
Felix
has
been
working
up
there
since
we
had
in
the
door,
but
it's
been
working
pretty
hard
on
getting
some
the
actual
UI
changes
into
the
products.
I
think
it'd
be
nice
if
he
could
give
a
little
update
on
progress
of
changes
he's
been
making.
What
he's
running
Joe
will
also
be
giving
a
bit
of
an
update
on
sort
of
intention
time
to
work
and
what's
coming
next,
so
rates
go
clinics.
D
You
see
my
screen
with
shell
Jenkins,
yes,
okay
great,
so
you
can
see
here
the
three
C's.
Basically,
this
is
our
current
development
version
of
the
new
Jenkins.
Everything
is
right
with
a
new
header
and
the
new
breadcrumbs
bar
so
yeah,
it's
mostly
reflected
on
the
updated
designs
and
then
please
document
that
yeah
we'll
talk
about
in
a
minute,
so
yeah.
B
D
D
Yeah
I,
think
they
activity,
monitor
books,
looks
good
vindication,
yeah.
Also,
the
search
menu
is
a
bit
more
modern
right
now,
yeah.
Well
I.
Are
we
talking
later
about
the
one
one
part
where
I
have
some
difficulties
where
the
breadcrumbs,
because
we
did
we
had
some
design
it
with
what
the
reference
will
be
separated
by
slashes
on
the
current
page,
but
we
have
a
different
color,
but
the
way
the
breadcrumbs
are
set
I'm
programmed
into
Jenkins
makes
it
really
difficult.
So
I
don't
know
what
to
do
about
that.
D
I
will
probably
talk
about
this
in
a
in
a
thread
on
the
Google
developers
group
so
yeah.
This
is
it.
If
you're
curious,
we
can.
You
can
see
how
it
behaved
some
on
mobile,
as
you
can
see,
on
tablet
screens
these
these
these
icons
remove
the
the
name
and
the
action
name
is
hidden
in
mobile.
It
hides
the
search
for
the
search
bar.
D
E
D
D
D
Know
maybe
we
can
well
I
was
going
to
talk
later
about
how
we
can
go
about
releasing
these
changes.
Maybe
we
can
talk
about
the
scene
after
inflation,
but
basically
well
what
I
want
to
mention?
Well,
what
I
think
about
what
you
said
is
that
I
suggest
we
go
with
it,
because
we
are
going
to
be
changing
more
stuff,
maybe
typography
or
maybe
maybe
everything,
and
then
we
can
update
all
the
other
sites
at
once,
once
we
have
updated
typography
color
scheme
or
everything
off.
E
D
E
D
E
Would
be
my
proposal
because
yeah
I
see
this
hitter
yeah
definitely
changes,
but
even
here
I
can
ask.
Why
do
we
have
for
Jenkins
text
and
dodging
this
text
on
the
left
of
angle,
which
looks
quite
strange,
I
understand
that
that's
how
a
break
embodied
current
work
and
that
it's
extensible
but
here's
a
common
user
yep
would
be
nice
to
understand
where
we
are
going
so.
B
Just
to
kind
of
respond
to
that
idea
of
creating
fullscreen
mock-ups
for
the
experience,
I
think
it
might
actually
do
more
damage
than
then
be
beneficial,
and
the
reason
for
that
is
because
it's
just
too
early
to
it
would
be
a
bit
presumptuous
to
try
and
design
all
of
these
different
elements
on
any
given
screen.
We're
going
out
at
this
really
cautiously
so
I
don't
I,
don't
it
would
be
the
right
move
to
and
incrementally
right
intentionally,
I,
don't
think
it'll
be
the
right
move
to
design
full
screens
and
send
them
out
for
approval.
B
I
think
this
call
and
our
select
channel
are
sort
of
the
forum
for
for
discussing
these
things
so,
rather
than
creating
those
additional
mocks
and
putting
them
out
there.
I
think
I.
Think
this.
This
call
and
like
I
said
slack,
are
where
we
should
talk
about
them
so
like
that
Jenkins
and
drinkin's
thing.
If
that
feels
weird,
that's
great
feedback,
and
let's
talk
about
that
and
slack
rather
than
creating
a
new
process.
B
E
Okay,
so
maybe
this
is
a
process
I'm
not
familiar
with
well,
basically
just
to
have
a
complete
proposal,
because
if
you
submit
this
change
for
the
header
yeah,
it's
fine,
we
can
vote
for
that.
But
yeah,
for
example,
I,
don't
understand
where
it's
going
and
if
you
expect
me
to
approve
it,
I
won't
approve
it
so
I'm
happy
to
be
able
to
voted
and
the
pull
request,
but
I
wouldn't
vote
for
that
in
the
current
state.
E
D
B
Sure
so
I'm
curious
to
learn
a
little
more
about
this
and
sort
of
what
what
would
get
you
there
like.
As
far
as
far
as
like
how
much
detail
do
you
actually
are
you
seeking,
because
I
don't
think
it
I,
don't
think
it
we
keep
providing
accurate
representation.
Yeah
I
could
make
fullscreen
mocks.
You
know
no
problem
there,
but
I.
Don't
think
that
they'll
necessarily
be
an
accurate
representation
of
what
we
could
achieve.
They
could
show.
Maybe
what
we
want
to
achieve,
but
they're
not
going
to
be
things,
are
gonna
change.
B
E
B
E
D
That's
something
we
I
wanted
to
touch
later,
which
is
how
long?
How
do
we
go
with
releasing
this
because
we
we
have
talked
before
about,
but
we
could
use
for
feature
flags
when
necessary?
So
maybe
with
that,
maybe
you
provide
you
do
well.
The
community
would
prefer
that
we
release
these
changes
instead
of
straight
to
core
behind
the
feature
flag
or
whatever,
so
that
the
users
can
double
all
of
the
new
UI.
E
A
I
mean
it's
some
kind
of
compromise
you
can
reach
because
I
mean
III
understand
what
he's
saying.
I
like
I
mean
I'm.
Also
I'll,
be
honest.
I
also,
don't
know
where
this
is
going
well
enough.
I
mean
I
like
what
I
see
so
far.
But
it's
you
know
it's
like
tip
stands
in
the
Jenkins
UI
I,
don't
think
it's
particularly
healthy
for
Jones
make
high
fidelity.
Mock-Ups
of
you
know,
90%
of
the
Jenkins
UI,
but
so
how
can
we
find
some
kind
of
middle
ground
where
we
have
a
better
idea
of
where
we're
going
with?
A
E
Here,
for
me,
it
would
be
nice
to
just
have
let's
say
three
pages.
One
is
front
page
from
Jenkins
is
maybe
some
jobs,
some
folders,
which
is
a
common
keys,
then
page
for
job
and
a
page
for
you.
So
these
are
three
main
pages
which
have
been
visited
by
Jenkins
users.
If
we
could
have
understanding
how
it
would
look
like
for
them,
I
would
be
totally
happy
I,
don't.
E
B
So
I
don't
think
that's
entirely
unreasonable
right.
It's
just
the
thing
to
remember
is
that
it
all
comes
with
a
huge
asterisk
mark,
which
is
to
say
that
the
design
will
change
from
whatever
I'm
providing
for
you,
but
I
think
that's
that's
fine
I
don't
want
to
commit
to
to
when
I
could
provide
that
for
the
sake
just
yet.
So
let
me
figure
that
out
and
I'll
post
an
update
in
slack
I
think
I
think
there's
a
middle
ground
to
achieve
there.
Let's,
let's
figure
it
out.
D
We
wanted
to
avoid
official
practice
as
much
as
possible
to
the
less
number
of
features
as
possible,
because
it
definitely
makes
everything
harder.
You
know
but
yeah,
maybe
if,
if
you
do
believe
that
if
they
are
necessary
for
this
first
step
sure,
but
what
I,
what
I
will
be
doing
is
probably
I.
Don't
have
enough
knowledge
of
the
Yankees
yeah
but
I've,
basically
to
say
this
big,
so
I'll
probably
requesting
some
pointers
from
the
community.
D
Maybe
to
how
do
you
hope
that
you
prefer
it
maybe,
as
may
be
enough,
for
example,
do
you
put
you
prefer
toggles,
a
toggle
switch
on
and
off
through
the
configuration
panel
at
runtime?
Do
you
want
to
set
it
up
startup
flags
when
running
the
binary
compile
time
flag?
You
know
there
are
several
options.
E
D
A
E
Also,
some
changes
could
be
actually
delivered
incrementally.
So,
for
example,
if
you
want
to
just
learn
the
basement,
if
occasion
bar
I
believe
it's
something
we
could
to
do
right
away,
because
it's
definitely
better
than
the
current
layout.
So
the
problems
start
with
color
changes
with
Stalin
changes,
because
there
is
a
lot
of
users
customizing
it
using
simple
theme
plug-in
and
if
we
just
break
the
rail
layout
to
add
a
new
header
without
your,
even
with
my
wishes
downstream.
So.
D
C
D
B
E
Maybe
I
wasn't
specific
enough,
so
this
top
panel
makes
you
change
basically
consists
of
a
number
of
controls,
but
what
companies
usually
change
is
the
logo
on
the
top
left
and
color
of
the
bar,
so
it's
pretty
common
to
replace
it.
So,
as
long
has
been
written
compatibility
there
and
maybe
who
can
feel
the
same,
the
rest
of
the
conveyance
that
can
be
modified.
So
if
you
want
to
modify
budget
trump
bar
I,
don't
see
any
issues
with
that.
If
you
want
to
modify
notifications
layout,
I
also
do
not
see
really
issues
there.
E
D
C
And
I'm
I'm
really
impressed
actually
by
the
the
way,
you've
improved
the
experience
for
the
user
on
narrow
screens,
the
collapsing
of
that
admin
user
and
that
logout,
that's
really
nice
boy,
I'd
like
to
have
that
sooner
rather
than
later.
That's
really
nice
and
I
don't
see
any
reason
for
a
feature
flag
for
that.
It's
not
a
commonly
customized
thing.
Nice
work,
no.
C
D
Look
into
that
over
there
definitely
now
Anthony
always
I
would
like
to
mention
one
thing
before
moving
on,
which
is
that
we
did
receive
some
feedback
from
the
community,
especially
thrown
you.
Listen
for
that,
for
example,
I'll
be
maybe
you'll
be
surprised
at
I
married
having
new,
modern
front
end
techniques
when,
by
the
time
I
create
a
PR,
for
example,
I'm,
using
a
new
way
to
adding
icons
which
will
enable
us
to
use
the
whole
suit
of
material
icons.
D
F
D
D
E
F
D
E
Wanting
to
keep
in
mind
regarding
the
icon
management,
this
just
caught
my
attention.
We
have
a
history
of
introducing
new
framework
for
icon
management.
You
can
take
a
look
at
icon,
shame,
library
and
by
ikenson
plugin,
so
yeah.
It's
not
not
the
engine
I
proposed,
but
we
already
have
mentioned
for
management
items
and
it
might
be
compatible
with
what
you
can
see.
They
don't.
D
D
D
D
D
Actually
incorporating
them
into
the
India,
they
will
be
featured
the
first
time
in
my
PR
and
yeah
I
took
some
Liberty
to
add
some
new
stuff
and
I
was
expecting
the
peers
to
have
those
discussions.
Something
I
can
buy
a
write
down
and
Robert
Chung
stuff.
If
the
community
doesn't
like
those
techniques
that
oh
yeah,
that,
oh
let's
please
can
you
please
point
me
to
those
to
the
destination
yeah.
B
So
we
get
a
couple
pretty
straightforward,
slides
here.
Our
last
meeting
due
to
the
holidays
was
just
around
a
month
ago,
so
there
are
a
lot
of
repeat
slides
in
this
deck
from
that
one
in
case
anyone
needs
to
meet
or
wants
to
go
back
to
check
them
out.
Naturally,
I
will
link
to
this
slide
deck
in
slack
after
the
call,
so
there's
some
housekeeping
stuff
that
we
don't
need
to
run
through
again,
I,
don't
think,
but
sort
of
what's
the
intent
behind
this
document.
B
What's
the
intent
behind
the
visual
refresh
evolving,
the
Jenkins
Grand
focus
on
visual
accessibility
and
long
term
wanting
to
work
toward
a
Jenkins
design
system.
So,
like
I
said,
we
don't
need
to
read
that
all
word-for-word.
We
can
take
a
look
at
some
mocks
here
and
because
we
had
that
update
from
Felix.
This
is
essentially
what
you've
already
seen.
B
There
might
be
slight
discrepancies
between
what
he's
working
on
and
what
I
have
in
these
mocks,
and
that's
because
since
Allah
days,
we've
already
been
kind
of
talking
back
and
forth
and
improving
things
on
his
end,
but
the
design
monsters
haven't
caught
up
to
yet
so
there
might
be
some
discrepancies,
but
essentially
we
can
run
through
the
updates
real
quickly.
So
this
is
sort
of
repeating,
but
functionality
will
remain
the
same
as
the
goal
and
we're
gonna
start
introducing
this
new
color
palette
and
modern
iconography.
B
We
wanted
to
start
with
the
header
bar
for
these
reasons
in
additional
details
on
the
screen.
I,
don't
think
we
need
to
run
through
all
of
it.
So
go
to
this
next.
One
changes
since
the
previous
meeting
stuff
that
you've
probably
observed
already
UI
palette
has
been
adjusted.
It's
actually
looks
pretty
different
from
from
the
previous
iteration.
You
might
have
noticed.
B
It's
got
greater
visual
contrast,
as
Felix
mentioned,
we've
committed
to
material
design,
icons
because
they're
easier
for
implementation,
and
they
also
just
have
their
since
we
have
their
recognizability
and
and
are
really
easy
to
understand
for
a
lot
of
people
as
they're.
Using
a
lot
of
different
products,
they're
very
accessible
for
for
third-party
developers,
for
anybody
who
wants
to
to
contribute
and
use
the
same
icon
set
so
material
icons,
and
that
was
also
directly
for
some
feedback
from
Elise.
Oh
thank
you
search
for
suggestions
have
that
new
treatment
improved
legibility.
B
Small
things
like
this,
so
we're
getting
very,
very
close
on
this
one
I
would
say,
and
also
Felix
mentioned
and
showed
their
own
screen,
which
is
a
lot
better
than
this
static
mock-up
having
design
considerations
and
some
graceful
degradation
for
smaller
screens.
As
I
mentioned,
like
these
marks,
aren't
actually
caught
up
to
what
he's
already
developed.
So
that
search
would
be
hidden,
for
example,
but
the
idea.
C
D
Look
the
same
in
all
browsers
right,
but
we
also
don't
want
to
be
limited
by
browser
from
so
simple.
We
don't
want
to
be
limited
by
CSS
properties
for
browsers,
not
having
CSS
properties
right
now
that
it
will
eventually
cut
an
example,
for
this
is
pretty
small
example.
Further
mid
technique
that
we
will
be
using
in
the
future
is
that
you'll
see
this
nice
diagonal
bar
on
the
Indies
logo,
for
example
yeah,
where
the
release
it's
a
husband,
Diana
Ronald
Porter
pride,
so
that
uses
that
strong,
the
only
sick
way
using
a
CSS
property.
C
D
Not
support,
it
is
just
a
normal
rectangular
box,
but
also
the
to
support
this
nice
visual
effect
and
this
nice
visual
property.
They
have
the
updated,
they
have
the
updated,
basically
styles
and
the
other
browsers
would
eventually
catch
up.
This
is
really
a
really
small
example,
and
maybe
not
this
example,
but
that's
something
we
will
I
want
to
make
it
a
point
that
this
is
something
that
we
will
probably
before
use,
doing,
which
is
making
sure
everything
looks
great
on
most
modern
browsers
and
the
others
will
work
and
eventually
they
will
get
up.
One.
E
D
B
Also-
and
the
final
thing
I
had
for
today
was
just
sort
of
to
give
an
idea
of
what
we're
gonna
be
thinking
about
next,
so
up
next
on
the
list
here,
as
we
finished,
the
header
bar
now
keep
in
mind.
I
take
this
out
before
we
actually
met
today,
of
course,
so
we
will
I
will
follow
up
in
slack
about
that
idea
of
providing
some
some
fullscreen
mock-ups
and
we'll
figure
out
where
to
meet
on
that
Oh
like
but
prior
to
that
bit
of
discussion.
B
Here's
what
is
on
the
docket
is
admin
monitor
warnings
as
a
type
of
component
and
of
course
they
will
go
and
go
ahead
and
inform
other
styles
throughout
the
interface
like
buttons
and
and
other
possibly
form
elements
and
things
like
that,
and
then
a
little
more
broad
jenkins,
typography
a
lot
more
broad
actually
so
feel
that
it
really
deserves
dedicated
consideration
great.
So
obviously,
there
are
huge
implications
with
something,
as
simply
stated
as
jenkins
typography,
and
I
don't
have
a
lot
of
my.
B
My
exact
thoughts
worked
out
on
that
just
yet,
but
in
the
next
segment,
I'd
like
to
share
some
ideas
and
more
specific
proposals
on
how
possibly
can
be
improved
to
to
improve
accessibility
and-
and
that,
of
course
goes
here
right
hand
in
hand
with
functionality.
But
these
are
two
things
we'll
talk
about
two
weeks
from
today
in
the
next
thing,
call
and
I
wanted
to
mention
them
in
case
you
want
to
talk
about
it's
like
leading
up
to
that
or
right
now
totally
fine.
Any
questions.
B
Font
choice,
of
course,
is
a
big
one.
Do
we
need
to
change
it?
Is
that
something
we
should
be
talking
about?
So
a
lot
of
question
marks
here
for
the
moment,
but
because
type
touches
so
much
of
the
experience.
This
is
something
I'm
like
Chris
to
think
about
very
soon.
So
we
talked
about
this
in
the
next
one,
more,
nothing
too
specific.
Yet
we're.
E
E
E
B
And
that's
it
for
now.
It's
quick
reminder
here
about
providing
feedback.
Obviously
we
have
our
slack
channel.
You
no
longer
have
to
email
me
be
found
inside
of
our
direct
link.
Thank
goodness.
So
just
click
on
that.
If
you
want
to
go
and
join
this,
if
anyone
here
isn't
already
in
there
I
think
we
all
are
comment
here.
Oh.
B
E
B
B
D
E
E
Know
one
question:
would
it
make
sense
to
start
tweaking
JIRA
tickets
and
maybe
create
an
epic
for
this
UI
changes,
because
if
you
want
have
an
incremental
approach,
having
an
ibeacon
or
whatever
in
Jenkins
judo
would
help
us
to
mean
what
would
be
the
pond.
So
even
if
something
it's
just
I
guess
at
the
moment
by
having
this
feast,
actually
it
could
help
this
discussion,
feel
them
and.
D
B
D
Bringing
this
out
I
think
it
can
be
better,
especially
if
their
community
has
a
reference
to
something
that
I
mean.
Isn't
this
also
just
crude
to
have
an
opaque
discussion
and
then
just
create
a
peer
right?
Maybe
so,
then,
for
our
community
people
who
are
not
following
the
seed.
So
maybe
it
can
also
be
a
good
idea
to
to
create
a
ticket
suffering
yeah,
wait
to
see
an
America
backlog
to
have
more
just
tasks
that
are
not
only
adding.
C
E
Will
be
helpful
and
could
also
help
to
facilitate
changes,
because
you
know
what
we
usually
recommend
is,
if
you
see
that
they
tick.
If
you
need
a
friendly
marketers,
so
that-
and
it's
likely
that
you
know
that
somebody
you're
working
on
that
I'm,
not
sure
whether
they
would
be
able
to
find
a
tickets
right
at
that
moment.
But
they
still
just
haven't
publicly
visible
and
traceable,
helps
us
to
get
more
attention
to
the
project.
So.
A
D
E
E
A
Yes,
so
I
mean
we
need
to
come
move
towards
having
effects
like
we've
been
fairly
ad
hoc
up
until
now,
I
think
we've
had
a
few
different
times,
but
I
mean
I.
Think
the
two
weekly
cadence
is
about
right.
Owsla,
Christmas
new
year
came
in
between.
Does
anybody
have
an
issue?
Is
it
being
at
this
time
or
should
we
make
it
earlier,
because
I
noticed
in
Jenkins
calendar?
There
is
another
meeting
right
now
the
pipeline
and
just
get
much
beyond
there.
A
G
A
G
A
A
A
G
A
B
E
Won't
take
much
time.
No.
Actually,
my
proposal
would
be
so
one
of
another
reasons
why
I
was
talking
about
mock-ups
for
the
entire
going,
maybe
it's
time
to
start
facilitating
in
the
community
and
creating
combos
for
the
Jenkins
exe.
So
once
something
presented
on
Jenkins,
IO
and
other
channels
to
highlight
these
activities
because
yeah
you
exists
on
the
top
of
our
list
in
terms
of
user
feedback.
So
if
you
just
show
that
there
are
some
things
happening
in
this
area,
we
can
forget
more
contributors.
We
could
attract
just
more
users
providing
feedback.
C
E
A
E
Whatever
is
interesting
to
users,
so
we
heard
someone
else
once
for
six
before,
but
usually
it's
in
the
manifesto
of
a
special
interest
group.
So
what
we
want
to
do
why
we
invite
people
how
to
provide
feedback,
how
to
contact
us
or
maybe
some
highlights
for
project
activities
so,
for
example,
poplar
drumstick.
We
start
from
Java
web
on
the
right
away
and
I
guess
we
have
never
offered
when
announced
that
this
special
interest
dog.
A
E
Seconds
so
just
the
biggest
open
source
conference
in
Europe,
okay,
listen
up!
Well,
it's
really
big!
It's
more
than
ten
thousand
people
coming.
It's
a
two-day
event
on
the
weekend
with
a
lot
of
things
going
on,
for
example,
Chinese
will
have
a
standard
there
and
there
was
a
seaweed
room
being
led
by
Olivia
Grenier
and
in
addition
to
that,
community
savanah
is
very
sneaking
around
Folsom,
because
a
lot
of
people
go
to
there
anyway
and
first
we
do.