►
From YouTube: Kubernetes Public Steering Committee Meeting 20210913
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
With
that
we
don't
have
too
many
things
on
the
agenda
today.
I
will
kick
things
right
off
with
an
item
I
tossed
on
the
list,
and
that
was
the
renaming
or
the
default
branch
for
kubrick
steering
owned
repos.
A
So
this
is
k-steering
k-funding
general
action
people
does
anyone
know
of
any
dependencies
on
that
one,
or
can
I
just
pull
the
trigger
and
take
care
of
it
later
today.
B
We
have
no
automation,
we
don't
have
any
github
actions,
so
we
should
just
do
it.
Yeah
yeah.
A
A
A
I
think
the
actual
process
is
the
election
committee
has
to
propose
a
timeline,
and
then
we
act
that
one
I
haven't
talked
to
josh
allison
you're
on
the
election.
Oh.
D
Yeah,
well
I'm
a
little
I'm
here
yeah.
I
think
my
my
gut
feelings
is
maybe
push
I
mean:
we've
got
kubecon
coming
up
and
then
steering
election
and
then
just
thinking
about
how
all
those
things
kind
of.
D
Fit
all
in
like
maybe
we
do
need
to
ask
for
more
time.
I
don't
know
I'd
like
to
hear
steering's
steering
committee
thoughts
on
that
one.
Do
you
need.
B
D
E
I
remember
there
was
a
thread
to
steering
with
the
proposed
collection
committee.
Was
that
has
that
actually
been
act
like?
Are
the
people
involved
good
to
go,
or
are
you
still
waiting
on
an
answer
from
us.
A
D
So
yeah
we've
got
the
pr
and
where
it's
got
the
election
offices
but
yeah
the
on
what
josh
has
left
here.
The
election
probably
won't
conclude
till
until
november.
A
A
A
A
So
I
guess
allison
if,
if
you
don't
mind
taking
an
ai
to
just
follow
up
with
the
rest
of
the
election
committee
and
see
if
you
know
these
dates
are
the
ones
that
you
do
want
to
propose
and
go
with,
and
then
we
can
act
on
it
either.
You
know
preferred
either
through
email
on
the
string
public
list
or
like
comment
on
the.
E
Yeah
and
in
terms
of
timelines,
any
it
seems
like
any
delay
would
push
the
push
this
out
even
further,
so
yeah
getting
both
the
election
committee
opinion
on
the
dates
and
our
act
on
it.
This
week
seems
important.
D
Yeah
I'll
look
back
for
the
election
committee
I'll
try
to
get
that
closed
out
within
the
early
half
of
this
week.
A
And
for
the
rest
of
steering,
if
possible
at
least
take
a
look
at
that
pr
for
any
other
potential
comments
on
there.
I
left
one
on
there.
A
Any
other
questions
comments,
thoughts
regarding
the
election
at
this
point
in
time.
A
C
I'm
just
gonna
say
it
sounds
like
we
might
need
like
a
november
one
and
bump
on
our
extension
for
are
effective
dates,
because,
right
now,
it's
like,
I
think,
like
technically
october,
7th
or
something
it
shows
october.
2021
on
the
read
me,
but
I
think
yeah.
If
we
go
according
to
like
zig
zamel
history
or
something
it's
like
october,
7th,
but.
A
Okay,
paris,
you
have
the
next
one.
C
It's
more
of
like
f
fyi
than
anything.
I
don't
really
have
anything
to
show
right
now,
but
I
did
start
a
dock
that
I
don't
want
to
share
it's
too
rough
right
now,
I'm
just
kind
of
pitter-pattering
along,
but
it's
on
sort
of
a
sustainability
plan
for
testing,
docs,
controvex
and
other
support
that
we
can
take
to
the
governing
board.
C
This
is
sort
of
out
of
the
box
stuff
that
we
haven't
talked
about
before,
like
the
idea
of
creating
some
kind
of
center
of
excellence
inside
of
cncf,
whatever
I
think
there's
like
four
ideas
on
there
right
now
that
I'm
fleshing
out,
I
gave
the
chairs
a
heads
up,
and
the
last
chairs
and
tech
leads
meeting
that
this
was
happening.
Bob
did
that
for
me,
thank
you
bob.
C
So
a
couple
people
know
that
you
know
the
ideas
are
sort
of
swirling
around.
I
told
chairs
to
like
think
big
and
also
collect
any
areas
that
they
know
need
support,
especially
if
there's
only
one
active
individual
in
that,
so
that
we
can
start
to
collect
like
where
we
might
need
contractors.
C
If
that's
the
thing
again
that,
if
that's
a
thing
and
then
also
sort
of
the
a
leg
off
of
that,
there's
already
been
talk
at
cncf
level
from
lucas
and
other
people
within
the
cloud
native
community
with
other
projects
who
are
very
interested
in
staffing.
Things
like
go
yaml
and
jason
iterator
and
things
that
only
have
one
active
maintainer
right
now,
but
affect
multiple
projects
within
the
community.
Not
just
kubernetes.
C
More
discussion
will
be
had
with
individual
chairs
and
maintainers
in
those
areas,
including
dimms
and
dems's
hand.
Just
went
up
so
we'll
get
sort
of
a
plan
together
and
present
it
dims.
B
Yeah,
so
I
forwarded
the
thread
that
was
floating
around
to
steering
private
for
everybody
here
to
take
a
look
yeah
thanks,
paris
for
doing
this.
I
wanted
to
address
specifically
the
questions
from
lucas
about
you
know
some
some
parts
of
you
know
the
parcel
that
is
more
forgiving
than
it
should
be
kind
of
thing.
We
might
end
up
fixing
those
kinds
of
things,
but
we
might
not
be
able
to
adopt
it
in
kubernetes
kubernetes,
because
you
know
that
might
be
a
backward
incompatible
change
for
us.
B
So,
yes,
it's
a
good
idea
in
general.
Yes,
we
we
need
to
fund
some
of
these.
You
know
single
person
or
smaller
repositories
and
maybe
even
take
over
some
of
them,
and
you
know
adopt
them
internally,
similar
to
what
we
have
done
before.
B
Yes,
plus
one
two
getting
some
contractor
help,
but
then,
in
the
end
the
respective
sigs,
like
ap
missionary,
should
be
the
ones
that
will
make
the
decision
of
okay,
whether
that's
an
acceptable
change
or
not.
So
that
point
was
kind
of
missed
in
lucas's
thread
and
I
didn't
want
to
bring
it
up
there,
because
that
would
have
been
counterproductive
to
the
larger
argument
that
we
were
trying
to
make
there.
C
Yeah
and
I'll
work
with
you,
too
dims
on
on
some
stuff
this
week
and
that's
what
I
wanted
to
do.
I
just
wanted
to
do
a
lot
of
due
diligence
and
talk
to
people
and
see
what's
up-
and
I
did
talk
to,
I
think,
almost
all
the
whole
customized
crew
now
about
go
yaml,
so
I
have
their
thoughts
there,
but
yeah
no
anyway
tldr.
C
I
asked
to
chairs,
if
and
through
bob,
if,
like,
there
are
any
other
areas
like
that,
whether
it's
dependencies,
whether
it's
sub
projects,
whatever
where
it's
like
wow
there
really
is
only
one
person
here.
So
that's
at
the
chair
level
right
now
and
that's
kind
of
all.
I
wanted
to
say
about
that.
If
they're.
A
There
wasn't
too
much
from
the
the
chair
meeting
this
last
week,
just
because,
like
it
was
also
enhancements
freeze,
so
only
a
couple
people
actually
showed
up.
It
might
be
worth
starting
a
separate
thread
in
slack
100.
C
A
A
For
us,
as
kubernetes
potentially
bring
like
developing
a
process
on
how
these
things
should
be
approached,
the
general
thought
was
that
this
should
be
turf
to
sig
arch
on
the
specifically
the
code
organization
subproject.
A
A
But
as
we
are
developing
this,
we
should
have
our
own
internal
process.
For
this,
and
another
example
that
was
mentioned
was
the
like:
the
kml,
the
the
the
customized
internal
fork
and
then
the
the
recent
thing
in
there's
an
issue
open
in
korg
regarding
importing
a
forking,
a
repo
that
we
would
maintain
for
another
dependency.
E
Yeah,
I
think
that's
a
good
discussion
for
like
sig
arch,
for
like
the
policy
around
dependencies
and
forking,
and
whether
to
take
on
new
new
dependencies
that
exchange
like
a
standard
library
package
for
some
third-party
thing.
That
seems
like
a
good
place
to
have
that
api
machinery
happens
to
own
most
of
the
libraries
that
I'm
aware
of
that
are
sort
of
these
like
low-level
serialization
libraries.
E
A
B
Oh
paris,
did
you
say
that
you
wanted
to
talk
later
this
week,
yep.
A
Are
there
any
other
thoughts,
questions
comments
regarding
sustainability,
those
sustainability
suggestions
to
bring.
B
Up
big
one
has
always
been
well
recently
is
sick
testing
for
sure
yeah.
In
addition
to
sick
dogs,
which
we
might
have
turned
the
corner,
there.
B
F
Yeah,
so
actually
it's
it's
hippie
hacker
who
is
working
on
it,
so
it's
in
progress.
I
believe
that
we
should
have
more
details
of
it.
Next
month's,
I
don't
have
fact
like
the
current
status-
is
that
hippie
hacker
is
working
on
a
draft
document
and
I
believe
it's
like
on
a
final
stage.
F
F
So
yeah,
that's
that's
that's
the
status,
so
we
are
we're
working
on
this
and
yeah
we'll
we'll
definitely
keep
you
posted
in
this.
B
So
at
some
point,
igor,
when
priyanka
has
taken
a
look,
could
you
please
give
us
a
heads
up
on
steering
private
before
it
goes
public,
yeah,
sure
I'll?
Actually.
F
C
A
I
I
am
100
on
board
with
that
idea,
because
there
are
some
one
big
glaring
issue
on
at
least
on
the
current
proposal,
that.
F
Yeah
yeah
I'll
I'll
affect
this
to
hippie
hooker
like
no,
no,
no
worries,
so
I'm
happy
to
jump
on
a
call
with
you,
like
I'm
myself
and,
and
he
and
probably
some
other
folks
from
from
his
team,
so
we're
happy
to
jump
on
a
call
and
discuss
some
stuff.
F
B
C
F
Problem
at
all
so
I'll
work
with
skipper
hacker,
I'm
I'm
more
act
like
myself
and
more
acting
as
a
reviewer
on
on
the
document
on
this.
This
program,
based
on
my
experience
of
setting
up
the
cloud
provider,
credits
in
the
past
for
kubernetes
and
other
projects,
but
he's
a
person
and
his
team
are
until
working
on
the
program
itself,
so
happy
to
happy
to
work
together
internally
and
to
to
schedule
something
for
for
us
all.