►
From YouTube: CHAOSS Metrics Models Working Group 3-1-22/3-2-22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
B
A
B
B
Know
I
think
the
the
meeting
today
is
the
last
meeting.
If
you
recall,
if
I
go
back
here,
we
kind
of
did
some
operational
stuff.
We
talked
about
the
release
process,
we
talked
about
metrics
models
and
toolkits.
Do
you
remember
all
this?
It
was.
It
was
kind
of
operational
like
we
were
thinking
about.
B
Oh,
we
talked
about
like
how
well
that
release
process
like
what
these
should
look
like,
and
I
thought
today
we
could
kind
of
get
back
into
away
from
the
operations
a
little
bit
and
back
to
the
work
that
sean
and
ragava
have
been
doing
with
respect
to
deploying
a
particular
metrics
model.
So
the
idea
here
is
that
we
would
have
like
a
metrics
model,
whatever
it
might
be.
Community
welcomingness-
or
you
know
anything
else,
that's
kind
of
on
this
list
here
and
as
we
develop
them.
A
A
B
A
B
Let
me
let
me
just
stop
you
there
too,
and
I
think
this
is
kind
of
what
we
decided
so
as
we
capture
the
metrics
model
in
this
repository,
the
the
artifacts
that
follow
the
models
would
also
live
in
this
repo.
You
know
what
I
mean
that
we
wouldn't
have
another
repository
called
like
model
implementations
or
something
something
like
that
that
we
just
we
create
subfolders.
So
I
think
I
agree.
A
It
was
relevant
metrics
for
getting
a
picture
of
how
welcoming
a
community
is
and
the
we.
We
took
each
item
that
elizabeth
identified,
for
example,
issue
age
and
identified
the
chaos
metric,
that's
behind
it
and
then
the
end
point
or
other
data
gathering
strategy
that
we
used
to
get
the
information.
In
this
case
out
of
an
auger
instance,
though,
I
think
we
could
do
something
similar
with
gremore
lab's,
sig,
ils
project
or
sigils
project.
A
Time
to
first
response-
and
we
just
kind
of
explain
these
different
places-
that
we
have
data
these
two
metrics
and
then
the
endpoints
that
deliver
them
community
culture.
We
show
the
code
of
conduct,
inclusive
leadership.
We
didn't
have
a
clear
metric
derived
from
data
for
inclusive
leadership
right
now,
so
we
just
right
now,
just
noting
that
in
this
design,
markdown
document
and
then
for
license
coverage,
we
identified
these
examples
for
license
coverage
license
is
declared
under
stability,
the
cii
best
practices
badge.
A
A
We
don't
have
elephant
factor
and
then
we
did.
I
think
some
of
this
is
a
little
out
of
date.
We
have
some
new
contributor.
This
is
actually
a
visualization
endpoint,
which
means
that
it
essentially
brings
up
a
visualization
when
you
hit
it
and
you'll
see
that
in
a
notebook
and
then
change
request
acceptance
rate.
So
this
is
just
kind
of
a
working
document
that
we
went
through
where
elizabeth
identified
the
metrics
to
include,
and
we
went
through
and
identified
where
to
get
the
data
and
then
regava
did
a
good
deal
of
work.
A
A
C
A
C
C
That's
probably
better,
but
the
endpoint
strategy.
So
the
way
I
was
thinking
like
there'd
be
multiple
types
of
things
in
there
at
some
point
right
like
there's
this
one
that
you've
you've
spun
up
to
as
an
example
of
how
to
look
at
issue
age
using
auger.
But
there
could
be
other
tools
or
things
that
you
should
look
at
yeah
yeah.
D
E
C
A
And
why
don't
you
just,
I
guess
the
piece.
That's
in
the
read
me
that
you're
not
seeing
is
how
ragava
started
this
notebook
from
the
command
line
so
and
that's
okay,
because
it's
in
the
readme,
but
just
so
you
know,
jupyter
notebooks
are
kind
of
a
command
line,
startup
thing
at
least
as
far
as
I've
used
them.
There
may
be
other
approaches
available
out
there,
but
this
is
how
we
have
implemented
it
right
now
and
now
I'll.
Let
you
talk.
F
Yeah
thanks
sean,
so
sean
do
you
want
me
to
start
from
the
terminal
or
just
just
start
with
the
job?
No,
you
could
just
go
from
here,
yeah!
Okay,
thank
you
so
me
and
sean.
We
both
collaborated
in
this
thing
and
we,
with
the
help
of
elizabeth,
has
developed
this
thing
and
I've
done
so
with
jupiter
notebooks.
You
get
a
lot
of
code.
A
F
A
F
A
B
B
Would
be
my
guess?
Okay
yeah,
I
mean
that's
interesting.
I
have
a
couple
a
couple
levels
right
because
it
allows
you
to
see
just
go
back
to
that
visual
and
just
go
back.
I
mean
it
tells
you
a
variety
of
things
that
having
having
it
captured
as
part
of
welcoming
this,
I
can
read
this
as
the
community's
getting
pretty
good
at
at
least
responding
to
issues
or
at
least
making
a
comment
on
an
issue.
B
That's
how
I
read
this
again
with
some
hiccups,
but
that's
that's
as
expected
in
community
work,
then
the
nice
thing
is:
is
this
same?
Endpoint
could
show
up
you
know
kind
of
in
a
different
metrics
model
once
we
get
these
developed
because
issue
response
time
could
certainly
mean
something
different:
it's
not
about
welcomingness.
It
could
be
from
a
from
a
community
manager
perspective
like
trying
to
understand
what
that
hiccup
is
on
the
5th
or
the
on
may
of
2021,
and
I
see
something
around
christmas
and
I
see.
B
B
A
F
A
A
Okay,
yeah,
actually,
is
this
the
closed
duration,
or
is
this
the
time
to
first
response?
Do
we
have
this
label
wrong?
This
is
this
is
not
time
to
this.
Is
this
is
issue
resolution
duration
for
gaba,
so
the
so
the
title
is
wrong
on
this
one.
This
is
not
time
to
first
response.
This
is
issue
resolution
duration,
okay,
so
we.
A
A
A
B
F
E
A
So,
there's
a
file
level
licensing
semantic
that
the
spdx
project
in
our
linux
foundation
created
and
this
the
tools
that
we've
built
read
that
header.
If
it's
present
in
the
file
and
it's
difficult
really
to
determine
what
the
license
might
be
on
a
particular
file,
if
there
isn't
a
license
declared,
I
think
the
linux
foundation
is
generally
not
like
to
assume
that
it's
the
license
declared
at
the
project
level.
So
I
think
many
people
do
assume
that.
A
B
A
A
That
seems
like
a
lot
of
licenses,
but
we
have
a
copy
of
each
license
declaration
file
in
our
repository
in
order
to
present
that
as
part
of
the
front
end.
So
that's
how
the
nomo
scanner
must
be
getting
167
licenses,
because
everything
that
we've
developed
is
mit,
but
we
have
one
example
of
167
different
licenses
because
we
have
that
text
file
in
our.
B
B
A
A
So
we
actually
have
the
full
license
declaration
for
a
number
of
different
licenses.
Oh
I
gotcha
yeah,
so
it
ends
up
being
very
very
this.
So
the
statistic
is
pretty
silly
for
augur,
which
is
why
under
licenses
declared,
we
actually
looked
at
gramor
lab
because
fogger
has
167
licenses
and
it's
just
a
mess
and
it's
very
odd
to
have
that
many
licenses
on
a
project.
B
A
So
so
my
thought
of
it,
my
thought
about
it
was.
This
is
how
I
rationalize
that
it
made
sense.
Is
some
people
only
want
to
work
on
projects
with
copyleft
licenses
or
only
work
on
projects
that
fall
into
some
other
category
of
license,
and
so
the
license
that
you
declare
could
reduce
the
number
of
potential
contributors
to
the
project.
C
I
figured
it
was
something
around
like
this
license
is
the
type
of
license.
I
can
work
with
my
and
I
don't
want
to.
I
mean
I
don't
think
it's
important
to
like
debate
all
this
right
now.
I
I
would
just
be
worried
to
have
too
much
under
these
where
it's
like.
You
know.
I
have
a
community
manager
and
they're
like
you
know,
I
want
to
be
able
to
value
community
welcomes
and
then
they
give
them
all
this
stuff
right.
C
They
don't
even
licenses,
never
even
cross
their
minds,
that's
something
that
the
legal
takes
care
of
and
and
that's
just
an
example
of
licenses,
but
even
like
stability
anyways,
I
maybe
just
challenges
to
try
and
be
as
as
like,
simple
or
simple's,
not
the
right
word,
but
you
know
like
I
get
it
well.
Yeah.
C
E
A
Yeah,
I
and
I
think
it's
very
hard
to
present
succinct
to
information
in
a
jupiter
notebook.
So
as
a
metrics
model
example,
it's
perhaps
not
the
ideal
platform
to
work
in
it
was
a
pl.
I
think
it's
a
place
to
start
and
we
should
maybe
think
about
what
other
technologies
can
present
this
information
in
a
more
like
visualize,
you
know,
viewable
on
a
single
page,
I
think,
would
be
a
sort
of
optimal
goal.
B
A
B
I
don't
know
it's
really
good,
and
so
I
agree
with
that.
I
actually
think
we've
had
this
discussion
before,
and
the
nice
thing
is
about
community
welcomingness.
This
has
not
been
released
by
any
means,
so
we
can
certainly
the
other
thing
that
is
really
cool
to
me
here
is
that,
even
if
we
don't
include,
for
example,
cii
best
practice
badging
status
in
community
welcoming
this
there's
now
an
end
point
in
augur
like
this.
Is
there
and.
A
B
A
B
A
B
A
Cool
yeah
there's
there
was
a
lot
in
this
metrics
model.
So,
yes,
we
do
have
the
building
blocks
for
getting
data
in
the
next
metrics
model.
I
think
we
just
maybe
want
to
think
about
what
other
technologies
we
should
consider,
so
we
can
get
it
in
a
page
and
still
have
it
be
easily
like
usable
by
a
normal
person.
B
C
I
had
one
other
like
again
like
out
of
scope
of
this
presentation,
and
I
don't
know
if
I'm
interrupting
it,
but
how
do
we?
I
know
we
talked
about
people
being
able
to
say
like
this
is
how
I
understood
this
and
like
when
you're
talking
about
this
is
when
everyone
went
on
vacation
or
that
kind
of
thing.
How
are
you
I'm
wondering
how
we're
visualizing
that
happening,
or
is
that
the.
C
Yeah
and
I
in
a,
I
think,
there's
kind
of
like
a
couple
different
audiences
like
there
might
be,
if
you
have
a
team
you
might
want
to
like
just
have
like
team
comments
about.
I
mean
we're
working
in
the
open,
though
so
it's
not
really
specific.
But
what
I'm
trying
to
say
is
there's
like
comments
that
are
helpful
to
the
team,
that's
working
with
the
metrics
and
then
comments
that
are
helpful
to
like
other
people
using
chaos.
A
C
C
Again,
like
these,
these
charts
are
great
and-
and
this
is
awesome
work,
but
how
do
we
like
help
people
like
they
might
look
at
it
for
their
project
and
then
they'll
want
to
know?
Oh
well,
how
did
this
work
for
this
other
project,
or
how
did
they
use
this
or
you
know?
I
think
that
that's
the
probably
the
part
I'm
just
excited
about
is
anything.
Is
that
like
sharing,
but
I
think
we're
I'm.
F
B
Next
thing
we
have
so
honestly
like
the
way
yeah,
that's
interesting,
I'm
just
thinking
about
from
a
welcomingness
perspective.
Again,
I
know
that
we're
kind
of
having
these
are
kind
of
two
different
conversations.
One
is
showing
the
endpoints.
The
other
is
how
this
is
related
to
welcomingness,
but
yeah.
A
A
B
A
I
think
that
gets
weird
then
yeah
I
mean
essentially
so
the
cutoff
was
like
for
80
of
the
code
and
if
we
went
to
50
of
the
code,
I
think
you'd
see
like
these
three
here
or
maybe
just
me
and
carter
as
a
bus
factor.
So
it's
I
think,
the
way
that
I've
pro
we've
parameterized.
This
is
understating
auger's
bus
factor
to
some
degree
yeah.
Why
did
it
fix
the
work
they
have
done?
F
A
A
A
Well,
we
we
took
the
model
that
elizabeth
specified
at
face
value.
We
didn't
ask
some
of
the
critical
questions
about
whether
or
not
this
is
really
welcomingness.
We
treat
we
were
analysts
and
tech.
We
were
more
technicians
than
analysts,
just
okay,
here's
the
things
in
this
model-
let's
put
them
all
in
there
uncritically
and
as
many
as
we
can
do
anyway,
and
it
took
some
time
to
have
a
gaba
get
up.
You
know
familiar
with
auger
and
how
to
get
data
out
of
it.
A
It
took
me
some
analysis
time
to
identify
all
the
endpoints
for
the
specific
metrics
and
create
that
metric
endpoint
map,
and
then
we
just
went
through
several
iterations
of
visualize
visualizing.
The
data
and
I'd
say
that
we're
probably
not
done
with
this
yet,
but
we
have
all
of
the
pieces
functional
I've
made
like
eight
notes
here
so
far
about
things.
I
want
to
change
in
it
already,
but
I
think
you
know
it's
like
a
working
model.
B
F
A
A
Okay
and
but
I
think,
subsequent
metric
models
will
be
easier
to
to
develop
and
we'll
iterate
on
them
and
develop
some
sort
of
standard
visual
presentation
which
we
didn't
quite
get
to
in
this
iteration
right.
So
I
think
so
I
think
there's
you
know
upper
this
basically
off
of
zero.
That
was
our
goal.
B
D
A
Should
probably
think
about
whether
or
not
what
other
technologies
we
could
possibly
use
and
reuse
the
python
code
that
we
have
and
produce
something
that
is
more
quickly
and
easily
visually
inspectable,
okay
by
a
user
right
because
having
to
scroll
down
the
page,
doesn't
let
you
think
of
all
the
information
at
once.
It
makes
you
scroll,
and
so
I
think,
like
thinking
about
things
like
that
is
important,
but
this
is
still
better
than
nothing
because
it
can
be
implemented
that
way
by
others
as
well.
B
Like
I'm
trying
to
think
of
as
we
develop
the
metrics
models,
the
markdown
files,
the
non-implemented
markdown
files
right
and
if,
if
the
associated
jupiter
notebook
that
you're
showing
here
is
a
huge,
if
it's
an
extensive
amount
of
labor
like
I
don't
want,
I
think
this
was
like
you
to
feel
like
yeah
there's.
Every
time
we
release
a
metrics
model,
you
inherit
80
hours
of
work,
but
yeah.
A
B
A
New
contributors,
so
this
one's
just
taking
advantage
of
a
visualization
api
endpoint
that
auger
already
has
and
it
just
it,
delivers
the
just
a
visual,
svg
or
png,
and
so
we
just
call
the
api,
get
the
png
and
put
it
in
here.
That's
why
this
one
looks
so
much
different
than
the
others,
the
the
ideal
you
know.
For
me,
the
ideal
world
would
be
that
we
have
endpoints
like
we
take
some
of
this
work
and
maybe
it
becomes
a
visualization
endpoint
and
then
those
can
maybe
be
assembled
on
a
page.
But
that's
that's
auger
specific.
A
I
think
the
other
thing
we
can
do
is
when
we
develop
these
models.
We
could
look
at
gremore,
lab-sig
ils
and
see
what
panels
have
been
developed
that
might
fit
some
of
what
this
metric
model
is
so
like
backing
a
panel
into
a
metric
model
because
there's
like
70
of
them,
so
I
think
we
may
be
able
to
illustrate
some
parts
of
some
models
in
one
to
three
gremore
lab
pages.
B
C
B
A
E
A
B
B
D
A
Cool
theoretically,
it
should
have
been
faster
lucas,
because
I
should
have
known
where
to
look
for
all
these
endpoints
and
how
they
were
mapped,
and
they
were
at
one
point
mapped
directly
to
the
metrics.
But
we
at
the
very
beginning
of
the
project,
maybe
through
2019.
We
were
changing
the
website
so
often
that
I
just
stopped
trying
to
include
a
link
to
the
chaos
metric
in
the
api.
Docs.
C
So
I'll
just
echo
that
that
it
I'm
it's
amazing
that
this
all
come
together.
I
wasn't
expecting
this
today.
I
think
when
I
look
at
the
jupiter
notebooks,
I
think
it'd
be
nice
to
have
a
little
bit
of
a
description
under
there
like
new
contributors.
You
can
use
this
too,
or
this
like
just
some
sort
of
just
to
make
it
more
user
friendly,
like
I
think
for
all
of
us
that
look
at
stuff
like
this
all
the
time
we're
like
oh
yeah,
that's
this,
and
it
means
that
maybe.
D
A
Field
that
we
yeah,
if
you
look
at
the
yeah,
if
you
look
at
the
visualization
endpoints,
I've
always
been
very
directive
about
including
legends
and
descriptions
of
the
visualization,
because
all
all
visualizations
are
hard
to
interpret
without
some
kind
of
legend
or
description
and
fell
away
a
little
bit
toward
the
end
on
this
one.
With
some
of
these,
but
we'll
go
back
and
make
that
more
present.
B
And
I
think
we
can
cover
that
ragava.
Can
you
stop
sharing
your
screen
for
a
second,
so
emma?
If
you,
I
think
one
of
the
things
that
we're
trying
to
do
with
the
metrics
models.
Again,
I
just
keep
going
back
to
the
ddi
event
badging
one,
but
we
have
right.
We
have
the
metric
here
and
then
we
have
a
small
description
as
to
why.
B
C
C
B
B
C
D
Maybe
maybe
we
could
add
some
description
about,
we
could
help
what
kind
of
people
and
because
different
people
have
different
requirements
for
this
metric,
for
example,
if
the
manager,
maybe
they
only
want
the
top
five
people
of
the
project,
it's
enough
and
if
the
maintainer-
and
maybe
they
want
to
know
the
button,
the
button
five
people
of
maintainer
and
they
they
could
find
out.
So
why
the
maintainer,
while
the
maintainer
and
not
contribute
well
and
at
rest
in
the
time.