►
From YouTube: 2022-11-03 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
A
D
Okay,
I'm
not
sure
if
severn's
gonna
be
joining
I
know
that
he
was
doing
some
PTO
at
some
point.
Yeah
I
guess
we
could
get
started
first
item
on
the
agenda
is
from
Libby
blog
content
and
frequency
per
select
discussion.
C
C
C
We
get
a
lot
of
blog
blogs
coming
in,
which
is
great
I'm,
wondering,
though,
if,
if
some
of
it's
getting
a
bit
noisy
and
the
I
think
the
question
about
whether
some
of
it
should
be
product
docs
is
a
really
valid
question
as
well.
That
we
may
want
to
think
about
addressing
in
the
context
of
all
of
this.
D
Yeah
I
I,
almost
kind
of
like
want
to
take
a
hard-line
stance
around
getting
started
material
in
particular
so
like
if
it's
like
how
to
get
started
with
blah
blah
blah
and
language.
D
There's
no
existing
docs
for
that
I
feel,
like
all
the
energy
towards
figuring
out
how
to
get
started
should
be
in
in
creating
those
docs
and
not
necessarily
creating
the
blog
post
and
like
I,
don't
want
to
tell
someone
to
like
stop
whatever
they're
doing
but
like
at
the
same
time.
I.
Don't
I
wouldn't
like
I,
don't
want
to
have
the
blog,
be
a
collection
of
how
you
get
started
with,
like
you
know,
asynchronously
at
some
point.
D
D
I,
don't
think,
and
we
got
that
from
golang
and
rust.
Already
rust
is
in
PR
right
now,
but
like
I'm
I'm,
fine
with
getting
that
rust
blog
post
in,
we
already
put
a
lot
of
energy
into
reviewing
it,
but.
A
C
D
C
D
And
it
was
like
this
code
doesn't
compile?
Could
you
fix
that.
D
So
so,
like
you
know,
they're
like
I,
don't
want
to
It's
Tricky
I,
don't
want
to
prevent
people
from
contributing
and
I.
Don't
want
the
blog
to
necessarily
just
be
like
a
place
where
announcements
about
open
Telemetry
go
and
that's
about
it,
but
like
okay.
So
to
like
draw
a
a
comparison.
D
There
was
a
blog
post
about
instrumenting
with
a
patch
with
instrumenting
with
Apache
and
Java.
That's
not
really
a
getting
started
topic.
That's
like
not
really
much
of
a
docs
topic,
like
maybe
parts
that
could
live
in
documentation
but
like
that
feels
like
it's
good
for
a
blog
post
right
now,
but
whenever
we
have
like
a
how
to
get
started
with
x-
and
you
know
language-
and
it's
like
really
just
how
to
use
open
Telemetry
with
a
given
language,
then
I
would
want
to
mold
that
into
docs
more
than
anything
else.
C
C
You
know
we
want
to
make
sure
that
there's
enough
space
around
the
blog
about
that
that
people
can
focus
on
that
and
it
doesn't
get
lost
in
the
noise,
and
that
may
give
us
an
additional
benefit
of
being
able
to
schedule
things
to
be
published
rather
than
you
know,
kind
of
an
ongoing
scramble
to
review
things
best
effort,
because
you
know
we're
in
this
sort
of
reactive
state
but
I'm
curious
to
hear
what
other
people
think.
D
I
completely
agree
that
having
a
a
publication
calendar
makes
sense
because,
like
it's
entirely
ad
hoc
right
now,
but
that's
not
a
good
solution.
B
What
I'm
feeling
is
the
if
we
have
a
consensus,
Among
Us,
then
that's
the
first
step
and
then
we
can
possibly
take
it
incrementally
in
terms
of
if
folks,
if
somebody
submits
a
blog
post
and
that
we're
feeling
that
it
should
go
into
the
docs
and
that
we
have
an
agreement
amongst
ourselves
as
the
main
reviewers.
Then
we
can.
We
can
take
that
kind
of,
maybe
one
at
a
time
and
I'm
feeling
that
there'll
be
a
momentum
that
will
pick
up
and
folks
will
start
to
see
a
pattern
that
oh
well
I.
B
If
I'm
going
to
submit
a
Blog
that
feels
like
a
get
started,
I'm
going
to
be
asked
anyways
to
rework
it
a
bit
and
submit
it
to
the
docs.
So
you
know
I
think
it'll
become
part
of
the
culture.
If,
if
we
do
it
incrementally
and
but
as
long
as
we
all
agree
that
that's
the
direction
we
want
to
head
in.
D
Yeah
I
would
I
would
agree
with
that
yeah.
So
as
far
as
getting
a
publication
calendar
set
up
Patrice,
would
you
know
how
we
would
do
that
or
like
should
we
just
talk
to
Austin.
C
D
Yeah,
you
know
actually
well,
let's
get
ignoring
scheduling
one
for
a
second
we're,
not
utilizing
projects
at
all
in
in
this
repo.
D
Maybe
we
could
actually
just
do
that
like
use
a
GitHub
project
for
for
blogs,
and
then
you
know
currently,
whatever
is
on
Deck
is
sort
of
sort
of
there,
and
then
we
we
establish,
like
whatever
the
the
publication
order,
is
going
to
be
there
and
if
anybody
has
any
questions
they're
like
well,
this
is
where
this
is
where
it's
tracked,
your
blog
post
would
probably
fall
like
along
these
lines.
D
So
it's
not
it's
not
quite
a
calendar
but
like
so
I
bring
it
up,
because
that's
what
I
know
that
one
of
our
marketing
managers
at
honeycomb
does
this
for
our
own
blog
there's
like
an
Asana
board
and
a
tracker
for
you
know
like
there's,
always
like
a
handful
of
blogs
in
flight
at
any
given
moment,
and
so
it
seems
to
work
pretty
well
I'd
be
more
than
happy
to
try
to
drive
that
and
see
if
we
could
do
a
similar
thing.
Yeah.
B
I
think
that
we
should
also
agree
about
process
in
terms
of
blog
posts
being
delayed,
I'd
like
to
suggest
that
we
review
them
in
whatever
time
frame
is
appropriate
and
get
the
PRS
merged,
as
opposed
to
let
PRS
stick
around
emerge,
but
with
have
blog
posts
with
a
draft
status
and
and
then,
whenever
the
time
comes,
whoever's
the
blog
Prime
can
just
twiddle
the
you
know,
remove
the
draft
status
and
then
the
post
and
maybe
possibly
change
the
date
hey.
C
C
Yeah
so
sort
of
related
to
this
I've
been
working
on
a
PR
to
put
together
some
guidance,
for
you
know
the
discussion
we
had
last
time
about
language
and
best
practices
and
so
on
and
realized
that
it
would
be
good
to
have
some
guidance
about
the
blog
too.
So
I
can
add
that
what
we've
talked
about
here
into
that
guidance
so
that,
as
we
publish
that
PR,
it
will
include
here's
a
new
thing,
we're
doing
and
we'll
be
able
to
point
people
as
they
as
blog
PR's,
come
in
to
hey.
C
Did
you
read
this
so
that
we're
not
just
surprising
people?
C
C
B
C
Don't
have
an
issue
tracking
I,
don't
believe
we
do
what
we
discussed
last
time,
which
was
adding
some
guidance
around
language,
best
practices
and
documentation.
So
it
started
a
section
of
that.
I
think
it'll
be
a
couple
of
new
pages,
but
anyway
take
Don't,
Panic
Take,
a
look
when
you
see
the
pr
and
totally
open
to
doing
it
differently,
but
I
think
it
makes
sense
to
also
add
in
guidance
around
the
blog.
C
And
so,
if
we
create
an
issue,
we
could
bundle
it
or
have
separate
issues
for
both
whatever
works
best
for
the.
C
Easily
could
I
ask
you
then,
to
create
them.
This
I'm
still
not
great
at
jira
issue
management.
So
thank
you.
I
am
learning
I
promise.
You
won't
have
to
keep
doing
it.
For
me.
D
Upon
my
honor,
we
will
never
switch
to
jira
for
this
project.
I.
A
B
A
D
Going
once
come
on
twice:
okay,
the
next
topic
timely,
is
about
the
timing
of
two
blog
posts
that
are
like
definitely
pretty
much
all
approved,
and
so
we'll
want
to
think
about
the
timing
of
these
two
and
which
one
goes
first
and
and
so
forth,
and
so
maybe
this
is
actually
a
great
way
to
practice.
What
we
want
to
establish
here,
where
we
could
merge
them
as
drafts
and
then
establish
the
ordering
and
then
and
then
release
them
during
those.
You
know
whatever
time
we
agree
or
best.
B
I
I,
don't
think
I
mentioned
this
in
the
meeting
before
but
I'm
surprised
at,
but
accepting
of
the
concern
of
wanting
to
throttle
Cadence
on
other
projects.
You
know
when
the
blog
posts
are
ready,
they
go
out
so
I
would
say
in
for
these
two
particular
ones
it
I
I,
don't
see
any.
A
D
Think
it's
more
different,
I
think
it's
more
like
on
the
promotional
side
of
things
so
like
in,
like
promotional,
like
via
social
media,
will
be
orthogonal
to
anything
that
we
actually
release
and
publish,
and
so,
like
you
know,
do
we
I
know
that
often
there's
like
a
little
bit
of
space
that
you
want
to
leave
between
things
that
you
promote,
but
maybe
that's
actually
not
the
case
and.
B
B
A
controlled
release
on
social
media,
okay,
so
I,
don't
know
if
we
would
like
to
adopt
that
sort
of
a
strategy
which
might
simplify
our
streamlining.
For
example,
we
wouldn't
be
having
this
discussion
because
I
think
both
both
of
those
two
are
pretty
much
ready,
so
they
could
be
merged
and
then
it
would
be
whoever's
responsible
would,
with
social
media
and
there's.
Even
there
are
Services
out
there
that
can
space
out
posts
for
you
and
post
at
particular
times
and
things.
C
B
I,
don't
know
if
if
he
is
using
such
feature
or
capability.
C
D
Did
that
one,
but
there
I
know,
there's
the
these.
The
official,
open,
Telemetry
account
and
I
know
that
Austin
runs
that
one
I
don't
know
who
else
has
access
to
it?
But
it's
probably
pretty
limited
I'm,
not
aware
of
any
tools
that
that
we
might
use
to
schedule
certain
things
or
like
Sprout,
social
or
I.
Think
that's
one
of
the
common
ones
that
people
use
I.
C
A
D
Okay,
okay,
so
then
just
tactically
then
we'll
just
merge
both
so.
D
B
D
Might
be
better
just
so
that,
like
the
timing
for
okay,
like
it,
it
is,
live
and
then
and
then
promoted,
is
sort
of
corresponds.
At
the
same
time,
we
also
don't
have
to
do
that.
It
could
also
just
be
merged
just
right
now,
as
whatever
the
current
date
is
and
then
tree
promotion
is
entirely
orthogonal.
C
If
we
go
ahead
and
do
a
Content
calendar,
one
of
the
things
that
we
could
do
is
say
well
logs,
come
out
on
Mondays,
so
there's
one
blog
a
week
and
then
use
these
two
blogs
as
the
first
ones
on
the
content
calendar.
As
you
know,
the
example
children.
B
We're
there
I
mean
that
makes
sense.
If,
if
that's
the
direction
you
all
want
to
go
in
in
terms
of
having
the
the
content
calendar,
then
it
would
make
sense
to
start
it
off
now,
and
in
that
case,
these
two
PRS,
the
blog
posts,
would
have
to
be
slightly
changed
so
that
there
they
have
draft
status
and
they're
further
merged
foreign.
B
D
Yeah,
let's
just
go
ahead
and
do
that
I
think
we
do
have
the
ability
to
Market
as
a
as
a
draft.
D
We
just
like
just
make
the
suggestion
to
do
that
and
then
accept
the
suggestion,
cool
yeah
I
think
we
should
just.
We
should
do
that.
Then
I
would
probably
propose
that
the
Jaeger
deprecation
won't
go
out
first,
just
because
that
has
a
survey
and
that's
well.
That's
time
sensitive,
like
there's
a
call
to
action
and
an
eventual
outcome
that
that
we're
looking
to
achieve
broadly
across
the
project
with
deprecating,
Jaeger
clients
or
sorry,
Jaeger
Jaeger
specific
exporters,
whereas
the
other
one
is
like.
D
B
D
D
Great
okay,
so
then
we'll
plan
to
get
the
front
end
overhaul
next
Monday
then
I'll
make
a
suggestion
for
the
date
for
for
Oscar
the
offer
to
to
do,
and
then
we'll
just
get
that
one
out
there
as
well
I'll
set
something
up
as
a
project
board
to
track
it.
I
guess
or
I,
don't
know
something
anything
so
that
I
don't
forget
about
it.
A
D
So
we
got
that
the
next
topic
on
the
agenda
that
we
have
is
the
hotel,
Bond
Patrice.
You
want
to
talk
about
that.
B
Mainly,
it
was
a
couple
of
questions
well,
first
of
all,
a
hooray
I'm
glad
that
we
had
the
bot
I
think
we
had
already
identified
quite
a
few
use
cases
for
the
bot
and
my
main
question
is:
who
set
it
up?
Who
should
we
contact
who's,
the
custodian
or
who
are
the
custodians?
If
anybody
knows
in
terms
of
if
we
want
to
reuse
it,
for
example,
to
automatically
automatically
pull
in
the
specification
every
time,
there's
a
new
release
so
that
we
can,
or
at
least
generate
the
pr.
D
So
I
can
answer
a
little
bit
of
that.
I,
don't
know
if
it
was
the
Java
instrumentation
folks
who
set
it
up,
that
they
use
it
the
most
just
to
coordinate
version
bumps
across
their
repos,
and
so
we
had
talked
to
them
about
using
it
to
also
update
the
version
of
Java,
SDK
stuff
and
a
few
other
things
just
in
the
docs
themselves,
and
so
like
it
knows
hey.
This
is
this:
is
the
version
in
this
part
of
the
markdown
file?
D
And
you
know
whenever
there's
a
new
release
just
pump,
it
I
think
there's
a
handful
of.
D
D
What
are
some
other
so,
okay,
so
like
it
could
be
set
up
for
a
few
other
things.
Basically,
anything
where
there's
like
a
version
number
so
like
like
a
collector,
contrib
version
or
just
collector
version
itself,
should
arguably
also
just
be
bot
PR's
that
kick
off
whenever
they
they
cut
a
release.
D
I
don't
know
who
would
set
that
up
for
us,
but
I
think
that's
something.
I
can
follow
up
on
to
make
sure
that
we
do
get
that
set
up,
because
that
is
way
better
than
having
to
do
it
ourselves
or
wait
for
a
maintainer
on
there
and
to
remember
that
the
docs
need
to
be
updated.
D
Okay,
well,
I
will
do
that.
D
Follow-Up
I'm
I'm
just
going
to
create
an
issue
for
myself,
I'm,
going
to
say
to
myself
to
get
that
set
up
for
the
spec
and
also
The
Collector
and
collector
contrib
version
numbers,
and
so
those
are
the
only.
Those
are
the
only
ones
that
I'm
aware
of
that
could
probably
be
bot
driven
the
others.
C
B
While
there's
a
moment
of
silence,
I
just
added
a
suggested
draft
status
to
the
the
other
blog
post
to
the
front
end
overhaul
and
change
the
date
to
next
Monday
awesome.
Thank
you.
C
Awesome,
oh
something
we
should
probably
talk
about
I,
believe
this
meeting
is
changing
time
and
date.
D
Yes,
it
is,
it
is
going
to
change
to
yeah
starting
two
weeks
from
now.
It
will
be
on
Monday
instead
of
Thursday,
and
it
will
be
I'm
using
I'm
in
Pacific
time.
So
it's
10
a.m.
My
time
Pacific
and
it
will
be
an
hour
rather
than
the
weird
30
to
45
minutes
that
we
have
today
so
a
bit
more
normal,
which
is
good,
yeah,
1
p.m,
Eastern,
Time,
Mary
and
also
yeah.
D
You
should
be
able
to
actually
see
it
so
starting
on
the
14th
is
when
it
will
be
there.
D
D
I
would
highly
recommend
doing
that
as
well
and
then
yeah,
it's
just
going
to
run
from
10
to
11..
That's
that's
the
current
plan.
Sorry!
So
one
to
two
Eastern
for
for
those
of
y'all
on
the
Eastern
side
of
things.
D
Some
of
the
impetus
behind
this
is
Mondays
seem
to
work
far
better
for
myself
and
Severn
in
general,
and
especially
Severn
is
going
to
be
having
some
like
problems
with
the
Thursday
time
for
the
next
couple
of
months,
just
in
general,
and
so
we're
like
okay.
Well,
if
we're
gonna
move,
it
then
like,
let's,
let's
move
it
and
have
it
be
like
when
a
lot
of
other
meetings
kind
of
just
tend
to
happen
in
general,
instead
of
being
at
10
15
every
other
Thursday,
it's
just
a
weird
time
in
general,.
D
And
then
from
there
the
Cadence
will
still
be
every
two
weeks.
So
really
just
the
the
time
and
day
that
are
changing.
A
D
Let's
see,
how
are
we
doing
on
time
here?
Okay,
so
we
run
until
the
end
of
the
hour.
Is
there
anything
that
we
want
to
cover
for
the
next
15
minutes.
D
E
It
is
there
anything
with
reinvent
and
metrics
documentation
that
needs
to
be
finished
up
before
the
big
event,
because
I
when
I
attended
like
a
meeting
two
or
three
meetings
ago,
that
was
like
a
priority
and
some
documentation
was
done
and
I've
not
kept
track.
But
it's
kind
of
a
big
to-do.
If
open
Telemetry
is
going
to
make
a
splash.
D
I
would
say:
yes,
it's
it's
been
a
little,
so
the
the
challenge
that
I've
seen
so
far
and
talking
to
some
of
the
other
maintainers
is
the
metrics
sdks
are
still
not
broadly
ga
turns
out.
Metrics
has
just
been
hard
to
implement,
but
it
even
the
past
couple
weeks.
It's
gotten
better,
in
particular
on
the
JavaScript
side.
They
do
have
it
it's
kind
of
a
weird
thing
going
on
with
them
with
a
contributor
who's
and
this
it
might
be
like
a
language
barrier
or
something
but
anyways.
D
D
This
is
the
right
like
way
that
you
should
use
this
part
of
the
SDK
and
then
we're
just
going
to
take
that
and
we're
going
to
move
it
on
over
into
the
website
and
then
we're
gonna
change
it
up
a
little
bit
so
that
it
fits
the
structure
that,
like
that
we
outlined
beforehand,
but
like
that's,
fine
right,
it's
code,
samples
that
are
gonna
work
and,
like
that's,
that's
easy.
D
Not
really
and.
A
D
Hopefully,
we
will
have
something
that
we
can
start
making
serious
progress
on
by
the
next
meeting.
The
JavaScript
side
of
things
are
like
mostly
wrapping
up.
I
know
that
python
is
pretty
much
wrapped
up
on
an
SDK
set
of
things.
D
Maybe
actually,
this
is
just
a
task
for,
for
some
of
us
I'll
count
myself
in
this
group
is
to
just
go
to
some
of
the
language
things
like
dot
net
Ruby
JavaScript
Java
go
will
not
be
ready,
so
it
won't
bother
with
that
one
and
then
just
say:
hey
metric
stocks,
here's
an
issue
that
we
filed
that
has
like
distance.
How
the
structure
of
the
dock
should
look.
D
Take
a
look
at
this
and
like
what
code
samples
can
you
contribute?
Even
if
it's
not
a
whole
lot
just
enough
to
like
get
things
going,
that
you
can
open
up
as
a
pull
request
and
just
throw
some
code
over
the
wall
at
us,
because.
D
You
can
do
that,
then
it's
actually
pretty
easy
for
us
to
mold
it
into
whatever
shape.
We
need
that
so
so
that
specifically,
the
the
the
thing
that's
trickiest
is
not
like
all
the
different
things
that
you
can
do
with
the
SDK.
It's
like.
How
do
you
properly
like?
How
do
you
properly
initialize
this
in
the
most
correct
way
possible?
D
D
These
are
like
the
main
five
topics:
I'll
try
to
create
one
of
each
and
like
have
like
a
little
counter
and
a
console
app
or
something,
and
then
you
know
you
have
examples
for
each
of
those,
but
the
initialization
in
particular
is
tricky
and
that's
like
especially
at
this
stage
like
really
only
the
maintainers
of
these
projects
know
how
to
properly
initialize
this
stuff
and
so
the
danger
that
we
run
into
when
we
try
to
document
it
right
now.
D
Is
we
tell
you,
hey
here's,
how
you
set
up
metrics,
so
you
can
do
this
stuff
and
then
it's
like
actually
wrong
or
or
just
bad
in
general
and
so
I've.
Personally,
held
off
from
that
and
I've
told
them
like
hey
when
you
are
ready
to
get
some
stuff
up
in
the
dock
site,
contribute
this
a
little
bit
this
little
bit,
and
then
we
can.
E
Okay,
that's
not
bad
I
mean
that's
still,
five
of
the
major
languages
that
are
available.
D
Yeah,
actually
Ruby
will
not
be
a
part
of
this
list,
so
it's
it'll
just
be
four
and.
E
Okay,
thank
you
for
that
update,
Philip
I
wasn't
quite
sure
what
that
status
was.
So
that's
very
helpful.
Yeah.
D
It
is
greatly
Complicated
by
the
inconsistent
status
of
metrics,
just
as
a
whole
across
the
project.
Oh.
D
Yeah
and
well,
and
they
run
into
separate
challenges.
Like
you
know,
I
was
talking
with
one
of
the
go
maintainers
and
apparently
the
way
that
particular,
what
are
called
views
are
specked
out
is
extremely
challenging
to
design
correctly
for
go,
whereas
apparently
for
JavaScript,
it's
like
easy
peasy.
So.
C
I
I
don't
know
if
this
is
the
right
place
to
bring
this
up,
but
at
hotel
unplugged
we
had
a
number
of
discussions
and
issues
and
suggestions
came
out
of
that.
I
I
was
one
of
the
note
takers
and
I
know.
Others
were
still
yet
to
put
that
together.
C
There
was
also
the
project
meeting
that
happened
on
the
Tuesday
at
kubecon.
All
that
the
decisions
actions
discussions.
All
of
that
should
be
recorded
somewhere,
I
guess
what
I'm
asking
is.
Should
this
be
something
that
goes
somewhere
onto
the
website
or
documentation
or
lives
in
GitHub
issues
and
I
I
expect
that's
a
broader
question
than
this
group
alone
can
answer,
but
I'm
not
sure
where
else
to
raise
it.
C
D
I
would
agree,
and
even
if
you
know
like
the
list
of
issues,
even
if
that
is
tracked
on
GitHub,
if
there's
a
link
to
it,
that
is
on
the
site
itself,
that's
more
discoverable
for
sure.
D
Right
and
so
where
on
the
site
would
be
a
decent
place.
Well,
you
know,
there's
always
more
in
the
table
of
contents
that
we
can
fill
out
under
the
community
site,
the
community
part
of
the
site
yeah.
D
Maybe
maybe
that
maybe
it's
it's
just
a
whole
new
whole
new
section.
There
I.
E
Mean
if
you
want,
you
can
do
there's
monthly.
A
D
There
is
I'd
say
like
go
ahead
and
take
a
stab
of
like
what
what
it
might
like
what
might
seem
like
a
good
place
for
it
on
the
website
and
if
it
doesn't,
if
it
doesn't
feel
like
you
could
find
a
good
place
for
it
to
fit,
then
we
could
figure
out
something
else,
but
I
would
I
would
probably
prefer
that
as
well.
If,
if
we
can
yep
represent
it
well
enough.
C
Yeah,
if
someone
couldn't
create
an
issue
and
aside
it
to
me,
I
can
take
that
and
then
work
with
the
other
two
people
who
took
notes,
Morgan
and
race
to
to
get
something
happening.
Okay,.
A
D
Yeah
and
and
I
would
say,
like
you
know,
even
like
a
draft
PR,
that's
like
hey,
and
this
is
what
it
might
look
like
that
works
totally
fine
for
me
as
far
as
giving
it
a
shot,
so
yeah
I
think
we
could
just
proceed
that
way
and
hopefully
hopefully
it's
not.
Hopefully
we
can
get
it
represented
in
some
decent
way
on
the
site.
I
I
think.
D
Okay,
fantastic
well,
I,
don't
have
any
additional
topics
and
we
have
three
minutes:
left
cool,
there's,
more
pull
requests,
but
they're
slowly
getting
merged.
D
I
think
so,
I
think
to
the
to
the
point
about
metrics
later
that
we
should
probably
expect
in
this
next
month
to
see
a
larger
flurry
of
pull
requests
start
coming
our
way
be
they
from
maintainers
or
just
ourselves.
There
might
be
a
spike
of
like
a
pretty
big
spike
of
activity
there
I
don't
know
if
there's
anything
specific
to
reinvent
that
we
want
to
do
for
hotel
in
general,
like
at
least
on
the
blog
or
something
like
that,
but
it's
at
least
as
far
as
content
is
concerned.
E
D
E
D
Yeah
I'm
not
aware
of
anything
so
so.
I
know
that,
like
Michael
hasenblaus
who
works
for
AWS
is
going
to
be
giving
a
talk
on
observability
in
general.
That's
about
like
open,
Technologies
and
hotel
will
clearly
be
a
part
of
that.
I
wouldn't
be
surprised
if
there's
a
couple.
Other
open,
Telemetry
talks,
but
I'm
not
aware
of
any,
like
particular
like
big
launch
or
Splash,
that
the
project
is
trying
to
accomplish
by
reinvent
okay.
E
A
E
A
D
Well,
we
are
pretty
much
a
time
here
so
I
gotta,
head
off
before
I,
have
a
Twitter
space.
It'll,
be
my
first
time
doing
that
it'll.