►
From YouTube: 2022-04-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
Well,
I
suppose
we
can
go
ahead
and
get
started.
Okay,
so
inside
the
meeting
notes,
we've
got
a
small
agenda,
so
let's
take
the
next
one
minute
and
y'all
can
review
the
agenda
and
see
if
there's
anything,
you
would
like
to
add
or
modify
before
we
get
started.
A
B
A
Okay,
cool
okay,
so
I
guess
my
first
question
is:
I
feel,
like
progress
has
been
a
little
bit
slow.
Would
it
help
to
expedite
some
of
that
if
these
meetings
were
either
longer
or
more
frequent,
and
so
I
wanted
to
get
your
thoughts.
B
I
agree,
I
think
we
all
have
stuff
to
deal
with
with
our
day-to-day
job.
I
think
so.
We
make
some
baby
steps.
We
take
a
few
hours
here
and
there,
but
I
think
we
don't
make
the
right
progress,
especially
kubecon.
Europe
is
a
is
right
out
in
the
corner,
so
I
think
we
should
have
maybe
a
more
regular
meetings,
at
least
before
kubecon,
so
we
can
finalize
everything
in
time,
so
I
think
yeah
once
a
week
and
they
now
we
have
just
half
an
hour.
B
So
maybe
at
least
an
hour
I
think
will
be
good
to
at
least
assign
things.
And
then,
if
we
have
small
work
working
groups
between
us,
then
we
can
organize
working
sessions
on
side
of
this
team.
A
I
believe
we've
got
four
four
more
of
these
potential
sessions
before
kubecon
eu.
So
if
we
did
weeklies
for
the
next
month
and
see
if
that.
B
Makes
sense
for
me,
I
want
we'll
be
off
next
week,
so
I
won't
be
able
to
connect
and
do
much
but
yeah
for
the
rest.
The
other
weeks,
oh,
no
worries
I'll,
be
there.
C
I
have
been
attending
this
sort
of
infrequently,
so
I
don't
have.
I
don't
know
if
I
have
anything
too
constructive
on
the
frequency,
because
it's
mostly
my
disgusting
schedule,
that's
conflicting
with
it.
A
Okay,
well
we'll
we'll
try
weeklies
for
the
month
leading
up
to
cubecon
and
see.
C
A
Okay
and
then
so
next,
one
we've
kind
of
waffled
on
the
idea
of
an
end
user
slack
channel.
I
don't
know
if
that
would
be
useful,
but
that
would
be
good
for
places
to
like
interview
the
bring
your
own
hotel
end
user
stuff
and
to
like
hit
and
target
them,
but
the
other
benefit
there
would
be
that
end.
Users
can
talk
to
each
other.
Some
end
users
like
that
right,
so
some
of
them
are
like.
Oh
no,
my
company
doesn't
know
how
to
deal
with
open
source.
A
I
can't
possibly
show
up
in
public
because
reasons,
but
for
those
companies
that
don't
have
those
types
of
constraints.
I
wonder
if
an
end
user
slack
channels
where
they
can
just
go
and
hang
out
and
share
best
practices.
I
don't
know
the
question.
C
A
Yeah
so
then,
in
that
case
I
would
want
to
like
provide
a
little
bit
of
guidance,
so
people
who
are
new
to
open
source
are
like
I
don't
know
how
to
get
in.
I
don't
know
what
the
expectations
are.
Where
can
I
chat,
and
so,
if
we
want
to
say
hey
end
users,
this
is
the
home
channel
open,
telemetry,
it's
a
great
place
for
you
to
connect
with
others.
B
B
Would
that
make
sense
to
have
like
a
help
open,
telemetry
channel
where
people
that
has
like
a
just
a
question
or
frustration?
They
drop
that
and
help.
So
then
we
we
could
basically
have
a
channel.
That
would
be
more
for
tech,
maintainer
discussions
and
one
more
for
yeah
problems.
Questions
because
I
am.
If
I
look
to
the
open
geometry
discussions,
there
are
lots
of
different.
That
is
not
only
end
user
topics.
There's
it's
broader.
C
C
Tends
to
be
a
lot
of
people
who
contribute
to
open
telemetry
again,
despite
the
name,
it's
not
strictly
maintainers,
it's
it's
really
just
like
the.
They
discuss
core
contributions
to
the
project,
whereas
the
open
telemetry
channel
tends
to
be
more
end
users
with
a
mix
of
maintainers
in
there.
So
then,
let's
keep
this
one.
Then
okay,.
A
Okay,
so
maybe
figuring
out
how
somewhere
in
a
community,
read
me
somewhere.
That's
like
hey!
If
you
have
basic
questions
about
the
project,
you
can
ask
an
open
telemetry
just
I
want
to
provide
guidance
for
end
users
about
how
can
they
interact
if
they're
new
to
this
and
they're
like
a
little
bit,
hesitant
to
reach
out
okay
I'll,
throw
some
guidelines
together
and
there
may
still
be
a
place
for
like
end
users
to
hang
out.
A
There's
2800
people
in
here,
which
can
be
people
might
not
want
to
to
say
anything
in
a
group
audience
that
large,
but
I'll.
Just
ask
some
of
the
end
users
that
I
talk
to
if
they
have
any
preferences
and
figure
that
out.
I.
B
Still
have
this,
this
idea
on
top
of
my
mind,
but
I
think
from
for
kubecon
is
too
short,
but
after
kucon,
I
really
want
to
have
this
organize
another
meeting
for
the
open
temperature
customer
advisory
board
and
we
should
not
record
because
people
would
probably
companies
won't
be
very
keen
to
have
something
published
so,
but
we
can
organize
that
we
can
try
to
launch
it
after
kubecon,
so
but
yeah.
A
I
think
that
might
is
that,
specifically
for
cubecon.
B
No,
no,
no,
I
think,
because
we
won't
be
able
to
organize
it
before
kubecon,
because
we
need
to.
We
need
to
first
yeah
sort
of
organize
the
entire
group.
B
Nothing,
I
think
I
think,
once
per
month
that
we
find
above
that
would
be
too
much,
but
at
least
if
we
then,
once
we
have
that
started
with
various
vendors,
then
we
can.
I
can
reach
out
to.
I
already
have
three
customers
in
mind,
and
if
you
want
to
do
that,
then
we
can
have
one
session
per
month.
We
want
all
of
those
customers,
and
I
think
that
would
be
great.
A
I
think
that's
a
really
good
lead
into
our
next
agenda
item,
and
so
I
think
what
you
so
customer
advisory
board
slash
customer
interview,
so
the
byo
hotel
end
user
is
like
a
customer
or
sorry
an
end
user
interview.
B
I
think
the
cab
would
be
more
like
a
we
every
month.
We
pick
a
story,
a
customer
I
mean
someone
is
leading
that
session
bring
the
customer,
and
then
we
can
start
with
the
with
the
the
intro
is
what
is
happening
there.
We
last
month
on
the
community
and
then
we
move
on
and
the
customer
explains
his
story
in
30
minutes
and
then
we
are
open
for
25
questions.
I
think
it's
not
a
good
fit
for
a
for
an
interview
for
interview.
We
could
then
we
could.
B
There
could
be
a
call
out
to
the
people
attending
that
session.
Hey,
we
are
organizing,
end
user
interviews,
we'll
be
interested,
and
then
we
can
have
a
list
of
people
and
then
we
can
reach
out
and
organize
those
interviews,
one
by
one
recording
and
then
store
the
videos,
and
we
can
come
up
to
producing
some
content
with
different
people.
Talking
about
the
topic.
B
B
How
do
you
manage
this
and
this
and
for
us,
we're
very
good
to
learn
through
this
use
case
or
a
story
about
a
problem,
a
potential
problems
related
to
the
getting
started
or
or
or
maintaining
your
entire
stack
whatever,
and
I
think
the
interview
it's
more
private,
so
I
think
we
should.
B
We
could
basically
try
to
identify
people
with
their
email
or
contact,
and
then
we
can
reach
out
to
those
people
one
by
one
and
do
interview
one
by
one
101
interviews,
so
people
could
share
or
and
give
details
without,
and
then
we
can
just
limit
the
scope
to
avoid
sharing
too
much.
If
they
are
data
sensitive.
I
would.
A
Say:
gotcha,
okay,
I
think
I
have
you
anyway.
So
let
me
share
my
screen
so
for
at
least
the
user
interview
I
put
together
a
process
doc,
and
so,
if
you
give
that
a
little
bit
of
a
a
read
through
to
see,
if
like
does
this
in
my
mind,
I
think
like
80
overlap
with
kind
of
whatever
you
want
to
call
bring
your
own
end
user.
A
But
the
idea
basically,
is
that
it's
a
facilitated
conversation
that
is
organized
and
structured,
but
it's
it's
not
necessarily
one-on-one,
but
it's
a
small
group
for
that
discussion
and
the
other
thing
in
here
is
like
a
discussion
template
and
so
maybe
that's
a
good
place
to
start.
So
this
is
like
the
process
that
would
be
followed.
The
roles
and
responsibilities
when
and
where,
but
like
the
meat
of
it
would
be
essentially
like
a
discussion
guide,
and
so
what
are
some
of
the
action
items?
A
What
are
some
of
the
questions
and
then
are
there
any
particular
meaty
questions,
and
all
of
this
is
pretty
much
straight
lifted
from
atlassian's
customer
interview
playbook
for
the
most
part,
that's
good.
I
think
I
think
it
covers
a
lot
of
what
you're
talking
about.
A
A
Of
course
we
need
the
interviewee,
but
I've
named
this,
like
second
role
for
somebody
who
is
explicitly
doing
note,
keeping
and
doing
some
facilitation
of
coordination
and
working
with
the
interview
facilitator
to
really
at
the
end,
be
like
okay,
so
that
discussion,
let's
write
up
a
a
recap,
and
so
it's
not
just
necessarily
one-on-one.
So
this
would
potentially
be
two
on
one,
but
I
think
there's
an
opportunity
to
have
a
member
audience
come
in
so
that
they
could
ask
questions
as
well,
but
I
don't
want
it
to
be.
A
I
don't
know
what
I
want,
but
I
I
don't
want
like
150
people
to
show
up,
because
that
also
like
how
do
we
keep
it
somewhat
casual
but
more
structured.
B
Yeah,
that's
a
good
point.
I
may
think
that
if
you
want
to
interview
and
get
more
experience,
because
at
the
end,
the
the
output
of
the
interview
is
for
us
to
share
it
with
maintainers
or
if
it's
pretty
interesting,
we
can
come
up
with
a
recording
of
the
video
of
the
interview
and
share
a
few
like
a
few
words.
So
then
we
can
come
up
with
some
some
some
small
videos
share
of
someone
speaking
about
success
stories
that
he
has
done
in
in
a
few
seconds.
B
I
think,
with
the
through
the
interview
we
could.
We
could
utilize
a
lot
of
things
behind.
So
I
think
I
would
think
that
a
101
or
201,
like
you
mentioned
interview,
is
better.
So
then
we
can
have
a
raw
recording,
at
least
of
one
part
of
the
interview
that
we
could
use
for
any
other.
A
Terms,
okay,
yeah,
do
you
want
to
throw
you
can
absolutely
like
throw
in
comments?
That's
like
hey
for
a
couple
of
these.
We
can
also
like
experiment
with
the
the
layout
and
say
no
community
members
attending
and
some
of
them.
Maybe
we
could
open
that
up.
Just
yeah
get
a
few
under
our
belt
and
then
figure
it
out.
A
I
I
have
done
a
couple
of
these,
but
different
at
least
for
the
template
of
like
I
think
we
need
date
and
time
who's
going
to
be
the
facilitator,
who's,
the
helper
who's,
the
end
user.
What's
your
contact
information,
a
recording
link,
and
so
all
of
that
information
is
important.
I
think.
B
Also
so
do
we
have
I
don't
just
this
is
pure
logistics.
I
don't
know
if
you
already
had
already
covered
that
aspect
for
the
recording.
Do
we
have
the
cncf
storage?
Where
do
we
I
mean,
especially,
although
all
those
questions
will
come
up
when
we
start
recording,
so
I
have
no
idea
when,
where
all
the
who
is
going
to
host
and
store
this
and
where,
because
at
the
end,
that
question
will
come
up
soon
once
we
start
the
interviews.
A
Okay,
good
point:
no,
I
have
not
gone
there,
I'm
assuming
they
will
be
on
zoom,
but
we
should
probably
have
a
additional
zoom
channel
that
we
can
record
to
and
have
access
and
I've
seen
people
be
like.
I
can't
get
into
zoom
and
then
figure
out
what
the
permissions
are
for.
That.
B
Because
if
you
want
to
do,
if
you
want
to
do
a
201
or
101
interviews
with
pretty
good
quality,
I
usually
do
for
recording
purposes.
I
use
reverse
side.
Fm
riverside
has
the
advantage
of
it.
Doesn't
it
doesn't
compress
the
audio
and
video
and
stream
it?
It
basically
gets
the
best
local
quality
of
the
people
interviewed
and
at
the
end,
you
have
one
raw
recording
per
attendee,
which
means
then
we
can
do.
We
can
have
it's
easier
to
utilize
it
for
to
building.
A
A
I
think
the
only
thing
when
we,
when
we
think
about
distributed
like
permissions
like
this,
is
just
how
do
we
make
sure
that
those
assets
stay
with
the
community
when
people
change,
and
so
is
there
like
an
administrative
account
that
has
certain
access
and,
like
we'll,
just
have
to
talk
through
those
logistics?
But
if
we
want
to
try
every
riverside
fm,
that
sounds
awesome.
I
don't
know
if
that's
like
a
page
service
we'll
have
to
figure
some
of
that
out.
B
It's
it's
a
paid
service
for
sure,
and
the
subscription
depends
on
the
number
of
interviews
and
hours
of
recording
you
do
per
month.
But
then
you
can
create
a
team,
sometimes.
C
A
Okay,
I'll
follow
up
with
taylor,
who
is
leading
the
end
user
stuff
for
cncf.
A
Awesome:
okay,
if
anybody
has
any
additional
feedback,
so
ben
created
this
like
quick
spreadsheet,
I
don't
know
if
ted
means
he's
actually
finding
someone
for
two
days
from
now.
Actually
I
guess
that's
four
days
from
now,
so
I
I
will
follow
up
with
him
and
say:
hey.
Is
this
real,
so.
B
A
Okay,
so
this
is
going
to
be
facilitator.
I
don't
know
if
I
spell
that
right
and
this
will
be.
A
A
So
I
think
this
is
relatively
good-ish
for
right
now,
because
we've
got
recording
link
and
then,
if,
if
applicable,
I
guess
recording
password.
A
Okay,
I'll
follow
up
with
ted
and
see
I'm
thinking
this
was
maybe
a
little
bit
aspirational
but
henrik
if
you've
got
people
like
in
your
pocket,
and
you
want
to
run
one
of
these
before
cube
con
I,
as
soon
as
we
figure
out
logistics.
I
think
we
should
be
good
good.
A
Okay
and
then
so,
we've
got
like
five
minutes
left.
I
created
some
more
surveys,
and
so
I
checked
in
with
taylor
from
cncf
and
they
do
not
have
access
or
they
don't
provide
projects
access
to
like
paid
survey
software,
and
so
it
would
be
on
us
to
figure
that
out
we
can,
we
can
run
with
google
forms.
I
like
the
ease
of
permissions
and
transparency
that
google
platform
provides.
I
just
don't
like
how
it
it
just
looks
kind
of
lame.
A
A
Whoever
and
that's
not
a,
I
think
it's.
A
Okay,
headphones
just
cut
out;
okay,
my
headphones
are
back,
so
I
think
google
forms
just
seems
reasonable,
given
that
constraint-
and
maybe
we
can
like
make
pretty
banner
or
something.
B
So,
who
is
going
to
trans
transform
the
various
surveys
into
cool
forms?
That's
the
the
big
question
mark
that
I
had.
I
was
going
to
ask.
A
I
think
that
is
open
for
anybody
who
wants
to
do
it.
I
I
could,
but
I
don't
have
to,
and
so
I
wanted
like
make
sure,
there's
still
a
couple
of
questions,
so
I
don't
think
they're
exactly
ready
to
follow
to
to
transcribe
into
google
forms
yet
but
they're
pretty
close.
A
So
maybe
yeah
I'm
like
one
week,
but
I
don't
know
how
to
get
feedback.
So
I
threw
this
into
my
corporate
slack
channel
and
said:
does
anyone
want
to
get
feedback.
B
A
Okay,
we
don't
have
our
own
repo,
we're
part
of
the
community
repo,
but
I
can
absolutely
open
an
issue
as
soon
as
like
I'm
like
95
percent.
There
hey
leave
it
open
for
a
week,
because
I
I
would
like,
like
maintainers
to
say,
hey
what.
What
is
there
something
specifically
that
maintainers
are
like.
I
really
wish
that
I
could
get
regular
feedback
on.
Can
we
incorporate
those
into
these
surveys,
so
I
will
absolutely
open
up
a
google
issue
as
soon
as
I
fiddle
with
it
just
a
little
bit
more.
A
These,
like
blue
ones,
are
ones
where
I'm
like
is.
Are
they
worded
the
correct
way?
And
so
I
think
this
is
the
most
complete
survey
minus
this
like
how
to
talk
about
experience,
and
then
I
want
to
copy
over,
like
these
demographic
questions,
to
all
surveys,
so
that
they're
consistent,
which
will
be
good
when
we
do
data
analysis
so
yeah.
We
can
use
this
survey
as
a
primary
one.
Right
now,.
A
Okay,
that's
everything
about
surveys.
Let's
see
how
to
finalize
ollyfest
opportunity
for
this
group,
we
bruce
who's.
Organizing
olliefest
has
some
potential
three-hour
block
time.
This
is
one
week
before
kubecon.
If
there's
anything
this
group
wants
to
do,
or
the
community
at
large
wants
to
do,
they're,
providing
that
as
a
like
a
an
opportunity
for
the
community.
B
I
think,
because
it's
an
event,
we
need
to
structure
it
very
a
lot
I
would
presume
so
we
need
to
in
that
case,
if
you
want
to
have
an
end
user
or
experience
also,
we
need
to
somehow.
If
you
have
three
hours
to
cover.
Oh,
we
need
at
least
four
or
five
customers
and
and
then
we
can
prepare
a
list
of
questions
and
we
are
just
like
a
panel
discussion.
We
just
moderate
so
yeah
that
could
be
possible.
B
But
again,
I
think
we
we
need
to
identify
who
could
be
a
good
candidate
to
be
invited
to
that
sort
of
panel
discussion.
B
For
the
oily
fest,
so
when
I
think
only
first
is
in.
A
B
It's
just
that,
just
after
three
weeks
it's
going
to
be
very
tight
to
do
yeah
yeah,
I
won't
have.
I
will
have
a
limited
bandwidth,
because
I
have
to
do
some
stuff
for
other
working
groups
yeah.
I
I
don't
want
to
commit
something
that
I
won't
be
able
to.
A
A
Okay,
we're
here
at
time,
morgan,
any
anything
you
want
to
add
about,
like
kubecon
eu.
C
Yeah,
so
I
mentioned
this
on
the
maintainers
call
and
gc
call
last
week,
so
we
have
a
couple
things
coming
up,
cube,
coney
you.
We
have
a
maintainer's
track
talk.
We
have
a
big
room
booking
that
I
need
to
send
out
like
the
invite
for
I'll
get
to
that
later
this
week,
and
we
there's
a
third
thing.
That's.
C
Right
now,
booking
maintainers
track
talk,
oh
and
we're
going
to
get
likely
some
time
highlighted
during
the
keynote
the
project
update
section.
So
we
can
discuss
the
metrics
release,
we'll
also
be
doing
a
project
blog
post
during
kubecon
to
discuss
the
metrics
release.
A
B
I
won't
be
there
at
kubecon
there's
two
things
because
I
started
this
new
video
series
for
now
it's
piloting,
so
it's
not
part
of
since,
but
it's
gonna
be
part
soon
in
the
cncf
channel.
It's
called
the
open
source
news
and
I
was
thinking
doing
some
interviews,
so
I'm
gonna
bring
camera
mics
lights
on
the
event
itself.
So
if,
if
there
are
any
like
you
said
interviews
that
make
sense
to
record,
I
should
be
able
to
do
that.
C
Fantastic
cool-
I
will
be
there
as
well,
so
let's
get
that
queued
up,
like
I'm,
I'm
sure
there's
some
like
press
interviews
and
things
that
are
getting
scheduled,
but
it
would
be
great
to
do
like
recorded
content
that
you're
describing
with
maintainers
and
end
users
and
everyone
else
yeah.
That
would
be
cool
perfect.
Thank
you.
Cool.
A
Awesome
all
right
folks,
well,
thank
you
so
much
and
I
will
chat
with
you
next
week.