►
From YouTube: CHAOSS.Risk.June.16.2020
Description
CHAOSS.Risk.June.16.2020
A
A
A
A
B
A
I
I
I
haven't
shared
the
zephyr
report
that
we
did
previously,
but
I
could
kate's
given
me
permission
now,
because
it's
already
public
to
share
that
zephyr
report,
and
so
I
I
think,
that's
a
really
good
place
to
start
I
was
I
was.
I
think
I
could
have
asked
much
sooner
to
share
it,
but
I
lost
track
of
that
to
do
item
of
sharing
it
because
it
was
about
a
week
and
a
half
after
we
shared
it
with
kate,
and
I
shared
with
that.
A
B
A
That's
novel
compared
to
the
standard
report
is
that
we
are
presenting
anonymized
competitors
inside
this
report.
So
for
the
first
page
of
the
report,
this
is
more
than
a
page
mat,
so
you
can,
you
can
make
sure
that's
clear.
This
is
more
than
a
page,
but
it's
that's
just
the
way.
It
is
because
it's
the
graphs
are
kind
of
big
and
it
is
more
visual
and
there's
there's
a
couple
of
distinctions.
One
is
that
you
have
all
the
merged
and
all
the
not
merged
in
one
column.
A
B
And
the
all
merged
and
not
merged
contains
includes
the
slowest
as
well.
That's
right,
that's
right
highlight
that
out
and
the
quite
frankly,
the
size
of
the
slowest
of
the
not
merged
and
the
lowest
not
merged
those
those
those
the
slowest
not
merged
are
lining
up
with
the
not
merged
pretty
much,
and
so
that
was
one
of
the
insights
we
had
from
later
on.
It
shows
up
better
than
some
of
your
other
charts,
but
that's,
I
think,
what
you're
remembering
sean.
B
A
Yeah,
it's
so
yeah
you're
right
for
the
prior
chart.
You
can
see
that
the
volume's
gone
up
and
then
essentially,
what
we're
seeing
is
there's
a
reaction
in
2018
to
the
slowness
or
the
perceived.
We
could
do
better
speed,
speed
wise
on
the
on
the
close
and
then,
as
the
volume
goes
up,
the
capacity
or
the
the
common
the
shared.
A
What
is
it
the
commons?
The
eleanor
ostrom's
idea
of
the
commons
is,
in
fact
people
and
as
the
number
of
people
grazing
on
the
commons
increases
or
the
number
of
code
requests
keep
grazing
on
the
commons
increases.
The
people
able
to
review
them
quickly
decrease
this.
This,
and
I
don't
know
if
you
want
to
talk
about
this
kate,
I'm
sucking
all
the
air
out
of
the
room.
B
B
If
you
go
to
the
next
slide
and
you
can
sort
of
do
the
comparison
against
the
other
repos
where
we
have
you
know
zephyr
and
you
can
see
his
effort,
the
red
is
obviously
things
are
taking
long,
but
you
can
sort
of
see
that
yeah
there's
spots
where
we're
not
thrilled
with
zephyr
but
compared
to
some
of
the
other.
You
know
alternatives
out
there.
In
this
space,
the
zephyr
community
is
doing
pretty
well.
A
A
B
And
we
we
have
been
here
a
mix
of
competitors
that
are
open
source
projects
that
we
don't
want
to
be
negative
about,
and
but
there's
also
ones
that
are
supported
by
companies
specifically,
and
so
it's
there's
no
point
in
attracting
rocks
that
we
did
want
to
understand.
You
know,
are
we
sort
of
better
or
worse
than
the
average
like
you
know,
then
what
else
is
out
there
and,
as
you
can
see
from
this,
it's
sort
of
saying
that
you
know
we
we've
we've
got
some
things
figured
out,
so
we
don't
beat
ourselves
too
hard.
B
C
B
A
Yeah,
that's
exactly
right
and
in
fact,
one
of
the
things
that
I've
started
doing
there's
a
sort
of
a
technical
understanding
trade-off
that
we're
experiencing
right
now.
One
of
the
things
I've
insisted
on
is
detailed,
captions
being
included
in
each
of
these
graphs
so
that
when
the
graph
is
created,
the
caption
is
created,
believe
it
or
not,
a
lot
of
the
tools
that
generate
visualizations
when
you
do
an
export
of
the
image,
don't
export
the
caption,
which
is
so
that's
that's
a
technical
sort
of
challenge
that
we're
working
on
right
now.
B
C
B
They
were
sort
of
like
okay.
Well,
you
know
it
it's.
The
behavior
is
different
for
the
slower
ones
than
it
is
for
overall
and
with
someone's
hypothesis
that
it
was
this
way,
and
so
this
was
a
way
of
addressing
that
too.
Okay
and
whether
it
be
the
slowest
10
percent
as
low
as
20,
not
sure
what
the
right
number
to
use
in
general
is,
but
looking
at
the
slower
ones
does,
you
know
say
where
it's
an
idea
to
see.
If
do
we
have
a
you
know,
behavior
issue.
C
C
A
Two
is
two
is
the
most
interesting
I
think
three
and
four
also
have
high
value,
but
only
one
contract
only
one.
I
think
I
think
we
would
want
to
maybe
show
two
and
three
side
by
side,
because
because,
as
I
was
explaining
it,
I
couldn't
remember
which
ones
had
the
height
the
volume
isn't
as
clear
here
and
so
the
the
reason
why
the
responsiveness
went
back
up
in
2019
isn't
clear
on
this
slide.
A
A
That
gives
you
a
competitive
context
for
okay,
it's
great
that
you're
doing
okay
compared
to
yourselves.
But
how
are
you
doing
compared
to
the
projects
that
you're
competing
against
or
the
other
pro
or
if
it's
not
even
a
competition
thing,
but
you're
considering
four
web
frameworks
and
you
want
to
know
which
ones
are
the
best,
for
example,.
B
A
C
C
A
Pretty
straightforward,
the
one
thing
I
have
gabe
working
on
right
now
is
auto
scaling.
So
obviously
zephyr
has
a
max.
The
y
max
is
around
6348
right
and
different
projects
are
going
to
have
different
y-maxes
and
we
have
some
logic
in
there
to
sort
of
tune
the
size
of
the
graph
to
the
ymax
and
the
xmax,
so
that,
if
you
have
100
repositories,
it
finds
a
way
to
100
is
probably
too
many.
A
C
A
A
C
B
A
Otherwise,
yeah
the
context
is
missing
like
it's,
it
relies
on
the
prior
slide
and-
and
I
think
some
of
these
like
this
is
for
this
is
in
presentation
format,
because
we
were
doing
it
as
a
presentation,
but
I
think
I
think
some
of
these
can
be
annotated
and
included
on
a
they
don't
have
to
be
as
big.
I
think
the
fonts
can
be
not
bolded
smaller,
there's
weights.
There
are
ways
to
make
it
a
little
bit
more
fitting
on
a
page,
friendly,
okay.
A
So
then
I
don't
like
I'm
gonna,
have
kate
cancel
in
her
meeting.
If
I
show
her
this
next
part,
but
I'm
gonna
do
it
well,
kate,
do
you
want
to
show
the
rest
of
this
or
matt?
Do
you
want
to
see
the
rest
of
the
zephyr
one
right
now,
I'm
gonna
fire
through
it
real
quick,
and
so
you
can
see
what
it
is.
Yeah.
A
So
I
mean
the
mean
days
to
first
response
for
closed
pull
requests.
The
critical
observation
that
come
came
out
of
this
is,
I
don't
think,
a
shock.
It's
that
one
is
when
a
pull
request
ultimately
ends
up,
not
merged.
The
response
time
is
slower
because
people
are
avoiding
it
or
for
whatever
reason,
unsure.
B
A
A
A
Pull
request
commits
this
is,
I
think,
a
very
important
one
to
think
about,
because
this
gets
also
into
the
superposition
question,
because
you
can
see
that
the
number
of
not
merged
rejected,
pull
requests.
They
all
have
more
commits
than
the
merged
accepted
ones.
Again.
Super
consistent
with
the
work
that
housing
did
on
superposition
that
the
bigger
it
is,
the
harder
it
is
to
understand
and
the
less
likely
it
is
to
be
merged.
A
C
B
A
But
we
didn't
have
to
do
that
in
this
case,
and
then
this
is
a
dot
for
every
single
thing
and
it's
an
indication
of
the
days
to
the
first
comment,
the
20
slowest
to
close
pull
requests
of
about
the
same
as
the
rest,
but
all
closed
pull
requests.
Sometimes
comments
occur
a
month
after
opening.
So
there
are
these
occasional,
it's
just
a
novelty.
A
Sometimes
a
pull
request
is
issued
and
it
takes
more
than
two
or
three
weeks
for
the
first
comment
to
occur
on
it,
and
these
are
very
anomalous
but
we're
pointing
them
out-
and
this
is
the
mean
count
of
event
type
for
closer
press
requests.
So
each
pull
request
has
an
event
listing
every
event
that
occurred
on
that
pull.
A
Request
and
events
include
things
like
comments,
being
closed,
being
referenced,
being
subscribed
being
labeled
having
a
review
request,
and
you
can
see
that
in
all
cases
the
number
of
events
on
a
pull
request
continued
to
increase
as
time
went
forward.
So
the
more
active
and
developed
the
zephyr
community
became
the
more
people
were
the
more
comment
and
closing
and
referencing
and
subscribing
accounts
occurred.
Now
we
could
one
idea
I
have
for
this.
As
I
look
at
it
is.
B
A
A
A
A
Yeah
4
30
central
daylight
time
right
all
right.
Talk
to
you,
then
bye,
all
right,
okay,
so
I
just
I
want
to
take
a
breath
and
take
a
look
at
the
because
that
that
was
a
lot
of
stuff,
and
this
is
this-
I
guess
what
I'm
the
reason
that
I
showed
this
is
because
the
zephyr
report,
zephyr,
is
very,
very
concerned
about
risk,
and
this
is
when
they
wanted
to
understand
the
risk
of
their
community
sustainability.
A
This
is
what
we
need
to
know,
and
so
I
just
want
to
take
a
step
back,
breathe
and
ask
if,
if
you
would
like
to
so
in
the
case
of
jenkins
x,
they
have
a
different
set
of
questions,
and
I
wanted
to
show
that,
but
I
don't
need
to
because
we
have
a
few
other
things
on
the
agenda
to
discuss
and
we're
halfway.
We've
got
about
19
minutes
left
so.
D
A
A
A
C
A
Closed
is
a
combination
of
accepted
and
declined.
Merge
as
a
combination
of
no
closed
is
a
respon.
A
combination
of
rejected
and
enclosed
and
accepted
and
closed
is
accepted.
So
merged
and
closed
is
accepted,
sorry
merged
and
accepted,
accepted
and
merged.
Are
the
right
can't
be
accepted
without
being
merged?
Yes,
so
if
it's
closed
and
merged,
then
it's
accepted.
If
it's,
if
it's
closed
and
and
not
merged,
then
essentially
there's
no
merge
date.
Then
it's
rejected
right.
C
A
To
keep
so
here's
what
I
would
say,
I
think
it's
important
that
that
be
noted
in
the
ana.
If
that
be
that
be
annotated.
So
it's
it's
in
the
case.
So
there's
two
there's
two
linguistic
things
happening
here:
one
is
the
language
that
the
actual
projects
use
so
that
when
I'm
that,
when
you're,
showing
this
to
the
tsc
or
when
you're
showing
this
to
your
to
your
users,
they
know
what
you
mean:
there's
also
the
mapping
of
that
to
chaos,
language
because
chaos,
language
has
is
more
abstract.
A
So,
if
I
said,
reviews
accepted
and
reviews
declined
for
most
projects,
that
wouldn't
mean
anything
like
it
would
have
meant
nothing
to
the
zephyr
technical
steering
committee,
because
they
don't
use
those
terms.
They
use
pull
requests,
but
I
do
think
it's
important
to
include
those
terms
somewhere
in
a
caption
or
somewhere
in
an
annotation,
so
that
people
know
when
they're
looking
at
the
chaos
metrics.
What
these
things
are.
Does
that
make
sense.
C
A
Look
at
the
the
volume
that
we
have
here
so
in
the
in
these
purple-ish
bars.
This
is
a
grand
total
of
all
the
poll,
requests
or
reviews
that
are
existed
and
that
were
resolved
in
a
calendar
year
and
the
ones
that
are
merged,
which
means
accepted,
is
the
dark
purple
bar
and
the
ones
that
are
not
merged
or
are
the
I
guess
like
lighter
okay,
and
so
yes,
the
the
kia
step,
which
is
also
yeah.
D
C
A
C
A
So
nice,
so
this
is
a
I
would
say.
This
is
a
I
think.
What's
useful
about
this
report
is
this
report
is
here,
are
questions
that
very
active
emergent
project
has
and
you're
right,
we're
we're
combining
so
so
combining
common
metrics
with
other
things,
I
think,
is
by
definition
expected
because
common
by
definition
means
that
more
than
one
working
group
is
interested
in
it.
D
But
I
also
feel
that
common,
not
a
specific
evolution
and
risk,
have
a
lot
of
overlapping
mattresses,
because
in
evolution,
project
evolves
over
time,
and
you
see
the
risk
in
the
evolution
also
like
how
the
risk
factors
are
evolving
or
changing
over
the
period
of
time.
So
there
are
many
metrics
which
can
be
in
both
the
working
groups
or
even.
A
I
think
what's
useful
or
interesting
about
this
report
is
that
it's
this
is
grounded,
and
this
is
what
it
what's
this,
what
a
really
super
active
and
growing
project
wanted
to
know
and
and
so
how
we
annotate
it
and
reference
it
to
chaos,
metrics,
and
I
think
doing
so-
is
really
important
it
it.
I
think
it
demonstrates
the
kind
of
value
that
chaos
can
bring
to
a
project
beyond
discrete
metric
definition.
C
D
C
C
A
A
C
A
A
C
A
C
C
C
A
Well,
I
think
I
I
think
I
think
one
of
the
narratives
that
we
can
put
around
the
community
report
is
here.
Here's
chaos
is
defined
like
there's
been,
there
has
not
been
agreement
in
the
open
source
community
about
what
a
commit
is,
or
a
pull
request
is
or
time
to
close
is
we're
defining
a
standard
way
of
saying
this
is
what
that
is,
and
that
is
useful
in
and
of
itself,
because
now
all
of
your
metrics,
regardless
of
the
tool,
have
the
same
definition.
A
A
It
did
it
did
it
did
it,
it's
it's
and
I
think
yeah,
and
so
I
guess
I've
been
trying
to
say
this,
but
being
very
unsuccessful,
because
I
haven't
had
permission
to
share
this
effort
report
like
when
I
say
I
think
we
need
different
metrics.
This
is
what
I've
meant,
and
I
just
I
haven't
had
the
ability
to.
I
haven't
had
permission
to
share
this
effort
report
until
now,
and
so
this
is
kind
of,
I
think
this
is
a
really
great
way
of
elaborating
on
risk.
We
have
two
minutes
left.
A
A
C
A
A
Well,
okay,
so
he's
the
guy.
So
I
guess
with
I
will
say
that
on
this
particular
instance
of
the
risk
project,
we
really
got
some
interesting
discussion
going.
We
didn't
get
to
things
that
need.
We
didn't
get
to
every
thing
and
I
will
leave
the
to
the
group
to
get
metrics
ready
for
release,
I.e
me
and
kate,
and
thus
motion
to
conclude
on
time.