►
From YouTube: CHAOSS Common Working Group 3/3/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
Welcome
to
the
chaos
common
metrics
meeting
for
thursday
march
3rd,
we
have
we've
got
a
few
things
on
the
agenda
today.
Actually
so
maybe
I'll
just
share
my
screen
and
we
can
go
ahead
and
get
started.
A
Okay,
so
the
first
thing
we
have
on
the
agenda
is
to
review
the
action
items
for
last
week,
so
we
have
sean
who's
going
to
take
a
look
at
how
to
create
labels
across
metrics
the
metrics
working
groups.
A
Okay,
I'm
just
gonna
move
that.
B
A
Let's
go
move
that
here
not
yet
so
we
have
them
for
next
week,
matt
you're,
going
to
explore
the
impact
of
issue
and
pr
templates
across
repos.
C
No,
I
also
didn't
do
that.
Okay,.
C
I
guess
part
of
it:
I've
been
thinking
a
little
bit
about
like
we
might
want
to
think
about
how
we,
I
don't
know
like
there's
so
many
different
repositories
and
there's
so
many
different
ways
that
people
work
in
those
repositories
for
a
fair
reason,
so
for
like
the
way
that
obviously,
the
software
works,
the
way
that
the
translations
repo
works.
This
is
quite
different
than
maybe.
A
E
A
A
Org-Wide
relatively
detailed
issue
templates
and
somebody
else
was
like
I
don't
like
these,
I
don't
want
it
don't
make
me
take
it
and
we're
like
all
you
have
to
do
is
just
override
it
with
a
blank
one
or
one.
That
just
says.
A
A
Yeah,
it
doesn't
use
the
top
level
one
at
all.
It
only
uses
the
the
one
at
the
it's
the
same
thing
with
like
code
of
conduct
right,
if
you
have
a
group.
C
C
A
That,
if
it's
named
the
same
thing,
then
it
won't,
you
won't
see
it
at
all.
C
A
D
B
B
A
Okay
and
then
other
action
items
elizabeth,
you
were
going
to
re-examine
the
handbook.
F
Yes-
and
I
I
did
that,
but
I
have
a
blocker
right
now,
because
there
it's
unclear
how
we
actually
add
or
change
information
in
the
handbook
like
we
make
that
change
in
the
repo
and
it's
not
translating
over
into
the
actual
front-end
display
of
the
handbook.
So
I'm
reach,
I
have
reached
out
to
josh
gratt.
He
got
back
to
me,
but
has
not
gotten
back
to
me
again
with
the
solution,
but
he
does
know
that
we're
having
that
problem.
So
hopefully
he
responds
pretty
quickly
and
we
can
move
forward.
F
A
F
C
Also,
I'm
sorry
this
also
raised
the
thing
we
should
probably
do.
We
need
a
master
document,
I'm
sorry.
We
need
a
main
document
that
kind
of
has
like
our
login
to
zoom
that
has
our
login
to
twitter.
C
Are
a
little
distributed
and
we
need
to
probably
fix
that
and
maybe
have
it
in
the
like
some
sort
of
board
level
directory
or
something
like
that.
B
Okay,
yeah,
I'm
back,
I
can
see
your
screen.
Okay,
I
know
for
the
google
summer
of
docs.
The
process
is
basically
not
anything
like
google
summer
of
code,
so
the
biggest
difference
is
that
they
give
us
money,
and
then
we
disperse
it
to
a
tech
writer
that
we
hire
and
we
only
can
submit
one
project
per
organization.
B
A
C
Can
I
just
say
what
it
means,
so,
basically,
what
this
is
is,
as
we
have
gsac
students
or
season
of
doc
students
or
outreachy
students.
We
we're
not
handing
off
to
the
mentors
really
well,
the
students
are
just
kind
of
vanishing.
Occasionally
it
works
okay,
and
so
we
just
need
to
communicate
to
the
mentors
that
part
of
the
mentoring
process
like
not
only
requires,
for
example,
building
the
handbook,
but
then
creating
really
something
that
is
a
handoff
document.
A
C
I
didn't
do
that
quite
yet.
This
is
the
so
we
have
templates
that
are
currently
in
the
metrics
repo,
okay
and
then
we
have
templates
that
are
in
the
community
repo,
but
I
didn't
want
to
just
move
them
quite
yet,
just
because
I
think
we're
still
kind
of
sorting
that
out.
G
A
Okay
and
then
we
had,
let's
see
kevin,
was
going
to
coordinate
a
meeting
conversations
about
the
roles
of
these
three
repos,
the
metrics
community
and
github.
E
There
appears
to
be
no
interest
on
slack
in
that,
so
I
guess
I'll
throw
that
back
to
you
all.
So
I
reached
out
and
got
no
replies.
A
So
is
this
something
that
so
sorry
I
missed
the
last
meeting.
This
is
probably
my
fault.
What
what
do
we
need
to
sort
out?
What
was
the
purpose
of
the
meeting.
E
So
it's
kind
of
connected
to
some
of
the
conversations
that
we've
just
been
having.
Primarily,
it
is
what
is
the
purpose
of
the
community
repo?
So
what
do
we
want
to
store
in
the
community
repo?
What
do
we
want
to
store
in
the
dot
github
repo?
E
A
A
A
Assuming
we're
going
to
shut
the
metrics
we
go
down,
I
mean
there's
kind
of
unique,
there's,
there's
sort
of
a
standard
set
of
things
that
typically
go
in
the
community
repo
for
a
project
the
size
of
chaos,
governance,
folder
being
being
one
of
them.
I
I'm
happy
to
participate
in
that
meeting,
maybe
kevin
you
me
and
matt
could
just
meet
and
sort
of
yeah
a
little
bit
for
me.
E
Yeah,
I'm
I've
got
a
pretty
good
availability,
so
whatever
works
best
for
you
all
yeah.
A
A
There
were
a
lot
of
action
items
last
week
and
I
think
the
other
two
action
items
are
in
things
that
we're
actually
going
to
talk
about
in
this
meeting.
So
we'll
skip
those
for
now
since
they're
actually
on
the
agenda.
So
we
can
hit
the
action
items
when
we
let
me
get
to
those.
A
Okay,
I
think
I
didn't
realize
we
had
a
project
board
for
this.
C
A
I
like
project
boards,
I'm
plus
one
count
me
in
I
assume
they're
pretty
much
populated
by
issues
you.
A
And
that's
an
open
discussion
item.
I
feel
like
there's
not
a
lot
to
talk
about
here
and
we
have
more
important
things
on
the
agenda.
So
maybe
we'll
just
call
that
one
good
metrics
release
kevin
we're
all
set
from
common
working
group.
Correct.
A
So
this
is
also
your
twice
a
year
reminder
that
it's
helpful
to
review.
Metrics
excuse
me
from
the
other
working
groups,
so
we
should
all
be
using
this
time
to
review
a
few
metrics
from
some
of
the
other
working
groups
and
provide
some
provide
some
feedback
and
encourage
people
to
review
ours
and
provide
feedback
as
well.
A
So
we
have
two
two
items,
so
we
have
some
metrics
in
progress
that
are
both
time
waiting
for
metrics
and
we
also
have
the
organizational
diversity
metric
and
those
are
both
yours,
which
order.
Would
you
like
to
do
those
in.
G
Yeah
before
we
go
to
the
order
I'll
say
for
revisiting
metric,
I
think
it
was
decided
that
matt,
kevin
and
elizabeth
are
going
to
review
it,
so
I
haven't
looked
at
it
for
revisiting
the
matrix
okay.
G
So
as
far
as
other
two
items
are
concerned,
time,
waiting
for
submitter
action
is
ready.
I
just
need.
I
have
made
some
comments,
so
we
can
review
that
and
finalize
it
in
today's
meeting
and
the
other
is
like
a
same
thing.
It's
a
flip
other
side
of
a
coin.
So
so,
once
we
finalize
the
time
waiting
for
submitter
action,
it'll
be
easy
for
me
to
work
on
the
other
one.
A
Okay,
well,
since
we
want
to
review
the
time
waiting
for
some
interaction
in
this
meeting,
do
you
want
me
to
stop
sharing,
so
you
can
share,
so
you
can
drive
that
conversation.
Is
that
all
right.
G
C
E
Yeah,
I
actually
agree
with
the
nod
on
this
there's
a
there.
We
have
a
lot
of
these
time
waiting
for
metrics,
I
mean
they're
they're
like
four
or
five
of
them,
and
we
are
very
inconsistent
in
how
we're
naming
them.
A
E
E
B
A
G
Okay,
so
here
the
goal
is
like
once
reviewer
has
reviewed
the
change
request,
how
long
it
takes
the
submitter
to
submit
the
response.
That
is
the
goal
to.
We
won't
assess.
D
A
A
G
So,
like
the
main
crux,
is
this,
and
then
we
have
the
objectives
like
understanding,
whether
submitter
is
willing
to
work
or
submitter
is
feeling
too
criticized,
or
you
know
and
like
just
wanted
to
assess.
These
are
the
objectives
that
has
been
mentioned
in
there.
G
Other
than
this
title
I
felt
the
metric
is
ready
and
developed.
There's
a
one
comment
which
is
like
organization
making
the
change
of
press.
Is
it
always
an
organization
or
it's
an
individual
who
is
making
the
change
request
representing
an
organization.
G
C
D
D
G
C
B
G
D
E
So
one
of
the
edits
that
was
just
made
was
changing
it
to
date
and
time,
so
the
title
currently
is
just
time.
Looking
at
common
there,
oh.
E
C
E
A
Oh
time
to
first
respond
some
time
to
close
yeah
yeah.
We
also
have.
We
also
have
duration
ones
too.
So
I
don't
know.
G
F
I
feel
like
there
is
a
little
bit
of
a
difference,
though
be
between
duration
and
time,
like
the
duration
is
like
the
wait.
Go
back
to
that
screen.
You
were
just
on
yeah
sure
if
you
don't
mind,
thank
you
like
the
review
cycle
duration.
So
it's
like
yeah.
It's
time
passes,
but
it
to
me
it's
like
a
different
connotation.
It's
like
a.
I
don't
know
how
to
say
it
put
it
in
words
but,
like
the
the
whole
package
of
the
the
whole
thing
is
going
into
this
duration.
A
I
absolutely
I
absolutely
agree
with
you.
I
think
I
think
duration
is
like,
like
the
the
whole
thing
so
the
time
it
takes
to
do
some
like
big
big
thing,
like
the
the
time
from
here
to
here,
yeah,
whereas
I
feel
like
time.
Two
is
the
time
it
takes
until
you
get
to
like
the
thing
so
the
time
to
first
response,
the
time
to
close
yes
and
so.
G
G
E
E
E
G
C
F
I
think
it's
way
for
me
personally,
it's
way
clearer
time
waiting
for
a
submitter
action
like
that,
tells
me
exactly
what
that
is,
or
you
know
time
to
close.
That
tells
me
exactly
what
that
is,
and
it's
it's
not
like.
I
think,
duration
again
is
like
how
long
something
lasts
and
not
you
know
like
how
long
did
that
whole
review
cycle
last.
That's
why
we're
using
duration
there,
so
I
think
it's
okay
to
use
time
waiting,
in
my
personal
opinion,
it's
okay
to
use
it,
because
it's
clear
yeah.
E
Yeah,
if
this
is
a
subset
of
that
other
one,
then
it
definitely
needs
to
be
discussed
and
I'm
okay
with
I'm
okay
with
the
time
as
well,
rather
than
duration,
I
recommended
we
look
at
it
last
meeting
just
for
consistency
sake,
so
I'm
I'm
fine.
Coming
to
this
conclusion
I
will
say
the
the
submitter
action
is
a
little
bit
odd
for
me,
so
it
wasn't
immediately
clear
that
we
were
talking
about
change
requests,
but
maybe
that's
okay,.
E
I
think
it's
it's
submitter
action
right,
because
the
this
is
actually
so.
It's
the
amount
of
time
that
it
takes
the
submitter
to
make
the
edits
and
respond
to.
G
E
E
D
D
C
D
D
G
E
E
Yeah
and
even
you
know
moving
forward
when
we
when
we're
creating
these
metrics,
I
think
the
I
think
that's
definitely
something
that
should
be
considered
the
are
we
using
the
time
to
or
are
we
using
duration,
or
are
we
using
some
other
form
of
some
other
naming
convention
for
these,
and
I
think
it's
okay
to
use
both
I
just
especially
if
they
mean
slightly
different
things
in
for
the
metric.
A
A
It
is
the
glossary
is
it
is
it?
Is
that
intended
to
provide,
like
just
general,
like
chaos
terms,
or
is
that
intended
to
provide
consistency
across
metrics?
I
feel
like
the
two
have
slightly
different
purposes
like
there's,
a
general
purpose
glossary
that
if
people
are
trying
to
understand
what
something
means
and
then-
and
this
is
more-
I
see
this
more
as
metric
style,
guide
kind
of
things
that
you
would
see
like
big
companies
like
when
we
talk
about
this
product.
We
talk
about
it
in
this
way,
and
it
means
this.
A
F
F
A
You
are
just
leaps
and
bounds
ahead
of
the
rest
of
us,
okay,
so
elizabeth
to
look
at
creating
a
style
guide
with.
C
C
E
E
And
then
to
the
the
the
glossary
issue
that
was
mentioned
as
well,
I
think,
once
the
knowledge
base
is
built
on
the
website,
it
could
be
pretty
easy
to
populate
a
glossary
on
that
knowledge
base
as
well.
A
A
So
the
organizational
diversity
metric
we're
deferring
that
until
matt
and
elizabeth
deliver
their
memo
to
the
common
working
group
about
our
metrics
and
whether
we
need
to
update
any
of
them.
It
looks
like
the
privacy
ethics
document
is
still
still
in
progress.
I
think
we
were
talking
about
that
in
the.
C
Yeah
it's
actually
coming
along,
so
I
was
this
is
that
I've
been
merging
like
six
different
documents
here
and
so
the
top
is
is
privacy.
So
if
you
scroll
down,
this
is
just
like
intro
like
who
we
are
and
then
there's
this
privacy
section
and
then,
if
you
keep
scrolling
down.
E
C
C
I've
been
the
only
thing
I
couldn't
find,
and
maybe
somebody
is
that
last
one,
if
there's
any
published
guidance
around
ethics.
There's
like
I
find
a
lot
around
ethical
ai
and
I
was.
C
C
Okay.
Well,
then,
just
also
like
maybe
a
general
action
item
to
everybody
here
like
if
you
happen
to
stumble
across
something
with
respect
to
ethics,
not
just
like
an
article
but
actual
you
know
like
not
an
article
like
ethics
are
important,
but,
like
some
guideline
like
here
are
the
things
to
think
about
with
respect
to
ethics,
just
let
me
know
or
drop
them
in
the
document
or
whatever,
but
I
think
it's
coming
along.
F
Matt,
are
you
in
that
ethical,
open
source
slack,
no.
C
C
F
F
F
A
A
C
I
will
just
say
a
couple
things
when
my
contacts
with
the
lf
it's.
This
is
kind
of
chaos,
connie,
but
we're
good
with
her
we'll
be
good
with
a
room
for
oss
eu
it'll
be
the
same
as
kind
of
like
what
we
had
in
seattle,
so
it'll,
we'll
probably
do
a
half
day.
I
think.
If
we
go
longer,
we
have
to
pay
for
it,
but
they
provide
a
room
for
a
half
day,
and
then
I
talked
to
brian
about
the
discourse
like
hosting
it.
You
know.