►
From YouTube: CHAOSS Metrics Models Working Group 9-14-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).
C
B
B
C
B
B
C
B
All
right
all
right,
so
I
think
a
few
things
that
that
we
need
to
think
about.
I
know
that
we
have
some
metrics
models
that
we
want
to
talk
about,
and
I
know
yeah
we
had
done
a
metrics
model
and
we
can
take
a
look
at
that
in
a
pull
request
down
here
and
I
had
started
one
as
a
google
doc
for
event
badging,
and
we
can
take
a
look
at
that
too,
but
to
kevin's
point
as
well.
B
This
with,
like
the
participate
page
or
how
it's
just
the
web
page
kevin,
do
you
have
thoughts
on
like
what
we
need
immediately.
D
D
B
D
So,
on
the
participate
page,
there
is
a
module
about
three
quarters
down
the
page
that
says
web
content.
So
that
is
the
old
web
content
meeting,
which
we
have.
D
That
for
this
foreseeable
future,
we
are
not
going
to
be
meeting,
because
there
is
not
much
interest.
D
We
migrated
the
website,
we're
done
yeah,
so
so
that
module.
I
think
we
turn.
We
can
turn
that
one
into
the
the
metrics
model
meeting
is
that
under?
What's
that
under
the
website
repositories,
it's
in
the
website.
B
D
Yep,
so
basically
we
can
just
we
can
edit
this
one
and
change
the
change,
the
name
so
change
the
name
to
maybe
metrics
dash
model.
B
D
D
So
the
the
web
content
call
markdown
file.
You
need
to
change
the
name
to
metric
model,
dash
call
got
it
or
met
metric
dash
model
dash,
call.
D
This
is
the
markdown
file
that
we
can
edit
to
add
all
of
the
information
we
need
for
the
this
particular
meeting
and
I'm
going
to
go
ahead
on
the
website
right
now
and
I'm
going
to
change
the
pointer
so
that
it
is
grabbing
the
new
name
that
you're
putting
in
all
right.
C
B
B
B
F
Oh
sorry,
I
know
this
book.
E
B
How
do
I
change
the
name
of
a
do?
I
go
into
settings.
B
B
B
D
D
Metrics
focus
areas,
release
metrics
contributors,
chairs,
chairs,
license.
B
C
B
You
can
I
mean
if
we
could
do
it
right
now,
that'd
be
okay.
You
could
at
least
merge
the
pr
okay.
B
All
right
and
then
what
I
did
too
was
I
started.
I
just
wanted
to
make
sure
that
people
were
okay
with
volts,
so
I
had
a.
B
Focus
like
is
this:
what
we
want
to
do.
Oh,
I
should
probably
not
name
that
metric
metric
model,
but
we
just
have
seen
I'm
saying
it'd
just
be
a
pretty
simple
readme
here.
It
would
just
be
a
the
name
and
we
have
to
specify
the
goal.
We
could
just
put
this
in
as
a
placeholder,
and
I
could
then
put
out
all
of
these
readmes
in
the
respective
folders.
That
would
just
correspond
to
these.
B
B
D
D
So
question
might
not
be
the
description
might
be
a
better
yeah,
better
title
rather
than
question
okay,
so.
F
B
I
don't
know
it's
on
the
recording.
I
clicked.
I
did
something
wrong
anyway,
so
you're
saying
like
instead
of
for
that
table
that
it
would
just
be
the
metric
model
name
and
then.
D
F
B
Okay,
okay,
I
can
do
that
and
then
just
so
I
had
only
done
one,
but
just
so
you
know
I'll
make
a
folder
then,
like
I
said,
for
each
one
of
these
particular
focus
areas
and
then
within
there,
that
folder
will
capture
all
the
metric
metric
models
for
each
one
of
those
focus
areas.
So
like
yeah,
I
think
the
one
that
you
had
done.
I
don't
obviously
it's
not
placed
in
a
folder
the
pull
request.
I
think
you
just
placed
it
like
in
the
main
repo,
but
we
can
move
it.
I
B
Yeah
once
we
get
the
folders
created,
we'll
take
care
of
that
all
right
cool.
Is
there
anything
else
that
people
had
with
just
respect
to
structure.
B
B
B
Okay,
kevin:
do
you
think,
there's
anything
else?
We
need
to
do
structure
wise.
D
Once
we
start
working,
some
of
the
some
of
the
processes
will
start
to
emerge.
D
Yeah,
okay
and
I'll
take
a
look
at
the
the
readme
and
try
to
add
some
content
to
that.
B
Okay,
great
thank
you
and
then
I
also.
B
Oh
new
metrics:
what
am
I
doing
here
so
I'm
in
the
metrics
model
under
resources,
so
I'm
in
the
metrics
repository
right
now.
So
this
is
where
we
keep
our
templates
and
we
have
a.
B
I
need
to
format
this
a
little
bit,
but
we
have
a
metrics
model
template
here
and
based
on
looking
at
the
upcoming
metrics
models.
I'm
gonna
suggest
one
one
or
two
changes
to
this.
This
template
all
right,
so
you
can
just
wait
with
wait
with
excitement.
While
we
do
something
before
I
tell
you,
what
those
changes
propose.
Changes
would
be
all
right
so
now
we're
finally
into
the
metrics
model.
B
A
B
I
kind
of
follow
that
obscure
american
cultural
reference.
That
is
a
very
obscure
one.
You
like
even
it
took
me
a
little
while
to
grab
onto
that
one
all
right.
So
yahoo
has
a
a
pr
that
he's
put
together
and
it's
for
a
metric
model.
Yeah.
I
Yeah,
it's
about
part
of
the
development,
precise
model
matrix
model,
but
but
you
know
we
have
goal
that
we
should
provide
integrate
everything
into
one
model.
So
I
I
divide
those
development,
oh
okay,
into
several
parts.
So
this
is
the
first
part
about
issue
handling
or
they
can
call
to
the
requirement
anyway.
I
Okay,
because
this
is
just
the
first
part
about
issue
funding-
there
would
be
more
like
request
say
that
is
an
impressive
number
of
metrics
in
a
single
model
yeah
exactly
so.
That's
that's
why
I
don't
want
to
be
integrated
into
the
month.
Well,.
A
B
So
the
so
I
mean
the
beauty
of
these.
I.
I
J
You
view
yeah,
try
that
you
can
view
that.
Try
it
yeah.
C
I
So
I
integrated
with
the
latest
matrix
model
like
a
bot
activity,
something
like
that
into
the
issue
response,
because
we
invoke
a
lot
of
thoughts,
activities
with
the
response
and
also
some
other
new
metrics.
So
I
go
through
how
the
metrics
we
have
today
and
they
plan
to
use
media
stage
next
month.
B
B
I
Because
the
people
who
create
this
new
issue
and
the
people
who
who
responds
the
issue
is
not
the
same,
so
I
would
like
to
create
a
tool
to
those
profile
for
this.
So
if
I
need
to
do
so,
I
have
to
add
those
metrics
for
those
three
friends.
B
I
Yeah
yeah,
because
for
this
matrix
I
just
want
to
integrate
as
much
scenarios
as
we
can
into
this
matrix
mode,
but
in
the
real
case,
maybe
we
don't
have
to
focus
our
need
to
focus
everything
every
metrics
are
listed
here.
Okay,
that's
the
yeah.
B
Gotcha
that
makes
a
lot
of
sense,
sean
or
or
anybody
else.
What
are
your,
what
are
your
thoughts
on
this.
H
D
I
I
like
it,
I
like
it
as
a
high
level
model.
I
I
would
like
to
see
us
kind
of
zero
in
even
further
on
this,
because
just
just
looking
at
this
I
can
see.
I
can
see
some
interesting
things
that
we
could
say
about.
D
You
know
the
new
contributors
to
to
a
project
and
the
response
time
that
they
may
get
or
things
of
that
nature.
So
I
I
would
as
a
high
level
model,
I
like
it,
but
I
think
to
be
really
useful.
We're
going
to
need
to
zero
in
on
focus
in
on
on
a
few
kind
of
specific
uses
in
here.
E
So,
adding
to
the
cabins
like
on
focusing
in
like
when
I
was
reading,
okay,
new
issue,
thinking
that
somebody
has
opened
a
new
issue
and
somebody
has
responded
to
the
new
issue.
So
I
was
thinking
like
how
the
bus
factor
is
impacting
a
new
issue.
So
these
kinds
of
questions
making
you
think,
maybe
we
have
some
description
to
add
to
those
list
of
metrics
like
I
was
having
hard
time
to
connect
this
first
factor
with
a
new
issue,
so
how
this
bus
factor
is
connected
to
a
new
issue
that
somebody.
I
Else:
okay,
the
bus
factor
means
we
need
to.
I
mean
we
need
to
guide
those
people
or
users
identities,
including
where
are
they
come
from?
Maybe
come
from
comes
from
the
different
organizations,
so
we
could
collect
those
information
to
identify
okay
today
or
this
month,
most
issues
was
created
by
one
company
of
all
organizations.
I
E
Okay,
so
this
is
helpful,
but
what
I
felt
is
like
now
you
have
provided
me
the
context.
This
is
helping
me
to
connect
the
dots,
but,
let's
just
looking
at
the
bigger
picture,
I
was
having
a
hard
time
to
connect
the
dots.
So
that's
where
I
was
trying
to
say
maybe
a
some
context.
Background
will
be
helpful
in
this
way
to
help
our
reader
to
think
through
those
contexts
that
we
can
provide
them
just
looking
at
the
list,
I
like
it
was
good.
E
D
B
So
let
me
make
two
comments,
one,
so
I
I
actually
think
this
does
tell
a
story,
so
it
tells
me
that
if
I'm
interested
in
looking
at
new
issues
or
issue
responses,
these
are
the
ways
that
I
can
think
about
them.
B
So
there
is
a
story
there
for
me
that
I
can
create
to
myself
and
so
then
my
second
comment
is:
I'm
I'm
really
hesitant
to
in,
like,
in
this
case,
to
add
descriptions
to
everything
like
why
new
issues
why
new
contributors?
Why
contributor
attribution?
Why
issue
label
inclusivity
and
the
reason.
B
Do
some
of
the
metrics
show
up
in
indifferent?
They
show
up
an
issue
new
and
they
show
up
initial
response
and
they
may
show
up
an
issue
closed.
I
don't
know,
but
it
would
make
the
the
document
huge
and
we're
trying
to.
I
think
we're
just
trying
to
draw
people
to
a
location
where
they
can
think
about
the
metrics
in
really
just
kind
of
concise
ways
that
that
maybe
they
haven't
otherwise
been
able
to.
D
So
I
do
I
do
agree.
I
think
simple
is
better.
So
too
much
too
much
text
content
is
going
to
take
away
from
it.
I
think
the
so
simplicity
in
the
description
and
also
simplicity
in
in
the
models
I
think,
are
better
and
then
to
the
to
the
point
that
she
made
earlier
when
I,
when
I
look
at
this
model.
Yes,
it
tells
it
tells
me
a
story
as
well
as
a
matter
of
fact.
D
It
tells
to
the
point
that
I
was
trying
to
make
is
that
it
actually
tells
me
four
or
five
different
stories,
and
maybe
that's
the
maybe
that's
a
little
bit
the
strength
of
the
model
in
that
it
can
be
interpreted
a
little
bit
differently.
But
the
point
that
I
was
making
is,
it
might
be,
it
might
be
nice
to
to
focus
in
on
those
three
or
four
or
five
stories
that
I'm
seeing
and
create
a
model
specifically
for
those
as
well.
D
So
this
could
be
a
high
level
view
of
issue
handling
and
then
we
could
kind
of
zoom
in
and
look
at
it
from
more
specific
in
more
specific
ways,
and
it
could
even
be
part
of
the
same
model
documents
if
we
wanted
to
yeah.
B
So
that's
we'll
run
into
the
same
thing.
Actually,
it's
interesting
because
we'll
run
into
the
same
issue
on
the
metric
model
that
I
put
together
for
the
dei
event
badging
because,
like
for
event,
badging
they're,
all
the
metrics
and
you
don't
have
to
attend
to
all
of
them.
Each
one
of
them
can
have
like
an
impact
on
the
metric
model
that
is
dei
event
badging.
B
D
And
it
does,
it
does
become
a
problem
of
scope
for
us
when
we're
def
when
we're
creating
these
metrics
models.
So
how
do
we
know?
How
do
we
know
the
scope
that
we're
looking
at?
Are
we
looking
at
it
at
a
high
level
like
this,
or
are
we
looking
at
it
at
a
at
a
lower
level,
or
are
we
looking
at
it
in
in
both
ways.
B
H
I
think
that
there
are
many
there
are
an
infinite
number
of
use
cases
for
the
models.
There
is
no.
There
is
no
one
scope
or
complexity
level
and,
as
as
as
we
learn
how
to
write
these
we'll
do
a
variety
of
kind
of
complexity
levels.
You
know
simpler
ones,
more
complicated
ones.
So,
for
example,
the
why
you
should
care
section
for
some
other
hypothetical
model
might
say.
H
The
influence
of
the
bus
factor
on
on
the
waiting
time
for
issues
to
be
accepted
and
then
the
only
real
metric
would
be
the
bus
factor,
and
I
don't
have
it
open
on
the
screen
right
now,
but
whatever
there
is
that
talks
about
the
the
throughput
processing
time.
So
in
that
case
there
would
only
be
two
metrics
or
maybe
three
at
the
most
that
were
actually
so.
I
think
that,
to
summarize
I
see
this
particular
model
as
being
kind
of
a
proof
of
concept
and
will
develop.
B
D
I'm
not
I'm
not
sure
I
mean
I
I
do.
I
do
see
this
as
a
proof
of
concept,
but
I
even
I
guess
I'm
just
I
don't.
D
D
C
B
B
That
model
was
too
big
needed
to
scope
it
down
to
just
the
issue
component
and
I
think,
we're
just
kind
of
kevin.
I
think
you're
wondering
how
and
you
can
totally
correct
me
if
I'm
wrong
but
like
how
far
down
do
we
scope
it?
You
know
what
I
mean
and
lucas
then
is
saying
we
may
have
metrics
models,
that
kind
of
live
at
different
scopes
and
that's
okay,
right
and
and
we'll
find
the
groove
over
time.
I'm
trying
to
summarize
you
huey
kevin
and
lucas
yeah,
one.
D
Yeah,
I
agree.
I
agree
with
that.
I
think
we
can
have
models
that
exist
at
different
scopes,
but
I
think
we
have
to
be
kind
of
clear
about
what
those
what
those
scopes
are
when
we're
defining
this.
So
I
think
the
the
first
thing
that
I
had
said
was:
I
thought
this
model
was
a
great
high
level
model
because
for
me,
when
I
look
at
it,
I
see
five
stories
and
it's
and
it's
a
great
model
for
that,
because
when
I
looked
at
it,
I
immediately
looked
at
it
and
saw
five
stories.
D
So
it's
a
it's
a
great
high
level
model
for
me
to
understand
kind
of
the
the
whole
issue
handling
process,
but
I
think
there
there
are.
D
There
are
models
that
exist
at
a
lower
scope
here
and
I'm
wondering
how
we
would
connect
those
or
differentiate
between
the
different
types
of
models
that
we
may
create
just
around
issues,
for
example,.
B
Maybe
I'm
okay
with
that,
like
that,
they
don't
need
to
be
like,
I
think,
about
our
metrics.
Some
of
our
metrics
are
they're,
just
like
a
single
thing
and
other
like
of
the
are
small
unit.
Metrics
and
other
metrics
are
considerably
more
complex
and
that
doesn't
seem
to
get
in
the
way
of
how
we
talk
about
metrics,
I
mean:
do
you
see
this
as
a
potential
problem.
I
Okay,
I
think
they,
if
we
at
the
beginning,
set
clear
boundary
with
each
models
with
each
other.
I
mean
it
would
make
this
work
com
complex,
complicated,
because
I
think
think
of
developing
some
software
application
based
on
some
libraries.
I
I
So
why
don't
we
just
do
not
too
restrict
on
the
definition
on
the
different
matrix
model
and
put
people
more
thinking
of
how
how
many
new
things
or
new
matrix
model
comes
up
based
on
those
matrix
libraries,
I
would
call
it
matrix
mod
matrix
language
at
this
time.
Yeah.
B
B
Okay,
thank
you.
So
I
have
a
one
myself
there's
a
link
here.
B
B
You
have
existing
metrics
model,
then
perhaps
you
can
just
capture
some
of
those
exactly
my
my
only
a
couple
of
my
questions
that
kind
of
came
from
this,
because
this
is
a
fairly
easy
model
I
think
to
define
is
whether
or
not
we
should
make
a
visual
of
the
metrics
model
optional,
because
there's
not
really
a
visual
for
the
dei
event
badging.
B
B
This
only
has
four
metrics
in
the
current
model,
and
then
I
I
propose.
I
don't
know
what
to
think
of
this
on
the
template
that
we
add
a
section
called
resources,
or
something
like
that,
just
because
this
already
exists,
and
I
wanted
to
point
to
it
as
an
existing
program
already.
I
I
mean,
except
for
this
link,
we
could
put
it
in
the
resources,
whatever
other
things
we
can
it.
I
I
could
imagine
that
it
has
some
connection
with
the
references.
Are
they
the
same.
B
D
In
there,
but
I
don't
think
we
need
references
because
we
are
referencing
the
metrics,
so
we
don't
need
to.
We
don't
need
to
reference
any
external
literature
websites.
We
just
need
to
reference
our
metrics,
so
I
think
I
think
resources
or
I
think,
what's
the
heading,
is
it
tooling
or
implementation
implementation?
That's
what
it's
called
yeah,
so
maybe
the
maybe
that
section
is
implementation.
D
B
Now
there
could
there
there
could
be
a
case
for
references,
and
my
only
thought
here
is
like
I'm
reading
an
opensource.com
article
and
somebody's
like
we
should
look
at
this
metric,
this
metric
this
metric
and
this
metric.
When
we're
thinking
about
this
concept,
I
can
see
somebody
writing
something
like
that
up.
E
Then?
We
can
publish
us
or
write
small
article
on
this
model.
We
develop
and
put
it
for
the
for
the
description
as
a
like
a
marketing
tool
or
a
like
write,
a
small.
Maybe
some
we
can
write
a
small
article
on
this
particular
model
and
publish
it
somewhere
for
the
outline.
K
K
B
Good
anybody
have
any
other
comment.
These
are
so
simple
in
a
good
way.
I
really
like
it
all
right.
Some
updates.
C
H
I
had
two
things
I
just
wanted
to
throw
out
there.
Let's
do
it
one
is
I'm
not
able
to
edit
this
sharepoint
document
because
of
some
weirdness
in
microsoft's
accounts,
yeah,
I'm
having
the
same
problem.
I
I
wonder
if
this
could
live
in
github.
Would
that
be
I?
I
know
that
could
be
really
inconvenient.
E
But
past
what
why
we
have
sister,
the
google,
why
aren't
we
using
the
google
docs
rather
than
word
it
does
so.
D
It's
for
inclusive
access,
and
so
everyone
can
not.
Everyone
can
access.
Google
docs,
okay,
sorry
to
speak
over
you
lucas,.
B
C
H
Yeah
and
thank
you
for
that
right
on
lucas,
you
said
you
had
one
other
thing
I
did.
I
just
thought
I'd
throw
this
out
there,
that
talking
about
ideas
for
metric
models
might
be
a
good
future
agenda
item
like
brainstorming
together.
D
From
a
from
a
process
standpoint,
just
looking
and
digging
into
the
model
that
we
were
looking
at
earlier,
gave
me
multiple
ideas
for
models
around
issues,
so
I
thought
yeah.