►
From YouTube: 2021-10-27 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
All
right
first
thing
that
I
wanted
to
mention
is
that
I
did
release
the
contrib
revo.
Sorry,
it's
been
so
long
since
the
last
release,
but
we
had
some
some
growing
pains
with
the
release
process
that
hopefully,
we've
got
figured
out
for
any
component
owners
if
you
notice
that
you've
had
any
issues
since
the
release
or
there
was
any
problem
or
your,
your
module
didn't
get
released,
or
something
like
that.
Please
reach
out
to
me,
but
it
at
least
appears
that
seems
to
have
gone
well.
A
So
that's
all
I
really
have
to
say
unless
somebody
has
an
issue
with
it
real
quick.
I
just
wanted
to
mention
the
metrics
api
project.
For
those
that
don't
know
there
is
a
project
tracking
the
metrics
api
updates
and
changes.
A
There
are
a
series
of
up
for
grabs
issues,
so
anyone
can
feel
free
to
grab
those,
but
also
this
in
progress
column.
Any
pr's
in
here
need
reviews,
so
this
is
sort
of
our
our
focus
at
the
moment,
at
least
in
the
core
repo.
A
So
for
those
that
have
time,
I
do
appreciate
it.
I
know
that
legendicus,
who
is
not
often
able
to
join
these
meetings,
has
been
doing
a
bunch
of
metrics
work.
So
that's
been
really
great
and.
B
Yeah,
I'm
not
sure
if
you
want
to
cast
the
google
doc
but
you're
casting
slack
right
now.
A
What
about
now?
Yes,
this
looks
right.
Okay,
so,
like
I
was
saying
this
is
the
metrics
project.
Just
for
those
that
didn't
know
it
was
there.
So
if
you're
looking
for
something
to
do
these
upper
grabs
issues
on
the
left
are
our
current,
like
high
priority
issues
all
of
the
ones
we
have
now
are
fairly
good
for
beginners
too.
So,
if
you
have
interns
or
anything
that
are
looking
for
something
to
do,
you
know
everything
helps
and
we
definitely
need
reviews
on
these
in-progress
prs.
A
A
He
updated
the
get
meter
to
add
this
meter
options
and
all
of
the
optional
parameters
were
in
here
and
I
know
bart
blocked
this
saying
we
wanted
to
match
the
api
of
the
trace
as
closely
as
possible,
which
I
definitely
agree
with.
So
we
have
the
get
tracer
with
name
and
version.
We
should
have
get
meter
with
name
inversion,
but
the
question
still
remains.
A
C
You
have
the
same
thing
with
trace
right.
What
do
we
do
for
the
scam,
url
and
trace.
D
A
E
A
Okay,
you're
you're
breaking
up
a
little
bit,
but
it
sounded
like
you
said
you
prefer
the
second
one
here.
A
A
I
think
the
name
and
version
are
really
like
the
most
important
ones
so
to
have
those
be
their
own
parameters.
I
think
totally
makes
sense
and
it
matches
the
trace
api,
but
having
this
options
object
at
the
end
makes
sense
to
me,
just
as
we
extend
the
api
it'll
be
easier
to
do
it
in
a
backwards
compatible
way.
D
D
A
And
then
there
was
actually
another
question
that
came
up
in
the
same.
I
believe
it
was
in
the
same
pr
yeah.
So
in
this
pr
he
required
some
change
in
core.
A
Yeah,
so
we
can't
link
if
you're,
making
changes
in
the
experimental
packages
we
currently
can't
link
like
the
core
or
that
the
stable
packages
in.
So
if
you
require
a
change
to
a
stable
package,
it
has
to
be
done
in
a
separate
pr
which
is
kind
of
a
frustrating
workflow.
It
does
prevent
us
from
releasing
the
experimental
before
it's
required,
stable
packages,
so
it
may
prevent
us
from
from
shooting
ourselves
in
the
foot
a
little
bit,
but
it
also
is
kind
of
a
frustrating
dev
experience.
A
You
know,
I
I
put
one
suggestion
to
how
we
could
fix
this,
but
I
don't
really
if
we
had
talked
about
it
before
it
seems
like
valentine.
You
don't
think
that's
the
way
to
go,
though
do
you
do
you
have
any
particular
alternative,
or
do
you
think?
Are
you
just
saying
that
we
should
research
alternatives.
B
Yeah,
I
think
we
we've
done
a
lot
of
research
in
the
past,
but
I
mean
we
always
go
back
and
forth
between
different
learner
setup.
I
think
we
should
look
out
for
for
other
tools.
I
think
nephew
you.
You
told
about
last
time
that
you
had
a
specific
tooling
for
this
on
the
microsoft
side,
maybe
I'm
mistaken,
but
yeah.
I
think
we
should
put
more
effort
into
the
research
before
trying
to
update
it
again
to
leona
and
we
have
other
issues
on
the
on
the
other
setup
so
yeah.
A
A
Okay,
it's
not
it's
not
completely
broken,
but
if
somebody
has
time
to
to
research
alternatives,
I
would
appreciate
that,
if
not,
we
have
other
higher
priorities
right
now,
so
I
I
don't
think
that
I'm
going
to
spend
a
lot
of
time
trying
to
to
to
get
that
done,
because
I
think
it's
a
sort
of
a
niche
use
case,
but
if
it
comes
up
more
in
the
future,
I
think
it
might
be
worth
spending
some
time
on.