►
From YouTube: CHAOSS.Evolution.April.8.2020
Description
CHAOSS.Evolution.April.8.2020
A
A
A
C
A
D
A
A
D
D
A
Oh
yeah,
I
I
said
that
I
close
this
Kevin's
gonna
update
the
meeting
time
so
yeah.
Let's
just
keep
going
with
the
PRS
and
I
will
stop
screen
sharing
and
let
you
take
over
if
I
can
find
my
there.
We
go
didn't
but
hit
so
oddly
and
everybody
be
sure
to
put
your
name
on
the
participation
sheet.
If
you
didn't
see
it,
one
of
the
funky
funky
things
about
zoom
is,
if
you
aren't
here
when
something
is
shared
in
chat,
has
to
be
shared.
So
I
already
shared
a
link
to
the
meeting
minutes.
C
D
D
A
D
A
A
D
A
A
A
A
So
just
just
not
meeting
this
next
week
it's
removed
we're
skipping
a
week,
we're
moving
it
from
the
13th
to
the
20th,
because
a
number
of
people
have
Easter
Monday
off
of
work
and
April
13th
is
Easter
Monday
and
then,
after
that,
you're
going
to
the
27th
will
be
the
next
meeting.
So
it
is
return
to
our
normal
cadence.
F
F
F
D
D
So
last
week
we
talked
about
the
news
metric
and
about
moving
it
from
being
three
separate
metrics
reviews
for
use,
accepted
and
reviews
closed
to
just
having
reviews
and
then
having
a
filter
for
status
of
open
or
closed,
which
is
what
this
PR
is
and
I
think
didn't
we
decide
that
we
were
going
to
still
wait
a
full
month
on
this
change,
even
though
it's
so
simple,
truly
because
it
gets
rid
of
two
metrics
and
that's
a
significant
enough
change.
Thank
you
very
much
sheet
yeah.
Well,.
A
I'm,
looking
at
March,
25th
and
I,
don't
see
a
note
about
that.
I
do
remember.
She
talked
to
her
create
tags
and
continuous
release
cycles
and
the
pull
request
is
adding
two
filters:
two
reviews,
but
what's
not
can
I
guess
I
created
that
but
I
didn't
create
much
comment,
but
that
would
remove
two
metrics
and
possibly.
D
A
So
real
music
I
mean
in
the
room,
I,
don't
see,
reviews
I,
don't
see,
reviews
I
see
respond.
If
you
look
at
my
screen,
I
see
I,
see,
reviews
open
and
reviews
closed,
yeah
I
didn't
mean
to
say
accepted.
Okay,
that's
my
fault.
Yeah
I!
Don't
think
that's
a
problem
actually,
because
those
are
not
our
least
metrics.
A
Removing
a
metric
as
if
it's
already
been
released
so
and
is
the
roof.
It's
it
just
just
reviews
as
released
so
I
mean
don't
I,
don't
think
it
requires
any
further
discussion
beyond
did
we
create
the
issue
that
we're
going
to
add
two
new
filters,
because
I
created
the
created
the
floor
with
the
changes
that
we
discussed?
A
A
F
D
Mean
it
it
as
small
as
it
is:
it's
a
non-trivial,
a
change
to
hollow
the
metric
like
functions.
It's
not
like
a
formatting
or
a
ticketing
thing.
It's
like
changing
the
content,
and
so
even
and
it's
a
release
metric,
so
I
still
think
we
should
wait
another
two!
Well,
we
should
we
actually
wait.
Four
weeks
from.
A
D
D
D
C
A
E
E
E
A
D
D
A
D
D
A
A
A
C
A
D
A
A
D
D
E
A
E
E
D
A
D
I'm
saying
is
that
the
formatting
for
how
the
aggregators
are
specified?
It's
not
how
we
do
it
in
the
rest
of
everything
else.
So
that's
that's
the
change
that
I
want
to
suggest
it's,
not
a
it's,
not
a
top
level
of
heading,
like
with
the
with
the
hash
marks
hash
marks
with
that
hash
tags.
It's
it's
a
lower
level,
one
which
is
fine,
like
the
subheadings,
are
supposed
to
be
up
for
grabs
that
the
there
is
no
high.
There
is
no
top-level
aggregators
hanging
in
the
regular
metrics
template,
so
that
needs
to
be
changed.
D
D
It
is
a
heading
in
like
not
down
heading
I'm
talking
about
just
like
a
generic
like
concept,
it's
a
it's
like
a
heading
for
a
section,
but
it's
not
a
it's,
not
formatted
like
a
markdown
heading.
It's
not
supposed
to
be
it's
supposed
to
be
formatted,
as
sharing
my
Firefox
sorry
share
with
lash.
It's
supposed
to
be
formatted.
Wait!
No!
That's
the
wrong
window
like
this
under
implementation.
That's
what
I'm
talking
about
it's,
not
one
of
these
high-level
headers,
okay,
I!
Think
it's
I!
Think
it's
a
high
level
heading
a
lot
of
metrics
released!
D
D
Heading
template,
the
only
things
that
are
different
are
these
optional
headings
and
if
there's
some
things
we
want
to
add,
we
add
them
as
bolded
words
below
it
same
place,
same
thing:
we
do
in
the
data
collection
strategy,
okay,
so
this
business,
how
we've
done
it
and
we
can
do
it
a
different
way,
but
this
is
how
we've
done
it
for
every
metric
we've
released
so
far.
Okay,
when.
A
D
D
D
A
This
is
pretty
hard
to
follow
like
how
much
supposed
to
do
this,
because
I've
created
a
number
of
Google
Docs
using
a
different
template
and
I
know
that,
like
if
so,
this
is
like
a
candidate
like
if
this,
like
I
used
this
high-level
stuff
and
I
guess
I
guess
your
only
question
about
aggregators
and
parameters,
then,
is
that
it
should
be
specified
as
a
bold
instead
of
a
heading
yeah.
That
would
be
your
feedback
all
right.
So
I.
D
D
But
the
reason
that
the
other
stuff
is
not
in
this
template
is
because
this
is
the
master
chaos
template
that
everybody
uses,
so
I
didn't
want
to
put
our
specific
stuff
in
the
master
template.
Maybe
it
would-
and
maybe
it
would
make
sense
to
have
in
here
an
additional
like
evolution,
code,
development,
metric
or
whatever
like
it's.
You
know
our
own
templates
to
help
them
with
that,
but
I
wouldn't
look
at
it
in
in
this
template,
because
this
is
the
this
is
the
chaos
one
and
I
don't
want
to
change.
A
D
D
A
A
A
A
C
D
D
D
A
D
A
A
D
A
D
D
D
D
A
D
What
did
you
say,
Carter
unit
the
words
since
the
kind
of
if
they
have
not
made
a
commits,
not
made
any
commits
since
the
cutoff
it'll
be
added
to
the
inactive
out
to
the
inactive
count,
yeah,
also,
the
phrase
inactive
count
added
to
the
inactive
count
of
the
period
of
their
last
commit
I,
don't
understand
what
the
of
the
whole
last
half
of
that
the
count
of
the
period
of
their
last
commit
I,
don't
know
what
that
means
either.
Is
that,
like
four?
It's
not.
A
A
A
A
A
A
D
So
so
to
me,
the
word
cutoff
is
confusing
in
that
sense,
because
to
me
cutoff
means
the
cutoff
is
a
single
date.
It's
if
you
have
not
made
a
commit,
since
you
know
the
cutoff
date
of
January
1st
2020
to
me,
that's
what
the
word
cutoff
means
that
and
I
still
think
that
doing
it.
The
way
the
of
like
you
haven't,
made
a
commit
for
this
long.
This
amount
of
time
I
think
that's
perfectly
fine.
I
just
think
the
word
cutoff
shouldn't
be
used
to
me.
That's
like
a.
F
D
F
A
A
F
F
D
A
A
A
A
D
A
E
C
D
The
reason
yeah
that's
true
because
it
might
not
be
because
they're
losing
interest
it
might
be
because
they
started
a
new
job
or
they
had
to
you
know
they
moved
across
the
world.
I
see
you're,
saying
something
like
that
come
in,
but
if
you
say
losing
interest,
you
lose
that
okay,
yeah
I
completely
agree.
We
should
change
that
I.
Think,
though,
the.
F
D
D
D
D
D
E
D
We
have
code
changes
measured
lines,
but
that's
not
the
number
of
lines.
That's
like
how
many
it's
like
the
number
of
miles
per
change.
That's
one
of
the
ways,
I
think
it's
you
know.
Let
me
put
a
link
to
other
than
that.
I,
don't
think
we
have
any
a
length
one
but
I'm,
maybe
I'm,
not
thinking
of
potential
use
cases,
but
part
of
me
is
hesitant,
said
I'm
not
really
sure
like
not
what
good
it
does,
but
I
guess
what
good
it
does
like.
D
A
So
like
so
when
you
sew
lines
of
code
is
a
metric
that
looks
at
not
commits
not
evolution,
but
it.
So
it's
not
if
you
think
of
evolution
as
where
is
a
project
at
today,
and
where
is
it
going?
The
where
is
it
going
part
is
a
large
in
large
measure,
then
how
is
it
moving
and
what
kind
of
progress
is
being
made?
Those
are
most
of
the
metrics
that
we
have
created.
I
think
create
I,
don't
know,
create
code
length
is
the
right
name,
but
I'll,
basically.
A
It's
hard
to
answer
the
question
about
efforts
to
shorten
it,
because
that
gets
pretty
complex,
although
because
then
you're
combining
you're
combining
both
the
total.
What
is
the
base
of
the
code
and
then
what
is
the
nature
of
the
commits
in
terms
of
lines
added
in
the
lead-in,
and
it's
often
hard
to
tell
if
lines
are
being
added
and
deleted
because
of
the
thoughtful
refactoring
or
because
of
a
change
in
functionality?
A
A
A
D
On
the
well,
the
code
link
one
and,
of
course
one
but
the
code
length,
one
I
think
I
just
and
it's
I
guess
the
Hughes
case
to
me
is
not
it's
immediately
apparent
but
having
the
Kokomo,
stuff
and
I
think
I
think
would
be
interesting
to
just
explore
further
the
idea
of
having
these
snapshot
metrics
so
I.
Think
of
why
you're
right
I
mean
basically
it's
all.
What
we
do
is
all
about
the
evolution.
It's
all
about
the
change,
not
so
much
a
you
know,
yeah
I'm
sure
I
know.
It
looks
like
a
specific
point.
A
All
right
so
I
just
made
some
notes
in
the
minutes
that
we
reviewed
pull
request
334
during
this
meeting,
and
also
that
we
looked
at
our
template
for
new
metrics
and
added
a
template
for
yes,
evolution,
metrics
and
then
I
assigned
myself
the
reviews
of
pull
requests,
335
and
336
before
the
next
meeting,
possibly
sooner
okay,
so
that
we
get
updated
versions
of
those.
Okay.