►
From YouTube: 2023-03-01 meeting
Description
Open cncf-opentelemetry-meeting-3@cncf.io's Personal Meeting Room
A
B
A
B
A
I
mean
I,
don't
know,
let's
wait
a
bit
I
think
Anna.
If
I
remember
correctly,
was
based
in
Spain.
So.
B
B
B
Okay,
like
at
least
I
I,
always
have
a
few
things
that
I
can
bring
up
because
I
started
looking
at
getting
the
Milestone
or
getting
feature
of
the
feature
Flags
package,
and
they
call
to
version
one
and
just
what
that
means
and
I
think
there's
a
few
discussions
around
what
it
like
deprecation
of
feature
flags
and
when
you
should
deprecate,
which
would
be
interesting
to
go
over
at
least
with
you
here.
I
can
bounce
ideas
off
and
then
and
leave
some
notes
for
the
next
segment.
A
A
A
A
B
Basically,
what
I'm
thinking
is
like
this
three
parts
that
I
want
to
try
and
solve
for
this,
and
that's
the
developer,
ux,
the
user
ux
and
the
up
like
the
documentation
side
of
it,
because
I
was
looking
at
like
before
I
got
sick
I
was
looking
at
how
kubernetes
does
their
Flag
Management
and
they
have
a
pretty
much
a
running
total
or
a
page
that
just
has
all
the
latest
feature
Flags
when
they're
added
when
they
were
removed
or
sunsetted,
and
then
there's
just
a
deprecations
page
of
like
these
flags,
just
don't
no
longer
exist
and
for
the
deprecations
park
to
make
it
to
help
make
it
aware
for
users.
B
I
was
considering
making
that
just
a
release
artifact
that
it's
just
a
change
in
tree
for
a
feature
flag
deprecation.
So
that
way
you
can
go
into
a
different
change.
Log
all
the
same
change
log,
so
you
can
see
which
feature
flags
are
being
deprecated
in
what
version
I
think
that
solves
the
user,
ux
problem
plus
discovery
of
when
feature
flags
are
there
I,
just
don't
I
haven't
had
enough
time
to
think
about
the
story
for
the
developer
experience
where
you,
your
your
changes,
can
be
removed
from
the
future
gate.
A
But
in
terms
of
the
user
once
a
feature,
gate
is
deprecated.
What
do
you
know
what
the
behavior
in
kubernetes
is
like?
Would
it
fail
on
graffiti
start
or
yeah
I,
don't
know?
What's
what's
the
story
there,
because.
A
Of
the
things
that
I'm
yeah
on
the
fence
about
I,
don't
know
if
we
should
allow
you
to
enable
something
that
is
deprecated,
but
not
disable
it
or
if
we
should
just
erode
or
if
we
should
do
one
at
first
and
then
the
other.
B
B
So
I
I
will
spend
a
bit
more
time
on
that
because
yeah
getting
sick
wasn't
fun.
A
Yeah,
sorry
about
that
so
yeah
I,
guess
yeah.
We
can
continue
on
the
issue.
B
Hey
that
was
the
other.
That
was
the
only
thing
that
I
was
currently
working
on
or
that
I
remember
working
on
I,
don't
know
if
you
have
anything
else,
that's
urgent,
popular.
A
A
B
A
A
B
B
Actually,
I'm
might
ground
your
opinion
on
something
so
in
the
collector
I've
been
trying
to
work
on
a
on
the
trip.
Sorry,
a
component
wrapper
for
the
life
cycle
part
that's
a
relatively
old
PR
that
I
need
to
get
back
to,
however,
I'll
be
interested.
If
there's
one
problem,
I'm
really
struggling
to
solve.
B
Fairness,
I
hadn't
actually
looked
at
it
for
a
few
versions
now
so
I
need
to
get
back
to
it.
However,
with
the
shared
components,
if
they're
using
this
shared
shared
component
map,
where
they've
either
in
the
map
or
they
get
created,
the
problem
is
if
a
component
is
wrapped.
B
A
His
first
time,
I
see
it
so
I
guess:
I
need
first
like
what's
what's
the
goal
of
the
the
component
helper
like
what
what's
the
problem
that
you're.
B
A
B
So
if
like,
if
you
start
all
the
components
and
then
in
that
start
phase,
if
you
stop
and
then
fail,
The
Collector
will
then
go
shut
down
everything,
but
it
can
shut
down
components
that
haven't
been
started,
which
the
component
interface
says.
That's
completely
fine,
but
some
code,
like
some
components,
haven't
properly
implemented
that
I
think
at
the
time
it
was
Prometheus.
B
A
Okay,
my
next
question
then,
is
so
are
you
we
have
say
the
exported
helper,
the
receiver
I
don't
know
if
there's
a
reasonable
actually
well.
A
Who
are
building
different
types
of
components
and
or
the
types
of
components
where
we
have?
That
is
the
goal
that
the
protocol
per
se
uses
this
component
upper
under
the
hood
or
how
would
that
work.
B
Yeah,
so
one
thing
I
haven't
quite
figured
out
because,
like
all
the
other
like,
like
the
helpers,
extend
the
component
type,
so
I
don't
know
if
those
helpers
should
use
the
component
helper
within
their
helper
function
or
if
you
wrap
it
again
on
top
like
outside
of
it.
So
you
use
the
receiver
Helper
and
then
the
component
help
out.
If
that
makes
sense,.
B
Theoretically,
I
would
I
would
like
it
to
be
part
of
the
extended
type
helpers.
So
that
way,
it's
less
code
being
duplicated.
A
Yeah
I,
wouldn't
yeah
I
would
favor
that
that
option
myself
too
on.
B
A
A
A
B
I
think
that
I
think
that
solves
a
bit
for
me,
but
I
also
need
to
get
back
because
I
know
there
was
an
update
to
Shared
components
and
how
they
work.
So
I
think
I
might
be
able
to
be
able
to
use
that
one
a
bit
more.
B
B
B
Ope
I'm
gonna
try
to
go
all
right.
Let
me
sign
that
here.
So
my
the
other
big
thing
that
I
was
working
on
was
the
schema
processor,
which
was
part
of
the
spec
for
The
Collector,
the
for
collector
assisted
schema
translations
I
had
written
a
lot
of
it
while
traveling,
so
it
wasn't
great
or
it
was
like
very
rushed.
B
So
I'd
like
split
this
up
into
four
parts
where
it's
just
like
the
config,
the
initial
types
and
the
actual
business
logic
and
business
logic,
part
two.
B
So
basically,
I
don't
know
how
much
you
know
about
this
schema
types,
but
basically
we
have
a
schema
type
definition
which
basically
says
from
these
versions.
This
is
how
you
change
to
and
from
and
then
from
there
you
can
take
those
translations
and
apply
them
to
all
data
running
through
that
processor,
yep.
B
And
then
from
there
it's
just
applying
those
modifications
in
the
processor
and
then
passing
it
on,
but
I.
Don't
think
the
naming's
done
quite
well
and
I
also
remember
writing
this
before
generics
were
a
thing.
So,
since
the
original
Upstream
package
redefine
the
type
for
string,
it
made
it
hard
just
to
make
a
generic
function
for
the
like
Constructor
for
the
type
I
could
have
used
the
options
pattern,
but
at
the
time
I
couldn't
be
asked.
B
So
I
might
revisit
that
and
just
clean
it
up,
but
I'm
curious
if
there's
anything
else
that
you
would
want
to
see
addressed
in
an
spr
and
I
know
I'm
putting
on
you
on
the
spot.
So
sorry
about
that.
A
No
worries
I
mean
I,
just
think
it's
going
to
be
hard
for
me
to
give
an
answer
to
that
right
now,
because
it's
a
huge
VR,
yeah
I
mean
I'm
familiar
with
schemas
and
I've.
Read
the
video
tape
on.
A
Yeah,
oh
sorry,
I'm
so
used
to
people
I'll
get
back
to
you
on
the
actual
ER.
If
that's
okay,
you.
A
Yeah
I'm
in
a
I
haven't
been
reviewing
it,
but
I.
The
schema
procedure
is
something
that
I
was
interested
in
for
for
data,
so
yeah
I'm,
Gonna
Leave
it
to
some
extent.
A
A
Back
to
you
on
that,
actually
here.
B
Yeah
I
I
at
the
moment,
that's
it
for
me.
Those
are
the
three
main
things
that
I
was
working
on.
A
Okay,
yeah
I
didn't
have
anything
busy
moving
homes.
A
Yeah
so
so
yeah
I
guess
we
can
leave
it
here
around
I
hope
that
in
future
meetings,
like
people
know
about
this
or
can
join
we'll
see
yeah.