►
From YouTube: 2019-10-10 website SIG meeting
Description
OpenTelemetry website SIG meeting
A
B
B
A
A
C
C
Project
status,
page
I,
think
I
can
make
a
PR
against
that
just
to
clean
up
the
literal
milestones
listed
there
and
I
think
poking
the
cigs.
If
you
look
at
the
actual
statuses,
they're
kind
of
like
all
over
the
map,
so
it
needs
to
maybe
be
around
of
like
coordinating
with
the
different
SIG's
who
have
posted
a
milestone.
To
actually
have
it
be
correct,
like
python
is.
B
A
C
C
C
C
A
B
A
B
C
Yeah,
a
simple
script
that
just
pulled
the
latest
release
from
each
sig
and
splatted
github
details.
There
would
be
probably
a
good
incentive
to
assembly.
The
milestones
were
to
get
people
to
you
know
how
something
to
github
releases
when
they
do
a
release,
which
might
be
a
good
practice.
I,
don't
know
if
we
have
to
maybe
bring
this
up
as
a
community
issue
first
and
like
not
just
impose
it
on
people
or
something,
but
in
the
short
term,
I
can
try
to
just
do
it
by
hand.
C
I
think
people
are
mostly
just
posting
directly
to
whatever
package
management
system
they
have
and
like
posting
something
up
on.
Github
release
is
sort
of
like
an
extraneous
step,
but
it
is
nice
for
people
coming
in
to
github.
They
can
see
that
release
tab,
so
it
is.
It
is
something
that
can
help
get
people
oriented,
but
I.
Imagine
like
no
one
actually
literally
needs
it
to
be
an
extra
step.
C
B
A
C
C
C
C
C
B
A
I
mean
I
I
see
these
as
being
more
that
kind
of
the
stuff.
That's
right
now
found
below
the
fold
in
the
getting
started
like
more
like
articles,
it
may
be
a
little
more
holistic
than
just
like
saying:
hey,
here's,
some
here's,
a
quick
start
in
the
language
or
something
it's
like:
hey,
here's
like
a
sample
application
and
here's
how
you
add,
hotel
and
deploy
it.
You
know
really
put
collector
or
stuff
like
that.
A
C
C
A
C
A
A
C
A
We
should
probably
yeah
we
apply
just
take
the
things
that
I
wrote,
the
hotel,
101
Club
and
then
yeah
put
that
onto
the
site.
C
A
A
C
B
B
C
B
B
B
C
Yeah
I
I
think
one
thing:
that's
critical
that
we
didn't
do
right
and
open
tracing,
but
I
think
will
do
right.
Here
is
as
a
user.
You
don't
really
need
to
read
this
spec
like
you
should
be
able
to
read
nice
formatted
articles
on
the
website
and
get
to
know
enough
about
open
telemetry
to
go
use
it
in.
C
We
were
kind
of
referring
people
there
a
little
too
much
for
though,
like
here's,
the
high-level
overview
of
what
this
stuff
is
and
so
I
think.
That's
why
it
was
kind
of
annoying
on
open
tracing.
So
if
we
just
don't
do
that,
if
we
just
have
enough
other
documentation
that
the
spec
is
really
just
for
the
sig
maintainer
is
to
be
looking
at
and
coordinating
with,
and
you
know
you
can
go,
read
it
if
you
want
to
but
like
you
don't
have
to,
then
it
just
won't
matter
that
much.
A
A
C
A
B
A
A
C
C
A
B
A
C
A
C
B
A
C
C
A
C
A
A
C
A
You
know
there's
so
many
people
in
the
space
and
I
was,
you
know,
we're
all
working
for
different
companies
that
have
our
own
goals.
Obviously,
but
if
we
can
sort
of
form
a
good
community
around
this,
but
it
isn't
just
you
know:
vendors
vendors
enters
like
I,
think
making
the
hotel
site
be
sort
of
the
one-stop
shop
for
people
to
come,
find
stuff
and
find
these
resources
and
be
really
good.
So.
A
B
B
A
Think
the
biggest
things
right
now
would
be
these
Quick
Start
Guide
and
some
of
this
new
user,
because
this
guide
content,
okay,
so
the
actual
technical
stuff
isn't
really
that
big
of
a
deal
and
but
what
I?
What
I
want
to
do?
What
I'll
do
is
I'll,
take
a
pig's
eye
to
go
and
make
sure
that
the
issues
and
milestones
are
up
to
date,
and
then
people
can
just
you
know.
I
can
take
responsibilities
like
managing
issues
and
labeling
things
and
making
sure
that
if
people
want
to
work
on
stuff
the
it
gets
reviewed
so.
B
So
I'll
just
I
guess
over
the
next
probably
next
week
when
I
have
more
time.
I'll
just
start
picking
up
a
few
of
these
and
writing.
Little
like
I
can
take
on
what
is,
for
example,
okay,
great
yeah
and
what
is
tracing
I
think
we
did.
What
I
think
you
intend
said
earlier,
which
is
copy,
that
tracing
site,
yeah
I've.
C
A
A
C
A
C
A
C
A
C
Post
that
could
be
repurposed
as
far
as
like
explaining
the
topology
of
open,
telemetry
right,
you
break
it
down.
You
say:
hey
these
api's
you're
using
that
for
instrumentation,
but
then
you've
got
to
process
the
data
and
that's
the
clients.
And
then
you
got
to
send
it
somewhere
and
that's
this
collector
and
then
you
gotta
put
it
in
it
back
end
and
then.
A
A
C
A
You
see
my
new
post
10,
send
it
to
you,
but
it's
it's
basically
that
perfect.