►
From YouTube: 2022-06-23 meeting
Description
Open Telemetry Meeting 1's Personal Meeting Room
A
Welcome
to
another
edition
of
the
licensing,
let's
give
a
couple
of
minutes
for
folks
to
join
and
we
will
start
very
soon.
A
Please
add
your
names
to
the
attendees
list
and
if
you
have
any
topics,
issues
prs
that
you
want
to
discuss.
Please
add
them
there
as
well.
C
A
A
A
Yes,
okay,
perfect
right,
so
first
issue
I
wanted
to
discuss
is
well.
As
you
know,
we
have
already
released
a
release
candidate
of
metrics,
but
we
are
trying
to
release
stable.
A
That's
of
course,
our
ultimate
goal
on
this
metrics
project.
So
we
had
agreed
to
make
another
release
candidate.
I
think
it
was.
A
Something
that
we
want
to
release
this
week,
but
I
wanted
to
discuss
with
you.
What
would
it
need
for
us
to
officially.
A
A
C
A
A
Yeah,
I
mean
we
tag
a
bunch
of
issues
as
rc2,
but
even
before
that,
when
we,
when
one
month
had
passed
after
rc1,
we
didn't
have
those
issues
rc2,
but.
A
The
this
group
didn't
feel
confident
we
we
didn't
feel
like
we
wanted
to
make
a
stable
release,
but
we
preferred
to
make
a
another
release
candidate.
So
it's
a
it's
a
bit
of
a
more
of
a
high-level
question,
but
will
you
what
other
folks
I
am
interested
in
knowing
what
other
people
in
this
city
will
want
for
us
to
have
in
order
to
feel
confident
that
we
can
make
a
stable
rules.
C
Yeah
I
mean
if
nobody
else
has
comments.
I
would
like
to
hear
from
other
folks,
because
I
I
know
that
me
and
diego
have
been
probably
most
involved,
so
don't
want
it
to
be
like
an
echo
chamber,
but
I
think
my
idea
was
once
once
the
rc2
goes
out.
C
Hopefully
it's
like
I
can't
like
a
successful
candidate
right
and
then
we
can
just
promote
that
one
to
be
the
stable
release.
So
I
I
would
be
pretty
happy
once
people
try
out
the
rc2
and-
and
we
don't
see
you
know
a
bunch
of
bugs
coming
in
and
and
maybe
we
give
it
a
little
bit
of
time
to
like
incubate,
that
we
could
make
that
one
the
staple
release
or
make
the
next
release
of
staple
release.
So
that's
that's
where
I
stand.
I
think.
D
I
have
a
quick
question
just
regarding
terminology,
since
I'm
a
bit
new,
I
assumed
release
candidate
just
meant,
like
current
version,
that's
being
under,
that's
not
released.
Yet
it
sounds
like
release.
Candidate
means
a
release
but
unstable
version.
So
what
do
we
is
is
is
release
candidate.
How
do
I
put
this
like?
Is
there
something
before
release
candidate?
Is
there
a
terminology
for
that?
A
A
Experimental
code
that
wasn't
released
publicly
in
in
python,
there
is
a
way
to
indicate
that
something
is
not
meant
to
be
used
by
the
end
users,
and
that
is
adding
an
underscores
prefix.
So
we.
B
Had
that
our.
A
Our
entire
metrics
package
was
prefixed
with
an
underscore
and
when
we
made
our
rc1,
we
pretty
much
much
removed
that
underscore
so
we
published
an
api
with
that.
Now
it
is
a
still
release.
Candidate
means
it's
it's
a
message
for
users
to
say
that
this
still
needs
like
end
user
testing.
A
Right
needs
people
to
use
it
so
that
we
can
pretty
much
fix
plus
bugs
that
may
show
up,
but
our
release
candidate
also
means
that
we
don't
expect
significant
api
changes
so
that
the
api
that
is
published
should
remain
the
same.
A
Sure
so
I
agree
with
aaron
when
he
mentions
that
it's
a
murderer
of
people
using
it
so
that
box
can
be
found.
A
I
am
not
totally
sure
that
that
is
a
process
that
we
can
that
we
can
be
confident
that
will
happen
right
because
it's
it's
hard
to
know
how
many
people
will
use
it
or
if
they
will
use
it
at
all,
if
there
will
be
many
users
or
few
users
or
if
they
will
focus
on
only
on
one
part
of
the
project
or
solve
for
projects
so
I'll
like
to
propose
that
we
define
some
testing
objectives
so
that
we
can
focus
on
that
themselves.
A
I
know
it's
unfortunate
that
we
need
to
do
our
own
testing.
Of
course,
it'll
be
better.
If
more
people
will
do
so,
but
the
releasing
of
stable
it's
it's
an
it's
an
important
goal,
so
I
I
think
it'll
be
good
for
us.
A
If
we
push
for
that
stable
release-
and
I
can
collaborate
with
efforts
in
in
testing,
but
I
would
like
to
have
something
a
little
bit
more
clearly
defined
on
what
objectives
we
want,
so
that
at
the
end
of
this
testing
process,
we
feel
confident-
and
we
can
make
these.
C
So
when
you
say
testing,
do
you
mean
I'm
assuming
you
mean
like
use
using
it
to
accomplish
something
not
like
automated
testing
or
not
necessarily
automated
testing
right.
A
Yes
correct,
we,
I
already
have
unit
testing,
of
course,
but
but
yes,
I
I'm
thinking
about
pretty
much
doing
more
integration
testing,
where
we
experiment
with
different
explorers
with
the
collector
different
protocols.
Stuff
like
that,
that
it's
it's
an
effort
that
I
think
can
be
made
more
productive.
If
we
turn
them
into
examples
right,
so
they
can
live
in
our
documentation.
A
But
I
was,
I
was
proposing
that
maybe
we
can
define
a
series
of
objectives,
for
example
similar
that,
like
having
one
example
for
every
protocol
that
we
support
or
every
exporter
that
we
support
or
mixing
them
with
the
collector
or
something.
A
So
that
we
can
define
issues,
clear
issues
that
we
can
accomplish
when
that
process
is
done,
we
can
feel
satisfied
and
confident
that
we
can
make
salaries.
C
I
mean
yeah,
I'm
I'm
all
on
board
for
testing.
I
think
I
don't
know
I.
I
guess
I'm
just
wondering
about
the
timeline
of
that
work.
A
Yeah
I
would
like
yeah.
I
can
pretty
much
concentrate
on
this
effort
by
myself,
of
course,
as
as
we
did
before
for
first
release,
candidate
I'll
need
some
support
view
reviewing
prs,
but
I
can,
if
you're,
okay
with
this,
I
can
create
a
new
project
and
I
can
open
some
issues.
A
I
can
make
a
list
of
issues
where
each
issue
is
a
specific,
testable
objective
like
create
an
example
for
our
frontiers,
or
something
like
that
right,
so
that
we
have
a
list
of
these
issues
and
we
can
define
that
the
completion
of
these
issues
will
make
us
confident
enough,
so
that
we
can
have
a
still
release.
C
Yeah,
I
think
we
already
have
some
issues
for
creating
examples
like
more
geared
towards
documentation
is.
Were
you
thinking
something
like
beyond
that?.
A
Just
just
making
sure
that
we
have
enough
coverage
that
we
are
making
examples
for
all
the
stuff
that
we
need.
I
can
take
a
look
at
the
the
issues
that
exist
already
and
pretty
much
group
them
into
a
project
so
that
we
can.
C
Yeah
I
mean
I'm
obviously
not
opposed
to
that.
That
sounds
like
a
great
idea.
I
I
guess
we
did
have
you
know
quite
a
few
users
trying
trying
this
out
trying
out
the
previous
rc.
C
I
guess
I'm
just
I'm
worried
about
like
the
time
that
that
effort
would
take,
and
I
also
don't
want
you
to
get
burnt
out
diego
trying
to
push
this.
Thank
you
bud.
A
It's
stable
it's
an
important
goal.
I'm
I'm
a
little
bit
worried
that
if
we
don't
concentrate
efforts
in
this
goal,
it
may
get
delayed
right.
So
I
I
rather
make
a
good
sustainable
now
in
order
to
get
us
to
save
a
release,
hopefully
so
that
we
can
finally
check
this
complete,
have
a
stable
release
for
metrics
instead
of
like
making
this
process
take
more
and
more
time.
C
Okay,
I
mean
that
all
sounds
sounds
great
to
me.
I
guess
my
only
comment
would
be
since,
since
we're
missing
the
other
two
maintainers
today
it
might,
it
might
be
good
to
try
to
like
get
some
just
before
you.
You
know
commit
too
much
to
this.
C
It
would
be
good
to
maybe
like
open
an
issue
or
or
like
a
design
doc
or
something
for
like
the
road
map
or
path
to
disability,
to
sort
of
get
other
people's
criteria
like
I,
I
think
yeah
yeah
like
I
would
love
to
see
some
automated
testing
on
this
front.
Like
I've
with
the
google
cloud
exporters,
we
did
some
automated
testing,
where
you
would.
Basically,
you
know
capture
like
the
input
and
output
of
the
system,
sort
of
sort
of
like
an
end
to
end
test.
C
A
All
right:
okay,
yes
I'll!
Do
that
I'll.
A
Communicate
with
your
arrest
maintainers
and
expose
these
ideas
to
them
so
that
I
can
get
to
know
their
opinions,
but
thank
you
for
your
input,
I
guess.
Well,
we
can
now
move
to
the
next
topic
that
it's
python3.6.
A
So,
as
you
know,
we
defined
a
policy
that
is
this
once
that
python
version
reaches
its
end
of
life.
We
will
wait
six
months
and
then
we
will
remove
support
for
that
python
version.
That's
the
situation.
306
is
in.
A
A
Yes,
yes,
so
I
I
received
a
message
from
from
olivier
who
has
some
concerns.
So
if
you
want
to.
E
E
E
So
I
was
just
wondering
if
we
could
delay
a
bit
I
I
know
I
can't
ask
you
not
to
do
not
remove
the
support
of
python
street
3.6,
but
if
you
can
be
a
bit
later.
A
Okay,
yeah.
E
A
I
am
the
one
pushing
for
the
removal
of
306..
It's
not
my
intention
to
cost
anyone
inconveniences.
Of
course
my
intention
is
just
to
have
one
less
thing
to
test
and
support
and,
of
course,
to
be
able
to
use
language
features
that
are
introduced
in
307.
A
I
am
for
for
this
particular
case.
I
think
it's
metrics
what
interests
you
right,
that
you
want
to
have
a
3.6
open
parliamentary
python
version
that
includes
metrics.
That's
the
situation
you're
in
a
stable
metrics!
Yes,
okay!
Well,
if
that's
the
case
me
personally,
I'm
okay
with
not
removing
support
for
three
or
six
until
we
have
a
matrix,
stable
release.
A
What
do
you
think
about
that?
Will
that
work
for
you?
For
me
it
would
be
great
all
right,
aaron
or
other
folks
here.
Do
you
have
any
opinions
on
this.
C
Yeah
I
mean,
if
folks
are
still
using
3.6.
I
definitely
think
we
should.
We
should
continue
to
support
it
at,
like
the
you
know,
syntax
level
stuff
like
that.
I
don't
think
we're
in
like
a
terrible
place
with
our
ci
usage.
So
you
know
obviously,
as
more
more
releases
come.
This
sort
of
same
thing
is
going
to
happen.
I
feel
like
3.6
is
sort
of
like
the
2.7
that
we
were
dealing
with.
C
You
know
a
year
or
two
ago,
so
I
feel
like
it
is
going
to
be
around
around
for
a
while
for
a
lot
of
people.
I
I
was
going
to
say
we
had
really
previously
looked
at
like
the
pi
pi
stats,
which
would
show
the
downloads
broken
down
by
language
version
as
well.
A
Yeah
I
took
a
look
at
those
stats
and,
if
I
remember
correctly,
306
wasn't
that
big.
A
When
compared
to
other
versions,
but
for
the
time
being,.
A
I
I'm
also
not
into
too
much
pressure
to
remove
this
yeah.
It's
not
that
bad.
So
I
think
we
can
leave
this
until
we
have
a
stable
metrics
release
and
then
we
can
maybe
discuss
this
topic
again.
C
Yeah,
can
we
just
document
this
discussion.
C
A
Maybe
sure
I'll
update
the
the
issues
that
I
have
through
move
three
or
six
to
include
this
discussion.
B
Yeah
just
a
question:
sorry,
you
know.
C
B
Yeah,
so
I
have
a
question
I
mean
so
is
there
any
reason
why
we
put
the
policy
of
six
months
before
we
remove
the
support
for
the
roots?
I
mean
any
unsupported
version,
no.
A
The
period
of
six
months
was
something
that
we
just
agreed
with.
We
needed
a
a
policy,
because
I
mean
these
things
happen
right.
New
versions
show
up
and
we
cannot
support
the
reversion.
A
B
Right
so
I
was
just
thinking
I
mean.
Maybe
six
months
looks
like
a
little
in
a
short
time
period.
So
can
we
increase
it
from
six
months
to
one
year?
So
by
the
time
most
of
the
people
will
be
moving
to
the
next
python
version,
the
it's
a
it's
not
guaranteed,
but
the
probability
is
high.
B
You
know
people
moving
from
the
to
the
next
version,
because
so
so
at
that
time
you
it
will
be
easy
for
us
to.
You
know,
remove
support
for
the
3.6
live
versions
just.
A
That's
that's
definitely
a
possibility.
Let's,
let's
do
this
when
we
have
the
errors,
symbol,
metrics
release,
we
can
discuss
this
again
and
if
you
want,
you
can
add
that
as
comment
in
the
issue
for
removal
of
three
or
six
so
that
that
idea
gets
tracked
somewhere,
I
don't
want
to
make
that
decision
now.
A
In
fact,
I
can't,
of
course,
because
your
two
maintainers
are
not
right
now
in
school,
but
but
but
yes,
please
add
that,
as
let's
comment
in
the
issue
that
proxy
removal
of
306.
B
Yeah
and
when
we
are
planning
to
release
the
stabilities
for
metrics
and
do
you
have
any
date.
A
Well,
we
are,
we
were
supposed
to
have
a
rc2
this
week
and
I
hope
that
we
don't
have
an
another
release
candidate.
That
means
that,
after
one
month
from
now,
we
I
hope
that
we
have
a
stable
release.
That's
that's
what
I
would
like
to
happen.
A
A
All
right,
okay,
great,
I
think
we
can
move
to
the
next
issue.
It's
a
material
time
off
of
this
is
not
a
great
meaning
to
discuss
this
since
the
other
two
maintenance,
but
not
here,
but
I
wanted
to
discuss
with
the
with
leyden
and
frequent.
A
If
they
plan
to
take
any
time
off
in
the
soon
or
in
the
next
few
weeks
or
I,
this
is
a
time
that
some
people
use
to
take
some
time
off
so
I'll
ask
them
I'm
flying,
but
I
don't
know
if
there
are
any
approvers,
maybe
aaron.
A
Do
you
intend
to
take
any
time
off?
Oh
yeah,.
C
I'm
gonna
be
gone,
I'm
gonna
be
gone
from
the
week
of
july,
4th
and
I'll
be
back
the
week
of
july,
25th
so
I'll
be
out
for
about
three
weeks.
Okay,
pretty
much.
A
During
the
the
whole
month
of
july,
more
or
less
yeah,
okay,
yeah
I'll
also
be
out
of
office
during
the
from
july,
the
11th
until
july,
the
20th,
which
is
a
week
and
a
half
so
yeah,
all
right,
I'll
I'll,
discuss
this
with
laden
or
spricken
just
to
no,
because
it's
an
important
for
us
for
metrics
freeze
that
we
know
many
people
can
prove
right.
A
All
right:
well,
if
that's
the
case,
I
guess
we
can
move
on
30
minutes
back.
Thank
you
for
joining
and
we
will
see
you
next
week.