►
From YouTube: 2021-09-15 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
Am
I
actually
audible
because
I've
had
problems
with
firefox
and
audio
with
zoom
today,
yeah.
C
A
E
We
decided
not
to
release
the
package
sdk
node,
because
it
depends
on
experimental
and
contrib
packages,
so
we're
holding
that
back
for
now,
but
it
can
be
promoted
soon.
When
we
resolve
those
issues,
we
just
didn't
want
it
to
hold
back
all
of
the
other
packages,
so
all
the
various
sdk
packages
will
be
released
as
1.0.
E
The
last
issue
holding
that
back
is
renaming
the
collector
exporter
packages
so
that
they
are
the
otlp
exported
packages,
which
is
a
more
accurate
way
to
refer
to
them.
It
also
makes
it
a
little
bit
more
clear
what
transport
is
being
used
between
hdp
and
grpc
and
protobuf
and
stuff
like
that.
E
E
Beyond
that,
I
am
not
aware
of
anything
else
that
is
holding
back
the
1.0,
but
if
anybody
else
is,
please
speak
up
we're
trying
to
release
as
soon
as
possible
here
now
at
this
point.
So
if
there's
something
that
that
needs
to
be
addressed
before
the
1.0
time
is
running
out.
A
A
E
E
Barton
valentine,
are
you
happy
with
where
we're
at
for
the
for
the
release,
yeah,
sure,
okay,
I
saw
that
will
opened
up
a
pr
for
the
release,
please
automation
in
contrib,
but
it
hasn't
really
been
reviewed
yet
so
this
is,
I
think,
the
last
step
before
you
know
of
the
contrib
package
ownership
story.
E
Once
this
is
merged
every
time
a
pr
is
merged,
the
release,
pr
will
be
updated
and
all
it'll
take
to
release
it
will
be
merging
it.
E
F
Yeah
I'll
probably
just
include
it
in
that
one,
so
I
just
wanted
to
confirm
that,
like
it'll,
do
like
an
npm
publish
of
all
the
updated
packages
or
the
release
packages
and
then
also
probably
cut
an
individual
github
release
per
package
as
well.
F
E
F
What's
what's
the
deal
there,
I'm
not
actually
sure.
If
release,
please
does
okay.
Yes,
they
do
do.
I
actually
haven't
checked
what
they
do
for
github
releases.
I
was
more
concerned
with
the
npm
releases,
which
they
don't
do
by
default,
but
I
know
at
least
for
other
hotel
repos,
the
other
hotel,
contrib
repos,
like
python
and
net.
F
They
do
one
release
per
component
for
on
github,
as
opposed
to
you
know,
grouping
them
together,
and
so,
but
I
guess
they
also
have
slightly
different
tooling,
but
in
general
I
think
it
probably
makes
more
sense.
Like
you
know,
if
there
were
two
completely
unrelated
packages
that
happen
to
be
updated
on
the
same
day,
like
probably
doesn't
make,
there's
not
a
huge
reason
to
be
including
them
in
the
same
release
that
could
be
confusing.
B
E
Yeah,
if
release,
please
can
be
configured
that
way
then
great.
If
not,
I
don't
think
that
it
should
be
a
blocker
for
now
it's
something
that
we
can.
We
can
change
later,
but
I
think
the
default
behavior
is
going
to
be
creating
one
release,
because
I
know
the
way
that
the
publish
automation
works
is.
It
looks
at
like
the
build
output
to
see
if
a
release
has
been
created
and
if
so
it
runs
the
publish
step.
E
So
I
I
don't
see
how
that
would
work
with
more
than
one
release
being
created,
but
that's
you
know
something
you
can
look
into
if
you
feel
like
it's
important.
F
Yeah,
no,
I
I'm
looking
at
it
now
and
I
yeah,
I
definitely
think,
you're
right.
So
I
I'm
a
if
you're.
Okay
with
that,
then
I'm
okay.
With
that,
I
just
wasn't.
I
wasn't
sure
if
it
was
even
included
in
release,
please
functionality
and
just
thought
it
was
gonna,
be
something
that
we'd
have
to
do
ourselves
so
yeah.
If
that's
how
release?
Please
does
it
then
that's
totally
cool
with.
E
Me
speaking
of
releases,
I'm
not
sure
who
noticed
or
was
aware,
but
the
release
for
zero
25
actually
failed,
because
the
test
utils
package
when
it
was
made
public,
it
didn't
get
a
published
configuration
in
the
package.json,
which
is
something
that's
easy
to
miss.
But
I
created
a
pr
to
add
that
just
so
that
we
won't
have
these
failures
again
in
the
future.
E
This
is
all
we
were
missing
and
I
did
go
ahead
and
finish
the
release
manually
on
my
local
machine,
so
the
zero
25
release
is
out
now
sorry
that
took
so
long
in
the
future.
We'll
we'll
try
to
not
have
issues
like
that,
and
hopefully
the
release,
please
automation
that
will
is
contributing,
will
make
that
a
little
bit
easier.
F
So
the
test
utils
package
was
released
for
the
first
time
yeah.
I
just
released
it
like
12
minutes
ago.
E
The
next
issue
that
I
want
to
talk
about
is
this
es2017
versus
es5
issue.
I
don't
know
if
legitimacus
is
on
the
call.
It
looks
like
no,
but
he
created
a
pr
here
which
updates
the
esm
output
to
target
es
2017
instead
of
es5.
B
E
That
the
build
tooling
doesn't
transpile
es
2017
back
to
es5.
So
a
lot
of
build
tooling
that
does
support
esm
will
output.
E
The
john
here
added
a
comment
for
a
vote
for
just
leave
it
as
is,
and
the
original
pr
author
actually
gave
it
a
thumbs
up.
He
hasn't
replied
here,
but
actually
bart.
This
is
a
question
for
you.
Are
you?
Okay?
If
I
just
close
this
pr.
D
E
E
This
stems
from
the
fact
that
we're
using
what
is
the
package
lodash
dot
merge,
I
think,
which
does
not
use
valid
esm.
E
E
There
is
some
discussion
that,
if
we're
careful
about
not
exporting
types
from
the
from
modules,
then
maybe
we
won't,
but
I
think
my
opinion
here
is
that
I
would
rather
not
enable
the
es
module
in
route
flag,
but
I'm
looking
for
input
from
bart
and
any
other
browser
experts
that
we
have
on
the
call.
Do
you
think
that
that's
I'm
not
that
familiar
with
esm,
so
I
wasn't
even
aware
that
the
esm
builds
were
were
broken.
B
I'm
I'm
wondering
so
you
say
that
the
lowdash
is
the
problem
to
get
it
all
going.
I
wonder
how
much
of
low
des
do
we
use?
Is
it
were
to
just
if
it's
like
one
or
two
factors?
We
can
probably
just
embed
those
two
functions,
and
you
know
you
know
in
a
exam
compatible
way,
instead
of
dragging
in
low
dash.
B
If
you
only
use
like
the
to
do
like
a
deep,
merge
or
objects
or
something
I
can
imagine
that
we
can
either
find
an
alternative
that
is
works
or
just
include
that
specific
function
in
the
in
in
our
project.
E
A
E
Yeah,
so
I
mean
we
could
copy
it
into.
I
guess
the
core
package,
if
you
would
prefer-
or
we
can
change
the
dependency
to
be
something
that's
esm
compliant,
I
probably
would
prefer
to
just
copy
it
in
just
so
that
we
avoid
you
know
I
prefer
not
to
pull
in
external
dependencies
whenever
possible,
but
I
could
be
convinced
either
way
really.
E
E
E
E
B
E
D
E
B
E
I
did
want
to
quickly
mention
that
we
have
a
governance
committee
elections
coming
up
soon.
For
those
that
don't
know
the
elections
will
be
at
the
end
of
october.
E
So
in
order
to
vote
in
the
election,
you
need
to
be
a
member
of
the
hotel
organization,
so
for
those
that
are
not
members
and
feel
like
they
would
like
to
vote
now
is
the
time
to
try
to
become.
E
And
for
those
that
didn't
know
that
we
have
governance
committee
elections
coming
up
now,
you
know
so
the
candidates
will
be.
I
think
I
think
there
will
be
a
blog
post
or
an
email
with
the
candidates
on
october
15th
and
then
the
actual
vote
will
happen
at
the
end
of
october.
I
think
the
26th,
through
the
28th,
if
I
remember
correctly
so
some
of
the
the
details
are
still
being
formalized
in
terms
of
how
the
election
will
actually
be
run,
but
I
think
those
are
the
important
dates
that
people
should
know.
E
Just
asking
for
this
pr
to
be
reviewed:
oh
it's
the
spec!
Yes,
we
talked
about
this
on
a
specification
call
yesterday
and
on
the
maintainers
call
on
monday.
Actually,
apparently,
because
we
are
one
of
the
only
sigs
that
enable
gzip
compression
by
default
in
our
otlp.
E
He's
just
wants
to
make
sure
that
specification.
Pr
is
okay
with
us,
so
I'll.
Look
at
this
after
the
call
and
bart.
I
think
you
also
should
because
you're
the
most
familiar
with
our
collector
exporter
situation.
E
Okay
and
will
can
we
expect
a
1.0
this
week,
that's
difficult
to
say
it
depends
on
how
quickly
we
can
get
the
collector
renaming
done
and
whether
anything
else
comes
up.
My
tentative
answer
would
be
yes.
That
said,
I'm
going
on
vacation
I'll
be
gone
tomorrow
and
friday.
E
So
if
we
can
get
the
collector
renaming
finish
today
and
we
feel
ready
for
the
release,
we
can
do
it
or
you
guys
can
do
it
while
I'm
gone
and
the
other
maintainers
are,
I
think,
still
capable
and-
and
that
would
be
fine
with
me
if
you
do
it
while
I'm
gone
or
you
can
wait
for
me
to
get
back
if
we
prefer
to
have
everybody
here.
So
if
we
don't
do
it
this
week,
then
it
will
be
done
monday.
I
assume
at
the
latest.
F
Yeah,
I
think
it
would
be
exciting
to
get
it
done
today,
if
that,
if
it's
possible,
since
it
looks
like
valentin
already
approved
the
collector
renaming
so
but
yeah,
I
just
wanted
to
see
if
there
would
be
any
other
blockers
for
it
but
yeah,
it
seems
like
it's
right
there
right
at
the
finish
line.
So
it's
pretty.
E
Yeah
I
feel
like
we've
been
we've
been
trying
to
get
this
done
for
weeks
now.
I
feel
like
every
time
I
go
to
the
maintainers
meeting
and
tell
them
oh
yeah,
we're
doing
the
1.0
like
this
week
or
next,
and
I've
been
saying
that
for
like
two
or
three
months
now,
so
I
I
I
feel
very
ready
to
be
done
with
this.
F
Yeah,
if
yeah,
if
there's
more
approval
on
the
on
the
collector
renaming,
then
and
it
gets
merged,
and
that
would
be
pretty
yeah,
hopefully
a
good
thing
to
do
right
before
vacation
and
that
you
could
really
have
a
have
a
good
vacation
after
that.
E
Okay,
yeah,
so
that
that's
that's
my
my
short
answer.
Hopefully
so.
Does
anyone
else
have
anything
that
they
would
like
to
talk
about?
I
know
we
had
sort
of
a
short
meeting
today
kind
of
a
good
change.
H
Sorry
I
was
just
gonna
plus
one.
What
will
said
yeah
1.0
is
really
exciting
and
would
love
to
see
it
soon.
H
E
I
think
if
nobody
has
anything
else,
you
probably
just
call
the
meeting
early
today.
B
Yeah
I
had
one
question
yeah
go
forward.
I
posted.
F
B
The
in
the
select
channel
about
the
the
metric
sdk,
I
was
wondering,
did
we
base
ours
on
a
like,
like
one
of
the
prototypes
of
a
different
language
like
like
the
java
one,
or
did
you
just
go
about
it
ourselves
in
a.
E
The
sdk
that
we
have
now
was
based
around
the
go
prototype
from
the
old
metric
specification.
I
think
bart
was
the
one
that
originally
wrote
most
of
our
current
metrics
sdk.
So
he
can
correct
me
if
I'm
wrong
about
that,
but
I
think
it
was
based
on
the
go
implementation.
D
Yeah
it's
it's
from
like
last
year,
but
the
thing
is
that
I
mean
the
output
of
the
metrics
are
quite
up-to-date.
I
would
say
the
internals
are
different,
but
the
spec
is
like
almost
finished
in
the
alpha
state.
So
once
this
happened,
I
can
go
back
and
and
refactor
the
the
metrics
and
currently
I've
been
told
not
yet
so
it's
it's.
It's
probably
may
may
happen.
I
don't
know
if
this
month
or
if
not,
then
then
probably
next
one
but
but
yeah.
It's
all
about
the
specification
because,
like
last
year
the
specification
was
changing.
E
I
think
that
they
would
have
the
last
that
I
heard
was
that
they
feature
freeze
the
api
so
that
there
can
be
time
for
some
sdk
prototypes
to
be
built
and
if
they
find
additional
issues
with
the
api,
while
they're
building
sdk
prototypes,
then
they
still
might
change
it.
But
the
api
should
be
considered
basically
stable
right
now,
and
the
sdk
spec
is
getting
very
close
to
that.
D
B
Okay,
cool-
I
was
just
wondering
just
amazing
right.
E
B
Yeah
one
question
I
can
imagine
because
of
the
changes
in
the
sdk
in
the
metrics
pack,
because
it
seems
to
do
a
bit
more
than
before.
It's
like
my
first
understanding.
Would
it
be
smart
to
have
like
some
performance
tests
for
it,
because
I
couldn't
find
them
previously.
E
I
mean
I
would
always
love
to
have
performance
tests
we
used
to
have
a
benchmark
for
the
tracing.
I
think
it's
actually
kind
of
out
of
date
right
now,
but
I
think,
as
we
mature,
more
performance
tests
and
things
like
that
will
become
more
important.
E
E
B
Oh,
I
was
just
wondering
if
that
would
be
something
if
that
would
be
a
good
thing,
because
I
can
imagine
that
the
open
military
committee
probably
wants
to
have
like
a
minimum
kind
experience.
We
have
some
sort
of
expectation
or
what
the
minimum
throughput
or
like
performance
of
the
different
sdks
are
like
try
to
have
them
in
specific.
E
I
don't
think
there's
been
any
like
formalized
requirements
for
like
minimum
performance
or
maximum
performance
impact
of
any
of
the
sdks,
but
certainly
as
the
project
matures
that's
something
that
will
become
more
and
more
important.
E
All
right,
everybody
have
a
good
week
and
I'll
talk
to
you
next
week,
hopefully
after
the
1.0
release.