►
From YouTube: Jenkins UX SIG Meeting - Feb 19 2020
Description
A number of topics around the new header bar and bread crumbs for the Jenkins UI revamp were reviewed.
Some members of the Jenkins security team (Wadeck Follonier and Daniel Beck) joined and discussed how feedback can be provided about the UI designs at an earlier stage in the development process.
A
So
agenda
for
today,
first
of
all
introduction
again
the
review
marion
within
the
topics
so,
first
of
all,
I'm
going
to
give
everyone
with
some
updates
got.
The
status
of
the
sig
is
what
we
did
this
past
two
weeks
and
then
we
I'm
going
to
talk
about
some
design
feedback
we
collected
when
working
in
the
header,
PR
and
the
emphatic
want
to
place
a
point
about
how
to
improve
support
group
for
non
sig
members.
Okay
into
slim,
participants,
I.
A
Please
past
52
weeks
we
move
together
thanks
to
whoever
create
of
the
channel
I
think
it
was
good
Rick.
So,
basically,
all
discussions
are
we.
We
are
going
to
start
discussing
all
the
matters
for
the
seeking
hitter.
We
have
a.
We
have
a
plate
of
the
also
the
documentation
page
engines
at
I/o,
and
we
try
to
notify
to
as
many
people
as
possible
in
as
many
channels
as
possible
that
we
change
the
discussion
forums
and
we
also
recently
well
the
header
and
reference
that
merch
will
not
merge.
A
And
what's
next
I
want
to
refresh
what
we
talked
in
previous
in
previous
six
meetings?
What
we
aim
in
changing
right
now,
as
our
next
steps
will
be
focused
on
changing,
mainly
typography,
the
typography
is
hierarchy
and
phones.
I
was
sorry,
but
I
prefer
hierarchy
and
the
typography
fonts.
Basically.
So
this
is
something
that
we
talked
in
a
past
sick
meeting,
this
design
deck
hey.
What
is
LinkedIn
here
is
limiting
the
Sigma
team
from
the
5th
of
February.
A
If
anybody
wants
take
a
look
at
it
also,
while
recovering
in
typography
I,
have
sent
an
email
to
the
j2,
the
leader
of
the
Chinese
localization
sick,
to
C&C
seek
input
for
for
fun
the
choices
that
don't
degrade:
user
experience
for
people
who
use
numbing,
non-latin
alphabets
as
their
main
other
main
language.
Basically,
so
this
was
it
for
this
past
two
weeks.
Basically,
no
active
development.
These
well
not
active
development
on
the
typography.
Just
research
is.
B
B
We're
good,
then
so
I
think
there's
maybe
something
one
thing:
I
just
thought
that
I
wasn't
honest,
that
I
think
we
are
seeing
the
executive
case
for
the
meaning
is
here.
That's
great.
You
reached
out
to
these
people
for
now
it
it
only
someone
in
private,
because
it's
not
in
targeting
of
our
ministries,
the
world
from
the
Chinese
community
and
I.
Think
we
clear
we
should
actually
CC
the
agent
Keens
to
explain
this.
Other
person
is
related
for
fun,
I.
Think.
C
B
C
C
D
Just
a
question
with
the
typography
you're
working
on
Felix:
do
you
have
already
some
plan
about?
Oh,
you
can
cover
every
case
in
the
ecosystem.
I
mean
the
true
typography,
the
current
one
and
the
new
one,
not
very
distant
one
from
each
other,
and
so,
if
there
is
some
specific
holes
in
some
pretty
annoying
core
things
like
that,
potentially
it
could
be
easy
to
miss
them.
Do
you
already
think
about
that
part?
Oh.
B
A
Now-
and
one
of
the
feel
to
do
is
based
on
our
discussions
on
previous
Sigma,
because
we
realized
base
in
one
of
the
things
is
update,
typography,
basically
updated
font.
What
are
we
going
with
a
more
modern
form
front?
Another
thing
is
establishing
a
hierarchy
using
CSS
classes
and
default
styling
for
the
tax,
a
hierarchy
that
makes
sense.
A
So
we
will
probably
be
looking
into
tackling
onto
the
typography
of
this
sidebar
I'm
working
on
this
on
this.
Basically,
so
that's
our
plan.
It's
eating
the
early
stages
of
research.
We
will
share
mock-ups.
We
will
share
everything
else
as
soon
as
we
happen
to
iterate
on
the
fit,
but
basically
this
answers.
Your
question:
would
you
like
for
the
verification
my.
D
Concern
is
more,
but
if
I'm
a
plug-in
developer,
if
I'm
using
a
specific
font,
that
is
exactly
the
same
one
as
the
core,
but
it
was
more
by
a
mistake
that
I
used
the
same
because
I
don't
know
exactly
all
CSS
is
working.
In
that
case
you
are
providing
the
new
style
for
the
core,
but
potentially
will
not
be
able
to
see
the
difference
between
my
font,
the
previous
one
and
the
font.
You
are
proposing.
A
B
D
Know
it's
more
about
if,
as
a
pretty
maintainer
I
was
just
overriding,
some
CSS
rules
by
mistake
or
by
a
lack
of
knowledge,
and
we
know,
though,
all
the
protein
are
not
equal
in
term
of
quality.
So
the
font
you
are
overriding
currently
is
the
same
as
the
one
in
the
car.
So
there
is
no
problem,
but
with
the
new
approach,
the
new
style,
the
new
font,
we
are
providing
that
previously
override
in
the
holes
adjust
to
new
walls,
and
so
it
take
precedence
potentially
so
it's
more
but
reckon
if
that
warning
innocence.
A
B
A
D
A
Way
takes
a
while:
okay,
if
there's
anything
else,
I
will
move
on
to
the
nest.
In
the
next
section
for
the
same
feedback,
there
are
pieces
of
feedback
we
collective
when
creating
on
the
thing
is
remember:
it
comes
PR,
so
I'm
going
to
scroll
past
all
of
this
everyone
this
more
for
the
benefit
of
new
people,
so.
A
Okay,
so
I've
been
monitored
warnings
there
was,
and
we
received
some
feedback
that
maybe
vatican
about
it-
that
mainly
that
these
new
design
for
the
working
monitors
does
not
pop
it's
not
in
your
face.
It
should
be
also
some.
We
also
there's
a
proposal
pieces
and
by
the
way
this
is
just
a
mock-up.
This
is
not
a
final
design.
A
Okay,
for
example,
of
having
this
shopping,
the
read
a
background
so,
for
example,
some
some
alternate
proposals
also
and
a
little
back
raise
a
good
point
that
realization
feels
weird
that,
for
example,
if
you
have
to
you,
would
read
monitors
to
instead
of
two
monitors.
So
that's
a
point.
That's
a
nice
point.
So
just.
A
C
A
A
A
We
will
collect
the
feedback
see
and
if,
if
needed,
we
will
revisit
it
and
once
we
work
on
the
warnings,
pop-up
product
or
my
separate
PR,
but
we
first
we
will
want
to
collect
the
feedback,
inform
ourselves
do
actual
access,
even
do
more
comprehensive
accessibility
testing
to
see
if
the
the
contrast
is
good
in
any
option.
So
basically
we
we
heard
this.
We
heard
this
feedback
and
we
will
look
at
it
any
product
to
elaborate
on
this
broad.
D
Just
one
point,
because
it
was
even
in
the
title
in
this
slide
deck.
The
most
important
thing
from
my
point
of
view
is
that
this
affirmation
about
the
admin
monitor
is
not
a
notification,
because
the
notification
Israeli
yeah,
you
receive
a
new
message
or
you
receive
something
that
is
not
already
important.
It's
interesting,
but
not
important
in
this
case,
is
the
admin
monitor.
We
listed
the
things
we
for
Daniel
back,
but
what
is
important
and
what
is
less
on
the
setup
that
we
had
for
the
test.
D
It
was
about
40
admin,
monitor
and
only
2
are
not
really
important.
All
the
other
robot
lack
of
performance,
lack
of
security,
lack
of
something
that
is
important,
and
so
for
me
this
UI
means
it's
just
a
notification.
If
you
don't
read
it,
it's
not
important,
but
actually
it
is
so
that's
my
main
concern
following
minimum
toe
in
general.
A
B
Kind
of
level
of
criticality
of
the
messages
that
are
being
sent
through
the
monitor,
animator
features
so
that
we
can
differentiate
and
maybe
make
it
read
only
if
the
question
is
high
or
something
you
know,
because
we
are
things
like
when
the
reverse
proxy
is
badly
set
up,
you
know
is
a
bad
thing,
but
is
not
maybe
walk
regret.
No
two
one
on
the
top
is
maybe
enough
for.
D
That
reason
we
have
something
in
our
backlog
in
the
security
team
to
split
the
warning
into
what
is
just
non
security
warnings
and
security
warnings,
because
for
some
companies,
if
you
have
at
least
one
security
issue,
you
cannot
use
it
in
production,
and
so
we
need
to
be
careful
about
this
kind
of
affirmation.
Just.
B
Kind
of
well
my
concern
or
my
request-
is
that
I
think
maybe
making
things
quickly
related
is
a
bit
unnecessary,
necessarily
to
constrain,
restricted,
I.
Think
maybe
we
want
to
introduce
something
like
you
know,
love
level
with
like
I'm
level
of
criticality,
and
then
people
were
using
a
Demeter's
define
the
criticality
of
the
message
that
are
being
messages
about
the
instance,
and
maybe
there
would
be
a
top
level
that
would
be
like
I,
don't
know
high,
Burnaby
or
something
or
or
security-related,
and
then
the
rest
would
be
yellow.
You
know
critical
high
medium.
A
B
A
A
Thank
you
so
yeah,
so
basically
what
I
said
we're
going
to
look
into
it.
We
are
going
to
inform,
inform
our
decisions
on
based
on
God
Aleksei
said.
But
of
course,
as
Jeremy
said,
this
is
your
space
refresh
and
rhythm,
so
we
are
going
to
not
expand
in
new
functionality,
especially
if
it's
security
related
okay.
A
Next,
in
the
next
clip
of
this,
we
did
received
worst
the
contextual
menu
drop-down.
It
has
been
mentioned
that
there
are
several
problems
going
on
with
it.
I'm
sure
everybody
knows
it's.
It's
use
across
the
whole
application
from
the
breadcrumbs
to
the
links
in
the
header
to
the
to
the
jobs
and
to
the
tables
it
has
several
provinces
is
the
discoverability
is
really
low.
You
need
to
hover
over
a
element.
It's
a
backward
user
feature.
Basically,
it's
difficult
to
click.
It's
only
16
pixels
wide.
A
If
there's
not
interact
with
a
elementadd
song,
when
you
hover
over
it
chances
are,
it
will
not
have
Hoeber
effects
or
focus
effects
on
the
element
it's
positioned
above
and
if
instrumentation
is
a
bit
difficult
to
evolve,
it
uses
some
rather
all
the
other
script.
No
saying
it's
rather
than
saying
it's
it's
it's
old
and
it's
and
with
it
whether
you
need
to
use
across
the
whole
application,
so
there
is
a
potential
to
break
lots
of
stuff.
So,
from
our
point
of
view,
is
we
acknowledge?
This
is
a
problem.
A
This
is
an
area
of
the
interface
that
definitely
there's
room
for
improvement,
but
we
don't
think
we
think
our
efforts
for
this
CSS
refreshed
are
better
look
elsewhere.
Basically,
there
are
far
more
important
things
from
layout
typography,
the
sidebar
tables
the
demand
our
attention.
So
we
know
this
is
an
issue.
B
A
C
B
To
give
it
a
try,
just
community,
actually
it's
an
opening,
so
you
know
I
mean
like
there's
kind
of
make
it
clear
so
that
people
don't
come
over
and
over
and
over
about
some
recurring
problem
and
there
you
go
I,
think
it's
and
we're
like.
Well,
we
actually
look
at
it.
We
know
it's
a
program
between
our
you
know.
Higher
more
important
thing,
that's
probably
into
the
cat
first
know
avoid
having
people
working
hours
of
the
meeting
is
to
actually
find
what
we
know
about
reduce
yeah.
G
A
G
A
A
C
A
A
A
D
Yes,
I'm
sure
it
was
the
discussion
we
initially
have
in
the
cloud-based
channel
directly,
but
for
the
openness
just
over
discuss
that
more
broadly,
so,
mainly
during
the
feedback
we
can
provide
in
the
PR.
It's
a
bit
difficult
for
a
community
member
to
come
and
to
provide
feedback
on
the
UI
directly,
the
new
design
that
is
proposed
because
it's
already
appear-
and
you
expect
the
people
to
be
present
in
the
submitting
to
discuss-
to
provide
feedback
to
improve
the
feedback
look
in
general.
D
But
it
seems
to
be
a
bit
difficult
for
every
community
member
to
be
involved
in
the
submitting.
In
addition
to
the
other
things
they
have
to
do
so.
Providing
the
feedback
in
the
PR
seems
to
be
the
most
straightforward
approach
for
the
people
outside
of
the
city,
but
it
seems
it
was
not
initially
expected,
especially
after
my
initial
feedback.
It
was
more
about
yeah.
We
need
to
discuss
in
the
sig
to
peek
inside
of
the
DPR,
but
in
that
case,
do
we
need
to
have
a
review
step
before
the
PR?
D
We
discussed
initially
thought
similar
to
Jaipur
things
like
that
to
proposed
the
design
in
the
community.
So,
outside
of
the
CG,
so
mainly
the
discussion
is
just
an
open
discussion.
What
could
be
improved
there
because
for
my
point
of
view,
as
an
external
member,
because
I
was
not
following
the
initial
meetings,
it's
a
bit
difficult
to
have
the
context,
because
it
was
not
really
explained
all
the
things
that
are
already
discussed
or
not
and
to
provide
feedback
to
have
something
usefully.
We
said
yeah.
C
I
guess
some
another
key
points:
I
mean
one
of
the
original
guiding
things
when
we
started
this
whole
process
was
that
we
wanted
to
avoid
design
by
committee,
so
we
didn't
want
to
have
the
whole
Jenkins
community,
saying
I,
don't
like
kara
I
done
like
that,
but
at
the
same
time
we
didn't
want
to
have
some
level
of
consultation
as
well,
which
is
why
we
set
up
the
Jenkins
yack
sick,
so
so
I
mean
I.
Think
I
grieved
the
approach
that
we
should
push
back
on,
giving
the
sign
feedback
in
the
PR.
C
C
Something
that
the
sick
meeting
really
is
the
place
to
review.
The
science,
however
made
we
could
also
poster
design
somewhere,
but
at
the
end
of
the
day
we
do
want
to
avoid
designed
by
committee,
where
everybody's
like
well
I,
think
this
thing's
a
little
bit
too
klinken
that
purple
is
a
little
bit
too
purple.
You
know
that's,
so
it's
a
difficult
balance
between
getting
some
reasonable
feedback,
and
you
know
not
having
a
thousand
people
clearing
a
pixel.
A
A
Us
too
long
to
deliver
even
small
UI
pieces,
something
we
can
do
is
maybe
whenever
we
we
are
about,
we
are
about
to
present
designs
on
the
cig
meeting.
Maybe
we
could
look
and
we
will.
We
will
explore
I.
What
I
would
suggest
is.
Maybe
we
can
look
into
venues
for
making
people
aware
that
new
designs
have
been
posted
and
they
erupt
for
this
passion
may
be
an
invitation
to
discussing
on
the
guitar
room,
but.
B
B
I
think
we
should
have
something
like
a
place:
oh
not
the
wiki,
but
either
using
more
Google,
Docs
or
some
central
place
for
people
twist
they'd
be
able
to
follow
from
far
away
or
something.
But
then
we
can
indeed
make
expect
everybody
to
be
a
three
up
to
date
and
then
be
able
to
well
long
people
to
vote
raise
concerns.
But
if
it's
really
related
because
less
per
year
too
late
and
then
will
be
released,
English
yeah
I
was
standing,
but
just
by
a
matter
of
opinion
or
feeling
yeah.
E
B
So
you
know
just
writing
a
link
or
something
some
kind
of
notes,
because
we
already
have
the
transcript
of
the
meanings
or
something
like
customary
or
what
I
just
I
could
do
a
dir
stupid,
sir
speeding,
there's
kind
of
a
boat
to
surface.
You
know,
amongst
of
nine
hundred
messages
request
and
under
ten
or
twenty
things
that
people
needs
to
know
about
what
what's
been
discussed
there.
You
might
be
good
for
people
like
that
egg
or
anyone
else
to
be
able
to.
D
G
G
Maybe
the
messages
are
deleted
yet
yeah,
that's
not
a
good
basis
for
to
enable
people
to
even
understand
the
change
in
the
first
place
and
I
want
to
also
going
to
make
it
very
clear
that
Roddick
and
I
don't
really
care
about
the
I
mean
design.
Is
everything
right
understand
that
but
I
think
what
Jeremy
described
is
more
like
you
know
which
shade
of
blue
or
red
or
what
pixel
distance
and
I
don't
think
badhak
or
I
really
care
about
that?
G
C
G
We'll
probably
design
mock-ups
or
something
before
it
was
implemented,
perhaps
share
goes
on.
Is
the
mailing
list
selective
or
are
we
entirely
on
getter
share
that
in
some
of
these
channels
that
are
accessible?
But
let's
just
say:
what's
something
that
people
just
stumble
over
if
they
are
on
the
death
list,
perhaps
war
and
III
admit
in
this
case
it
would
be,
might
have
been
difficult.
G
Try
to
identify
specific
stakeholders
for
changes
like,
for
example,
if
you
redesign
how
security
warnings
specifically
appear
in
Jenkins
I
would
expect
that
you
contact
body
or
me
as
stakeholders
in
this
area.
Now,
obviously
the
notification
area
or
the
monitors
are
more
generic
than
that.
So
perhaps
that
would
not
have
worked
in
this
case,
but
that
would
be
an
idea
in
the
future
when
it
concerns
something.
That's
security
related
that
you
invite
specific
additional
stakeholders
to
provide
feedback.
G
A
A
great
point
that
I
think
that's
a
great
idea.
We
will
definitely
look
into
doing
that.
I
think
you're,
absolutely
right.
Regarding
the
stakeholders,
we
will
look
into
that
and
into
practically
engaging
the
stakeholders
like
in
this
case
you
mentioned
and
yeah.
Let
me
say
that,
maybe
my
answer
to
you,
too,
you
can
look
at
the
competition
this
lag
and
then
this
Lux
was
a
bit
random.
Maybe
that
was
not
the
best
answer
and
it
apologized
for
that
mm.
A
C
That
would
be
nice
and
then
I
think
it's
least
I
mean
I.
Guess
what's
frustrating
everybody's
that
you
know.
Is
you
don't
want
to
get
the
feedback
by
the
time
they
are
doing
that
you
want
to
get
it
earlier.
So
of
course
it's
not
always
possible
to
get
all
the
feedback.
As
you
know,
you
can
probably
get
quite
a
lot.
B
B
To
be
able
to
work
from
the
project,
you
have
to
be
involved
more
I
just
thinking,
because
we
need
to
have
a
central
page
again,
just
stop
that
right
away
in
where
we
can
be
curate
like
you
reach,
even
if
we
kind
of
don't
have
it
anymore,
but
you
know
some
places
where
to
eat.
We
eat
afterwards
and
make
minard.
B
Market
that,
worse,
you
know
again
shared
lecture
last
seed
meeting,
but
I
fully
understand
again.
That's
not
already
could
afford
watching
the
one
to
just
yeah
I
think
we
should
trade.
The
next
immediate
and
easy
step.
Is
that
and
then
we
finished
a
write
on
one
missing
on
lecture
entry
points
or
for
outside
moisture
I
guess
we
can.
I
I
think
we
should
move
on
on
the
next
discussion
or
subject.
Are
we
going
to
run
out
of
time?
Actually
no.
A
B
D
D
A
It
really
depends
on
the
effort
it
takes.
You
know
because,
for
example,
for
all
those
things
can
be
okay,
but
for
the
typography
it
can
be
full
whole
week
of
development
effort
just
to
have
an
experimental
PR.
You
know
it
really
depends
on
the
component,
how
much
it
can
take,
but
also
I'm
sure
other
UI
elements
don't
have
full
seek
than
10
using
specific
finish
for
discussion
as
we
do
so
you
do
have
these
resource,
so
I
think
we
need
to
use
it.