►
Description
Kubernetes Public Steering Committee Meeting for 20221003
A
B
B
A
C
B
Congratulations
to
the
winners
and,
on
behalf
of
the
steering
committee
I'd
like
to
thank
our
election
officers,
kazlin
Noah
and
dims
for
for
running
the
selection,
I
I've
said
it
in
some
other
places,
but
elections
are
really
critical
time
for
the
community.
As
far
as
you
know,
deciding
our
leaders
in
a
democratic
and
fair
and
transparent
way,
and
we
really
appreciate
that
work
that
the
election
officers
put
in
in
running
this
election
foreign.
B
C
Like
tomorrow,
okay,
we
do
have
a
doodle
pull
out,
so
we're
probably
gonna
finalize
when
the
Retro
will
be
today.
It'll
be
kind
of
short
notice.
If
we
change
it,
but
it
looks
like
all
of
the
the
dates
might
be
tomorrow,
but
once
I
can
see
right
now
are
so
but
I'll
send
out
an
email,
letting
everyone
know
exactly
when
it
is
once
we
have
that
settled.
B
F
A
B
B
We
originally
pulled
the
folks
that
were
going
to
be
remaining
on
the
committee
and
I
have
a
list
of
those,
but
Bob
number
and
Ben
expect
to
get
pings
from
me
specifically
on
this,
if
you're
going
to
be
attending
kubecon
and
if
you
would
be
available
to
desire
to
join
these
join
these
two
sessions
yeah,
that's
basically
all
I
had
on
that
one.
Any
questions,
feedback.
B
I
guess
one
thing
I'll
ask
while
we're
here
Bob,
because
you're
also
on
the
contributor
Summit
team,
was
there
any
specific
details
as
far
as
the
request
for
the
the
session?
That
was
that
the
that
it's
being
asked
for
for
the
contributor
Summit?
Is
it
very
similar
to
the
success
that
we
had
in
Valencia?
Yes,.
D
B
C
Jordan
made
a
lovely
suggestion
in
the
chat
for
a
a
doc
to
put
any
asynchronous
feedback
comments
about
the
election
into
so
I
went
ahead
and
just
created
a
document.
If
anyone
has
any
feedback
that
they
would
like
to
share,
and
they
don't
want
to
worry
about
trying
to
make
that
meeting,
please
feel
free
to
share
it.
There
and
I'll
make
sure
that
it
gets
recorded
in
the
proper,
more
formal
locations.
F
For
the
for
the
onboarding
of
the
new
hooks
I
know,
we
have,
we
normally
create
an
issue
that
has
a
checklist
and
then
ask
the
new
folks
to
divvy
up
driving
that
checklist
and
updating
the
template.
For
that
checklist,
I'm
happy
to
spawn
the
issue
and
like
copy
in
the
current
template,
and
then
you
can
tag
people
in
and
start
working.
F
G
B
B
A
H
The
airport,
so
there
is
one
question
so
I
think
I've
been
elected
to
sharing
I,
have
to
step
down
from
the
code
of
conduct
committee
now
and
I,
then
giving
it
something
that
reach
out
to
you
all
about
acting
like
who
is
left
in
line
to
replace
me
and
we'll
also
get
the
Handover
rolling
in
the
code
of
conduction.
So
just
right
now,
I.
Let
the
current
committee
members
know
that
I'm
stepping
down,
but
once
I
know
who
is
going
to
replace
me.
H
B
I
The
policy
discussion
got
complicated
but
pragmatically
our
practices
that
we
stepped
down,
or
we
would
pick
so
what
I'm
hearing
you
say
is
that
you,
you
vocalize
and
tend
to
step
down
so,
regardless
of
anything
else,
simple,
it's
the
AI,
then,
is
on
steering
to
look
at
the
past
election
and
go
through
the
the
next
folks.
In
line
and
we'll
we
will
we'll
take
the
AI
or
I
I
can
take
the
AI
to
go
through
that
and
reach
out,
because
contacts
may
have
changed.