►
From YouTube: CHAOSS Common Working Group Meeting
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
All
right,
hi,
everybody
welcome
to
the
december
10th
chaos
common
work
group
meeting,
it's
good
to
have
you
all
here.
I
will
get
things
rolling
here
by
putting
stuff
in
the
chat.
A
C
A
It
does
not
feel
like
december.
I
can
tell
you
that
much
all
right,
okay,
so
I
put
a
couple
things
in
here
for
the
minutes.
We
kind
of
have.
D
A
A
Outstanding
any
outstanding
issues
or
pull
requests
that
we
need
to
attend.
A
A
C
Yeah
so
I
I
went
through
it,
I
basically
accepted
the
suggestions
by
all
of
you.
So
thank
you
very
much
for
those
I
left
like
four
or
five
extra
comments,
so
the
first
of
them
is
about
the
title
that
we
want
to
use,
which
is
that
thing
and
then
we
can
see
on
the
top
that
there
is
kind
of
another
really
long
title.
So
I
don't
know.
I
think
that
doesn't
make
sense.
That's
why
I
strike
through.
A
A
C
C
C
C
C
C
Provides
this
right
not
not
out
of
the
box,
so
it's
kind
of
indirect
metric
where
we
have
the
different.
So
there
is,
let's
say
we
don't
have
a
metric
that
says
hey.
This
is
the
time.
So
you
need
to
calculate
this
on
top
of
existing
data.
Okay,.
A
C
A
Okay,
it
would
be
kind
of
nice
if
we
could
give
it
just
a
read
here
for
10
minutes
and
come
close
to
putting
closure
on
this.
So,
okay,
I'm
going
to
stop
the
stop
my
share
and
I'm
going
to
pause
the
recording,
because
you
know
if
people
watch
this,
they
don't
need
to
watch
us
all
stare
at
our
screen.
B
Like
to
me,
that's
still
ambiguous.
B
If,
especially,
if
so
I
had
added
a
comment
here
or
a
suggestion
to
just
clarify
that
the
metric
applied
to
change
requests,
I
have
more
than
one
review
cycle
within
them,
but
given
so
like,
obviously
we
would
you
know
it
in
my
head.
The
between
the
cycles
was
what
we
were
looking
for,
not
the
total.
B
So
I
just,
I
still
think
that
that's
a
little
bit
ambiguous
if
we're
also
saying
that
it
could
even
be
one
review
cycle,
we
want
to
know
what
the
what
that
review
cycle
was
the
time
of
that
review
cycle,
even
if
there's
just
one.
D
B
C
Hi
so
yeah
we
were
discussing
about
this
we're
to
bring
some
more
context
where,
where
all
of
this
discussion
came
from,
this
is
part
of
a
work
done
with
the
same
community,
and
so
we
we
really
dig
into
the
process
they
had
and
so
on,
and
how
we
can
split
once
and
again
the
information
and
so
on.
Well
the
same
community
and
the
openstack
community,
because
this
is
referenced
there
as
well.
They
were
using
carrick.
C
So
it's
like
it's
like.
We
were
observing
the
different
events
and
then
trying
to
make
sense
of
all
of
the
all
of
the
ones
they
had.
So
then
you
can
see
how
things
were
working.
So
that's
why
we
are
defining.
We
have
this
concept
or
I
brought
this
concept
of
cycles
or
or
iterations
and
then
the
time
waiting
for
a
submitter
or
reviewer.
So
this
all
of
this
is
based
in
all
of
this
previous
work
anyway.
D
C
E
D
D
C
D
B
C
With
respect
to
the
to
the
metrics,
I
I
updated
a
bit
with
the
other
one,
so
I'm
waiting
for
a
submitter
action,
but
what
they
did
was
to
copy
part
of
the
initial
paragraph.
He
has
to
have
the
same
definition
of
change
request.
That's
all
I!
I
didn't
really
add
many
more
things,
so
I
can.
C
B
B
So
so
I
guess
this
would
be
another
metric.
That
will
excuse
me,
take
a
look
at
next
time,
since
we
did
make
some
good
progress.