►
From YouTube: 20190515 - Cluster API Office Hours
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).
B
B
One
other
thing
is
to
keep
agenda
items
short
and
like
around
two
minutes,
so
to
give
other
folks,
also
kind
of
like
a
way
for
them
to
contribute.
The
meeting
and
I
would
like
to
propose
to
use
the
zoom
raise
hand
feature.
This
will
put
a
little
bit
more
work
on
the
moderator
there
that
we
just
make
in
this
case,
like
Jason
and
I,
avoid
interrupting
folks
unless,
of
course,
you're
moderating.
D
E
D
I
think
in
the
context,
right
now
are
on
a
fact-finding
discussion
mode
and
so
I
think
that's
where
some
some
of
maybe
the
contention
here
is.
You
know
we're
actively
proposing
things
and
actively
discussing
those
things
and
if
we
pivot
out
of
that
mode
into
more
of
a
maintenance
kind
of
mode
I
think
that's
a
fine
set
up.
F
Andy
yeah,
I,
I
I
think
this
is
a
good
idea.
I
understand
Michaels
concern
about
having
it
sort
of
caused
the
flow
of
conversation
to
maybe
slow
down
a
little
bit,
but
I
think
it
gives
us
an
opportunity
to
listen
to
each
other
in
a
way
that
I
noticed
last
week
we
weren't
necessarily
doing
too
so
I
think
it's
a
good
change,
I'd
like
to
at
least
try
it
for
a
little
while
and
if
we
decide
later
that
it's
causing
us
to
go
too
slow,
then
maybe
we
change
again.
B
Yes,
so
I
think
like
what
kind
of
coming
before
cube
con
and
we're
kind
of
set
like
ourselves
for
the
next
few
weeks
to
propose
to
put
the
proposals
in
posture
API.
So
it
would
be
great
to
like
kind
of
wrap
up
the
the
work,
streams
and
kind
of
just
discuss
like
in
the
main
meeting,
if
like
there
is
anything
they
want
to
discuss.
Synchronously
were
just
like
focus
on
the
proposal.
I
thought
that
was
still
work
in
progress.
B
B
Some
work
streams
are
I
I.
Think,
though,
they're
like
at
this
point,
it's
kind
of
clear
like
where
we
want
to
go,
which
is
like
kind
of
proposals
and
kind
of
to
say
it,
like
you
know
like
to
make
some
progress
and
I
think
the
work
streams
can
probably
be
wrapped
up
at
this
point.
Given
that,
like
we
know
what
we
want
to
wanna
go
and
which
proposal
like
are
in
flight
and
so
kind
of
focus
on
that
and
then
bring
up
the
discussion
in
this
community
meeting
if
needed,
where
I
see
it.
E
Let
Tim
go
first,
I
think
there's
there's
two
parts
that
I
think
are
good
to
this
and
you
know
feel
free
to
point
out
things
that
you
don't
like
well
there.
There
are
overlapping
concerns
that
exist
in
some
of
these
proposals
and
if
we
collapse
them
into
concrete
things
that
we
can
talk
about
in
this
main
meeting,
I
think
that's
a
good
thing
and
then
it
forces
us
to
review
the
docs
that
we've
created
and
I
do
know
that,
like
you,
can't
do
some
things
without
the
other
things
and
it
this
way
we
can.
E
A
F
So
I
I
think
we're
probably
ready
to
do
it
I'm
a
little
bit
concerned
with
the
way
Vince
phrased
the
idea
that
we
know
exactly
you're
more
or
less
what
we
want
to
do
because
I
feel
like
that
is
still
very
much
up
for
discussion,
but
I
think
having
them
split
up.
Helped
us,
as
Tim
just
said,
focus
on
different
areas
but
realize
that
there
is
a
lot
of
overlap
between
them
and
we're.
Gonna
have
to
do
some
things
in
certain
order
and
I
think
we
do
understand
that
part
now.
So.
A
Illya,
can
you
please
start
raising
your
hand
in
zoom
we're
trying
to
enforce
a
watering.
C
C
H
B
But
that's
exactly
that.
It's
more
like
to
kind
of
realign
like
in
the
product
group
exactly
keeps
everything
Thanks.
D
A
All
right
anything
else
on
that
topic
beds,
no
big,
all
right
next
item,
I
just
wanted
to
make
sure
everybody
is,
was
aware,
we're
not
having
it
in
office
hours.
Next
week
it's
been
canceled
because
there's
gonna
be
quite
a
few
people
that
are
at
cube
con
next
week
and
I
lost
my
space
there
we
go
and
I'm
also
going
to
need
to
see
if
we
can
find
a
volunteer
to
moderate
the
office
hours
for
the
29th
of
May,
because
I
will
be
out
that
week.
A
I
Yes,
so
there's
been
quite
a
lot
of
discussion
going
around
or
on
the
document
itself
and
I.
Think
one
of
the
things
that
we
perhaps
need
to
tackle
is
kind
of
way
the
the
extra
images
get
it
built
upon
and
what
are
constraints
for
these
ti
infrastructure,
I
think
if
we,
if
we
can
kind
of
solve
that
problem,
we
might
be
able
to
move
a
little
bit
forward
on
that
I'm,
not
sure,
but
tell
me,
maybe
you
have
some
different
ideas.
There.
E
I
think
it's
fine
I
was
going
to
rewrite
the
current
proposal
and
break
down
some
of
the
pieces
into
details
underneath
the
proposal
there's
a
lot
of
good
data
in
there
we
have
like
twice
20
pages
now
so
the
but
the
the
ordering
of
what
we
talked
about
last
time.
I
have
not
written
down.
I
focused
my
last
two
days
on
rewriting
the
Machine
lifecycle
hook
proposal,
if
that
is
in
good
shape.
E
A
E
A
broad
sequestered
lifecycle
session
at
during
the
contributor
summit,
so
I
highly
recommend
for
folks
to
go
during
that
it's
on
Monday
in
the
afternoon
we
have
the
entire
afternoon
blocked
out
for
the
entire
Singh
and
I'm
sure
there
are
a
bunch
of
discussions
we
can
have
there.
I
do
want
to
make
sure
that
we
at
least
take
notes.
If
we
can't
get
a
video
recording,
I
do
believe
that
they,
the
last
time
they
had
a
video
recording
for
the
some
of
those
breakout
sessions.
E
J
E
Asked
several
times
for
a
proposed
agenda
and
people
didn't
step
up
all
the
way,
but
if
you
have
ideas
feel
free
to
reach
out
to
me,
I'm
trying
to
curate
a
document
about
some
of
the
broader
sing
things
and
then
try
to
maybe
even
break
down
on
specifics
of
project
elements.
There
are,
if
you
want
to
work
on
that
with
me,
that
would
be
a
highly
beneficial,
like
I've
asked
for
help
a
number
of
times
and
I
got
crickets.
So
if
you're
interested
in
curating
topics
for
discussion,
that
would
be
that'd
be
helpful.
J
Maybe
I
can
continue
later
or
slack
and
because
I
have
no
idea
what
the
format
of
session
is.
So
maybe
you
give
me
some
more
background.
I
can
prove
it
all
right
sure
not
to
take
time
in
this.
Medium
is
probably
more
like
just
I
haven't
proposed
anything
because
I,
don't
really
know
what
the
format
of
the
know
is
going
to
be
something
specific
topics:
more
brought
community
related
topic,
Heather.
No!
So
next
this
is
you
don't
mind
yeah
in
it.
J
E
Typical
way,
we've
run
these
things
in
the
past
just
to
give
people
some
background.
Is
we
kind
of
do
it
almost
as
an
unconference,
where
the
unconference,
if
you're
not
familiar
with
it,
you
kind
of
write
down
your
ideas
and
people
kind
of
get
to
vote
on
what
topics
they
want
to
address
and
then
because
the
sake
has
grown
so
large
I
think
that's
the
only
way
we
could
really
handle
it.
K
You
want
to
ask
that
there's
a
central
list
of
links
to
the
current
kept
tracks,
just
so
to
make
it
easier
for
anyone
interested
in
reading
through
them.
I
know,
eventually,
they'll
they'll
become
PRS
in
the
new
cluster
API
repo,
but
for
now
and
I'm
happy
to
make
that
list,
but
where?
Where
should
it
go?.
A
E
L
Just
a
quick
one,
you
know
I'm
trying
to
work
through
the
material
for
the
v1
alpha
two
proposals
that
are
sitting
out
there
I'm
just
you
know
coming
into
this
a
little
late,
but
but
kind
of
curious.
When
now,
when
are
you
looking
to
sort
of
make
a
decision
on
which
sort
of
path
you're
looking
to
go
down?
It
just
helps
prioritizing
how
how
quickly
to
move
through
this
material,
yeah.
E
E
C
E
Hopefully,
let's
let's
talk
some
more
and
we'll
the
hopefully,
by
that
time
it
doesn't
have
to
come
to
it,
but
typically
because
it
is,
it
falls
underneath
approvers
and
reviewers
category.
So
if
there
is
if
the
approvers
and
reviewers
have
given
the
thumbs
up,
that's
the
end
of
the
day
is
just
like:
okay
right.
F
E
H
Well,
first
I
want
to
say:
hey
Doug,
good,
to
see
you
from
OpenStack
but
yeah
when
people
say
kay-kay,
it's
often
a
shorthand
for
how
the
project
functions
as
at
large,
so
lectin
was
saying,
based
primarily
on
the
conventions
and
tooling
applied
to
the
kubernetes
kubernetes
mono
repo.
So
it's
a
cultural
thing
as
much
as
anything
else
but
good
to
see
you
yeah.