►
From YouTube: Jenkins UX SIG Meeting - 4 March 2020
Description
An overview of the planned work for the Jenkins UI overhaul for Q1 was discussed. A short slideware demo of the typography changes was given. There was a discussion about how to bring in more community contributors.
B
C
D
D
C
D
You
may
have
already
seen
those
in
in
the
ether
channel
and
then
Julie
is
going
to
raise
a
question
regarding
the
incompatibility
of
reading
changes
of
the
Incans
grid
system
with
the
good
sub
grid
system.
And
what
come
with?
What
can
be
done
to
address
that
issue?
And
then
we
will
end
up
talking
about
good
to
do
with
about
destruction
and
discussions
and
it
is
going
to
be
kill
so
participants
and
their
interests
I
think
only
in
greenness
of
a
new
person.
D
E
So
I'm
Roman
resale
I'm
part
of
training
team
at
cloudBees
as
US,
but
this
ser
and
the
guy
from
the
Canary
Islands
and
basically
last
year,
I
was
trying
to
spend
some
time
contributing
to
Jenkins
I
made
a
few
commits
to
Jenkins
core
and
published
a
few
blog
posts.
I
mean
previous
jobs.
I've
been
working
as
an
engineering
front-end
teams,
so
I
really
wanted
to
every
like
front-end
and
UX.
So
I
wanted
to
try
to
continue
to
what
you
guys
are
doing,
which
I
think
is
great.
Oh.
D
F
Absolutely
if
you
want
to
just
open
up
that
link
yeah,
so
it's
it's
a
very
straightforward
resource,
I,
actually,
unfortunately
miss
last
sick
meeting,
but
I
went
back
and
watch
the
recording
and
something
that
I
was
getting
from
the
conversation
was,
you
know
it
can
be
challenging
to,
because
it's
a
very
specific
time
and
we're
all
in
different
time
zones.
It
can
be
challenging
to
make
every
single
meeting,
which
is
totally
fair.
F
H
Yeah,
maybe
we'll
just
pink
oleg
on
that
one
or
something
providing
the
link.
I,
think
it's
great,
because
I
think
Oleg
was
at
least
one
person
requesting
you
know
having
an
ocular
I
mean
I'm,
not
saying
my
leg
didn't,
but
just
saying
that
I
do
remember,
Oleg
asking
for
it
like
and
more
like
global
overview.
Not
just
like
the
header
work.
F
There's
always
sort
of
a
balance
with
stuff
like
this
because
yeah
yes,
everything
sort
of
been
documented
up
until
now,
but
it
can
also
be
really
valuable
to
see
it
all
to
see
it
visually
in
one
place,
because
all
I
did
it
so
I
I
totally
get
that
you
know
at
the
same
time,
I
have
to
make
sure
that
we're
spending
time
working
on
this,
and
rather
not
not
getting
too
caught
up
in
the
process
of
documenting
it.
But
let's,
let's
use
this
moving
forward
and
totally
iterate
we'll
see
what
only
can.
H
F
A
F
H
F
D
F
Okay,
cool
so
just
for
a
bit
of
context
Roman,
so
this
link
to
the
slide
deck
will
be
available,
of
course,
on
the
resources
dock,
but
so
you
might
want
to
go
in
for
for
greater
context
about
what
this
thing
is
and
and
what
we're
trying
to
achieve
with
it.
The
first
few
slides
in
this
deck
and
every
deck
are
always
the
same,
and
they
they
might
be
good
reading
for
you,
but
yeah.
If
you
can
go
up
one
slide,
Felix.
F
F
So
this
is
the
new
content,
so
Felix
mentioned
that
we
wanted
to
know
that
we
had
to
find
sort
of
a
more
specific
strategy
and
goals
for
these
next
couple
of
months
for
exact
to
a
couple
sig
meetings
ago,
something
that
I
said
was
was
coming
up
next,
in
addition
to
typography,
was
designing
the
redesigning
the
admin
monitor
warnings.
Now
these
are
something
that
dude
that
does
need
to
be
redesigned.
F
However,
in
looking
at
the
timeline
and
sort
of
how
long
it
took
us
to
implement
to
design
and
implement
the
header
bar
and
we're
still
refining
this,
this
process
of
getting
feedback
from
everyone
and
and
implementing
all
of
these
designs,
so
you
know
it
takes
some
time
and
we
kind
of
did
a
little
bit
of
a
revaluation
to
see
how
we
can
have
the
maximum
impact
over
these
next
couple
of
months.
So
what
we
did
is
we
chose
some
selective
improvements
for
that
maximum
impact.
F
F
Well,
let's
just
say,
to
try
and
solve
something
that
leans
heavily
on
typography
without
thinking
about
type.
First
like
table
Styles,
for
example,
so
we're
focusing
on
base
Styles
here.
If
you
go
to
the
very
next
slide
and
here's
sort
of
a
visual
of
what
we'd
like
to
fix
over
the
next
couple
of
months.
So
we've
already,
of
course
got
the
hair
bar
with
breadcrumbs.
F
The
footer
is
very
straightforward.
Buttons
are
probably
not
quite
as
straightforward,
but
fairly
reasonably
fairly
reasonable
to
get
done
right
now,
there's
quite
a
bit
of
disparity
in
button
styles,
throughout
the
Jenkins
user
experience
so
I
like
to
consolidate
that
and
improve
those
across
the
board.
F
Felix
will
share
in
a
moment
we're
already
working
on
some
typography
improvements
and
then
a
big
one
is
that
nav
sidebar
on
the
left
side
of
the
interface
there
would
be
a
huge
win
and
then
also
sprucing
up
some
remaining
iconography.
This
is
what
we'd
like
to
achieve
over
the
course
of
March
and
April.
So
it's
fairly
ambitious
when
you
think
about
the
timeline
and
some
of
the
technical
constraints
that
we're
probably
going
to
run
up
against,
but
I
think
that's
a
good
thing,
and
this
is
what
we
would
like
to
get
done.
F
F
D
One
of
the
things
that
we
realized-
and
this
is
a
concern
that
Olek
shared
with
us-
is
that
we
we
were
too
small
and
too
slow
iterating
on
the
header
and
everything
and
we
going
to
be
more
agile.
We
want
to
deliver
faster.
We
want
to
to
basically
to
be
able
to
iterate
more
and
get
a
faster
velocity
right.
D
So
one
of
our
goals
for
dividing
the
work
like
this
was
to
try
to
find
work
that
can
be
done
in
parallel,
not
just
one
in
waterfall
model.
Well,
now,
big
header
changes
and
one
big
typography
changes.
Reading
big
size
changes
now,
for
example,
footer
patterns
can
be
done
in
parallel.
We
will
probably
have
sometimes
many
peer
mentor
peers.
We
will
also
probably
be
separating
within,
for
example,
we
will
not
probably
segment
this
hyper
at
once,
we'll
probably
try
to
iterate
on
it.
D
Try
to
get
smaller
changes
accepted
first
and
and
then
expand
on
those,
and
the
reason
for
that
is
I
think
it's
easier
to
promote
together
community
feedback
and
discussions.
Well
that,
if
you
were
framing
with
framing
the
discussions
within
a
bigger
picture,
I
think
it's
having
a
smaller
PR
consult
with
that.
So
that's
what
we
want
to
try
these
next
two
months
and
that's
something
what
I
am
going
to
go
over
it
again.
So
that's
short
for
plan
any
thoughts
on
this.
F
D
Okay,
yeah
everybody
will
be
able
to
see
this
later
there,
so
the
others,
one
of
the
well
the
state
of
the
current
buttons
and
why
we
want
to
tackle
them
yeah.
This
is
sweet
old
peppermint.
So
thank
you,
Joe
and
I'm
going
to
move
on
to
the
typography
changes
so
I'm
building
basing
on
what
we
just
talked
about
regarding
typography.
D
What
I
worked
in
these
past
two
weeks
is
basically
taking
a
look
at
the
way
the
typography
code
is
set
up.
Looking
on
how
we
can
change
it.
Looking
at
how
the
typography
behaves
in
Jenkins,
doing
some
market
research
so
to
speak,
see
what
other
similar
tools
use
a
typography
on
that
side
and
what
I
prepared
was
a
really
small
as
a
small,
pra,
sorry
PR
candidate
as
possible,
with
some
basic
typography
changes
that
will
enable
us
to
do
iterate
more
basically,
based
on
what
we
talked
at
last
last
sick
meeting.
D
We
want
to
have
typography
changes,
not
go
into
the
page
styles
of
Jenkins,
that
we
don't
need
to
update
each
parameter.
We
just
want
some
reasonable
default
setting
product
you,
but
if
you
do
raise
this
issue
before
the
last
meeting
so
yeah,
so
what
we
want
to
do
is
basically
Landry's
a
small
PR
first
and
then
try
to
see.
Maybe
we
can
work
in
the
hyperlinks.
Maybe
we
can
look
if
we
can
improve
the
typography
in
the
plugins
table.
Maybe
we
can
look,
but
first
we
want
to
have
these
base
typography
changes
on
so
there.
D
Okay,
so
identify
stakeholders.
This
is
something
that
we
also
raised
topic
that
also
came
up
in
submitting
that
maybe
we
can,
it
would
be
good
to
identify
stakeholders
for
each
UI
feature
or
each
you
a
domain,
for
example,
for
in
the
having
it'll
be
great
to
have
some
security
people
involved.
So
I
want
to
throw
the
question
out
there
is
this
anybody
feel
that
and
I
know
any
specific
stakeholders
fighter
for
typography.
D
Ideally,
I
would
like
to
to
gather
some
feedback
from
everybody
who
uses
from
different
screen
sizes,
different
zoom
levels
in
monitors
all
that
stuff,
even
especially
examples.
People
have
trouble
reading
certain
fonts
or
certain
stuff,
so
all
the
feedback,
but
we
appreciate
it.
So
if
somebody
wants
to
say
okay
I,
this
is
my
use
case.
This
is
what
I
feel
about
this
so
and
they
are
welcome.
D
Wait
a
second
please,
okay,
so,
first
of
all,
what
did
I
found
I
am.
What
I
found
is
that
the
Jenkins
UI
code
uses
different
levels
of
font
sizes
from
thirteen
from
twelve
ten
to
eleven
to
thirteen
to
fourteen
some
screens
uses
fifteen,
it
freely
verizon
lot,
but
it's
really
inconsistent
also,
and
it
responds
I
believe
it
they
found.
There
were
two
packed
yeah,
so
the
readability
was
not
the
best
one
in
some
screens
so
and
also
they
a
font.
D
So
this
is
regarding
font
sizes
right
also,
regarding
font,
the
types
even
used
for
the
youngest
project,
you
it
was
using
trovato
and
the
Roboto
font,
and
it
were
in
most
of
the
code
ways
it
was
using
Helvetica,
Arial
and
other
similar
phones
right
is
anybody
waiting
in
the
chat
system
is
somebody's
okay.
It's.
F
H
A
F
D
Look
at
the
chat
so
yeah,
so
move
to
I
am
to
pick
up.
Phones,
I'm
the
type
systems,
and
we
think
is
project-
is
using
some
rather
old
and
ugly.
Looking
defaults,
for
example,
on
Windows
and
Linux,
it's
using
Arial
font,
which
is
not
the
greatest-looking
one,
just
looking
wrong
so
so
this
is
what
I
found
out.
There
was
so
we
took
some
the
say
it.
We
took
some
decisions
and
this
is
basically
a
proposal,
so
the
first
part
of
our
proposal
is
move
towards
using
system
forms.
D
Historically,
people
used
to
our
custom
forms
for
and
for
soon
for
two
reasons
and
and
people
are
there's
a
custom
fonts
to
their
websites
because
either
because
the
default
forms
were
too
weak
or
they
want
this
specific
font
to
reflect
a
specific
design.
Sorry
not
weak
to
army.
So
lately
there
are
modern
operating
systems,
both
desktop
and
mobile.
You
offer
good
right
of
decently
decent
looking
funds.
D
Basically,
the
training
industries
is
system.
Phones
whenever
possible.
Right
and
I
did
examine
similar
tools
like
it
happen.
Well,
other
tools
and
everybody,
basically
everybody's
using
system
funds
and
there's
a
big
case
for
them.
Users
are
familiar
with
them;
it
does
not
look
off
with
the
operating
system
of
the
users.
They
also
save
clothes
time,
for
example,
on
a
Norma
Jenkins
page
and
the
Roberta
font
was
20%
of
the
server
traffic
generated
by
the
well.
What
using
of
the
fronton
bay
payload
was
the
fun
20%
right,
so
definitely
shelter
yeah.
So
there
are
drawbacks.
D
The
first
drawback
is
that
the
you
ice
can
be
the
sizing
of
some
elements
that
depend
on
the
font
can
be
everything
consistent
from
one
operating
system
to
another
and
then
the
well
yeah,
that's
basically
it
that's
the
biggest
rower
drawback,
but
I
think
yeah
I
think.
Basically,
this
is
the
current
trend
in
the
industry.
There
are
good
reasons
to
try.
This
and
I
will
show
you
how
it
looks
in
after
this
in
doing
OSX.
D
F
D
J
D
A
D
D
D
So
basically,
what
I
was
this
property
CPR
will
propose
unifying
all
the
font
sizes,
except
on
the
set
up
with
our
by
the
way,
but
to
fund
system
based
on
14,
pixel
font
size
and
then
for
a
smaller
part,
used,
12
pixels
and
for
bigger
parts
for
bigger
bits,
maybe
use
16
pixels
headings
yeah.
We
also
change
headings,
but
those.
F
D
For
the
headings
are
not
final
at
all
so
yeah,
these
changes.
What
eyes
you
are
about
to
see
on
a
proposal
you
can
change,
and
these
are
meant
of
the
first
step
on
notice,
an
end
goal:
okay,
so
basically
I'm
going
to
show
some
examples.
This
is
on
our
our
section,
my
laptop
on
my
macbook
pro.
This
is:
where
was
very
old
today,
all
the
landing
page
of
Jenkins,
with
the
all
typography
thing,
I
believe
it
was
held
at
11
News-
and
this
is
this-
is
with
a
new
font.
D
So
the
changes
from
here
to
here
you
can
see
the
disposition
of
the
dimensions
of
some
stuff
definitely
changes,
and
this
is
young
move
on
to
system.
The
different
monitor
resolution
on
a
full
HD
monitor.
As
you
can
see,
this
one
does
look
different.
It
does
look
mooring
line
with
the
native
operating
operating
system
in
the
system
font.
No,
no,
the
system
from
this
Segoe
UI,
it's
quite
good-looking.
Looking
for
my
taste,
yeah.
Okay,
this
is
the
job
screen
for.
H
F
H
D
Okay
and
yeah,
so
this
is
the
job
summary
screen
on
the
old
screen
so,
and
this
is
on
the
newest
X,
keep
in
mind
that
I
know
this.
There
is
more
white
space
under
the
header
and
pieces
because
the
header
having
dimensions,
change
and,
for
example,
I
like
the
permalinks
change.
It's
definitely
a
read
anything
in
this.
We
are
more
readable
there,
let's
factor
together,
yeah.
A
D
Please
notice
that
yeah
that
I
took
this
in
the
font
size
down
a
bit
from
15
pixels
to
12
pixels
on
the
side
panels,
because
I
know
we
we
have
had
problems
of
fitting
stuff
within
those
panels.
There
are
some
there's
lots
of
open
issues
of
all
the
time.
So
that's
why
I
proposed
in
this
that
size
we
can
always
revert
it.
Of
course.
Okay.
F
D
F
F
F
Excuse
me,
but
it's
also,
if
we
think
about
it's
a
it's
a
sort
of
an
opportunity
to
benefit
from
all
of
the
investigation
and
research
that
several
large
large
companies
have
done
to
see
what's
best
for
for
users
on
their
system
and
I.
Think
there's
a
lot
of
value
in
allowing
users
to
not
jump
into
a
different
approach
to
typography
and
different
fonts,
just
just
when
they're
in
Jenkins,
so
I
think.
Overall,
this
can
be
really
good
for
just
user
consistency
in
the
larger
Jenkins
experience
and
in
the
larger
cloudBees
experience
as
well.
D
Okay,
so
basically,
this
is
a
this
is
this
is
a
big
one.
I
know
this
is
what
this
one
is
going
to
raise
lots
of
discussions.
This
is
forum,
and
this
is
this-
was
the
old
screen,
the
older
type
system-
and
this
is
on
the
new
ones.
As
you
can
see,
there
is
more
political
spacing
within
the
elements
for
add,
for
me
at
least,
is
more
readable
that
maybe
some
people
will
have
a
problem
with
having
less
information
available
on
the
screen.
This
is
what
it
looks
like
in.
D
F
D
We
looking
in
anyone
again
more
vertical
breathing
room
and
there
has
to
be
to
not
be
annoying.
This
is
what
it
would
look
on.
The
plug-in
table
more
readable,
basically
so
yeah.
This
is
a.
This
was
just
a
some
iteration
of
the
typography.
This
is
something
that
I'm
going
to
probably
create
a
PR
within
this
week,
but
a
way
before
the
end
of
the
week
yeah.
We
would
appreciate
all
the
feedback
and
we
can
gather
on
this
one.
It's
not
meant
as
a
it's
meant
as
a
stepping
stone.
D
C
F
F
I
agree:
that's
that's
where
it
really
comes
into
play,
is
when
you're
curing
it
and
also
you
know,
over
over
the
periods
of
time
as
we
integrate
other
CSS
improvements.
This
will
these
improvements
will
compound
and
it
won't
just
you
know:
they'll
complement
the
other
things
that
were
that
we're
improving
so
overall
we'll
create
a
better
experience.
Yeah.
H
Think
it's
you
know,
I
see
it
that's
kind
of
a
foundational
change,
but
we
need
to
build
upon
you
know
and
it
would
be
more
visible
when
we
like
see
the
difference
between,
say.
You
know
the
weekly
from
four
weeks
ago
and
weekly
from
no,
we
eight
weeks
or
12
weeks
from
now.
You
know
in
the
future,
and
you
know
we
need
to
basically
lend
it
as
soon
as
possible
so
that
we
can,
you
know,
address
the
feedback.
How,
like
you
know
the
field,
so
we
you
know
we
got
address
every
single
plug
in
us.
H
That
would
between
weird
things.
So
it's
I
think
it's
very
interesting
and
we
need
to
as
kind
of
a
building
back
of
what
you're
talking
about
Felix
about
the
velocity
I
think
we
need
to
lend
it
and
move
to
the
next
item
and
see
you
know,
post
a
potential
followers.
We
won't
be
able
to
address
any
I
know,
but.
D
D
Because
there
are
some
risks,
for
example,
I
want
to
see
the
the
monospaced
font
look
smaller
or
setting
on
certain
components,
so
you
want
to
see,
depending
on
I,
will
use
one
technique
or
another
to
set
the
font
size
for
monospaced
fonts.
By
the
way,
I
want
to
try
to
see
with
actual
planets
which
planet
Earth
actually
to
change.
It
so
I
think
that's
what
would
be
good
having
the
actual
changes
up
there.
D
H
Is
this
is
what
we've
come
to
realize
in
software
world?
You
know
that
when
people
talk
about
betas
and
release
candidates,
somebody
cares
until
it's
actually
released
and
then
people
are
stopped
providing
feedback.
So
I
guess
we
should
actually
push
you
to
do
weekly
and
and
see
what
people
have
to
say.
You
know.
C
F
A
A
D
K
One
okay,
so
I
released
this
week.
A
new
version
of
the
Warnock's
plugin
and
one
thing
I
made
in
this
release
was
a
refactoring
of
all
the
UI
components
that
I'm
using
these
are
now
bundled
plugins.
So
everybody
else
can
use
this
plugins
as
well.
So
what
I'm
using
is
bootstrap
from
SM
and
some
additional
tools
and
one
thing
which
is
incompatible
with
the
current
Jenkins
is
bootstrap
for
I'm,
using
because
in
Jenkins
we
are
using
your
quite
old
version
of
bootstrap
from
2:14
it's
bootstrap,
3
and
currently
bootstrap
5
is
in
development.
K
So
I
think
you
know.
This
is
something
we
need
to
change,
because
most
of
the
modern
JavaScript
in
libraries
expect
some
recent
versions
of
bootstrap,
for
instance,
so
I'm
wanted
to
use
tables
and
some
would
strap
grids
and
these
seem
to
be
not
compatible
with
Jenkins
because
we
are
using
a
quite
old
grid,
and
this
grid
is,
as
you
see
on
this
image
here.
M
is
this
place
where
I'm
using
the
script?
This
is
the
grid
I'm
using,
and
this
is
a
official
good
strip
for
it.
K
But
in
Jenkins
we
are
using
an
old
version
and
yeah
I
discussed
it
already.
I
think
two
meetings
ago,
I'm
not
sure
if
it's
a
good
idea
to
use
this
grid
only
in
my
plugins
I
think
it
would
be
better
if
Jenkins
would
use
a
more
up-to-date
version
of
the
grid.
So
the
idea
is
that
I
prepare
a
pull
request
in
Jenkins
that
will
replace
the
old
Jenkins
grid
with
with
a
new
one
and
that
I'm
using
here
in
this
screenshot
and
yeah.
This
will
of
course,
break
some
plugins
I.
K
Think
so
one
thing
is
you
leave
the
old
grid
forever
and
the
problem
is
that
we
are
not
only
using
old
grid.
We
use
a
patched
version
of
that
grid
that
has
not
12
columns
as
the
default
that
I
have
24
columns.
So
my
plan
is
to
replace
that
grid
and
I
created
an
issue
for
that.
You
find
it
in
the
agenda
and
the
idea
is,
if
you
have
some
ideas
around
that
issue.
Please
comment
in
that
issue,
so
we
can
discuss
that
topic
before
I'm,
creating
a
pull
request.
I.
D
L
D
K
Prepped
in
github-
and
there
are
not
so
many
which
actually
use
columns,
because
actually
we
don't
have
much
plug-in
that
use
you
I
at
least
open
sourced
ones.
I,
don't
know
what
you
have
in
cloud
based,
but
I
think
it's
a
change
similar
to
your
changes
to
the
footer
or
header
yeah.
There
will
be
some
things
which
will
look
weird,
but
yeah
we
can
fix
it.
So
yeah
would
be
good
if
we
can
take
that
effort.
D
Okay,
so
what
I
would
suggest
to
D
is
a
maybe
we
can
if
we
can
get
a
properly
the
plan
is,
maybe
we
can
create
a
list
of
the
plan.
Is
credit
prioritized
I
used
use
so
just
to
see
they
put
impact
is
you
know
see
if
there
are
twenty
fifty
thousand
use,
plugins
versus
a
thousand
use
number
of
use?
You
know
so
yeah,
and
if
these
changes
we
included
people
who
do
our
job
with
our
proprietary
plugins,
of
course,.
H
Sorry,
if
you
said
it
early,
but
I
mean
yeah
if
we
move
to
from,
but
from
bootstrap
3
to
bootstrap
for
everywhere
we're
gonna,
we're
gonna
break
the
world
right,
we
break
some
layout.
Yes,
so
I
mean
like
is
this
I
mean
on
the
UI
development
ecosystem?
What's
the
kind
of
a
story
here
is
this
like?
Are
you
know?
Is
it
I?
The
committee
is
moving
away
from
our
mood.
You
know
other
communities
moving
away
from
bootstrap
3
and
you
know
upgrading
everybody's
going
to
boost
before
or
is
this
like
Python?
H
And
this
is
nobody-
cares
about
Python
3
west?
Now
it's
it's
a
case,
but
no,
it's
like
a
fork
and
people
keep
using
the
old
version
of
bootstrap
or
you
know,
I
mean
by
that
I
mean.
Should
we
also
kind
of
a
great
digital
ecosystem
to
bootstrap,
for
because
that's
the
way
to
go
for
it,
since
you
know
I
hope
kind.
K
Of
clear
yeah,
actually
in
Jenkins
we
don't
use
very
much
from
bootstrap,
it's
just
the
grid.
We
are
using
currently
all
right.
So
this
is
a
small
change,
I
think.
But
this
is
something
we
need
to
discuss
in
more
general
I
think
which
part
of
your
ia
libraries
we
will.
You
should
have
in
Jenkins.
So
currently
we
have
actually
nothing
now.
K
I
have
for
the
plugins,
some
more
libraries,
but
this
is
some
kind
of
architectural
thinking
we
need
to
do
for
Jenkins
what
should
be
part
of
Cora
and
whatnot
as
far
as
I
remember,
Jenkins
core
cannot
use
plugins
to
visualize
things.
So
if
we
want
to
use
bootstrap
for
in
core,
it
must
be
part
of
core
and
not
in
a
plugin.
D
Yeah
well
we're
covered
in
that
example,
and
yeah
I.
One
thing
is
definitely
Yankees
need
need
to
provide
several
needed
to
provide
agreed
because
that
plugins
integrate
all
your
element.
You
can
put
a
yoke
nada,
Worcester
car,
whatever
you
want,
and
you
can
use
that,
but
the
grid
is
definitely
a
problem
by
the
way
you
can
namespace
and
grading
is
utilities,
for
example,
instead
of
a
dot
the
a
Jenkins
car
or
whatever
you
want,
but
you
don't
need
a
grid
system
and
the
current
want
is
not
standard,
unknown
extensible.
D
Basically,
and
that's
the
it
conflicts
now
with
your
plugins
but
I'm
sure
it
would
conflict
with
other
otherwise
so
and
the
problem
at
this
is
probably
going
to
play
that
yeah,
it's
basically
things
will
look
off
and
it's
not
about
also
using
they
using
bootstrap
within
junkies.
In
my
opinion,
the
way
I
see
it
is
not
about
using
bootstrap
within
Jenkins
is
that
just
adding
bootstrap
will
break
everything
basically,
because
the
current
read
is
also
not
the
book
subtree
grid,
it's
the
change
for
it
right.
It's
really
good
I,
don't
know.
C
F
D
J
D
Something
I
wanted
to
propose:
I
am
proposal
II,
maybe
we
can
discuss
it
further
is
to
sandbox
their
plugin
views
because
I'm
not
something
that
I
actually
going
to
explore
more
within
the
Jenkins
ecosystem.
Is
that
you
it's
taller
and
problematic
loading
lots
of
JavaScript
lots
of
CSS
within
the
Jenkins
and
everything
will
clash
right,
but
if
you
can
sandbox
within
an
iframe
certain
complex
views,
you
can
do
whatever
they
want.
Whatever
you
want
there
right.
So
maybe
that's
an
approach.
We
don't
explore.
Maybe
it's
complex,
maybe
it's
not
what
it
may
be.
I
F
D
F
Just
a
small
small
item:
essentially,
we
had
some
pretty
valuable
conversations
when
this
cig
was
was
starting
to
ramp
up
over
in
the
slack
journal
before
we
switched
to
get
her,
we
didn't
want
to
lose
those
conversations
because
they
useful
for
reference
later
so
I
got
in
touch
with
the
the
admin
or
I
guess
the
owner
of
the
slack
organization
for
the
continuous
delivery
foundation.
He
was
the
only
person
with
the
rights
or
the
ability
to
go
in
there
and
actually
archive
properly
so
long
story.
F
Short
I
have
an
archived
file
of
all
of
our
conversations
from
that
time.
If
anyone
has
any
preferences
on
where
to
put
that,
I
could
certainly
put
it
on
the
resource
this
list
and
link
it
and
get
her.
You
know
it
probably
isn't
something
we're
going
to
need,
but
it
has
been
successfully
archived
and
we
can
refer
back
to
it
as
we
need
to.
K
D
H
Yeah
yeah
I
would
still
yeah
request
that
we
have
a
link
or
a
zip
file
stored
somewhere.
You
know
because
I
mean
I.
This
is
great,
that
we've
done
that
work.
For
now
still
people
can't
access
it
and
we'll
have
to
request
it,
and
you
can
be
explicit
that
already
requests.
That's
like
I,
don't
know.
There's
the
public
zippers
on
the
thing
posted
somewhere,
sure.
F
H
And
if
there
is
actually
not
another
point
to
raise
the
discussion
on
the
chat
with
Robin,
let
me
think
we
I
mean
I,
already
kind
of
raised
it
a
bit,
but
I
think
we
should
have
a
page,
a
landing
page
somewhere.
You
know
something
like
getting
solid,
UX
page
somewhere.
That's
like
the
always
up-to-date
information
about.
Maybe
that's
the
jinkies
I
owe
you
expect.
You
know
you
know
for
anyone
that
would
be
joining
us.
You
know
in
the
next
week's
a
month,
something
that
would
avoid
us
prevent
us
from
having
having
to
tell
people
yeah.
H
Everything
is
the
in
the
running
notes,
so
just
go
through
it
the
go
through
the
ten
pages
and
find
anything,
that's
valuable
and
please
figure
out
yourselves.
What's
what's
Stanga
and
what's
up
to
date,
what's
cedar
11th,
you
know
so
something
like
a
one
pager
or
something
you
know
with
like
up
to
depth,
links
or
something.
F
H
Yeah,
maybe
I
mean
I'm,
not
I'm,
not
strongly
be
feeling
about
where
it
should
be,
probably
living
where
slash
seek
page
six
/ux
page,
you
know
on
the
changes
that
website
would
make
sense,
but
I'm
not
requiring
it
really
just
saying
that
I
think
it
would
be
valuable
to
you
know
for
people
like
Roman
or
anybody
in
the
future.
Something
like
you
know
in
a
few
minutes.
If
you're
interested
you
can
I,
don't
know
like
a
half
page
or
a
page
wide
length,
you
could
figure
out.
H
You
know
what
he
is,
for
instance
the
mock-ups,
because
I
think
that's
the
thing
we
want
to
keep
up-to-date
somewhat
I,
don't
know,
maybe
the
link
to
the
you
know:
JIRA,
that's!
If
you
scroll
down,
you
will
find
the
Jenkins
epic
on
the
issues.
You
know
something
like
this.
That
would
actually
point
give
you
a
few
pointers
for
anybody
to
jump
into
it
and
start.
You
know
getting
involved.
Basically,
yeah.
E
I
would
say
things
I
would
would
like
to
have
and
now
I'm
made
getting
the
context,
but
things
I
would
like
to
have
us.
A
new
comer
would
be
relevant
to
your
tickets
and
some
of
them
points
that's
new,
be
friendly,
so
for
those
that
are
doing
first,
things
in
the
Jenkins
UI,
which
ones
are
like
easier
to
get
started
with.
Also
the
repo
which
I
guess
is
the
core
repo,
but
maybe
them
few
PRS.
E
F
So
we
do
have
have
this
web
page
with
sorry.
It
looks
like
it's
part
of
a
longer
link,
but
it's
just
that
last
one
I
just
put
in
the
comments
which
is
the
page
for
the
UX
or
the
user
experience
thing
it
sounds
like.
Maybe
we
can
achieve
this
by
just
adding
having
some
updating
the
resources
on
here.
Exactly
okay,.
H
There's
pre
some
imitations
in
the
study
generating
their
chat,
static,
generator
system,
still
yeah,
something
like
getting
started.
You
know
part
there
would
probably
making
a
lot
of
sense
and
I
mean
I
love.
What
just
sort
of
man
just
said.
If
we
can
file
some,
you
know
maybe
split
link
building
upon
what
you
just
you
know.
You
said
also
at
the
beginning,
or
at
least
a
few
minutes
earlier
feelings
about.
H
You
know
splitting
things
a
bit
more
or
trying
to
accelerate
I
think
we
would
actually
be
great
if
we
are
able
to
file
a
few
things
like
really
smaller
and
tag
does
newbie
friendly,
because
actually
people
would
be
actually
working
on
these
getting
started
contributing
and
that's
really
what
we
want
to
hear
you
want
people
involved,
provide
feedback
better,
so
potentially
people
to
actually
do
the
work
you
know
playing
with
the
software
country
with
Jenkins
overalls.
Oh
yeah
I
mean
it
could
be.
You
know
very
first,
your
Cinco
fears
your
circle
here.
E
A
D
Especially
if
people
want
to
talk
a
little
did
some
stuff
like
we
are
not
planning
on
doing,
but
in
definitely
needs
to
be
done.
For
example,
there's
house
close
be
are
by
just
sort
of
about
moving
the
configuration
pages
to
front
tables
to
dibs
it's
close
to
bigger
Cisco,
but
I
think
that's
absolutely
needed.
I
think
that's!
That's
a
huge
need.
A
A
H
Instance,
I
am
thinking
about
something
that
poori
would
be
actually
doable
by
a
lot
of
people
who
have
the
notice
cheese,
new
experiences.
We've
discussed
a
few
times
publicly
and
possibly
between
some
of
us.
You
know
on
the
bat,
for
instance,
yeah
admin
monitor
thing
that
shouldn't
really
poppy
cult
monitor.
But
it's
you
know
military's
on
your
thing
only
drink
it
admins
come
to
understand
at
some
point,
but
it's
like
an
alert.
H
Actually,
it's
like
a
not
official
notification
thing,
so
you
know
moving
it
to
the
right
and
make
it
bell
only
like
you
know,
get
Trello
a
lot
of
tools
to
to
make
it
also
because
we're
talking
about
system
forms
here,
but
you
know
moving
to
the
right
and
looking
like
the
others
about
like
here's,
the
notification
and
maybe
it's
if
it's
a
security
notification
actually
have
the
different
bell,
or
maybe
a
red
I.
Think
that
can
that's
one
I
think
Felix
at
some
point
said
that
it
was
not
maybe
a
big
one.
H
D
H
H
Yeah
might
be
something
we
want
to
discuss
a
bit
because
we
have
you
know
I,
don't
want
to
catch
up
with
temperatures
because,
but
you
know
indeed
I
mean
in
terms
of
UX.
Only
experts
in
Jenkins
I
can't
understand
why
the
hell
we
caught
that
monitor
it's,
it's
really
an
alert
or
a
notification.
You
know
and
I
think
an
issue
has
been
filed
recently
by
Jesse
on
differences,
tracker
about
removing
the
term
admin,
monitor
and
calling
it
alert
or
when
it's
come
up
with
a
term.
H
E
F
The
review
processes
you're
talking
about
like
opening
these
these
tickets
and
such
and
opening
the
process
a
bit
more.
Our
view
processes
to
be
really
critical
here
too,
because
one
thing
we
have
to
keep
in
mind
is
that
long
term
we're
trying
to
you
know:
we've
already
taken
some
steps,
we're
trying
to
create
a
sustainable
design
system
over
the
long
term
and
so
I'm
definitely
open
to
the
stuff
we're
talking
about.
H
Your
concern
show
this
is
valid
one
and
at
the
same
time
you
know
if
we
define
a
new
thing
to
system
whatever,
and
we
don't
kind
of
challenge
it
make
it
go
through.
Actually
like
someone
else
than
Felix
being
able
to
follow
it,
then
you
know
it's
actually
also
going
to
be
interesting
to
see
how
people
understand
the
design.
You
know
rules
system
we've
put
in
place
to
be
compliant
to
be
complying
with
it.
H
You
know
and
then
work
together
and
I
expect
with
the
group
of
people
here,
I
mean
team
is
reviewing
every
single
PR,
zonocorp
Olli
is
doing
a
lot
of
work.
I'm
I'm
not
too
concerned
that
you
know
we
will
be
able
to
request
a
review
from
Felix
from
gaming
who's.
Also
pretty
active
and
also
people
you
know
are
knowledgeable
about.
You
know
the
UI
so
under
to
concern
about
that.
F
G
Also
concerning
the
London
page
and
the
current
topic
about
the
newbie
friendly
tasks
and
things
like
that,
I
think
it
could
be
a
really
interesting
to
put
aside
what
was
decided
to
not
be
taken
as
a
priority
by
the
way
waxey
at
the
moment,
to
let
the
Fink
being
done
by
newbie
friendly.
Think
like
that,
to
be
sure
that
we
are
not
taking
the
things
from
the
workload
from
Felix
innocence.
G
If
we
want
to
provide
some
improvement
and
some
UI
and
things
like
that,
it's
especially
important
to
know
that
it's
something
that
is
independent
and
that
we
did
not
take
some
conflict
of
things
like
that
with
what
is
planned
by
the
league,
in
essence.
So,
for
example,
to
admin
when
Itoh
is
something
that
is
definitely
not
inside
the
current
scope
of
what
Felix
is
doing
so
to
let
the
people
know
that
they
can
take
the
tasks
we
thought
virtual.
Being
the
other
system
could
be
useful.
D
Yeah
or
maybe
even
some
tasks
we
will
handle
in
the
future,
but
people
assemble,
for
example,
if
somebody
wants
to
go
ahead
and
set
up
a
storybook
to
have
a
UI
library,
our
UI
component
library,
visible.
Please
be
my
guest,
it's
something!
That's
tough
work!
So
yeah.
We
appreciate
any
contributions.
They're
here.