►
From YouTube: CHAOSS.Common.December.12.2019
Description
CHAOSS.Common.December.12.2019
A
Oh
now
we'll
go
ahead
and
get
started
so
welcome
to
the
chaos
common
metrics
meeting
for
December
12th
2019.
We
have
a
couple
of
things
on
the
agenda
today.
I
thought
we'd
do
a
have
a
quick
look
at
the
open
poll
requests
and
new
issues
release
plans.
So
we
need
to
talk
about
that
and
discuss
the
contribution
metric
overlap
with
with
DNI.
A
So
if
we
take
that
from
the
top
I
realized,
there
were
a
couple
of
poll
requests
from
a
while
ago
that
I
had
not
looked
at
Garriga
merged
yours
for
the
funding
thing
for
the
repo
that
one
was
obviously
a
obviously
a
no-brainer,
so
that
was
easy
and
then
the
other
one
we
have
is
the
contributors
metric,
which
is
pull
request.
Number
36.
A
A
C
B
A
A
D
D
D
B
A
A
So
we
have,
we
have
the.
Let's
see
we
released
org
diversity.
Last
time
we
have
contributors,
pretty
much
ready
to
go,
activity
dates
and
times
is
ready
to
go,
and
then
we
have
a
number
of
in
progress
ones
we'll
get
to
the
considering
one.
Was
it
that
last
cuz?
That's
on
the
agenda
for
today,
anyways.
A
C
A
A
A
C
A
C
B
C
E
E
A
B
E
A
A
C
A
E
C
E
A
A
E
C
E
Think,
speaking
to
Matt's
point
I
think
that
is
probably
just
a
simpler
objective:
we're
identifying
a
level
of
activity
you
know
in
terms
of
speed
or
cadence
or
whatever.
We
want
to
call
it
because
making
a
community
more
welcoming,
it's
certainly
a
secondary
goal.
You
can
also
use
this
measurement
like
for
the
diversity
and
inclusion
set
if
you're
trying
to
see
if
there's
a
problem
in
that
area,
but
that's
a
second
level
goal.
Mm-Hmm
yeah.
C
E
E
B
A
A
Would
like
add
something
about
contributors:
I
think
that
this
is
too
specific
and
I.
Think
it's
too
focused
on
new
contributors.
The
reality
is,
if
you,
if
the
time
the
first
response
is
terrible
in
any
community
like
you
just
don't
want
to
contribute.
If
you
it
doesn't
matter
how
long
you've
been
there,
if
I
submit
a
pull
request
in
kubernetes-
and
it
just
sits
there
for
forever
every
single
time
and
nobody
replies
to
it,
then
that
becomes
a
problem.
E
E
B
A
A
C
A
A
C
A
B
B
D
A
B
A
A
B
C
A
A
C
A
A
A
B
C
B
A
B
A
A
D
B
So
we
had
written
this
originally
for
the
DNI
working
group,
and
so
it
still
has
a
DNI
angle
to
many
aspects,
but
the
feedback
that
Emma
had
provided
on
the
pull
request
is
that
this
is
a
lot
of
generic
ways
of
how
do
we
determine
types
of
contributions?
It's
not
focused
enough
on
diversity
and
inclusion,
but
we
meet
this
level
of
detail,
and
so
the
idea
is
to
pull
out
what
is
just
generic
identifying
types
of
contributions
and
putting
that
into
the
common
working
group.
A
A
B
C
A
A
So
we
do
need
to
put
together
release
notes
and
we
decided
that
the
release
notes
would
also
be
a
part
of
the
review
period
and
we
talked
about
how
the
release
notes
should
be
pretty
high-level,
so
kind
of
along
the
lines
of
you
know.
These
metrics
were
put
into
the
new
template
and
the
list
of
those
metrics.
This
metric
had
some
kind
of
fundamental
change,
so
if
we
decided
to
change
the
way
that
we
calculated
organizational
diversity,
that
would
be
in
the
release,
notes.
B
A
C
A
B
A
A
A
A
B
A
A
B
A
B
A
A
B
A
Made
lots
of
progress
so
we'll
look
at
this
one
last
metric
done
for
the
release
and
then
I
think
we'll
be
I.
Think
we'll
be
in
good
shape.
I
think
looks
like
we'll.
Have
three
three
new
ones
for
the
release
or
was
orc
diversity?
Was
that
in
the
last
release
it
was?
It
was
just
the
update
to
be
yeah.