►
From YouTube: CHAOSS Common Working Group 1/20/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
A
I
do
okay
yeah.
You
can
all
see
that
right.
B
A
Okay,
so
this
is
the
first
meeting
of
the
year.
I
think
I
missed
the
last
meeting
of
the
year.
If
I
remember
correctly,
I
did
indeed
so
I
I
kind
of
put
together
sort
of
the
same
same
agenda,
starting
with
kind
of
all
of
the
the
typical
things
like
reviewing
our
pr's
metric
spreadsheet,
I'm
not
sure
where
we
are
with
the
episodic
contributors
or
occasional,
consistent
contributors.
So
if
we
need
to,
we
can
talk
about
that.
A
We
also
had
that
discussion
about
reviewing
older
metrics,
and
we
can
also
talk
about
which
metrics
to
work
on
next,
unless
what
we
want
to
work
on
next
is
the
older
metrics
review.
A
But
before
we
started,
I
wanted
to
ask:
is
there
anything
else
that
we
need
to
add
to
the
agenda
that
people
that
we
really
need
to
talk
about
today?
Are
there
any
burning
things
that
have
come
up.
B
The
only
other
thing
that,
if
we
could
just
talk
about
it
here,
real
briefly
or
at
the
end,
is
the
relationship
of
the
working
groups
with
the
metric
model
working
group,
because
the
metric
models
are
based
on
the
metrics
that
come
from
the
like.
The
common
ddi
evolution
working
group,
we're
just
kind
of
sorting
that
out
a
little
bit.
So
the
as
it's
first
on
the
list.
I'll
just
say
this.
B
So
the
the
idea
is
is
that
in
the
metrics
model,
working
group,
which
again
is
a
a
collection
of
kind
of
these
atomic
metrics
that
we
in
the
working
group
like
like
common,
won't,
initiate
the
conversation
with
the
model
group
that,
as
the
model
group,
is
developing
models.
If
there
are
metrics
that
they
believe
are
not
developed
and
or
potential
candidates
to
be
developed
in
common.
A
C
Cool
a
comment
on
that
so
they'll
be
creating
an
issue
on
the
that
on
a
particular
atomic
metric
that
need
to
be
developed.
Will
they
be
joining
in
helping
figure
that.
B
Out
or
yeah
so
part
of
the
issue,
the
issue
that
would
be
posted,
it
could
be
like
a
preliminary
draft
of
what
that
metric
could
be.
It
could
include
perhaps
the
question,
perhaps
the
objective
of
the
metric.
I
think
there's
enough
of
us
that
are
on
the
metrics
model
working
group.
It's
really
late,
you're
timed
on,
so
you
won't
be
there,
but
like
enough
of
us,
it's
like
6
p.m.
Central!
So
I'm
pretty
sure.
That's
not!
Okay,
for
you.
B
B
A
A
The
apac
I
was
just
thinking
in
the
apac
call
we
we
talk
about
the
models
all
the
time,
so
I
wasn't
surprised
that
it
was
super
late
in
an
asia-friendly
time.
C
A
Oh
that's
great
who's
joining
for
microsoft.
I'm.
D
B
A
I'm
a
fan
club,
that's
so
bad!
That's
what
I
am
anything
else
on
the
metrics,
mama
working
group,
okay,
so
prs
and
open
issues,
no
pull
requests!
That's
great!
You
guys
must
have
been
productive
at
the
end
of
the
year
and
then
the
issues.
A
A
See
this
one
is
more
of
a
discussion.
I
like
that,
we've
labeled
some
of
these
that's
great.
This
is
just
the
standard
release,
notes
one-
and
these
are
these
two
metrics-
that
we've
been
kind
of
working
on
off
and
on
so
anything
here
that
we
need
to
talk
about.
B
A
D
A
Okay,
should
we
just
should
we
just
close
it?
Do
we
need
to
open
anyone.
B
A
I'll
just
tag
kevin
in
it
to
ask
about
whether
we
need
to
open
a
new
one.
Okay,.
A
B
A
A
A
B
Part
of
it
is
just
like
getting
the
color
coding
together.
Some
of
the
color
coding
was,
like
greens,
were
not
with
greens
and
reds
were
not
with
the
reds,
so
I
consider
that
just
a
personal
thing,
I
added
the
versioning
column
there.
So
that's
just
as
we.
If
we
re-release
a
metric,
we
want
to
update
the
version.
We
have
not
talked
about
what
that
revisiting
would
be.
Do
we
just
go
to
version
two.
D
D
A
B
C
B
B
B
And
then,
if
you
scroll
a
little
bit
to
the
right,
I
just
also
made
sure
that
anything
that
we
were
working
on
common-
I
don't
think,
was
had
this
problem,
but
anything
we
were
working
on
was
in
a
google
doc
or
some
shared
doc,
because
we
don't
work
on
metrics
in
github.
They
only
live
on
github
when
they're
under
review
or
released.
A
D
A
D
D
B
A
On
the
on
the
agenda
for
us
to
look
at
what's
what's
the
status
on
the
occasional
inconsistent
contributors.
B
B
D
C
I
recall
regina
and
beth
for
coordinating
on
this.
She
was
working
and
I
was
supporting
that's
what
I
record
lost
yeah.
We
were
communicating.
B
B
A
Today
so
we'll
talk
about
in
the
next
meeting,
if
that's
all
right.
B
A
B
That
should
be
re
reviewed
at
some
point,
and
so
then
this
is
to
elizabeth's
point
as
well
like
there
are
a
few
new
sections
that
we
add
like
one
is
synonyms
if
there
are
any
synonyms
and
the
common
example
well,
episodic
is
really
good,
because
that
there
are
synonyms
for
that
yeah,
the
other
one
was
merge,
requests
or
whatever
we're
calling
them.
You
know
for
change,
requests
or
merge
requests
and
pull
requests.
B
So
it's
just
kind
of
a
walk
through
of
things
to
think
about
when
we're
doing
reviews
of
the
metrics.
So
it's
a
little
bit
clunky
in
the
sense
that
what
what
I
think
we
do
is
if
we're
working
on
a
metric,
so
scroll
up
just
a
little
bit
like
burstiness.
I
know
that's
one
in
there,
so
if
we're
re-reviewing
burstiness,
we
really
can't
use
this
issue
just
for
burstiness,
because
it's
like
there's
there's
a
lot
going
on
in
here.
B
B
A
It's
it's
like
the
big
issue,
that
kind
of
ties,
everything
together
and
then
what
we
would
usually
do
is
we'd
create
like
a
new,
a
new
issue
and
then
mention
it
in
this
issue
that
the
work
on
burstiness
is
happening
in
issue
number
two
whatever
so
so.
This
place
is
like
where
we
collect
all
the
all
the
pointers
to
the
other
pieces:
okay,
but
yeah.
What
you
were
saying
this
is,
as
as
you
were
walking
through
it.
I
was
like.
A
C
A
Yeah,
I'm
going
to
put
a
note
that
we
need
to
put
these
in
each
issue.
Okay,.
A
A
I
think
it
depends
on
how
you
do
it:
okay,
yeah,
okay,
okay,
so.
A
A
I
like
having
this
as
a
checklist,
because
what
we
can
do
is
once
we
so
when
we
create
the
issue,
we
can
put
the
issue
number.
You
know
either
right
before
right
after
this
and
then
once
we've
once
we've
finished
it.
Oh.
A
Are
there
any
of
these
that
we
want
to
start
with?
Are
any
of
these
things
that
people
have
been
thinking
about
wanting
to
update
that?
Does
anybody
want
to
sign
up
to
take
one
of
these.
B
A
A
A
D
B
C
And
I'll
create
a
issue
for
this
and
copy
all
that
stuff.
Okay,.
A
Cool
all
right,
so
we'll
start
with
that
one
and
we'll
start
working
through
it,
and
then
we
can
refine
our
process
before
we
restart
any
others,
and
then
do
we
as
as
a
working
group.
C
A
Well,
this
is
the
second
time
banana
said
exactly
what
I
was
gonna
say
I
I
feel
like
we
were
sort
of
the
overachievers
in
the
last
release,
and
so
we
cranked
out
a
whole
bunch
of
metrics,
and
so
I
agree
with
matt.
I
think
now
is
probably
a
good
time
for
us
to
just
kind
of
focus
on
going
through
some
of
the
older
ones
and
making
sure
that
we
have
solid
metrics.
So
I
will
I'll
split
a
note
that
we're
focused
on
over
metrics.
A
B
I
had
one
other
thing:
just
that
came
to
mind.
We
have
been
archiving
meeting
minutes
that
are
like
from
2019
and
2000,
and
so
the
way
dei
is
doing
it
is
they
just
have
a.
I
forget
what
it
is.
It's
like
meeting
a
meetings
folder
and
then
like
a
2019.md
file
and
then
a
2020.md
file,
and
it's
all
just
copied
over.
So
we
should
probably
do
that
here
too
yeah,
because.
B
B
C
So
I
would
add
like
if
you
want
to
keep
that
google
doc
as
a
mock
time.
There's
a
plugin.
You
can
use
and
it'll
create
the
entire
google
doc
as
a
markdown
for
you
and
you
just
upload
that
markdown
rather
than
formatting
it
or
changing
anything.
You
can
just
do
it
as
a
montage.
C
A
C
Yep,
I
can
share
the
screen
now
it's
option,
just
if
you
can.
C
C
Can
you
see
this
screen
yep?
So
in
the
add-ons
I
have
a
doctor
markdown
there
is
an
add-on.
I
found
it
in
the
firefox
like
for
the
google
docs.
I
just
convert
it.
I've
opened
this
up,
so
if
I'm
pressing
it
convert,
it's
creating
a
dock
and
like
you
can
use
this
in
here
and
about
converting
your
texture
mountain
here.
C
Output
as
a
mountain,
so
you
can
copy
and
save
it,
so
I
can
just
copy
and
save
it
as
and
upload
it
in
a
github
as
a
markdown
and
just
take
the
pieces
that
need
to
be
uploaded.
Okay,
yep,
I
can
just
save
it
as
a
new
page
as
a
markdown
page
and
upload
it
as
a
file
in
the
github
as
a
markdown.
That's
all
I
have
to
do.