►
From YouTube: CHAOSS Common Metrics Working Group 5/12/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
Community
welcome
to
the
common
metrics
working
group
meeting
for
may
12
2022.
We
have
a
few
things
on
the
agenda
to
talk
about
today.
We
don't
have
a
ton
of
stuff,
but
we'll
review
the
action
items
from
the
previous
meeting
review,
some
open
issues
and
pr's
we'll
talk
about
the
process
for
reviewing
old
metrics.
Although
we
might
not
talk
about
that
because
that's
what
I
think
that
was
shawn's
action
item
and
assuming
the
node
makes
six
he's
usually
a
few
minutes
late
because
of
the
bus.
D
A
D
A
A
D
A
C
A
C
A
Okay
yeah,
so
we
won't
hit
you
with
your
action
items
right
away.
I'll
give
you
we'll
give
you
some
time.
Let
you
get
settled
so
while
we,
while
we
wait,
let's
do
the
pull
requests
because
we
got
several
pull
requests
and
I
wasn't
sure
if
anyone
had
looked
at
these
yet
so,
let's
look
at
them
together,
because
I
had
some
questions
about
them.
I'm
not
sure
who
this
this
person
is.
Are
they.
B
They've
been
recently
very
active
with
respect
to
really
about
the
metrics
revisions.
Okay,
recently,
meaning
the
last
week.
Probably-
and
I
mean
I
think,
the
recommendations,
at
least
in
the
dei
working
group
have
been
in
line
with
like
okay,
so
the
these
I
think,
I'm
guessing.
These
are
revision,
requests
or
revisions
to
existing
metrics
yeah.
A
A
B
D
B
C
B
A
C
D
With
so
with
with
copyright,
the
the
copyright
goes
from
the
date
of
creation
of
the
document
to
the
to
the
current
date.
However,
so
that's
this
style
has
kind
of
gained
popularity
in
website
design
where
you
have
the
range
and
the
yeah
so
the
so
it
would
be
the
the
date
of
creation
for
the
document
or
the
website
to
the
current
date.
However,
it's
also
perfectly
acceptable
to
just
have
the
the
updated
date.
D
A
A
A
A
A
B
A
A
C
C
A
C
A
B
D
B
D
C
A
D
C
D
A
Yeah
we,
those
are
those-
are
github
permissions
so
before
we
before
we
change
that
I
mean
so
the
way
we
do
it
in
a
lot
of
cncf
projects.
Is
we
don't
necessarily
use
the
the
github
permissions?
We
we
tend
to
use
bots
that
control
all
the
things,
as
you
know,
and
within
so
I
wouldn't
say,
bots
or
viewer
type.
Whoever
take
that,
but
within
a
lot
of
the
the
cncf
projects,
we
have
board
members,
we
have
reviewers
and
we
have
maintainers
as
like
the
the
roles.
C
D
C
C
A
Yeah,
okay,
so
I
would
say
that
we
should
add
bots
as
something
that
we
filter
by
as
something
separate
from
the
reviewer
role
yeah,
because
so
the
bots
can
have
a
significant
amount
of
time.
So
there
are
a
lot
of
like
automated
ci
jobs
that
in
projects
like
kubernetes
and
k-native,
those
the
ci
jobs
can
take
a
little
while
to
run
and
those
those
could
skew
your
results.
If
you're
not
filtering
filtering
out
the
bots.