►
From YouTube: CHAOSS.Common.March.21.2019
Description
CHAOSS.Common.March.21.2019
A
Previous
action
items,
Shawn
was
gonna,
create
a
template
in
the
repository
basically
modeled
off
with
GMD
template.
I
have
not
seen
that
yet
and
he's
not
here
so
I'm
going
to
assume
that's
ongoing
Matt
was
going
to
filter
and
consolidate
the
metrics
list
and
he's
not
here
either
so
looks
like
no
update
on
that
and
the
risk
working
group
is
gonna.
Look
at
the
take
on
the
the
license.
Metrics
did
it?
Does
anybody
attend
the
risk
working
groups
if
I
know,
if
there's
been
any
progress
on
that?
A
A
A
No
worries
realistically
I
think
this
might
be
a
short
meeting
because
I
don't
think
any
of
us
got
our
work,
get
anything
done
because
they're
conferencing,
so
there
just
wasn't
a
lot
a
lot
going
on
how
about
progress
on
the
responsiveness,
metrics,
I,
think
Daniel.
You
were
looking
at
that
right.
Yeah.
C
So
I
know
that
you
had
another
meeting
two
weeks
before
that
I
could
not
then
I
didn't
know
if
we
had
some
specific
advances
on
this
okay,
so
what
they
did,
or
at
least
I
start
started
to
to
work
on
worse,
at
least
a
set
of
metrics
that
we
have
been
seen
with
some
people,
some
customers
and
so
on.
So
I
will
copy
some
of
them
here.
A
C
C
Yeah,
this
is,
let's
say,
pretty
focused
on
Garrett,
so
there
might
be
other
code
review
processes,
let's
say,
for
instance,
may
ministers
in
the
linux
kernel,
so
this
works
in
a
different
way.
So
we
may
use
some
of
this,
but
basically
time
to
merger
is
the
time
the.
Since
we
have
oh
it's
for
the
whole
time
in
here,
the
neighbors
would
looking
for
specific
things
like
we
have.
You
know
we
have
iterations,
and
then
we
have
the
time
for
each
of
the
directions
there.
A
C
Each
of
the
iterations-
basically,
this
is
a
ping-pong
between
the
submitter
and
reviewer
to
them
in
this
case
as
well,
doesn't
need
to
be
in
this
way,
but
typically
you
have
one
submitter
and
one
reviewer.
So
it
means
that
well,
there
is
a
time
waiting
for
a
reviewer
action
and
there
is
a
time
waiting
for
a
submitter
action.
We've
been
using
these,
for
instance,
probabilistic
foundation,
then
the
number
of
iterations
the
time
to
merge
since
this
was
approved.
C
So
this
is
an
example
were
sanguine,
says
well,
for
instance,
in
Garrick
Plus
to
own
in
in
in
the
Linux
kernel.
I
acknowledge
this.
So
then
there
is
a
time
until
since
this
is
a
proof
that
say
till
this
is
really
in
the
the
master
branch
and
then
the
time
the
for
responds
to
say,
hey
someone
sent
something.
So
what's
our
time
for
attendance
here,
this
more
or
less
the
the
time
in
IE
I
produce.
C
A
A
A
Yeah,
maybe
I,
don't
know
we
really
so
the
bit
that
we're
doing
now
is
a
bit
different
than
what
the
what
a
lot
of
the
other
Doc's
and
the
templates
have
which
is
stuff
about
individual.
You
know
like
details
for
each
individual,
metric
and
I.
Think
right
now.
What
we're
trying
to
do
is
get
the
list
of
metrics
that
we
should
be
that
we
should
be
working
on
so
and
then
once
we
have
the
list,
we
can
figure
out
the
definition.
A
F
F
If
there,
if
you
post
it
in
the
document,
I
can
do
it
kind
of
a
cross-check
as
to
whether
or
not
any
particular
metrics
is
in
the
metrics
repo
I.
Think
they're,
just
gonna
have
to
be
some
cleanup.
It's
done
like
you
know.
Some
of
them
have
different
names,
but
they're
the
same
fundamentally,
the
same
thing.
So
if
you
can
just
get
those
posted
I,
don't
mind
kind
of
just
cross-checking
things:
okay,.
A
Yeah
I
think
I
think
what
else
rest
day
was
I.
Think
if
we,
if
we
start
with
an
issue-
and
we
list
out
all
the
metrics-
that
we
think
we're
gonna
need
for
this
particular
area.
I
think
that
would
be
a
really
good
starting
point.
And
then
then
what
we
might
want
to
do
is
do
one
more
review
in
the
in
the
call
and
decide
that
yeah.
A
A
Metrics
Geographics
geographic
data,
and
so
those
are
kind
of
the
three
that
we've
identified
so
far,
I'm
sure
there
are
other
other
focus
areas,
I
think
part
of
the
work
you
do
is
kind
of
break
those
metrics
down
in
focus
areas
and
then
and
then
figure
out
how
to
how
to
define
them.
Does
that
yeah.
F
A
F
F
F
A
A
C
A
C
A
A
The
work
that
John
did
on
oh,
that
link,
doesn't
work
anymore.
The
issues
link
because
I
changed
the
name
of
the
tag
to
common
metrics.
A
E
E
A
A
A
Cool
anything
else
on
Geographic
for
today,
probably
probably
should
cycle
back
on
it
in
the
next
meeting.
Hopefully,
when.
A
C
Just
mention
here
that
importance
of
Ramallah
we
have
time
zones,
it
is
something
discussed
here
and
in
for
some
people
we
were
talking
at
simply
adding
the
country
president.
So
then
well
they
can
filter
away
this
information.
This
is
supported
by
charting,
have,
for
instance,
that
personal
personal
community
many
years
and
they
were
filling
the
information
there,
which
is
perhaps
not
consider
here
kind
of
consider
eyepiece,
but
it's
it's
set
around
the
issue.
They've
been
really
now
anything.
It's
quite
interesting,
this
hours
of
activity
by
a
meter
overall
for
just
make
two
cents
here:
okay,.
C
C
A
E
E
A
A
A
A
I'll,
try
to
provide
some
feedback
on
the
the
language
that
you
used
for
the
for
the
governance,
because
I
think
there's
a
pretty
standard
language
that
people
use
for
describing
how
to
do
the
developer
certificate
of
origin,
origin
and
the
language
that
we
have
feels
a
bit
different
to
me
for
some
reason,
and
so
I
need
to
I
need
to
dig
into
that
a
little
bit.
Did
you
use
an
example
from
another
repository,
or
did
you
write
that
from
scratch?
Garak
what
you
put
in
the
contributing
for
the
governance.
A
A
If
I
don't
get
a
chance,
I
would
say
so
the
two
projects
that
I've
seen
that
I
think
do
a
really
nice
job
of
describing
how
to
do.
This
are
the
Concours
project,
which
is
a
pivotal
project.
I
worked
with
them
a
little
bit
on
implementing
the
DCO
and
chef,
so
those
two
did
a
pretty
good
job
and
they're
contributing
Docs
of
describing
how
to
how
to
do
it.
So
maybe
maybe
have
a
look
at
those
two.
E
A
D
A
B
B
B
E
But
my
concern
is:
how
do
we
structure
the
different
pages
get?
My
life
is
using
a
structure
where
at
the
highest
hierarchy
they
have
the
functions
within
the
business
and
then
within
that
they
have
each
process
documented,
and
my
question
right
now
is:
do
the
that
many
functions
or
do
we
just
start
with
the
processes
later
I
was.
B
Thinking
we
start
with
the
processes
that
we
know
we
have
and
then
obviously,
since
it's
collaborative
effort
I'll
be
throwing
that
out
to
the
group
because
I'm
sure
I'll
miss
something
and
they're
also,
you
know
probably
be
processes
that
were
so
one-off.
An
ad
hoc
will
never
do
them
again
for
lack
of
a
better
description.
B
B
B
A
A
D
B
B
A
Okay,
just
wanting
you'd
probably
prefer
ensign
facilitator.
Okay
looks
like
Daniels
gonna
facilitate
and
Brian's
gonna
note
take,
because
that's
what's
in
the
notes,
perfect,
okay,
so
and
Daniel.
Just
as
a
reminder,
part
of
the
facilitator
role
is
to
send
out
the
reminder
for
the
meeting
which
think
about
on
I
guess:
Monday
send.
A
A
A
Yeah
because
the
u.s.
already
did
daylight
savings
time,
so
this
is
like
the
three
weeks
of
chaos
where
no
one
knows
when
any
meetings
are
the
number
of
times
this
week
that
I've
heard
oh
I
thought
that
meeting
was
you
know
in
an
hour,
so
fun
stuff,
so
just
make
sure
that
you
get
there
the
right
times
and
the
in
the
email,
because
it'll
be
different
than
what
I
set
out
this
week,
but
it'll
be
back
to
the
original
times
that
are
on
the
participate,
page
cool,
all
right.
Anything
else.
Are
we
done?