►
From YouTube: CHAOSS.Evolution.November.7.2019
Description
CHAOSS.Evolution.November.7.2019
A
C
C
Go
ahead
and
we
merged
them,
because
there
were
like
four
of
us
trying
to
clean
up
the
evolution,
repository,
get
rid
of
old
ones
and
put
new
ones
in
and
it
was
just
hard
to
coordinate.
If
we
didn't
merge
things
so
I
mean
Kurt.
Probably
the
first
thing
is
just
to
review
the
things
that
we
merged
just
yeah,
so
in
case
there's
any
objections
which
I
doubt
there
will
be
because
everybody
likes
it.
When
someone
cleans
their
house
yeah
go.
B
D
D
This
was
the
second
metric
that
I
worked
on
and
we
templating
it
it's
the
same
as
the
all
the
other
templating
ones.
It
just
changes.
This
itching
there's
one
whitespace
change
I
made
in
here
to
be
consistent
with
the
rest
of
the
changes
we
changes
we
made,
and
then
all
of
this
is
just
porting
stuff
over
to
the
new
template.
D
Then
one
was
believed
it
was
this
one,
so
the
community
growth
focus
area
somehow
got
missed
in
the
transition
of
working
on
the
new
focuses.
We
were
breaking
out
code
development,
so
this
one
just
adds
that
back-end
as
a
focus
area
in
the
readme.
Just
so
people
know
it
exists
just
so
for
posterity
sake,
I
think
it
just
got
lost
in
the
transition,
the
other
one.
Another
one
was
this.
So
this
one
takes
all
of
the
metrics
and
code
development,
efficiency
and
switches
them
over,
so
reviews
accepted,
declined
and
I
think
just
iteration
hour.
Duration.
D
D
So
those
duplicates
and
add
ones
that
we
didn't
think
really
made
any
sense
to
have
their
own
files.
We
got
rid
of
those
as
well
I
think
some
of
them
also
were
accidental,
deletes,
but
there's
a
commit.
There's
a
polar
Coast
will
go
through,
which
will
add
them
back
in,
and
we
can
talk
more
about
that.
But
those
are
the
I
think
this
is
the
the
four
big
ones
that
that
we've
merged
already
I
think.
B
C
D
Stuff
this
one
I'm
just
looking
at
this
issue,
really
quick,
okay,
so
since
I
added
community
growth
in
this
isn't
quite
done,
but
it's
almost
done
and
I
have
another
I.
Did
the
issue
resolution
metrics
well
I'll
get
to
that!
Wait
to
that
part
a
second
before
we
go
through
the
the
ones
that
we
haven't
merged.
Yet
there
any
questions.
B
A
D
A
D
D
Okay,
so
let's
start
with
the
the
first
one
259,
so
this
one
is
another
switch
here.
Let
me
put
the
link
in
the
chat
just
for
posterity's
sake,
just
for
ease
of
so
we
can
all
pull
it
up
if
we
want
to
oops
I
need
to
do
that.
So
this
one
just
switches,
it
says
all
of
the
code:
development
process,
quality
metrics,
it's
just
reviews-
is
the
only
one
that's
currently
like
defined
to
be
in
that
focus
area.
D
So
that's
the
only
one
that
changes-
and
this
is
the
same-
it's
the
same
sort
of
changes,
all
the
other
ones,
just
switching
over
how
we
did
that
first
metric
together
on
the
call
two
weeks
ago,
I
think
was
two
weeks
ago
or
yeah.
I
think
was
two
weeks
ago.
It
was
switching
over
all
of
that
stuff.
In
the
same
vein.
D
D
B
D
D
D
D
D
D
B
B
D
D
B
D
Hang
on
so,
if
you
look
at
the
is
italics
one
underscore
two
underscores
I've
been
doing
two
and
I
think
as
I
thought
they
were
italics.
If
you
look
at
it,
if
you
look
at
the
markdown,
I
did
I
did
to
underscore,
because
that's
what
I
thought
italics
was.
Is
that
I've
been
doing
it
wrong
this
whole
time
because
I
had
to
me
they
are
separate.
I
thought
I
was
doing
italics,
hang
on
I.
B
B
D
D
D
B
A
D
B
D
B
B
B
A
D
D
D
C
B
A
A
D
D
B
D
D
B
B
B
D
It
changes
the
name
of
the
file
to
match
the
metric,
that's
defined
inside
and
then
also
switches
the
metric
over
to
be
in
the
new
template.
For
this
one.
We
only
did
metrics
that
one
stub
metrics
and
by
that
I
just
mean
the
only
thing
that
was
in
the
file
for
the
definition
was
this
question,
so
we
just
moved
the
question
over
and
then
copied
the
rest
of
the
template
in
just
to
go
ahead
and
switch
them
over
as
well
as
renaming
the
file.
So
we
find
them
easier
if
that
makes
sense.
D
D
D
C
Right,
so
that's
if
you
create
a
lot,
if
you
click
that
link
that'll,
take
you
to
a
folder
that
I
have
used
to
create
a
whole
bunch
of
metrics
that
have
the
template.
I
pasted.
Everything
in
those
templates
in
markdown
and
I
put
the
name
of
the
metric
at
the
top,
and
then
the
question
in
for
each
metric
and
a
short
description
for
each
metric
is
a
starting
point
right
now
and
I
figure.
C
If
we
can
edit
these
Google
Docs
as
markdown,
then
we
can
just
copy
and
paste
them
into
markdown
Docs
and
getting
to
your
question
from
yesterday's
auger
saw,
we
could
do
some
work
on
the
you
know.
We
could
choose
metrics
anonymous,
pandas
and
closed
issues
count.
Now
we
could.
We
could
choose
a
metric
to
start
working
on
in
this
meeting,
with
the
balance
of
time
that
we
have.
C
D
B
C
A
C
C
C
C
C
D
D
D
C
C
D
B
D
D
B
D
B
A
D
D
B
C
B
The
resolution
duration
for
open
issues
doesn't
make
sense
because
they're
not
right,
that's
true.
We
can
look
at
during
this
time
period.
How
many
issues
did
we
close
our
degree
for
old
issues
and
filter
by
quote
time,
or
we
can
look
at
over
time?
How
long
did
it
take
from
when
we
open
it
by
that?
Okay.
D
D
B
D
B
D
A
D
D
D
A
B
A
A
D
B
D
D
D
Are
there
any
other
possible
visualizations,
besides
just
doing
the
average
over
time?
Should
we
also
just
include
the
total
average
over
all
time
like
as
its
own
visualization
like,
instead
of
doing
what
it
was
for
each
of
these
time
periods,
just
like
a
number
like
for
this
time
period,
is
that
a
visualization.
B
D
D
B
D
B
B
B
D
At
time
for
the
yeah
for
this
line
right
here
for
issues
that
were
reopen
and
closed
again,
this
is:
does
that
include
like
over
a
time
period,
an
issue
was
opened
and
then
closed
and
then
like
reopened.
Is
it
like
it's
closed
and
stays
closed
within
the
time
period,
or
only
it
had
a
closed
in
the
time
period?
B
So
the
way
that
I
wasn't
ending
this
sentence
is
to
say
if
we
have
an
issue
that
was
reopened
and
closed
and
reopened
and
closed,
we
only
look
at
the
last
post
and
you
closed
and
reopened
in
the
middle
did
not
account
for
this
metric
okay,
and
so,
if
it
has
not
been
closed
again,
then
it's
obviously
not
resolved.
Okay,.