►
From YouTube: CHAOSS Common Working Group 8-19-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).
B
If
some
of
you
want
to
add
your
name
to
the
attendees
list,
that
would
be
that
would
be
cool
and
how
you're,
how
you're
feeling
today,
I'm
feeling
a
little
sleepy.
I
don't
know
why
just
damn.
C
B
Okay,
so
we
have,
we
have
an
action-packed
agenda
today,
primarily
because
this
is,
I
think
our
is
this,
our
last
meeting
before
the
metrics
freeze
on
september
1st.
It
is
because
our
next
meeting
is
on
september
2nd.
So
I
think
that
we
should
we
all
I.
I
know
we
need
to
talk
about
the
metrics
freeze
and
what
we're
going
to
have
in
it.
We
need
to.
B
There
were
several
metrics
that
were
kind
of
in
flight,
so
we'll
talk
about
all
of
those
and
make
sure
that
we
get
those
finished
wrapped
up
and
into
the
metrics
release,
because
there
are
several
that
they
may
have
already
been
pr-
and
I
haven't
looked
at
the
prs,
but
we'll
look
at
that
as
well,
and
we
also
need
to
make
sure
that
we
have
translation
issues
for
all
of
our
metrics
to
be
released.
So
is
there
anything
specific?
B
We
need
here
I'll
share
my
screen,
so
so
you
can
see
the
agenda
and
stuff.
Is
there
anything
specific
that
we
need
to
do
for
the
metrics
freeze
other
than.
A
C
B
Okay,
so
let's,
let's
start
by
by
looking
at
the
prs
and
let's
see
which
of
these
metrics,
we
already
have
prs,
for
I
think
that'll
simplify
the
rest
of
the
agenda,
so
we
have.
D
D
B
E
Do
those
two
metrics
have
review
issues
associated
with
them?
Yeah.
D
E
D
D
D
E
Yeah,
I
think
one
issue
is
fine.
I
think
we
just
can
change
the
labels,
but
we
do
need
to
make
sure
we
do
need
to
make
sure
that
all
of
the
information
that
we
have
described
in
the
process
gets
put
in
here
and
in
in
the
future.
There
will
be
a
there.
There's
a
template
checklist
that
we're
going
to
use
that.
So
you
basically
change
the
label.
D
E
D
B
Okay,
cool
and
then
we
also
had
the
technical
fork.
A
D
B
B
I
don't
know
what
happened
there:
okay,
so
the
the
technical
fork
yeah.
We
basically
just
go
ahead.
D
D
E
D
E
D
B
E
I'm
kind
of
of
the
opinion
that
we
should
err
on
the
side
of
sending
it
to
review,
otherwise
it'll
be
really
easy
for
us
to
justify
not
sending
edited
metrics
back
to
review.
E
Additionally,
there
is
a
translation
issue
here
where
we
are
going
to
have
to
there's
enough
work
in
here.
That's
been
done
that
this
is
going
to
have
to
go
back
to
the
translation
team.
E
B
No,
I
think
I
think,
that's
I
think,
that's
fair,
so
I'm
just
going
to
leave
a
comment
that
the
node
will
add
the
disclaimer
text
and.
D
D
B
E
D
B
We
just
need
to
make
sure
that
we
do
get
this
merged
and
oh
and
we
need
the
translation
issue
too.
A
Those
several
libraries
exist.
That's
actually
correct.
B
B
Okay,
so
if
I
close
it
with
comment,
that's
closed
without
merge.
I
just
do
this,
so
rarely
that
I
close
something
without
without
merging
it.
B
B
Okay,
so
I'll
leave
that
that
you're
you're
on
the
hook
to
pr
that
yep,
but
I
think
matt
that
was
you-
is
that
right.
A
A
A
B
B
Should
we
before
we
pr
this,
should
we
talk
to
the
grimoire
lab
folks,
because
I
know
that
they
use
bots
as
a
filter
on
a
lot
of
their
dashboards?
So
I
wonder
if
it
would
make
sense
to
also
get
a
visualization.
A
B
F
E
E
C
B
That
to
pr
this,
and
we
should
ask.
E
E
For
more
more
lab
camel
case,
l,
okay,.
F
B
No,
the
the
actually
the
filtering
of
the
bots
was
incredibly
manual
on
my
part.
It
was,
it
was
basically,
I
was
looking
at
my
contributor
graphs
and
I
was
like
spring
dash
ci,
that's
not
a
real
person,
they're,
not
the
top
contributor
to
this
project.
That
must
be
a
bot.
So
a
lot
of
it
was
me
looking
at
things
that
looked
weird
on
my
contributor
charts,
realizing
they
were
bots
and
then
manually
filtering
them
out
in
the
select
statement
for
for
the
commits.
B
A
Right,
well,
I
will
get
that
pr
in
and
then
just
because
we're
because
we
won't
meet
again
I'll.
B
Okay,
cool
and.
F
F
B
F
B
B
Okay,
okay,
so
this
is
looking.
This
is
looking
good.
B
A
E
We
changed
our
focus
group
names
as
well.
I
wonder
if
the
translation
team
has
already
accounted
for
that,
I
seem
to
think
they
have.
A
E
B
Okay-
let's
just
do
that
right
now,
so
that
we
don't
forget.
B
B
I
well
it's
one
of
the
things
I
measure
on
on.
All
of
our
all
of
our
existing
open
source
projects
is
like.
Do
you
keep
up
with
your
pull
requests?
Yeah,
and
it
feels
sort
of
hypocritical,
though,
if
you're
not
keep
up
with
the
full
requests,
it's
just
one
of
those
things.
Okay,
so
we
got
that
one
and
then
there
should
be.
There
should
be
one
more
that
we
need
to
do.
Oh
event,.
B
A
A
A
A
B
Okay,
we
did
the
prs
this
translation
issues,
bot
clones
event
location.
B
Perfect,
okay!
Well,
I
feel
like
we,
we
got
through
all
of
the
things
we
had
on
the
agenda.
Is
there
anything
else
we
need
to
talk
about?
Is
there
anything
related
to
the
release
that
we're
forgetting
to
do.
B
B
Cool
okay
and
kevin
said
you're
involved
in
the
release
process.
I
will
try
to
keep
an
eye
out
for
some
of
these
metrics
and
just
merge
them,
but
kevin.
Can
you?
Can
you
just
make
sure
that
we
don't
forget
this
when
the
when
the
freeze
happens
since
you're
involved
in
the
release.
B
Thank
you,
okay,
I
think
that's,
I
think.
That's
it
sean.
I
sent
you
some
slack
messages
about
some
issues
with
commits.