►
From YouTube: CHAOSS Common WG - 8-5-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
A
Okay,
so
we
have,
we
have
a
few
things
on
the
on
the
agenda.
A
Let's
start
with,
let's
review
the
action
items,
so
we
can
just
kind
of
mark
some
of
that
as
as
done
so
kevin,
you
said
that
the
collaboration
platforms,
one
is
done
so
I'll,
just
go
ahead
and
mark
that
and
then
vinod
you
had
some
action
items
on
the
clones
metric.
C
Yes,
they
are
done.
We
just
need
to
review
them.
A
Okay,
okay,
so
we'll
do
that
as
part
of
the
this
part
of
the
agenda.
D
A
Okay,
well,
let's,
let's
start
with
that,
then
I'll
go
ahead
and
share
my
screen.
While
we
look
at
the
issues
pr's,
can
everybody
see
that
perfect?
Okay?
So
it
looks
like
we
don't
have
any
pull
requests.
So
that's
easy
issues.
So
we've
got
a
couple
of
things
in
the
metrics
candidate
release
kevin.
You
want
to
just
talk
about
those
quickly.
E
So
if
they've
yeah,
if
they've
label,
if
they've
been
labeled
metrics
candidate
release,
they
are
officially
on
the
website.
So
we
have
we've
sent
three
metrics
to
the
as
part
of
the
continuous
release
process.
We
have
sent
three
metrics
in
so
it
is,
I'm
sorry,
not
three
metrics,
but
two
metrics
and
we've
re
we're
renaming
our
focus
areas.
That's
the
other
bit.
A
E
C
So
but
I
recall
in
the
last
journal
meeting,
it
was
announced
that
release
has
been
stopped
like
further
release
for
from
august
1..
Is
that
correct?
C
No
because
it
was
discussed
in
the
journal
meeting-
and
I
said
that's
what
I
recall
yeah
this
last
meeting
in
in
and
that
it
is
a
freeze
from
august
1.
E
B
E
I
think
he's
mistaken,
so
I
believe
the
the
release
time
and
I'll
go
through
and
see
if
I
can
find
it
in
the
notes,
but
I
believe
the
the
release.
The
release
dates
are
meant
to
correspond
about
six
months
apart.
So
if
the,
if
we're
releasing
in.
E
Because
the
the
first
of
the
month
release
is
pushed
back,
this
one
is
pushed
back
as
well.
So
I
believe
that
the
the
release
date
is
october.
The
first
week
of
october
and
september
should
be
the
the
freeze,
okay
view
period.
I
will
go
through
and
take
a
peek
at
that,
I'm
sure
those
are.
We
have
those
notes
somewhere.
A
Yeah,
can
you
I'm
just
going
to
give
you
the
action
item
to
confirm
the
release
date
and
the
freeze
timing
and
then
maybe
send
an
update
to
the
mailing
list
because
it
seems
to
be
causing
some
confusion.
C
One
more
question
on
the
three
release:
metrics
has
all
these
three
being
issue
like
requested
in
the
translation
repo,
like
for
the
translation
of
these
three
release,
metrics.
E
So
we
actually
did
discuss
that,
and
that
was
that
was.
E
I
think
there
was
discussion
of
pulling
it
back
so
this
the
release
we
did
this
year,
so
it
is
labeled
20
2103,
but
we
actually
released
that
in
april.
I
believe
that
first
week
of
april,
so
I
believe
the
I
believe
the
plan
was
to
move
everything
back
a
month.
E
And
I
think
that
was
that
was
part
of
the
discussion
we
had
and
I'm
pretty
sure
sean
is
the
one
that
brought
that
forward
initially
and
I'm
I'm
yeah,
I'm
I'm
I'm
I'm
about
95
positive,
that's
what
was
it
was
discussed
in
in
the
community
meeting
and
we
had
decided
to
go
with
it
and
I
think
we
just
didn't
change
the
dates
on
the.
We
have
a
tentative
release
dates
on
the
web
page
that
tells
when
the
next
freeze
is
going
to
happen.
E
We
just
didn't
change
those
dates
so,
according
to
the
documentation
here,
georg,
is
right.
The
freeze
started
october
august
1st,
but
I'm
I'm
pretty
sure
that
we
made
that
switch
and
we
just
never
got
the
documentation
changed.
A
Yeah
that
makes
sense,
and
then
I
was
just
adding
the
the
three
that
we've
talked
about
already
here.
A
But
back
to
the
node's
question
about
translation
matt,
I
think
he
started
to
answer
that
and
then
we
got
a
little
bit
sidetracked.
Was
there
something
else
you
were
going
to
say
about.
D
Yeah
so
right
now,
there's
a
we're
working
on
there's
a
document
that
we're
working
on
and
so
there's
two
ways
that
the
it
looks
like
that
the
working
groups
will
signal
to
the
translation
team
but
they're
new
metrics
or
revised
metrics,
and
one
is
and
really
there's
really
no
change
based
on
what
we're
doing
here.
D
So
it's
just
marking
those
new
metrics
in
that
document
that
you're,
you
know
the
for
the
issue
that
you're
in
right
now
and
having
the
tag
which
we
already
have
like
metrics
release
candidate
or
whatever
the
name
of
the
tag
is
and
then
in
the
so
it's
all
good
here
and
then
I
can
get
rid
of
my
oh
sorry,
that's
okay,
I'll,
just
delete
it
and
then
in
I
think
in
the
translations
repository
so
just
chaos.
E
E
D
C
C
E
E
Just
for
consistency,
okay,
so
the
the
way
that
so
right
now
we
only
have
the
chinese
translation
team
working
right.
However,
in
the
future
we
may
have
more
translation
teams
working
so
the
way,
the
way
that
we
need
to
sort.
That
is,
we
need
to
prevent
one
of
the
teams
from
closing
the
issue
if
it
hasn't
been
translated
in
the
other
language.
E
E
And
we
haven't,
so
we
don't
have
the
we
haven't
created
the
template
for
what
we
would
want
to
put
in
here.
Yet,
okay.
However,
we
know
that
we
need
to
link
to.
We
know
that.
E
F
E
So
the
new-
this
is
really
the
only
new
step
that
we
would
be
asking
the
working
groups
to
do,
and
I
don't
want
to
put
too
much
of
a
burden
on
them
to
do
it.
So
I
would
rather
just
let's
create
it
tag
it.
We
link
it
to
the
working
group
site,
so
the
the
goal
would
be
to
get
the.
We
want
the
translation
team
to
go
to
the
working
group
site
to
see
the
markdown
could.
E
Yeah
and
yeah,
we
can
do
maybe
something
something
like
this
common.
E
Okay,
yeah
just
and
like
I
said
we
don't
have
the
we
haven't
actually
discussed
what
this
standard
document
would
look
like,
but
we
can.
We
can
create
a
template
for
what
it
would
look
like.
Okay,.
E
B
E
That
and
we
can
be
more
explicit
with
it
if
we
want,
we
could
change
that
label
to.
G
A
A
So
we'll
talk
about
we'll
talk
about
clones
because
that's
on
the
agenda,
how
are
we
doing
on
bot
activity
where's
that
one
matt.
C
C
G
A
A
Language
distribution,
clones;
a
couple
that
daniel's
working
on
he's
not
here.
C
A
E
It
should
be
so
it
shouldn't
be
ready,
it
should
be.
I
think
there
actually
is
an
under
view.
Isn't
there.
C
A
Not
in
the
drop
down,
sorry,
what
were
the
other
two
metrics
language,
distribution
and
focus
area
renaming.
D
A
C
A
Thank
you
so
he'd
be
the
one
to
ask
and
he's
pretty
responsive
on
slack.
So
if
you
can't
figure
it
out,
we'll
just
talk
to
you.
E
A
An
email
I
would
send
an
email
to
the
entire
like
the
whole
chaos
mailing
list,
because
I
think
that's
important
enough
that
people
don't
always
read
the
meetings
if
they
miss
a
meeting.
A
That's
a
good
idea,
okay,
so
but
you
have
the
action
items
on
on
the
clones
metrics.
Maybe
let's
talk
about
that
one
and
then
where
are
we
on
the
space?
One.
D
E
I
don't
so
so
I
I
took
a
peek
at
it
and
it's
so
it's
a
it's
a
really
simple
metric.
I
think
we
can
advance
it.
I
think
it's
pretty
much
ready
to
go.
I
think
there's
a
little
bit
of
editing
needs.
That
needs
to
be
done,
but
I
don't
think
we
need
to
add
too
much
more
to
it,
because
it's
I
mean
it's
quite
literally.
E
So
that's
why
I
added
it
back
into
the
so
I
had
taken
it
as
an
action
item
to
take
a
look
at
it
and
try
to
advance
it,
and
my
my
takeaway
is
basically
it's
it's
a
simple
metric.
Let's
just
move
it
forward
as
yes,.
E
Okay,
we'll
see
see
if
see.
If
you
all
agree,
I
believe
I
think
elizabeth
had
done
the
majority.
A
Should
we
should
we're
gonna
now
to
advance
it
or
since
elizabeth's
done
a
lot
of
the
work
on
it?
Should
we
maybe
punt
it
off
to
next
week
or
two
weeks.
E
I
think
the
reason,
the
reason
that
I
had
taken
it
as
an
action
item
is
because
she
had
done
a
lot
of
work
on
it
and
she
wanted
just
another
pair
of
eyes
to
look
at
it.
E
I
think
I
think
it's
ready
to.
We
could
peek
at
it
as
a
group
and
say
yay
or
nay
to
to
sending
it
to
release.
But
but,
as
I
said,
it's
a
it's
a
simple
metric
and
I
think
we
need
to
resist
the
urge
to
make
it
more
complicated
than
it
than
it
is.
It's
just.
D
Not
really
it's
like
kevin
said
it's
pretty
yeah,
pretty
straightforward.
A
Okay,
I
would
agree,
maybe
we
just
need
to
add
the
contributors
at
the
bottom.
E
I
was
just
thinking
about
adding
an
example
of
from
the
linux
foundation.
Event
page
might
be
a
nice
example.
E
B
C
D
A
No,
I'm
gonna.
To
be
honest,
it's,
like
you,
said
it's
already
the
bottom
of
the
hour.
I
think
we
can
move
the
clones
metric
forward
and
then
what
I'm
gonna
do
is
add
this
to
the
agenda
for
next
time.
Okay,
if
that's
all
right.
E
That's
fine
I'll
get
to
the
ones
that
I
can,
but
the
the
times
on
those
kind
of
correspond
with
some
of
the
the
amsa
stuff
yeah.
D
A
I'm
gonna
stop
sharing,
so
vanilla,
maybe
see
you
later
matt
vanilla.
Do
you
want
to
share
your
screen
so
that
we
can
talk
about
the
phone.
C
C
Not
that
technical
work
one
not
yet,
because
I
was
not
clear
what
is
the
process
of
changing
the
existing
release
metric,
which
I
got
clarity
in
the
last
common
meeting
like
general
meeting
and
then
I'll?
Do
it
once
we
agree
on
this,
because
that
needs
to
be
with
the
same
formatting
on
that.
So
I
was
like.
Let
me
get
the
confirmation.
Everybody
agrees
that
this
is
fine
I'll,
create
a
pr
for
the
technical
form
for
that.
E
Did
you
did
you
get?
Are
you
clear
on
what
that
process
is
on
editing.
E
C
And
one
more
thing
on
this
metric
was:
I
need
to
get
the
visualization.
I
contacted
both
the
team's
auger
and
remote
app,
but
none
of
them
provided
me
the
visualization,
so
they
said
it
grimold
lab.
I
said
it
can
be
implemented,
but
it
is
not
implemented.
I
provided
them
the
api
like
how
to
get
this
data,
but
I
haven't
received
any
visualization,
so
I
would
say,
drop
for
right
now.
I
don't
have
any
visualizations
for
the
clone.
B
And
also
some
of
the
work
that.
E
I
would
say
that
the
auger
is
the
one
that
would
be
able
to
provide
the
the
visualization
for
this.
I
even
contacted
the
auger.
They
have
not
provided
me
the
visualization,
so
they.
C
And
I
don't
recall
their
disinterest,
they
don't
have
responded.
I
guess
let
me
I
can
quickly
look
at
it
but
criminal.
I
had
a
detailed
discussion.
They
were
looking
for.
Is
there
an
api
to
extract
the
data?
I
provided
them
the
api,
but
then
got
any
response
of
implementation.
They
will
implement.
Well,
I
don't
know
okay.
Well,
let's,
let's
bug
sean
then
we'll
hope
sean.
C
F
C
Needed,
oh
that's
funny!
Okay!
I
I
I've
created
the
issue
in
the
augur
eco
for
implementing
this
particular
like
provide
a
visualization
or
implement
that
clone
option,
but
they
haven't
provided
me
them
with,
like
any
update
on
this.
A
A
E
It
I
was
like
I
don't
know
so.
This
is
something
that
github
like
straight
up
measures
in
their
interface
right.
This
is
that
github
might
be
the
whole
reason
we
have
this
metric
in
the
first
place,
so
I
think,
and
github
itself
has
visualizations
of
of
their
of
their
metrics.
So
perhaps
we
just
go
back
to
the
beginning
and
do
a
github
visualization.
We
don't
do
that.
That
often
perhaps.
A
A
C
So
now
they
have
released
an
api
earlier.
It
was
only
to
the
who
are
the
project
owner.
They
can
see
the
clones,
but
now
they've
opened
an
api
which
everybody
can
access,
but
visualization
is
still
not
in
that,
like
a
trend
line
or
whatever
they
show
whatever
the
visualization
it's
clone
is
not
at
their
estimate.
C
F
C
E
Would
be
a
visualization
right?
So
yes,
so
it
doesn't
necessarily
so
the
visualizations
don't
necessarily
have
to
be
connected
to
auger
or
more
lab.
It's
quite
obvious
that
I
mean
so
github
did
this,
so
they
are
obviously
using
the
github
api
to
pull
the
data
and
then
create
the
visualization
in
some
fashion.
E
So,
and
I
think
we
have
talked
about
that
as
well
like
using
so
tools
providing
the
metric,
you
know
we
can
quite
literally
say
graphql
and
the
github
api
as
a
either
as
a
as
a
tool
providing
the
metric
or
a
data
collection
strategy.
Although
I
think
that's.
E
And
I
I
think
that's
something
we
don't
do
enough
of
either
so
oftentimes.
We
just
fall
into
tools
providing
the
metric,
auger
or
lab,
and
that's
that
is
not
an
accurate
depiction
of
the
world.
E
Yeah
remove
the
optional
bit,
there
leave
tools
providing
the
metric
empty
and
then
in
data
collection
strategies.
Why
don't
you
put
something
to
the
effect
of
querying
github
api.
C
A
C
That
so
in
some
of
the
release,
it
has
been
captured
as
a
blank,
but
now
when
we
were
developing
the
checklist,
we
decided
to
keep
like
remove
them,
since
they
are
not
there,
they
are
not
adding
anything.
We
just
remove
those.
C
A
A
Okay,
all
right,
I
think,
we're
in
good
shape.
This
is
thank
you
so
much
kevin
for
the
work
on
the
event,
location
and
the
note
for
the
work
on
the
the
clones.
I
think
these
are.
These
are
looking
really
good.
I
feel
like
comet's,
going
to
be
well
represented
in
the
next
next
release.
I'm
feeling
pretty
good
about
this.