►
From YouTube: CHAOSS Common Working Group 10-14-21
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Great
all
right
welcome
to
the
october
14th
2021
chaos,
common
work
group
meeting,
and
so
for
those
of
you
that
are
new
to
this
work
group
welcome.
We
do
have
live
transcript
available.
So
if
you
down
at
the
bottom
of
your
zoom
channel,
you
see
the
live
transcript
button
and
if
that
is
something
that
you
would
like
to
use,
it's
there
for
you.
So
that's
great!
A
If
you
could
it'd
be
great
if
you'd
like,
if
you
could
add
yourself
to
the
minutes
so
just
type
your
name
in
there
and
maybe
even
tell
us
how
you're
doing
it's
something
we
normally
add
so
like
if
it's
a
nice
day
or
something
like
that,
I'm
getting
rid
of
a
really
old
printer,
something
you're
doing
today,
whatever
it
might
be.
A
B
C
A
A
All
right
so
today
you
know,
I
think
the
primary
thing
for
today
is
to
take
a
look
at
at
the
common
metrics
so
as
as
we
may
know
we're
getting
towards
the
end
of
our
release
period
kevin.
A
I
think,
you're
looking
to
have
these
things
kind
of
done
by
today
slash
tomorrow
from
each
of
the
working
groups,
so
we
can
get
the
metrics
published
on
the
web
page,
so
that's
cool,
and
so
we
need
to
kind
of
take
a
look
at
the
metrics
that
the
common
working
group
has
been
developing
over
the
course
of
the
last
six
months
and
just
see
if
there's
any
last
comments
and
just
one
final
push
to
make
sure
that
we're
done
in
that
regard.
A
A
A
It
looks
like
we
have
two
two
four
six,
seven
metrics
that
we're
releasing
out
of
common
as
tagged
by
this
label
all
right.
So
let's
take
a
look
here
and
we
can
also
take
a
look
at
our
minutes.
A
A
A
Because
then
we
can
kind
of
sign
off
on
this
yep,
I'm
doing
it
right
now.
Okay,
thank
you
and
maybe
you'll
be
I
see
you
had
another
action
item
around
technical
forks,
so
I'll
speak
slowly
as
we
go
through
collaboration
platform
activity.
B
Yeah,
so
so
what
I'll
do
is
like
I,
I
know
I
have
these
two
action
items
whatever
I
I
know
them
exactly
so
I'll
try
to
resolve
them
by
three.
That
is
why.
A
All
right
collaboration
platform
activity,
let's
go
back
and
take
a
look
at
that
one.
A
F
F
F
We
discussed
the
general
naming
conventions
for
that.
I
don't
know
if
that
was
here
or
elsewhere.
It
was
here.
We
did
talk
about
yeah.
The
the
naming
convention
that
we
landed
on
for
images
is
weird,
I
think,
that's,
I
think,
that's
something
we
need
to
go
back
and
reevaluate.
F
I
do
not
want
to
make
this
change
now,
because
I'm
actually
gonna.
I
have
to
go
through
this
weekend
and
change
every
relative
link.
I
saw
that
absolute
links,
so,
although
I
suppose,
since
I'm
making
that
change
anyway,
I
could
well
I
couldn't.
I
could
do
that.
F
Yep,
so
the
the
collaboration
platform
activity
metric
does
need
to
be
edited
okay,
so
there
are
a
few.
If,
if
you
look
at
the
the
issues,
yep
ray
ray
was
kind
enough
to.
D
D
G
A
All
right:
well,
let's
take
a
look
at
what
it
is.
Let's
see
what
ray
had
said,
I
assume
formatting
issues
will
be
fixed,
so
aggregators
looks
like
it
should
be
a
list
in
addition
to
raw
numbers.
B
B
B
B
It
was
like
all
the
lines
were
as
a
one
line,
rather
than
a
separate
bullet
points
for
all
of
the
indicators.
E
B
A
A
A
Why
I
was
just
oh,
my
gosh,
okay.
Finally,
how
do
we
measure
message
activities
in
code
management
platforms.
A
F
That
one
is
that
one
is
needed,
though,
because
that's
basic
that
code
management
platforms
is
that's
github
yeah.
So
how
do
we
measure
so
maybe
maybe
copy
part
of
his
is
sent
so
yeah,
the
gitlab
new
and
eg
get
lab
or
github
git
gitlab
there,
where
in
the
the
bit,
where
we're
talking
about
code
management?
Where
is
that
yeah.
A
G
D
G
F
Right
and
the
answer-
and
the
answer
is
correct-
comments
in
issues
and
pr's
is
the
primary
way
that
we
would
look
at
this.
A
F
So
he
wants
to
know
if
the
contributions
are
represented
by
organizations
or
independent
contributors.
So
I
think
we
could.
Probably
I
don't
think
that's
and
is
that
an
aggregator
or
is
that
a
filter?
A
A
F
Yes,
so
it
is
aggregators
and
filters
are,
are
headings
that
are
used
by
we've.
We've
used
them
in
evolution
before
and
I
think
they
may
exist
in
risk
as
well.
Okay,
however,
I
think
there's
a
there's
kind
of
a
subtle
distinction
between
what
an
aggregator
is
and
what
a
filter
is,
and
I
think
most
working
groups
are
using
filters.
I
think
so
too.
I.
A
Is
it
is
yeah,
should
we
add
rey
to
the
list
and
well
remember
it's
the
opt-in
thing
out
there.
B
B
D
F
Well,
maybe
maybe
this
is
for
later.
Ideally,
we
should
link
to
defined
metrics
and
since
since
contribution
attribution
is
a
filter,
we
should
link
to
that.
Let's
just.
A
Do
it,
you
know
what
I
mean
while
we're
here.
D
A
F
Cool
and
then
I
don't
know
that
we
have
to
do
this
now,
but
I
know
we've
talked
about
revisiting
these.
These
metrics
in
the
next
release,
yeah
and
I
think
part
of
that
audit,
I
think,
is
going
to
be
going
through
and
like
the
that
one
filter
we
have
is
number
of
people
like
what
is
that
is
that
a
metric
that
might
be
a
metric
is
that
number
of
contributors
that
might
be
number
of
contributors.
F
A
A
All
right,
let's
go
back!
Thank
you
everybody
for
that,
like
I
said,
I
think
this
is
our.
This
meeting
today
is
really
just
meant
to
go
through
these
metrics
if
we
have
any
changes
to
them,
so
this
one,
what
was
we
were
just
on
this
one
which
which.
F
F
A
So
yeah
just
so
everybody
knows
too
is
kind
of
following
along
every
time
we
make
any
change
to
a
metric,
so
we
have
a
the
metric
is,
is
what
we
were
just
working
on
and
all
of
our
metrics
are
also
with
this
round.
This
is
our
first
time
being
translated
into
chinese,
and
so
kevin
is
also
including
kind
of
a
note
that
signals
that
the
metric
that
we
just
worked
on
has
some
changes
that
need
to
be
changed
translated
into
chinese.
A
A
A
F
This
is
a
good.
This
is
a
good
task
for
the
operations
team.
When
we,
when
we
meet
this,
the
the
image,
the
image
folder
structure
and
image
naming
is,
is
something
that's
going
to
have
to
happen
across
the
board
so
yeah.
So
maybe
we
can
bring
this
up
at
the
whenever
we
have
an
operations
meeting,
and
I
don't
know,
do
we
have
one
of
those
do
we
have
no.
A
D
D
A
F
Or
then
yes,
there
would
be
a
shortcut
to
do
that.
I
believe,
but
I
don't
think
it
is
in
in
github
mark
down
in
the
browser
so
and
then
in
in
the
description
there
is
actually
so
we
do
mention
is
that
time
to
first
response
should
be
linked
out.
A
F
D
D
F
F
How
about,
if
you
so
take,
provide
a
filter
on
things
like
and
bold
it
and
put
a
colon
there.
G
I
think
it
might
be
two
spaces.
I
don't
remember
that.
D
F
The
bold
header
to
separate
it,
okay
and
you
can
just
have
maybe
so-
maybe
the
maybe
the
those
first
two
bullets
can
be
turned
into
a
sentence
and
then
provide
filter
on
things
like
can
be
the
list.
However,
I
would
say
if
we're
saying,
provide
filter
on
things
like
shouldn't
that
be
under
filter.
B
D
F
Yeah,
I
guess
I'm
not
a
I'm,
not
a
fan
of
this
subjective
section,
so
half
the
stuff
half
the
stuff
in
there
is
filters
that
should
be
down
below
demonstrate
an
increase
in
new
contributors.
I
believe
that's
an
objective
show
cla
bot
activity
is
an
objective.
F
A
D
D
A
So
people
you
people,
community
managers,.
D
D
D
A
A
B
F
F
What
is
this
so
bots
are
often
used
to
provide
elevated,
elevated
access
to
individuals
who
do
not
have
admin
rights.
Okay,.
F
F
I'm
provide
maybe
this
metric
may
provide
additional
context
for
project
activities
like
or.
F
Yeah,
okay,
yeah,
that
that
feels
better,
oh
and
look
the
understand,
project
access,
so
maybe
change.
I
suppose
that
that
last
bit
that
I
gave
you
on
that
sentence
is
actually
in
the
down
below,
so
we
could
either
yeah.
We
could
either
delete
it
or
yeah
all
right,
great
and
then
so
where's.
The
dei
in
that
objective,
by
the
way.
A
Well,
it's
not
that
every
metric
has
to
have
it.
Okay
is
there?
Is
there
dei
here
it
wasn't
in
the
original?
I
don't
know,
if
that's
our
responsibility
in
a
final
review
to
add
it.
A
F
That
is
part
of
our
checklist
on
on
sending
it
to
review.
D
A
Amen
did
the
issues.
Five
genuine
filters
have
a
formatting
problem.
It's
all
fixed,
oh
looks,
like
lucas
already
submitted
a
pr
to
fix
it.
The
implementation
section
of
benefit
for
more
detail.
D
F
But
not
I
merged
your
pull
request.
F
F
D
B
Kevin
this
might
break
the
link
to
the
website.
I
don't
know
because
we.
A
A
D
What
I
wanted,
that's
not
what
I
wanted
either.
A
I
was
right
there.
I
like
went
in
a
giant
circle.
All
right,
everything's
checked
off,
I'm
going
to
call
that
one
done,
and
then
we
have
one
last
one.
H
B
A
B
C
F
F
Was
done
in
conjunction
or
it
was
very
connected
to
that
other
metric,
so
yeah
I
would
yeah.
I
think
it
would
be
okay
to
just
copy
the
contributor
list
from
the
other.
A
B
Yep,
should
I
do
it
directly
or
I
create
a.
I
need
to
create
a
mod.
A
Two
three:
oh
edit,
edit
one
that
one
okay
programming,
language
distribution:
yeah.
Are
you
double
checking
against
translations?
Yes,
this.
E
F
A
A
A
Technical
fork
needs
to
be
in
there
because
we
have
a
new
header
called
contributors.
Okay
again,
what
we're
doing
here
is
we're
just
going
through
the
metrics
that
we
have
completed
in
the
common
working
group
and
kevin,
I'm
not
showing
it
on
the
screen.
Kevin
is
over
in
a
repository,
called
github,
slash,
chaos,
slash
translations
and
he's
updating
issues
in
there.
Well,
here
let
me
just
show
you
I'm
just.
A
A
Translations
and
we'll
share
my
screen,
so
kevin
is
here
and
so
every
time
we
create
a
new
metric
in
the
respective
working
group
over
here
in
the
chaos
translations
repository,
we
have
all
of
the
new
metrics
that
are
being
released
here
or
have
been
released
and
kevin.
If
you
notice
we've
been
working
on
collaboration
platforms,
he
just
tagged
it
again
with
a
chinese
translation,
because
we
had
a
few
edits
there,
and
so
our
our
colleagues
who
are
helping
with
the
chinese
translations.
A
Thank
you
very
much,
colleagues
and
friends
they're
doing
some
some
translation
work
and
same
with
language
distribution.
D
A
F
A
Did
do
technical,
4k,
okay,
clones
does
not
need
anything.
Okay,
bot
activity
needs
to
be
redone
or
relooked
at.
A
F
Which
one
is
that
bot
activity?
Oh?
No?
No,
so
all
of
them
should
still
be
open
because
none
of
them
have
been
translated
to
spanish.
A
A
G
I
just
noticed
that
these
pull
requests
that
are
getting
merged,
they're
getting
merged
into
master.
It
looks
like
not
me.
F
It's
have
you
changed
your
your,
your
forked
repo.
B
F
A
F
A
H
F
He's
editing
directly
in
the
in
main
on
the
browser.
A
D
F
Yeah
there
should
be
a
little
pencil
thing
that
you
can
click
edit
and
and
just
type
in
main
yeah.
Okay,.
H
A
H
A
Okay
well
there.
So
this
is
a
spreadsheet
that
we
use
to
track.
So
you
can
see
across
the
bottom.
We
have
all
of
the
different
working
groups.
The
dei
working
group
risk
evolution
value
in
common
and
these
like
rows,
14,
21
so
on
and
so
forth.
Those
correspond.
Those
are
the
the
focus
focus
areas
within
each
of
the
working
groups,
and
so
these
are
obviously
just
kind
of
based
on
what
we
have
here
with
the
color
coding
and
the
naming
the
metrics
that
we
have
released
the
ones
that
are
currently
under
community
review.
A
We
should
recognize
all
those
that
we
just
talked
about,
and
so
what
will
happen
in
two
weeks?
Is
we
will
kind
of
take
a
look
at
this
list
and
see
which
of
the
metrics
are
probably
candidates
to
continue
to
work
on?
So,
if
you
can
see
a
few
of
them
have
kind
of
started
like
33
and
34,
we
just
didn't
have
the
capacity
to
finish
those
up
in
this
round.
I
know
that
this
is
one
occasional
contributors
or
episodic.
A
C
A
And
one
of
the
other
things
that
we're
going
to
be
doing
in
the
next
round
as
well
is
all
of
the
released
metrics.
So
like
15
and
26
and
27,
you
know
within
each
working
group
some
of
the
metrics
it's
kind
of
like
I
don't
know
if
you've
ever
read
like
a
paper
that
you
wrote
years
ago
and
you're
like
oh,
that,
like
that
paper
needs
to
be
updated,
a
little.
H
A
So
we
we
want
to
spend
the
next
like
six
months
kind
of
going
back
through
the
metrics
that
we
have
released
already
and
just
kind
of
ask
ourselves
like
is
the
narrative
and
the
story
within
each
metric
still
appropriate,
because
we
need
to
kind
of
treat
these
as
as
living
documents,
not
just
something
we
released
two
years
ago,
and
then
we
just
never
look
at
it
again.
So
part
of
the
next
round
is
going
to
be
revisiting
our
release
metrics
as
well.
F
Are
we
using?
Are
we
using
consistent
language,
for
example?
We
we
had
two
full
releases
before
well,
possibly
three
full
releases
before
we
even
came
to
consensus
on
what
to
call
pull
requests,
so
so
how
many
metrics
are
using
are
still
using
the.
F
A
Okay,
cool
thanks
all
right
great,
so
we
are
at
the
end
of
our
time.
Everybody.
Thank
you
so
much
for
joining
it's
good
to
see
everybody
and
we
will
see
other
people
on
other
things.
Solona.
If
you
have
a
second
I'd
like
to
chat
with
you
real
quickly
sure
all
right,
I
don't
know
what
your
next
meeting
is.