►
From YouTube: CHAOSS Weekly Hangout July24 2018
Description
Weekly CHAOSS Project Hangout.
A
And
then
I
don't
know,
I
thought.
I
know
this
is
an
open
session,
but
we've
always
kind
of
been
starting
with
conferences
and
stuff
like
that,
I'd
really
like
to
get
an
update
on
kind
of
the
software.
You
know
whether
it's
augur
or
or
more
lab,
and
the
reason
I
ask
is
because
I'm
I'm
really
interested
in
how,
from
a
software
perspective,
things
are
kind
of
being
aligned
with
you
know
what
I
mean,
because
I
think
that's
kind
of
an
important
component
was
the
work.
B
C
B
B
B
And
you
know
the
google
Summer
of
Code
is
now
in
the
final
weeks,
so
we
still
expect
to
have
something
fully
functional
by
the
end
of
the
period,
but
when
Dell
is
interested
in
following
even
after
the
period,
so
maybe
we
can
draw
with
with
it
and
the
third
one
is
we're
in
the
middle
of
we're
thinking
about
the
documentation
in
the
mandala.
So
a
person
from
Adobe
is
collaborating
with
us
in
that
ICU,
sir,
so
we
are
trying
to
restructure
in
everything.
B
A
person
in
Adobe,
who
is
a
user
of
game
or
lab,
suggested
to
rethink
how
the
documentation
is
written
in
restrictor
importantly
and
write
some
new
documentation
and
so
on
and
he's
interested
in
collaborating,
and
we
are
basically,
we
think
in
that
reason,
I
need
to
open
for
discussing
that
right
now
and
any
people
join
in
there
and
help
in
even
just
to
discuss
how
the
documentation
should
be
is
very
useful.
At
this
point.
Okay.
B
B
The
Danil
is
more
related
to
DNI,
you
know
again,
I
just
say
now:
they
are
still
using
our
indexes
for
most
of
the
staff
or
at
least
support
of
the
stuff.
Remember
that
they
are
working
like
in
two
levels.
Well,
I
think
George.
You
know
the
details
much
better
than
myself,
because
you
are
following
the
group
more,
but
there
is
this
work
on
the
matrix.
Let's
stay
home
attics
should
be,
and
they
don't
wanna
compete
in
the
matrix.
So
now
that
the
nail
is
still
using
the
model
of
40
billion,
the
matrix
okay.
C
B
But
I
don't
know
that
it
is
about
that
and
in
the
case
of
of
of
the
DMD
group,
all
signals
as
well
from
the
Gemara
point
of
view.
What
I've
done
is
reading
some
Python
notebooks
that
start
to
compete,
some
of
the
matrix
from
scratch
I
mean
using
Perceval
directly
to
the
repository
and
producing
some
of
the
matrix.
This
has
been
stalled
for
like
two
or
three
weeks,
because
I
could
have
borne
now
in
doing
the
samurai
aspect.
B
C
We
have
a
in
the
auger
system.
Now
we
have
a
dashboard
that
actually
indicates
which
of
the
metrics
that
are
specified
in
the
metrics
repository
and
we're
looking
actually
at
the
workgroup
version
of
the
metrics,
the
worth
of
growth,
maturity,
decline
of
working
groups,
version
right
now,
and
also
a
clone
of
diversity,
inclusion,
kind
of
blending
them
together
and
so
that
you
can
actually
run
a
metric
status
page,
which
I
was
trying
to
bring
up
right
now.
But
somebody
broke
the
build
last
night.
C
But
so
you
can
see,
and
maybe
by
the
end
of
the
call
I'll
figure
out
how
to
get
it
running,
but
you
can
see
actually
how
implemented
different
metrics
are
and
then
what
experimental,
metrics
that
are
not
even
specified
yet
but
have
been
discussed
in
different
contexts
are
implemented.
So
we're
trying
we're
trying
to
make
that
that
connection
between
excuse
me,
the
metrics
that
are
specified
transparent
in
this
one.
Before
okay.
A
So
the
idea
is
the
D&I
workgroup
has
specified
particular
metrics
that
can
be
pulled
from
trace
data
which
augur
can
get
or
the
growth
maturity
and
decline.
Workgroup
likewise
has
specified
particular
metrics
and
augurs.
Would
it
provide
a
display
for
DNI
and
it
does
via
or
growth
maturity
and
decline
like
two
different
tabs.
B
B
A
At
the
end
of
at
the
end
of
the
line,
whether
it's
represented
via
a
panel
or
whether
it's
through
a
report
that
produces
a
PDF
you've,
still
got
to
push
the
button
on
that
piece
of
software
of
it,
I
think
just
kind
of
continuing
to
keep
those
things.
You
just
things
to
run
my
mind,
keeping
the
the
workgroups
aligned
to
the
software,
it
ending
up
being
the
real
the
real
trick
here
and
then
the
metrics
that
huge
activity
metrics
list
that
we
keep
over
on
the
metric
side
of
things.
A
Those
are
just
that's
just
kind
of
a
kind
of
a
curated
laundry
list
of
things
that
may
or
may
not
be
relevant
to
the
work
groups.
You
know
what
I
mean
so
I,
don't
I,
don't
know
that
any
of
the
tools,
whether
it's
augur
or
more
Lab,
necessarily
have
to
point
to
the
metrics
committee
list
of
metrics
I.
Think
it's
more
important
that
they
point
to
the
work
group,
the
kind
of
a
curated
for
smaller
set
of
metrics
that
are
important
for
those
work
groups.
Ya
know.
C
Just
gonna
say
I
think
in
growth,
maturity
and
decline.
We've
we've
definitely
started
to
see
the
the
need
for
that
and
there's
I
think
a
good
deal
of
work.
That's
starting
to
happen.
I
know
that
for
this
week
we're
going
to
talk
about
metadata
that
needs
to
be
around
each
of
the
metrics
and
how
important
that
is,
but
but
I
think
also
getting
down
to
what
each
of
the
metrics
actually
means
in
its
quote.
C
Unquote
standard
form
is,
is
I,
mean
I'm,
not
terribly
surprised,
but
I
think
it's
coming
to
require
a
bit
of
discussion
and
I.
Think
there's
some
work,
putting
those
specifics
back
into
the
metric
markdown
and
definition
that,
once
it's
implemented,
that
that
there's
more
work
to
do
there,
because
that
just
an
implementation
simply
raises
more
questions.
It
seems
one.
B
Of
the
examples
is
when
we
are
starting
to
implement
in
manuscripts.
The
matrix
is
discussing
with
an
ethical
man
about
I'm,
serious
and
results,
and
absolute
is
going
to
be
very
useful,
because,
basically,
what
we
are
doing
is
implementing
classes
that
can
be
produced
in
a
little
time,
serious
or
the
final
metric
in
a
snapshot
or
stuff
like
that
which
is
or
tries
to
be
exactly
what
we
were
discussing,
but
now
with
some
implementation
code
to
this
case.
B
A
That
sounds
great
okay,
cool
yeah,
cuz
I.
Think
you
know
when
we
when
chaos
first
started,
it
was
kind
of
just
it
was
just
kind
of
getting
the
software
in
place.
What
is
the
software,
obviously
with
grimore
lab
and
time
GH
data
in
it
and
then
just
trying
to
identify
what
metrics
people
like
to
see,
but
these
workgroups
have
really
formed
into
this
kind
of
critical,
critical
juncture
deployment
and
so.
B
C
A
C
Essentially,
what
l
look
at
growth,
maturity
and
decline,
because
it's
the
most
well
developed
right
now,
but
this
is
an
auger
status
screen
which
shows
a
back
end,
which
would
indicate
that
there's
an
endpoint
available
and
then
front
end
which
indicate
there's
a
visualization
available
for
each
of
these
metrics
that
are
defined
by
the
metrics
committee
and
I
will
say
that
some
of
the
definitions
are
not
yet
mature.
They're,
very
they're,
sparse
in
the
way
that
they're
defined,
but
we've
implemented
them
as
we
interpreted.
What
is
there
in.
C
Right
so
I
think
a
lot
of
them
leave.
Leave
leave
are
somewhat
open
to
interpretation,
yet
I
mean
they'll
always
be
open
to
some
interpretation,
but
I
think
that
that
window
is
pretty
big
right
now
in
most
cases
and
and
we
just
show
which
ones
are
implemented
at
the
back
end
in
front
end.
So
like
in
the
case
of
closed
issue
resolution
duration,
we've
got
a
back-end
API,
that's
built
on
top
of
the
gh.
Let
me
see
here
each
joint
Plus,
which
is
sort
of
our
custom
yeah.
C
What's
that
what's
use
a
custom
view
of
that
we've
created.
Excuse
me
off
the
gh
torrent
data.
Okay,
so
make
it
run
faster.
Basically,
I
mean
we
could
pull
it
from
gh
to
R,
but
it
would
be
very
large
query
and
then-
and
you
can
see
which
ones
are
implemented
not
implemented,
and
this
is
an
automated
sort
of
thing
and
if
it's
undefined
somebody
has
mentioned
it,
but
it's
neither
defined
and
are
implemented
yet
so
what
it?
What
is
undefined
mean
here?
C
A
C
A
C
C
Yeah,
so
it's
pretty
close
to
up-to-date,
because
most
of
the
work
is
happening
in
the
working
groups
right
now
and
we're
trying
to
we're
trying
to
keep
up
with
those
changes,
but
because
the
working
groups
are
happening
across
repositories,
it's
a
little
bit
of
emerging
thing.
You
have
to
do
okay,
and
you
can
see
just
you
know
like
there
are
some
like
value
metrics
that
are
enumerated,
but
they're
not
yet
defined,
and
then
we
have
down
here.
C
We
have
this
long
laundry
list
of
everything
yeah,
but
then
this
is
the
experimental
are
things
that
actually
aren't
defined
in
specific
places
in
in
the
metrics
committee.
You
wake
will
be,
but
we
have
we
have
back-end
api's
or
things
that
that
provide
those
metrics.
Well,
these
are
just
kind
of
your
own,
your
own
thoughts.
Well,
they
come
from
discussion
with
people
they
just
haven't
made
their
way
into
having
a
metrics
definition.
Okay,.
A
C
A
C
A
E
E
D
A
Well,
this
list
that
Shawn
here
that
shawn
has
here
in
augur
for
diversity
and
inclusion,
is
the
list
that
we
kind
of
informally
came
up
with
before
the
words
formed.
That's
right.
This
is
like
six
months
ago,
and
so
this
is
just
kind
of
based
on
our
own
reflections
and
just
trying
to
get
some
big
scary
well
trying
to
get
some
semblance
of
order
to
these
categories.
The
diversity
and
inclusion,
category
and
I
tried
to
click
on
Shawn's
link
there
because
he's
sure,
sorry,
anyway,
in
treating
organizations.
A
A
B
E
A
So
I
think
that
those
goal
quest
to
use
the
question
approach
to
turn
this
use
the
gqm
approach,
so
I
say
at
one
point
the
work
that
the
DNI
workgroup
has
come
up
with
those
the
gqm
metrics
that
you
have
that
should
essentially
override
what
we
have
on
the
metrics
list.
Their
shine,
that's
my
thinking,
because
that's
the
DNI
Group
they're,
the
ones
that
have
come
up
with
what
they
believe
to
be
important,
they're,
the
ones
that
are
working
diligently
to
figure
out
what
metrics
are
really
important
in
the
first
list.
A
A
C
Yeah,
the
metrics
I've
read
over
on
diversity
and
inclusion,
team
or
project
group
repository
or
I
think
at
this
point
not
yet
any
there's
not
yet
anything
that
could
be
produced
as
a
metric
from
trace
data.
This
point,
the
the
goals
are
at
a
higher
level
and
and
could
not
be
generated
from
trace
data.
Okay,.
A
C
I
think
you
know
one
of
the
questions.
One
of
the
things
that
I
think
might
be
important
is
if
the
diversion
inclusion
working
group
decides
that
these
metrics
that
have
been
identified
are
no
longer
diversity.
Inclusion,
metrics,
I,
think
it's
it's
clear
that
these
metrics
remain
important
for
projects
and
are
utilized
in
different
ways,
and
so
we
don't
want
to
lose
these
metrics
that
already
exist.
We
want
to
put
them
somewhere
because
I
know
a
lot
of
the
tools.
C
I
look
at
are
looking
at
new
contributors,
organizational
level
contributions,
maintainer
x'
and
all
these
all
these
sort
of
other
forms
of
diversity
are
things
that
community
managers
do
look
at.
In
addition
to,
however,
the
committee
might
operational-
or
maybe
the
committee
will
include
these
things-
I
don't
know
I
just
this
thing.
We
don't
want
to
lose
these
measures,
because
we
know
that
they're
used
yep.
D
A
A
Okay,
this
is
helpful,
at
least
in
my
mind,
so
Georg.
The
idea
is
potentially
at
least
bring
these
forward
to
the
work
group
as
a
way
to
understand
diversity,
inclusion
through
trayvis
data
and
then
ultimately,
the
diversity
and
inclusion
of
work
group.
Would
it
include
some
low
level
metrics
that
could
be
obtained
via
trace
data
such
as
these
and
some
that
just
absolutely
could
not
be
obtained
through
trace
data,
which
is
perhaps
through
interviews
or
surveys,
but
other
methods
that
are
required
to
understand
those
people
right.
E
Right
that
is
absolutely
correct,
and
if
you
follow
the
link
that
I
post
in
the
chat
to
the
project
places
there,
you
can
see
that
within
each
goal
we
then
have
these
actual
metrics.
When
you
you're
on
the
documentation
link
there,
you
get
an
idea
for
where
these
metrics
will
live,
and
this
is
per
than
in
category
four,
we
will
have
quantitative
meta
data
metrics.
E
E
E
F
A
A
So
when
I'm
looking
at
this
overall
repository
here,
you've
broken
down
this,
these
highest
level
items
within
there,
each
within
their
own
markdown,
so
goal
event
has
contribution
events,
governance,
leadership,
so
on
and
so
forth,
and
so,
if
I
click
on
governance
gives
me
the
lower,
so
that
name
category
the
name
column
is
the
actual
lower-level
metric
correct.
Yes,.
E
A
A
And
this
goes
to
the
point
of
kind
of
keeping
everything
together.
I
think
this
is
where
a
lot
of
effort-
maybe
this
is
some
effort
that
I
need
to
put
in,
is
just
trying
to
make
sure
everything,
kind
of
stays
together
and
I
understand,
there's
gonna
be
periods
as
Georg
is
pointing
out
where
there
is
gonna,
be
a
little
bit
of
four
kings.
C
We
I
think
it
wouldn't
mean
I.
Imagine
because
it's
not
I
that
would
do
it,
but
I
think
it
wouldn't
be
hard
to
to
have
a
reference
to
the
pitar
gia
Orgrimmar
lab
implementation
of
these
metrics
as
well.
Like
perhaps
I
mean
it
might
not
be,
is
mmm-hmm
I
mean
way,
I
have
to
conceptualize
what
that
link
looks
differently.
Mm-Hmm.
D
C
I
think
that
there's
there's
almost
certainly
representations
of
many
of
these
metrics,
most
of
them
in
in
grimore
lab,
and
it
would
be
good
to
see
that
alongside
bogger,
just
just
because
I
would
I
think
give
us
a
more
full
view
of
the
overall
chaos
effort.
I
mean
this
was
this
was
clearly
and
I
think
transparently,
just
the
auger
teams
way
of
trying
to
keep
track
of
this.
But
what
we
did
here
could
be
expanded.
Okay,
we're
just
meeting
reading
metadata
from
different
places.
B
Something
similar
at
least
for
manuscript,
so
that
when
we
produce
a
PDF
report,
we
can
now
which
of
the
metrics
in
cows
are
represented
in
it,
using
basically
your
format.
So
I
like
how
you're
representing
this
because
I
the
way
you
can
very
quickly
now
which
part
of
the
matrix
are
implemented
on
I
mean
which
one
there
is
working
progress
and
so
on
and
so
yeah
and
that's
super.
A
C
B
C
B
Means
that
we
decided
to
start-
let's
say
from
the
beginning,
to
the
end,
trying
to
have
at
least
some
of
the
metrics
implemented
from
scratch.
I
read
a
couple
of
notebooks
upon
notebooks
for
some
of
the
metrics,
pretty
simple
ones
like
number
of
commits,
so
in
the
differences
like
the
account
Mars
commits
or
not
all
to
account
commits
are
empty
or
that
kind
of
staff
so
that
we
can
see
and
actually
running
the
notebook
on
any
repository.
The
difference
is
in
metrics
at
the
same.
B
C
A
B
In
general,
but
in
some
cases,
when
we
look
at
them,
we
realize
that
we
need
either
to
define
or
chain
is
like
some
of
those.
If
you
go
to
the
repository
to
the
gym
developer
to
Tory,
you
can
see
the
current
setters
and
you
can
see
how
for
Sam
off,
they
were
metrics
ready
to
pull
requests.
We'd
have
to
split
them
in
either
membrane
3,
I
think
because
of
the
definition
didn't
match
the
sector.
What
you
find
in
the
repository
is
now.
C
Diversity
and
inclusion
that
just
merely
primarily
reflects
the
growth,
maturity
and
decline.
Our
metric
tight
is
a
metric
category.
That's
been
discussed
for
quite
a
while,
and
the
diversity
and
inclusion
sort
of
instrumentation,
if
you
will,
is
a
very
recent
discussion.
You
know
very
recent
thing,
maybe
it's
not
five
years
ago
at
the
most
now.
B
That
was
way
different
because
stadia
the
basically
on
GNB
is.
We
are
not
going
to
discuss
why
this
matrix
are
useful.
Of
course
anybody
is
welcome
to
come
and
say,
I
find
this
metric
useful,
or
this
is
more
useful
if
you
look
it
this
way
or
whatever,
but
there
has
been
a
lot
of
work
on
that.
So
the
basic
idea
is:
let's
keep
the
matrix
in
general
as
they
are,
and
now,
let's
that's
about
the
details
so
how
to
compute
them
so
that
we
can
concur
with
the
canonical
way
of
completing
all
the
metrics
and.
A
Makes
it
that's
super?
This
is
really
helpful
conversation
for
me.
Thank
you,
so
I
think
in
the
case
of
diversity
and
inclusion,
I
think
one
of
the
things
to
keep
on
the
back
of
your
mind,
Georg
or
folks
that
are
in
the
DNI
work
group,
is
to
take
the
work
that
you've
done
and
make
sure
that
that's
parallel
with,
what's
actually
over
at
the
metric
side
of
things,
I
understand
that
you
there's
work
to
do
to
get
that
done,
but
keeping
those
two
things
aligned
I
think
from
the
growth
maturity
and
decline
perspective.
A
It
sounds
like
it's
it's
less
about
keeping
those
two
things
in
line,
it's
more
about
actually
contributing
back
to
that
activity
list
to
make
sure
that
the
definition
of
these
low-level
metrics,
like
code
commits
I
just
picked.
One
is
defined
properly
in
that
in
the
markdown
that
is
so
Sean.
If
you
like,
commit
on
Lincoln
click
on
code
commits
right
now,
yeah
or
any
one
of
those
I
don't
care
commits.
A
A
C
It
does
I
think
I.
Think
one
of
the
one
of
the
aspects
of
this
is
that
we're
probably
going
to
have
to
do
like
it'll
be
a
little
bit
of
an
I.
Don't
it's
probably
just
a
detail,
but
we're
gonna
have
to
separately
fork
the
metrics
repo
and
edit
it
and
put
these
files
in
just
because
the
current
growth
minute
reading
decline,
repo
doesn't
include
the
other
categories,
so
yeah,
that's
more
good
erase
them.
If
we
did
a
pull
request.
A
B
C
C
B
Okay,
I'll
go
to
the
route
rep
own
right
and
now
click
on
examples.
Look
at
the
with
me
and
there
are
several
notebooks.
Are
click
on
code
commits
at
the
beginning
of
example,
saying
whatever,
then
you
have
code
meets,
which
is
the
only
one
which
is
currently
accepted.
This
is
a
notebook
getting
actual
data
from
an
actual
repository.
B
Is
the
most
interesting
one?
So,
for
instance,
in
this
case
maybe
I
don't
know,
maybe
we
are
going
to
consider
old,
commits,
ignoring
merge,
commits
and
considering
only
commits
a
touch
of
file,
for
instance,
and
there's
going
to
be
a
process
definition
that
we
are
going
to
say,
but
in
in
the
same,
at
the
same
time
we
can
also
say
well,
maybe
for
your
specific
project.
It's
more
interesting
that
you
have
intercom
most
commits
because
of
this
and
this
so
that
this
can
be
lets.
B
Say
they
tailored
enough,
so
that
one
can
realize
how
to
use
the
metrics
even
for
doing
an
independent
implementation
of
this,
for
instance,
which
was
the
idea,
because
if
you
remember,
we
are
going
to
provide
a
kind
of
a
canonical
implementation,
but
anyone
can
implement
it
in
some
other
ways.
But
the
idea
would
be
what
numbers
should
be
the
same,
because
the
definition
should
be
the
same.
So.
A
B
What
is
picked
in
Vancouver
is
that
we
go
through
these
notebooks
and
this
cache
unsettle
on
wall.
For
now,
at
least,
this
is
going
to
be
the
definition
for
this
indiscretions
and
as
well
having
after
all,
users
of
the
matrix
is
quite
interesting,
because
the
actual
users
of
the
matrix
and
admirers,
for
instance,
can
say
well
for.
C
B
B
B
A
D
A
C
Think
this
code
is
the
intention
issues
to
actually
implement
this
code
or
as
a
or
is
the
intention
really
to
have
the
code
represent
for
people
a
concrete
implementation
that
helps
them
to
differentiate
between
these
naive
versions.
The
empty
commit,
ignoring
versions,
the
only
non
merge
commit
I
mean.
Essentially,
these
are
different
ways
of
looking
at
commits.
B
Difficult,
the
idea
is
that
by
writing
the
code.
You
are
very
specific
and
this
is
exactly
how
we
do
that,
because
in
English
you
know
in
some
cases
you
know
the
details,
so
they
have
to
of
code
and
of
course
any
implementation
could
implement
in
many
other
ways,
but
the
idea
is,
if
they
implement
it
right,
there
were.
Some
should
be
the
same,
because
that
you
know
the
final
counts
would
be
exactly
the
same,
and
that's
it.
These.
A
Types
of
contributions
not
not
commits,
but
the
type
of
the
types
of
contributions
that
you're
showing
here
in
this
notebook
super
helpful
I.
Think
it's
really
really
descriptive,
because
for
a
lot
of
a
lot
of
the
just
singular
metrics
that
we
have,
we
kind
of
have
just
a
high-level
definition.
You
know
a
code
commits
these
are
commits
that
go
into
the
code
and
there's
much
to
it.
But
but
then
we
could
say
for
for
detailed
description,
please
source
below
and
I
think.
This
would
really
give
no.
B
B
I
know
in
the
second
of
three
a
formula
you
probably
would
be
saying
one
of
the
implementations
in
the
notebook,
the
one
that
we
decide.
This
is
a
vital,
let's
say,
and
maybe
we
also
need
to
include
some
other
comments
or
whatever,
which
is
something
like
other
ways
of
understanding
this
metric
and
I'm,
talking
about
in
English
about
the
different
possibilities
and
just
link
in
the
notebook
for
the
tables,
so
that,
if
you
are
interested
in
this
other
ways
of
understanding
political,
not
oh,
can
you
see
the
details,
but
it.
A
B
D
A
We
just
want
to
embed
embed
that
notebook
here
saying
so
you
have
your
page
that
you
showed,
which
was
the
the
really
rich
understanding
tonight,
clay
finals,
yeah,
all
right.
She
put
her,
have
notebook
yeah?
What
do
you
want?
At
least
my
first
thought
was
that
we
have
this
markdown
file,
which
is
called
code
commit
CMD.
We
have
a
description
which
is
pretty
generic.
Some
use
cases
I
think.
C
I
think
so
I
think
he's
just
one
I'm
going
to
try
to
do
this
fast
here.
I
think
his
point
was:
if
we
go
to
this
example,
notebook
and
yeah,
he
would
say
we're
gonna
decide
just
only
non
merge
commits
as
the
definition
that
we're
gonna
use
for
pogrom.
It's
not
saying
it
is
I'm
just
using
an
example
right,
and
so
you
would
essentially
bring
this
this
probably
this
code
in
this
text
over
to
the
markdown
document
under
the
formula
IPC.
So
the
formula
would
be
you
know
here.
C
It
is,
and
maybe
I'll
indicate
it's
in
Python,
and
perhaps
there
would
be
a
link
to
this
notebook
to
see
more
options
or
to
see
the
discussion
or
the
you
know,
the
perspectives
that
were
considered
or
something
here's
the
notebook
link,
I,
don't
know
what
you
think
is
that
what
you
meant,
hey
shoes.
You
really
want
to
know
well,.
B
B
Do
you
see
the
different
options
that
you
have
put
a
matrix
and
then
you
can
decide?
Okay.
This
is
the
more
sensible
one
in
this
context.
So
that's
why
those
are
like
two
views
and
my
impression
is
that
the
notebooks
are
mainly
supporting
information,
so
they
are
not
really
needed
for
understanding
what
the
metric
is
about.
It's
only
needed
if
you
are
implementing
or
here
discussing
about
the
details
and
that's
why
let
me.
A
A
Yeah
there
we
go
yes
hole
the
list
of
like
one,
two,
three,
four,
five,
six,
seven,
whatever
the
sub
headers
are
on
here.
This
is
always
this
is
always
kind
of
a
moving
target.
Keeping
this
as
simple
as
we
can
just
listening
to
talk,
hey
soos.
You
know
that
we
have
a
very
high
level
description.
I,
don't
know,
I.
Think
I'll
need
to
continue
to
think
about
this
as
to
what
we
might
think
having.
C
B
In
any
case,
it
is
to
have
some
of
the
metrics
completely
written
in
this
format,
and
then
this
caste,
and
maybe
we
can
find
out
the
position
of
the
word
format
that
we
are
missing
something
or
there
is
too
much
information
whatever
and
then
we
can
discuss,
but
it's
easier
to
discuss
on
a
specific
cases
than
just
discussing
them.
You
know
on
the
wood,
okay,
there
you
said
that.
E
A
C
B
So
I
think
that
second
check
them
for
at
some
point
needs
to
be
refine.
It
in
these
are
the
actual
metrics
that
we
propose,
because,
right
now,
my
impression
is
that
you're
discussing
metrics
that
could
be
used
and
at
some
point
you
need
to
say
well.
These
are
the
real
metrics
that
we
want
to
suggest
section.
C
Four
looks
like
almost
a
collection
of
metrics
yeah,
the
model
like
if
I'm
just
to
go
back
to
the
one
we
were
looking
at,
where
there
were
four
or
five
different
implementations
of
code
commits
this
might
be
code.
If
I
was
to
put
code
commits
here,
you
might
actually
list
in
this
model.
The
four
or
five
specific
types
of
implementation
is
that
am
I
understanding
what
the
intention
here
is.
Georg,
yes,.
E
B
C
You
it's
a
this
is,
but
it's
I
think
what's
interesting
is
that
it's
saying
we're
not
picking
a
specific
definition
for
documentation,
we're
saying
or
let's
say,
there's
11
ways
to
look
at
how
to
measure
documentation,
and
here
are
samples
of
those
11
ways.
And
similarly
we
would
say:
there's
these
four
or
five
ways
to
look
at
code
commits
direct
examples
of
those
and
here's
a
link
owed.
C
C
B
That
I,
like
when
this
kind
of
stuff
is
that
in
the
DNI
group
they
are
starting
from
what
do
we
need,
which
is
something
that,
in
the
case
of
MD,
you
were
discussing
for
years,
but
maybe
it's
not
captured
in
documents
like
this
one.
Well,
you
say
in
the
end,
we
want
activity
because
of
this
and
these
goals
that
we
have
and
then
activity
we
can
measure
it
with
commits
and
some
other
staff.
B
So
this
kind
of
files
that
you
are
so
in
right
now
on
the
screen
seems
like
this
is
why
we
need
the
ideas,
and
these
are
the
ways
that
we
could
measure
it
in
the
case
of
MD.
We
have
the
ways
we
can
measure
it,
and
we
have
some
details
about
why
that's
useful,
but
we
don't
have
something
like
this
capture
or
everything
is
together,
and
this
is
the
reason
why
activity
is
important,
or
maybe
we
have
it
somewhere,
but
not
in
the
collective
with
the
matrix.
B
That's
something
that
we
can
also
reflect
on,
or
maybe
we
can
discuss
him
Coover,
because
I
like
this
way
of
say
starting
from
the
user
needs.
You
had
anything
on
matrix,
yes
in
the
end
is
like
the
matrix
are
done,
and
the
discussion
on
why
those
metrics
are
done.
The
rationale
is
maybe
lost
in
this
discussion
that
you
have
had
for
years.
Yeah.
A
B
May
vary:
listen.
Maybe
we
can
try
to
write
this
level
to
maybe
we
can
talk
him
and
Google
about
that
to
try
to
write
this
level.
Forty
MD
because
I'm
sure
that
you
have
it
in
your
minds,
because
you
have
been
working
on
this
for
a
long
time.
We
maybe
we
can
have
these
reading
from
scratch,
but
from
from
your
ideas,
I
mean
note
for
spots
with
your
ideas
and
linked
into
the
matrix,
so
that
we
have
two
more
similar
structures
that.
A
B
I'm
sorry
I'm
not
being
able
of
joining
on
Thursday
to
the
gym
the
median
on
not
on
this
of
the
next
Thursday
either
because
basically
I'm
leaving
tomorrow
until
Thursday
next
week,
right
so
I
can
I
will
try
to
submit
something
before
living
on
all
the
way
I
will
what's
up
when
I
come
back
to
the
next
meeting.
Okay
I.