►
From YouTube: CHAOSS.Evolution.July.3.2019
Description
CHAOSS.Evolution.July.3.2019
B
Okay,
then,
for
the
recording,
we
are
reviewing
the
open
issues.
We
are
right
now
in
188,
in
the
repository
in
the
working
group
of
story,
and
for
this
one
there
is
recommend
for
a
dead
link
I'm
going
to
level
it
as
good
first
issue,
just
in
case
somebody
wants
and
if
not
nobody
wants
to
take
it.
I.
A
C
B
C
Is
no
no
more
yeah
that
issue
I?
Think
we
during
the
it's
just
not
it's
not
an
issue,
that's
been
defined,
so
there's
no
actual,
there's
no
actual
metric
age
for
it.
So
I
don't
know
if
we
want
to
have
it
point
towards
issues
new
which
is
a
metric.
That's
been
defined
yeah,
but
that's
not
the
way.
It's
written
clearly
yeah.
A
B
B
A
B
C
D
B
B
B
B
B
B
B
Later
they
are
not
coming
for
code
changes
lines
and
coaching
is
the
whole
key
change.
There
is
common
yeah,
but
it's
only
related
to
the
reference
implementation,
which
is
something
we
are
working
on
and
priories
just
commenting.
He
is
a
Google,
some
of
the
other
student,
but
it's
just
saying
that
I
knew.
A
D
A
Yeah
comment:
I
think
the
evolution
candidate
metrics
are
I've,
been
taking
a
look
at
I'm,
really
nice
and
detailed.
So
thanks
for
the
work
on
that
to
the
evolution,
group
and
I.
Think
to
your
point
yesterday
in
the
community
call
hey-zeus,
you
know.
Maybe
this
is
something
in
later
versions.
We
can
ask
for
the
other
working
groups
to
kind
of
strife,
or
is
this
level
of
detail
so
anyway
I
just
thanks
for
the
work.
Ok,.
A
A
B
B
159,
which
is
documenting
how
remote
lab
can
display
the
metrics
that
have
been
released,
I
need
to
still
go
through
it,
but
they
think
that
that
was
already
done
for,
if
not
all,
most,
of
the
metrics,
okay
and
yeah,
because
I
see
there,
you
can
see
several
Apple
Records
linked.
You
know
them
are
merged,
so
I
think
all
of
the
matrix
now
have
the
blue
mode
of
implementation
with
them.
That's
great,
so
I'm
closing
this
one
right,
yep.
B
A
E
B
B
So,
in
a
very
simple
example
like
computing,
the
number
of
open
issues,
for
instance,
when
s
is
go
to
the
database
and
get
directly
with
a
curry
the
number
of
ability
and
display
that,
and
they
think
that
can
be
the
number
of
open
issues
per
month
or
something
so
what
I
have
the
plan
to
do
in
the
future
is
to
include
their
specific
query
in
the
non
implementation
section
of
the
matrix?
Okay,
all
right
now.
B
E
E
A
B
D
B
D
B
Then
we
can
go
move
on
to
pull
requests,
and
here
we
have
like
again
several
two
lovers
by
the
war
summer:
foot
project
we
can
escape
them,
but
just
for
briefing
you
over
them.
We
already
have
a
class
hierarchy
for
the
implementation
for
this
reference
implementation,
and
now
the
student
is
implementing
the
different
networks:
okay,
yep.
B
B
A
B
B
A
B
A
A
B
That's
by
reading
it
there
were
some,
not
some
edges.
So
if
somebody
can
review
the
text,
which
is
not
much
more
than
that,
I'll
take
a
look.
This
is
a
bit
of
a
detail
only
when
we
were
implemented
I
figure
out
that
the
description
of
what
is
our
code
chains
are
aligned
in
the
good
sense.
It
was
not
that
clear,
okay,
some.
E
B
B
C
B
B
A
B
A
B
F
C
B
My
feeling
is
that
the
pension
direction
I
mean
if,
after
this
release,
I
mean
three
months
after
cash
from
North
America.
We
see
there's
a
lot
of
more
and
we
have
several
new
matrix
changes.
In
other
words,
we
can
consider
a
new
if
not
I
would
well.
A
A
B
A
A
B
It's
very
likely
that
during
the
next
month
we
are
going
to
have
more
movement
in
the
package.
So
probably
around
I
don't
know
October.
Maybe
we
can.
We
can
evaluate
and
decide.
Okay.
On
the
other
hand,
I
see
that
the
current
release
processes
may
be
too
long
because
it
says
taking
those
two
months
from
the
moment.
The
working
groups
decide
what
to
include
to
the
moment.
We
can
fix
them
and
an
object
yep,
and
with
that
I
mean
more
than
two
releases.
B
E
B
F
That
works
for
me
thanks.
One
other
thing
we
could
do
is
like
do
one
major
release.
Then
we
have
minor
releases,
yeah
yeah
then.
So,
if
we
are
making
like
let's
address
on
pressing
issues,
we
can
make
a
minor
release.
Then,
at
the
end
of
the
day
it
depends
on
how
the
they
are
consumed
like
the
community.
If
the
desire
for
more
like
some
high
productivity,
we
could
not
I
just
that's
right.
B
That
could
be
especially
interesting
in
the
case
of
our
important
modification
to
already
religious
metrics.
For
that
reason,
some
will
find
how
that
than
some
of
the
definition
was
was
or
they'd
be
grilling
it.
So
we
could
do
something
like
a
version
1.1,
yes,
with
some
of
the
metrics
change,
so
non
new
metrics
only
changes
to
existing
model,
yep.
F
Want
to
be
clarified
at
some
times,
I'm
confused,
like
what
we
discussed
yesterday,
if
we
just
want
to
go
and
like
give
our
feedback.
Okay,
it's
fine
like
for
the
English
country
that
math
releases
the
sense
yesterday.
If
we
just
want
to
go
through
and
see
like
it's
okay
with
me,
do
we
need
to
create
a
poor
request
for
that?
No.
F
B
F
A
B
F
B
F
B
Then
the
bottom
eye
gets
highlighted
appears
tough
to
write
in
the
box.
Yeah
right
you
can.
You
can
comment
in
a
close
it
issue.
The
only
problem
is
that
that's
not
going
to
appear
in
the
list
of
open
issues
because
it's
not
open
PDI.
It's
closed
yeah
yeah,
but
you
can
comment
and
the
people
involved
in
the
in
the
issue.
They
are
going
to
receive
an
email
that
you
comment
it
so.
Okay,.