►
From YouTube: CHAOSS GMD Workgroup September 26, 2018
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
C
D
Don't
think
so,
or
at
least
I
didn't
say
it
in
the
Middle
East
I
think
that
we
have
one
topic
that
is
important
to
this
case,
but
I
don't
know
if
we
can
do
it
today
with
so
few
people,
which
is
how
to
work
just
as
I
commented
in
the
mailing
list,
I
don't
know
if
that
was
decided
in
a
minute
or
I
could
not
go
in.
If
that's
the
case,
that's
fine
with
me.
D
D
D
What
I
saw
is
that,
right
now
there
is
a
new
branch
in
the
matrix
repository,
which
seems
to
be
the
same
information
I
mean
the
same
data
as
the
main
branch
as
the
most
very
minor
modifications.
So
it's
like
coming
back
again
to
the
beginning,
because
if
you
remember,
when
we
move
to
the
repository,
we
moved
everything
it
was
not
directly
related
to
Jim
Dee,
so
I'm
a
bit
upset
I,
don't
know
what
to
do
honestly.
I.
C
D
C
Remember,
I,
actually,
don't
remember
that
decision
being
formalized
either
I.
Remember
it
being
discussed
in
my
notes:
I
had
it
being
discussed,
I
did
not
have
it
being
formalized,
however.
I
was
when
I
when
I
went
to
do
the
meetings.
I
was
told
that
the
decision
had
been
made
in
that
meeting.
So
perhaps
there
was
just
some
confusion
around
that.
Could.
D
Have
been
them
so
I
don't
know
if
it
is
better
to
just
consider
that
as
a
decision
and
try
to
oh,
like
that
for
some
walls
and
see
what
happens
or
wait
until
the
next
meeting,
where
maybe
sin
as
I
mean
especially
since
should
be
important
to
be
here,
I
think
so.
I
don't
know
if
we
could
maybe
talk
about
all
our
staff
and
leave
this
and
maybe
discuss
in
the
Middle
East
because,
on
the
other
hand,
is
yester.
C
I
think
there's
definitely
opposing
views.
I
think
there
are
people
that
would
like
it
to
be
a
branch
and
I
think
there
are
people
that
would
like
it
to
remain
as
a
separate
repo,
so
so
I
think
there
I
didn't
I,
think
you're
right
in
that
the
decision-
probably
it's
probably
not
a
matter
of
reopening
the
decision,
I
think
it's
probably
a
matter
of
that
the
decision
hasn't
been
made
yet
so
maybe
we
just
need
to
talk
about
it.
Some
more.
A
I
have
observed
this
conversation.
Is
that
it's
about
what
is
the
best
way
to
collaborate,
especially
because
the
growth
matron
decline,
workgroup
is
feeding
into
the
metrics
committee,
and
the
core
issue
with
repository
is
that
it
is
not
apparent
that
it's
only
a
fork
of
the
metrics
repository
and
has
to
stay
in
sync
and
that
this
getting
out
of
sync
has
led
to
problems
of
merging
changes
back.
A
The
benefit
of
the
branch
is
that
it's
Blaine
fully
painfully
clear
that
it
belongs
to
that
metrics
repository
and
it's
just
a
different
working
ranch,
but
it
reduces
the
visibility
and
if
you
don't
merge
changes
regularly,
then
they
will
just
the
same,
be
out
of
sync
again
so
yeah
you
lose
visibility.
You
lose
the
ability
to.
C
A
New
maintained
errs
that
are
unique
to
the
growth
merchants
in
Klein
workgroup,
because
you
can
only
add,
maintain
errs
that
are
then
assigned
to
the
entire
metrics
committee.
You
don't
have
a
front
page
readme
people
looking
for
the
workgroup
will
have
to
be
directed
to
a
repository
to
a
branch
of
the
repository.
The
github
workflow
is
towards
the
master
branch
by
default,
which
might
cause
people
to
accidentally
create
pull
requests
and
to
the
wrong
branch,
and
also
you
don't
have
unique
issues
to
the
girls
mentoring.
A
D
Completely
share
your
opinions.
I
already
commented
in
the
mailing
list
burst
hill
from
a
procedural
point
of
view,
I
think
it's
bad
thing
to
call
and
go
back
and
again
so
right
now,
I
think
there
are
two
options:
one
could
be
to
say:
decision
was
not
made
with
me
to
discuss
and
either
have
a
decision
in
the
Middle
East
or
in
the
next
working
group
meeting.
Maybe
we
can
do
that
in
the
Middle
East.
C
D
At
the
beginning,
as
you
said,
that
helps
of
my
personal
view,
so
I
think
that
if
sin
is
not
here
since
he
was
as
far
as
I
remember,
support
your
off
or
maybe
the
main
support,
your
opinion
and
in
branch.
So
maybe
we
can
discard
clips
in
the
mailing
list
and
consider
that
until
we
have
a
firm
decision
on
the
mailing
list,
there
is
no
decision
there.
So
what
do
you
think
I
just.
A
D
What
we
did
in
the
repository,
if
you
remember
yeah
and
I,
mean
assuming
we
don't
revert-
that
the
decision
to
the
decision
was
to
have
a
working
space
for
Jim
D,
and
that
was
one
of
the
reasons
for
teaming
up
top.
If
we
prefer
to
stay
in
sync
with
everything.
That's
fine,
but
in
that
case
is
meant
to
be
more
difficult
to
explain
people.
What
is
the
working
group
about,
because.
A
C
Even
after
we'd
have
to
change
the
file
structure,
sorry
we'd
have
to
change
the
file
structure
for
the
entire
metrics
repo,
rather
than
like
diversity.
Inclusion
would
have
to
have
a
folder
and
that
he
would
work
out
of
that.
Folder
right
GMD
would
have
a
folder
and
they
would
work
out
of
that
folder.
That's
probably
what
we
would
have
to
do
if
we're
working
on
the
branch.
D
D
C
I
actually
I
I
would
rather
work
from
the
separate
repository
just
for
the
record,
so
I'm
I'm,
not
in
favor
of
moving
to
the
branch
but
I
agree
I
think
maybe
we
should.
We
should
take
the
conversation
to
the
email
list
and
maybe
kind
of
create
a
chain
that
we
can
kind
of
+1
and
maybe
did
consensus
that
way.
If
your
could
make
his
arguments
in
favor
of
the
repository,
that
would
be
helpful
because
I
think
Sean
made
arguments
in
favor
of
the
master
branch
today
in
an
email.
A
D
A
Part
also
in
this
conversation,
how
the
repository
of
the
branch
will
look
like,
because
if
we
are
cleaning
it
up,
removing
things
that
are
part
of
other
work
groups,
then
we
will
have
the
same
issue
that
we
have
right
now,
regardless
of
whether
it's
a
branch
or
repository.
So
that
is
something
that
needs
to
be
addressed.
Do
we
want
an
easy
way
to
just
get
merge
back
and
create
a
pull
request,
or
is
it
the
more
involved
process
of
choosing
the
files
that
we
manually
copy
back
and
forth.
D
So
one
thing
that
we
have
is
that
the
diversity
Ning
conversing
group
is
already
doing
this
kind
of
stuff.
Since
there
there
is
a
new
structure
as
far
as
say
it.
So
the
repository
so
I
think
that,
at
least
for
that
working
group,
the
decision
is
taking
some
words
him
back.
The
matrix
is
going
to
be
possible
point
five
by
five
and
I
found
that
reasonable,
because
every
working
group
should
decide
in
my
opinion
and
the
burden
of
margin.
D
In
fact,
it's
only
merging
up
to
a
point,
because,
from
our
point
of
view,
what
we
really
need
is
to
let's
say,
release
a
version
of
the
gene
d
matrix
and
basically
copy
that
into
the
repository,
not
necessarily
getting
the
history
or
whatever,
because
the
history
is
changed
can
stay
in
the
working
world
repository.
If
we
do
it
with
branch,
it
could
be
from
me
the
same.
So
that's
why
everything
which
is
not
related
to
Jim
day
in
the
GMB
branch
or
in
the
gym.
D
D
But
but
again
maybe
we
can
stop
here.
Try
to
have
the
decision
made
by
consensus
in
the
mailing
list
and
if
there
is
no
possibility
we
can
decide
in
the
mailing
list
either
just
have
a
podium
or
have
any
specific
meeting
where
we
discussed
this
because
it's
important
for
you
for
the
working
group.
Do
you
agree.
D
Okay,
thank
you,
so
I
would
say
that
there
are
two
old
things:
a
place
in
my
mind
that
they
would
like
to
briefly
talk
about.
One
is
the
use
cases
that
jerk
is
willing
to
merge,
so
my
impression
is,
we
should
do
it
now,
a
stop
to
pull
records
with
them.
So
my
decision
is
once
we
might
remind
my
my
opinion.
D
Is
that
once
we
are
done
with
the
way
we
work
with
repository,
we
should
be
merging
them,
and
this
is
an
important
part
of
the
repository
so
I
very
much
like
those
use
cases
in
having
more
when
we
can
have
them
and
the
second
one
is
more
related
to
the
renaming
that
was
commented
some
weeks
ago
on
the
metrics
and
everything
I
think
we
should
also
go
on
with
that.
So
I
could
consider
these
two
decisions
as
taking,
if
you
all
agree
with
independence
of
what
happens
with
repository.
Do
you
all
agree
on
this.
D
B
B
We've
got
the
examples
over
talking
up
these
having
the
Jupiter
notebook
as
a
format,
so
I
raised
that
on
the
on
the
kibble
list
and
the
feedback
I
got
was
that
because
people
already
has
the
visualization
and
the
aggregation,
it
doesn't
didn't,
make
sense
to
try
and
call
the
day
throughout
of
cueball
third
try
and
use
Jupiter's
to
make
it
do
what
people
already
does
so
so
my
question
was
you
know
with
the
examples
that
we
can
get
out
of
people?
How?
How
can
we
integrate
them?
If
we're
not
new,
so.
B
B
C
I,
don't
think
you're
obligated
to
use
the
Jupiter
notebooks
I.
Think
in
the
the
use
case
templates
were
wanting
to
create
the
there
was
a
section
I
think
where
we
were
wanting
to
have
like
example,
implementations.
Is
that
correct
mm-hmm?
So
we
could
just
just
point
it
towards
kibble?
Is
there
a
public
instance
that
you
can
show
yeah.
B
D
So,
in
any
case,
the
Jupiter
notebooks
are
only
designed
as
a
kind
of
a
reference.
It's
not
important
that
the
code
is
the
same,
but
if
we
agree
on
the
definition
of
the
matrix,
the
result
for
a
given
repository
should
be
the
same.
So,
for
instance,
when
the
accounting
commits,
as
we
are
trying
to
show
in
the
in
the
notebook
right
now,
which
is
only
one
written,
you
need
to
decide
which
commits
your
account.
In
fact,
and
you
can't
count,
merge,
commits
and
pick
me
to
know
that.
D
But
then
the
thing
is
whichever
you
are
counting
that
the
number
should
be
the
same
in
the
case
of
committee.
It's
obvious,
because
there
is
very
little
room
for
for
difference,
but
you
know
not
in
other
cases,
depending
on
how
you
actually
count
could
be
a
bit
different.
So
the
idea
is
as
to
to
have
a
reference
to
know
that
we
account
in
the
same.
D
So
if
you
want
that,
I
can
also
work
with
you
in
trying
to
find
out
if
there
are
differences
or
not,
because
for
some
of
the
things
I'm
pretty
mature,
that
there
is
not
going
to
be
any
difference,
but
I
don't
know,
for
instance,
maybe
at
some
point
you
decided
to
only
count
commits
in
master
instead
of
in
all
the
Drobo
story,
for
instance
a
difference.
So
that's
the
kind
of
things
that
we
need
to
be
a
bit
careful
with
and
4-stroke
evil
doesn't
need
to
run
to
get
exactly
the
same
metrics.
D
C
D
B
D
D
It's
not
tied
to
how
do
more
lab
a
staff
or
a
cable
or
anything
else,
and
but
but
we
could
use
it
to
define
precisely
how
the
metrication
period,
let's
say
at
Scout,
says,
and
then
you
may
have
a
good
reason
for
comparing
it
in
some
wall
away
or
Gomorrah
forever,
but
they
cannot
claim.
This
is
the
way
counterfeit.
That's
it.
Okay,.
B
Because
one
of
the
things
I
was
I
was
starting
to
do
as
well.
We
start
with
discussion
to
just
analyze
all
these
new
people
against
all
GMB
metrics.
Let's
make
sure
to
look
at
the
calculation
that
we're
using
as
part
of
a
no
application,
as
you
see
whether
or
not
believe
in
line
with,
what's
being
already
be
fine,
so
this
was
also
a
discussion
that
I
started
to
look
at
as
well.
So
like
I,
think
let
me
so
look
what
I'll
do
that
I
was
gonna
paste
in
younger
time.
B
D
Because
I'm,
something
that
we
something
that
we
could
do
together,
if
you
want,
is
for
the
matrix
in
GMD
just
start
an
open
discussion
on
each
of
them,
how
to
compute
them
in
English
and
then
write
the
notebooks
based
on
that
discussion.
If
you
want-
or
at
least
for
those
were,
we
could
have
differences
may
be
counting
committees,
not
one
of
those
bad
for
some
others,
and,
and
that
way
we
can
come
to
a
conclusion
which
is
let's
in
neutral.
From
the
point
of
view.
B
Like
a
logical
flower,
well
then,
so
let
me
let
what
I'm
one
of
the
things
that
I
will
take
away.
Then
I'll
go
I'll,
go
away
and
find
out
about
how
they're
doing
how's
it
been
implemented
for
the
various
metrics
as
they
are,
as
they
are
now
see
what
you're
not
going
align
them
and
then
we
can
actually
put
like
if
they
work
through
and
see
how
it
is
in
specify
in
a
logically
English,
but
why
anything?
Okay,.
D
If
you
look
at,
if
you
look
at
the
commits
matrix,
which
is
the
only
one
where
we
are
complete
a
complete
notebook,
the
idea
is
to
first
define
the
data
source,
then
try
to
say
in
English.
This
is
what
we're
doing
in
the
first
case
count
commit
and
then
look
at
the
different
ways
that
could
be
considered
reasonable
for
counting
the
commits
in
the
case
of
commits.
We
only
came
up
to
there
at
this
point.
We
should
be
deciding
okay.
B
B
A
Just
wanted
to
say,
I'm
super
excited
about
this
idea
of
seeing
how
cable
influenced
electric
and
then
comparing
that
to
how
grimille,
app
and
auger
are
doing
it
and
then
defining
one
way
that
becomes
then
the
the
way
that
Kaos
says
is
not
necessarily
the
right
way.
But
the
way
that
we
want
to
standardize
on
the.
A
B
A
Way
that
I
think
we
could
do
this
is
I.
Have
three
questions
I
think
prepared,
there's
a
document
on
this
idea
for
the
blog
post
to
ask
this:
whoever
responded
if
they
could
elaborate
a
little
bit
more
and
write.
This
blog
post
include
a
few
screenshots,
and
then
we
would
include
this
in
our
blog
post
series
on
how
our
metrics
currently
being
used
so
that
we
built
up
a
database
of.
B
B
B
And
one
of
the
things
that
I'm
trying
to
do
as
well
as
trying
to
get
a
bit
of
a
bit
more
of
a
visibility
on
the
metrics
and
chaos
and
diversity,
and
inclusion
and
stuff
like
this
into
not
only
the
people
particular
to
the
community
development
project
because
we
might
have
comdev.
We
it's
the
sort
of
subjects
that
we're
looking
at
and
we
would
be
wanting
to
use
that
information
to
be
able
to
better
inform
better
reports,
but
a
health.
A
D
C
D
That
the
notes
that
the
comments
that
York
and
me
did
about
the
repository
were
already
already
sent
to
the
mailing
list,
so
it
could
be
mainly
about
the
let's
decide
on
this.
If
there
is
an
opportunity
for
conscience,
first
I
can
I
can
sign
on
your
on
your
message.
If
you
want
you
just
summarize
what
we
thought
today
right.