►
From YouTube: 2023-03-08 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
A
A
A
And
I
have
submitted
to
PRS
a
few
folks
could
review
it.
That
would
be
great
I,
I
think
on
the
resource
attributes
I
included
both
the
ones
we
had
under
the
normal
and
the
varying
resource
attributes.
A
C
A
D
A
A
I
was
thinking
that,
while
you
continue
working
on
the
events,
LDK
events
API
interviewing
SDK,
he
can
start
on
the
protecting
of.
Maybe
you
know
the
first
event.
Maybe
the
page
view
event
that
is
essentially,
you
know
creating
a
new
package
from
from
the
existing
code,
but
it
will
emit
an
event
instead
of
a
spam
using
the
new
conventions
that
will
come
up
with.
He
will
also
need
to
introduce
the
log
attribute
so
he'll.
A
B
Yeah,
that's
that's
great.
That's
sounds
good
to
me.
A
And
yesterday
we
also
spoke
about
talking
to
you
know
Daniel
about
the
sandbox
progress
as
well.
As
you
know,
what
his
latest
thinking
is
with
respect
to
keeping
the
the
node
and
the
web
code
together
in
in
one
place.
A
I
I,
don't
have
any
specific
opinion,
but
I
I
thought
we
should
start
talking
about
it
more
seriously.
Now
in
the
jsic
as
well-
and
you
know
to
me,
whenever
I
look
at
the
code
I,
it
does
feel
a
little
complicated
and
and
then
that's
because
you
know
we
have
to
support,
because
the
code
is
split
across
multiple
packages
and.
A
And
there
are
also
scenarios
for
for
the
node
that
that
you
know
are
to
be
supported.
I
mean
there
are
two
use
cases
that
need
to
be
supported
and
it's
confusing
and
and
also
we
I,
don't
know
much
about
the
sandbox
like
do
we
have
any
indication
on
on
the
size
that's
coming
out
for
for
the
web,
API
plus
SDK
bundle
the
download
that
customers
will
have
to
do
the
end
users.
E
Sorry
I
was
talking,
but
I
was
muted.
On
that
thing
you
only
have
a
quick
look,
because
that
is
one
of
the
things
the
sandbox
does
do.
E
So,
if
you
look
at
the
the
web,
SDK
I
haven't
built
it
yeah.
Okay,
now
let
me
build
it
and
then
I'll
tell
you
what
size
it
is.
Give
me
about
five
minutes:
okay,
yeah
I
gotta
fix
up
some
JS
bugs
that
haven't
been
merged.
Yet
that's
one
of
the
PRS.
B
That's
just
gonna
be
the
only
difference.
There
is
going
to
be
that
it's
going
to
be
packaged
with
not
with
webpack
but
with.
E
With
roll
up
yeah
yeah,
yeah
webpack
will
be
larger,
it
just
is,
but
it
gives
an
indication
which
is
the
whole
point
of
doing
this
is
having
a
baseline
so
that
when
I
get
the
minification
work
going,
it's
we
can
like
say.
Are
we
getting
better
or
worse.
D
D
B
E
20K,
okay,
okay,
that's
just
the
API!
That's
nothing
else!
I
think
that's
hasn't
got
to
be
twice
SDK
yet.
A
A
Yeah
I
guess
the
question
is:
do
we
have
a
reason
to
believe
that
if
there
was
no
like
this
all
excludes
the
node
code.
E
Yes,
this
is
this
is
just
the
the
web
code
and
they're
the
individual
things,
so
the
core
will
include
the
API,
because
that's
just
the
way
the
bundling
works
for
these
are
effectively
creating.
You
know
downloadable
web
bundles,
so
it's
just
building
Trace
base.
E
E
So
I'm
not
quite
sure,
what's
in
the
metric
SDK
but
minified,
it's
72k
unminified,
there's
177.,
so
that's
probably
dragging
in
a
bunch
of
the
trace
stuff,
I'm
gonna
guess.
E
E
Care
yeah,
so
the
SDK
comes
down
to
16.25
K.
E
So
it's
the
SDK
web
100
wins
it,
which
that's
using
the
latest
version
of
WinZip.
So
it's
not
that's
better
than
what
Giza
could
get
so,
but
again,
it's
still
includes.
Hardly
anything.
E
So
yeah
that
so
the
whole
point
of
of
this
pre-bundling
is
so
that
I've
got
a
Baseline
really
and
until
I
can
bring
the
examples
over
which
isn't
going
to
happen
anytime
soon
to
see
what
I
get
the
complete
list.
It's
going
to
be
painful.
I
know
when
I
did
my
OneNote
a
couple
of
years
ago.
C
A
A
So
I
think
my
I
also
I'm
curious,
like
what
are
your
individual
thoughts
on
on
this
topic
of
keeping
the
code
combined
is.
Is
that
okay
long
term,
or
do
you
feel
it's
good
to
have
separate
code
basis
so
that
we
can
have
a
more
concise.
E
D
D
A
A
Yeah
I
mean
that
in
general,
the
the
way,
the
code
so
on
the
on
the
browser.
I
can
understand
that
you
know
you
don't
want
to
include
both
the
printable
friend.
Let's
say
you
know,
Json
exporters,
you
know
at
the
same
time
it's
unnecessary,
but
for
a
back-end,
app
I
I,
don't
know
how
size
is
a.
You
know,
big
concern,
because
for
the
for
the
Java
case-
and
you
know
several
other
languages,
you
know
I
I,
don't
think
that
code
is
split
into
so
many
tiny
packages.
Yeah.
D
E
C
E
So
yeah
I
got
to
this
point
and
went
you
know:
I
can't
use
this.
That's
that's
even
before
I've
got
to
layer
out
stuff
on
top,
so
this
is
what
eventually
drew
me
to
to
try
and
get
the
sandbox
up
and
running,
and
initially
it
was
just
copying.
The
code
over
with
a
manual
merge
every
time,
but
Daniel
wanted
to
keep
the
history.
E
So
that's
where
we're
at
and
why
I'm
going
through
so
many
convoluted
steps
to
get
it
over
so
that
it
we
can
keep
the
history
so
that
you're
playing
in
this
hand
box.
You
can
see
the
complete
history
of
the
file.
E
Okay,
but
yeah
I
I,
you
know
my
gut
field
is
it.
It
needs
to
be
separated
at
the
very
minimum.
I
think
Daniel
wants
to
keep
the
API,
but
I
I.
Think
even
core
has
got
stuff
in
there
that
we
don't
want.
E
The
key
piece
is
going
to
try
and
keep
API
level
compatibility
So
in
theory.
You
could
write
an
instrumentation
or
grab
an
existing
instrumentation
and
get
that
right
on
top,
but
I
guess
we'll
see
how
we
go
like
there's,
probably
enough
in
the
sandbox.
Now,
if
we
wanted
to
create
a
branch
assuming
we
only
want
to
keep
the
API
that
we
could
go
off
and
do
that
and
start
it
already,
because
the
API
is
already
there
API
core
and
a
few
other
bits
and
pieces.
Where
is
it.
B
So
something
in
theory,
if
we,
if
he
kept
the
if
we
kept
the
API
the
way
it
is
and
and
finished
and
finished,
like
the
you
know,
the
sdks
and
the
instrumentations,
based
on
what
we
have
now
then
like
some,
even
if
we
have
instrumentations
that
need
to
use
those
apis
in
the
future
like
if
you
have
a
different
SDK,
which
is
you
could
customers
could
just
swap
those
out
correct.
B
E
Yeah
so
I
pasted
a
link
into
where
the
where
I
dropped
the
packages
so
already
in
the
sandbox
in
main
already
is
the
API
context,
core
resources
and
semantic
conventions.
As
of
about
a
week
ago,
like
two
weeks
ago,
let's
say
that
my
script
PR,
that's,
there
is
to
fix
resources
introduced
introduced.
I
could
speak
properly,
introduced
a
a
test
for
testing
with
version
1.9
and
that
broke
the
script.
I've
now
got
it
working
as
part
of
that
PR
except
the
pr
it's
broken.
E
No
I
know
it's
going
to
be
broken
because
the
tests
are
failing,
because
we
need
code
changes
from
okay,
Latino
I've
got
some
type
issues.
I
need
to
fix,
okay,
too
easy
so
effectively.
It
runs
a
rush
check
which
just
makes
sure
that
all
packages
are
using
the
same
versions
and
they
don't,
which
is
why
it's
failing
at
the
moment.
I'll
fix
that
shortly.
E
In
terms
of
timing,
I'm-
probably
not
going
to
have
much
time
for
the
rest
of
this
month,
I'm
currently
working
on
a
Beta
release,
I'm
going
to
I'm
going
to
be
pushing
out
for
an
internal
versions,
and
we
still
have
a
lot
of
code
to
write.
So
even
though
I've
got
two
other
people
working
with
me,
we
have
a
end
of
March
deadline,
so.
C
E
I
get
the
sandbox
up
and
running
I'm,
probably
going
to
pause
until
April.
A
So
now,
so
what
what
do
we
want
to
like?
How
do
you
want
to
structure
the
discussion
with
Daniel
next
week.
B
E
Been
trying
to
get
the
sandbox
going,
okay
might
as
well
as
prepping
your
release
like
I'm,
doing
a
release
today,
okay,
which
is
a
pre-release
before
we
actually
promote
our
leader,
so
I'm
actually
doing
multiple
releases
this
month,
which
is
the
problem.
Okay,.
A
Martin,
are
you
planning
to
join
the
JS
I?
Think.
B
I
will
probably
not
join
today.
Okay,
next
weekend,
okay,
yeah.
E
And
the
sandbox
should
be
up
and
running
by
next
week,
based
on
how
I'm
going
the
camera
PR
almost
included.
All
the
instrumentations
I've
ended
up
changing
the
location
a
little
bit
but
I
think
it's
for
the
better,
so
effectively
I'm
dragging
in
Fetch
xhr
document,
load,
user
interaction
and
long
task.
E
They
have
a
couple
of
compile
errors
because
the
sandbox
uses
a
later
version
of
typescript,
which
is
the
other
PR.
That's
open
in
JS.
At
the
moment,.
E
C
E
I
haven't
tried
with
doing
that
completely
it's.
There
are
a
couple
of
issues.
That's
stopped
upgrading
typescript,
previously
one
of
the
ones
was
people
were
starting
to
use
some
of
the
new
typescript
features
which
were
then
breaking
backward
compatibility
but
I
think
there's
some
components
that
are
currently
outdated,
that
weren't
compiled
with
the
or
won't
work
with
the
latest
typescript
either
and
the
es
link
it
complains.
E
But
at
the
moment
it's
still
working,
at
least
in
the
sandbox
but
yeah
it's
it's
not
just
a
case
of
just
updating,
typescript,
there's
a
whole
bunch
of
stuff
that
yeah.
B
E
But
yeah
trying
to
keep
them
up
to
date.
I
know
one
of
the
discussions
was
last
week.
The
week
before
was
how
do
we
go
about
upgrading
the
JS
repo
to
use
Rush
instead
of
Luna?
So
that's
on
target
on
on
a
potential
thing
as
well
and
the
sandboxes
one
of
the
ones
that
will
show
how
to
do
that.
But
it's
still
like
at
least
a
week
or
two
of
work
just
to
upgrade
the
main
JS
repo
to
use
Rush
instead
of
learner.
So.
B
Can
can
you
remind
me
why,
in
the
sandbox
you
are
using
a
newer
version
of
typescript.
E
It's
pretty
cases
just
keeping
it
up.
To
date,
I
I
was
using
a
slightly
later
version,
I
bumped
it
up
to
the
the
very
latest
version.
Recently
yeah.
It's
just
keeping
you
up
to
date,
yeah,
like
the
the
main
one
uses
4.4.4
I,
think
it
is
I
was
originally
using
475
and
now
I'm
using
495..
E
B
B
Yeah
I,
don't
I,
don't
know
like
if
you
what
kind
of
feedback
you
get
from
from
you
know
from
the
rest
of
the
chess
group
on
making
this
change
without
upgrading
typescript.
So
I
was
just
wondering
like
if
the
alternative
would
be
to
to
use
the
same
version
of
typescript
as
they
have
for
now.
Yeah.
E
Yeah,
just
a
bunch
of
like
in
terms
of
what
versions
get
used.
It's
the
merge
script
is
the
thing
that
enforces
the
specific
versions
so
actually
overwrite.
Whatever
the
other
versions,
they've
got
and
I
say
you
need
to
be
at
least
this
version.
E
So
if
we
want
to
roll
it
back,
we
could
quite
easily
I've
already
done
one
push
to
the
JS
repo
to
fix
one
of
the
typing
issues
and
that
got
approved
like
in
the
same
day,
actually
the
the
JS,
the
one
yesterday
you
know
was
it,
but
no
one's
looked
at
it
yet
so
I
was
going
to
bring
it
up
in
the
JSC,
so
I'm
hoping
that'll
get
in
pretty
quickly
as
well.
E
B
Okay,
actually
Market
just
approved
Europe
excellent.
E
E
B
Okay,
so
yeah
I'm,
I'm
I'll
be
back
on
Friday,
but
it
I
can
I
can
reach
out
to
abernet
about
like
how
you
how
we
can
work
on
the
prototype
together.
Yeah.