►
From YouTube: Kubernetes WG Apply 20181009
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
A
See:
okay,
API
change;
no,
we
did
not
get
to
it
and
Jenny's
out.
I
should
coming
back
tomorrow,
I
think
so.
Okay,
yeah
Jenny
was
out
for
a
few
days
translate
existing
tests
into
new
tests.
We
don't
think
we
got
to
that.
Modify
the
test
suite
to
take
a
series.
It
okay,
we
got
one
round
and
it
sounds
like
it's
out
for
more
comments.
Now,
it's
cool,
okay,
I'll,
take
a
look
at
that
same
later,
yeah,
sorry,
I
didn't
realize
it
was
waiting
for
more
comments.
I
would
know.
A
Yeah
yeah,
sometimes
you
have
to
like
comment
like
pta.
Please
take
another
like
PT
al
or
something
like
that.
But
I
haven't
gotten
to
my
email
yet
this
morning,
so
is
probably
waiting
for
me.
All
right
make
sure
the
new
repo
is
tested
on
presubmit.
We
did
that
not
us,
but
somebody
did
that.
How
was
it
done?
Yeah
I
didn't
I
didn't
catch
his
name,
but
the
really.
D
D
A
A
A
E
A
B
A
C
A
A
A
D
D
They
are
yeah,
you
could
even
just
leave
it
like
like
empty
struct
it.
Currently,
it's
filled
like
got
a
string
field
in
conflict
and
because
we
want
to
check
for
unexpected
or
expect
the
conflicts
and
some
there
needs
to
be
something
to
check.
So
I
just
put
up
fields
string
in
there
and
to
compare,
but
it's
very,
very
primitive.
No,
not
beautiful
yeah.
A
A
C
C
A
C
E
A
A
A
D
D
B
A
A
C
A
B
A
A
A
A
I
means
defining
the
API
change
to
the
object,
meta,
meta,
p1,
again,
yeah,
yeah
and
then
we're
gonna
have
to
like.
We
can
do
that
in
the
feature
branch
like
just
just
throw
something
up
there
and
then
then
we
have,
but
we're
gonna
have
to
get
an
API
review
yeah
so
like
I.
Actually,
maybe
maybe
that's-
maybe
that's
a
that's.
A
What
I
could
just
just
make
a
simple
change
in
the
feature
branch,
so
we
can
start
integrating
what
simpler
change
like
the
the
first
thing
that
comes
to
our
mind
and
then
and
start
the
process
of
getting
an
API
review
in
parallel,
because
it
can
be
changed.
Okay,
that
make
sense
yes,
sort
of
I
sort
of
like
like
just
make
an
API
change
that
is
similar
to
the
type
that
I
made
in,
but
it
lists
instead
of
a
map,
yeah
yeah,
and
then
we
cannot.
You
find
and.
D
D
A
Can
merge
it
right
away
because
this
to
the
feature
branch
yeah
and
we
can
start
implementing
it
because
whatever
we
do
is
just
like
changing
the
API,
and
this
just
means
changing
the
code
that
connects
it
up
to
our
implementation.
So,
yes,
so
actually
I'm,
gonna,
I'm
gonna,
put
get
an
API
review.
Yeah.
A
A
A
C
A
D
C
A
A
Be
a
good
focal
point
for
people
to
have
that
conversation,
okay,
cool!
So
that's
there
you'll
already.