►
From YouTube: 2021-11-10 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
B
The
first
order
of
business
here
is
the
release.
Some
of
you
may
have
seen
that
I
created
a
release
pr,
I
created
a
couple,
but
I've
actually
closed
the
other
ones.
This
will
release
both
the
stable
and
experimental
folders.
One
thing
that
you
might
notice
is
that
the
build
is
failing
for
experimental
packages.
B
That's
because
I
updated
the
dependencies
of
the
experimental
packages
to
point
at
the
stable,
the
unreleased
stable
packages.
So
what
I'll
have
to
do
is
release
the
stable
packages
and
then
rerun
the
tests
and
when
they
pass,
then
I'll
release
the
experimental
packages.
B
B
B
Some
of
you
probably
also
seen
I
created
a
pr
to
create
a
new
work
in
progress,
metrics
sdk
for
those
that
have
seen
it.
It
is
very
work
in
progress
like
it's
missing
a
lot,
but
when
we
were
looking
through
to
see
what
work
would
be
done
would
need
to
be
done
to
bring
the
sdk
up
to
date.
It
just
seemed
like
it'd,
be
easier
to
to
rewrite
it
from
the
ground
up.
B
The
old
metrics
sdk,
I'm
also
planning
on
removing
there,
is
a
pr
to
remove
it
already
open
it's
failing,
because
the
the
pr
tests
fail,
because
the
exporters
and
such
depend
on
unreleased
changes
from
the
old
metrics
sdk.
So
after
we
do
the
release
this
afternoon,
these
tests
should
pass,
and
this
should
be
mergeable.
B
So
please
take
a
look
at
that.
It's
currently
marked
as
a
draft,
but
after
we
cut
this
release,
I
will
rerun
the
tests,
update
it
and
mark
it
as
ready.
B
So
that's
sort
of
our
road
mapping
and
housekeeping
anyone
have
any
questions
on
on
those
three
items.
B
Okay,
first
question
that
I
have
for
all
of
you
is
this
pr
that
rana
opened.
We
did
a
similar
thing
in
the
contrib
repository
where,
if
the,
if
issues
are
more
than
60
days
old
or
have
60
days
since
the
since
their
last.
B
Interaction,
they
are
marked
as
stale
and
then,
if
nobody
comments
on
them
for
14
days
after
that
they're
automatically
closed.
I
think
it's
been
working,
okay
and
the
contributory
vote
and
we're
moving
it
over
here.
I
can
see
that
obviously
the
maintainers
have
already
approved
it
and
nab.
It
looks
like
you
just
did.
Thank
you.
It's
currently
a
draft
so
I'll
reach
out
to
ramo
to
find
out
why
it's
a
draft,
but
does
anyone
have
any
reason
we
shouldn't
do
this?
Has
it
been
working
for
everybody
in
contrib,
okay,.
B
I
think
silence
says
positive
in
this
case.
I
guess
the
second
question
I
have
is
this:
esm
2015
release
this
was
opened
kind
of
a
while
ago,
but
it's
just
adding
a
new
target
to
our
release,
so
we
currently
release
for
like
common
js
modules
and
we
have
a
esm
release
within
the
same
package.
B
This
is
just
adding
an
esm
2015
into
the
package
for
people
that
are
targeting
modern,
modern
browsers.
The
code
is
a
little
bit
lighter,
there's
fewer
polyfills,
and
things
like
that.
B
I
think
this
is
a
good
idea.
I
know
bart
has
already
approved
it
also,
but
does
anyone
have
thoughts
or
opinions
on
this
know
that
this
is
related
to
minification,
which
nev
always
seems
to
be
happy
about,
but
is
there
anyone
else
that
thinks
this
is
a
good
or
a
bad
idea.
B
There
are
a
couple
of
older
prs
that
are
just
fixing
lint
issues.
I
believe
that
these
still
oh,
that
one's
had
reviews
on
it.
I
guess.
B
Yeah,
so
this
one
was
the
one
that
I
noticed
it
needs
reviews
and
I
think
it
also
needs
to
be
brought
up
to
date.
B
B
B
This
was
obviously
opened
a
long
time
ago
and
there's
he
never
signed
the
cla
so
like
this
isn't
mergiable
as
it
is,
but
I
was
wondering
what
people
think
of
this
idea.
Is
this
a
good
idea,
or
should
we
leave
this
alone
for
now?
Is
this
a
feature
that
other
people
would
want?
B
I
know
we've
had
a
lot
of
requests
around
being
able
to
give
custom
names
to
the
just
fans
in
various
instrumentations,
not
just
in
the
http
one,
but
is
this?
Is
this
something
that
that
people
think
would
be
useful
or
and
worth
pursuing?
B
C
I
was
just
saying
that
I've
seen
specification
around
spam
names
before.
How
does
this
play
with
that?
Like
a
specification?
Just
really
a
guidance
for
like
spam
should
have
this
these
names
with
low
cardinality,
but
once
you
give
people
a
customization
option,
they
will
no
longer
follow
that
spec.
B
Yeah,
so
the
way
that
I
guess
I
would
interpret
that
is
if
nobody
has
configured
anything
like
the
the
spec
is.
This
is
the
what
the
sdk's
default
behavior
should
be.
I
don't
think
that
the
spec
specifically
disallows
the
use
of
custom
names
and
things
like
that
like
if,
if
a
user
has
a
reason
to
customize
the
name,
I
don't
see
any
any
reason
to
block
them
on
that.
B
I
guess
if
they
are
exporting
those
fans
to
some
telemetry
vendor
and
the
vendor
was
depending
on
the
name
for
some
reason,
then
that
is
a
potential
pain
point.
I'm
not
completely
sure
how
all
of
the
various
vendors
do.
That,
though,
like
I
know
at
least
at
dynatrace,
we
don't
use
the
name.
We
actually
generate
our
own
name
based
on
the
semantic
conventions.
B
B
A
Yeah,
I
could
just
suggest
to
maybe
contact
the
because
there's
already
a
seek
for
the
instrumentations
and
they
are
working
on
things
that
might
be
quite
related
to
what
they
are
working
on,
and
maybe
it
would
be
worth
to
ask
them
if
they
already
have
some
position
for
that,
because
it
might
appear
that
such
functionality
can
be
implemented,
basically
for
all
instrumentations
and
just
not
trying
to
reinvent
the
wheel
how
to
make
it
I
mean.
Maybe
they
already
had
some
solution
and
inspect
how
such
things
can
be
handled.
B
Yeah,
that's
a
good
idea.
We
can
reach
out
to
them.
I
think
they
actually
meet
at
the
same
time
as
we
did
so
I
can.
A
They
have
some.
I
think
this
is
from
the
I
mean
from
my
time.
This
is
quite
late
in
the
night.
This
is
from
tuesday
to
wednesday
at
1
00
a.m
the
night.
So
this
would
be
probably
I
mean
much
more
confident
for
you,
but
you
can
ask
that
basically,
that
young,
so
so
he's
organizing
this
meeting.
So
just
you
can
reach
the
email
task.
E
And
we
also
do
have
a
mechanism
for
changing
the
http
spanning
right.
We
write
something
on
the
context
and
then
downstream
components
can
pick
it
up
and
change
the
name
yeah.
So.
B
It's
a
little
bit
different
because
I
mean
it's.
This
would
be
a
much
easier
way
for
like
an
end
user
to
do
it.
The
the
reason
we
have
that
mechanism
is
so
that
instrumentations
can,
you
know,
play
nicely
together
so
that
the
express
instrumentation
can
rename
the
span
from
the
http,
instrumentation
and
stuff
like
that,
but
for
an
end
user,
that's
not
a
very
friendly
api,
so
this
would
provide
like
a
much
easier
way
for
an
application
owner
to
rename
spans
if
he
has.
If.
B
So
this
is
their
first,
it
says
on
the
thing:
this
is
their
first
pr
ever
first
time,
github
contributor.
B
E
B
B
I
don't
know
if
any
of
the
the
contrib
package
authors
have
any
concerns
that
need
to
be
addressed
right
now,
and
I
know
that
the
metrics
work
is
kind
of
on
hold
right
now,
while
we
deal
with
these
releases
and
merging
the
the
new
framing
for
the
sdk,
but
beyond
those
things,
does
anyone
have
anything
that
that
they
would
like
to
bring
up.
A
B
Okay,
well,
I
I
hope
that
you
know
you
enjoy
what
you're
moving
on
to
you
next
and
thank
you
for
all
the
time
and
effort
you
put
into
this.
We
really
appreciate
it.
A
B
Okay,
well,
if
nobody
else
has
items
for
the
agenda,
I
guess
I'll.
Let
everyone
go
early.
I
know
it's
pretty
late
for
some
of
you
so.
B
Next
week
is
thanksgiving
in
the
us:
do
we
believe
that
we
should
it's
it's
the
day
before
thanksgiving?
Should
we
cancel
the
meeting
or
are
people
still
planning
on
being
here?
I
don't
know
who
is
wait.