►
From YouTube: 2022-03-17 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
A
I
am
portland
oregon.
How
about
you.
B
It's
just
south
south
of
take
the
front,
the
french
map
and
you
take
the
south
part,
which
is,
from
my
perspective,
the
most
beautiful
part
of
friends.
But
again,
this
is
not
objective
at
all.
A
All
right,
I
say
we
go
ahead
and
get
started
excellent.
So
the
only
thing
I've
got
on
the
agenda
today
is
to
review
work
from
last
week
and
one
of
the
pieces
is
the
community
survey
strategy
document,
and
so,
if
you
haven't
had
a
chance,
we
can
pull
it
up
and
review
it.
A
I
think,
if
you
have
comments
about
the
content,
let's
chat
about
that,
but
I
think
it
would
be
if
nothing
else
on
the
agenda
today,
we
can
do
a
little
bit
of
thinking
about
that
quarterly
feedback
survey
and
what
are
those
trendable
data
points
that
we
want
to
try
to
check
in
with
four
times
a
year?
A
B
A
Well,
if
there's
anything
that
catches
anyone's
interest,
we
can
look
at
it.
I
think
maybe
just
like
we
can
start
by
talking
about
the
philosophy
of
surveys
and
does
it
make
sense
to
have
a
recurring
survey
and
for
recurring
surveys,
my
intent,
there
is
that's,
probably
survey
one
out
of
out
of
the
list
of
options
there
so.
B
B
I
think
it
would
be
interesting
to
see
skill
to
figure
out
what
were
their
approach
did
their
manly
used,
automated
instrumentation
or
or
or
they
basically
jump
into
direct
manual
because
they
didn't
get
the
details.
I
mean
that
would
be
a
way
for
us
to
see
if
we
need
to
do
any
actions
on
this
so,
but
I'm
not
sure
if
it's
that
it
will
be
the
first
survey.
A
So,
at
least
from
my
perspective,
I
think
it's
we
will
have
multiple
surveys.
Some
of
them
will
be
like
this
question.
One
that
are
are
not
deep.
They
ask
some
high
level
questions
that
we
can
trend
over
time
versus
more
like
specific
type
surveys
that
maybe,
for
example,
go
into
the
getting
started
experience.
A
And
so,
if
you
remember
the
survey
from
last
year
like
it
can
be
a
funnel
from
a
here's,
a
high
level,
please
engage
with
us,
but
if
you,
what
are
the
most
important
things
that
we
want
to
capture
if
we
only
get
an
end
user's
attention
for
five
minutes
and
that
getting
started
survey,
I
don't
think,
is
accessible
in
five
minutes
type
time
frame.
So
this
really
that
survey
number
one
that
I
threw
out.
There
was
intended
to
be
kind
of
high
level,
but
we
can
totally
ask
that
might
be.
A
One
of
the
things
that
we
want
to
trend
over
time
is
what
is
the
percentage
of
users
who
are
using
automatic
instrumentation
capabilities
versus
custom
instrumentation
capabilities,
because
I
don't
know
my
hypothesis
is
this
once
open
telemetry
graduates
and
it
becomes
a
much
more
widely
adopted
technology
that
that
trend
towards
automatic
instrumentation
is
going
to
just
accelerate
and
if
it
doesn't,
is
there
any
action
that
we
can
take
about
if
we
learn
that
the
acceleration
isn't
happening,
and
so
I
guess
that's
the
question
of
like
philosophically.
A
What
do
we
want
to
know
in
two
years
from
now
and
wish
that
we
would
have
theta
from
two
years
ago
to
back
up
any
type
of
prioritization
that
we
do
so
for
those
of
you
who've
been
in
the
project
longer?
How
would
you
answer
that
question?
What
did
you
wish
you
knew
from
two
years
ago
today.
C
Well,
it's
kind
of
funny
it's
a
little
different
in
the
past
than
going
forwards,
because
in
the
past
it
would
have
been.
How
long
is
it
gonna
take
to
to
get
traces
and
metrics
and
logs
at
the
door,
but
yeah,
I
would
say
one
of
the
the
big
things
we
want
to
know
about
is
installation,
time
and
success
rate.
C
Slash
like
frustration
right
like
when
people
try
to
install
open
telemetry.
Does
that
feel
like
a
smooth
like
happy
experience,
or
is
that,
like
a
frustrating,
confusing
experience,
I
would
say:
that's
that's
like
to
me
besides
it
it
just
like
working
correctly.
C
C
Yeah,
the
the
second
one
that
I
think
is
really
important
is
how
satisfied
people
are
with
the
quality
of
the
instrumentation
that
we
provide
so
assuming
they
get
it
all
set
up
properly
like
out
of
the
box.
Are
they
they
satisfied
with
the
the
data
that
open
telemetry
gives
them
without
them
having
to
write,
write
any
further
instrumentation.
A
A
C
Getting
that
would
be,
my
hope
is
that
it
it
generally.
The
only
reason
I
would
see
it
going
down
is,
if
there's
other
stuff
out
there,
that
they
might
be
coming
from
or
using.
That's
also
continuing
to
improve.
A
B
B
And
then
you
look
at
what
they're
they're
what
you
get
out
of
the
automated
instrumentation
and
then
you
say,
and
then
you
start
doing
manual
stuff
and-
and
I
think
that's
that
having
that
to
figure
out
if
they
have
enough
information
produced
from
those
measurements
to
help
them
to
troubleshoot
or
to
understand
or
to
that
would
be
very
interesting.
So
to
know
how
how
deep
the
measurements
that
are
produced
by
the
automated
instrumentation
library
could
be
reliable
for
for
production
use
cases.
C
Yeah
yeah,
like
one
like
stated
goal,
or
at
least
I
hope
it's
stated
but
like
intended
goal
for
open
telemetry-
is
that,
assuming
that
your
services
are
built
out
of
stock,
open
source
components,
in
other
words,
it's
not
just
some
bespoke
system,
which,
obviously
you
know
you're
going
to
have
to
instrument
yourself,
but
that
out
of
the
box,
assuming
you're,
building
your
stuff
out
of
web
frameworks
and
database
clients
and
stuff
the
instrumentation
we're
providing
is
sufficient
for
you
to
roll
into
production.
C
So
it's
just
not
there
and
the
other
is
it's
there.
But
what
they're
getting
out
of
that
instrumentation
is
is
not
what
they're
used
to,
and
this
is
usually
people
coming
from
some
other
system
because
they're
like
hey,
I
was
using
brand
x
and
I
was
getting
more
detail
or
or
something
about
the
instrumentation
I
got
from
that.
Other
system
was
was
better
than
the
instrumentation
that
that
I'm
getting
here.
C
B
I
hadn't,
I
think,
that's
a
great
point,
but
I
was
also
maybe
that's
another
and
I
don't
know
I'm
just
sharing
my
thoughts
there,
because
now
you're,
focusing
on
how
how
relevant
those
data
we
produce
are
for
the
users,
but
also
maybe
there
would
be
some
feedback.
That
could
be
very
useful
for
us
to
say.
Oh
I've
been
using
the
wrong
samplers
or
the
wrong
span
processor,
and
it's
been
it's
been
too
hard
to
maintain.
B
I
had
to
deploy,
I
don't
know
more
collectors
or
my
storage
just
exploded,
so
that
there
could
be
also
a
way
of
helping
us
to
sort
of
educate
the
community
on
which
type
of
samplers
and
and
process
spam
processor
they
should
use
to
to
to.
I
mean
to
manage
the
storage.
C
That
and
that
brings
up
actually
a
place
where
there's
maybe
a
split
in
audience
here.
Maybe
it
could
all
be
in
the
same
questionnaire,
but
there's
the
developer
experience,
which
is
usually
centered
on
installing
this
stuff
and
standing
it
up.
There's
the
the
operator
experience
of
like
what
is
it
like
to
run
open
telemetry
in
production?
Yeah
is
the
overhead
from
open,
telemetry
unacceptable?
Is
it
like
confusing
yeah
like?
C
B
A
B
A
Kind
of
like
how
you
break
that
down
developer
experience,
one
when
you're
talking
about
that.
I'm
thinking
my
mental
map.
There
was
like
the
life
cycle
of
open,
telemetry,
the
install
config
and
then
the
generating
data
part,
and
then
the
processing
and
shipping
data
off,
like
those
three
main
facets
of
an
end,
user's
experience.
C
A
I
think
they're,
all
they're,
all
really
important
right
and
right
now
I'd
say
we're
trying
to
definitely
optimize
that
installation
and
configuration
of
like
just
getting
started
yeah,
but
over
the
course
of
time
we
may,
as
a
community,
start
working
to
offer
up
optimize
the
running
and
the
maintaining
the
upgrade
cycles.
The
those
long
term
costs,
but
we
know
customers
are
using
and
experiencing
those
already
today,
yeah
and
users
yeah.
C
C
You
know
across
their
fleet
of
stuff,
and
they
have
like
a
kind
of
like
one
big
push
to
try
to
do
that
or
it
has
to
kind
of
go
like
team
to
team
and
each
team
kind
of
has
a
push
to
do
it,
and
so
there's
a
moment
where
they've
like
done
that
push
and
you
kind
of
want
to
know
how
did
that
feel
and
then
there's
the
kind
of
like
ongoing
after
that
it
switches
into
more
this
like
operation
operating
open
telemetry
is
the
kind
of
like
ongoing
experience
of
like
running
the
collectors
and
looking
at
the
data.
B
I
was
thinking,
maybe
also
question
about
maintenance
or
update,
so.
A
B
Made
the
installation
to
configure
everything
and
then
suddenly
I
need.
I
have
a
new
feature,
I'm
going
to
say
I'm
I'm
changing
version
of
whatever
framework
and
bom.
I
got
a
problem
because
the
release
of
my
this
doesn't
work
or
yeah.
That
could
be
also
a
very
good
indicator
and
experiments
as
well.
C
Yeah
yeah
ongoing
dependency
management.
We
care
quite
a
bit
about
backwards
compatibility
for
that
reason
like
we
don't
want
open,
telemetry
to
ever
be
the
the
dependency
that's
causing
some
dependency
conflict
where
they're
getting
stuck
somewhere
yeah,
but
maybe
a
way
this
is
pointing
to
is
it's
sort
of
like
almost
like
two
surveys.
There's
the
one
survey
around
that
installation
experience
that
that
people
kind
of
do
once
and
then
there's
all
this
stuff
that
you
could
keep
going
back
to
the
same
people
right
like
quarter
after
quarter,
and
it's
about
yeah.
C
This
like
upgrade
and
maintainability,
and
operating
and
and
data
quality
and
stuff
like
that,
and
I
say
it
might
be
worthwhile
to
separate
it
out
just
because
one
of
the
feedbacks
we
had
was
like
when
you
jam
all
of
this
together
into
one
too
much
big
survey.
It's
like
too
much.
A
Yeah,
I
completely
agree
just
from
a
usability
of
a
survey
standpoint.
I'm
I'm
wondering
right
now
is
if,
like
that,
five
minute
survey
right
five
minutes
to
joy,
but
the
five
minute
survey
to
joy
can
we
potentially
identify
like
a
funnel
of
people
to
dig
into
with
and
send
them
that
second
survey?
That's
like!
Oh
your
operator
experience
wasn't
so
good.
Can
we
give
you
a
whole
survey
just
about
this
piece?
Maybe
that's
another
way
to
look
at
this
high
level.
B
So
maybe
we
can
have
questions
initially
to
identify
which
personas
yeah
saying:
were
you
the
one
installing
or
configuring,
or
are
you
the
one
consuming
or
are
you
so
then
that
could
help
us
to
find
to
then
provide
the
right?
Second
survey.
C
C
B
Maybe
also
the
the
level
of
experience
and
say
how
long
have
you
been
or
how
many
project
or
how
many
I
don't
know,
have
you
been
instrumenting
so
because
if
it's
just
like
a
like
a
pet
store
project
sitting
in
the
side
and
compared
to
someone
that
has
fully
instrumented
their
two
entire
critical
business
application,
I
mean
the
priorities.
Obviously,
the
experience
and
and
and
the
information
will
be
completely
different.
A
Yeah
yeah
good
call.
I
totally
left
out
a
demographic
segmentation
question
on
this
high
level,
which
definitely
is
important.
Okay,
so
I
just
want
to
be
causing
out
of
time.
B
I
think
it's
good
one
point
that
I
just
gone
so
we
briefly
touched
based
the
previous
session
on
the
potential
opportunity
to
create
like
a
sort
of
a
customer
advisory
board
or
whatever,
where
we
bring
customers,
so
they
can
share
the
story
and
so
on.
So
I
think
that
would
be
very
useful,
but
for
my
end
I
already
asked
a
couple
of
customers,
so
they
could
potentially
participate.
B
C
Yeah-
and
I
think
I
think
we
discussed
was
there's
like
the
concept
of
a
board
which
is
like
the
same
people
coming
back
over
and
over
again
and
then
there's
just
the
concept
of
like
a
feedback
like
a
report
back,
and
I
think
it's
like
a
lower
bar
to
ask
for
the
report
back,
but
also
it
gets
back
into
that.
C
I
do
think
the
thing
we
should
concentrate
first
and
foremost
on
is
like
this
installation
experience
and
it
would
be
great
to
be
able
to
to
catch
customers
like
when
vendors
have
customers
that
you
know
when
they're
doing
have
just
done
that
big
push.
Hopefully
right,
like
your
sales
engineers
or
somebody
in
the
organization's,
hopefully
in
contact
with
them
and
being
able
to
make
the
ask
at
like
that
point
in
the
cycle,
so
that
we
can
get
feedback
from
people
like
when
it's
fresh
in
their
minds.
C
I
think
that's
really
important
if
we
could
get
something
like
that
going.
I
think
that
would
be
really
helpful
because
my
experience
is
like
when
too
much
time
passes
after
that,
it's
like
it's
hard
to
get
concrete
information
out
of
people,
because
they
kind
of
you
know
it's
just
like
old
news
yeah.
They
just
have
a
vague
idea
of
whether
it
was
painful
or
not,
but.
C
Exactly
so
that
I
think
that
would
just
be
like
fantastic
if
we
could
start
getting
like
a
feed
of
of
people
giving
us
their
experiences
after
they've
they've
gone
through
a
a
roll
out
process.
A
We
need
so
much
more
than
half
an
hour
because
I
think
there's
different
ways
to
capture
that
information
right.
So,
like
I've
been
on
a
number
of
end
user
interviews
this
week
and
I
was
like
oh,
I
wish
I
had
a
survey
that
I
could
just
dump
what
the
like
community
facing
stuff
just
into
that
survey,
yeah,
which
we
should
set
up,
but
also
the
piece
of
inviting
for
that
that
highly
engaged
direct
communication
with
the
community,
and
I
think
we
need
both
of
those.
But
where
would
you
start
since
we?
B
I
think
we
should
we
should
because
kubecon
is,
is
there
and
we
probably
have
a
lot
of
customers
that
will
be
there.
I
think
the
survey
will
be
awesome
to
have
there,
so
we
can
take
advantage
and
and
ask
people
directly
on
site
or
or
or
if,
if
everyone
has
a
qr
code
on
every
single
presentation
say,
please
take
a
few
minutes
and
answer
those
questions.
C
A
Oh,
it
totally
would
we
don't
have
time
to
get
into
that
today,
but
I
propose
for
our
next
okay,
our
next
chat,
whenever
that
will
be
that
we
really
do
that
cube
con
survey,
because
I
know
folks
are
building
their
decks
right
now,
and
so
it
would
be
good
to
get
that
in
there.
I
love
that
idea.
Anyone
talking
about
hotel,
add
this
qr
code,
nice
and
then
yeah,
we'll
figure
out.
What's
going
on.
D
If,
if
possible,
too,
to
use
that
cubecon
survey
kind
of
as
a
funnel
to
meetings
with
people
who
are
at
kubecon,
like
you
know,
if
possible,
are
you
interested
in
spending
five
or
ten
minutes
with
us
to
talk
about
your
experience.
D
A
So
the
governance
office
hours
that
I
tried
to
go
to
last
week.
Nobody
showed
up
that's
my
question.
A
We
should
take
it
off
of
the
calendar.
I
am
curious
about
what
formal
plans
there
are
for
a
kubecon
presence
of
the
open
telemetry
community.
Is
there
a
boost
like
who
are
the
right
people
to
ask
these
questions
to.
C
That's
that
can
go,
I
think,
to
the
mailing
list.
Maybe
the
governance
committee
mailing
list,
I
mean
the
right
people
to
ask
are
like
the
cncf
folks
like.
I
think
I
believe
it
is
possible
for
us
to
get
an
open,
telemetry
booth
now
that
we.
C
C
That's
definitely
my
understanding
is
that's
a
doable
thing
and
I
think
that
would
be
if
we
can
do
that
and
then
direct
people
to
that,
and
then
have
a
have
this
like
survey
available
either
for
them
to
fill
out
or
for
us
to
fill
out
on
behalf
of
people
anonymously
like
when
we
get
feedback
from
people
you
just
go
and
quickly
fill
the
survey
out
that
that
would
be
great.
B
Because
it's
almost
next
week,
it's
the
blah
blah
blah,
so
it's
almost
beginning
of
almost
april,
so
it
means
we
have
almost
one
month
left
to
get
that
survey
and
be
ready
for
con
yeah.
Are
you?
Are
you
okay?
I
mean
that's.
My
pure
suggestions.
Are
you,
okay,
that
we
extend
the
meeting
instead
of
half
an
hour?
We
do
one
hour
so
then
we
can
focus
on
on
finalizing
that
survey.
So
then
we
will
have
something
at
least
ready
for
come.
A
Yeah
for
sure
yes,
we'll
we'll
get
that
for
the
next
one,
or
we
can
have
like
a
an
intentional
session
right
outside
of
the
scope
of
this
one.
Do
you
have
a
preference
between
the
two
I
kind
of
have
a
preference
for
an
intentional
discussion.
It
could
be
at
the
same
time,
but
just
in
case
like
people
who
show
up
at
the
end
user
group,
we've
had
like
different
levels,
they'd
be
like.
A
A
I
like
that,
okay,
I
will
figure
out
how
to
make
that
happen
and
I'll
email,
the
gc
distro,
and
see
if
what,
if
what
of
any
plans
are
there
are
for
kubecon
eu.
So
I
know
that
there
are
going
to
be
open,
telemetry
talks,
so
that
will
be
good,
so
we're
here
at
time.
Is
there
anything
we
didn't
get
too
far
into
the
customer
advisory
interview
like?
I
don't
even
know
what
we
want
to
call
that
thing,
but
I
definitely
hendrix
sounds
like
you've
got
end
users
interested.
A
I
also
have
some
end
users
who
are
like.
I
totally
want
to
come
talk
to
them,
and
so
what
are
next
steps
over
the
course
of
the
next
two
weeks
on
the
set.
B
B
So
maybe,
if
we
do
one
session
per
month
or
every
two
to
month
or
be
er
one
every
month,
I
think
is
enough
and
we
take
maybe
the
first
15
minutes
or
the
first
20
minutes
just
to
share
hey
here
is
the
updates:
what's
happened
on
the
last
releases
and
what
you
have
been
approved,
and
so
that's
will
be
just
to
then
get
some
news
and
they
will
be
happy,
and
then
we
ask
one
of
the
customers
that
are
there
to
prepare
like
a
30
minutes
presentation
on
their
project,
how
they've
been
doing
it
their
challenges,
how
they
resolved
or
is
there
still
open
issues
yeah
anything?
B
And
then
we
do
have
half
an
hour
moderating
questions
between
us
and
maybe
there
are
customers
that
say
it
is
interesting.
I
want
to
talk
about
this
as
well,
so
there
will
be
a
way
also
to
get
customers
involved
and
seeing
that
there
are
other
customers
that
have
tried
that
has
failed
or
their
success.
So
then
they
can
talk
about
it.
I
think
there
will
be
a
so.
B
A
That'd
be
awesome:
okay,
we'll
chat
on
that
a
little
bit
more
next
time
be
respectful
people's
time.
Thank
you
so
much
for
engaging.
I
will
see
you
in
the
end
user,
cncf
slack
channel,
and
we
can
outline
our
suggestions
and
hopefully
get
other
folks
to
weigh
in
on
those
like
core
themes
that
we're
going
to
be
tracking.
In
that
first
survey.