►
From YouTube: 2022-07-14 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
B
C
C
B
B
B
C
I
can
start
and
sorry
I
don't
have
my
camera
on
because
I'm
eating
lunch
yeah.
My
name
is
adriana.
I'm
a
developer
advocate
at
lightstep,
so
I
joined
lightstep
just
before
I
joined
this
group.
So
I
recently
I
I
helped
to
give
the
docs
a
bit
of
a
facelift,
so
I'm
super
stoked
that
that's
happening
and
I'm
I'm
hoping
to
be
able
to
dig
into
that
a
little
bit
more,
I'm
newish
to
open
telemetry.
C
B
C
Way
to
go,
thou
shalt,
do
it
so
yeah,
I'm
I'm
actually
super
excited
to
be
participating
and
contributing
in
whichever
way
I
can.
B
Yeah,
that's
so
cool
go
ahead,
race.
A
Oh,
I
didn't
mean
to
cut
you
off.
Oh
these
things
are
always
so
weird
yeah.
My
name
is
rhys.
I
am
a
developer
relations
engineer
with
new
relic,
I'm
I
still
say
I'm
like
new
to
open
telemetry.
I
joined
our
open
source
community
team
back
in
november
and
yeah
it
just.
It
has
felt
like
a
whirlwind
trying
to
get
my
open,
telemetry
legs
as
as,
to
use
a
c
analogy,
I
suppose,
but
yeah
it's
pretty
fun.
A
I
I
really
want
to
contribute
to
documentation,
which
is
why
I
attend
these
and
yeah.
I
just
need
to
pick
like
something
to
to
work
on.
I
keep
getting
pulled
away
by
other
projects
related
to
open,
telemetry.
B
Okay,
so
I'm
libby-
this
is
my
first
time
joining
this
meeting
or
any
hotel
meeting
other
than
open
telemetry
day
at
the
open
source
summit
last
month,
I'm
very
new
to
open
telemetry
itself,
although
I've
heard
about
it
and
been
interested
in
it
for
quite
a
while
in
in
my
work
in
open
source
and
deveral,
I
work
at
humeo,
building,
devrel
and
community
and
hotel
is
a
big
topic
for
us.
So
this
way
it's
kind
of
nice.
B
I
get
to
spend
some
of
my
work
time
on
hotel.
Not
just
have
to
do
it
in
my
free
time.
C
B
So
I
was
thinking
east
coast
when
you
said
you
were
eating
your
lunch
because
I
mean
and
it's
10
in
the
morning
and
I'm
just
eating
my
breakfast.
I
don't
know
if
that
says
more
about
it.
B
I
I
guess
you
know,
I
should
probably
read
the
meeting
notes
and
you
know
I
I
see
a
lot
of
reference
to.
Oh,
oh,
look
at
the
issue
and
I've
been
still
trying
to
navigate
through
the
github,
org
and
figure
out
which
repos
to
look
at
so
maybe
a
pointer
to
the
issues.
So
just
so,
I
can
get
a
sense
of
what
what
the
current
focus
is.
What
else
is
of
interest?
C
I
think
like
I,
I
can
speak
a
little
bit
to
that
in
terms
of
the
documentation
side
of
things.
So,
if
you
want
to
look
at
where
the
docs
are
located,
it's
in
the
repo
called
open
telemetry.io.
I
believe-
and
I
know,
there's
like
a
whole
set
of
instructions.
C
Yeah
yeah,
so
no
I
mean
so
in
github.
There
is
a
repo
called
opentelemetry.io
which
points
which
is
basically
the
content
for
the
actual
open,
telemetry
website.
A
C
And
then
I
would
say
I
think
one
of
the
big
undertakings
for
open
telemetry
is
like
docs
wise
is
basically
making
open,
telemetry.io
the
source
of
truth
for
documentation
around
open
telemetry,
because
there
was
like.
I
think
there
was
just
some
discussion
well
back
on
how
each
vendor
has
their
own
like
getting
started
with
open
telemetry.
C
Just
fine
like
in
terms
of
like
okay
connect
to
my
tool
using
open
tool
and
telemetry.
But
then
let's
try
to
duplicate
the
docs
so
that
all
of
the
full-fledged
examples
on
how
to
use
open
telemetry
are
in
the
dark
site
or
in
their
respective
repos.
That
sort
of
thing,
rather
than
like
everyone
having
like
their
own
definition
and
that
of
open
telemetry
and
of
like
the
different
terms
around
right,
telemetry.
C
The
goal
is
to
like
unify
open.
Telemetry.Io
is
the
source
of
truth
and
then
like
I,
I
can
speak
on
the
lightstep
docs
like
we're,
trying
to
point
everyone
to
the
open,
telemetry,
docs
and
anything
that's
slight
step.
Specific.
Then
we'll
show
you
how
to
connect
specifically
to
light
step
if
you're
using
open
telemetry,
but
otherwise,
like
the
core
concepts
we
want.
We
want
that
to
reside
in
in
the
actual
hotel
site.
B
And
does
that
include
the
website
as
a
whole,
because
the
site
has
that
the
way
I
thought
about
it
is
there's
the
site
has
how
to
get
involved
with
the
community
blogs.
It
has
the
documentation
and
it
has
sort
of
here's
how
to
find
more
technical,
here's
how
to
find
source-
and
you
know,
sort
of
a
hub,
github
and
and
slack
and
so
on.
B
So,
what's
that
trying
to
say
when
we
say
the
site,
are
we
talking
about
the
site
as
a
whole
or
we're
focused
on
the
documentation
specifically.
C
B
Not
not
that
I
necessarily
do
I'm
just
exploring.
B
A
B
B
B
C
So
like
I,
these
who
I
worked
on,
which
I
think
they
closed,
because
it
was
like
a
huge
umbrella
issue.
I
just
I
just
referenced
it
in
my
commits,
but
yeah.
I
don't.
I
think,
just
let
people
know
maybe
in
the
in
in
the
slack.
B
B
B
A
C
A
Oh
shoot
yeah,
it
was
the
first
one
it's
been
like
over
a
month
in
the
making
to
like.
Oh
was
it
last
week.
It
was
just
like
nine
o'clock
earlier,
oh
no
yeah.
I
posted
some
announcements
in
the
main,
open,
telemetry
channel
and
cncf
slack,
okay
yeah.
We
were
trying
to
figure
out
like
what's
the
best
way
to
reach
people,
because
I
know
there's
a
lot
of
interest
in
it,
but
we
figured
well
maybe
just
the
main,
open,
telemetry
channel.
A
Yes,
it's
set
to
a
monthly
cadence
at
the
moment,
so
the
next
one
will
probably
be
mid
next
month.
I
think
okay
and
yeah
it'll
be
it.
I
don't
know
if
it's
set
for
the
next
month
on
the
calendar
yeah.
Let
me
see.
B
A
Oh,
of
course,
yeah
I
think
for
the
first
meeting.
It
went
really
well.
I
had
a
number
of
end
users
and
people
shared
their
topics
and
it's
a
lean
coffee
format.
So
it's
like
democratically
generated
topics,
so
people
put
in
what
they
want
to
talk
about,
and
then
you
can
vote
up
to.
A
I
think
two
or
three
votes,
depending
on
how
many
people
are
there
and
then
each
topic
gets
six
minutes
and
then,
at
the
end
of
six
minutes,
people
can
vote
on
whether
they
want
to
continue
talking
about
it
or
talk
about
the
next
topic
and
yeah.
I
think
there
was
some
good
stuff
discussed
and,
of
course
the
hope
is.
You
know
we
get
more
experienced
end
users
to
participate.
B
A
A
A
And
also
around
open
telemetry
in
ci,
cd
pipelines
and
philip
actually
asked
about
documentation
gaps
and
which
gaps
to
fill.
A
I
did
take
some
notes
on
the
documentation,
one
which
I'm
just
now
realizing.
I
could
have
probably
shared
sooner.
I
kind
of
need
to
gather
my
my
notes
into
a
more
cohesive.
B
A
A
That
was
an
interesting
one.
That
did
another
comment
was
on
how
there's
a
lot
of
focus
on
greenfield
practices,
but
not
only.
A
Topics
and
yeah
there's
some
other
notes.
I
kind
of
need
to
decipher
what
I
was
writing.
B
We
feel
that
maybe
cultural
background
I'm
from
australia,
but
I
I'd
always
understood
greenfield
to
be
like
you
know,
a
clean
slate
deployment
rather
than
you're
trying
to
integrate
with
something
that's
already
there,
but
from
what
you
were
saying.
Reese
it
sounded
like
greenfield
needs
something
different
like
more
more
new
user
sort
of
primary
level
content,
rather
than
advanced
level
content.
A
B
Yeah
that
came
up
at
hotel
day,
like
that
was
one
of
the
big
takeaways.
I
had
that.
Having
a
you
know,
a
write-up
or
a
real
working
example,
a
reference
architecture
that
that
would
be
really
helpful
for
a
lot
of
people.
A
lot
of
people
were
asking
for
it
and
there
was
a
talk
given
by
someone
from
nginx
full
disclosure.
I
used
to
run
that
team
at
nginx
on
a
they
built,
a
modern
apps
reference
architecture
and
they
used
open
telemetry
for
the,
for.
B
I
guess
observability
is
as
good
a
word
as
any.
That
was
useful,
but
that's
an
example
rather
than
a
sort
of
use
case
of
here's,
what
we
did
in
production,
but
that
got
a
lot
of
interest
too.
B
So
I
can
see
that
there's
you
know
one
thing
that
would
help
new
users,
and
I
think,
probably
help
with
you
know,
supplement
the
documentation
too,
is
having
some
sort
of
reference
architecture
like
what
is
it
that
micro,
google
has
its
bank
of
anthos
sort
of
example,
which
you
can
sort
of
it
allows
you
to
whatever
the
technology.
B
B
Way
way
too
many
taps
there.
We
are.
B
B
Yeah,
like
it
looks
like
a
dog,
it
gets
sort
of
similar
to
a
fox
dog,
wild
dog.
A
A
A
A
B
A
B
Yeah
when
I
was
on
back
in
australia,
I
was
on
the
east
coast.
So
no
wasn't
in
a
lot
of
time
zones,
but
you
know
as
soon
as
it
got
close
to
like
five
hours.
Five
time
zones
passed.
Asia
was
online
and
it
was
like
that
half.
A
Oh
and
actually
let
me
share
this
blog
post
with
you
both
as
well.
It
has
info
about
the
end
user
discussion
group.
B
A
And
there's
a
private
slack
channel
for
end
users
as
well.
B
I
pinged
shar,
when
I
saw
them
actually
one
of
my
colleagues
saw
the
post
was
it
last
week.
I
just
got
back
from
being
out
with
covert
and
oh
crazy
yeah.
It's.