►
From YouTube: 2022-06-06 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
A
C
A
So
I
mean
anything
we
already
discussed
on
these.
I
think
one
first
of
june.
B
C
A
The
second
one,
I
think,
there's
no
further
update.
I
have,
I
think
I've
I
mean
I'm
I'm
starting
to
work
on
the
sorry
on
the
mile
on
the
pending
milestone
issues.
So
basically
I'll
be
working
on.
B
A
I
was
thinking
that
we
will
have
a
release
candidate
and
then
probably
will
have
a
subsequent,
probably
couple
of
releases.
After
that
we
may
have
two
releases
for
a
release
for
making
the
final
ga,
okay.
I
think
it
should
be
good
to
have
a
release
candidate
by
end
of
june,
and
our
last
release
was
okay,
so
we
still
have
probably.
B
Of
me
right,
this
looks
like,
and
I
think
now
maybe
like
may
15.
A
B
B
A
A
Let's
take
a
call,
maybe
next
week
I
think
probably
okay.
B
A
A
B
B
C
A
B
A
A
A
A
B
Everything
yeah
make
it
dedicated.
A
A
B
A
A
Yeah
that
results
fine
and
nothing
in
interoperability
with
other
languages.
I
think
even
I
didn't
raise
it
in
the
maintainers
meeting.
I
thought
of
doing
it
today
when
there
was
a
plan
for
subsequent
subsequent.
There
was
a
plan
which
was,
I
think,
being
discussed,
but
I
think
that
we
didn't
raise
it
but
yeah.
I
think
nothing
has
a
problem
which
we
have
to
do
in
this.
B
A
Log
hdk,
I
think
clean
up
for
log
name
so
yeah,
so
let's
target
it
in
the
next
release.
But
okay,
I
already
raised
the
issue
to
this.
I
I'll
see
if
I
can
take
it.
I
saw
there's
some
discussion,
but
I
can
check.
A
B
A
B
A
B
B
A
So
there
is
already
an
issue
for
log
removing
the
logger
name,
and
I
think
we
also
have
an
issue
for
specs
compliance
for
just
a.
B
A
Is
so
so?
Oh
and
the
oven
says
here
that
I
am
waiting
for
one
four
one:
three,
that
is
the
async
changes,
because
there
may
be
more
conflicts.
If
I
do
it
now,.
C
A
B
A
Okay,
I
think
we
can
quickly
look
into
the
pr's.
I
mean,
if
there's
nothing
else
to
add
in
this.
B
A
A
The
first
one
is
not
ready.
I
just
raised
it
because
I
plan
to
complete
it
by
today
end
of
day
today,
so
I
think
it
should
be
ready
by
today.
This
is
it's
a
bigger
change.
Actually,
this
will
break.
I
mean
it
will
bring
the
async
instrument
api,
which
we
have
as
of
now,
which
is
okay.
I
think
anyway,
I
think
the
matrix
I
think
we
are.
We
are
good
to
even
have
any
breaking
changes,
but
for
this
it
will
have
breaking
changes
in
the
matrix
api
for
creating
the
async
instruments.
B
A
Because,
as
of
now
the
when
we
create
the
async
instruments,
we
provide
the
callback,
but
there
is
but
that,
as
per
the
specs
now
we
a
given
instrument
can
have
multiple
callbacks.
So
we
need
to
change
the
api
and
which
we
have
to
provide
a
separate
method
to
add
callbacks.
A
A
A
A
A
Let's,
let's
wait
for
this
week
for
the
original
author
to
really
do
something
I
mean
otherwise.
I
think
we
can
take
a
call
of
creating
a
new
vpn
merge.
Also
completely.
I
think
that's
probably
it's
important
now,
I
think,
should
not
keep
it
open
for
a
long
time.
I
think
then.
I
also
have
to
start
looking
into
this.
Let's,
okay,.
C
B
A
A
Okay,
there
is
another
pr,
which
is,
I
think,
it's
just
it's
a
small
one,
add
the
attribute
dimensions
to
matrix
or
stream
exporter.
So
we
were
not
printing
the
attributes,
the
matrix
attributes
in
the
hosting
exporter.
A
So
we
already
have
the
method
to
print
the
attributes,
the
key
value
attributes,
so
I'm
just
using
that
method.
The
same
method
make
it
you
reusable
for
both
log
exporter,
matrix
exporter
and
span
exporter,
okay
and
then
that
that
way,
fixing
it
for
matrix
importance.
A
B
A
A
A
Yes,
that's
that's
what
it
is
trying
to
resolve.
We
should
not
have
multiple
trying
to
avoid
the
multiple
copies
of
these
static
variables.
Okay,
so,
which
is?
This
is
okay,
actually,
basically
for
the
semantic
variables,
I
think,
multiple
lots
of
semantic
variables,
so
I
think
multiple
copies
would
be
bit
heavy
for
them.
B
A
Yeah,
my
library
is
delivered,
reconcile
yeah,
it's
also
a
good
issue.
So
right
now
I
think
the
the
targets
which
are
created
for
bazel
and
for
cma
cut
bit
different.
They
are
consistent
with
each
other,
so
I
think
it's
important
to
have
a
consistent
targets
getting
created
for
through
both
of
them.
B
B
B
A
B
A
It's
it's
good
to
have
it
along
with
the
fluency
exporter,
the
etw
exporter,
so
that
at
least
for
the
geneva
we
have
all
the
things
that
one
place.
So
something
similar
to
how
right
now.net
is
doing.
has
moved
open,
telemetry
dot
net,
so
they
have
moved.
If
you
see
in
the
dotted
contract,
they
have
moved.
B
B
Any
vendors
specific
should
be
moving
into
country
sounds
like.
A
A
B
A
A
Probably
fix
it
then
we'll
close
this
once
we
do
that
we'll
close
this
issue,
we
already
have
another
issue
for
automation.
I
think
and
we'll
talk
we'll
track,
that
automation
issue.
B
Yeah
sure
I
will
attach
the
pr
the
release
vr
to
this
issue,
I'll.
A
B
A
B
A
A
A
A
A
C
B
A
C
A
A
B
A
B
A
A
No,
no,
there
won't
be
a
compilation
issue
because
we
are
still
using
the
same
same
I
mean
the
variable
is
still
the
same
right.
I
mean
that
the
std
variant
type.
B
A
So
it
won't
be
a
compilation
problem
and
I
think
it
won't
be
anywhere.
There
are
cases
where,
like
application,
libraries
are
built
separately,
okay
and
they
will
be
just
when
so.
The
libraries
are
built
separately
and
applications
are
built
separately.
The
instrumentation
libraries
are
built
separately
and
applications
are
built
separately
and
they
are
just
brought
at
the
time
when
we
are
deploying
it.
We
just
use
those
libraries
okay,
so
I
mean
that
this
will
not.
I
mean
this
will.
A
Therefore,
there
won't
be
a
scenario
where
there
can
be
a
compilation
issue,
because
sdk
is
still
being
built
using
the
old
old
api.
Our.
A
B
A
A
Yeah
I
mean
that's
that
that's
the
only
thing
whether
we
should
do
it,
I
mean
it's.
How
how
strong
is
the
case?
I
mean
it's
not
a
blocker.
Definitely
it
needs
more
work
for
the
instrumentation
library
like
in
this
case,
if
it's,
if
it's
pointer
of
care,
pointer
type
in
that
case,
they
have
to
explicitly
create.
A
B
B
C
A
B
B
A
B
C
B
C
A
B
A
A
A
A
A
More
from
my
side,
also
thanks
for
joining
the
meeting,
have
a
good
okay,
you're
coming
this
week
to
office
or
now
what's
up,
I
mean
just.
B
No,
I
didn't
go
to
office
today
for
this
week.
I'm
not
sure,
maybe
not
because
yeah,
due
to
recent
the
spread
of
covert
19
and.
A
I'm
planning
to
go
tomorrow,
I'm
not
sure
what
how
it
looks
like
I
mean,
because
it's
already
two
weeks
for
me
after
recovered
now,
I
think
I'm
totally
recovered
and
I
think.
B
Okay,
great
great
okay,.