►
From YouTube: CHAOSS Metrics Models Working Group 10-12-21
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
uh
welcome,
oh
and
I'm
going
to
turn
on
live
transcripts
enable
so
I've
turned
on
live
transcripts
and
we
are
recording
so
welcome
to
the
october
12th
october
13th
uh
metrics
model
working
group
meeting
the
minutes
and
the
repo
and
the
spreadsheet
are
all
in
the
chat.
So
if
you
could
take
a
look
and
add
yourself
to
the
list,
that
would
be
great
just
like
to
all
let
you
know
that
halloween
candy
has
arrived
in
my
house.
A
A
A
A
I
put
the
minutes
in
from
last
time
because
we
haven't
met
for
a
month
because
last
two
weeks
ago
we
were
in
seattle,
many
of
us,
and
so
I
just
wanted
to
give
you
kind
of
an
update
through
here.
um
There
were
a
few
to
do
things
for
us.
I
think,
partly
it
was
just
kind
of
organizing
the
work
and
kind
of
getting
the
repository
set
up
and
uh
getting
things
aligned
with
the
spreadsheet.
You
know
what
I
mean.
A
I
did
want
to
just
real
quickly
and
I
think
the
main
point
of
today
that
we
left
off
last
time.
Just
so
you
know,
is
that
we're
going
to
brainstorm
for
new
metric
model
ideas.
I
think
this
was
lucas's
suggestion
from
a
month
ago,
if
I
remember
correctly-
and
I
think
that's
a
great
idea,
but
nonetheless
I
just
wanted
to
do
just
a
little
bit
of
housekeeping
here
to
kind
of
show
you
what
we've
got.
um
Does
anybody
want
to
add
anything
to
this
agenda?
A
A
A
So
I
think
the
the
readme
is
actually
working
out
pretty
well
at
this
point.
So
if
you
could
all
just
take
a
look
at
the
readme,
I
tried
to
keep
it
fairly
simple,
but
all
the
links
should
work.
It
goes
out
to
our
code
of
conduct.
It
goes
out
to
our
participate
page.
It
goes
out
to
our
agenda
that
nobody
can
get
to.
It
goes
out
to
our
focus
areas.
You
know
what
I
mean,
so
it's
it
should
have
everything
pretty
well
squared
away
in
there.
D
A
A
A
D
A
So
this
should
be
all
the
point
being
not
that
I
really
did
anything
it's
just
this.
This
should
all
be
categorized
pretty
well
now,
just
in
terms
of
what
yahui
had
done,
you
know
what
I
mean
and
now
that
we
have
it
properly
placed
and
that
aligns
with
this
spreadsheet,
which
is
our
metrics
model
templates
our
metrics
models.
I
suppose
we
could
just
call
it,
and
this
is
in
the
development.
A
This
is
in
the
development
focus
area,
and
this
is
issue
handling
right
here.
I
went
ahead
and
took
the
text
that
yahui
had
put
in
the
metrics
model
and
just
put
it
in
the
why
you
should
care.
I
also
included
all
of
the
metrics
that
were
in
there
as
well
so
again
just
trying
to
keep
these
things
somewhat
parallel
and
then.
Finally,
just
all
the
way
over
to
the
right
side
is
a
link
to
the
metric
itself.
All
right
so
does
anybody
have
a
comment
as
to
how
we
kind
of
track
these
metrics
models?
A
E
B
E
A
A
E
A
F
I
think
it
might
be
helpful
um
to
lay
that
groundwork
now,
because
in
the
future
we
may
want
to
lump
metric
model
models
for
specific
groups
of
people
or
for
like
a
specific
scenario
like
okay,
I'm
starting
a
new
open
source
project.
What
are
the?
What
are
the
different
metrics
models
that
I
will
need
to
look
at
the
different
pieces
of
my
project?
Something
like
that
like
I
just
feel
like.
It
might
be
good
to
start
that
now,
maybe
it's
a
little
more
work,
but
that
could
be
helpful
later
on.
A
G
D
D
Very
explicit:
what
are
we
measuring?
What
is
it
and
then
the
next
section
we
jump
down
to
objectives
and
in
that
objectives
area?
That's,
basically
the
why
we
should
care
and
with
the
with
the
metric
model,
we're
just
we're
jumping
straight
to
the,
why
we
should
care,
because
this
is
this
really
is
kind
of
the.
D
D
A
A
F
B
A
B
A
F
Have
a
quick
question
uh
so
in
these
metrics
models,
we're
listing
all
the
metrics
that
we
think
go
together,
but
we
don't
really
talk
about
how
to
use
them
together
and
like
how
like,
okay,
here's
this
list,
am
I
looking
at
them
all
separately?
Am
I
like
layering
them
on
top
of
each
other
or
like
does
uh
you
know
burstiness?
Does
that
mean
that
it's
going
to
affect
my
time
to
first
response
or
like
we
don't
really
talk
about
the
way
they
interact
with
each
other
to
fit?
That
picture
is
that
on
purpose.
D
I
think
that
has
to
be
on
purpose,
because
uh
using
these
models
is
going
to
be
highly
contextual,
I
don't.
uh
I
don't
think
we
want
to
get
too
specific
in
how
they
fit
together.
I
mean,
even
if
we,
even
if
we
include,
if
we
include
six
metrics
in
in
a
model
that
uh
that
looks
at
uh
you,
know,
responsiveness
in
a
pull
request,
not
all
of
those
not
all
of
the
metrics
that
we've
included
may
be
important
to
the
uh
the
person
that's
using
it.
D
D
D
E
A
F
Do
you
think
that's
something
that
maybe
like
long
term,
we
can
look
at
exploring,
because
I
think
that
that's
really
the
piece
that's
helpful
to
people
like
giving
them
a
list
is
great
and
that's
that's
like
the
first
step,
but
like
helping
them
understand
how
these
things
interact
with
each
other
and
the
context
you
can
build
around
something
I
think
is
like
next
level
stuff,
so
maybe
like
in
two
years.
We
could
do
that
or
something
like.
I
would
really
like
to
say
yes
to.
F
A
A
A
A
A
D
D
A
G
A
B
I
think
I
think
um
we
could
um
come
up
with
a
tidy
package
for
this
sentiment.
Analysis
thing
by
just
kind
of
name
checking
the
social
listening
metric
right
right
because,
like
in
the
template,
basically
we're
coming
up
with
a
list
of
relevant
metrics,
and
I
think
the
answer
is
that
the
social
listening
metric
is
relevant.
A
A
Why
don't
I
pause
the
recording
and
maybe
like
elizabeth,
you
could
try
to
come
up
with
a
metrics
model,
metric
and
lucas.
You
could
try
to
do
the
same,
and
you
know
I
mean,
like
everybody,
could
maybe
just
kind
of
follow
this
really
coarse
grain
approach
for
a
metrics
model.
Would
that
be
okay
with
folks.
A
Yeah
exactly
so
you'd
have
kind
of
this
top
level
um
metrics
model
that
you
just.
I
think
it's
something
that
you
just
through
your
experience
and
through
your
conversations
around
community
health,
no
might
be
a
good
model
that
people
would
care
about,
um
and
then
yes
and
then
it's
identifying
chaos
metrics.
That
could,
as
we
kind
of
always
say,
like
move
the
model
off
zero.
So
I
don't
think
the
chaos
metrics
that
we
have
would
fully
articulate
the
metrics
model,
but
it
would
help
excuse
me
it
would
help
create
some
insight
on
that
model.
Okay,.
A
F
A
B
A
A
All
right,
we
are
back
recording
from
a
little
break
and
I'm
going
to
go
share.
My
screen
again
wasn't
a
break
but
um
share
my
screen
again,
and
here
we
are
one
of
the
things
that
came
up
over
the
our
short
micro
sprint.
I
like
that
name
was
that
um
we
have
slowly
been
building
out
metrics
models
you
can
see.
I
have
one
up
here.
Elizabeth
has
one
here:
the
welcoming
community,
I
think
kevin
and
lucas
have
been
working
on
that
one
together.
A
A
D
I
I
did
put
bus
factor
in
and
the
uh
the
reason
I
put
bus
factor
in
is
because,
if,
uh
if
a
project
has
a
really
low
bus
factor,
that
means
that
the
majority
of
the
work
being
done
is
being
done
by
one
or
two,
a
small
number
of
individuals
right.
So
if
a
small
number
of
individuals
are
doing
the
all
of
the
work
you
do
have
to
ask
yourself
the
question
would
my
contributions
will
be
uh
be
accepted
right
because
I'm
I'm
not
part
of
that
that
in
crowd
or
that
small
core
group.
B
D
Cool,
so
I
think
it's
interesting
that
we
both
kind
of
went
to
a
uh
that
user
story
uh
format
for
these,
and
I
think,
that's
kind
of
what
matt
was
asking
as
well.
So
I
know
we
had
talked
about
perhaps
using
the
user
stories
in
the
uh
the
why
we
the
why
we
care
apart,
but
maybe
uh
maybe
this
is
where
the
user
stories
belong.
D
And
then
maybe
the
maybe
the
why
we
care
I
I
I'm
contradicting
what
I
said
before
when
I
said
that
I
I
thought
the
uh
having
the.
Why
we
care
first
uh
is
a
good
thing,
but
uh
but
maybe
we
maybe
we
do
take
that
back
and
and
and
do
more
kind
of
a
high
level
description
of
what
the
model
is,
rather
than
the
the.
Why
we
care
at
that
point.
B
For
example,
um
there
are
projects
that
only
have
a
small
group
of
core
contributors,
even
though
there
are
a
lot
of
users
and
and
that
prefer
it
that
way
um
and
and
those
that
second
type
of
project
would
be
disinterested.
So
um
I
can
imagine
the
why
you
should
care
would
be
something
like
as
a
maintainer
of
a
project
looking
to
grow
the
contributor
base.
I
D
uh
So
a
lot
of
personas
can
can
share
those
same
user
stories
so
it
because
it
becomes
kind
of
a
uh
like.
Let's
count,
how
many
different
personas
we
can
identify,
uh
whereas
if
we,
if
we
focus
on
the
activity,
then
we
can
say
you
know,
this
activity
is
probably
important
to
a
number
of
different
people,
uh
and
you
know
what
I
don't.
I
don't
necessarily
care
who
the
people
are
that
are
important
to
it
other
than
maybe
as
a
as
a
reference
tag,
so
that
a
community
manager
might
come
in
and
say
hey.
A
A
And,
as
you
feel
like,
you
need
to
add,
I'm
totally
making
this
up,
but
like
a
subsection
called
personas
or
you
want
to
add.
You
know
like
that,
subpart
that
we
were
just
doing.
You
know
how
it
says
metric
one,
and
then
we
added
this
other
thing
here.
Whatever
that
thing
is
user
story.
Is
that
what
we're
calling
this.
A
D
A
A
H
A
um
I
guess
maybe
the
one
thing
before
we
wrap
it
up
here.
That
I'd
ask
is
that,
like
elizabeth
is
you're
putting
yours
together
and
you
have
kind
of
a
way
that
you
are
feeling
like.
You
are
describing
your
metrics
model
and
I
have
a
way
that
I'm
describing
my
metrics
model.
You
know
I'm,
including
perhaps
a
new
subheading
and
lucas
and
kevin.
A
You
also
the
same.
The
likelihood
that
we're
all
going
to
land
in
the
exact
same
design
is
zero,
as
we
all
come
back
in
two
weeks,
and
so
um
can
we
all
just
kind
of
promise
to
do
this
work
and
then,
when
we
come
back
like
it's,
not
a
it's,
not
a
competition
of
like
whose
model
is
the
best
that
we
find
beauty
amongst
all
of
them
and
work
together.