►
From YouTube: Jenkins UX SIG Meeting 14 Sep 2022
Description
Jenkins user experience special interest group 14 Sep 2022.
03:45 - UX prototype - Jan Faracik
30:53 - Pipeline graph view latest fixes and improvements - Tim Jacomb
47:13 - Hacktoberfest and the Jenkins UX SIG - Patti McLetchie
1:00:40 - Open UX regressions - Daniel Beck
A
C
D
A
Okay
is
the
ordering
okay,
I
thought
security
reviews
relatively
quick
progress
check
and
then
focus
on
ux
improvements
and
we'll
try
to
give
ourselves
enough
time
at
the
end.
To
talk
to
the
other
topics,
daniel
is
that
okay,
in
terms
of
the
ordering
open,
ux
regressions,
will
be
later
in
the
session.
A
Right,
okay,
then,
so
this
this
section,
security
reviews
for
ux
pull
requests
is
mostly
about
asking
the
group
as
a
whole.
How
is
it
going
with
the
security
review
process?
Is
it
progressing?
Okay?
Are
there
any
concerns,
things
that
need
to
be
raised,
or
from
vatic
and
or
daniel?
Are
there
things
you
need
to
flag
to
the
rest
of
us
about
it?.
F
A
C
B
A
C
E
A
B
D
D
Well,
the
last
last
meeting
and
we've
kind
of
made
several
refinements
to
it
since
then,
so
I
just
thought
I'd
kind
of
walk,
walk
everyone
through
them
and
try
and
get
some
feedback
before
we
download
to
a
larger
audience,
and
it
comes
time.
So
hopefully
you
can
see
the
dashboard,
so
it
looks
looks
quite
similar
to
what
we
have
at
the
moment.
Kind
of
key
difference
here
is
that
the
the
navigation
bar
at
the
top
has
moved
to
the
left.
D
D
So
say,
for
example,
the
stage
view
appears
at
the
very
top
build
history.
Next
to
it
and
as
you
scroll
down,
you'll
have
more
information
about
your
the
project
that
you're
viewing,
for
example.
So
we've
got
the
test,
result,
trend
and
stages
and
kind
of
empty
blocks
at
the
moment,
just
to
fill
the
space,
but
we'll
film
number
four
devops
world
and
these
cards
are
interactive,
so
you
can
full
screen
them.
D
For
example,
and
that'll
show
you
more
information
about
that
block
people
build
and
kind
of
folds
a
very
similar
pattern
where
we,
instead
of
having
a
large
kind
of
sidebar,
we
said
display
that
information
all
at
once
on
the
page,
so
it's
kind
of
less
clicking.
Ideally
so
the
very
first
thing
you'll
see
is
this:
this
kind
of
large
console
pane
or
card,
and
it's
kind
of
one
less
clip
to
interact
with
it.
You
also
have
kind
of
quick
actions
such
as
the
copy
button
to
copy
the
log
or
down.
D
That's
the
kind
of
pattern
that
we
kind
of
develop
in
here
really
for
these
pages
is
this
kind
of
card
layout
that
can
kind
of
flow
to
different
screen
sizes.
So,
if
you're
on
a
mobile
it'll
fit
nicely
there,
if
you
want
an
ultra
wide
little
scale
to
that
too,
so
you'll
have
lots
of
lots
of
information.
D
So
it's
kind
of
taking
nutrition
from
blue
ocean
in
a
way,
so
you
might
have
kind
of
kind
of
what
you
call
them
kind
of
get
instances
and
they
can
provide
little
pieces
of
ui
that
can
plug
into
this
page.
So
if
I
want
to
connect
to
a
git
repo,
I
just
hit
github
and
I
can
turn
the
information
and
we
can
go
straight
from
there
rather
than
building
a
project
and
doing
it.
That
way,
hopefully
makes
the
kind
of
process
a
bit
smoother.
D
A
D
Sure
so,
for
me,
currently,
the
pages
of,
of
course
jenkins
that
they
kind
of
a
lot
of
the
stuff
in
the
pages
aren't
necessarily
related
to
one
another.
So
if
we
could
break
that
out
into
kind
kill
more
sections
if
possible,
and
that's
where
I
think
the
kind
of
sidebar
approach
would
be
better,
it's
easy
to
kind
of
flick
through
various
pages
rather
than
having
to
kind
of
go
back
to
this
main
settings,
hub
kind
of
call
it
that
just
to
join
for
another
section
but
yeah.
D
A
A
D
F
F
C
Just
wondering
some
sort
of
search
here
as
well,
which
kind
of
helps
solve
that
security
issue
as
well,
because
I
think
an
example
is
get
plug-in
recently
chain
added
some
feature
I
can't
remember
quite
about,
but
it
went
on
the
security
page,
which
was
a
bit
different
to
other
things,
and
so
so
it's
another
place
to
look
for.
But
you
could
search
find
all
git
configuration
by
searching
or
something
like
that.
B
A
Certainly,
on
okay
on
my
android
device,
I've
learned
now
by
hard
experience
that
when
I
want
to
do
settings
I
always
have
to
search
for
it
anyway.
Likewise
on
my
chromebook,
so
the
concept
here
might
be
add
a
search
facility
here
that
lets
me
search
for
all
of
the
settings
and
then
find
the
things
that
matched
him.
Is
that
what
you
were
saying.
A
Yeah
because
I
agree,
the
the
example
you
gave
from
the
git
plugin
is
a
is
a
very
recent
one.
It
it
intentionally
put
something
in
security
because
it
was
security
related,
but
all
the
other
configuration
things
for
the
git
plug-in
system-wide
are
in
the
system
configuration
page.
So
now
it's
in
two
places,
yeah
good.
F
C
I'm
not
sure
at
this
point
so
yarns
existing
search,
stuff
kind
of
integrates
with
more
components
like
users
builds
other
jobs
and
everything.
So
it's
a
I'm
sure
if
you've
seen
it
the
pop-out
one,
which
kind
of
splits
the
search
results
out
into
different
sections.
So
you
can
see
what
sort
of
thing
it
is.
C
So
that's
that's
something
that's
prototyped
at
some
point
and
did
start
exploring
the
search
for
the
design
library
as
well
kind
of
a
similar
sort
of
idea
to
this.
But
like
searching
all
the
design
library
components,
you
don't
have
to
try
and
find
what
you're
looking
for.
But
you
need
to
explore
that
a
bit
further.
E
A
A
A
And-
and
I
had
a
question
julie,
I
believe
I
think
uli
hoffner
was
with
us.
No,
maybe
he's
not.
Here
I
was
wondering
if
there
was
experience
for.
Oh,
you
are
okay
with
warnings.
Ng
are
there?
Are
there
experiences
you've
had
on
this
card
style
layout
that
that
might
inform
us
in
terms
of
hey?
What's
worked
well
and
what
hasn't
worked
well
in
terms
of
concepts
and
ideas.
A
D
A
D
C
D
A
G
G
And
we
started
with
pixels
as
yeah,
that's
width
and
height,
and
this
was
not
really
good,
so
I
think
it
would
be
much
better
if
we
have
a
layout
like
a
grid
of
12
by
12
or
what
else,
and
then
we
can
have
some
widgets,
which
are
only
small,
widgets
or
large
widgets.
Well,
this
would
really
awesome
for
plugins
to
contribute
to.
G
G
G
Be
really
helpful
if
I'm
not
sure
this
configure
button
is
maybe
it's
not
yet
programmed,
but
it
would
be
helpful
if
we
can
select
widgets
somehow.
So
it's
because
some
people
would
like
to
see
the
test
results.
Some
other
people's
would
like
to
be
the
stage
view
and
some
would
like
to
see
the
build
history,
but
nobody
is
interested
in
everything
I
think
so
because,
typically
in
a
team,
you
have
a
project
manager
who
is
more
interested
in
some
overviews
and
the
deep
developers
would
like
to
see
something
totally
different.
A
D
A
D
Yeah,
that's
the
kind
of
so
on
on
kind
of
current
jenkins.
You've
got
the
build
history
and
the
users
they
kind
of
sit
there
at
the
moment,
not
too
sure
how
useful
that
is.
I'm
kind
of
seeing
this
bar
is
a
good
place
to
have
kind
of
permanent
links
that
you
kind
of
frequently
want
to
access
or
links
that
kind
of
span
across
pages,
for
example.
So
it
depends
kind
of
what's
useful.
Home
or
dashboard
is
useful
search
kind
of
pops
over
the
kind
of
current
interface
and
settings.
E
Well,
a
question
about
this
ui:
what
parts
do
you
envision
to
be
extensible,
because
I
mean
this
looks
great
but
as
we
know,
for
example,
from
side
panels
of
jobs
and
builds,
the
challenge
is
to
make
it
work
once
every
plug-in
dumps
additional
links
everywhere,
because
obviously
every
vendor
things
their
own
plugin
deserves
a
spot
in
the
top
level
navigation.
That's
shown
on
every
page,
and
so
this
won't
be
just
seven
links
but
more
like
50,
and
how
well
does
it
work
then.
D
So
for
the
dashboard
I
was
kind
of
envisioning
this.
This
kind
of
sidebar
has
been
extensible
pretty
much
the
same
way
as
it
is
now.
Plugins
can
provide
their
own
cards
here.
For
example,
currently
kind
of
secondary
sidebar
links
would
appear
underneath
this
kind
of
overflow
button
kind
of
links
that
aren't
important
or
very
rarely
used,
for
example,.
D
A
D
E
E
I
similarly
on
this
page,
how
would
you
present
existing
prominent
project
actions,
which
is
what
graphs
and
such
are
currently
implemented
with
if
they
show
up
on
the
builds
main
page?
So
I
think
that
would
be
our
job's,
the
main
page.
So
I
think
that
would
be
interesting.
You
know
existing
extension
points
and
where
they
appear,
even
if
with
reduced
fidelity,
because
there's
some
backwards
compatibility
requirement
there
and
for
it
to
look
really
great
or
integrate
really
nicely,
for
example,
to
have
this
ex
full
screen
button
on
the
top
right
of
each
block.
E
They
need
to
use
a
new
api
so
that
I
think
that
would
be
very
interesting,
a
very
interesting,
very
important
because,
obviously
we're
not
starting
from
scratch
right.
We
have
2000
plugins.
We
need
to
take
along
on
this
and,
if
jenkins
looks
great,
if
you
have
zero
plugins
installed
and
there's
an
unusable
mess
as
soon
as
you
have
a
realistic
setup,
I
don't
think
that
would
benefit
anyone.
D
E
Don't
get
me
wrong,
it
looks
great,
so
I
like
the
bar
on
the
left,
for
example,
design,
wise
and
last
time
when
you
presented
this
build
view
already.
I
think
it
looks
nice,
but
I
worry
about
how
all
of
the
plugins
that
people
are
already
using
will
integrate
with
this
in
blue
ocean.
We
basically
didn't
even
attempt
it
and
that
didn't
go
well,
and
so
I
think,
with
a
ui
redesign
like
this,
we
need
to
have
a
plan
to
make
existing
functionalities
still
be
reasonably
accessible.
D
For
the
existing
kind
of
project,
page
kind
of
plug-in
integrations,
I
was
imagining
we
could
just
kind
of
wrap
them
in
a
kind
of
basic
card
at
the
moment.
So,
for
example,
the
test
results
could
be
a
car
charge
and
then
the
current
states,
you
could
be
a
card
and
that
can
just
say
be
placed
at
the
bottom,
for
example.
D
So
it's
not
that
backwards
compatibility
but
say
when
a
plugin
developer
kind
of
enhances
it
for
the
new
design.
It
might
get
a
more
prominent
position,
for
example,
it
might
get
access
to
the
new
kind
of
controls
and
so
on.
So
it
can
integrate
better.
Just
one
thing:
you
want
to
get
kind
of
get
rid
of
is
kind
of
this
idea
that
plugins
can
just
chuck
stuff
wherever
because
it
kind
of
gets
a
bit
on
bld
like.
E
B
A
B
A
D
D
B
C
Yep
so
I'll
share
some
of
the
enhancements
to
the
pipeline
graph
view.
Plugin,
that's
came
in
so
quite
a
few
people
would
have
seen
this
before
but
pipeline.
Graphic
plugin
was
a
kind
of
prototype
that
I
did
during
the
ui
ux
hackathon
last
haven't
really
had
much
time
to
work
on
it
over
the
last
year
since
the
hackathon
itself.
C
So
since
the
initial
release,
I
probably
haven't
represented
that
much
since
then,
but
it's
had
two
new
features
since
then
one
was
the
job
view
and
one
was
a
pipeline
logs
view
as
well.
Those
are
all
in
kind
of
semi-broken
state.
There
were
some
issues
and
the
blue
ocean
graph
wasn't
accurately
represented,
as
it
was
in
the
pipeline
graph
view.
Some
things
just
didn't
work
right
from
my
prototype,
but
over
the
last
week
we've
had
a
contributor
come
along
and
fix
all
of
those
issues.
C
Basically
all
the
graph
related
issues
so
currently
have
currently
have
no
open
issues
with
any
reproduction
issues
from
blue
ocean
to
the
graph
and
there's
also
some
pipelines
that
can
be
represented
in
the
graph
that
couldn't
that
blue
ocean
wasn't
able
to
handle
the
only
the
only
open
issue
related
to
the
graph
is
now
the
parallel
pipeline
visualization
support,
which
was
the
most
upvoted
issue
on
blue
ocean
and
was
never
solved
so
then
that's
the
only
visualization
issue
still
are
open.
So
let's
show
you
some
of
the
enhancements.
C
So
there's
a
recent
one,
so
issue
that
was
fixed
yesterday
was
let's
go
here,
show
a
simple
one:
it's
taken
a
deviation
from
blue
ocean
where
declarative
is
now
showing
its
synthetic
stages
previously
and
declarative
they
sh.
It
was
shoehorned
into
the
previous
stage.
So
there's
a
synthetic
stage,
integrative
scm
when
a
when
it
does
the
global
checkout
for
the
for
the
whole
agent
that
was
just
randomly
put
in
the
first
stage
and
same
with
post
action.
C
So
if
you
did
a
post
actions
across
the
whole
pipeline
that
was
put
into
the
last
stage
randomly,
but
that
was
found
a
bit
confusing,
and
so
we've
just
put
that
in
here
just
to
see
how
it
works
the
benefit.
Is
you
get
a
actual
stage
up
here
at
the
top,
and
you
can
see
the
checkout
in
case?
That's
ever
useful.
C
C
So
that's
all
working,
I
just
haven't
created
a
pr
for
it,
yet
just
to
show
you
one
where
it's
failing.
I
think
this
one
here.
So
this
is
a.
This
is
a
build
from
the
slack
pug
plugins
master,
build
which
running
on
my
local
machine.
So
some
things
aren't
quite
there.
So
this
is
the
visualization
as
in
blue
ocean.
It's
all
accurate.
C
If
I
go
here,
you
get
so
that
the
parallel
branch
failed.
That
was
the
linux.
Eight
branch
failed
in
the
build
stage.
Nested
stages
don't
work
properly,
so
this
in
theory
should
be
nested
under
another
level,
but
that
doesn't
quite
work
in
the
log
and
if
you
go
down
here,
you'll
see
that
it
was
the
step
here
that
failed
and
you
click
on
it.
You
can
see
the
logs,
and
this
is
one
of
those
jenkins
systems
where
it
failed
for
a
agent
connection
issue
which
never
appeared
in
the
blue
ocean
log
either.
C
So
if
I
were
to
go
to
the
playing
console,
log
you'd
see
that
it's
got
a
stack
trace
with
no
such
method
error.
That's
what
it
failed
with
and
the
same
with
blue.
So
blue
ocean
wouldn't
display
that
either
the
same
sort
of
error
because
be
using
similar
apis,
I
guess
but
yeah.
So
that's
the
stuff!
That's
kind
of
most
of
this
is
real,
and
so
the
other
thing
is
that
it
used
to
be
for
those
who've
seen
this
before
say
on
ci
jenkins
io.
C
C
Pipeline
graph,
so
so
so
yeah
this
should
all
be
fixed,
visualizing,
so
yeah,
so
they
haven't
updated
it
here.
But
you
see
that
there
used
to
be
a
couple
of
ux
issues
here.
One
the
step
would
overflow
into
the
pipeline
log
area,
and
the
other
issue
is
that
you
can't
really
tell
the
difference
between
steps
as
they're
pretty
much
the
same.
There's
no
real,
clear
separation.
C
E
E
C
C
It
was
moved
all
this
far
away
over
to
the
right.
So
now
it's
moved
to
a
much
better
location,
which
yeah
makes
it
all
work
quite
a
lot
better,
so
something
I'm
working
on
which
isn't
released
here
is
kind
of
pulling
in
some
of
the
concepts
from
the
prototype
that
was
shown
earlier.
So,
if
you
see
here,
this
is
using
the
card
design,
so
it's
pulled
in
a
the
build
display
name,
hopefully
pull
in
the
for
pull
request,
hopefully
pull
in
a
pull
request.
C
B
C
A
C
A
A
B
A
C
C
Well,
I
hadn't
tried
on
any
long
ones
but
yeah,
so
that
and
it
would
it
would
have
like
yarns.
That's
if
you
remember
the
full
screen
sort
of
click,
so
you
could.
You
could
add
that
and
then
expand
it
out
fully
but
yeah.
So
this
is
something
that
I'm
just
working
on
at
the
moment.
I'm
not
sure,
and
it's
yeah
it's.
So
this
isn't
a
react
app,
so
I'm
not
sure
how
extensible
or
whatnot,
but
it's
kind
of
just
a
prototype.
C
I'm
working
on
it,
probably
just
to
sit
in
this
plug-in
for
now
and
then
look
at
how
we
can
pull
things
in
better
in
a
more
extensible
way
and
kind
of
just
as
a
early
look
before
before
bringing
this
into
the
main
jenkins.
It's
kind
of
a
good
place
that
we
can
experiment
with
some
of
the
sun
and
a
plug-in.
A
No,
no,
you
had
mentioned
something
earlier,
that's
you,
you
got
me
all
wound
up
and
happy
about
build
374.
That
was
on
the
page.
There
you
mentioned
that
might
someday,
be
the
description
of
the
pull
request
so
that,
instead
of
trying
to
remember
what
pr9
means,
it
would
tell
me
hey
this
is
this
is
what
pull
request.
Nine's
description
was
so.
C
A
A
C
B
B
C
Yeah
file,
an
issue
with
just
with
a
simple
pipeline:
if
you
see
recent
one,
basically,
just
don't
don't
use
an
agent
just
basically
just
put
your
stages
in
and
put
echoes
to
identify
what
stage
they
are
or
whatever.
So,
if
you
see
my
ones
here,
they're
all
so
it'll
be
something
like
agent
in
your
agent.
None
mostly
agent,
none
and
then
using
echo,
not
shell,
because
you
don't
need
an
agent
just
so
they
run
super
quick,
because
it's
just
about
visualization
and
a
lot
of
these
go
into
the
unit
tests
as
well.
C
So
they
unit
tests
will
show
the
visualization
make
sure
the
visualization
doesn't
regress
when
changes
are
made
so
yeah
in
any
thing,
we're
interested
in
yeah,
anything
that
doesn't
match
promotion
currently,
unless
there's
been
decided
to
deviate.
So
with
these
synthetic
stages
have
been
pulled
up
and
they've
been
marked
as
italics,
just
to
kind
of
highlight
that
they're
a
little
bit
different
they're,
not
you
don't
have
any
control
over
what
they're
named
or
anything
they.
C
A
C
That,
due
to
a
global
checkout,
you'll
get
a
stage
here
which
says:
declarative,
checkout
sem
and
basically
it
strips
that,
and
this
implementation
same
with
post
actions.
It
strips
that
and
the
reason
for
it
one
was
it's
not
helpful
and
two
was
it:
the
label
just
cut
off
because
you're
only
allowed
like
10
characters
or
whatever
before
you're
outside
here,
and
you
get
the
dots
the
same
as
blue
ocean.
C
C
B
C
A
A
H
H
So
I'm
helping
with
some
of
the
organization
stuff
that
is
happening
with
oktoberfest
for
us,
and
I
was
hoping
that
maybe
there
would
be
some
good
issues
that
we
could
maybe
get
from
the
group
just
to
say
I
I've
heard
that
maybe
it's
not
the
best
place
to
be
a
first
time
contributor
to
jenkins.
So
of
course
I
will
take
your
your
feedback
with
me,
but
I
was
just
curious.
A
So
so
part
of
me
wondered
that
most
of
the
ui
things
for
me
are
are
beyond
a
first-time
contributor,
but
with
uli.
Here
I
wonder,
maybe
there
are
things
from
his
experience
with
coursework
at
the
university
and
his
environment
for
warnings,
ng
and
data
tables
that
maybe
that
is
more
of
a
hacktoberfest
kind
of
topic.
Uli.
Could
you
absorb
hacktoberfest
contributions
or
or
did
you
find
them
a
distraction
in
years
past.
G
G
G
The
problem
is
you
you,
you
need
your
ux
experience
and
you
need
jenkins
experience
to
understand
what's
going
on,
and
I
think
this
was
the
main
problem
that
if
you
have
a
ux
expert,
then
you
don't
have
someone
who
knows
what
is
code
coverage
and
what
to
show
in
code
coverage.
So
I'm
not
sure
if
it's
so
helpful.
B
H
For
us
to
go,
try
to
tackle
might
help
get
better
eyes
on
those
tagged
issues,
but
also
I
realize
that
it's
you
know
it's
it's
a
it's
an
ask
for
a
little
bit
of
work
for
our
maintainers,
who
are
active
in
this
workspace
and
so
definitely
want
to
make
sure
that
we're
respectful
of
that
and
being
helpful
and
not
adding
more.
You
know
useless
work
for
you.
G
Yeah,
but
I
think
it's
not
so
really
useless,
because
I
I
use
these
issues
in
a
for
different
audience
and,
for
instance,
I
use
them
these
issues.
For
my
students,
that's
okay,
too,
so
I
just
noticed
that
it
was
not
really
helpful
for
oktoberfest
yeah.
So
what
I
can
do
is
to
review
these
issues
that
I
have,
and
I
also
can
add,
a
lot
of
new
ones,
a
lot
of
them
I
can
add,
so
maybe
it's
helpful
and
if
it's
not
helpful,
it's
not.
H
G
C
Yeah
there's
a
number
of
open
issues
on
jira,
which
some
of
them
are
probably
fine
for
new
contributors,
some
of
them
not.
So
it's
quite
a
lot
of
open,
ux
regressions,
which
could
probably
be
looked
at
apart
from
that
there's.
If
it's
like
ex
more
experienced
from
engineers,
there's
pieces
of
work
that
getting
a
bit
stalled
that
could
certainly
be
helped
with
in
certain
areas,
I'm
not
sure,
there's
things
like
tepee
and
then
there
was
the
jenkins
button.
Rework
that
was
tried
a
while
ago,
which
would
be
nice
to
revive.
H
C
A
A
C
A
A
E
C
Yes,
yeah
yeah
and
another
project
is
things
like
ripping
out
back
to
build
links
and
that
sort
of
thing
and
removing
side
panels
that
don't
need
to
be
done
like
so.
I
didn't
actually
show
it
today,
but
there's
a
I
did
a
pull
request
on
the
credentials
plugin
to
rework
its
layout,
but
so
it
basically
removes
the
side
panels
mostly
and
moves
any
actions
from
that
into
the
app
bar
along
with
a
couple
other
fixes.
I
think.
A
B
E
Yeah
to
a
degree,
the
challenge
here
is
basically
identifying
plugins
that
misbehave
in
some
way,
not
everything
is
as
simple
as
tim's
query
for
bigtable
the
keyword,
but
one
of
the
things
is,
for
example,
if
you
would
not
have
a
site
panel
with
links
other
than
you
know
back
to
dashboard,
then
we
would
change
the
layout
to
not
have
a
site
panel
at
all.
I
think
is
the
current
rule
and
if
you
know
of
plugins
that
do
have
such
pages
then
very
low
hanging,
fruit
kind
of
improvement
is
change.
E
I
think
there
are
a
handful
of
these
changes
that
we
can
define
very
generically,
and
then
you
know
if
you
have
your
favorite
plugin,
that
few
other
people
are
using,
and
you
want
to
look
into
whether
you
probably
as
as
a
jenkins
user.
You
probably
already
know
whether
that
plugin
behaves
according
to
these
rules
or
not,
and
if
it
doesn't,
you
can
follow,
pull
requests
for
it.
A
Good,
thank
you
all
right,
so
patty.
I
think
that
addressed
your
question
thanks
very
much
for
bringing
it
any
other
items
on
hacktoberfest,
so
we're
now
at
14
september.
So
we're
in
what
the
hacktoberfest
team
calls
preptember
welcome
to
prep
timber.
We're
very
glad
that
you're
here
and
hacktoberfest
starts
october.
1.
A
All
right
ready
for
next
topic
now
we're
we're
just
past
the
hour
daniel
you
had
said
you
open,
ux
regressions
might
be
brief.
Would
we
like
to
take
two
more
minutes
for
open,
ux,
regressions
and
then
in
the
meeting,
or
do
you
think
it's
going
to
take
longer
than
that?
What's
your
preference,
daniel.
E
A
E
It's
basically
just
a
graph
for
the
same
query
as
tim's
dashboard.
It
just
highlights
not
just
what's
currently
open,
but
how
much
has
been
filed
and
how
much
of
that
has
been
addressed
and,
as
you
can
see,
there's
quite
the
gap,
both
in
absolute
terms
as
well
as
in
relative
terms.
A
third
of
all
file
regression
still
being
open
is
is
a
lot
thank
you
and
it
seems
to
keep
growing.
C
C
D
A
All
right,
then,
I
propose
we
go
ahead
and
end
I'll
after
the
recording
is
archived
I'll
upload
a
copy
of
the
recording
I'm
going
to
actually
put
index
points
into
this
one
so
that
people
can
see
jump
to
various
points
in
the
demos.
Thanks
john
thanks
tim
looking
forward
to
seeing
everybody
at
devops
world.
Thank
you
very,
very
much.