►
From YouTube: 2022-11-14 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
B
C
D
E
B
B
Up
there
for
people
and
if
you're
gonna
be
in
a
meeting
with
like
a
VP
or
something
sometimes
you
wanna
change
it
before
you
join.
C
B
Okay
well
I,
think
well.
Ted
had
some
topics
but
Ted's,
not
here
yet.
E
I
I
think
it's
semantic
conventions,
working
group,
yeah,
yeah
and
I.
Think
I
I
think
his
proposal
was
like
yeah.
Let's
do
another
meeting
next
week
and
then
start
alternating
so
having
one
more
meeting
versus
yeah
them
waiting
three
weeks
and
then
having
one
I
would
be.
Okay
with
that
would
be
before
I
say
anything.
Let
me
check
my
own
calendar
for
next
week,
but
this
distance
work
for
everybody,
or
should
we.
E
F
E
G
G
F
G
F
E
B
B
Okay,
okay,
so
yeah
I've
had
a
few
of
the
ability
to
change,
go
ahead
and
do
that
I
guess
I
am
going
to
do
it.
B
E
Okay,
the
next
topic
was
also
from
you
Tad
on
the
hotel
announcements,
yeah.
G
So
yeah
there
was
a
I
think
Rhys.
You
had
a
good
idea
to
create,
like
an
announcements
channel
on
slack,
just
something:
that's
like
low
volume,
so
that
people
have
a
place
where
they
can
keep
track
of
new
releases
and
other
things.
I
thought
that
was
a
good
idea.
So
I
went
ahead
and
made
the
channel
seemed
like
there
was
some
debate
about
how
to
to
update
it
or
what
to
do
with
it.
G
I
think
Matt
Young
had
a
lot
of
questions.
I,
don't
see
him
on
the
call,
but
for
for
me,
I
kind
of
feel
like
keep
it
simple.
It's
like
the
best
principle
to
follow.
I
was
thinking.
It
was
just
going
to
be
a
slack
Channel.
G
He
was
suggesting
something
like
a
GitHub
repo
that
people
update
and
then
it
gets
like
pushed
out
to
other
things,
and
if
we
are
trying
to
like
push
this
out
to
like
many
places,
I
could
see
that
that
being
a
thing
but
like
I,
don't
I,
don't
know
that
we're
trying
to
do
that
so
I
I
would
be
content
with
just
trying
to
figure
out.
G
I
feel
like
there
must
be
a
bot
already
connected
up
to
cncf
slack
for
like
automating,
like
github-based
announcements
for
things
like
releases
and
stuff
I
think
it
would
be
cool
to
just
automate
like
for
all
of
our
repos
and
hotel,
that
generate
releases
if
we
could
just
have
a
bot
that
automatically
added
a
message
to
that
channel.
Every
time
a
new
release
gets
pushed
out.
E
E
E
On
the
on
on
the
Chatters
thing,
so
there's
a
thing
we
have
here.
We
have
a
products,
announcements,
space
and
there
are
only
a
certain
amount
of
people
are
allowed
to
to
send
messages
to,
and
everybody
else
is
only
allowed
to
go
into
threats.
I
think
that
could
also
be
an
interesting
approach
to
to
say,
like
hey,
only
hotel,
maintainers
are
allowed
to
make
announcements
and
everybody
else
is
only
allowed
to
or
only
depart
or
whatever,
and
everybody
else
is
only
allowed
to
to
comment
on
threats
or
something
like
that.
E
G
G
G
Yet
feel
like
we
have
like
a
problem
with
like
too
many
announcements
like.
If
so
it
would
be
nice
to
have
it
be
open
for
anyone
to
come
in
there
with
an
announcement,
even
if
it's
something
like
Hotel
adjacent
like
like
a
there's.
These,
like
Trace,
driven
testing
projects
that
are
based
on
open,
Telemetry-
and
you
know
stuff
like
that
and
I
just
think
it
would
be
cool
if
we
had
a
wide
pool
without
the
need
for
moderation.
G
So
that's
that's
my
my
thought
is
if
we
could
just
start
with
something
like
that,
and
maybe
the
only
thing
there
really
is
hey
I
feel
like
it's,
maybe
a
little
nebulous
who
has
access
to
the
hotel.
Twitter
account
I
had
access
to
it.
G
It's
probably
in
like
the
one
password
thing
that
I
haven't
set
up
yet
I
always
thought
it's
just
Austin
there
there
was
a
pile
of
us.
I,
don't
know
I
used
to
post
there,
but
at
any
rate
like
maybe
a
thing
is
like
part
of
comms
is
if
we
can
make
sure
it
seems
like
if
I
don't
know
about
automating
it,
but
like
just
watching
that
announcement's
channel
and
putting
relevant
things
up
onto
our
hotel,
Twitter
account
or
just
in
general,
being
a
little
more
active
with.
C
And
then,
before
we
move
on
to
Severance
topic,
I
was
gonna.
Ask
about
you
know
from
the
announcements
channel.
Would
it
make
sense
to
do
like
periodic
blog
posts
that
summarizes
releases,
like
maybe
weeklies
too
often,
but
maybe
like
bi-weekly
or
monthly.
C
Maybe
like
some
of
the
larger
I,
don't
know,
I
know,
there's
sometimes
like
the
bigger
news,
gets
their
own
blog
posts,
but
I
don't
know
if
might
be
helpful,
for
you
know
people
to
have
that.
I
mean
I,
guess
that
we
could
see
how
the
channel
ends
up.
Looking
too,
if
it's
a
lot
to
navigate
or
if
it's
like,
oh
okay,
yeah.
E
I
I
think
also
I
mean,
let's
see
how
the
channel
turns
out
and
then
maybe
let's
do
the
twitters
thing.
And
then,
if
we
see
like
hey
here's
a
substantial
amount
of
stuff,
every
I,
don't
know
I
would
say:
maybe
a
month
should
probably
be
enough
or
or
maybe
even
only
quarter,
and
then
we
say
like
hey
here's
the
quarterly
update
on
an
open,
Telemetry
yeah,
something
like
that.
I
mean
that's.
E
That's
definitely
something
people
also
internally,
ask
me
again
and
again,
like
hey:
what's
new
in
open
Telemetry,
hey,
what's
what's
the
version
of
x
y
and
said
so
having
something?
And
even
if
it's
only
the
slack
channel
that
you
can
say
like
hey,
let's
Point
them
there
that
I
think
that
that's
a
good
starting
point
and
then
we
can
see
like
how
could
to
to
maybe
feed
the
blog
or
yeah.
G
E
Maybe
even
a
releases
page
or
something
like
that
from
there
so
yeah.
B
Is
actually
just
very
similar
to
the
top
I
got
them
that
I
put
on
there
like
announcements
about
like
hey,
like
meaningful,
was
released
like
we
don't
really
do
like,
for
example,
JavaScript
metrics
just
went
GA
that
could
like
totally
go
to
the
hotel
announcements
Channel
if
it
existed
and
like
you
know,
maybe
if
there's
a
couple
other
things
that
like
Teresa's
Point
like
yeah,
we
could
bundle
that
up
and
that's
a
blog
post
like
hooray
check
it
out.
I
think
that'd
be
fantastic,
like
I.
B
G
I'm
doing
work
right
now
to
get
more
project
management
into
the
specification
working
group
like
we
have
a
process
now
for
organizing
things
into
projects
and
kind
of
scheduling
them
out,
but
we
don't
really
have
like,
like
the
people
power
to
to
keep
that
up
to
date,
but
looks
like
there's
interest
from
various
organizations,
there's
a
call
out
to
like
people
on
this
poll
too.
G
If
you
know
anyone
at
your
respective
organizations
who'd
be
willing
to
be
part
of
a
a
PM
team,
they
don't
even
have
to
be
official
PMS
or
anything
just
someone
who's
willing
to
to
like
do
that
kind
of
work
on
the
spec
backlog.
G
Once
we
have
that
up
and
running
it
will
be
a
lot
easier
to
like
turn
that
into
like,
like
if
we
have
a
quarterly
blog
post
to
have
it
not
just
be
like
this
is
what
we
released
but
like
this
is
what
the
the
high
level
roadmap
looks
like
for
the
future
get
involved
in
these
projects.
If
they're
interesting
to
you
that
I
think
that
would
be
like
super
super
valuable.
G
But
I
feel
like
it's
right
now.
It
would
be
kind
of
like
a
fair
bit
of
work
for
whoever
took
on
that
blog
post
to
kind
of
like
collect
up
all
that
information
so
should
like
maybe
hold
off
on
that
for
a
bit
yeah.
G
B
Yeah,
like
let's
create
the
channel
and
then
we'll
just
like
next
Monday,
go
to
the
sink,
because
we
already
missed
our
chance
this
week
and
say
hey
by
the
way.
Please
post,
like
you
know,
you
got
metrics
sdks,
you
all
are
working
on
when
you
flip
the
switch
to
like
say
it's
live
Post
in
this
Channel
and
yeah.
G
Yeah
and
I'm,
hoping
like
I'll
talk
to
the
PHP
people,
if
it's
possible
to
just
get
this
hooked
up
with
releases
that
we
don't
like
you
know,
the
maintainers
don't
need
to
to
be
bothered
with
it
too
much.
Hopefully,
they're
like
there
should
be
a
courage
to
write
good
release
notes
and
if
they
write
like
good
release
notes,
then
they
probably
don't
need
to
to
make
a
separate
update
over
there,
but
but
yeah.
It
would
be
good
to
once.
We
once.
B
G
G
D
G
That
as
an
action
item
for
this
week
to
see,
let's
see
about
the
bot
but
oh
I
did
have
one
question
like
the
one
thing
I
was
a
bit
nebulous
about
was
whether
content
counts
as
announcements.
G
A
Would
probably
bump
up
the
traffic
quite
a
bit,
and
originally
you
said
this
would
be
a
low
volume,
Channel
yeah
and
so
tying
back
to
the
idea
of
a
monthly
summary
I.
Think
that
would
make
sense
to
put
into
the
monthly
report.
Okay,
great
yeah.
C
G
I
think
that's
totally
fair
I
wanted
to
check
in
with
people,
because
that's
if,
like
there's
one
thing
we'll
probably
have
to
moderate
in
there,
it's
that
is
to
so
I
just
wanted
to
make
a
I'll
make
a
like
short
pinned
announcement.
Just
saying
this
is
for
open
source
updates
to
hotel
and
hotel
adjacent
projects.
It
has
to
be
like
an
actual
like
update,
though
to
one
project
you
can't
be.
It
can't
just
be
content
about
the
projects
and
cool
yeah.
E
E
We
also
had
some
issues
for
getting
started,
so
the
people
coming
to
the
open,
Telemetry
I
over
reported
that
we
update
the
to
read
me
a
little
bit
and
then
we
also
had
this
discussion
around
writing
and
styling
guidelines
so
that
we
say
like
hey:
let's
use
the
open
the
the
Google
rule
set
yeah,
I
I
think
we
we
should
I,
don't
know
I,
think
all
of
them
are
stalled
a
little
bit
I'm,
not
sure
if
you
can
find
a
little
bit
of
time
on
pushing
that
within
the
next
few
weeks.
A
E
I
mean
one
more
thing
to
add:
I
mean
I
played
around
with
a
tool
called
Wale.
I.
Think
I
mentioned
it
before
once
so
it
allows
you
to
do
things
like
hey,
write,
open
Telemetry
in
oh
uppercase,
t
uppercase,
no
space
in
it
or
hey,
don't
use
passive
voice
or
all
those
things
I
played
around
a
little
bit
with
it.
I
think
the
it
can
be
a
little
bit
overwhelming
initially,
especially
if
you
introduce
too
much
rules
at
once,
but
I
I
just
tried
out
the
other
way
around.
Did
you
incrementally
add
rules?
E
So,
instead
of
saying
like
hey,
here's
the
whole
Google
rule
set
I
just
copied
out
individual
ones,
and
then
this
is
I
think
something
we
could
also
consider
doing
like
hey,
let's,
let's
start
off
with
a
few
simple
rules
and
then
see
like
how
it
is
going
and
then
grow
from
there.
That
might
be
another
approach.
A
B
Yeah
it
was,
it
was
hard
to
configure,
and
there
was
a
there
was
a
ton
of
pushback
internally
by
a
lot
of
people
when
we,
when
we
tried
it
like
yeah,
maybe
we
were
holding
it
wrong,
but
it
was.
It
was
not
a
good
time.
A
Right,
it
might
be
worth
trying
and
Sever
and
I
agree
if
we
go
incrementally
it
could
be
good.
A
I
just
want
to
mention
that
things
might
be
a
bit
complicated
because
we're
we
intersperse,
we
have
marked
down
with
short
code
calls
so
essentially
what
amounts
to
liquid
code
inside
the
markdown
and
sometimes
I,
don't
know
if
that
can
trip
tools,
and
that's
one
of
the
reasons
why
I
haven't
brought
in
prettier
as
as
as
part
of
the
check-in
process.
It's
just
because
we
cannot
systematically
apply
it
to
our
all
of
our
source
files,
because
it's
going
to
break
those
that
contain
calls
to
short
codes.
Yeah.
E
E
So
if
someone
is,
let's
say
interested
in
doing
that,
I
think
we
now
have
a
few
people
that
are
interested
in
doing
a
better
style
and
provide
pull
requests
around
like
hey
write
this
word
differently
because
whatever
so,
if
we
can
just
give
it
like,
like
I,
also
just
have
it
in
visual
code,
and
it
just
gives
me
a
list
of
potential
things
you
can
change,
but
yeah
I
I
would
also
not
enforce
it
right
as
we
do
it
with
still
markdown
linting
I
mean
it's
yeah
I
mean
let's
not
make
it
especially
I
mean
we
have
a
lot
of
people
just
coming
by
and
saying
like.
E
A
E
E
A
I
think
they're
assigned
right,
so
okay
Libby
is
assigned
to
one
of
them.
Maybe.
E
Yeah
I
think
she
wanted
to.
She
I
think
she
wanted
to
to
spend
some
time
on
that
yeah,
but
yeah.
The
other
thing
I
I,
just
I
was
not
around
last
time,
so
with
Miss
Ruby.
We
are
now
back
into
the
repo
right,
so
they
migrated
D
yeah.
What
about
go?
Is
there
any
any
updates
on
that
or.
B
Still
outstanding,
so
I
talked
with
Anthony
and
Aaron
on
the
go
Sig
in
person
at
kubecon
about
this
they
were
like
you
know,
both
yes,
a
fan
of
pulling
the
the
godox
in,
but
they
were
also
like.
This
should
be
talked
about
at
the
Go
Sig
as
a
topic,
and
so
that's
just
something
that
all
so
like
before
we
go
and
create
any
issues.
I'll
just
go
and
talk
with
them.
So
two
of
the
two
of
the
members
would
already
be
on
board.
B
I
think
they
want
to
just
spend
some
time
talking
through,
like,
for
example,
when
they
start
working
on
logs,
and
they
want
to
have
some
kind
of
documentation
a
should
they
have
that
documentation
if
they're
working
on
it
and
it's
unstable,
but,
like
you
know,
maybe
somebody
connects
it
and
B
if
they
do
like
who
should
be
in
charge
of
owning
that
and
like
should
there
be
like.
B
Should
we
just
like
put
a
placeholder
up
on
the
site
that
says:
hey
it's
unstable,
but
if
you're
interested
like
go
here
and
then
like
that
lives
in
their
repo
and
they
kind
of
around
with
it,
however
long
they
want,
because
I
think
like
for
things,
signals
that
are
stable,
like
traces,
they're,
not
gonna,
go
and
break
everything
all
the
time
and
so
like
having
it
live
outside
the
repo
and
not
be
co-located
with
any
other
thing
related
to
the
code
or
something
like
that's
far
less
of
a
concern
from
their
standpoint.
B
Well,
we
don't
even
want
metrics
like
on
a
site
yet
right
now,
because
there's
still
some
pending
things
with
views
that
could
change
stuff
and
like
that's,
why
they're
still
in
in
development
right
now
and
so
they're
like
well,
we
we
wouldn't
want
you
to
start
adding
like
metric
stocks
right
now,
because
that
could
just
make
things
unstable
for
folks
and
so
I
think
they
just
want
to
get
like
they
want
to
have
a
talking
through
of
like
how
do
we
consider
things
that
are
stable
versus
things
that
are
not
stable
and
like
if
they
are
represented
on
the
doc
site,
how
they're
represented
in
the
doc
site
and
that
that
kind
of
stuff?
B
So
okay,
yeah
lots
of
talking
with
the
mouth
words
but
I
think
overall,
they
at
least
two
members
of
the
of
the
Sig
are
very
open
to
the
idea
of
not
having
to
keep
their
docs
in
their
own
repo.
A
Can
I
mention
that
if
this
issue
of
having
dogs
that
are
in
quite
a
preliminary
state,
they
could
add
them
to
the
website
repo
but
have
a
whole
section
as
a
draft,
and
that
way
it's
not
published
on
the
production
server,
but
they
can
have
access
to
them.
Npr
previews
or
we
could
even
set
up
a
separate
Branch.
So
I
don't
know
if,
if
that
could,
if
you
could
bring
that
to
their
attention,
if
they'd
like
that
or
if
they
wanted
it
to
be
co-located,
so
it
would
be
more
convenient.
But.
B
B
We
want
to
have
the
docs
for
that
and
then,
like,
we
can
add
placeholders
to
just
say:
hey
it's
unstable
but
like
if
you
go
here,
this
is
like
a
sample
and
the
repo
that
demonstrates,
like
the
last
known,
good
way
to
do
something
with
metrics
or
logs,
or
something
like
that,
and
at
least
it's
not
like,
like
we
don't
avoid
the
situation
where
we're
documenting
something
as
if
it's
stable
and
then
like.
It's
clearly,
not
somebody
copy
paste
into
their
program
and
it
doesn't
work
and
so
I
think
their
perspective
was
like.
B
Oh
well,
you
know
that's
easier
for
us
to
update
if
it's
in
our
repo
but
I
think
the
interesting
discussion
is
like
well
should
that
be
documented
in
the
first
place,
if
it
is
like
unstable
enough
such
that
from
release
to
release
somebody
is
going
to
break
their
stuff
because
also
in
theory,
it
might
be
easier
to
update
stuff
if
it's
in
your
repo,
but
as
we've
seen
in
practice,
that
doesn't
happen.
So
it's
just
the
problem
is
closer
to
to
their
their
coach.
A
Okay,
thanks
for
moving
that
forward,.
A
It
is
all
we
have
left
to
do
is
to
delete
the
directory
in
the
Ruby,
repo
and
I'm
kind
of
doing
that,
as
as
we
speak,
is
that.
E
D
A
D
E
Okay,
so
Philip
dropped,
but
he
had
one
more
topic,
so
nature
announcement,
blog,
post
and
SDK
is
going
stable
yeah.
Maybe
maybe
we
discussed
this
the
next
week
or
follow-up
and
it's
like
anyways
anything
else,
any
any
topics
we
need
to
discuss
or.
E
No
awesome,
no,
no,
we
extended
the
meeting
to
to
an
hour
and
then
suddenly
we
don't
need
it
anymore
so
and
we're
gonna.
Do
it
again
next
week
yeah
exactly
let's
find
enough
topics
for
next
week
right,
so
it'll
vary
yeah,
awesome,
okay,
cool!
Thank
you!
Everyone
talk
to
you
thanks.
Everybody
bye,
bye,.