►
From YouTube: Jenkins UX SIG Meeting - 18 March 2020
Description
Discussed planned changes for text links, the redesign of the footer and finally there was a long discussion about suitable issues for contributors during which Josh Soref requested support for getting a PR merged that would change the configuration screen from using HTML table elements to divs to make it more modern and mobile friendly.
B
B
C
B
D
B
D
Josh
sorry
I'm
trying
to
use
a
space
which
is
well-lit
unfortunately
well.
It
means
that
there's
a
Sun
somewhere
out
in
the
general
area
and
it
kind
of
washes
everything
out.
Can
you
hear
me
yeah
I,
currently
work
for
small
company
and
we
use
Jenkins
in
past
lives.
I've
worked
for
research
in
motion
and
Nokia,
and
before
that,
I
worked
well
up
through
Nokia's
work
on
this
all
project
for
various
companies.
So
I've
done
various
things
for
user
interfaces
at
Barry's
place.
D
A
E
A
Cool
and
then,
as
we
usually
do,
we
make
sure
none
missing
anybody
I
think
that's
everybody
might
be
new
to
the
somebody.
Stop
me
I'm
wrong
and,
as
we
usually
do,
we'll
just
kind
of
run
through
the
agenda
for
today
and
then
give
folks
a
chance
to
add
something
if
they
want
to
so.
A
couple
of
quick
updates
on
the
list
for
today
are.
This
is
very
simple.
Just
a
reminder
of
that
new
resource.
A
We'll
take
a
look
at
that
when
we
get
started,
we'll
take
a
look
at
a
second
or
not
a
second,
a
new
design
deck
this
week
with
text
links,
tiles
and
a
footer
design,
and
then
we
have
a
discussion
here
about
how
to
triage
them
some
open
source
tickets
as
well
that
Felix,
you
could
probably
speak
to
a
little
better
than
I.
Could
right
now?
F
A
B
A
So,
first
on
the
list
here
we've
got.
This
is
a
resource
that
was
requested
a
couple
meetings
back
essentially
for
our
folks
who
could
not
make
every
meeting,
and
you
know
we
have
one
of
these
every
other
week.
They
wanted
a
way
to
kind
of
be
able
to
scan
design
improvements
and
see
what's
going
on
without
having
to
attend
ever
meet
a
conflict
put
together
a
super
simple
webpage
here.
A
All
this
does
it's
again
very,
very
straightforward
is
gather
up
mocks
from
our
different
meetings,
fold
directly
out
of
our
slides
and
then
these
link
back
to
the
relevant
slide
from
from
our
slide
deck
from
that
meeting.
So
this
is
sort
of
just
a
board
to
collect
those
all
up
and
that's
useful
for
some
people.
So
just
a
reminder
that
that
is
there,
and
the
second
thing
we'll
dig
into
is
a
design
deck
for
this
week.
Actually,
I
already
have.
A
Cool,
so
it
always
kind
of
pet
peeves
me
when
people
don't
go
fullscreen,
because
it's
you
know
it's
right
there,
but
I'm
actually
gonna
break
my
rule
and
not
go
fullscreen
this
time.
Just
anyone,
let
me
know
if,
if
that's
not
big
enough
to
see
or
anything
like
that,
and
because
we
have
a
couple
of
people
on
the
call
today
who
aren't
normal
attendees
or
may
be
interested
in
the
initiative.
A
I'm
gonna
run
through
some
of
these
slides
that
are
usually
here
that
we
usually
skip
over
and
there's
not
a
new
person
attending
I'll
try
to
do
this
quickly.
So
so
what
is
this
right?
What
are
we
been
looking
at
here?
Of
course,
this
slide
deck
was
created
as
a
resource
for
the
Jenkins
UX
sig,
which
stands
for
a
special
interest
group.
A
We've
got
some
great
feedback.
We
were
in
slack
for
a
while
we
moved
over
together
so
that
the
conversation
is
more
public
and
it's
been
a
really
good
back-and-forth
for
the
past.
A
few
months
now,
I
won't
read
through
everything
here,
but
if
you'd
like
more
context
about
the
visual
refresh,
what
is
this
initiative?
How
does
it
relate
to
you?
The
Jenkins
brand?
Is
this
club
is
taking
over
Jenkins?
The
answer?
Definitely
not,
and
how
that
all
pans
out
is
is
here
and
this
slide
deck
and
every
other
resource.
A
One
more
thing
I'll
mention
here
is
this
last
tidbit
about
working
toward
a
Jenkins
design
system.
This
is
something
that
the
community
has
tried
to
do
in
the
past.
You
know
there
have
been.
There
have
been
previous
attempts
to
try
and
do
this.
It
doesn't
make
it
any
less
valuable
to
try
and
make
it
work.
Now
we're
coming
at
this
trying
to
involve
all
the
relevant
parties
and
make
sure
that
we're
designing
for
what
drinkin's
is
right.
It
needs
to
be
fundamentally
extensible.
It
needs
to
be
a
community.
First.
A
Jenkins
is
a
very
special
project,
and
so
we'd
like
to
do
this,
but
we'd
like
to
do
this
the
right
way
and
a
small
part
of
that
is
why
we're
here
talking
today
in
this
format,
so
we'll
jump
into
the
first
thing
here
and
I
feel
like
I'm
kind
of
broadcasting,
just
because
I
went
through
those
early
slides.
But
of
course
anyone
can
interrupt
me
any
time
and
we
could
talk
freely
throughout
the
call.
A
The
intended
outcome
is
to
establish
clear
that
was
clear,
interactive
States
for
defects
of
text,
links
throughout
Jenkins
and
improve
clarity
to
support
the
way
people
use
them
now,
but
also
make
them
more
intuitive
for
people
who
are
coming
to
Jenkins,
maybe
for
the
first
time
we're
relatively
new
some
additional
details
here
and
we'll
take
a
look
at
a
at
these
in
just
a
second.
Thus
far,
we've
identified
three
distinct
types
of
text,
links,
sidebar,
ephemeral,
content
links
and
standalone
links.
A
We'll
look
at
those
in
more
detail
in
just
a
sec
and
I
want
to
highlight
to
the
nature
of
this
meeting
is
never
to
say
we
have
designed
something
or
we
have
implemented
something,
and
it's
done
here's
what
we
did
it's
over
make
sure
this
meeting
is
we're
working
on
XYZ
and
we'd
love
your
feedback
on
it.
So
the
stuff
we
look
I
hear
you
know
it's
not
set
in
stone.
A
So
I
mentioned
links
are
everywhere
throughout
the
interface
right
now,
but
if
we
can
define
some
clear
Styles
in
the
end
and
help
people
over
the
long
term
associate
different
functionality
and
different
types
of
content
based
on
the
Styles
links
that
can
make
the
overall
experience
a
lot
more
intuitive,
even
though
it
doesn't
look
like
a
dramatic
shift.
Visually
color
treatments
are
based
on
the
Jenkins
color
palette,
which
we
looked
at
in
a
previous
meeting
and,
of
course,
just
like
any
other
component
right.
These
explosions
are
going
back
and
informing
the
evolution
of
that
palette.
A
So
a
tiny
example
being
a
visited
state
for
a
link,
this
violet
color
wasn't
her.
It
wasn't
previously
in
the
palette,
so
we're
going
back
and
adding
that
just
like
with
any
component
or
any
element
they
feed
off
of
each
other
and
and
make
the
system
stronger
over
the
long
term
and
just
yeah,
it's
just
like
I
was
saying
there.
As
with
most
other
elements,
these
will
help
inform
the
design
of
more
complex
components
moving
forward,
and
so
we
can
dig
into
those
three
categories
that
I
mentioned:
sidebar
text
links,
femural
content
and
standalone.
A
A
Yeah,
that's
a
great
point:
Josh.
We
can
link
together
on
the
agenda
for
sure
awesome.
How
are
you
doing
sweet?
So,
let's
talk
about
these.
The
sidebar
text
links
this
category
of
link.
Right
is
exclusively
inside
of
that
left
panel.
That
sidebar
we
don't
have
a
official
designation
for
different
people,
call
it
different
things,
but
it's
where
most
of
our
navigation
occurs
and
it's
where
of
course,
plugins
can
contribute
navigation
items
and
different
links
as
well.
So
the
treatment
for
those
links
is
very
much.
A
You
know
work
in
progress
on
the
design
side
right
now,
because
we're
also
currently
designing
my
panel.
So
these
will
change
quite
a
bit,
but
this
kind
of
gives
the
idea
that
we're
starting
to
think
about
what
would
be
necessary
for
links
in
that
panel
as
far
as
different
interactive
States.
Some
of
these
are
already
there
and
some
of
them,
maybe
haven't
been
considered.
Yet
it's
a
mixed
bag
throughout
the
interface.
But
this
is
something
we're.
Mindful
of
the
second
type
of
link
here
would
be
what
we're
just
calling
ephemeral
content
text
links.
A
So
these
are
links
to
content
where
it's
especially
useful
to
have
a
visited
state,
something
that
it
might
exist
in
a
long.
It's
all
a
list
of
links
say
different
different
builds
perhaps,
and
it's
especially
useful
to
go
and
see
which
ones
you've
clicked
back
into,
whereas
by
comparison
sidebar
text
links
for
top-level
navigation
items,
it's
not
useful
to
have
a
visited
state.
In
fact,
it
can
be
sort
of
a
detriment
to
the
experience,
especially
for
new
users,
to
have
that
for
something
that's
more
high-level.
A
C
A
C
Ahead,
if
I
made
all
right,
the
fumarole
category
is
well,
we
similarly
service
name
who
came
up
with
it,
mostly
thought
for
stuff,
like
jobs,
a
number
of
wheels.
You
have
first,
when
we
first
run
disease
hyperlinks
in
cloud.
We
some
people,
told
okay,
we
want
the
specifics
for
four
jobs.
We
want
to
see
when
a
job
was
visited
when
I
build
was
visited
when
an
artifact
was
unloaded.
So
that's
why
we
want
the
family
of
of
they're.
Our
family,
yeah
I
know
if
Emily's
in
good,
we
accepted
by
their
name.
C
A
F
D
Yeah,
that's
back
probably
around
five
slides
in
the
when
you
started
to
talk
about
the
sidebar,
you
can
get
away
yeah.
So
if
you
look
at
the
table
for
enabled
sidebar
text
link,
the
real
problem
with
the
sidebar
is
that
you
also
occasionally
have
things
are
just
pure
text
and
if
you
aren't
keeping
that
in
mind
when
designing
for
the
style
of
enabled
text
links,
then
you're
missing,
what's
actually
important
about
how
it's
different
from
something
it's
different
from
text.
So
that
needs
to
be
visible
and
in
conversation
with
text
links,
yeah.
A
I
totally
agree
and,
like
you
know,
I
mentioned
like
this
one.
These
are
gonna
evolve,
pretty
dramatically
right,
because
this
is
clearly
as
an
enabled
state,
not
a
finished
solution
right
this
doesn't
this
doesn't
look
like
text
like
a
link
at
all,
so
yeah
point
taken
and
that's
definitely
gonna
happen.
I'm.
D
D
G
B
C
And
maybe
it
doesn't
really
make
sense
in
my
waiting
for
stuff,
like
going
through
a
section
obligation
like
that,
but
people
several
people
do
indeed
mention
that
that
they
think
for
stuff.
They
want
to
see
whenever
they
went
in
to
appeal
they
what
the
C
word
yeah
whenever
they
could
see
the
log,
so
soft
locks
for
a
specific
field
so
is
for.
F
C
F
The
mean
seems
to
me
that
it's
very
weird
or
special
case
I
mean
because,
for
instance,
there's
the
latest
links
and
those
things
which
actually
is
pointing
to
something
different
over
time.
So
it's
an
application.
So
it's
that
the
websites
so
yeah
I
agree
with
Jeremy
I
would
actually
be
more
like,
which
should
an
ever
differentiate
links,
but
I
mean
I'm,
really
really
a
really
a
eager
to
read
and
hear
from
people
who
would
like
this
to
be
a
same
in
Jenkins.
You
know
or
keeping
a
thing.
H
C
B
F
A
C
C
F
A
It
yes,
I
mean
that's,
not
a
bad
idea.
I
think
we
need
to
do
a
little
more
asking
around
and
get
her
and
maybe
other
places
to
just
to
see
how
it
in
how
it's
a
part
of
different
people's
workflows,
right
I,
don't
think
that
it,
even
though
I
personally
don't
really
like
seeing
them
throughout
the
application
either.
A
You
know
if
they're,
if
they're
really
important
part
and
this
one's
actually
not
even
that
that's
far
a
stretch
of
the
imagination
right
like
it's,
it's
a
useful
thing,
maybe
not
the
most
pretty
thing,
but
it
can
be
pretty
useful.
So
that's
an
interesting
idea,
though,
but
this
may
be
only
in
certain
places
where
it's
actually
used.
You.
F
Know
really
accommodate
people
who
might
get
used
to
that
reading
that
local
place,
but
I
think
in
a
rack
like
in
the
instance
central
when
you
see
the
jobs,
when
you
see
the
burglar
notice,
the
cool
main
panel
or
something
I
mean
I,
mean
click
on
the
job.
Yeah
I've
already
clicked
on
that
job
I've
already
visited
it,
but
I
I,
don't
think
I've
ever
found
that
very
handy.
That's
why
people
do
using
GPS.
We
look
into
jobs,
and
this
makes
no
sense
to
be.
You
know:
purple
purple,
no
fair.
A
F
C
A
For
sure,
I
want
to
watch
the
time
too.
So
good
call.
This
is
a
very
straightforward,
so
I
don't
think
we'll
have
as
much
digging
to
what
we're
calling,
because
to
my
knowledge,
and
it
might
have
one
somewhere
in
documentation,
but
to
my
knowledge,
I
didn't
have
a
name
before
so
what
we're
calling
the
footer
inside
of
Jenkins
the
goal
here
to
delineate
between
current
content,
but
is
in
that
space
using
some
subtle
visual
improvements
and
then
to
introduce
a
little
bit
of
graceful
degradation
on
smaller
screen
sizes.
A
I
actually
wanted
to
come
with
a
specific
question
to
the
group
and
say:
I
want
to
get
different
people's
opinions
on
the
value
of
seeing
those
page
generation
details
at
the
bottom
there
say
you're
accessing
or
you
want
to
go
access
on
a
smaller
screen.
Is
that
something
that
you'd
be
and
as
they
one
have
any
strong
opinions
about
removing
that?
Is
it
something
that's
a
part
of
your
workflow
in
some
way,
I'd
love
more
insight.
There.
I
A
C
A
C
Thing
on
the
footer
I'm
going
I'm
going
to
ask
on
the
sick
chat,
maybe
on
the
developers
mailing
list,
because
there
are
a
few
things
that
looks
likely.
Insertion
points
for
JavaScript
on
the
footer
markup
and
now
I'm
going
to
ask
in
the
developer.
Training
is
probably
pride
able
to
see
if
somebody
is
actually
some
plugging
is
actually
using
it
because
yeah
in.
C
J
C
A
Ahead,
oh
that's
interesting,
and
then
this
we
actually
looked
at
in
the
last
meeting.
Talking
about
you
know
very
ambitious
goals
for
what
we'd
like
to
achieve,
and
so
I
put
this
back
in
the
slide
back
because
it
was
anticipating
might
have
some
people
who
weren't
here
last
time,
I
think
we're
at
least
at
least
incrementally
working
on
throughout
the
rest
of
this
month
and
next
month.
It's
you
know,
still
sort
of
to
be
determined
to
what
level
of
fidelity
these
will
exist.
A
But
throughout
the
past
few
meetings
we
have
seen
you
know
progress
on
each
of
each
of
these
things
in
some
small
way.
They
all
inform
one
about
one
another.
So
it's
really
not
a
very
linear
process
of
like
header/footer
buttons
typography.
You
know
we
talked
a
lot
about
typography
two
weeks
ago,
for
example,
and
that's
further
on
the
list
technically
so
anyway,
I
wanted
to
put
that
in
there,
but
I,
don't
think,
there's
more
to
take
into
for
the
moments
and
then
I
know
we
have
a
lot
more
topics.
A
C
So
these
are.
This
is
a
list
of
issues
that
I
failed
identified.
They
are
part
of
the
epic
four
on
the
Jenkins
on
the
OSS
issue,
tracker
for
for
the
this
project.
So
I
wanted
to
give
a
rundown
for
these
items,
so
maybe
we
can
check
them
just
do
a
quick
mention.
I
just
wanted
to
introduce
them
to
everybody,
to
see
if
everybody
so
a
yeah
just
to
make
everybody
aware
so
the
first
one
is,
but
the
pin
you
x1
on
the
screenshot.
C
H
H
C
I
mean
bootstrap
alert
if
you
just
want
copy,
and
basically
we
all-
we
already
have
cone
for
the
bootstrap.
We
already
have
the
bootstrap
added
code
within
Jenkins.
They
alert
alert,
opt
danger
all
those
classes
if
they
are
in
game
in
youngest.
If
not,
you
can
just
copy
and
paste
the
CSS
from
boots
up
and
it's
okay.
Yes,
go
ahead,
I'ma
just
assign
it
to
your
shirts
to
yourself
and
work
on
the
PR
and
yes,
I'm,
asking
the
sick
chat.
If
you
have
any
any
doubts
regarding
this
hang
or
whatever,
okay.
A
A
And
then
hey
Robin,
so
so
something
keep
in
mind
too.
You
know
Oh
everything's
kind
of
linked
on
the
resources
stock,
but
when
it
comes
to
like
a
little
individual
design,
decisions
and
stuff
like
that,
we've
got
a
pallet
we're
trying
to
make
this
whole
piece
of
long
term
rights
to
like
reach
out
to
me
and
let's,
let's
work,
the
other
on
that
yeah.
C
A
C
This
is
more
of
a
tool
thing
one.
This
is
something
that,
if
not,
if
not
a
buddy,
who
does
it
I
will
do
in
the
future.
So
basically
two
thing
enhancement
that
in
both
CSS,
so
that
we
can
automatically
are
the
vendor
prefixes
for
all
browsers.
So
we
don't
worry
about
when
do
in
developing
CSS.
We
don't
worry,
we're
all
worried
about
old,
browsers
too
much.
So
this
is
just
an
r1.
C
Can
you
yeah
not
a
really
important
one
renamed
route
read
cram,
so
flooding
Nunez
wants
to
work
on
this,
so
this
is
something
that
we
talked
about
back
in
January.
I.
Think
that
having
the
root
breadcrumbs
called
a
home
is
easier,
doesn't
feel
right.
Sorry,
coach,
Jenkins,
so
we
were
thinking
about
calling
it
home.
I
know
some
some
project.
Some
teams
want
to
customize
it
in
some
installations
to
say
a
different
name
in
the
in
the
root
in
the
breadcrumbs
root.
C
C
There
is
no
infrastructure
in
Jenkins
two
to
four
programs.
They
are
just
under
you
read
some
stapler
pass
some
daily.
They
are
generated.
There
are
no
utilities.
You
can
check
what
what
if
the
vellum
is
a
corresponds
to
the
current
page
if
the
variant
has
a
parent,
so
we
cannot
do
good
designs
for
mobile.
That's
also
one
of
the
problems
we
don't
have.
We
cannot
do
mobile
for
works
programs.
So
there's
a
purpose.
C
We
there's
a
discussion
there
about
improving
improvements
on
the
Java,
API
yeah
and
just
just
mention
that
maybe
home
is
not
okay,
maybe
main
I
really,
for
maybe
something
that
should
be
configured
also
so
so
yeah.
If
it
would
be
great,
if
somebody,
if
you
can
you
wanna,
take
a
look
at
discuss
with
Java
API,
whatever
yeah,
okay
next
item
so
yeah,
Josh
I
saw
that
you
reopen
this
great
PR
I
think
it
is
for
context.
C
We
want
to
work
in
the
forms
in
the
future
to
do
to
these
doodle
actual
designs,
working
the
inputs,
input,
Styles
label,
Styles
working
like
form,
accessibility.
All
of
that
stuff
right
now
is
impossible
because
of
they
are
and
the
way
that
the
engines
build.
The
form
is
using
tables,
so
yeah
VC
initiative
is
really
important.
At
least
the
infrastructure
may
be
just
having
the
infrastructure
of
being
able
to
use.
Deeps
may
be
looking,
I
it
is
allows
everybody
to
expand.
C
D
So
and
yeah
this
is
in
first
all.
I
start
working
on
this
over
a
year
ago.
So
I
don't
even
remember
what
I
ran
into
but
yeah.
I
was
probably
on
some
sort
of
mobile
streak
and
the
fact
that
jenkins
works
so
really
poorly,
whereas
probably
at
the
time
I
was
starting
to
play
with
either
Travis
or
one
of
the
various
other
competitors,
I'm,
basically
a
github
user,
and
that
means
that
I'm
randomly
contributing
to
random
projects
that
use
random
CIS
and
every
other
one
did
a
reasonable
job
of
scaling
to
mobile.
D
But
when
I
was
actually
interacting
with
my
company's
Jenkins,
my
phone,
it
was
unusable.
So
this
was
an
effort
to
I
think
this
was
an
effort
to
try
and
bite
off
the
easier
part,
because
there
are,
thankfully
not
so
many
ways
you
can
mess
up
the
Settings
thing.
There's
a
there's,
essentially
a
theoretical
toolbox
that
most
people
are
using
for
it
and
so
I
figured
well.
D
We
can
try
this
and
if
I
can
push
this
through,
then
I
can
go
after
the
bigger
things,
which
is
all
the
actual
UI
things,
although
if
I
get
this
merge
and
if
somebody
else
wants
to
take
it
forward
to
do
all
the
more
events
or
some
UI
things,
I'd
be
quite
happy
to
stick
a
victory
flag
and
move
on,
but
yeah.
The
the
general
idea
is
that
if
you
get
close
to
narrow
screens,
you
end
up
having
very
basically
a
vertical
form.
D
The
picture
at
the
bottom
of
the
screen
is
a
good
example.
Basically
you
have
a
title
and
then
an
object
and
the
title
on
an
object,
and
this
is
that's
mostly
how
mobile
things
work
again.
I
was
working
at
research
in
motion
before
that.
I
was
working
at
Nokia
and
actually
I
was
at
Nokia
when
Microsoft
effectively
blocked
the
Nokia
engineering
group.
So
we
were
starting
to
use
the
Windows
Phone
style,
and
that
was
very
much
the
style
of.
Basically,
you
just
had
control
and
thing,
and
it's
actually
a
very
usable
model
in
mobile.
D
It's
a
lot
harder
to
mess
up
than
the
models
of
letting
developers
try
and
pick
everything,
because
it's
fairly
forgiving
everyone's
just
sees
there's
a
thing
in
the
thing
and
just
like
okay,
like
obviously
there's
some
talks
to
this
and
there's
just
not
much
else
to
do
so
that
that's
basically
the
general
design
principle.
The
implementation
is
basically
convert
everything
from
tables
to
forms
or
sorry
from
cables
to
divs
dealing
with
a
lot
of
fallout
and
then
answer
questions
of,
for
instance,
where
do
I
put
the
question
marks?
D
D
There
were
a
fairly
strong
feedback
saying
that
if
your
screen
is
as
wide
as
the
screen
in
your
sharing
that
having
the
question
marks
on
the
far
right
of
the
screen
and
the
actual
label
on
for
a
lot
of
the
screen,
and
if
you
have
a
bunch
of
them
next
to
each
other,
it's
impossible
to
figure
out
which
one
is
talking
in
theory.
If
somebody
wants
to,
we
could
set
it
up
so
that
the
question
marks
on
mobile
do
one
thing
and
on
desk
or
do
you
want
thing
on
desktop
to
another
aisle?
D
You
not
opposed
that,
but
I'd
rather
land
the
feature
in
general
and
have
somebody
else
move
that
forward
again.
This
feature
has
taken
a
year
of
clock
time,
not
technically
a
year
of
engineering
time,
I've
done
it
in
bursts,
mostly
it's
spent
in
various
states
to
either
test
fails
or
merge,
fails,
but
yeah.
So
at
this
point,
I
believe
it's
still
in
the
test
field
and
I
don't
have
a
lot
of
patience
for
it.
Currently,
my
team
has
an
own
gdb
database,
which
is
corrupting
itself
periodically
roughly
weekly.
D
D
Now,
I'm
generally
credit,
if
everything
and
you'll
see
that
I'm
giving
feedback
on
everything
as
people
run
here
in
random
projects
about
everything
I
just
but
I,
don't
have
a
lot
of
time
and
again,
my
official
eye
has
I.t
I'm
gonna
have
a
database
that
I
expect
to
corrupt
itself
with
the
next
5
hours.
So
that's
an
overview.
C
Yeah
well
gonna
talk
for
the
test.
I
just
want
to
say
that
this
is
a
great
initiative.
I
think
it's
really
important.
This
is
a
problematic
because
it's
really,
this
is
really
sensitive
to
to
merge
conflicts.
Basically,
everywhere
everything
causes
a
merge
conflict
with
this.
We
are
what
I
would
think
it
would
help
us.
I
did
try
to
take
into
this
PR
really
to
understand
it,
so
something
that
I
didn't
even
really
get
the
P
picture
is
where
is
it
now?
So
what
what
are
the
limitations?
C
What
is
there
so
to
what
extent
is
done
to
see?
How
did
you
end
up
having
wrong
strategy
for
improving
the
plugins?
For
me,
my
mace
else
is
that
we
should
leverage
the
F
n
tree
or
whatever
new
F
n
3v,
to
get
a
helper
as
much
as
much
as
possible,
so
that
we
can
update
it
and
the
police
would
have
taped
updated
themselves,
but
yeah
I,
don't
know
exactly
where
this
is
at
the
moment.
C
G
G
D
About
it,
the
I
was
for
a
lot
of
the
things
that
I've
gotten
stuck
it's
because
I'm
essentially
looking
for
feedback.
Basically,
there
were
a
couple
paths
forward:
I
didn't
really
have
one
that
was
on
that
scene.
People
were
actually
actively
encouraging,
like
with
the
question
mark
people
really
sited
on
something.
So
it's
like
okay,
I
can
go
that
way
and
just
do
it,
but
for
which
way
to
go,
whether
one
or
the
other
there
just
wasn't
enough
anybody.
D
The
only
thing
that
actually
did
get
done
was
I.
Think
I
got
the
hetero
thing
fixed
so
that
it
will
be
able
to
work
once
we
switch,
and
so
that
cleared
somewhere,
I
think
in
like
September
and
I.
The
LCS
fits
for
him
also
cleared.
So
at
this
point,
that's
no
longer
a
stumbling
block,
but
I
haven't
actually
even
run
this
locally.
So
I
don't,
but
it
sounds
like
you
actually
try
using
it.
So
it
sounds
like
it's
not
totally
broken.
I
ran
it
yesterday,
yeah
the
right
somebody
saw
some
pictures
in
github
so
I'm.
J
D
Think
data
dog
might
have
been
one
of
them,
but
this
was
from
like
probably
nine
months
ago
and
maybe
like
it
one
of
the
AWS
plugins
and
so
I
mean
the
general
idea,
for
this
should
be
to
land
right
after
an
LTS
branches
out,
I
think
so
that
there's
the
most
amount
of
time
to
break
all
the
interesting
things
and
then
spend
time
fixing
them
because
there's
no
real
way
what
I
ran
to
is,
there's
really.
No.
D
J
A
B
B
D
Not
a
huge
amount
of
work.
In
most
cases,
it
is
literally
changing
the
word
table
to
the
word
div
and
the
word
TR
to
the
word
did
and
where
TD
the
word
div,
maybe
adding
some
classes
that
are
like
TD
or
similar.
So
it's
the
amount
of
effort
is
a
little
bit
higher
if
you
were
actually
doing
fancy
JavaScript
to
muck
around
with
things
so
the
the
fancier
plugins
were
making
some
extra
odd
copies
or
doing
some
really
odd
things
worth
it.
B
C
B
C
Something
that
so
my
thoughts
on
this
is
that
forms
are
a
problem.
Forms
are
not
being
unusable
in
Jenkins
and
there
is
no
rule.
There
are
no
good
primitives
in
Jenkins
to
allow
oh
Jenny
does
not
offer
developers
enough
for
them
to
have
a
good
four
options
when
dealing
with
with
with
forms
also,
but
for
me
forms
do
need
work,
and
this
is
a
necessary
step,
because,
right
now
it's
its
own
style
I
did
try
the
side
of
the
tables.
It's
just
not
possible,
so
I
think
we
should
maybe
try
to
go
ahead
with
this.
C
Maybe
in
the
future
we
can
try
to
support
you.
It's
not.
We
can
try
to
Herot
at
these
PR,
but
this
will
not
happen
within
the
next
month.
Probably
so,
because,
right
now
we
want
to
follow
our
roadmap,
but
we
will
keep
it
please
PR
open
and
we
do
keep
an
eye
on
this
PR.
If
there's
a
blocker,
we
will
not
be
consoled.
We
maybe
we
can
take
a
look
at
that.
Somebody
I'm
a
there's.
D
D
And
it'll
be
fine,
because
this
will
not
impact
them
and
in
fact,
if
they're
doing
something
that
complicated,
they
should
be
doing
that
in
the
first
place
and
actually
between.
Why
I
started
this
work
and
now
or
a
couple
months
ago,
somebody
actually
broke
something
out
of
config.
I
might
have
been
like.
D
Cloud
configuration.
Thank
you.
Yes,
so,
basically,
if
you're
doing
something
very
complicated,
kick
yourself
out
of
config,
you
don't
get
it
impacted
by
this,
and
you
get
more
time
and
we'll
visit
you
later
so
yeah
that
that's.
If
people
can't
deal
with
it,
then
yeah.
That's
the
other
way
out.
Yeah.
J
I'll,
try
to
take
a
look
at
this,
so
I
had
a
better
player
that
last
night
and
worked
with
everything
I
had
installed.
It
worked
fine,
it
was
just
the
issue
with
the
padding,
so
the
padding
on
the
help,
icons
in
the
formulas
that
were
too
close,
but
this
test
a
failures.
I
can
take
a
look
though
yeah.
D
Yeah
I'm
quite
happy
to
set
people
up
so
that
they
can
contribute
directly
into
my
rat
into
my
repository,
so
they
can
just
add
extra
commits
to
muck
with
the
padding's
and
styles.
I
mean
I
care
about
mobile
and
at
times
on,
a
pixel
pusher.
But
on
this
one
right
now
and
in
fact
on
some,
the
other
jegging
sig
lives
on
recently
I.
Don't
care
about
pixels
I!
Just
want
it.
Just
it's
proof
concept,
somebody
else
tuned
the
pixel
lines
or
whatever
they
want.
C
C
I
C
F
Worry
about
merging
wind
sesh,
you
know
it's,
it's
kind
of
a
downstream
thing.
We
merge
way
when
we
merge
and
it
lands
in
weeklies,
I.
Think
and
then
you
know
the
new
baseline
gets
picked,
we're
depending
on
the
various
feedback
we
got.
You
know
so
I,
don't
think
we
should
really
worry
about.
The
weeklies
are
designed
for
this.
So.
F
J
F
We
have
that
public
blog
entry
from
Kazuki
like
one
year
or
something
ago,
where
he's
been
kind
of
committed
to
weekly,
to
kind
of
try
to
accelerate
or
something
we
need
to
find
a
balance
between
breaking
Oprah
gears
and
keeping
Jenkins
relevant
on
the
side.
It's
hard,
but
yeah,
committing
to
make
plugins
that
are
being
released
like
seven
years
ago
is
obviously
maybe
an
endeavor.
We
shouldn't
spend
so
much
time
on
right,
so.
A
Thank
you
everyone
for
your
time
today
reminder
we
have
a
space
or
a
channel
I
guess
over
in
Gator,
and
if
anyone
needs
access
I
think
actually
it
should
be
publicly
linked
to
everyone
who
attended
today.
I'll
send
the
resources
dock
out
after
this
and
I.
Think
that's
it
for
this
room
and
we'll
see
you
all
weeks.