►
From YouTube: CHAOSS Common Working Group Jan 19 2023
Description
Minutes from this meeting can be found here: https://docs.google.com/document/d/1xsii5tfmmDwWpuhrFcBJMeYeT3RipJdiCdHrbi0NalQ/edit
A
Gas
community,
thank
you
so
welcome
to
the
January
19th
chaos
community
meeting
we
have
an
action-packed
agenda
and
I
will
share
my
screen
just
to
make
it
easier
to
go
through.
A
Okay,
so
first
question
on
the
agenda:
should
we
archive
our
minutes?
On
the
one
hand,
it's
nice
to
start
fresh
at
the
beginning
of
the
year.
On
the
other
hand,
we
meet
every
other
week,
so
we
don't
have
a
ton
of
like
the
documents,
not
super
long
49
pages,
I
guess
what
do
people
think.
C
E
A
Time
based
metrics
review,
so
it
looks
like
I
know.
You
said
you
updated
the.
A
C
D
A
E
G
Back
there,
let's
focus
on
amazing,
but
if
the
fox
is
there,
maybe
the
it
is
not
a
very
good.
It
is
not
very
good
news
because
it
means
that
the
folks
didn't
find
I
pray
in
the
in
the
forest.
So.
A
Yeah
we
actually,
we
actually
live
right
on
a
Green
Space,
so
surprised
that
we
hadn't,
because
there's
all
there's
all
kinds
of
trees
like
right
next
to
where
we
live.
Yeah
we're
cool,
okay,.
A
Oh,
oh,
anybody
have
any
feedback
before
I
go
ahead
and
merge
this.
A
Okay,
that's
done,
and
that
was
our
only.
That
was
our
only
pull
request,
so
we
will
yep.
So
that's
done
and
merged
cool
metrics
models,
like
I
said
I
actually
actually
did
some
I
did
some
work
in
between
now.
Did
this
get
talked
about
in
the
metrics
model
meeting
your.
H
I,
do
we
sorry
I
haven't
posted
the
video,
yet
that's
my
bad.
We
did
look
through
it.
We
had
a
very
small
group.
There
was
only
four
of
us
there
so
and
like
yahui,
wasn't
there
or
you
know
any
any
of
the
other
like
core
core
members,
so
we
did
look
at
it.
H
I
think
the
resolution
was
that
this
group
would
also
look
at
it
and
like
finalize
it
and
then
maybe
back
one
more
time
at
metrics
models
to
just
give
it
the
final
okay,
but
it
looked
really
good
like
we
were
yeah,
just
kind
of
like
yeah.
This
is
awesome
so
that.
C
Part
I
remember,
I,
think
there
was
one
metric
that
needs
to
be
developed
before
even
we
finalized.
This
I
guess
was.
E
C
B
E
A
I
did
but
it's
a
really
really
good
point,
so
what
I
did
was
I
added
this
bit
after
you
commented
on
the
on
the
issue.
A
About
data
collection
strategies,
because
you
make
a
good
point-
I
mean
not.
Everybody
releases
puts
releases
in
the
same
places,
so
I
think
it's
up
to
the
project
to
decide
where
they
want
to
collect
this
from.
A
Let
people
read
through
this
and
just
put
comments.
Suggestions.
Do
you
want
me
to
kind
of
walk
through
it?
Do
you
have
a
a
preference,
probably
how
we
do
this.
F
A
Let's
do
that,
let's
give.
Let's
give
it
a
few
minutes.
Just
have
a
look
I'm
going
to
drop
the
link
in
the
chat
so
that
you
can
leave
your
feedback
on
it.
A
A
A
A
I
I
However,
this
is
not
a
free
frequency.
Frequency
metrics
are
not
one
that
we've
discussed
prior
we've
discussed
and
if
we,
if
you
scroll
down
to
the
bottom,
the
guidance
is
in
the
template.
That's.
I
That
you're,
making
kind
of
yeah
so
I'm
so
I'm
wondering
if
we
should
add
guidance
based
on
this
naming
so
that
in
the
future,
when
we
have
frequency
metrics,
we
can
use
a
similar
naming
policy
and
maybe
based
on
the
guidance
that
we
have
now.
Maybe
it's
the
maybe
the
the
guidance
would
be
event
frequency
if
you
scroll
down
to
the
you'll,
see
the
right
there.
The
naming
convention
for
time-based
metrics
time
to
Event,
Event
duration,
event,
age
and
maybe
we
add
a
line
that
is
event
frequency.
I
E
A
H
You
can
give
me
that
action
item
if
you
want
to
put
that
in
them
many
minutes
I
can
make
that
change
to
the
template.
Sure.
F
I
That's
that's
what
I
was
thinking,
but
at
the
same
time
I
was
kind
of
I
was
opening
up
for
discussion,
so
I
don't
know
if
that's,
but
something
along
those
lines.
The
frequency
frequency
is
what
I
grabbed
simply
because
that
was
the
that
was
actually
the
definition
of
release.
Cadence
it
was
released.
Cadence
is
the
frequency,
so
so
just
get
rid
of
cadence
and
just
say.
Well,
if
your
frequency
is
the
definition,
let's
just
use.
A
C
We
used
to
have
synonyms,
but
now
we
have
tags,
so
we
can
say
Cadence
as
a
tag.
E
A
C
Yes,
okay,
yes,
but
I
was
like
one
thought
that
came
to
my
mind
is
like.
Is
it
just
focus
to
the
software?
For
example,
we
are
releasing
the
metric
and
updating
it,
so
we
have
different
versions
or
even
so
is
it
just
and
we
are
not
releasing
the
software.
We
are
releasing
an
artifact,
so
should
we
call
it
a
software
or
artifact,
not
sure.
B
C
B
C
Maybe
we
can
write
something
like
our
defect,
something
like
this
release
of
their
software.
Slash
artifact,.
E
That
I
would
yeah.
F
A
F
F
H
I
I
have
a
quick
question.
Sorry
when,
when
we
do
this
search,
someone
remind
me,
does
it
look
at
it
doesn't
look
at
the
question.
It
will
only
look
at
the
keywords,
because
we
don't
we
don't
have
software
in
there.
Do
we
need
the
word
software
as
opposed
to
like
Community,
or
is
that
would
that
be
a
context?
Tag
I
can't
remember
on.
I
It
does
not
search
the
the
document
externally
that
I
that
I'm,
aware
of,
although
there
there
may
be
some
cash
searching,
but
we
haven't,
we
haven't
been
able
to
get
a
definitive
answer
on
that.
Yet.
E
A
A
I
think
these
changes
all
look
good.
Does
anybody
anybody
object
so.
F
C
A
A
D
A
F
A
F
E
D
E
A
A
E
A
C
C
E
I
We
do
we
do
some.
We
do
sometimes
add
text
in
between
the
implementation,
header
and
the
filter
header
that
that
describes
the
implementation.
I
So
we
we
could
describe
the
implementation
in
there
as
well,
if
it
makes
more
sense
to
just
straight
up
kind
of
describe
what
we,
what
what
it
is,
we're
measuring,
although
that
should
be
in
the
definition
as
well
so.
I
So
if
it's
in
the
definition,
I
would
say
it's
not
necessary,
but
if
there's
any,
if
there's
a
specific
implementation
that
we're
describing,
then
we
could
add
that
guidance
here
as
well,
but
I,
don't
I,
don't
think
it's
necessary
I
think
the
the
definition
is
fine
and
then
the
filters
are
very
descriptive.
A
So
Sean
you
suggested
replacing
the
period
with
a
colon,
but
the
rest
of
them.
I
used
I'm
cool
with
I'm
cool.
B
With
whatever
I
don't
have,
a
strong
opinion
is.
A
E
F
B
F
A
Well,
that
is
super
inconsistent,
so
let's
just
fix
that
how
about
if
I
fix
it
with
I'm
gonna,
reject
that
one.
E
E
A
So
those
are
just
a
kind
of
a
couple
of
comments
about
the
tools.
Maybe
do
we
still
have
Luis
on
the
call
Luis
are
you
still
he's
looks
like
he's
still
here?
Yes,.
C
A
He
is
thank,
you
does
does
groomer
lab,
have
have
this
data
about
the
releases.
A
Okay,
so
auger
auger
has
it,
but
apparently
it's
not
in
the
we.
A
Now
so,
okay,
so
I'm
just
gonna
resolve
this.
So
we've
got
a
visualization
that
yuhui
created
from
OSS
compass.
So
we've
got
that
here
and
then
I
have
the
visualization
from
auger
using
my
weird
weird
graphics,.
C
A
Yes,
so
I
would
say
that
the
reference
is
this
lightning
talk.
Is.
C
E
G
A
Do
it
yeah
perfect.
A
D
C
B
C
D
A
Fix
that
later,
okay,
any
any
final
thoughts
on
this.
E
A
Okay,
now
we
have
the
basic
project:
Health
metrics
model,
now
that
we
have
the
release
frequency
metric.
A
B
A
So
let's
just
spend
five
minutes
and
have
a
look.
E
A
And
so
so.
I
I
A
The
metric
specific
insights
section
is
where
this
is
all
documented,
so
each
one
of
these
has
some
thoughts
on
why
it's
important
and
so
that
that's
all
in
the
insights
section,
okay,.
C
B
A
Okay
and-
and
you
know
to
get
back
to
vanilla's
question,
so
these
These
are
the
four
metrics
that
I've
been
using
because
I
feel
like
it's.
It's
a
representative
group
of
a
small
metric,
small
small
set
of
metrics
that
that
captures
kind
of
you
know
across
various
areas
of
the
project.
Kind
of
four
things
that
I
think
personally
are
are
particularly
important.
So
getting
at
Sean's
comment
is
you
know,
responding
responding
quickly
to
things
so
that
people
feel
like
their
contributions
are
welcome.
A
So
we
get
more
contributors
actually
taking
the
time
to
close
pull
requests,
even
if
they're
not
merged,
but
closing
them
with
you
know
not
merged
or
whatever
I
think
helps
so
like
the
the
first
one
is
like
the
response.
Time
is
really
designed
to
make
sure
that
you
know
people
are
seeing
some
engagement
initially
with
their
metrics.
The
time
to
close
is
a
signal
that
a
project
is
not
getting
behind.
A
So
sorry,
yeah
time
to
close
is
more
around
making
sure
they're
not
getting
behind.
So
if
they're
there's
never
closing
PR's,
all
of
a
sudden,
the
PRS
are
gonna
back
up
and
they're,
going
to
end
up
with
a
big
pile
of
abandoned,
pull
requests,
which
is
not
not
what
you
want
to
see
on
a
project.
A
A
You
know,
in
addition
to
like
bug,
fixes
and
new
features,
but
it's
it's
making
sure
that
the
any
security
updates
are
actually
Landing
in
a
release
where
the
user
can
pick
it
up.
Yeah.
A
C
Yes,
it
now,
it
makes
perfect
sense,
but
I
have
a
little
like.
Maybe
my
opinion
on
the
bus
factor
is
like,
but
I
feel
bus
factor
is
a
little
more
complex
than
a
basic
metric.
How
about
adding
number
of
contributors
or
some
kind
of
showing
the
country?
But
though
bus
factor
is
focused
on
the
contributor
aspect,
but
I
feel
it's
more
complex
or
more
higher
level
than
a
general.
C
A
number
of
contributors
like
how
many
contributors
are
actively
engaged
in
the
project
or
some
other
measure
of
the
contributor,
rather
than
a
bus
Factor.
It's
just
my
two
cents.
C
B
B
Have
a
super
strong
opinion,
I
think
if
you
looked
at
number
of
active
contributors,
you'd
end
up
with
essentially
the
data
that
Lies
Beneath
bus
Factor
instead
of
the
bus
factor
and
I,
don't
I
don't
have
a
strong
opinion
about
whether
or
not
that's
a
good
thing,
I
think
if
the
bus
Factor
looks
bad,
it
maybe
compels
you
to
look
deeper.
You
know,
for
example,
if
it
comes
out
to
like
one
that
might
compel
you
to
really
look
a
little
bit
more
deeply
into
the
project.
B
B
So
yeah,
like
I,
said
I,
don't
have
a
strong
opinion.
Yeah.
A
G
Yeah,
thank
you.
Well,
I
I
do
have
a
strong
I,
strong
opinion
about
about
bus
factor,
and
it
is
one
of
the
key
metrics
and
just
as
an
example
when
the
AC
Foundation
was
a
study,
what
they
call
the
pony
factor,
which
is,
is
the
same
as
as
we
are
defining,
but
the
bus
factor
in
chaos.
They
got
the
result
for
open
SSL,
which
is
the
this
area
was
two
or
one
so
yeah
I
think
it
was
it
was.
G
I
Yeah
I
think
bus
Factor
may
be
more
relevant
when
we
look
at
the
different
sizes
that
projects
can
be
as
well
so
I
think
bus
factor
is
relevant
for
small
projects.
Bus
factor
is
relevant
for
large
projects,
whereas
when
when
we
start
when
we,
if
we
were
just
looking
at
the
number
of
active
contributors,
the
relevance
of
that
number
may
be
or
the
way
we
understand,
that
number
is
probably
going
to
be
different
for
small
projects
versus
large
projects,
so
that
I
think
the
bus
Factor
kind
of
works
in
in
different
contexts.
I
A
Cool,
so
let's
go
ahead
and
just
just
kind
of
start
through
this.
A
H
B
No,
no
I
think
that
was
Sean
like
his
keyboard,
while.
A
He
was
on
the
page
without
realized,
not
a
problem,
and
this
was
a
question
I'll
leave
that
answer
in
case.
He
hasn't
seen
that
yet
because
it's
time
zones
are
hard,
let
me
go
and
resolve
this
one,
because
that
was
from
a
while
ago.
There
was
a
question
about
the
type
of
contribution,
and
so
what
I've
tried
to
do
in
this
is
be
as
consistent
as
I,
possibly
can,
with
the
actual
definition
of
these
individual
metrics,
so
I've
tried
to
be
consistent,
says
defined
that
one
we've
resolved.
I
Is
there
a,
is
there
a
way
we
can
better
kind
of
differentiate
the
title
of
this
metric
Maybe
kind
of
separate
it
from
that
that
idea
of
basic
health
metrics
model.
I
So
if
there's
some
way
that
we
can
differentiate
this
model,
even
if
it
was
just
a
matter
of
calling
it
like
the
the
Foster
Health
metrics
model,
or
something
like
that,
so.
F
H
I
mean
to
be
fair,
like
as
a
community
manager
personally
I,
don't
know
that
this
model
would
necessarily
apply
100
like
bus
Factor
may
not.
I
may
care
more
about
the
demographics,
for
instance,
of
our
contributor
base,
or
something
like
that
you
know
so,
maybe
maybe
it
is
specific
to
hospitals,
I,
don't
know
I'm
just
throwing
that
out
there
yeah,
but.
A
I,
actually
you
so
you
say
that
and
I
I
think
maybe
I
should
delete
the
community
manager
one
because
I
actually
don't
encourage
our
community
managers
to
use
my
metrics
I,
encourage
them
to
install
something
like
so
we're
using
the
turkey
ad
we're
using
grimmar
lab
for
the
community
managers,
because
they
really
need
to
like
dig
into
every
single
aspect
of
the
community,
and
this
is
way
too
simple
for
a
community
manager.
What
about
something
that
incorporates
project
risk
in
the
title,
because
I
think
what
this
metrics.
B
B
A
I
I,
actually,
don't
want
to
call
it
risk,
mainly
because
we
have
a
working
group
around
risk
and
I
think
that
will
be
confusing
for
people,
because,
while
I
do
focus
on
on
risk
as
a
part
of
this
I,
I
kind
of
yeah
I
think
the
focus
should
be
project.
Health,
health
and
risk.
C
B
I
I
I
made
suggest
instead
of
Simple
Start.
The
word
starter
because
I
think
I
think
that's
kind
of
the
intention
here.
Yes,.
I
I
E
D
B
B
A
B
A
I
A
Okay,
so
who,
since
I
since
those
are
at
midnight
my
time,
does
someone
want
to
take
the
action
item
to
just
bring
it
back
into
the
metrics
model
working
group
and
discuss
it
for.
A
A
B
A
There
I'll
just
I'll
just
how
about
if
I,
just
bring
all
of
this
back
into
the
into
the
next
meeting
next
meeting,
yeah
and
so
I
can
contribute
our
location
on.