►
Description
Kubernetes Public Steering Committee Monthly Meeting for 20200404
A
Hello,
everyone
and
welcome
to
the
first
steering
public
meeting
in
april.
I
will
be
the
host
today,
bob
killen.
As
a
general
reminder,
these
meetings
are
repo
recorded
and
will
be
posted
to
youtube.
Sometime
later
today,
we
abide
by
the
cncf
code
of
connect,
which
essentially
boils
down
to
please
be
excellent
to
each
other.
C
Let's
see,
I
already
forgot,
where
what
I'm
doing,
let's
see
oh
steering
steer.
Well,
we
do
have
time
on
the
next
upcoming
governing
board
meeting
right
now
we
have
15
minutes.
That
is
not
this
wednesday,
but
next
wednesday,
and
we
don't
know
necessarily
where
we
are
on
the
schedule.
Yet.
Priyanka
and
arun
are
working
on
the
agenda.
I
think,
as
we
speak
so
hope,
to
hear
at
some
point
this
week
where
we
are.
A
C
Yep
yep,
I
shared
them
with
priyanka
in
a
roon
already
and
they're
reviewing
them.
So
I
think
priyanka,
oh
so,
yeah
priyanka
wanted
to
share
with
cncf.
Was
that
cool
with
us
at
this
stage?
Okay,
cool,
all
right
I'll,
get
back
to
work
with
that
yeah,
but
intentions.
Are
that
we're
okay
to
share
these
documents
with
gb
members
as
well
as
cncf
staff
at
this
point
sounds
good.
A
A
We
had
started
this
conversation
in
the
let's
see
q4
of
last
year
with
the
potential
intention
of
moving
their
project.
Their
are
sub-projects
under
sig
apps.
At
this
time
there
hasn't
been
any
traction
on
that,
both
in
terms
of
potentially
migrating
it
over
and
retiring.
The
sig
at
this
point
kicking
off
the
sort
of
more
public
discussion
on
it.
B
A
A
E
F
D
E
D
A
E
E
E
C
C
Yeah
I've
been
challenging
them
hard
on
like
what
that
means
like
what
does
this
mean
exactly
I'm
an
nd,
I'm
a
gb,
I'm
in
gb
and
I'm
an
end
user
looking
at
help
wanted,
and
I
can
assign
head
count
to
this
right.
Like
that's
the
kind
of
mindset
that
I'm
looking
at
right
now,
because
they're
not
going
to
assign
head
count
to
something
that
doesn't
have
any
justification
and
generic
and
generalized.
D
Any
other
can
I
ask
a
related
question:
paris,
somewhat
related,
so
the
hcd
stuff
ended
up
on
our
lap
as
well
right,
because
you
know
the
original
email
came
to
the
steering
public
mailing
list.
So
then
the
question,
so
people
do
that
got
you
know
wider
wider
publicity
and
then
ended
up
with
at
least
aws,
offering
up
a
couple
of
people
to
help
with
hdd.
So
do
you
want
to
do
something
like
that
as
well?
And
would
we
do
it
before
or
after
the
gb
meeting.
C
Probably
after
and
yes,
we
already
have
a
lot
of
things
planned,
so
the
contributor
comms
team
has
been
assigned
to
work
on
blog
posts
per
theme,
they're
also
doing
tweets
per
help
wanted
issue
we're
also
going
to
do
a
giant.
A
gigantic
k.
Div
help
wanted
email
so
yeah.
I
plan
an
entire
campaign
around
this.
C
A
Okay,
next
thing
up
is
steering
ama
for
for
those
of
us
that
can't
attend
kubecon
eu.
There
is
going
to
be
a
contributor
summit,
it
is
monday,
may
16th
and
right
now
it
looks
like
there's
going
to
like
one
of
the
requested.
Things
was
a
ama
of
the
steering
committee,
and
this
is
strictly
the
contributor
base.
A
It's
not
the
general
public
or
general
keep
cutting
attendees,
so
this
is
people
are
just
gonna
have
questions
for
for
us
as
a
group,
there
is
no
time
on
it
yet,
but
like
I'm
in
favor
of
attending-
and
I
was
gonna-
be
there
anyway
should
is-
is
anyone
not
going
to
be
there
on
monday
that
was
planning
on
going
to
keep
kanye?
At
this
point?
A
The
the
big
thing
is
at
least
the
people
that
will
be
at
the
contributor
summit-
one
it's
just
gonna,
be
our
contributor
base.
There
won't
be
any
general
public,
so
yeah
there
might
be,
it
might
be,
there
might
be
overlap,
but
it's
honestly
a
good
time
if
people
have
questions
like
our
contributors
have
questions
regarding
steering.
A
B
G
D
A
A
C
A
A
B
One
of
these,
like
cross
community
collaboration
sessions
with
the
openstack
community,
I've
gotten
like
a
decent
amount
of
value
out
of
it,
and
at
least
reaffirming
that,
like
we're
talking
about
the
right
things
and
we're
not
coming
out
of
left
field
with
with
different
stuff
like
it's
a
good
opportunity,
knowledge
here
and
the
openstack
community
has
been
great
about
engaging
us
and
inviting
us
because
they
have
this
this
thing
of
cadence.
I
think
we
should
probably
be.
The
thing
we
haven't
done
is
done
the
opposite,
because.
B
D
B
A
H
H
D
H
E
H
D
E
H
A
There
might
be
other
restrictions
around
like
if
they
want
to
use
the
fact
that
they're
sponsoring
us
in
any
sort
of
like
marketing
material,
because
that
was
the
cloudflare
tends
to
like-
include
the
logos
and
things
like
that.
The
projects
that
they
sponsor,
which
I
think
is
generally
okay,
but
that
still
needs
sign
off
from
the
cncf
yeah.