►
From YouTube: 2022-07-11 meeting
Description
Open Telemetry Meeting 1's Personal Meeting Room
B
B
B
I
see
someone's
trying
to
connect
to
the
audio.
I
wonder
if
just
give
up,
is
there
anything
top
of
mind
on
like
the
the
repo
for
you
right
now?
I
was
trying
to
get
a
better
sense
of
like
the
documentation
story
and
then
also
when
I
was
at
the
community
day.
I
had
a
couple
people
like
reach
out
to
me
about
like
how
to
get
started
by
contributing,
but
I
wasn't
really
sure
like
where
to
point
them
or
if
we
had
a
list
of
things.
B
B
C
A
And
then
I
saw
that
there
was
a
couple
of
files
that
there
was
a
discussion
with
michael
yep
and
he
he
pointed
some
some
files
to
you
and
you
fix
it
like
removing
the
actually
adding
a
blank
line
at
the
end
of
the
file
and
then
removing
some
protofiles,
and
that
was
okay.
That
was
done
and
then
in
your
last
commit
those
files
came
back.
C
So
that's
where
I
get
lost,
because
I'm
looking
at
the
the
changes
on
github
right
now
and
actually
I
actually
see
that
they're
gone
and
when
I
look
at
my
local
copy,
I
also
don't
have
them
so
I'm
not
sure
what
view
you're
seeing
that
these
files
are
still
there.
Okay,
that's
yeah
the
demo,
proto
and
then
health
service
yep
got
rid
of
those
blank
line
at
the
end
of
the
file.
Let
me
double
check
on
my
local
copy.
I'm
pretty
sure
those
are
done
as
well.
C
B
D
D
So
probably,
I
think,
instead
of
blocking
that
pr,
I
think
we
should.
We
can
go
ahead
with
by
merging
it
and,
let's,
let's
decide,
let's
continue
discussion
for,
and
I
think
once
once
it's
decided,
we
can
always
create
a
script
to
replace
the
license
across
all
these
services.
In
the
complete
code
base,
I
mean
either
one
we
have
decided.
C
A
A
Tommy
in
one
of
the
comments-
because
I
wasn't-
I
wasn't
able
to
see
the
event
in
one
of
the
well.
I
think
we
have.
We
are
sending
two
events
right,
that's
right,
yeah
and
we
are
able
to
see
nieger
only
one.
I
don't
know
why
the
other
one
is
not
showing
up.
Even
though
you
follow
the
same,
exactly
same
approach
that
we
have
in
the
in
the
rust
docs.
A
B
A
A
A
I
saw
that
he's
working
on
some
tests
and
I
think
that's
great,
because
we
had
some
breaking
changes
in
in
the
past,
but
the
the
test
that
he's
doing
is
like
won
by
service
by
service,
and
if
we
could
try
to
think
well,
I
had
I
actually
have
no
better
idea.
So
as
I
I
just
would
like
to
discuss
with
everyone.
If
someone
had
any
ideas
on
how
we
could
test
multiple
services,
because
then
in
that
way
we
also
ensure
complex
propagation,
because.
A
B
Yeah
yeah,
I
see
what
you're
saying
we
haven't
really
used
the
github
discussions
feature
at
all,
but
it
sounds
like
it
could
either
be
a
good
first
use
case
or
we
could
just
start
a
slack
thread
around
it.
I'm
not
sure
which
one
you
think
would
get
more
tr
more
traction,
but
yeah.
It
seems
it
seems
reasonable
to
have
a
bit
more
of
a
discussion
on
it.
B
I
think,
michael
to
his
credit,
has
a
bias
to
action,
so
just
jumps
in
a
little
bit,
but
I'm
sure
I'm
sure
we
can
redirect
that
no
problem
but
yeah.
I
agree
like
a
more
holistic
test
would
be,
I
think,
more
desirable,
especially
because
just
because
one
service
is
working
doesn't
mean
all
of
them
are
necessarily
together
or
something
like
that.
A
E
B
A
C
Garrison
yeah
I
wanted
to
you,
know
first
appreciated
the
vote
of
confidence
that
you
took
somebody
who
hasn't
contributed
to
the
project
and
trusted
them
with
such
a
major
refactor,
and
also
just
wanted
to.
Thank
you
for
all
the
really
helpful,
like
input
that
you
guys
have
been
able
to
give
me,
because
it's
took
something
that
was
big
and
complicated
and
a
very
particular
problem
with
it
made
it
a
lot
easier
to
debug.
C
C
It's
kind
of
like
all
the
way
at
the
end
downstream,
and
I
think
that
there's
a
possibility
that
there
could
at
least
be
something
with
the
quote
service
for
the
quote
function.
Is
it
doesn't
check
the
product
catalog
for
the
price
of
any
of
those
items?
When
I
saw
it
and
go,
it
was
written
that
just
every
item
was
priced
at
8.99
and
I
did
notice
that
the
product
catalog
does
include
pricing.
So
it
might
be
a
improvement
for
us
to
also
be
able
to
reach
out
to
the
product
catalog
service.
C
A
B
B
F
F
F
A
little
bit
I
actually
recently
updated
the
swift
because
of
the
changes
in
metrics
back
so
the
protobufs
and
so
on
so
yeah
I
mean
I
do
have
some
familiarity
with
the
metric
spec
and
the
way
to
use.
I
mean
the
recent
histogram
changes,
and
so
on
that
I'm
kind
of
looked
at
from
a
few
language
agents
or
sdks
so
yeah.
I
think
I
would
definitely
want
to
help
in
the
golang
side
of
things,
because
I'm
also
using
it
currently
and
and
yeah
anything
on
the
client
side
as
well.
A
A
F
F
A
B
E
B
Yeah
so
the
main
things
we're
working
on
right
now
so,
like
julianna
mentioned,
we
need
a
lot
of
help
on
metric
kind
of
just
getting
that
area
more
mature,
but
we
also
need
help
on
fleshing
out
like
the
tracing
side.
So
all
the
different
services
have
like
a
list
of
like
requirements
essentially
for
what
values
they
should
be
producing
for
our
v1
kind
of
like
release,
so
to
speak.
B
So
if
you
wanted
to
pick
up
some
of
those
tracing
items,
that
would
be
super
helpful.
They're,
not
you
know
really
heavy
weight
or
anything
like
that.
Like
add
manual
instrumentation
and,
like
you
know,
custom
tags
or
something
like
that,
I'm
on
top
of
those
and
just
kind
of
getting
those
out
to
all
the
various
different
services.
That
would
be
really
helpful
and
then,
of
course,
our
our
documentation
could
always
use
help.
I'm
not
sure
if
that's
as
you
know,
motivating
as
some
of
the
other
stuff
necessarily.