►
From YouTube: CHAOSS Common Working Group 3/31/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
Welcome
to
the
march
31st
common
working
group,
I
almost
said
community
working
group.
That
is
not
the
name
of
this.
It
is
common
hi
everybody.
We
have
a
very
light
agenda
today,
so
yeah
I
can
share.
A
If
we
need
to,
I
don't
mind
I'll,
do
that
and
venad
you
were
just
saying
these
action
items
are.
Yours
is
that
right.
C
I
think
we
need
to
table.
We
need
to
table
this
until
after
the
release.
D
C
C
Yeah,
so
I
I
do
have
some
concerns
about
both
of
these,
but
I
think
I
need
to
think
about
them
a
little
more
in
depth,
so
the
the
and
and
we've
talked
a
little
bit
about
those
concerns
prior,
so
the
one
of
the
concerns
is
submitter.
I'm
not
sure
submitter
is
a
is
a
thing
in
in
chaos
anyway,
right,
it's
not
a
it's,
not
a
term
we've
used
in
the
past.
C
So
if
it
is,
if
it
is
a
term
we're
going
to
adopt,
do
we
need
to
define
it?
Is
there
a
term
that
other
working
groups
are
using
that's
better
than
submitter
or
it's
contributed.
C
Yeah,
so
maybe
contributor
is
the
better
word
than
submitter,
but
and
then
we've
we've
already
talked
about
the.
I
think
we
already.
We
also
talked
about
the
some
of
the
inconsistency
across
working
groups
and
how
we
are
dealing
with
time
right.
Some
some
working
groups
like
to
use
the
word
duration.
B
Yep,
we,
I
think,
sorry
to
interrupt
kevin,
but
we
brought
it
in
the
last
meeting
and
after
a
long
discussion,
it
was
again
agreed
that
we'll
go
with
the
time
meeting.
C
I
don't
know
if
that
was,
I
don't
know
if.
C
To
that
or
if
there
was
just
lazy
consensus
on
not
doing
anything
yeah,
so
I
do
so.
I
do
still
have
a
little
bit
of
concern,
but
I'm
willing
to
table
those
concerns
as
we
because
we
are,
we
are
going
and
looking
at
the
metrics
as
a
whole,
matt
and
elizabeth,
and
I
think
sean
is
going
to
take
part
in
that
as
well.
I
think
part
of
that
process
can
look
at
the
how
the
metrics
kind
of
fit
together
across
the
working
groups
and
consistent
use
of
language
and
things
of
that
nature.
C
So
I'm
I'm
willing
to
table
my
concerns
for
a
while,
but
but
I
would
like
to
reiterate
that
I
do
have
a
few
concerns
about
these
two
metrics.
A
I
think
that
was
on
my
my
action
item
is
to
create
a
style
guide
with
that
guidance
of
like
how
do
we
define
stuff
and
how
do
we
use
our
language,
but
I
haven't
even
started
that
at
all.
So
that's
going
to
be
like
another
thing:
we
do
after
this
release.
I
think.
C
I
think
one
of
the
one
of
the
nice
outcomes
of
the
knowledge
base
is
that
we
can
possibly
create
a
a
glossary
online
and
maybe
that
glossary
can
be
populated
just
by
like
automatically
populated
through
some
sort
of
the
scraping
of
our
existing
documents.
C
Kind
of
the
because
one
of
the
because
one
of
the
one
of
the
things
we're
doing
in
the
new
template
we
we
now
have.
We
have
that
that
header
for
synonyms
so
it'd
be
interesting.
If
we
could
scrape
the
document
grab
the
metric
title
and
grab
the
sentiment
synonyms
and
maybe
also
grab
the
description.
C
So
that
metrics
that
had
been
defined
could
automatically
be
added
to
the
glossary
with
synonyms
added.
B
C
C
Yeah,
I'm
okay,
letting
it
stew
and
honestly
I
I'm
okay.
At
this
point
I
would
even
be
okay
pushing
this
into
a
release
with
the
idea
that
some
of
the
work
that
we're
doing
to
to
look
at
the
the
metrics
as
a
whole
could
resolve
some
of
these
issues
and
when
we
start
when
we
start
mapping
mapping
the
relationships
between
these
metrics
and
and
looking
for
language
consistency,
then
then,
perhaps
some
of
these
answers
resolve
themselves
right.
C
So,
for
example,
if
we
were
to
if
we
were
to
go
and
take
a
look
at
every
metric
right
now,
that
has
to
do
with
change,
requests
and
kind
of
put
them
in
a
bucket
across
the
working
groups.
Yeah
we
would.
We
would
notice
that
some
of
the
language
is
off,
but
once
we
have
them
in
the
bucket
we
can
we
can
figure
out.
We
can
figure
out
where
the
language
is
off
and
fix
it,
and
maybe
that
maybe
that
means
changing
some
of
the
the
names
of
the
metrics.
C
Maybe
it
means
editing
the
metrics,
but
I
think
that
would
be
a
when
we
that's
another
benefit
of
the
knowledge
base
is
that
we
have
we'd
start
to
have
the
ability
to
create
these
different
types
of
buckets
to
organize
these
metrics
into
and
when
we
start
doing
that,
we're
gonna
we'll
start
to
see,
inconsistencies
and
the
ways
that
these
metrics
fit
together
in
the
ways
that
they
they
don't
fit
together.
A
A
C
Check
the
check
the
metrics
document
itself,
I
wonder
if
they
used
a
are
they
using
a
static
or
a
dynamic
yeah
there?
It
is.
C
D
A
C
C
C
Full
url
yep
it.
C
Yeah
and
within
the
within
the
documents
we
we
could
hide
the
we
can
hide
the
links,
but
at
the
end
that-
and
I
think
this
is
this-
is
from
a
reference-
isn't
it
yeah
yeah?
So
I
think
that
the
full
url
is
correct
here.
Yeah.
B
A
A
What's
this
comment
again
track
status
as
an
evolving
metric
over
time.
C
A
Yeah
yeah,
I
don't
know
yeah
and
then
armstrong
was
like
yeah.
It
looks
good,
so
I
don't
think
we
need
to
necessarily
add
any
words
to
the
metric
to
track.
A
C
C
Moving
from
a
occasional
contributor
to
a
core
contributor
to
an
occasional
contributor
to
a
core
contributor,
so
so
moving
between
those-
maybe
that's,
maybe
that's
something.
That's
not
explicitly
stated
in
the
metric.
The
idea
of
the
idea
of
tracking
an
occasional
contributor,
as
they
become
a
core
contributor
or
tracking
a
core
contributor,
as
they
become
an
occasional
contributor.
A
Would
that
be
this
repeat?
Occasional
contributors
like
someone
who's
becoming
an
occasional
contributor
more
than
once,
is
that
what
that
means.
C
D
C
Based
on
this
definition,
right
because
we've
we've
kind
of
split
those
two
things
so
there's
the
core
contributors
that
the
people
that
are
that
are
constantly
contributing
to
a
project
and
then
they're
the
occasional
contributors,
the
people
that
sporadically
contribute
or
do
the
I
know,
drive-by,
isn't
the
correct
term,
but
they
they
come
and
they
make
a
contribution
when
they
need
to,
and
then
they
disappear
for
a
period
of
time
right,
okay,
so
man,
maybe
they
don't
come
back.
A
C
C
They
don't
have
a
value
associated
with
them,
saying
that,
like
for
the
the
number
of
the
minimum
number
of
contributions
before
someone
is
no
longer
an
occasional
contributor,
that
filter
doesn't
differentiate
between
that
person,
whether
they
stopped
contributing
or
whether
they
became
a
core
contributor
right.
C
There's
no
value
attributed
to
those
filters
as
far
as
directionality
goes,
so
maybe
it's
already
there.
It's
just
built
into
the
metric.
We
just
okay,
it's
just
not
explicitly
stated.
A
On
that
reference
link
that
yahoo
we
brought
up
this
we'll
clean
it
up.
Did
we
say
we
wanted
to
clarify
that
a
little.
C
A
A
Does
does
somebody
want
to
take
that
action
item
to
submit
that
pull
request
like
I
can
do
it
if
nobody
wants
to
do
it,
it's
fine
yeah.