►
From YouTube: 2022-01-14 meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
C
Excuse
me
that
was
very
strange.
C
All
righty,
thank
you,
everyone
that
is
adding
your
name.
I
appreciate
it.
C
Quick
agenda
item
and
then
we
will
go
first,
happy
happy
2022.!
If
everyone
had
a
good
holiday
good
to
see
familiar
faces
bryce.
I
don't
recognize
you
first
time.
B
Yep
first
time,
so
just
I'm
excited
a
lot
to
learn
here.
Don't
want
to
get
in
the
way,
but
so
yeah.
First
time
cool
well
welcome.
C
To
the
comp
sig,
so
we
do
we
communicate,
which
mostly
means
the
website
at
this
point,
but
new
things
will
be
happening
so
yeah.
I
guess
first
off,
let's
just
go
around
the
room
or
I
guess
I'll
start
with
my
priorities
or
what
what
my
priorities
for
q1
at
least
are
for
the
sig
and
those
you
know
we
can.
There
can
be
other
priorities,
I
don't
know,
but
the
the
first
big
thing
is
finish:
consolidation,
information,
consolidation
to
the
website
so
have
open,
telemetry
io,
be
kind
of
source
of
truth.
D
Hopefully
start
delivering
them
next
week
is
one:
is
a
an
overhaul
of
the
status
page
worked
with
josh
cereth
from
google
to
to
do
a
like
a
survey
of
all
the
maintainers
and
get
like
detailed
status
information
from
other
projects
and
have
like
just
kind
of
a
better
more
table
based
way
of
displaying
it
on
the
website.
So
hopefully,
that
page
will
become
a
lot
more
useful,
and
at
that
point
it
would
be
great
to
to
put
it
more.
D
Nice
and
then
the
the
other
thing
I'm
working
on
right
now
is
adding
the
open
tracing
migration
documentation.
D
This
is
a
thing
we
haven't
been
getting
like
a
huge
file
request
from
users,
possibly
because
they
don't
know
it's
even
a
thing,
but
the
cncf
has
it
as
like
a
requirement
from
from
them
as
part
of
trying
to
archive
the
open
tracing
project.
One
of
the
requirements
is
just
making
sure
all
that
information's
on
available
here
and
on
the
open
tracing
side
about
about
how
to
migrate
over
token
telemetry.
So
for
that
reason,
it's
it's
a
priority
to
me
to
get
at
right
now.
D
C
Is
already
on
there
open
tracing
sunset
punch
list
stuff,
anyone
else
have
any
big
things
that
isn't
kind
of
on
that
list.
I
know
philip
there's
the
ongoing
docs
doc
extravaganza.
E
Yeah
plenty
more
of
that.
Another
thing
is
so
on
the
honeycomb
side
is
we
have
a
docs
contractor
who
we
are
going
to
start
working
with
and
basically
with
their
their
thing
is
like
hey.
E
We
have
the
subject
matter:
experts
around
open
telemetry,
let's
like
interview
typical
tech,
doc,
stuff
like
interview
them,
gather
the
right
kind
of
stuff
and
then
start
making
docs
contributions,
and
so
the
big
question
right
now
is
a
matter
of
ordering,
because
we
think
that
all
any,
for
example,
like
there's
a
big
conceptual
docs
guidance
about
like
what
what
is
a
span.
E
What
is
a
span
event
like
generally
speaking,
language
agnostic,
and
we
don't
want
to
like
host
that
on
the
honeycomb
docs
site,
unless
it's
just
like
as
a
short
term,
just
get
the
stuff
written
and
get
it
published
sort
of
things
so
that
we
could,
then
you
know,
figure
out
a
way
to
migrate
it
to
upstream.
So
what
that'll
probably
be
like
a
top
question
that
they're
gonna
have
about
like
hey
in
a
week's
time?
I'm
gonna
start
writing
stuff.
E
Should
that
go
upstream,
or
should
that
go
on
honeycomb
assets
for
now
until
it
can
be
made
upstream,
and
so
if,
like,
I
think,
I
guess
my
question
is
like
if
another
person
just
starts
throwing
a
lot
of
docs
at
this
repo
in
a
short
period
of
time,
are
we
okay
with
that
or
do
we
want
to
like
hold
off
and
do
something
else.
C
D
Yeah,
I
I'm
definitely
pro
like
get
it
up
there
and
then
continue
to
edit
it
yeah.
D
C
Big
kind
of
like
competing
like
organizational
or
you
know
if
it's
like,
oh,
we
want
to
take
if
they
want
to
take
like
an
entire
existing
page
and
say
like
okay,
we're
gonna
black
that
and
replace
it
with
three
as
long.
You
know
that
might
take
a
little
more
review
time,
but
I'm
generally
okay.
I
would
prefer
for
them
just
to
put
it
on
the
hotel
site
and
let
you
know
be
done
with
it,
because
the
more
we're
committing
straight
to
hotel,
there's
kind
of
a
bias
to
action.
E
I
agree
and-
and
I'm
also
just
going
to
bias
towards
getting
new
content
written
like
refactoring
existing
content.
Yeah,
that's
like
people
always
want
to
reorganize
stuff,
and
it's
like
okay,
we
can.
We
can
do
that
later.
Yeah.
C
I
do
want
to
make
sure
that
we're
not
we
will,
if
they're,
replacing
pages
that
might
be
linked
to
already.
Then
we
need
to
be
a
little
cautious
with
that,
so
that
existing
links
from
like
you
know,
downstream,
don't
don't
break
so
either
from
other
docs
or
from
like
vendors
or
whoever
that
have
blogged
about
this.
Although
I
know
like
I
was
talking
to
someone
at
lights,
I
was
helping
someone
with
a
collector
plug-in
development
yesterday
and
like
their
big
complaint,
was
oh
no.
C
I
think
that's
just
going
to
be
an
ongoing
problem,
but
yeah.
Let
me
know
when
they're
going
to
be
doing
it
and
I
will
or
when
they
start
and
or
when
they
start
want
to
start
committing.
Then
I
will
make
myself
like
some
dedicated
review
time
every
day.
A
I
have
a
related
question
for
which
I'd
like
feedback
from
ted
and
austin
about
this:
how
much
review,
assuming
there's
a
sizable
volume
of
new
content?
How
much
of
that
do
you
want
reviewed
from
a
tech
writer's
perspective?
How
much
should
that
be
gaining?
A
You
know
tech
writer
issues
aside,
maybe
aside
from
what
philip
and
I
did,
which
was
in
the
initial
few
commits,
you
know,
I
would
say,
oh
by
the
way
the
convention
is
to
do,
you
know
not
have
a
manual
table
of
contents.
Do
links
this
way.
So,
aside
from
that,
are
you
kind
of
okay
with
let's
try
and
commit
things
as
quickly
as
possible
and
then
we'll
review
if,
if
necessary,.
C
Yeah,
I
would
prefer
like
maybe
for
the
first
ones,
if
we
could
have
that
kind.
You
know
if
we
could
get
the
the
tiki
tacky
detail
stuff
like
how
you
know
the
links,
the
toc.
You
know
stuff
like
that,
okay
done
or
consistent,
and
then
I
mean
personally,
like
I
read
through
everything
that
gets
submitted
just
to
kind
of
pass.
C
The
sniff
test,
at
least
like
the
only
stuff
I
go
like
deep
in
on,
is
stuff
that
I
personally
like
recognize
or
I'm
familiar
with,
but
I
really
don't
want
us
to
be
in
a
situation
where
every
single
language
maintainer,
you
know
where
we're
blocking
blocking
stuff,
because
it's
like
we
need
a
java
contrib
to
get
in
here
and
read
it
right.
We
have
to
kind
of
trust
the
tech
writers
to
be
basically
competent
at
tech
writing.
D
C
B
D
You
know
posting
things
is
better
than
than
not
posting
them,
even
even
if
we
haven't
verified
that
everything
in
them
is
100,
accurate,
someone's.
C
C
I
am
100
supportive
of
that.
The
other
other
thing
that
is
maybe
less
of
a
website
thing
is
I'm
also
going
to
be
working
to
kind
of
one
thing
we've
identified
is
like
a
problem
is.
C
Where
is
this
is
why
this
is
part
of
why,
like
moving
the
blog
to
the
website,
is
important,
is
there's
kind
of
a
a
general
lack
of
like?
C
Where
do
you
go
to
find
new,
find
out
stuff
like
there's,
not
an
authoritative
source
for
like
information
about
hotel,
so
to
kind
of
help
combat
or
to
help
with
that
we're
going
to
be
investing
a
little
time
into
one
this
website,
the
website
stuff
will
help
with
this,
obviously
to
open
telemetry
tuesday,
making
that
a
little
bit
more
of
a
formal
thing
and
more
of
a
format
to
that.
C
So
if
anyone
wants
to
get
involved
with
that,
let
me
know,
and
then
hopefully,
at
some
point
we'll
have
once
we
kind
of
get
all
this
stuff
nailed
down
then
week
you
know
monthly
kind
of
status,
reports
or
newsletters
or
something
you
know
some
sort
of
like
at
a
regular
cadence
like
hey
here's
project
status
for
may
here's
process
for
june
here's
products,
project
status
for
blah,
blah
blah
blah
and
have
that
be
something
that
we
produce
out
of
this
sig.
C
D
Yeah,
so
this
this
came
out
of
the
gc
meeting
that
I
was
just
in,
so
I
would
say
backing
up.
The
the
general
request
is
that
the
registry
is
naturally
kind
of
out
of
date,
because
a
whole
bunch
of
stuff
has
been
added
to
open
telemetry
as
far
as
integrations
go,
but,
of
course,
lots
of
those
people
don't
know
or
bother
to
go.
Add
it
to
the
registry,
so
there
was
kind
of
a
request
of
like.
Is
there
a
way
to
make
it
simpler
to
add
things
to
the
registry?
D
So
I
wanted
to
just
see
if
there
were,
if
people
here
had
any
ideas,
it's
not
actually
clear
to
me
whether,
like
one
of
the
things
that
was
proposed
was
like,
if
you
could
just
add,
like
a
you,
know,
a
tag
to
your
repo
on
github
and
then
put
the
markdown
file
over
there
somewhere.
Could
we
then
scan
github
for
those
things?
D
Would
that
actually
make
life
easier?
The
flip
side
of
that
is
that
opens
the
repo
up
to
spam.
D
D
I
wanted
to
bring
it
up
here
see
if
there
is
actually
something
we
could
do
to
make
the
registry
more
useful.
C
Every
time
this
comes
up,
I
mean
you've
identified.
The
thing
is
that
if
we
make
it
any
the
the
any
more
automation
makes
it
more
vulnerable
to
unwanted
things
and
remove
one
it
we
haven't.
You
know
it
removes
a
quality
control
gate
to.
It
still
requires
affirmative
participation
by
a
like
maintainer
or
by
like
a
contributor.
C
A
Do
we
know
the
extent
to
which
the
registry
is
actually
being
used
and
how
helpful
it
is
because
it
would
require
it's
something
I
looked
at
and
chose
not
to
touch,
because
it
would
require
rework.
But
if
folks
aren't
consulting
it
that
much,
it
may
be
a
quite
a
low
priority
thing.
A
So
go
ahead,
the
other
suggestion
I
was
going
to
make
was:
we
could
keep
the
current
setup,
but
we
could
mark
entries
outdated
after
a
period
and
that
could
be
automated
and
that
would
be
easy
to
automate
on
the
website
and
it
would
be
the
author's
responsibility
to
come
back
and
say
no,
no,
we're
we're
actually
compatible
with
version
whatever
or
so
that
would
be
a
suggestion.
C
Yeah
just
some
data
real
quick
last
30
days.
The
registry
has
about
4
000
or
3
500,
uniques
average
time
page
of
about
a
minute
30.
C
C
You
know
as
a
comparative
point
over
the
same
time
frame
like
the
docs
page
gets
about.
Eight
percent
of
uniques,
like
just
the
docs
landing
page
collector
getting
started,
is
about
four
and
a
half
for
four
and
a
quarter
percent.
So
it's
you
know,
people
are
using
it.
Would
they
use
it
more
if
it
was
better?
Probably.
D
D
Wasn't
there
and
just
in
general,
there's
a
there's
a
discover
to
put
it
another
way.
There
is
a
discoverability
issue
with
open
telemetry,
which
is
in
order
for
it
to
work
really
well.
You
do
have
to
install
all
the
integrations,
some
of
those
like
the
ones
that
are
like
plugins
for
your
app
things
could
definitely
be
improved
as
far
as
automation
for
those
specific
languages
around
discovering
those
plugins
and
doing
it
for
you,
but
then
there's
also
stuff,
like
lambda
integration
or
like
other
kind
of
cloud
provider.
E
D
We
could,
I
think,
there's
I'm
sure,
there's
probably
ways
we
could
make
the
registry
as
like
an
interface
or
a
display,
more
useful
for
discovery
purposes,
but
the
the
real
low-hanging
fruit
right
now,
there's
just
a
bunch
of
stuff-
that's
not
listed
in
it,
and
so
actually,
just
just
like
a
registry
as
we
have
it
now
that
has
everything
in
it
is
a
useful
resource,
but
registry,
as
we
have
it
now,
that's
actually
missing.
A
big
chunk
of
stuff
is
almost
like
an
anti-pattern
right
right,
because.
E
D
It's
going
to
you're
going
to
get
a
bunch
of
false
negatives,
which
is
the
thing
we
want
to
avoid
and
we're
not
sorry.
I
just
want
to
say
one
other
thing:
we're
not
also
just
we're
not
getting
feedback
that
the
problem
is
there's
a
bunch
of
outdated
stuff
in
the
registry
like
something
got
added
there,
but
now
it
got
moved
and
it
doesn't
exist
anymore
or
something.
D
D
D
D
To
work,
there's
no
escaping
that,
so
I
don't
think
we
actually
need
to
change
how
it
currently
works.
Basically,
I
don't.
D
A
Yeah
I
I
noted
in
the
meeting
minutes
that
the
the
most
most
important
point
you
mentioned
was
that
items
are
missing
and
that
led
me
to
the
question.
Well,
could
we
just
play
catch
up
for
a
little
bit
and
add
those
items
who
should
be
responsible
for
adding
those
items?
Should
it
be
us
should
it
be?
A
Should
we
be
pinging
other
contributors
and
so
two
things
one
is:
can
we
catch
up
quickly
to
make
the
website
be
more
valuable
to
folks
in
the
short
term
and
then
longer
term
is
then
we
could
discuss
process
but
ted?
I'm
glad
that
you
said
that
probably
what
we
have
now
is
is
good
enough.
We
yeah
more
importantly,
need
to
add
some
items.
C
As
the
person
that
has
done
the
ketchup
in
the
past,
I
respectfully
don't
want
to
do
the
ketchup
anymore,
because
it's
a
frustrating
process.
One
thing
that
maybe
I
like
ted's
suggestion
or
you
the
idea
you
had
is:
is
there
a
way
we
can
make
it
easier
yeah?
C
Because
I
do
think
that
one
of
the
challenges,
one
of
the
the
a
significant
challenge,
both
with
ketchup
and
also
with
just
net
new
and
also
modification
stuff,
is
that
it's
a
single
markdown
file
that
is
90
boilerplate
and
we
don't
use
all
the
fields
in
it.
So
it
might
be
worthwhile
to
take
a
look
at
how
we
generate
all
that
and,
like
I
don't
know,
if
the
answer
is.
D
D
You
know
clone
the
repo
fork,
the
repo
add
a
version
of
this
template
file
to
this
directory.
I
don't
know
how
much
more
we
could
automate
that
for
people
right
yeah,
but
but
that's
that's
literally
the
the
long
and
the
short
of
it.
We
could
paste
the
contents
of
that
template
file
into
the
instructions
right
there.
It
says
just
copy
paste
this
into
a.
C
A
Sorry
so
austin
you
were
saying
I'm
coming
back
to.
We
could
make
things
as
easy,
as
almost
you
know,
clicking
a
single
button,
but
somebody
has
to
click
that
button.
So
I'm
coming
back
to
the
question
somebody
with
domain
knowledge,
who
knows
what
needs
to
be
added
and
that
could
be
multiple
individuals.
A
D
The
advantage
is,
it
can
be
with
our
current
model.
Is
it
can
be
anyone?
You
don't
need
to
have
github
permissions
on
a
repo
to
do
this
right?
You
just
need
to
make
a
pr
against
ours,
so
it's
really
just
advertising
like
going
to
slack
going
to
the
maintainer
sig
and
other
cigs
asking
people
there
to
do
it
going
to
twitter
and
saying
like
when
I
help
the
project
out
like
help
update
our
registry.
If
you
know
something's
missing,
just
fill
it
in
please.
C
I
I
actually
think
that's
the
answer
right.
There
is
just
having
a
coordinated
like
let's,
let's
take
another,
let's
write
something
up:
okay,
let's
write
up
just
a
a
post
or
some
just
some
really
simple
documentation
like
one
something.
That's
like
one
click
and
you
click
on
this,
and
it
shows
you
whole
thing
top
to
bottom
and
then
we'll
publish
that
to
medium
or
wherever,
we'll
put
it
on
the
blog,
the
website
blog
and
then
we'll
go
into
slack.
We'll
go
go
to
twit.
C
F
A
I
would
mention
the
blog
only
because
you
brought
it
up
earlier.
I
again,
I
haven't
I'm
just
back
so
and
I
haven't
reviewed
the
the
items
for
this
quarter,
but
since
you
mentioned
the
blog,
how
important
do
you
feel
it
would
be
either
in
this
quarter
or
the
next
quarter
to
bring
the
blog
to
the
website.
C
C
The
longer
we
go
or
where
the
website
isn't
like
a
source
of
truth
like
where
open2io
is
not
like
the
source
of
truth,
then
you
know
the
more
alternate
channels
pop
up
weird,
the
more
like
alternate
channels
and
alternate
ways
for
this
stuff
to
get
communicated
right.
So
I
think
especially
as
we
get
to,
I
think
this
whole
registry
thing
is
a
great
example.
C
If
we
had
you
know,
if
the
blog
existed
and
was
like
easier
to
add
stuff
to
and
sort
of
stuff
went,
then
we
could,
you
know
tomorrow,
go
out
and
put
a
blog
post
up.
That
says:
hey
do
you
want
like
an
atta
boy,
then
go
do
this
registry
stuff
people
right
and
then
everyone
could
tweet
about
it,
and
you
know
you
know
where
it
was
and
we
could
ought
to.
Even
you
know
we
could
do
like
yeah.
A
new
thing
appeared
on
the
blog
and
it's
automatically
tweeted.
I
don't
know,
I
don't.
C
You
know
more
docs
more
good,
but
the
status
page
stuff
is
what
but
that's
mostly
kind
of
being
handled
right,
ted.
D
Yeah
yeah
the
status
page
stuff
chef
pr
coming
in
a
couple
days:
yeah.
A
D
A
C
Think
that
part's
less
complicated
just
because
I'm
pretty
sure
the
what
I
think
I
mean
ted,
you
can
tell
me
if
I'm
wrong
the
requirements
for
like
steering
or
for
the
gc
to
go,
for
this
would
be
like
what
migration
of
old
posts
like.
Would
they
care
about
that.
A
C
C
D
D
B
D
Then
people
there
provide
feedback
and
then
it
somebody
with
medium
permissions.
You
know
approves
it
so
just
the
people
who
look
at
that
like
so
basically
the
comms
mailing
list
needs
to
be
updated.
Saying
like
hey
everyone
here
who
likes
to
review
these
things,
you
need
to
now
pay
attention
to
our.
You
know:
github
prs,
basically
on
this
repo
right,
so.
C
D
C
D
C
D
D
C
D
But
I
don't
think
we
need
approval
from
anyone
to
go
ahead
and
make
this
change
like.
Let's.
C
C
Then,
let's
yeah,
let's
patrice
we'll
async
figure
it
out
on
the
actual
date.
But
let's
work
on
that.
After
whenever
we're,
probably
starting
next
week,
we'll
figure
out
what
we
need
to
do
and
get
it
done.
C
Okay
well,
exciting
year,
ahead
of
us,
oh
and
I'm
always
on
slack,
we're
all
always
on
slack.
So
if
you
all
need
anything
ping
me
and
other
than
that,.
B
C
I
can
just
make
channels
in
the
cncf
select
cool,
so
now
there
is
hotel
comms.
I
will
put
that
in
the
notes
feel
free
to
join.
D
C
D
It
does
not
look
like
it
is
in
the
list
of
special
interest
groups.
The
website
on
the
website
on
sorry
on
the
on
the
community
read
me
so.
F
C
Well,
I
will
I
can.
I
can
update
this
and
also
add
a
link
to
our
slack
channel.
A
Ted,
I
have
a
question
for
you
sure
sure,
for
the
open,
tracing
migration
and
archiving
that's
so
I
heard
you're
you're
working
on
that.
F
A
Again,
offering
my
help,
if
you
need
help
archiving
the
old
site
or
yes,
I
would
love
if.
D
So
I
think
the
first
order
of
business
is
just
to
get
the
docs
up
here
right.
So
then
we
have
something
to
point
people
at
and
then
yes
going
into
the
old
website
and
just
seeing
what
we
need
to
update
like
there's
a
little
banner
there.
That
could
be
updated,
but
we
might
want
to
add
a
page
to
that
site
as
well
about
migration
path.
D
And
then
we
need
to
go
into
like
basically
do
a
pass
to
like
every
github
readme
major
github
readme
in
the
opentracing.org.
D
D
D
Should
it
be
yeah
suggesting
that
it
be
a
top
level
section
under
docs,
because
it
seems
it
seems
different
enough
from
everything
else
that
it
would
deserve
that.
But
I
don't
know
if
you
you
have
thoughts
otherwise,.
A
What
I've
seen
other
websites
do
is
that's
what
the
blog
is
for,
because
eventually
this
becomes
outdated
right.
It
becomes
no
longer
relevant.
Think
in
a
year
two
three
five
years.
How
important
is
that
migration?
Well
at
some
point,
no
matter
how
many
years
it'll
become
less
important.
So
if
the
blog
were
on
the
website,
then
you
could
have
a
blog
entry,
which
is
here's.
The
migration
guide.
D
Just
a
suggestion
I
mean,
I
think,
that
just
for
practical
purposes,
the
cncf
needs
to
see
it
in
our
docs,
and
it
is
a
semi-permanent
feature,
though
I
agree
like
as
time
goes
on,
people
will
care
less
about
it,
but
we
should
also
make
a
blog
post
when
we
add
it.
D
C
D
D
That's
just
like
open
tracing
migration,
which
explains
in
general
what
you
can
expect
and
in
general,
how
it's
expected
to
work,
because
there's
kind
of
like
a
general
version
of
this
and
then
it
would
be
nice
to
then
link
to
for
all
the
languages
that
have
this
currently
to
the
docs
for
how
to
do
it
in
that
language,
and
so
there's
like
a
part
two
of
like
rustle
up
all
of
those
stocks
and
maybe
add
them
to
the
website
as
well
as
like
headers.
C
Well,
it
depends
so
if
this
was
in
a
book,
this
would
be
an
appendix
right.
So
I.
A
I'd
like
to
point
out
that,
regardless
of
where
it
ends
up,
we
can
make
it
prominent
on
the
home
page.
We
can
make
a
banner
that
shows
up
on
the
homepage.
We
can
make
a
banner
that
shows
up
in
any
subsection
or
wherever,
and
I'd
also
like
to
point
out
that,
no
matter
where
we
decide
to
put
it
today,
we
can
always
change
it
tomorrow.
Next.
C
D
I
would
the
only
reason
I
would
like
it
to
be
top
level
for
now,
and
I
agree
we
could
like
in
a
year
or
something
shove
it
under.
Something
else
is
it.
There
does
appear
to
be
like
a
discovery
issue
about
the
concept
that
for
one,
though
cncf
would
probably
be
happier
to
see
it
like.
D
I
don't
want
them
to
come
back
to
me
and
say,
like
I
looked
for
it,
I
didn't
find
it
because
I
didn't
think
to
like
dig
around
under
the
menus
and
also
it
seems
like
like
end
users
do
not
automatically
know
that
this
is
a
migration
path
available
to
them,
and
so
it
might,
it
might
actually
help
people
when
they
go.
Look
at
our
docs
to
see
that
this
is
a.
This
concept
exists.
A
D
It
was
before
at
some
point.
Hopefully
there
is
also
an
open
census,
migration
thing
and
because
they
need
to
do
that
because
they
said
they
would
and
so
then
it
could
turn
into
like
a
top-level
thing.
That's
like
migrations
or
then
we
at
some
later
date.
We
just
shovel
it
all
under
reference.
A
How
about
this
creating
the
top
level
migration
entry
and,
for
starters,
the
content
will
be
migration
of
open
tracing
and
later
it
will
become
a
section
landing
page
with
the
two
sub
pages.
How
does
that
sound.
D
Yeah
there's
also,
I
mean
I
would
actually
be
the
interesting
thing
about
having
migrations
is.
There
is
also
a
a
thing
I
do
talk
about
and
have
content
about
and
could
write
up
that
people
have
found
genuinely
helpful,
which
is
like
how
to
adopt
open
telemetry,
and
so
there
is
this,
like
general
purpose,
migration
guide
of
like
all
right.
I
want
to
get
lifted
up
onto
this
thing
off
of
whatever
I'm
currently
using.
That
involves
like
well
step
one.
D
You
know
you
can
start
sending
the
data
off
to
other
yada
yada
that
explaining
to
people
how
they
can
progressively
migrate
is
like
been
very
helpful
to
people
to
learn
that
it's
not
like
an
all
or
nothing
transition.
I
have
to
do
or
you
know
I
have
like
data
breaks
or
something
so
so
maybe
it's
actually
three
migration
guides.
We
have
have
it
there.
C
So
my
only
point
to
that
is:
are
we
sh?
How
confident
are
we
that
migrations,
as
a
top
level
topic,
is
clear
to
our
audience
like,
given
the
other
top
level
items
we
have
like?
Is
someone
gonna.
C
The
hypothetical
example
I
use
is
that
whenever
someone
on
hacker
news
posts
about
open,
telemetry,
there's
like
inevitably
a
bunch
of
people
that
start
screaming
about
privacy
right
because
they
think
it
means
like
user
telemetry.
So
with
that
in
mind,
like
is
my
migrations,
the
right
top
level
thing
for
this.
It
might
be
patrice.
A
That's
a
good
question.
I
had
raised
my
hand
because
I
I
wanted
to
see
if
I
understood
well
what
ted
was
saying,
which
is
possibly
an
argument
in
favor
of
having
a
top
level
migration
section
to
right
from
the
start,
even
though
it
could
contain
it
will
contain
one
entry
for
now.
D
Because
we're
saying
I
could
actually
add
two
pages
to
that
to
get
started.
One
is
specifically:
how
do
you
migrate
from
open
tracing
because
the
answer
there
is,
you
don't
have
to
actually
even
change
your
instrumentation
like
boom
and
then
there's
this
general
migration
of
I've
already
instrumented
my
system
with
blah,
and
now
I
want
to
switch
to
open
telemetry
instrumentation.
D
But
that
means
like
I
have
this
whole
prior
pipeline.
How
do
I
do
that
without
without
having
downtime
or
breaking
things,
and
we
actually
do?
I
do
have
a
migration
guide
for
people
in
that
scenario,
so
so
that
would
be
another
page
to
to
have
there
and
then,
hopefully,
eventually,
there
is
also
an
open
census.
Migration
guide
that
goes
there.
C
C
A
lot
of
vendor
specific
or
point
solutions,
or
even
stuff
like
like
micrometer
or
I
don't
know,
there's
40
billion
things.
Okay,
I.
C
C
C
Yeah,
I
think
good
we
got
to
start
somewhere.
Let's
start
there
top
level
migration
section
and
the
the
the
section
section
index
is
basically
like
hey.
These
are
guides
on
how
to
migrate
from
some
non-open
telemetry
technology,
to
open
telemetry
technology
to
open
telemetry
and
then
we'll
start
with
the
open
tracing
guide.
Ted
can
move
you
can
we
can
take
some
of
your
stuff
and
put
it
in
there
like
cool,
that's
something
that
I
think
also
we
can
socialize
to
our
vendor
partners,
our
lovely
vendor
partners
and
see
if
they
want
to.
C
C
Less
but
more
like,
let's
focus
on
you
know
a
couple
of
big.
You
know
a
couple
of
punchy
things
rather
than
trying
to
spread
ourselves
out
and
satisfy
every
single
person
like.
I
think
that's
what
you
know
like.
Why
have
the
documentation
stuff
been
the
way
it
is
for
so
long
because
we've
been
having
you
know,
we've
had
a
lot
of
stakeholders
and
trying
to
make
everyone
happy
and
ain't.
Nobody
turned
out
happy.
So
let's
be
more
assertive
about
stuff.
A
Okay
thanks:
well,
that's
it
for
me
and
I've.
I've
added
quite
a
bit
of
notes
to
the.
A
And
I'll
I'll
follow
through
with
creating
issues
as
as
needed
and
ted
being
me
somehow,
when
you
add
the
content
or
whenever
you'd
like
some
feedback.