►
From YouTube: GMD Weekly Meeting - 8.24.2018
Description
CHAOSS Growth-Maturity-Decline weekly meeting
A
You
need
for
its
meeting
after
the
meeting
so
that
we
get
a
note
of
it
in
the
future
and
my
idea
is
to
do
that
in
a
separate
file
at
some
time,
because
right
now
it's
in
the
with
me,
but
at
some
point
we
can.
We
can
have
a
separate
file.
So
if
you
agree
keeping
issues,
we
take
notes
or
somebody
else
can
do
it.
If
he
is
not
available
and
then
the
idea
is
to
put
decisions
and
everything
in
the.
B
A
A
B
A
Related
to
some
metrics-
and
this
is
let's
say
the
other
way
around-
so
it's
when,
for
instance,
Ray
is,
is
right.
Now,
writing
with
me,
one
of
those
cases
and
Ray
is
interested
in
finding
out
or
what
happens
with
first
contributors
and
he's
interested
in
see
how
they
are
coded
being
cultivated
and
how
they
can
improve
the
bushes.
A
B
And
I
mean
I
think
you
know.
My
reflections
on
that
are
in
the
discussion
in
the
online
forum
was
that
the
DNI
group
is
using
a
Google
Doc
to
perform
the
same
function
in
their
group
if
I'm
right,
so
they
don't
have
the
use
cases
in
the
repository
and
I
think
we
also
had
an
email
exchange
about
characterizing.
Some
of
these
use
case
like
items
inside
of
the
like
a
blog
post
or
something
like
that,
and
so
my
only
question
about
putting
them
in
the
repository
and
treating
them
like
code
is.
Does
that
limit?
B
The
visibility
of
an
evolving
discussion?
Is
that
and
I
guess:
I'd
like
people
on
the
Chaos
Enterprise
in
general,
to
like
know
that
if
they
want
to
understand,
they
want
to
know
other
use.
Cases
for
the
working
groups
are
that
if
we're
going
to
follow
it
like
we've,
we've
changed
things
to
follow
the
pattern
that
the
night
follows.
So
we
should
follow
it
all
the
way,
because
the
point
is
to
be
consistent
and
if
I'm
understanding
what
they
do,
they
don't
have
them
in
the
repo.
B
And
so
my
question
is
really
sort
of
my
question
about
whether
we
should
do
that
or
not
is
entirely
around.
How
do
we
do
this
in
a
way
that
makes
it
so
that
every
working
group
looks
the
same
from
the
outside?
So
that's
somebody
coming
to
Kass
can
find
the
thing
that
they're
looking
for
regardless
of
the
so.
C
A
Looking
for
how
to
do
this
and
they
are
finding
some
ways-
and
maybe
we
can
find
some
different
ways
and
maybe
after
some
experience
we
may
try
to
coordinate
that.
So
in
some
cases
we
are
already
converging
in
some
others,
maybe
not
yet,
because
we
don't
have
enough
enough
expertise,
bad
if
you
prefer
to
go
with
Google,
Docs
or
something
I
do
I
honestly,
don't
know
what
they
are
doing.
Yeah.
C
A
To
do
that,
let's
do
my
main
concern.
There
is
the
other
way
around
now.
I
would
like
people
come
into
the
repository
and
finding
everything
they
need,
and
there
is
no
way
of
passing
on
a
Google
Doc,
for
instance,
while
you
have,
you
can
have
it
in
a
pull
request.
Bad
I
am
ready
to
experiment
anything
we
want
and
then
evaluate
later.
My
concern
here,
in
fact,
is
that
maybe
we
are
losing
too
much
time
on
procedures
and.
B
Exactly
what
am
I
gen
items
for
today?
Okay,
yeah
I,
just
want
it
like
I'm
in
the
working
group
and
I'm.
This
has
moved
so
much
I'm
having
a
hard
time
knowing
where
things
go
and
what
goes
where
like
I'm
in
the
working
group
like
you
and
I,
are
the
most
active
members
and
and
I'm
got
cut
off
from
last
meeting,
but
the
more
this
involves
the
more
confused
I
get.
Okay,
it
out.
C
B
We're
capturing
everything
it's
just
like:
okay,
the
I
guess
the
use
cases,
maybe
I'm
I,
guess,
let's
just
like
I'm
I'm,
reticent,
to
contribute
anything
right
now,
because
I'm
not
sure
what
goes
where
all
of
this
moving
around
has
just
made
it
harder
for
me
to
follow,
because
I
thought,
on
the
one
hand,
at
the
I
thought
the
value
system
we
were
employing
was
that
we
were
just
gonna,
do
at
DNI
was
doing,
and
so
it
seems
like
we
went
so
far
to
do
it.
Dni
is
doing,
and
then
we
now
we're
stopping
and
I'm.
B
B
B
And
I
guess:
I'm
talking
this
through
and
I'm
thinking
about
when
I've
had
use
cases
written
out
in
a
repository
before
they've
followed
a
certain
structure
right,
like
I,
include,
there's
like
seven
or
eight
headings:
I'd
have
to
pull
out
old
examples
to
come
up
with
them,
but
actually
I
think
chaos
began
with
some
high-level
use
cases
that
had
most
of
those
headings
and
so
we've
had.
We
can
begin
organizing
this
around
some
use
cases
and
I.
B
Think
now
that
we're
into
the
details,
the
use
cases
are
probably
more
elaborate
and
do
we
want
to
follow
a
format
and
if
we're
experimenting,
we
probably
don't
want
to
specify
a
format
and
I
guess
if
we
want
to
do
it
in
the
repository,
then,
where
do
we
I?
Guess
I?
Guess:
that's
okay,
I
mean
putting
it
in
the
repository.
Is.
B
C
B
A
A
Again,
what
I
only
tried
to
do
is
to
write
a
procedure
and
that's
what
it
is
in
the
pool
request
and
the
procedure
is
based
on
good
records
and
files,
bad
if
you
prefer
to
try
with
something
better
than
Google
Docs
ham.
Something
knows
I'm
more
than
happy,
so
I'm
interesting
having
the
use
cases
and
try
anyway
to
have
them
and
if
you
feel
like
Google,
Docs
or
whatever
is
better.
So,
let's
try.
Let's
try
for
a
couple
of
months
and
then
we
can
decide
so
I,
don't
mind
the
only.
C
B
A
For
now,
I'd
like
to
start
with
a
couple
of
them
and
see
what
happens
and
at
some
point
we
need
to
instructor
them.
But
for
me
it
doesn't
make
sense
to
try
to
structure
them
right
now,
because
we
didn't
know
what's
going
to
be
in
so
I
have
the
idea
they
need
to
have
a
goal.
They
need
to
have
questions,
they
need
to
have
metrics
yeah,
probably
they
need
to
have
a
description,
and
all
this
has
been
used
and
stuff
like
that.
A
But,
honestly,
right
now,
I
don't
know
more
so
I'm,
it's
not
in
the
world
with
right
in
one
and
with
another
one.
Somebody
from
over
and
in
both
cases
I
will
I
was
intending
to
do
it
in
an
open
way
so
that
people
can
come
and
see
the
requests
and
comment
on
it
and
say:
maybe
you
need
some
and
some
fields.
So
maybe
you
need
to
order
to
this
instructor
or
whatever,
so
that
we
can
this
kind
of
this
castle
on
the
pull
request.
A
B
Okay,
so
you've
created
the
I,
say:
you've
created
the
directory
here:
let's
try
it.
Let's
not
I
understand
now
a
little
bit
better,
what's
happening,
I
think
I.
Think
our
intention
of
the
process
being
the
same
as
DNI
isn't
quite
I'm,
not
I,
really,
don't
think
it's.
What
we're
doing
I
mean
I.
Think
we've
made
some
changes
that
make
us
more
like
DNI,
but
I
do
think
that
we're
following
a
distinct
process
that
somebody
from
D
and
I
couldn't
walk
into
this
repository
or
our
working
group
and
know
where
things
are
you.
C
B
A
I
feel
like
both
of
us
need
to
be,
like
the
other
I
mean
they
need
to
be
like
s,
and
we
need
to
be
like
them
once
we
have
enough
enough
experience
to
know
what
works,
but
that's
why
I
was
saying
if
the
user
right
in
the
use
case,
or
mainly
right
in
the
use
case,
is
more
comfortable
with
Google
Docs.
We
could
load
that
to
in
at.
A
When
the,
when
the
document
is
ready,
I
mean,
with
everybody,
got
the
comments
and
everything
we
can
damp
that
into
file
easily.
So
it's
it.
That's
not
a
a
problem.
We
can
even
include
that
into
the
procedure
or
wait
until
if
somebody
asks,
because
the
thing
is
to
make
it
easy
for
contributors,
in
this
case
people
working
with
metrics
or
whatever,
to
write
the
use
cases.
So
we
can
start
with
pull
requests
and
files.
We
can
say
in
the
same
file,
if
you
prefer
to
use
Google
Docs,
please
do
or
whatever
oh
yeah.
B
A
So
this
is
for
people
with
your
files.
If
you
want
to
watch
your
musical
dogs,
please
link
them,
provide
here
the
link
to
the
Google
Doc,
so
that
people
can
contribute
and
let
you
use
Google
Doc
in
Tosa
specific
case
and
at
some
point,
let's
mark
when
the
use
case
is
really,
and
in
that
case
I
volunteered
to
dump
it
into
a
file
in
the
room
into
the
repository,
so
that
we
can
have
everything
together.
A
B
C
C
B
C
C
Okay
and
I
think
I
took
maybe
the
idea
that
they're
supposed
to
be
the
same
a
bit
too
literally
no
I
think
it's
just
that
that
first
high-level,
look
at
the
repositories
with
the
focus
areas
is
really
not
very
consistent
and
then
kind
of
the
drill
down
on
the
particular
metrics
within
those
focus
areas.
That's
very
consistent,
but.
A
But
in
any
case,
I
think
we
should
converge
in
the
future,
maybe
a
bit
more,
but
we
can
discuss
this
after
experience.
So
after
we
have
some
use
cases
and
they
have
use
cases,
we
can
decide
at
some
point.
Well,
let's
use
this
structure
or
even
let's
allow
people
to
use
both
systems
because,
depending
on
the
user,
maybe
the
user
is
more
yeah.
A
Well,
we
think,
although
but
so
with,
github
or
wherever,
so
that
I'm
unhappy
with
trying
to
converse
in
the
future
as
much
as
possible,
so
that
repositories
are
at
as
a
small
equal
as
possible,
but
still
I
also
think
that
we
need
some
room
for
experimentation
because
they
are
basically
experimenting
and
we
are
spare
Amenti
too.
So
that's
it.
A
So,
as
I
come
closer,
if
you
are
happy
what
I'm
going
to
do
is
to
amend
my
pull
request,
they
stayed
in
this
thing
if
you
prefer
to
use
Google
Docs,
please
do
that
case,
just
link
to
the
document
and
tell
everybody
so
that
they
can
contribute.
Let's
use
Google
Doc
comments
for
the
contributions
right.
C
A
C
C
B
A
You
have
an
instructor
for
the
use
cases
we
can
start
with
it
too.
So
I
don't
mind.
I,
don't
have
any
specific
instructor
in
mind.
I
was
thinking
about
using
what
the
people
in
DNI
are
using
or
something
similar,
but,
in
my
mind,
as
I
said,
is
basically
goals,
questions
metrics
and
some
descriptions
in
the
middle.
So
but
if
you
have
some
in
plate
or
something
I'm
happy
to
use
it.
A
C
B
B
I
think
we
also
think
the
use
cases
need
a
space
for
expressing
something
about
temporal
aggregation
and
my
conversations
with
people
how
they're
thinking
about
actual
use
cases
has
to
is
really
fairly
grounded
in
how
frequently
they
have
to
report
and
in
most
cases
that's
monthly
and
I.
Think
if,
if
we're
getting
information
like
that
about
the
because
the
metrics
themselves,
technically,
don't
include
these
these
filters
or
or
parameters
in
them,
but
I
think
the
use
case
is
possibly
ought
to,
because
how
these?
How
these?
How
people,
who
are
the
primary
actors,
are
consuming?
B
A
Okay,
we
can
include
something
specific
for
that
or
we
can
or
we
could
use
nodes,
which
is
an
empty
field.
No,
no,
no
yeah
for
that
kind
of
stuff
I
mean
anything
which
is
not
in
the
in
the
template,
but
but
they
agree
in
many
cases
you
need
to
define
aggregator
or
something.
My
only
concern
there
is
I
was
trying
to
keep
this
to
the
let's
say
close
to
the
user,
not
close
to
the
people
thinking
on
metrics,
so
that
they
can
really
say.
A
B
A
C
B
A
Then,
for
the
rest
of
the,
let
me
check
it
for
the
rest
of
the
repository
I
mean
the
other
staff
that
that
we
want
to
do.
I
was
thinking
about
having
some
something
like
a
procedure
or
something
file
where
we
explain
how
to
contribute
could
be
also
contributing,
because,
right
now
we
are
starting
to
have
several
directories
and
people
can
get
a
bit
lost
about
how
to
contribute
and
would
loop,
usually.
B
A
A
C
A
C
A
A
A
B
C
A
A
Okay
and
then,
if
you
look
at
the
peers
in
the
in
the
repository,
there
is
still
another
one
which
was
producing
Danny
with
me
and
Alberto,
which
is
they
add,
more
details
to
finishes,
and
here
daily
awards
to
basically
refine
the
description
of
this.
So
the
description
of
this
specific
matrix
this
was
before
we
were
discussing
to
move
these
to
another
structure,
ending
move,
our
move
back
or,
and
everything
so
I
can
I
can
solve
the
conflict,
but
I
wanted
to
know
if
you'll
find.
A
This
is
that
the
right
moment
to
do
is
to
put
in
this,
because
my
impression
is,
we
can
still
work
at
both
levels
again,
even
when
we
want
to
go
top
level
top-down
sorry,
we
can
also
work
at
the
matrix
level
by
refining
them
a
bit
more.
What
do
you
think
this
is
request
yeah
and
I'm?
Not!
This
is
pull
request
number
of
the
number
number
20,
okay,.
B
A
A
So
it
is
more
like
if
you
look
at
it
what
what
Danny
mainly
did
was
to
refine
the
description
and
specify
a
bit
more
like
a
couple
of
cases,
since
we
are
talking
about
issues
and
issues,
don't
work
the
same
way
in
github
and
maxilla.
It
was
just
a
matter
of
defining
a
bit
more
in
the
specific
case
of
github
and
the
specific
case
of
axilla,
how
things
work
and
then
talk
a
bit
more
yes
about,
what's
mandatory
for
as
parameters,
so
things
that
you
need
calculating
or
computing.
A
So
it's
only
that
so
it's
trying
to
be
persist
on
what
we
consider,
for
instance,
as
a
closed
back
or
sorry,
a
closed
ticket
in
Bugzilla
right
right,
so
I
can
I
can
I
can
fix
the
conflict,
which
I
think
is
to
the
name.
I
can
check
that
and
grai
upload
people
requests,
but
I
wanted
to
check
whether
you
find
it
convenient
to
do
this
now
and
follow
on
working
with
all
the
matrix
to
refine
them.
This
way.
B
Wanting
to
pick
the
aggregation
period
and
also
I
think
yeah
I,
just
looked
at
I
found
what
they're
the
pull
request
was
and
I
added
a
comment
about
the
time
period
and
I.
Think
there's
always
this
question
about.
If
something
when
in
particular
goes
from
open
to
close
to
open
again,
essentially,
the
reopening
of
issues
can
confound
issue
metrics.
In
my
experience
and
but.
A
A
B
A
A
B
So
I
think
I
think
maybe
the
parameter
isn't
point
in
time
and
then
maybe
that's
it
wasn't
clear
to
me.
What
point
in
time
was.
This
is
actually
like.
This
is
the
day
I'm
running
the
report.
So
as
of
this
moment
in
time,
these
are
the
statistics,
mm-hmm
and
I-
guess
yeah,
just
maybe
a
little
bit
of
elaboration
about
what
point
in
time
is
defined,
as
this
is
the
time
for
which
the
snapshot
of
open
issues
is
computed.
B
B
B
A
What
I
mean
is
that
what
I
mean
is
maybe
you're
running
the
report
right
now,
but
you're
interested
in
how
many
packs
you
had
open
one
year
ago,
so
I'm
say
on
the
first,
because
you
want
to
compare
or
something
we
all
you
want.
You
know
every
month,
the
first
day
of
the
month
how
many
bags
I
have
open
over
time
right
and
in
that
case
point
in
time
is
every
first
day
of
every
month,
for
instance,.
A
But
in
any
case
saying,
if
you
find
it
appropriate
to
discuss
this
kind
of
stuff
now
we
can
follow
on
on
the
on
the
pull
request.
So
my
main
idea
was
to
to
just
raise
the
issue
whether
it
makes
sense
for
you
to
have
this
kind
of
discussions
right
now.
For
me,
it
has
that's
why
we
propose
it
appear.
No,
after
now
we
can
discuss
on
the
on
the
pier
itself,
if
you
want
so
no
problem
with
that,
so
that
the.
B
A
A
A
Whatever
I
don't
know
the
name,
that's
now,
but
I
think
it's
the
only
problem.
Yeah.
A
A
A
B
A
Now
I
remember
another
thing
that
I
wanted
to
command
this.
Maybe
we
should
have
a
description
of
what
we
consider
a
CMD
prominently
at
the
beginning
of
the
Whitney
file
for
the
repository,
and
maybe
you
could
do
that.
I
mean
mat
or
or
or
Orson
just
because
you
were
working
for
with
this
for
a
while
suggest
you
to
let's
say,
define
an
ax
scope
like
the
people
in
diversity
and
inclusion
are
doing.
You're
saying
this
is
the
kind
of
matrix
we
are
talking
here.
A
B
B
A
A
B
The
only
thing
I
wanted
to
bring
up
in
addition
to
what
we've
talked
about
is
it
would
I
think
we
we
might
be
getting
to
a
point
where,
to
keep
momentum.
Meeting
more
frequently
might
be
appropriate,
I'm,
okay,
trying
to
continue
to
work
every
other
week
right
now,
but
I
just
wanted
to
I
guess
raise
my
own
I
guess
for
the
way.
I
work,
it's
easier
for
me.
A
C
A
A
C
A
But
what
I
mean
is,
if
you
prefer
to
have
a
meeting
every
week.
Let's
do
it.
I
will
join
as
much
as
I
can
and
otherwise
it
can
be
the
minutes
and
come
under
command
line
or
whatever
so
I'm
happy
with
having
the
meetings,
if
you
prefer
and
still
I
would
like
I
would
try
to
join
as
much
as
possible.
I'll.
B
Be
here
every
week
you
know,
maybe
maybe
do
it
with.
We
could
do
it
similar
to
how
we
do
the
general
meetings,
where
it's
kind
of
an
open
forum
every
week,
and
we
don't
make
decisions
on
a
weekly
basis,
and
then
we
just
have
a
monthly
version
of
the
meeting
where
we
confirmed
any
decisions
so
that
you
don't
have
to
worry
about
missing
me
not
being
attuned
to
the
decision-making
process.
Hey
sis,
that's
fine
too,
so
about
yeah
I!
B
B
A
A
Let's
try
that
model,
so
I,
don't
mind
and
I
mean
a
couple
of
months.
We
can
discuss
whether
it
is
working
or
not.
So
that's
that's
fine
with
me
in
that
in
that
case
may
be,
the
deciding
meeting
should
be
the
last
one
in
the
month
so
that
we
do
it
before
the
first
decision
meeting
for
the
whole
group,
which
is
usually
the
first
choice.
B
B
A
B
A
A
B
A
A
You're
talking
about
the
27
right,
yep,
okay,
okay,
so
if
you
agree
it's,
what
would
basically,
he
could
do
is
basically
doing
something
similar
to
the
trace
of
an
pull
request,
but
for
the
two
in
the
immediate,
the
minutes
for
today
and
what
we
can
do
is
all
the
people
who
participated
yet
say
we
are
okay
with
that,
and
that
would
mean
that
the
minutes
are
running
Frank.
What
works
and.
C
C
A
B
C
B
A
A
B
C
A
C
A
B
C
B
C
Working
group
meeting
to
have
well
no
the
reality
is
I
mean
for
the
tools
that
are
being
considered
for
grimore,
lab
and
kagura.
Yeah
I
mean
they
have
limitations
right
so
I
mean
if
you're
gonna
be
using
facility.
There's
only
so
much
data.
You
can
pull
right
in
a
meaningful
way,
so
the
metrics
are
gonna,
be
in
those
regards
somewhat
limited
to
the
tools.