►
From YouTube: 2020-07-06 meeting
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
A
A
A
B
Okay,
so
my
only
update
is
we
have
from
last
week.
This
is
the
ga
Kanban
board
for
the
specs
repo,
and
so,
as
we
mentioned
last
week,
we
have
all
of
the
issues
for
metrics
that
are
tagged
as
required
for
GA,
and
then
we
also
did
a
scrub
last
week
to
tag
really
like
a
first
round
of
tagging,
tracing
issues
that
we
think
are
required
for
GA.
So
those
should
be
appearing
here
and
they're.
Not
so
maybe
I
need
to
fix
that
this
metal
browser
it
looks
like
those
aren't
showing
up
the
Kanban
board.
B
I
will
get
that
fixed
after
this
meeting
to
have
them
properly
show
up
here,
but
there
they
all
they're
tagged
now,
with
the
release
required
for
GA
tag,
it's
just
starting
this
week.
I
will
be,
and
anyone
else
is
interested
in
joining.
You
can
assist
joining
all
of
the
language
SiC
meetings
and
having
them
tag
their
own
issues
for
things.
B
They
know
they
need
to
do
already
to
me
GA
and
then
also
have
them
file
issues
for
things
for
issues
that
have
been
filed
for
the
spec,
for
a
TBD
work
for
GA
and
then
we'll
have
each
cig
have
a
similar
Kanban
board
to
this.
This
Kanban
board
is
scoped
to
the
Oklahoma
tree
organization
because
it
needs
to
pull
in
issues
and
PRS,
both
from
the
specs
repository
and
from
the
Oh
tips
report
story.
Most
SIG's
will
just
have
a
project
scope
to
their
specific
signal,
which
just
makes
it
easier
to
manage.
C
B
C
B
Okay,
okay,
that
makes
sense
yeah
I,
also
some
co-workers
at
Google
or
on
vacation,
so
I
suspect
this
may
just
be
a
quiet
week.
Just
one
quick
question
so
for
for
logs,
have
we
decided
whether
we
put
that
part
of
the
spectrum
or
it's
not?
No,
it's
not
a
scope.
Frigate
like
there
will
be
a
large
GA
later,
but
but
certainly
not
at
the
same
time
frames.
It's
just
not
that
far
long
as
that
is
the
challenge.
Yeah
thanks,
yep.