►
From YouTube: Kubernetes Steering Committee Meeting September 20190904
Description
Monthly public meeting
A
C
B
F
B
B
C
A
A
B
B
I
Hi
so
the
way
I
was
thinking
about
this
was
we
wanted
to
given
opportunity
for
the
people
who
are
standing
for
election
to
ask
questions
about
what
what
we
do,
both
internal
both
on
the
private
meeting,
as
well
as
the
public
meeting,
how
the
how
we
do
the
Bolton
process,
how
we
track
milestones
and
things
like
that,
just
to
get
you
up
to
speed
I
mean
that
was
one
aspect
of
it.
The
other
aspect
is
about.
I
You
know
mm
what
we
think
the
future
of
Cuba
raters
should
be.
That
kind
of
that's
a
whole
another
bucket
of
things
that
we
could
talk
about,
but
it's
mostly
open
floor.
It's
up
to
you
all
to
ask
questions.
We
can,
if
you
have
like
a
specific
scenario
or
a
specific
thing
that
you
wanted
to
question
you
know
ask
about.
You
know
why
we
took
a
decision
or
something
like
that.
Then
that
is
another
thing
that
we
could
talk
about
as
well.
I.
J
E
Think
it's
also
worth
saying
that
these
rules
aren't
written
in
stone.
I
think
some
of
the
the
way
that
the
steering
committee
has
acted
initially
I
think
was
a
light
hand
just
because
bootstrapping
that
whole
process
you
know
we
wanted
to
to
make
sure
that
you
know
the
consent
of
the
governed
type
of
thing,
but
I
think
you
know.
As
we
move
towards
the
bootstrap
physicians
aging
out,
you
know,
there's
a
lot
more
sort
of
clear
mandate.
A
Stephen,
you
can
go
first,
so
I'll
drop
three
questions.
Oh
so
one
can
we
if
anyone
had
the
opportunity
to
see
my
nomination
thread,
that
there
were
questions
around
questions
around
like
the
ability
to
run
so
I
think
that
there
could
probably
be
some
clarification
in
documentation.
I
think
we
solved
it
on
the
thread,
but
clarification
and
documentation
would
be
helpful.
A
Don't
think
this
is
the
forum
for
that
I.
Think
overall,
like
the
entire
project
should
be
dedicated
to
that,
but
sig
p.m.
sig
usability,
say:
contributor.
Experience
are
all
great
places
if
you
want
to
help
alleviate
user
pain
and
then
the
individual
SIG's
should
be
helping
on
that
stuff
too.
So
maybe
three
comments
as
opposed
to
questions.
I
can.
C
I
can
jump
in
with
at
least
a
couple
of
pieces.
An
answer,
I
think
the
third
one
is
a
much
longer
discussion,
but
generally
to
Joan's
point
we've
been
doing.
This
is
a
very
light
hand
and
not
and
not
having
it
about
the
the
project
software,
but
having
it
about
how
the
project
is
organized
and
run
so
the
software.
C
So
it
depends
on
who
you
mean
by
user
in
this
case,
because
if
it's
user
contributor
that's
different
and
the
steering
committee
might
have
more
opinions
about
it,
but
if
it's
an
end
user
of
kubernetes,
then
I
agree.
The
whole
project
needs
to
be
paying
attention
to
that
and
just
the
same
way
we
have
contributor
experience.
We
at
some
point
needs
user
experience,
focus
so
then
backing
up
from
that
one
one
actually
I
may
have
to
go
to
the
first
one.
C
First,
the
first
question
was
who
can
run
and
it
may
be
solved
as
well
in
the
thread
and
that's
that's
grand
the
original
thought
was
choosing,
and
this
is
how
the
bootstrap
committee
came
to
this.
This
plan
was
we,
we
couldn't
either
constrain,
who
could
run
or
who
could
vote
in
and
then
from
there
being
able
to
manage
the
process
a
lot
more
evenly
and
even-handedly
and
avoid
astroturfing,
and
we
decided
that
we
wanted
to
limit
who
could
vote
more
than
we
wanted
to
limit?
C
Who
could
run
because
that
would
self
select
for
people
that
were
the
governed
functionally
the
people
in
the
project
to
choose
someone
that
they
respect
may
have
come
from
industry
and
not
participated
for
long,
but
they
know
has,
you
know,
has
done
good
worked
on
the
past
or
someone
maybe
who
has
been
in
the
project
a
long
time,
but
you
know
isn't
particularly
publicly
well
known,
but
the
people
who
are
in
the
project
know
them.
So
we
wanted
that
to
be
the
case
and
now
I've
lost
the
middle
question.
C
E
E
We
can
do
to
shape
behavior
or
folks
to
actually
move
the
project
in
a
certain
direction
and
again
light
hand.
We
don't
want
to
be
overbearing
with
it,
but
like
the
idea
is
that
the
steering
committee
does
have
some
levers
that
they
can
use
to
move
things
like
asking
the
CNC
F
for
money
and
Men
helping
to
manage
that
budget
to
be
able
to
actually
bring
folks
to
really.
You
know
do
more
in
certain
areas
right,
I,
think
you
know
the
Sigma
X
is
a
very
example
there
and.
E
I
B
The
main
goal
is
to
head
off
those
kinds
of
issues
and
to
set
up
the
project
so
that
it
functions
properly.
So,
in
the
past
couple
of
years,
a
lot
of
work
has
gone
into
you,
formalizing
the
rules
and
guidance
in
conventions
around
how
our
six
formed
and
dissolved
our
working
groups
formed
and
dissolved.
What
are
you
that
even
working
groups
was
just
brought
up
so
yeah
Jason
created
a
bunch
of
documents
around
there,
I
just
double
checked
those
are
in
the
community
repo.
Recently
we
introduced
user
groups.
B
Right
charters
was
didn't
just
mentioned
in
a
comments.
Phil
and
others
put
work
into
that
you
know.
So
a
lot
of
the
focus
has
been
on
setting
up
laying
that
groundwork
and
setting
up
the
structure
so
that
the
project
can
function.
The
funding
is
a
recent
bit
that
has
been
coming
into
place
about.
How
does
the
project
request
funding
from
the
scenes
yeah
and
manage
that
in
the
past?
A
lot
of
these
things
were
done
informally,
and
you
know
as
the
project
scales
and
matures
and
people
come
on
and
off
the
project.
H
Yeah
and
I
think
that's
been.
Such
a
challenging
thing
is
to
just
not
take
the
easy
route
and
fix
the
problem
really
quickly.
It's
that
the
process
that
Brian
described
like
you
really
got
a
it's
it's
challenging,
but
you
really
gotta
like
figure
out
what
the
process
should
be
and
and
have
it
vetted
and
take
the
critiques
and
then
find
some
compromises
and
collaborate
and
iterate,
and
until
you
never
want
to
look
at
that
piece
of
document
again
so
yeah
I
mean,
like
people
I,
think
I.
Think
that
staring
is
this
like
I
place.
H
B
And
just
to
follow
up
on
that
just
one
simple
example
from
the
most
recent
election-
and
this
isn't
the
first
election
we've
had.
But
you
know
we
have
some
rules
written
about
things
like
a
certain
number
of
voting.
Members
from
different
organizations
must
+1
the
candidate
for
them
to
qualify,
but
if
you
look
at
all
the
plus
ones,
nobody
provides
the
information
we
need.
It's
actually
that
the
plus
wants
right.
So
that's
we're
gonna
post
for
them
the
election
process
and
what
went
well
and
what
didn't
well-
and
you
know
definitely
things
like
that.
H
I
had
no
idea
how
to
suck
any
of
that
up.
I
have
had
never
done
that
before
and
I
just
had
to
come
up
with
document
and
Brandon
gave
me
a
lot
of
good
feedback,
and
then
you
know
we
pass
it
off
to
the
steering
committee
and
they
did
around
and
looking
back
it
totally
wasn't
perfect,
and
you
know
as
an
engineer,
you
just
have
to
be
okay
with
like
imperfect
work
and
you
got
to
iterate.
So
so
that's
just
something
to
be
said:
yeah.
I
Oh,
it's
a
lot
of
research
about
how
people
have
done
this
before
in
other
organization,
other
foundations
and
try
to
learn
from
them
and
try
to
talk
to
them
about
what
works
for
them.
What
they
could
have
done
differently
and
bring
that,
as
you
know,
feedback
when
we
are
doing
something
is
also
something
very
important.
C
Yeah,
this
is
less
about
advocating
any
particular
direction
as
some
just
finding
and
aligning
interests
so
that
the
project
can
move
forward
and
to
Philips
point
delegate
as
much
as
possible
out
to
the
the
other
groups.
I
think
it
was
Tim
that
said
arbiter
of
last
resort,
which
is
a
great
way
to
describe
it.
H
I
A
Okay,
so
we
mentioned
we
mentioned
funding
CNCs
funding.
There
was
a
thread
going
at
some
point
regarding
like
diversity,
scholarships
for
kube
Khan.
Other
events
I
know
that
there
has
been
some
documentation
and
process,
probably
a
PR,
or
that
is
either
up
or
emerged
at
this
point,
but
I'm
starting
to
get
questions
like
on
the
release
team.
So
I
wanted
to
see
where
we're
at
with
that.
Okay.
I
I
can
I
can
handle
it,
so
the
diversity
scholarship
is
run
by
CN
CF,
but
then
we
figured
out
that
there
are
people
that
we
would
like
to
bring
to
the
contributor
summit,
for
example,
and
we
want
a
process,
for
you
know
getting
some
funding
for
it,
as
well
as
some
selecting
some
people
who
wish
to
invite
to
the
contributor
summit
and
then
cube
con.
So
currently
we
have
a
proposal
that
Paris
and
George
wrote
up.
It
is
in
a
PR
form.
It
has
not
it's
currently,
we
are.
I
You
know
the
rest
of
the
people
on
the
steering
committee
are
looking
at
it,
but
there
is
a
hold
on
that
PR
right
now,
because
CN
CF
mentioned
that
Dan
Cohen
mentioned
that
they
he
CN
CF
is
trying
to
do
the
same
thing
and
trying
to
roll
the
same
process
out
for
all
the
projects
where
the
projects
can
come
up
with
a
set
of
people
that
they
would
like
to
invite.
For
us.
I
It's
about
people
who
are
who
have
roles
in,
for
example,
the
release
team,
or
you
know,
contrib
X
or
you
know,
who
would
not
be
able
to
travel.
Otherwise.
We
would
like
to
bring
them
and
who
might
not
fit
into
the
diversity.
You
know
category
there
as
well
as
the
other
issue
is
that
they
have
only
a
limited
number
of
people
that
they
can
get
as
well
right
and
that
needs
to
be
spread
across.
You
know
the
entire
CNC
F,
so
we
would
like
to
prioritize
some
people
that
we
can
bring
with
us.
I
I
E
E
I
C
C
If
we
give
airtime
on
our
steering
committee
meeting
to
people
who
have
nominated
nominated
themselves
or
nominated
others
that
this
could
turn
into
sub
speeches,
whereas
I'm
more
interested
in
the
questions
at
this
point,
because
we
didn't
make
any
sort
of
announcement
that
anyone
who
has
nominated
what
get
time
to
to
speak
broadly
so
I'm
a
little
bit
worried
about
that.
Anyone
else
have
thoughts
or
concerns
about
this.
No.
H
H
K
E
Think
this
is
urgent
but
important,
but
I
would
love
to
see.
Just
in
that
idea
of,
like
you
know,
carrots
and
sticks
I'd
love
to
see
the
steering
committee.
You
know
curate
a
sort
of
hotspots
and
actually
be
like
hey
kudos
to
the
folks
who
are
working
on
this
to
essentially
provide
a
little
bit
of
direction,
and
then
you
know,
whatever
you
know,
support
necessary
to
say
like
hey.
These
are
the
things
that
we
think
are
critical
in
the
project
right
now
or
we
need
more
help.
J
Yeah
I
want
to
echo
that
sentiment
in
that
what
we've
seen
over
time
and
I
don't
know
how
to
solve.
This
is
partially
governance,
and
this
is
partially
beyond
governance.
Is
that
how
do
we
prevent
the
tragedy
that
commas
that
we
already
see
the
following
us
today,
like
many
of
us
already
worked
in
this
project
for
a
long
time,
but
we
see
it
already
like.
There
are
key
areas
of
project
that
have
been
underfunded
and
it's
very
difficult.
J
A
J
Think
that's
a
key
problem
with
this
project
or
any
open
source
project
for
that
matter.
It's
like
how
do
you
make
sure
that
vested
interest
parties
did
not
just
try
to
extract
value
from
the
project,
but
also
help
to
solve
common
problems
that
exist
across
the
entire
state
space
and
don't
see
it
as
a
lever
for
some
form
of
differentiation
right?
Sometimes,
some
some
history
for
open
source
business
models
indicates
that
having
a
chaotic
bad
upstream
is
actually
in
their
best
interest.
B
I
I'll
say
what
I
usually
say
in
this
in
this
kind
of
topic
right,
so
we
are
currently
geared
towards
full
time
contributors
who
are
working
on
the
only
on
this
project.
You
know
they
might
be
doing
other
things,
but
mostly
they
are
doing
Cuban
artists,
whether
inside
or
outside,
we
are
not.
We
are
not
geared
towards
occasional
contributors,
we
don't
use
the
longtail,
so
that
is
one
of
the
things
that
have
been
trying
to
encourage
in
different
spaces.
I
So
that
is
something
that
I
would
like
to
continue
to
see
happen.
Especially
you
know
in
specific
six
things
are
okay,
but
then
we
don't
have
people
who
can
span
six.
We
do
not
have
a
replacement
for
Jordan,
for
example
right,
so
you
know
people
have
to
grow
beyond
their
individual
SIG's
and
then
the
so
it's
harder
for
people
to
do
that
now.
I
think
I
feel
and
it's
difficult
to
cultivate
people
to
get
to
that
point,
and
we
have
to
do
something
better
and
we
have
to
figure
out
ways
and
means
of
doing
it.
A
B
Going
back
to
Michelle's,
question
and
I
think
it's
along
the
lines
of
what
Tim
was
saying
about
tragedy.
The
comments
like
one
thing
that
I
find
very
challenging
now
is
just
hatred.
Understanding
what's
going
on
across
the
entire
project
is
super
challenging
like
if
you
think
about
an
engineering
effort
involving
hundreds
of
Engineers
broken
down
into
several
sub
teams,
there
would
be
a
lot
of
management
infrastructure.
There
would
be
project
management,
there'll,
be
people
managers,
there
would
be
ways
for
information
flow
processes,
we're
kind
of
lacking
that
and
the
organizational
complexity
is
quite
high.
B
B
One
thing
I
found
in
the
past
is
that
new
people
coming
to
the
project
weren't
aware
that
those
areas
were
underfunded,
and
occasionally
we
have
pleas
for
people
to
help
with
VRI
or
with
Docs
or
some
other
specific
area,
but
managing
that
over
time,
like
how
much
work
is
in
the
backlog
and
how
much
progress
are
the
different
areas
making
and
where
do
we
have
gaps
is
something
that
we
haven't
really
addressed
very
holistically
in
the
project,
so
that
was
some
was
pitched
stews.
Sic
p.m.
B
at
some
point
and
we
tried
various
things
like
having
the
six
report
summaries
of
what
they've
been
doing
to
the
community
meeting
and
things
like
that.
But
none
of
them
other
things.
We
have
tried,
whether
it's
the
world
board
or
whatever
seems
to
really
adequately
address
the
problem,
so
I
think
new
ideas
and
that
space
would
be
valuable.
So.
C
I'll
jump
in
and
tight
as
to
what
Stephen
was
saying
as
well,
because
one
of
the
things
that
I
think
has
been
a
real
challenge
with
the
first
many
years
of
this
community
has
been
the
development
of
artifacts
that
aren't
video.
We
do
a
lot
of
things
in
video
and
development
of
searchable
stories
and
decisions
and
communication
in
that
way,
so
to
Stevens
Point.
How
do
we
get?
C
You
know
across
the
sink
communication
to
Brian's
point
we've
asked
things
to
you
know,
write
summaries
and
share
summaries
across
the
community,
and
that
has
been
more
and
less
effective,
depending
on
the
sake.
But
this
is
a
this
is
an
ongoing
problem
and
it's
one
that
that
we
have
not
yet
mastered,
because
there's
there's
just
too
many
lines
of
communication
and
not
a
good
way
to
get
a
summary
perspective
of.
What's
going
on.
I
All
right,
another
thing
that
comes
to
mind
is
you
know:
we've
always
talked
about.
We
need
state,
we
need
to
stabilize
the
code
and
we
need
you
know
we
are
not.
We
are
not
getting
a
chance
to
do
that
and
typically
the
number
is
somewhere
timeframe
is
a
good
good
time
to
do
that.
But
then
we
don't
want
to
push
the
you
know,
mandate
from
the
top.
It
needs
to.
You
know,
come
from
the
bottom
and
how
do
you?
How
do
you
tell
six
to
put
the
brakes
on
the
features
and
prioritize
the
bug
fixes?
I
B
B
D
Wanted
to
say
that
most
of
the
problems
that
we
just
talked
about
here
are
problems
with
many
open
source
projects.
So
we
have
to
also
think
about
that,
and
it
might
seem
daunting
to
us
because
we're
living
it,
but
other
people
live
this
too,
and
I've
been
spending
a
lot
of
time
with
other
open
source
projects
in
talking
with
them
about
how
we
consult
this
together.
So
I
think
that
that's
an
opportunity
for
us,
because
people
look
up
to
us
as
a
very
large
project.
D
L
Yeah,
it
was
just
a
comment:
I
mean
on
the
and
I
do
have
a
question
as
well
on
the
back
of
what
DIMMs
was
saying.
Is
it
actually
the
responsibility
of
the
steering
committee
to
set
technical
direction
and
say
we
should
feature
on
stability
rather
than
enhancements?
Is
that's
not
stated
in
the
Charter?
So
I
was
just
wondering
if
that's
actually,
that
should
be
delegated
out
in
my
opinion
and
freestanding
if
SIG's
want
to
take
that
on.
It
is
in
the
Charter,
the.
L
I
was
just
reviewing
so
yeah
I.
Would
my
question
now,
while
I
will
have
the
microphone
is
really
how's
the
dynamic
tin
and
have
you
found
this
I
think
we
touch
them
too
briefly,
an
effective
forum
to
make
decisions
between
the
parties
that
members
of
the
steering
committee
is
this
the?
What
are
the
forums
that
you
have
and
are
they
effective.
L
G
H
I
think
we've
grown
a
lot
in
the
way
that
we
communicate
and
hash
out
decisions.
I'm
really
proud
of
it.
I
think
that
a
lot
of
really
great
decisions
have
gotten
made
at
in-person
conversations
and
I.
Looking
back
I
really
wish.
We
had
had
more
time
for
those
kinds
of
get-togethers
and
they've
just
been
really
effective.
H
F
Ellis
is
there
got
it
not
trying
to
cut
you
off
either,
but
I
just
wanted
to
like
I.
Think
in
my
two
years
now
with
the
committee
most
of
what
I've
observed
is
we
tried
to
decide
who
is
going
to
make
a
decision
who
we
are
going
to
empower
to
do
something
versus
us
doing
it
ourselves
and
so
I
would
say
in
my
experience
so
far,
our
bias
towards
empowering
others
to
make
more
local
decisions
has
been
largely
effective
and,
if
that's
the
root
of
your
question,
I
think
thus
far.
That
approaches
worked.
C
The
other
component
of
this,
which
I
was
putting
in
the
chat,
is
that
as
leadership
across
the
project,
we
all
have
to
work
to
align
interests
so
sometimes
with
something
like
a
you
know,
stability
release.
There
would
be
a
lot
of
conversations
among
the
leaders
of
the
project,
so
that
would
be
leaders
of
large
SIG's.
That
would
be
leaders
of
sake
architecture
that
would
be
all
of
Sagarika
texture.
That
would
be
the
steering
committee,
but
the
the
idea
being
there
is
work
from
this
group
also
to
align
interests,
as
well
as
delegating.
E
Yeah
I
would
say
that
the
I
mean
the
the
CNC
F
community
and
the
kubernetes
community
are
actually
pretty
different.
There's
a
different
flavor
there
and
I
think
you
know
we
look
at
things
like
SIG's
in
the
CNC
F.
They
have
the
same
name
as
cigs
and
kubernetes,
but
they're
really
sort
of
different
purposes,
different
different
ways
of
working,
and
so
you
know
slipping
that
clutch
between
sort
of
the
the
needs
and
the
motivations
and
the
way
that
kubernetes
works
and
the
way
the
CNC
F
work
is
is
sometimes
pretty
tricky.
A
All
right
can
ask
more
questions
so
with
this.
So
what
do
you
think
of
teams
so
like
we
have
quite
a
few
governance
structures
and
we
have
started
to
or
I
think
myself
and
multiple
people
have
started
to
see
like
things
crop
up
that
are
working
group
esque,
but
should
exist
for
a
longer
time,
then
just
the
fuzzy
span
of
like
what
a
working
group,
as
so
like
product
security
committee,
comes
to
mind.
It
was
a
team.
A
It
became
a
committee
I,
don't
know
why
exactly
because
it
like
operates
a
little
bit
of
both
whether
they're,
you
know
there's
kind
of
a
little
bit
of
both
there
test
in
for
on-call
working
group.
Cates
infra,
like
those
are
all
things
that
could
potentially
be
a
team,
but,
like
don't
have
like,
we
don't
have
the
idea
of
a
team
yet
like
it
needs
to
like
those
are
things
that
need
to
consistently
be
staffed
for
the
project
to
be
successful.
A
I
I
can
talk
about
the
kids
in
Frey
if
you
want,
or
if
somebody
else
wants
to
talk.
Please
tell
me
so,
for
the
kids
in
we've
tried
to
find
the
right
bucket
for
the
current
situation
and
one
of
the
things
for
kids
in
front
of
what
we
were
saying
was
we
don't
want
the
group
to
exist
for
a
really
long
time.
I
A
E
You
can
organize
that
I,
don't
know
that
we
need
to
actually
have
another
top
level
thing
under
kubernetes,
but
if
there's
support,
that's
needed
for
sort
of
keeping
track
or
whatever
I
think
that
that's
something
that
you
know
everybody
would
be
open
to,
but
I'm
not
sure
that
we
need
a
separate
thing
from
sake.
That'd
be
my
date,
but
you
know
yeah.
B
Like
what
are
you
specifically
looking
like?
What
do
you
need
like,
because
the
governance
structures
we
have
in
place
now
exist
for
a
couple
different
reasons?
Some
are
like
for
to
help
define
decision-making
and
ownership.
Others
are
to
provide
like
communication
tools,
such
as
discussion
forums
and
any
times
as
that
sort
of
thing.
Is
there
like
a
specific
need?
You
have
that
you
feel
the
existing
structure
doesn't
fulfill.
A
I
guess
not
with
the
the
same
chat
happening
as
well
like
we
served
first
thing
release.
We
reason
I
spun
up
the
release
managers
group,
which
lives
inside
of
a
release,
engineering,
sub-project
right
and
that's
essentially,
the
aggregate
of
build
admins
who
are
Googlers
with
the
access
to
like
push
the
button
to
sign
packages
on
behalf
of
kubernetes,
the
branch
management
squad,
the
patch
release
team
and
the
sig
chairs
right.
There's
also
like
the
github
administration
team,
so
I
think
that
maybe
some
projects,
that's
the
right
place
for
that
right.
A
So
noting
again
so,
Paris
mentioned
something
about
the
sub-project
owners
are
responsible
for
staffing,
I'm,
not
sure
how
that,
like
I,
think
there's
a
wider
staffing
need
for
things
like
Kate's
infra,
because
we're
basically
saying
that,
like
one,
this
needs
to
be
a
it
needs
to
not
be
a
Google
effort
needs
to
be
a
community
effort.
It
needs
to
be
funded
by
the
community
essentially
or
there
has
to
be
a
mandate
for
the
companies
that
are
participating
in
that
right.
So
I
think
that,
like
I,
I
I,
don't
know.
P
B
That
has
been
dialogue
between
the
project
and
individual
companies
with,
for
example,
if
we
needed
to
staff
documentation.
Yes,
this
seems
you
have
did
fund
one
person,
but
we
also
went
to
other
individual
companies
to
ask
for
help
or
credits
for
testing
is
another
example
that
has
come
up.
You
know,
so
it's
pretty
easy
to
tell
like
which
companies
have
heavy
investments
in
the
project
and
in
terms
of
in
terms
of
people
in
terms
of
its
role
in
their
products.
B
E
Mean
they
can
work
through
the
steering
committee
also
like
I,
think
if
a
cig
came
to
the
steering
committee
saying
like
this
is
a
critical
thing
for
the
project
and
like
we
don't
have
enough
people
what's
problem
solved
together.
I
think
that's
a
totally
appropriate
interaction
with
the
steering
committee
Michelle.
C
L
E
Mean
I
think
part
of
it
is
that,
like
you
know,
I'm
excited
that
we're
getting
new
folks
in
because
bring
new
perspective
right.
So
I
think
you
know,
we've
been
talking
about
a
bunch
of
stuff
here,
but
like
I,
also
think
that,
like
there's
problems
and
creativity
and
ways
to
solve
them
that
you
know
you
know
world
Toby's
at
this
point,
I
think
new
new
passion,
new
creativity
is
actually
going
to
be
awesome.
So
I
don't
want
to
put
my
thumb
on
the
scale.
B
H
I
think
that
we
well
like
there's
so
many
things.
I
could
write
an
essay
but
I
think
we
needs
to
use
the
role
board
more.
That's
one
piece
of
advice:
I
will
write
dims,
you
know
what
I
will
write
an
essay
I
will
blog
post
coming
soon,
yeah
just
just
be
super
patient.
There's
a
lot
of
like
Joe
mention.
H
D
So
we
are
doing
the
2019
contributor
survey
from
contributor
experience
and
I
wanted
to
ask
all
the
steering
committee
members
if
you
want
to
post
on
the
community
at
all.
Please
comment
on
that
issue.
There's
some
other
retro
items
from
last
year
too
for
what
we
learned
about
the
survey.
But
please
comment
I'd
like
to
get
this
out
ASAP
with
the
deadline
to
have
something
pretty
buy
the
contributor
summit
in
November,
so
that
we
can
present
some
of
that
data
there.
P
I
D
D
N
George
yeah,
just
real
quick,
just
a
reminder
that
the
deadlines
for
everyone
is
next
Wednesday.
Exactly
week
from
today.
Those
of
you
running
you
need
to
have
your
candidate
BIOS
put
in
there.
Please
don't
put
it
off
it's
hard
to
get
like
the
300
words
right
and
then,
after
that,
in
about
a
month
from
now
well,
the
election
will
be
concluded
so
to
remind
everybody.
I
will
continue
to
post
every
Wednesday
the
status
of
that
week.
The
upcoming
deadlines
on
the
kubernetes
mailing
list
thanks.
I
I
N
We've
been
peeing
the
people
directly
into
the
voters,
MD.
Actually,
that
reminds
me
don't
assume
that
you're
in
voters
MD
everyone
please
go
through
there
and
check
I
might
find
a
few
instances
where
people
have
like
their
github
thing
misconfigured
or
something
and
we're
getting
the
right
things
and
we
can
work
through
it.
That's
all
easier
to
do
before
the
ballots
go
out.
Would
you
put
a
link
in
the
doc?
I
will
do.
B
B
B
B
B
Okay
from
Joe
a
late
take
the
best
thing
as
he
can
do,
is
activate
others
find
Stoke
and
harness
the
energy.
The
community
from
Sarah
+1
Joe
SC,
isn't
a
platform
for
driving
an
individual
issue,
much
more
about
aligning
interest
in
learning
from
the
pinna
t,
Clayton
Derrick
+1,
and
that's
all
on
that
topic.
Wait.
H
No
I
have
one
more
one:
more
okay,
y'all
should
really
get
to
know
each
other
super
well
I'm,
like
so
ready
to
pass
this
baton.
I,
don't
know
if
y'all
can
tell,
because
I'm
really
excited
I'm
really
excited
for
fresh
blood,
but
but
yeah,
so
y'all
should
get
to
know
each
other
really
well.
I
think
we
all
have
different
strengths
like
like.
If
I
really
need
to
hammer
out
a
document,
I'll
be
like
Phil.
H
Can
you
please
help
me
because
I
know
that
it
will
go
to
completion
and
if
I
am
like
I,
don't
want
to
deal
with
this
particular
issue?
Because
I
don't
have
the
bandwidth
I
know
Jim's
can
just
like
you
know,
take
off
with
it
and
I.
Don't
really
like.
You
know,
think
about
anything.
So
like
there's,
every
person,
I
realized
has
a
strength.
H
J
B
B
D
I
think
I
think
you're
next
I
think
you
actually
do
have
one
more
meeting.
We
don't
announce
the
winners
until
the
third
right
George
or
it's
the
fourth
the
day
after
yeah
you'll
actually
have
your
right.
The
third
sorry
now
you'll
have
one
more
you'll,
have
one
more
full
meeting
with
the
bootstrap
community.
So
this
is
not
your
last
one.
Okay.