►
From YouTube: 2021-02-04 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).
C
Yes,
so
instead
you
get
to
watch
me
stumble
with
finding
my
screen
share
and
all
the.
C
C
A
C
D
C
No
problem,
as
long
as
as
long
as
you
wanna,
you
know,
hit
the
release
button
and
write
the
release
notes.
Then
it's
all
good.
E
Yeah,
I
think
so
I'll
probably
do
it
either
very
soon
or
tomorrow
morning.
C
E
C
The
the
approver
approver's
group
has
write
permission
to
the
repo
which
allows
like
merging
and
all
the
good
stuff.
B
B
We
want
to
release
o16
very
quickly
to
give
it
a
little
bit
more
time
to
bake
as
an
rc
before
doing
a
1.0,
so
hopefully
tomorrow
I
suppose
it
possibly
could
leak
into
saturday.
But
I
think
our
plan
is
for
tomorrow.
B
So
I
think
we're
targeting
the
15th
as
one
1.0,
so
that
would
give
us
a
week,
but
we'll
see
how
it
goes,
and
I
will
reiterate,
as
I've
been
telling
everyone
this
is
your
last
chance
for
comments
before
we
are
rc2
is
basically
going
to
be.
If
you
want
to
do
anything,
any
changes,
it's
the
answer
will
be
no
unless
you've
got
some
incredibly
compelling
reason.
B
If
you
take
a
look
at
the
change
log,
I've
kept
the
change
log
up
to
date,
so
you
can
see
the
and
all
the
breaking
changes
that
have
been
merged
so
far.
I
think
I'm
maybe
one
pr
behind,
but
pretty
much
is
already
there
in
the
change
log
ready
to.
B
C
B
I
mean
the
big,
the
big
things
that
will
probably
in
well
there's
those
things
yeah
aside
from
those
those
weren't
our
choice,
that
was
the
spec,
but
the
the
two
big
things.
I
think
that
will
impact
most
users
with
that
one,
the
change
of
trace,
config
to
span
limits
and
moving
and
repackaging
it
and
the
bigger
one
on
the
api
is
the
taking
of
the
span.kind
inner
enum
and
making
it
top
levels.
Mankind.
Everything
else
is
pretty
minor
that
shouldn't
really
impact.
Hardly
anybody
at
all.
D
B
I
was
trying
to
figure
out
some
way
to
in
to
write
this
better,
so
that
j,
what
jason
just
did
isn't
what
happens?
I
was
thinking
about
maybe
putting
strike
through
on
the
the
old
ones.
I
don't
know
whether
that
would
help
or
not.
F
D
B
B
B
D
C
I
think
trace
is
more
concise.
It's
it's
like
20,
more
concise.
C
C
I
think
the
the
reasoning
I
think
it
boils
down
to
the
reasoning
was
that
we
called
the
signal
traces
and
like
that.
That
term
is
used
in
the
spec
in
various
places,
and
we
call
the
signal
metrics.
F
I
find
it
kind
of
ironic
that
you
know
open
telemetry
and
open
tracing
both
have
this
notion
of
of
traces
as
a
term,
but
they
don't
actually
have
literal
traces,
they're,
they're,
just
a
collection
of
spans.
C
D
B
Anyway,
it
was,
it
was
heavily
litigated
already
and
we
lost.
B
I
think
that's
still
on
the
table,
but
I
think
also
the
introduction
of
github
discussions
has
made
that
a
little
less
a
little
less
painful.
Although
people
still
come
together
and
ask
questions
and
I
have
to
continually
play
traffic
and
redirect
them
over
to
discussions.
Yup.
C
Yeah,
thank
you
john,
for
you
know
it's
actually
just
leave
it
totally
abandon
it.
Without
I
was
thinking
of
I
mean
I
could
post
like
like
a
big
banner
there
every
week
that
redirect
that
tells
people
to
go,
I
can
delete
it,
but.
D
F
B
Yeah,
I
don't
know,
I
think,
trust
your
idea
of
like
posting
a
banner
for
a
couple
weeks,
like
maybe
daily,
just
like
hey.
This
is
not
the
place
to
go
hey.
This
is
not
the
place
to
go.
Yeah
before
deleting
might
be
might
be
friendly
and
then
the
archive.
I
like
the
idea
of
the
archive,
if
that's
even
possible,
to
get
her.
C
I've
looked
for
such
a
thing
and
haven't
found
any
way
to
archive
or
banner,
of
course,
not
because
it's.
G
A
C
C
Agreed
but
yeah
I've
been
happy
with
the
github
discussions.
The
threading
is
a
little
weird,
but
as
a
source
as
a
you
know,
it
shows
up
in
my
notifications
all
in
the
same
place.
It's
easy.
It
works
in
sort
of
my
work
workflow
and
it's
gonna,
be
you
know
more
persistent
and
searchable,
which
is
great
that
it
was
impossible
to
find
like
a
prior
discussion
in
getter
and
sort
of
link
people
to
it.
C
We
did
have
one
question
from
the
google
folks
about
the
hotel
exporter
jar
and
I
recommended
the
the
custom
distro
approach,
because
I
took
a
look
across
everybody's
repost
that
I'm
aware
of,
and
it
looks
like
everybody
is
using
the
custom
distro
stuff
that
nikita
so
excellently
documented
and
created
this
nice
example.
A
C
I
caught
that
on
the
maintainers
meeting.
He
was
talking
about
he's.
He
and
his
team
are
responsible
for
the
the
scala
version
encoded
in
the
artifact
name,
stuff.
A
C
C
G
C
Anything
else
on
people's
minds,
jason,
how's
keller.
I
was
curious
as
I
was
thinking
about
looking
at
people's
vendor
distributions
how's
the
new
relic
stuff
going
from
the
open,
telemetry
java
agent.
Do
you
know
if
you
have
people
using
it?
H
Yeah,
it's
a
good
question.
I
don't
I
don't
have
much
data
around
like
numbers
of
people
using
it.
We
haven't
gotten
too
many
issues
filed
or
anything
like
that.
It's
as
far
as
on
our
end,
it's
been
going
pretty
smoothly.
Once
we
got
the
initial
distro
project
set
up,
it's
been
really
easy
to
maintain
the
bulk
of
the
work.
There
is
just
keeping
up
with
the
sdk
api
releases
and
trying
to
trying
to
make
sense
of
the
breaking
changes
there
to
keep
our
exporter
up
to
date.
H
So
we
can
keep
our
distro
releases
up
to
date,
but
but
yeah,
it's
not
entirely
clear
to
me
how
many
people
are
jumping
on
these
releases
that
are
changing
pretty
quickly.
I
think,
once
once
we
hit
the
1.0
release,
I
expect
a
lot
more
uptake
there,
but
it's
pretty
easy
to
maintain
on
our
side
of
things.
C
Cool
awesome,
yeah
yeah,
one
zero
is
going
to
be
really
amazing
for
this
project,
because
we
have,
we
have
been
churning
so
yeah
good,
good
work,
keeping
up
with
the
all
the
changes
yeah.
It's
definitely
it's
definitely
a
task
but
yeah,
and
I
don't
remember
if
you
were
on
last
week.
C
Our
plan
for
the
java
agent
is
to
release
a
one
zero
shortly
sometime
shortly
after
the
sp
api
one
zero,
but
we
are
not
going
to
guarantee
we're
not
going
to
release
all
of
our
basically
apis
and
java
agent.
Apis
and
spis
will
be
still
marked
alpha,
so
we're
not
really
going
to
guarantee
any
stability.
C
It's
just
going
api
level,
stability
or
even
telemetry
level
stability.
At
this
point,
the
open,
telemetry
spec
discussion
seems
to
be
going
in
that
direction
of
punting.
The
open
telemetry
data
stability
for
one
to
some
point
beyond
one
zero.
H
C
And
sergey
how's
how's
everything
going
at
lightstep.
G
Yeah
last
step:
actually
it's
it's
in
beta,
so
we
say
that
it's
in
beta
and
I
think
we
don't.
We
don't
actually
have
any
issues
or
any
customer
feedback
yet
yeah.
Maybe
people
just
afraid
to
use
it
until.
D
F
D
C
Yeah,
so
just
quick
recap:
if
anybody
doesn't
know
open
telemetry
is
calling
ga
is
going
to
be
a
they're
calling
a
marketing
term
which
will
only
get
applied
when
open
telemetry,
essentially
when
open
telemetry
can,
when
they
can
deprecate
open
census
and
open
tracing
and
so
technically
with
with
tracing
1.0,
you
could
deprecate
open
tracing
because
open
tracing
didn't
have
metrics,
but
open
census
did
does
have
metrics.
F
C
C
B
My
guess
is
that
ga
will
mean
more
specifically
full
replaceability,
with
both
open
census
and
open
tracing,
which
will
imply
metrics
but
also
implies
some
other
things
about
the
open
census.
Compatibility.
C
C
Well,
did
anybody
have
any
other
topics
they
wanted
to
raise
today.
H
B
C
Okay,
cool
yeah,
my
meaningless,
mean
totally
meaningless
guesses.
You
know
end
of
the
year,
like
would
be.
C
C
All
right
well
definitely
want
to
give
people
time
back
here,
always
good
to
see
everybody
and
see
you
in
github.