►
From YouTube: CHAOSS Common Working Group October 27, 2022
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
Okay,
thank
you.
Thank
you
because
I
am
not
I
was
logged
in
earlier
and
then
someone
else
logged
in
and
I
got
locked
out.
So
all
right,
so
time-based
metrics
review.
A
And
I
know
I
made
some
changes
to
some
of
these
last
time
in
I
can
share
my
screen
here.
Oh
someone
else
is
here
on
their
screen.
Excellent.
A
A
Go
back
to
the
working
group,
yeah,
so
I
think
we
I
think
we
have
a
framework
for
coming
up
with
with
these
in
terms
of
using
duration
and
time
or
at
least
I
feel
like
there
were
clear
suggestions
in
that
spreadsheet.
That
Matt
was
sharing
a
minute
ago.
A
So
historically,
we
we've
not
used
duration
and
time
in
a
consistent
way
and
so
I
think
Kevin
had
an
action
item
to
add
it
to
the
template
and
met
was
going
to
file
issues
to
rename
three
metrics.
B
D
A
Think
Matt
submitted
issues
to
the
like
I,
have
a
memory
of
going
into
the
evolution
and
risk
ones
and
making
those
changes.
I
mean
I.
C
D
You
want
me
to
bring
it
up
at
the
community
meeting,
just
so
people
know
or.
A
Yeah
so,
like
I,
think
I
missed
the
evolution
meeting
and
they
missed
the
issue.
I
have
just
put
it
in
the
chat.
I
have
a
pull
request
with
one
change
for
evolution
here.
A
Well
at
least
I
thought
I,
please.
Oh
somebody
else,
okay,
yeah
and
so
I
think
you
know,
I
made
the
changes
that
were
requested.
A
I
did
not
okay,
well,
I,
don't
know,
I,
don't
think.
Did.
A
Okay,
so
now
it
is
tied
to
an
issue.
A
So
I
think
if
I
think
we
can
just
merge
this
okay
merged.
A
B
B
This
probably
needs
to
be
turned
into
a
markdown
file
very
stored
in
the
Community
handbook,
and
when
that
happens,
the
the
link
should
probably
change
now.
General
guidance
is
one
to
two
context:
areas,
oh
sorry
and
three
to
five
Search
keywords.
B
B
So
asking
firm,
comma
delineated,
there's
just
a
little
bit
of
guidance
on
the
keywords,
basically
related
terms
and
synonyms.
B
It's
not
meant
to
be
a
definitive
list
and
then,
if
we
scroll
down
so
I
kind
of
cleaned
up,
some
of
the
formatting
guidance,
so
the
the.
D
B
B
You
want
me
to
yeah,
so
under
metrics
naming
we
have
some
general
guidance
on
the
naming,
so
the
the
name
of
the
metric
should
be
the
same
in
the
metric
heading
file,
name
so
on
and
so
forth.
B
E
Oops
is
there
like
capitalizer
lower
letter
instruction,
because
we
keep
all
the
letters
as
a
lower
letter
as
that's
what
I
recall
in.
B
B
Oh
never
mind,
I,
don't
know
what
I
was
thinking,
I,
don't
yeah
I,
don't
think.
There's
it's
not
explicit
guidance
to
use.
Lowercase,
though
yeah.
E
Maybe
we
can
add
a
mention
of
keeping
it
lowercase
yeah.
B
Yep-
and
it
looks
like
we're,
why
are
we
not?
Is
there
something
weird
with
the
with
the
bullet
points?
Aren't
working
and
now
are
we
gonna
code?
Is
this
like
a
code
block?
Yes,
that's
weird.
C
B
Must
have
already
been
like
that
so
okay
I'll
fix
that,
but
the
but
the
naming
convention
for
time-based
metrics
is
what
we're
looking
for
here
right.
So
it's
time
to
event
and
that
event
should
be
italicized
and
then
the
description
there
is
the
amount
of
time
until
something
happens.
My
example
is
time
to
First
Response.
Okay
event
divert
event.
Duration
event
is
italicized
amount
of
time
that
something
takes
example,
issue,
resolution
duration
and
then
the
last
one
italicized
event
age.
The
amount
of
time
that
is
passed
or
an
unfinished
activity.
B
A
That
looks
good,
yeah
I.
Think
if
you
just
post
a
link
to
that
and
I
under
next
to
AI
Kevin
added
to
the
template,
then
yeah.
B
And
then
my
my
goal
here,
what
I
edited
them
was
to
kind
of
make
some
of
that
stuff
a
little
bit
clearer,
because
the
the
guidance
for
embedding
images
was
kind
of
put
together
with
the
guidance
for
tables
and
lists,
so
I
I
kind
of
cleaned
it
up
a
little
bit.
However,
everything
is
in
a
code
block,
apparently
so
I
need
to
figure
out.
Why
that's
happening
or
what
the
reason
for
that
was.
E
So
can
you
clarify
what
is
being
italicized
in
this.
B
B
Yes,
the
event
aventus
italicized
in
all
of
those
for
all
of
those
names
right,
so
the
the
guidance
is
that
event
is
the
event.
Is
the
thing
that
we
are
measuring
right.
C
B
Time
to
some
event
or
it's
the
duration
of
an
event
or
it's
the
age
of
an
event,
and
this
is
how
we,
and
so
this
is
how
we
would
come
up
with
the
names
for
those
time-based
metrics.
So
if
you
look
at
the
the
example
there
you
have
time
to
First
Response
the
event
is
the
First
Response
right.
Okay
in
the
second
example
issue,
resolution
is
the
event.
E
E
So
we
have
to
italicize
the
issue
or
the
first
response.
B
E
We
have
to
italicize
the
title
to
make
it
more
explicit.
Oh
that's
what
my
confusion
was
no.
B
D
B
The
but
I
I
did
it
this
way,
because
I
thought
it
would
be
a
little
more
descriptive.
E
B
Really
I
just
I'll
just
figure
out
what's
going
on
with
the
code
block
and
then
and
then
I
think
it'll
be
fine.
D
B
Yeah
yeah
and
that
just
has
some
general
formatting
in
there
and
I'm
guessing
that
that
code
block
is
there
because
of
the
this
General
formatting
area.
Actually
because
the
the
sum,
the
sum
heading
part
those
with
the
the
alt
text,
link
yep.
So,
okay,
that's
that's
where
we
would
meet
the
block,
so
I'm
not
sure
why
it's
taking
up
so
much
space
I'll
fix
it.
C
A
Other
two
there's
two
I've
put
and
I've
added
I
added
notes
in
the
about
the
pull
request
and
the
spreadsheet,
and
then
I
just
put
the
ones
that
I
think
remain
to
be
done
and
the
ones
that
are
complete.
Okay
in
in
here
just
sure
direct
linking
purposes
all.
B
Okay,
so
when,
when
those
when
that
change
does
go
through,
it
will
break
the
link
on
the
website.
Okay,.
A
A
B
A
C
C
Then,
on
the
website,
because
otherwise
that'll
be
cool
on
chaos,
yeah.
E
E
B
Yeah
they
do.
They
do
do
that
automatic
redirects
on
GitHub,
but
I,
don't
know
how
long
they
I
don't
know
how
long
they
maintain
that,
if
that's
something
that
eventually
goes
away
or
if
it's
just
a
temporary
redirect
or.
A
You
wanna
so
I
think.
Are
there
any
there
I,
don't
think
there
are
any
other
things
under
the
time-based
metrics
of
you
there's
a
new
metric
with
with
some
visualization
with
that
have
had
some
action
items
that
are
done.
So
perhaps
we
want
to
look
at
this
time
waiting
for
reviewer
action,
metric
and
yeah
and.
E
See
where
it's
at
this
is
ready,
so
one
thing
I
need
is
like
we
have
a
synonym
in
this
rather
than
synonym.
We
need
to
have
now
the
tags
and
keywords.
E
Since
we
have
new
template
ready
in
Mars,
so
I
would
rather
make
it
more.
A
A
PR,
why
don't
we
do
I,
spend
like
five
minutes
making
final
changes
in
edits
right
now,.
E
E
So
what
should
be
the
synonym
and
or
I'm
saying
tags
and
keywords
for
this.
E
C
A
What
it
started
editing
before,
looking
at
the
canonical
list,
it's
just
going
Korean
chaos
again
well,.
C
B
E
A
B
Just
it's
just
comma
deliminated
and
that
should
say
context,
tags
and
the
the
bottom
one
will
say:
keyword,
tags.
C
C
B
You
share
the
link
to
the
the
metric
real,
quick.
A
E
Should
we
have
a
time
or
duration
in
the
tag
so
that
anyone
looking
for
any
time
based
metric?
This
should
pop
up
in
that,
like.
E
B
I,
don't
yeah
I,
don't
think
it
was
ever
reviewed
duration.
It's
always
been
time
waiting.
It
was
for
reviewer
action,
yeah,
yeah,
I
think
the
the
time
the
time
waiting
bit
is
the
the
part
that
throws
me
off
so
I'm,
just
I'm
picturing,
someone
and
they're
tapping
their
fingers
waiting
for
waiting
for
a
reviewer
to
finish.
B
I
think
this
is
I.
Think
review.
Duration
is
what
we're
asking
for.
Not
it's
not
it's
not
a
time.
Two.
It's
a
it's
a
duration.
B
E
E
E
E
A
A
B
A
A
B
E
So,
which
is
a
change
request?
Duration.
This
is
like,
within
the
change
request,
a
single
set
of
like,
if
you
have
a
big
change
request,
I
submitted
one
change
request
and
then
I
resubmitted
or
resubmitted
within
that
entire
cycle.
B
E
B
D
I
know
we
internally
call
everything
change
requests,
but
someone
new
to
chaos
that
might
be
coming
from
GitHub.
Would
they
still
be
using
pull
requests
like?
Should
we
be
adding
pull
requests
in
these
keywords?
Yes,
yeah.
C
C
B
C
Because
I
mean
just
from
a
common
MLK
with
it,
but
just
from
a
common
perspective,
this
this
makes
it
a
little
less.
My
comment
are
always
those
metrics
that
kind
of
float
across
all
things
potentially,
and
this
one
certainly
does
I
agree
with
you.
Kevin
kind
of
have
an
evolution
feel
to
it
like
that.
That
kind
of
workflow
of
something
but.
C
C
C
E
C
B
A
person
for
the
meeting
in
the
previous
conversation
I'm
really
glad
we're
adding
a
primary
key
because
I've
been
contemplating
chaos
metrics
database
for
a
while
yeah.
That's
a.