►
From YouTube: 2021-01-28 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).
A
Hey
austin,
hello,
is
it
cool
I
I
bounced
in
last
time
and
you
you
probably
know
why
I'm
starting
to
pay
attention
to
the
com
sig,
but
is
it
okay
that
I'm
kind
of
just
hanging
out.
B
Yeah
free
country,
okay,
I
don't
know
if
we're
gonna
have
it.
I
will
see
who
shows
up.
B
C
C
B
Speck
and
I
guess
so,
I
think
the
so
here's
my
understanding
for
where
the
release
stuff
stands.
The
spec
there
are
parts
of
the
spec
that
are
one
like
tracing
in
a
spec
is
frozen,
so
each
language
like,
I
think
the
first
two
are
going
to
be
java.net.
B
B
B
Okay
sure
and
then
what'll
happen.
I
imagine
is
not.
Everything
is
not.
Everything
is
going
to
have
1.0
docs
at
that
point,
but
we
would
be
able
to
at
least
say
like
you
know,
this
is
where
they
need
to
get
to
and
then,
if
you
know,
spec
1.1
comes
out
or
something,
then
we
can
version
it
again
and
say
like
okay,
here's
the
drop
down
between
1.0
and
1.1.
B
A
page
explaining
that
other
than
that,
though,.
D
D
You
know
on
this
the
kind
of
the
1.0
tracing
stuff-
it's
I
was
looking
at
the
median
engine.
It
looked
like.
Maybe
you
talked
about
it
a
little
bit
in
the
last
meeting,
but
I
was
wondering
if
there's
going
to
be
any
sort
of
you
know
broader
announcement
from
open,
telemetry
kind
of
the
community
around
this,
the
1.0,
obviously
not
the
ga
stuff,
because
that's
you
know
a
different
thing
and
going
to
be
at
a
later
later
time
frame.
D
But
I
know
like
net
that's
kind
of
more
where
I'm
involved
and
there
you
know
they
have
their
post,
that
they're
drafting
for
to
put
on
medium
and
they're
they're.
Basically,
you
know
waiting
for
this.
The
the
issues
you
highlighted
basically
they're
waiting
for
that
to
just
go
ahead
and
to
stamp
out
their
1.0
version.
A
D
Planning
on
releasing
that
medium
post
immediately-
and
I
was
just
wondering
if
there's
gonna
be
other
any
other
communication
beyond
you
know
beyond
the
kind
of
the
language
specific
announcements.
So
I
think
what.
B
My
thought,
at
least,
is
that
there'll
be
posts
from
the
we
twitter.
There
will
be
tweets
about
it
from
the
hotel.
Twitter
account
we'll
put
a
banner
on
the
site
that
says,
like
hey
the
you
know:
here's
the
thing
like
like
the
hotel
spec
has
reached
1.0
or
whatever,
and
then
these
languages
have.
You
know
well
like
an
announcement
of
some
sort
on
the
site
for
like
specs
1.0.
B
Here's
the
components
that
are
now
1.0
and
like
I
assume
java
will
probably
also
have
some
sort
of
blog
post,
like
the
governance
committee
of
the
technical
committee,
will
probably
write
something
when
I
talked
to
morgan
about
this
like
a
month
ago,
and
it
feels
like
the
last
might
talk
to
morgan
about
this.
Like
kind
of
the
gc
idea
was
for
1.0
like
let's
not
necessarily.
B
Do
like
a
ton
of
media
stuff
around
like
these
individual
languages
hitting
1.0?
Let's
do
more
of
like
a
bigger,
coordinated
push,
and
you
know
a
month
or
two
when
we
hit
that
ga
thing
or
that
ga
ability,
because
two
reasons
one
the
people
that
are
using
like
companies
that
are
integrating
hotel
or
otlp
are
going
to.
We
assume,
I
assume,
are
going
to
be
like
making
noise
about
it
on
their
own
as
well.
B
D
Yeah,
no
that's
I
mean
that's
that
that
is
exactly
it
that
we
like.
We
do
have
a
blog
post
that
we're
gonna,
post
kind
of
in
in
conjunction
with
with
one.net,
goes
and
gonna.
D
Do
something
similar,
I
think
for
for
java,
we're
just
trying
to
decide
if,
like
how
much
we
were
gonna
like
kind
of
combine
those
blog
posts
and
then
also
if
there
was
any
other
sort
of
you
know,
like
I
said,
like
a
kind
of
general
open,
telemetry
announcement
we
wanted
to
line
up
with,
but
it
sounds
like
probably
probably
not
just
the
more
the
site
update.
I
think
so.
B
Yeah,
just
because
a
lot
and
a
lot
of
it's
because
like
we
can't
we're
not
going
to
hold
anyone
at
the
whole
point
of
the
way
that
ga
is
like
four
things
going,
1.0
like
we
don't
necessarily
want
to
hold
anyone
any
sig
to
be
like
well
hold
on.
Can
you
time
this
release
right?
We
want
everyone
to
kind
of
like
when
the
work's
done
the
work's
done
and
ship
it.
B
You
know,
because
ga
is
much
more
of
the
marketing
the
marketing
friendly
thing
here,
where
we'll
probably
try
to
combine
that
line,
that
up
with
like
a
cncf
post,
and
maybe
even
incubation
and
stuff,
like
that
right
that
I
just
think
requires
more
work
and
prep
yeah.
D
B
Total
sense
but
yeah,
I
think,
for
1.0
because,
like
we
did
in
the
when
we
did
the
beta,
we
had
a
banner
that
was
like
hey.
These
components
are
beta,
so
we'll
probably
have
a
banner
of
like
you
know.
Hotel
spec
is
now
1.0
hotel,
tracing
and
java
and
net
is
one
point
you
know,
and
people
just
had
add
stuff
on.
B
B
Cool
a
second
thing
is,
there
was
an
issue
that
was
posted
recently
in
the
community
repo
about
sample
code
basic
effectively.
B
B
B
B
Contributing
those
upstream
or
creating
like
hotel,
specific
versions
of
those
that
just
use
upstream
api
and
sdk
don't
use
like
a
distro
or
anything
and
have
those
be.
You
know.
B
A
Well,
I'm
looking
at
that
issue,
and
I
don't
know
if
I'm
reading
into
it
or
not,
but
you
know,
the
effective
thing
is
something
something
something
a
place
to
to
get
how
to
use
and
observe
the
enhancement
effect
right.
So
it's
to
me
this
max
of
like.
Are
there
tutorials
and
like
aside
from
just
probably
the
smattering
of
all
the
stuff?
That's
already
existed
existing
content
out
there.
A
I
think
there
might
I'm
sure
there
are
some
gaps
in
there
and
then,
when
it
comes
to
version
specifics
there
I'm
sure
there
will
be
some
gaps
and
as
we
go
along
those
just
kind
of
expand
until
we
fill
them.
But
the
meaningful
thing
that
I
get
out
of
this
is
help
people
understand
how
to
use
hotel
right
because
the
official
instrument-
and
I
I've
been
evangelizing
the
crap
out
of
hotel
in
my
fortune,
250
base
just
as
an
independent
person
working
at
another
job
somewhere.
D
A
B
A
B
This
goes
with
documentation.
This
is
a
second
order,
sort
of
effect
over
the
documentation
we
have.
I
would
say,
because,
right
now
we
have
you
know,
there's
there's
basically
two
things,
there's
three
things
right
now
I
would
say
for
each
language,
you've
got
you
know,
kind
of
the
quick
start.
Hello
world
you've
got
these
slightly
more
advanced
like
here's,
how
things
work,
or
you
have
like
something
more
advanced
than
that.
You
have
like
example,
code
in
each
repo.
A
B
Are
arguably
the
most
useful
documentation
because
they
actually
show
you
like
how
things
work,
but
nothing
explains
the.
Why
very?
Well
I've
been
doing
this
with
like
hotel
metrics
for
the
past
couple
weeks
of
trying
to
come
up
with
like
translation
guides,
where
it's
like
hey.
If
you
use
prometheus,
here's
hotel
metrics,
you
know
stuff
like
that,
is
really
hard,
because
hotel
metrics
doesn't
necessarily
map
cleanly,
or
at
least
it's
certainly
not
it.
B
Okay,
a
better
way
to
say
this
from
an
end
user
point
of
view
from
like,
like
a
guy,
I
just
want
to
go
write
some
instrumentation.
The
tracing
is
mostly
fine
if
a
bit
wordy
in
terms
of
initialization
but
the
metrics
api
blows,
it's
really
hard
to
use.
It's
extremely
verbose.
B
A
B
Would
this
okay?
If
we
can
scope
it
down
some,
then
I
think
it
would
be
great.
I
again,
I
would
simply
say,
like
I
think
it
would
be
valuable
if
we
as
because
I
know
like
lightstep,
has
we
have
a.
Let
me
link
it
actually,
because
we
have
a
pretty
sure
this
is
make
sure
this
is
a
public
repo
yeah
like
I
am
not
a
huge
fan
of
this,
but
you
can
look
at
it.
B
Guide
or
it's
very
thorough
in
terms
of
like
what
this
does,
is
it
takes
you
through?
You
know
here
for
every
length
or
for
all
these
different
languages.
Here's
like
creating
a
span
sending
it
using.
You
know
open
tracing,
shim
straight
up
and
telemetry
ardistro,
and
you
know
using
it
with
things
like.
B
Can't
words
good
today
using
it
with
things
like
the
instrumentation
plug-ins
right,
like
the
the
javascript
one,
has
you
know
the
express
library,
the
so
one
example,
one
idea
could
be
like
a
short-term
thing
could
be
like
what
if
there
was
a
link
for
all
of
these
on
the
site
somewhere
like
what,
if
we
had
a
you
know
like
for
the
resources
page,
that
would
be
a
good
way
to
collect
them.
B
B
Like
I
don't
know,
I
I
don't
have
the
answer
here.
I
just
know
what
I
like
and
I
don't
like,
and
I
don't
like
the
hipster
shops.
I
don't
like
the
like
heroes,
20
different
services,
and
they
all
happen
to
be
using
proprietary
cloud
things
like
that's
what
I
don't
terribly
care
for,
like
the
microsoft
stuff
from
the.
A
C
Yeah
I
wanted
to
chime
in
that
for
jager.
There's
a
sample
application,
that's
instrumented,
with
open
tracing
today,
yeah
hot
rod,
yeah
hot
rod,
exactly
yeah.
B
B
B
So
something
that
looks
closer
to
hot
rod
than
you
know,
eshop,
but
try
to
find
a
sweet
spot
between
those
two
things
and
have
it
be
composable
in
such
a
way
that
you
could
show
like
here's
how
this
works.
Like
the
poly.
You
know
when
I
this
is
polyglot
right
or
I
could
pretty
easily
swap
out
certain
parts
of
this.
You
know
if
I
was
doing
if
I
wanted
to
like
here's,
a
back-end
service
or
here's
an
api
server,
and
then
here's
a
go
version
of
it
in
a
java
version
of
it.
B
I
don't
think
you
have
to
start
with
that,
but
something
that
is
designed
to
be
a
little
composable
and
let
different
languages
kind
of
come
and
do
their
own
thing,
and
I
think
it
would
be
very
nice
if
this
could
be
something
that
we
kind
of
did
as
a
project
like
we
as
hotel
did,
rather
than
having
a
bunch
of
different
vendor
versions
of
it
right
right.
A
I
think
I
think
the
reference,
the
reference
app
and
architecture
as
jonah's
saying
is
definitely
a
key
component
and
boy
would
it
be
nice
if
various
tutorials
for
various
different
languages
and
swappable
or
otherwise
could
use
that
same
reference
app?
But
I
hesitate
to
like
put
that
as
like
the
key
focus
specifically
of
this
issue,
because
that's
not
exactly
what
he's
asking
but
yeah.
A
More
importantly,
I
think
it
can't
be
a
blocker
to
to
the
demand
that
already
exists
now,
as
in
indicated
in
this
thing
too,
for
this
notion
of
that
the
docs
are
insufficient
for
the
audiences
that
were
that
we're
seeing
now
right
and
they're
they're.
Looking
for
something
more,
you
know,
step
by
step
and
stuff
like
that.
This.
A
B
Like
we
need
better
docs,
we
need
a
sample
apple
code.
That
is
more,
we
need,
we
need
reference
applications
or
reference.
Architectures
one
does
not
preclude
the
other,
I'm
the
the
real
point
is
it's
like
it's
really,
and
this
is
I've
struggled
with
this
for
months,
like
it's
really
hard
to
like
convince
people
to
write
docs
for
something
that
changes
every
two
weeks
you
know
like
we
are.
We
are
simply
not
going
to
have
good
documentation
upstream
documentation
on
the
website
until
we
have
some
level
of
stability
around
the
ai.
B
A
I
I
actually
think
it
sounds
like
the
people
inside
the
product
project.
Don't
see
it,
I
mean
technically,
you
ask
them,
is
doc
important.
Then
they
would
say
yes,
but
it's
it's
kind
of
like
if
it's
not
getting
done
and
if
it's
like
always
the
backlog,
there's
a
kind
of
a
the
fundamental
problem
is
like
okay.
This
is
more
than
just
something
a
subgroup
or
a
secondary
set
of
people
can
solve.
For
you
right.
We
we
have
to
figure
out
how
to
solve
it
together.
B
I
think
a
lot
of
it
is
just
that
like
they
and
they
would
they
would.
If
you
asked
it,
if
you
asked
the
other
cigs,
they
would
say
like
that
for
the
most
part
like
it
is
kind
of
a
solved
problem,
because
you
know
their
example,
code
is
up
to
date
and
all
the
stuff
that
they
and
they're
correct,
because
that's
why
it's
all
in
a
monorepo
right
like
well,
that's
not,
I
don't
say
montreal.
That's
why
each
sig
is
kind
of
doing
everything
unto.
B
A
So
there's
two
questions
in
my
mind.
Right
one
is
at
some
point
when,
when
do
you
feel
like
we're
going
to
land
in
terms
of
this
sdk
settling
down
for
the
for
the
short
term
and
really
that's
another
question
of?
Is
this
an
ecosystem
where
it'll
ever
ever
settle
down
enough
for
some?
Why
sort
of
notion
of.
B
B
B
A
B
Something
that's
like
we're
talking
about
things
that
we
don't
have
to
like
to
solve
today,
and
I
believe,
once
we
are
on
the
other
side
of
defiant
of
actually
cutting
some
releases
it'll
get
better
quickly.
It's
just
that
it
can't
get
a
ton
better
until
that
happens,
yeah.
A
A
B
I
think
once
we
hit
that
level
of
stability
with
you
know
some
of
once
there
is
a
level
of
like
okay,
this
isn't
going
to
change
out
from
under
your
feet
every
two
weeks,
then,
I
think
we'll
encourage
more
people
to
do
documentation
and
samples,
and
things
like
that,
both
by
leaning
on
you
know,
partners
and
vendors,
but
also
just
by
promoting
it
to
the
broader
community
right-
and
you
know
well.
A
To
help
raise
this,
not
necessarily
in
the
technical
route
but
in
the
business
route,
so
I.
B
A
B
Even
more
than
it
already
is
anyway,
I
have
another
meeting
to
get
to
did
anyone
else
have
any
parting
thoughts,
and
I
would
say
if
you
have
like
ideas
in
this
poll,
probably
the
best
way,
I
think,
because
they're
probably
bigger
than
we
can
get
to
in
a
single
meeting.
B
He
either
started
a
discussion
in
the
website,
repo
or
started
an
issue
and
like,
let's
you
know,
let's
work
this
out,
I'm
painting
in
a
thread
and
get
some
more
concrete
ideas.
Does
that
sound
good
yep
all
right
thanks
so
much
for
watching.