►
From YouTube: CHAOSS Metrics Models Working Group 3/15/22-3/16/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
A
A
I
think
all
of
these
things
are
connected
a
little
bit
today,
so
let's
just
hold
off
on
taking
a
look
at
this
one
for
just
a
second
we're
gonna
go
to
some
of
the
ones
that
emma
had
put
together,
which
was
responsiveness
and
project
safety.
I
think,
is
what
it's
being
called
now
at
this
point.
So,
let's
take
a
look
at
responsiveness.
C
B
So
yeah,
I
changed
why
you
should
care
to
why
it
matters
more.
It
was
on
the
safety
side.
It's
like
it
just
felt
like
the
wrong
language
to
talk
about
safety,
so
so
I've
just
been
using
that
and
then
I
put
a
description.
This
was
coming
out
of
the
last
meeting
a
little
bit
where
we
started
talking
about
how
we
would
have
descriptions
relevant
to
the
matrix
model
and
the
atomic
model
that
might
be
slightly
different,
depending
on
which
matrix
model
is
a
part
of
anyway.
B
So
the
description,
I've
written
it,
I'm
not
precious
about
it.
I
also
started
to
do
user
stories.
I'm
not
sure,
that's
what
we
were
quite
calling
them
before,
but
the
reason
that
I,
like
writing
out
user
stories
and
someone
else
had
suggested
this
in
the
chat.
So
it's
not
like
my
idea
was
that
when
we
get
to
the
metrics
mouse
we
can
say
who
that
audience
or
user,
which
users
would
probably
use
that
particular
measurement
or
tactic.
B
B
So
the
audience
speaks
to
the
user
story
and
I
also
found,
as
I
start
to
build
these
out,
I'm
like
oh
wait,
a
minute,
there's
another
user
that
could
use
this
and
actually
like
just
doing
this
format,
helped
me
and
then
description
specific
to
the
focus
area,
so
responsiveness
and
then
so
source.
I
think
I
was
taking
from
sean's
design,
which
is
more
like
okay.
Now,
how
do
you
go
and
measure
that?
B
That's
the
format
that
I
have
right
now
and
I
apologize
I
kind
of
went
on
my
own
journey
here,
but
it
was
mostly
because
I'm
just
trying
to
sell
it
internally
right
like
I
need
to
be
able
to
not
sell
it,
but
it
needs
to
be
able
to
make
sense
to
them.
If
I
just
link
to
a
metrics
chaos,
metrics
page
people
just
kind
of
glaze
over,
I
want
to
be
able
to
give
them
something
that
they
can
click
on
and
go
do
and
I'm
not
sure
that
I
have
that
yet.
D
I
like
that.
I
like
that
better.
I
think
that's
that's
an
appropriate
change
in
regards
to
user
stories.
I've
been
a
I've,
been
a
proponent
of
user
stories
for
a
while.
I
keep
on.
I
keep
on
bringing
them
up.
However,
as
much
as
I
like
user
stories,
you,
I
think
you
you
pointed
out.
One
of
the
problems
you
have
with
it
is
as
you're
writing
this.
You
keep
on
coming
up
with
more
user
stories
and
more
more
people
that
maybe
this
this
can
connect
to.
So
it.
D
Yeah,
so
for
me,
scoping
scoping.
The
model
is,
is
kind
of
an
issue
where
we
we
constantly
need
to
fight
to
not
over
scope
it,
and
so
so
I'm
wondering
if
so.
I
like,
I
like
having
the
user
stories,
but
I'm
wondering
if
how
we
rain
that
in
so
that
we're
not
trying
to
do
everything
with
the
user
stories
or
not
trying
to
identify
every
single
type
of
user,
that
this
would
be
important
for.
E
A
B
B
What's
a
one
like
art
scale
like
people,
don't
know
what
to
do
with
that,
and
so
I
feel
like
we
need
to
get
much
more
specific
to
help
those
folks
I
mean
maybe
you're
right.
There
could
be
100
different
users,
but
I
literally
cannot
take
those
and
give
them
to
anyone
right
now,
as
they
are
even
ones
I've
written
like
the
leadership.
B
C
Maybe
we
can
keep
the
user
stories
and
with
disclaimers
some
of
the
stories
are
these:
if
you
apply
it
in
your
context,
you
can
create
a
pull
request
or
suggest
those
as
a
head-on
to
model
as
it
evolves.
So
maybe
we
know
one
or
two
or
three
stories.
We
have
kept
it
here,
as
emma
has
put
in
there
and
to
help
the
user.
Maybe
there
are
different
perspective,
the
same
model
can
be
adopted
by
different
users
and
they
can
suggest
to
add
their
line
or
like
stories.
They
have
used
it
as
a
starting
thing.
C
E
So
when
I
look
at
change
request
responsiveness,
I
think
there
are
two
kinds
of
responsiveness
people
care
about.
One
is:
how
quickly
is
there
a
comment
or
acknowledgement
of
the
change
request,
and
the
second
is
what
is
the
time
to
close,
and
perhaps
what
is
the
review
process
and
how
does
that
vary
by
the
two
key
variables,
I
think
would
be
how
large
is
the
pull
request
and
whether
or
not
the
person
making
it
has
already
made
a
contribution
to
the
project.
A
A
This
is,
and
so
the
like,
ultimately
in
emma,
you
can
tell
me
if
I'm
wrong,
but
ultimately
like
when
you
put
when
you
put
when
you
talk
about
chaos
metrics
to
a
group
of
people
one
is
they
want
to
agree
that
measuring
this
would
be
helpful
in
their
context,
which
I
think
we
we've
overcome.
I
I
think
we
can
tell
that
story,
but
the
second
is
just
tell
me
how
to
do
it
then,
like
tell
me
how
to
implement
it
like
I
just
I
just
want
to
click
the
thing
and
that's
it.
B
B
But
there's
like
a
header
that
says
you
know
this
this
this,
then
we
just
feed
it
in
it
could
be
even
inner
source
type
projects
and
we
just
feed
it
into
this
front
end
and
it
gives
us
something
and
other
people
use
it
and
other
people
are
like.
Oh,
I
fed
this
data
in
and
you
know
like
there's
that
shared
thing
that
for
us
it
would
be
a
win
like
to
have
a
repo
like
that.
B
F
D
I
think
the
conversation
we're
having
right
now
is:
what
do
we
need
to
put
in
that
bridge
that
that
gets
us
to
that?
The
the
application
right,
the
practical
guidance,
whether
that's
auger,
software
or
or
a
toolkit?
That
tells
you
exactly
how
to
to
to
measure
these
ideas
right.
So
so
I
think
so.
This.
D
A
A
A
E
A
I
think,
with
talking
through
the
notebooks
they're
they're
good
for
people
who
are
technically
comfortable
like
day
in
and
day
out,
but
I
think
if
we
just
provide
the
notebooks
like
honestly,
I'm
not
a
big
person.
If
I
look
at
a
notebook,
I'm
going
to
be
like
yeah
like
now.
What
like
do?
I
have
to
install
auger
and
jupiter
and.
B
B
Could
we
create
a
power,
bi,
query
and
custom
language
where,
because
people
are
happy
to
press
click
on
a
query
like
you
know,
it's
not
that
it's
technical,
it's
the
problem,
just
maybe
like
it's
just,
but
it's
great
sean
like
it's
still
like
people
when
you
show
it
to
them.
They're
like
yes,
but
then,
when
you
like,
leave
them
in
a
room
alone
with
it.
It's
like.
D
Well,
so
what
what
are
the?
What
is
the
purpose
of
the
toolkit,
because
I
thought
the
purpose
of
the
toolkit
was
to
basically
provide
guidance
for
those
situations
where
blogger
software
or
remorelab
doesn't
provide
the
answer
right.
The
toolkit
could
help
you
create
a
survey
to
answer
these.
The
the
questions
that
you
have
or
the
tool
could
could
point
you
towards
a
jupiter
notebook,
for
example.
If,
if
that
particular
model
doesn't
exist
in
augur,
is
am
I
wrong
in
thinking
that.
E
The
tool
kit
would
be
at
that
level,
or
so
I
think
I
think
what
we're
looking
for
is
a
way
to
actually
not
have.
People
have
to
mess
with
any
of
the
back
endy
stuff,
where
they
would
just
have
a
page
where
they
could
log
into
an
auger
account
or
basically
a
chaos
account
they
could
take
them
to
the
auger
or
more
lab
implementation
for
their
repos.
Like
that's,
that's
I
think
what
people
are
looking
for.
E
D
B
D
Okay,
so
so
I
think
that
still
holds
up
with
what
I
said
that
the
metrics
models
that
we're
working
on
are
the
bridge,
the
bridge
between
the
metrics
and
the
tool
kits
or
the
auger
software
right.
So
so
the
question
then
becomes:
what
do
we
need
in
the
metrics
model
that
that
can
act
as
that
bridge
between
what
needs
to
be
there?
Do
we
need
to
have.
B
G
B
B
B
There's
a
bunch
of
different
ways:
you
can
do
something
the
toolkit
will
list
all
those
things.
Some
of
them
might
be
easy
right.
That's
why
I
have
like
the
difficulty
some
of
them
might
be.
You
have
to
spin
up
an
august
instance.
Some
of
them
might
be
able
to
run
a
survey.
Some
of
them
might
be.
Oh,
you
click
this
link
and
change
the
thing.
B
A
F
A
G
B
B
A
Well,
let's
say
that
if
I
look
at
responsiveness
this
one
here,
sean
could
you're
really
loud
sorry
on
issue,
responsiveness
or
wait
on
just
responsiveness.
We
have
change,
request,
responsiveness,
issue,
responsiveness,
discussion,
forum,
okay,
so
all
of
those
are
things
that
could
be
measured
from
auger
right.
B
You
know,
because
I
kept
coming
and
my
other
in
the
safety
one
I
kept
coming
across
things
like
psychological
safety
and
I'm
like
oh
auger,
doesn't
do
some
evaluation
of
sentiment
and
I
felt
like
there
was.
There
were
tool
kind
of
things
that
we
could
use
as
well
yeah.
But
I
didn't
know
where
to
what
that
would
be.
B
A
A
No,
that's
so
like
if
we
I'm
thinking
like
okay,
pretend
like
at
microsoft,
like
you,
showed
somebody
this
and
you're
like
no
like.
Oh
okay,
that's
cool,
and
then
you're
like
here
are
the
metrics
that
comprise
this.
I'm
like!
Okay,
that's
super
cool
too
and
you're,
like
click
on
that
button,
and
it's
going
to
take
you
to
the
auger
instance
and
you
just
put
in
your
repos
and
they'd,
be
like
oh
that's,
sweet.
B
A
A
Is
that
is
that,
okay,
in
one
of
these,
like
from
your
perspective,
if
we
were
at
microsoft
and
you're
like
so
this
here's
this
metric
model
and
to
get
this
data,
you
need
to,
in
part
run
a
survey
and
part
go
to
auger
impart
whatever
do
something
else
like
does
that?
Does
that
get
to
be
too
tenuous
of
an
ask
for
people?
Do
you
think.
B
B
I
will
create
one
survey,
for
this
is,
you
know,
would
probably
be
an
ass,
but
I
think
if
we
were
to
have
sort
of
example,
pages
or
example,
surveys
that
people
could
grab
from
and
and
and
there's
just
some
direction
like
wherever
there's
just
you
know
some
direction,
that's
like
make,
you
know,
build
a
bear
or
something
good
thing.
I
don't
know.
C
C
Two
metrics
data
can
be
collected
through
this
way
and
for
fourth,
you
have
to
do
a
survey
for
a
survey
sample
question
you
can
find
them.
This
is
what
the
toolkit
was
trying
to
do
it.
I
guess
so.
Maybe
we
can
merge
it
over
here
and
say
how
to
collect
the
data
or
analyze
it
as
a
separate
section
rather
than
within
each
individual
section,
or
we
have
each
individual,
and
we
can
collectively
say
two
data
can
be
obtained
through
chaos.
A
B
No,
but
I
I
think
I
think
again,
if
it's
more
like
at
high
level,
there
are
two
different
types:
ways
that
we
will
suggest,
or
you
know
like
at
a
high
level.
People
like
there's
two
two
ways
that
I'll
be
asked.
You
know
one
of
those
ways
is
a
survey
and
there's
examples
of
those.
The
other
one
is:
is
a
systems
link
and
there's
a
link
to
that.
A
B
A
A
B
F
That's
what
I
was
going
to
say,
like
I
think
in
when
we
were
developing
metrics,
that
include
a
survey
the
we
just
gave
sample
questions,
because
I
think
the
conversation
was
that
we
actually
didn't
want
to
provide
a
sample
for
a
couple
of
reasons.
One
being
we
didn't
want
people
to
just
brainlessly,
do
it
like
we
wanted
them
to
be
mindful
in
the
way
that
they
craft
a
survey
specific
to
their
communities
so
like
we
wanted
to
make
sure
that
they
were
thinking
about
what
they
were
doing
essentially,
especially
with
regard
to
dei.
F
You
know
that
they
want
to
ask
those.
But
that
being
said,
I
think
it
might.
There
might
be
an
extra.
I
know
we're
having
a
hard
time
trying
to
decide
at
what
like
how
far
we
handhold
people,
because
I
think
that's
really.
Our
challenge
here
is
is
how
far
are
we
taking
this
or
how
you
know?
And
so
I
think
what
we
might
do
is
for
each
of
these
individual
tool
kits
they
would
kind
of
be
static.
F
I
I
think,
and
someone
correct
me
if
I'm
wrong
so
like
for
each
metric,
there
is
a
tool
kit
and
it's
pretty
static
and
it
kind
of
goes
with
the
metric
and
then
that
block
gets
plopped
into
different
metric
models
as
needed.
But
what
we
might
insert
is
like
an
extra
layer
like
if,
if
you
scroll
up
to
the
top
mat
so
like
on
on
this,
why
it
matters
user
stories
all
this
stuff.
F
Maybe
we
provide
one
survey
for
this
metric
model
that
pulls
bits
and
pieces
from
those
chunks
that
need
surveys,
and
then
here's
the
stuff
you're
going
to
pull
from
auger
and
here's
a
list
of
all
the
things
that
you're
going
to
the
trace
data
that
you're
going
to
pull
from
auger,
and
so
like
it's
at
that,
like
higher
level,
instead
of
having
them
go
through
each
tool.
Kit,
there's
like
a
a
guide.
A
A
F
And
we
could
tailor
it
specific
to
that
model
so
that
somebody
could
look
at
the
metric
model
and
say:
okay,
it's
going
to
take
me
overall.
It's
going
to
take
me
30
hours
to
implement
this
metrics
model,
and
here
are
the
different
blocks
and
here's
how
long
each
one's
going
to
take
and
then
I
can
decide
am
I
going
to
do
all
of
these?
Am
I
going
to
do
some
of
these?
What
pertains
to
me?
A
F
And
then
again,
if
we
wanted
to
do
a
sample
as
an
emma
said,
you
know
just
to
make
it
easier
for
people.
Well,
then
we
could
maybe
provide
an
example
that
has
those
different
things
all
wrapped
in
one
survey
and
say
here's
the
example.
This
survey
goes
with
this
metrics
model
and
it's
a
compilation
of
these
three
survey
based
metrics.
C
I
have
a
one
comment:
we
are
you
putting
these
in
the
blog
if
you
scroll
down
in
the
individual
metric,
yes,
here,
like
sources
or
ways
to
do
it,
and
then
we
are
here
are
the
things
I
think
we
we,
as
a
group
should
decide
like.
Should
we
keep
it
as
an
individual
metric
level
or
as
a
collective
entire
model
level.
C
A
C
B
B
When
I
wrote
the
description,
I
would
write
like
how
how
like
inclusive
leadership,
you
know
applied
to
project
safety.
How
govern
like
how
that
applied
to
that
specific
thing,
but
it
might
apply
differently
like
if
there
was
a
recognition
thing
at
some
point
like
how
you
talk
about
leadership,
it
would
be
different
description
and
maybe
anyways.
I
just
want
to
say
that
that's
how
I
was
thinking
about
whether
that
answers
your
question
or
not.
I
don't
know.
A
A
D
Up
here
you
know
what
I
mean
well,
the
collectiveness
is
the
the
model
or
the
toolkit
right,
so
the
whole
of
the
the
whole
of
this
document.
Okay,
but
the
the
individual
data
points.
The
surveys
are
the
tools
I
think
you
have
to.
You
have
to
look
at
those
individually,
just
as
a
as
a
practical
as
a
practical
thing,.
A
C
A
A
B
You
do
as
well,
because
you
know
what
is
the
first
thing
I
almost
think
of.
Like
I
don't
know
the
answer
again
like
what
is
the
hello
world
version
of
some
of
this
stuff,
where
someone
gets
it
working,
they
test
it,
they
feel
like.
Oh,
okay,
I
know
how
to
run
this
tool
or
I
know
how
to
like
do
that
thing
and
then
they
grow
and
wouldn't
it
be
cool,
as
I
know
that
people
actually
start
to
understand
the
format
and
then
get
contributions.
F
F
Emma
to
your
point,
I
had
the
same
thought
when
I
was
doing
the
dei
badging
toolkit,
because
there
are
things
in
there
that
are
like
the
baseline.
You
absolutely
have
to
have
a
code
of
conduct.
Absolutely
you
know,
but
there's
no
way
to
indicate
that
it's
just
kind
of
all
like
here
are
all
these
things.
You
can
do
totally.
B
B
Yeah,
so
I
started
like
trying
to
play
with
difficulty,
which
obviously
doesn't
apply.
If
there's
a
bunch
of
different
things
you
can
do,
but
then
maybe
it's
all
like
foundational
or
something
like
that
or
lots
all
the
attributes
might
be
helpful
and
that's
what
I
hear
too
is
people
just
want
like
what
is
the
baseline?
How
do
I
I
want
to
start
building
on
something.
A
A
A
E
E
A
D
Were
unmuted
there?
Oh
yeah,
I
was
going
to
say
something
earlier
and
I
didn't
want
to
interrupt
so
I
was
just
quiet
generally
my
general
feedback
on
this.
Is
I
I
love.
I
love
the
the
way
it's
going.
I
love
the
discussion.
I
love
the
the
inclusion
of
tool
kits
in
the
metrics
models
and
and
user
stories
in
matrix
models.
D
B
I'll
just
speak
for
the
work
here
in
front
of
you,
and
I
agree
that
that
it
was
a
third
document
and
that
I
have
muddied
the
waters
here
by
blending
them
both
and
I
apologize.
I
don't
think
I
feel
strongly
either
way,
but
I
I
was
just
trying
to
get
something
in
that
I
yeah,
so
I
apologize.
I
still
think
that
well.
D
D
A
It's
the
way
to
go.
I
know
that
we
had
talked
about
simplicity,
but
I
I
feel
like
at
this
point,
putting
it
together
is
probably
actually
simpler
than
maintaining
a
different
document
which
is
called
tool
kit,
so
we'd
have
a
the
metrics,
the
metrics
models
and
the
tool
kits,
I
think,
bringing
it
all
together
here
makes
more
sense
to
me.