►
From YouTube: Kubernetes Steering Committee Election Q+A 20200831
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
Hello:
everyone
today
is
monday
august
31st
2020..
This
is
the
kubernetes
steering
committee
election
candidate
q.
A
today's
meeting
is
an
opportunity
for
candidates
for
the
kubernetes
syria
committee
election.
This
fall
to
ask
questions
of
the
current
kubernetes
steering
committee,
a
reminder
that
this
meeting
is
like.
As
with
all
meetings
we
are
subject
to
the
kubernetes
code
conduct,
please
be
excellent
to
each
other.
This
meeting
is
also
being
recorded,
the
so
one
of
the
the
the
stated
goals
for
this
meeting
again
I'll
I'll
iterate
from
the
email.
A
So
this
is
not
a
candidate
pitch
session.
This
is
not
a
an
interview
to
to
see
if
candidates
are
like
fit
for
this.
This
kind
of
role.
This
is
an
opportunity
for
candidates
themselves
to
ask
questions
of
us
to
make
sure
that
anything
that
the
candidates
have
the
information
they
need
to
to
kind
of
like
decide
for
themselves.
Is
this
a
role?
That's
right
for
me
and
kind
of
understand
better
what
we
do
before
this
meeting.
We
had
sent
out
a
a
form
kind
of
asking
like
asking.
A
If
anybody
had
any
questions
ahead
of
time,
we
did
not
get
any
responses
to
that.
So
I'm
at
this
point
I'm
going
to
open
up
to
the
floor.
A
If
you
have
a
question,
I'm
going
to
try
and
like
go
in
a
rotation
like
one
question
at
a
time,
if
somebody
has
something
they
would
like
to
ask
like
please,
please
mute
yourself
and
feel
free
to
ask,
but
I'm
going
to
make
sure
that
we
give
everyone
an
opportunity
here
to
answer
questions
as
opposed
to
you
know
a
question
and
then
like
five
follow-ups,
we'll
want
to
get
have
a
little
bit
of
flow
to
this.
The
session.
B
I
I
was
actually
sort
of
wondering
what
is
something
that
you
wish
you
would
have
been
told
before
you
started
the
job
like
in
some
ways
I
feel,
like.
I
don't
know
the
questions
to
ask,
so
you
have
the
benefit
of
hindsight.
So
what
is
something
this
is,
I
guess,
for
anyone
and
around
the
table.
What
is
something
you
wish
you
had
been
told
before
you
started
the
job.
A
Okay,
I'll
I'll
speak
up.
First
then
so
it's
this
is
this
within
the
community.
This
is
a
very
unique
role,
because
there's
no
definition
around
it
there's
all
sorts
of
weird
things
that
end
up
coming
up
to
steering
that
you
can't
really
be
prepared
for
and
for
the
most
part
again,
because
we
have
very
clear
technical
delegation
of
things.
A
There
are
human
issues
that
end
up
coming
up,
so
the
the
biggest
thing
that,
like
I,
I
like,
I
kind
of
knew
in
my
brain,
but
you
don't
really
know
until
you're
in
the
hot
seat
is
like
how
many
weird
human
issues
get
pushed
up
to
you
that
are
like.
Can
you
please
have
an
opinion?
Can
you
please
speak
on
behalf
of
this
very
like
broad,
diverse
community
of
contributors
and
there's
a
there's,
a
lot
of
like
gut-searching
kind
of
moments
where
you're
like?
A
I
don't
really
know
what
the
right
answer
is
here,
but
I
need
to
just
kind
of
you
know:
do
do
my
best
to
kind
of
figure
out
what
it?
What
is
the
right?
What
is
the
right
course
of
action
here
to
take
referring
back
to
the
very
clear
community
values
that
we've
defined
over
the
last
you
know
six
years
or
so
so
that's
that's.
A
The
biggest
one
is
like
be
prepared
for,
like
the
human
issues,
like
the
human
interaction
issues,
the
human
like
how
people
feel
and
the
emotional
issues
that
come
up
as
part
of
the
project
because
the
technical
stuff,
we
have
a
pretty
kind
of
clear
technical
escalation
path
for
figuring
those
issues
out.
C
Okay,
I
was
just
gonna
add
one
small
point
to
that.
Is
that
when
I
was
coming
onto
steering,
I
was
not
aware
of
how
much
of
like
pr
like
public
relations,
pr
or
marketing
related
stuff
would
be
involved.
I
mean,
I
wouldn't
say
we
do
like
marketing,
but
it
still
involves
representing
the
kubernetes
project
and
a
part
of
it
comes
down
to
hey
how
is
kubernetes
being
represented
on,
say,
twitter
or
any
other
news
website,
article
or
anywhere
else,
and
making
sure
that
nothing,
that's
not
accurate.
C
D
D
I
mean
this
is
pretty
typical,
open
source
stuff.
I
feel
like
a
lot
of
the
work,
is
actually
really
invisible
and
it's
consensus
building,
whether
that's
you
know,
blasting
stuff
out
and
having
a
group
conversation
or
having
sort
of
one-on-one
conversations
to
get
pulse
checks
and
sort
of
get
more
context,
but
I
have
found
that.
D
D
I
I
think
we've
gotten
better
about
routing
those
to
the
appropriate
venues,
but
it
helps
to
to
take
your
time
and
understand
the
full
context
of
what's
being
asked,
as
opposed
to
presenting
a
strong
face
that,
like
totally
enforces
the
values
of
the
community
right,
like
sometimes
pausing
is,
is
appropriate.
D
D
A
D
One
of
whom
just
joined
the
question
was:
is
there
something
you
wish
you
had
been
told
like?
What
would
you
tell
your
yourself
about
joining
the
steering
committee.
E
I
I
just
want
to
say
one
thing:
we
have
a
lot
of
power
and
the
best
way
to
use
it
is
not
to
use
it
at
all,
it's
kind
of
counterintuitive,
but
you
know
nobody
should
feel
that
we
are
there.
You
know
nobody
should
feel
our
touch,
that
that's
the
way
I
feel
and
feel
about
it.
A
Okay,
opening
it
back
up
to
new
questions
from
candidates.
F
G
H
A
And
anything
like
I
said
I
would
say
pretty
much
anything
that
we
try
and
do
like
from
when,
when
you're
looking
at
it
from
the
top
of
the
pyramid
from
the
steering
point
of
view,
the
amount
of
like
you,
you
don't
want
to
make
the
wrong
decision.
You
want
to
have
like
the
right
amount
of
touch
like.
A
As
you
know,
jim
said,
you
know,
people
shouldn't
feel
impacted
by
decisions
that
steering
makes
at
least
adversely
impacted
by
decisions
that
that
steering
makes
so
things
like
yeah,
like
an
and
the
annual
report
process
that
we're
trying
to
do.
It's
like
incremental
changes
to
make
it
better
like
reviewing
and
making
sure
that
we've
got
like
the
right,
the
right
process.
It's
tuned
correctly,
something
like
that
like
we're,
we're
still
kind
of
going
through
that
process
and
it
yeah
it
is
definitely
taking
longer
than
we
expected.
A
I
I
would
also
say:
2020
has
just
been
a
weird
year
on
the
whole
for
trying
to
make
changes
to
any
process
but
yeah,
I
I
think
that's
probably
the
biggest
one
as
I'd
agree
with
paris
like
the
annual
reports.
You
know
we
started
that
pretty
much
at
the
beginning
of
2020.
A
That
was
like
a
january
february
kind
of
thing
that
we
were
we're
starting
to
talk
about
that
process
and
it's
it's
lingered
on
not
for
any
like
anyone's
fault
or
anything
just
that
going
through
the
process,
iterating
tuning
and
then
getting
it
rolled
out
with
with
working
groups.
And
now
it's
just
taken
time.
I
This
will
be
my
third
year
on
steering,
I
would
say,
I
kind
of
think,
maybe
a
kubernetes
answer
to
a
kubernetes
governance
question
like
in
the
in
my
first
year
on
steering.
We
spent
a
lot
of
time
talking
around,
like
what
sigs
are
and
what
working
groups
were
and
working
through
everyone's
charters
and
trying
to
get
language
right,
and
I
feel
like
we
were
trying
to
figure
out
the
spec
part
of
our
api
model
or
governance
model
and
that
took
longer
than
one
would
have
realized.
I
Even
if
the
output
at
the
end
was
largely
a
small
readme.md
or
charter.md
file
that
linked
to
a
broader
governance,
and
then
I
think
what
we
didn't
do
in,
maybe
we
could
always
do
for
future
members
who
come
on
is
when
we
define
a
policy
like
just
like
in
cube.
We
have
a
spec,
we
didn't
always
think
through
the
status
bit,
and
so
I
think,
christopher's
answer
around
the
just
the
the
health
check
on
how
things
are
going.
I
I
think,
as
kubernetes
is
maturing,
we'll
just
spend
more
time
trying
to
figure
out
how
to
get
better
status
and
then,
where
I
think
we
still
have
struggles
are
how
to
actually
find
the
right
carrots
and
sticks
to
better
align,
spec
and
status.
But
at
this
point
like
I
feel
like,
we
did
a
pretty
good
job
figuring
out
a
general
governance
model
within
cube
that
I
can't
I
can't
actually
imagine
undoing
it
or
making
a
massive
change
to
it.
So.
I
At
this
point,
I
I
tend
to
look
at
it
as
a
lot
of
people
in
cube
depend
on
us,
and
so
it's
just
important
that
we're
good
stewards
to
it.
Unless
that
there's
a
lot
for
us
to
to
shake
up,
and
then
in
general,
I
would
say
like
it's
natural
for
every
new
steering
candidates
who
who
joined
the
committee
to
to
aspire
to
getting
a
lot
done.
I
But
then
I
would
second
aaron's
comment,
which
is
like
it's
important
to
recognize
that
we're
all
time,
sliced
and
coming
onto
steering
will
just
further
increase
your
time
slice.
But
I
don't
know
from
for
me.
I
think
the
next
big
question
will
come
to
steering
is
how
did
the
health
checks
go
and
then,
if
they
didn't
go
as
well
as
you'd
like?
What's
the
new
practice,
we'll
follow
to
bring
speculum
and
status
born
alignment?
And
I
don't
think
we
have
that
fully
figured
out
as
a
group.
Yet,
but
that's
probably
the
next
year's
challenge.
D
D
E
Yeah,
so
you
may
answer
communication,
I
I
brought
it
up
on
chat.
We
still
have
to
work
a
lot
about
asynchronous
communication
between
teams
between
six
between
people.
Sig
release,
you
know,
is
always
affected
adversely,
so
we
got
to
figure
out
how
to
do
better
for
the
global.
A
Okay.
Moving
on
to
the
next
question
from
canada,
lockheed.
J
Kristof,
what
do
you
think
in
2020
has
been
the
most
impactful
change
to
the
community?
That
steering
has.
J
A
So
the
the
format
just
to
explain
the
format
that
we're
doing
here,
the
you
know,
candidates
are
able
to
ask
questions
of
the
current
steering
committee
and
then
the
current
steering
committee
is
going
to
respond.
A
The
purpose
of
this
meeting
is
not
for
like
candidates
to
give
like
a
platform
or
to
to
say
why
they
why
you
should
vote
for
me.
This
is
so
that
candidates
can
have
the
information
that
they
need
and
understanding
of
the
kind
of
work
that
stirring
does
and
to
kind
of
figure
out
if
they're,
a
good
fit
for
running
for
steering
committee.
E
So
lucky
I
take
a
stab
at
the
answer.
To
that
question
is,
I
think,
the
leads
meeting
and
in
the
leads
mailing
list
and
said
in
concert
with
contrabex
the
efforts
in
concert
with
contrabex,
which
which
helped
out
at
least
try
to
get
a
sense
of
people
working
across
with
each
other.
E
I
think
that
paved
the
way
for
some
of
the
things
that
ended
up
happening,
including
you
know,
the
locking
down
for
119
and
slowly
removing
slowly
opening
the
floodgates
all
those
kinds
of
things
you
know
we
gave
a
platform
on
the
forum
for
people
to
talk
about
things
that
was
across
six.
I
think
that
helped.
I
think.
C
I
can
go
next,
so
I
think
one
of
the
biggest
thing
hands
down
was
definitely
the
health
checks
that
paris
mentioned
and
like
she
was
instrumental
in
rolling
this
out.
The
other
good
thing-
that's
happened,
I
think,
is
which
hasn't
been
very
visible.
Is
our
interactions
and
engagement
with
the
cmcf
we've
had
frequent
communications
with
priyanka
who's,
the
gm
of
cncf,
and
we
are.
C
Our
interactions-
have
been
pretty
amazing
so
far
and
I
think
we'll
be
seeing
way
more
positive
engagements
with
the
cncf,
and
maybe
I
don't
know
like
we
have
to
still
figure
out
how
that
looks
like
that's
something
for
to
solve
in
the
future.
But
it's
it's
been
going
pretty
well
so.
C
A
Yeah,
nothing
else
to
add
for
myself,
but
I
I
would
agree
in
particular
that
the
the
couple
points
that
nikita
brought
up
the
health
check
and
that
that
process,
like
that's,
that's,
going
to
be
bearing
fruit
for,
for
you
know,
years
to
come.
I
think,
and
the
improved
kind
of
interaction
with
the
cncf
is
also
less
visible,
but
very,
very
important
for,
like
the
long
term,
stability
of
the
project.
A
The
process
health
check
with
the
currently
we're
rolling
it
out
to
working
groups
and
but
eventually
like
all
of
our
different
community
groups,
including
sigs
and
committees,
and
everyone
else,
will
be
basically
putting
through
an
annual
report
to
to
kind
of
describe
both.
You
know.
Things
are
going
well
in
the
community
group
as
well
as
things
that
that
particular
community
group
might
need
help
with.
I
Derek
yeah,
I
guess
going
back
on
the
theme
of
like
change
like
I
think
it's
a
bad
sign
if
we
make
too
many
proactive
changes
in
my
opinion
to
james
earlier
comment
on
a
lighter
touch
as
often
as
helpful,
I
think
changes
that
did
happen,
that
we
were
in
consultation
with
to
try
to
support
the
community
so
like
anytime,
we
create
a
new
sig
is
like
a
new
major
structural
change
of
the
project.
I
Community
than
maybe
the
application
or
traditional
cluster
administration
community-
and
so
I
think
in
general,
like
any
time
we
as
a
steering
body,
can
just
kind
of
supplement
or
support
what
the
community
needed
is
is
preferred
over
making
a
large
change
so
but
yeah
that
one
stands
out
to
me.
D
Gopro,
I
feel
like
it's
kind
of
putting
the
focus
on
inclusivity
so
the
I
know
it
took
us
a
good
while
to
actually
move
forward
with
it
and
it's
very
small,
very
incremental
progress.
The
issue
was
originally
suggested
by
tim,
pepper
a
while
ago
that
we
go
through
inclusivity
and
leadership
training
and
that's
something
now
that
all
sig
chairs
are
going
through
and
I
think,
even
though
it
might
be
small.
I
think
it's
a
good
reminder
and
sort
of
helps
set
expectations.
D
That
inclusivity
is
something
that
we
value.
It's
sort
of
to
reinforce.
A
D
Community
values-
and
I
think
again
it's
a
small
thing,
but
putting
the
statement
that
we
did
on
the
kubernetes
website,
I
think,
was
a
good
representation
of
this.
This
project's
values
and
where
we
stand
and
what
sort
of
behavior
we
do
and
do
not
find
acceptable
within
the
community.
Just
because
I
feel
like
the
the
health
and
the
in
the
intentional
nature
with
which
we
treat
our
community
interactions
is
one
of
the
things
I
value
most
about
this
project
and.
A
Okay,
I
think
it
goes
to
bob
the
next
candidate
question.
H
Cool,
you
probably
covered
some
of
this
already,
but
I
sort
of
have
to
toss
this
out.
What
is
something
you're
proud
of?
It's.
It's
actually
like
three
questions.
What
is
something
you're
proud
of?
What
is
something
you
wish
you
had
done
differently
and
what
would
you
like
to.
H
I
I'm
gonna
work
out.
I'm
proud
that
we
still
have
a
relatively
vibrant
engaged
community
in
kubernetes,
like
open
source,
is
hard
and
figuring
out.
The
right
way
to
engage
with
such
a
large
group
of
of
people
around
the
world
is
is
non-trivial
and
the
success
of
projects
like
this
are
or
something
that
we
should
all
sit
back
and
kind
of
admire
right
like
so,
it's
exciting
to
see
the
new
candidates
want
to
to
join
the
role
and
hopefully
take
on
the
mantle
to
do
good
going
forward.
I
The
second
question
now
I've
lost
me
because
I
was
too
happy
with
the
first
one
which
was
like
this
is
all
a
place
we'd
like
to
be
right,
like
I
guess,
it'd
be
in
a
bad
spot.
If
you
didn't
have
a
good
pool
of
candidates
wanting
to
actually
run,
and
so
I'm
happy
that
to
date,
we've
left
the
ability
for
folks
to
run
relatively
open
and
give
their.
I
A
I
posted
the
question
and
for
reference
in
chat
anyone
else
from
steering.
D
A
D
Did
but
who
knows,
I'm
proud
of
the
fact
that
the
people
who
got
who
have
been
elected
to
the
steering
committee
thus
far
have
been
people
who
actually
do
the
work
as
opposed
to
people
who
do
a
lot
of
posturing
and
grandstanding.
I
feel
like
as
a
signal
from
the
community
that
it
values
getting
work
done.
D
I
also
value
or
am
proud
of,
the
fact
that
I
have
been
able
to
serve
on
a
committee.
That
is
not
a
bunch
of
white
dudes
and
again.
I
want
to
thank
the
community
for
voting
that
way,
and
I
want
to
thank
our
amazing,
diverse
school
candidates
for
being
awesome.
A
The
the
thing
that
I
you
know
I,
I
guess
the
third
question-
is:
it's
definitely
tough.
For
me,
the
first
question
is
the
thing
that
I'm
proud
of,
like
I
got
a
little
bit
emotional
about
this.
A
When
we
put
out
the
you
know,
the
change
in
policy
that
we
wanted
to
to
introduce
unconscious
bias
training
and
make
it
mandatory
for
sick
chairs
and
technical
leads
and
say:
okay,
if
you're
in
a
leadership
position
in
the
kubernetes
community,
this
isn't
gonna
solve
unconscious
bias
by
far,
but
this
is
like
one
small,
incremental
step
that
we
can
take
when
we
put
that
out
there
we
had
a
tremendous
uptake.
A
You
know
today
is
the
last
day
of
the
the
kind
of
like
we
put
out
like
a
45
day
timeline,
but
the
vast
majority
of
the
community
responded
and
like
did
that
training
right
away
right
off
the
bat
and
there
there
wasn't.
So
what
there
wasn't
in
our
community
was
anyone
who
said
this
is
a
waste
of
my
time.
This
is
this,
isn't
valuable.
I
don't
see
this
as
a
problem.
A
A
That's
like
I'm,
proud
of
our
community
that
when
we
put
out
there
like
hey,
we
want
to
take
this
one
tiny,
incremental
step
and
maybe
make
this
a
slightly
better
place
for
you
know,
for
contributors
and
and
and
be
able
to
have
common
language
to
talk
about
unconscious
bias
in
our
community
groups,
at
least
be
aware
that
it's
like
a
thing
that
that
exists.
A
Our
community
responded
like
overwhelmingly
positively
and
overwhelmingly
quickly
to
to
kind
of
like
take
out
that
mantle
and
run
with
it,
so
that
I
think
that
is
probably
my
the
proudest
moment
that
I've
seen
as
a
as
a
leader
in
the
community
in
the
year
or
so
that
I've
been
on
on
steering.
That
was
amazing
to
see,
though,
and
as
far
as
like
things
I
wish
I
had
done
differently.
A
This
has
been
like
mentioned
in
a
couple,
different
answers,
but
steering
takes
up
time
and
it's
just
another
time
slice
of
things.
But
the
thing
I
wish
I
had
done
differently
was
allocate
more
time
and
drop
more
things
quicker
to
do
more
and
do
more
at
the
steering
level
like.
I
would
say
that
to
every
candidate
like
expect,
if
you
are
elected,
to
steering
you're
going
to
need
to
drop
things,
like
other
things
that
you
have
been
doing
up
to
this
point,
you
will
need
to
delegate
them.
D
D
A
more
regular
cadence
of
connectivity
with
the
cncf
I
feel
like
there
was
a
period
of
time
where
the
cncf's
attention
turned
to
yeah.
A
D
You
graduated
now,
let's
go
like
graduate
as
many
other
projects
as
we
possibly
can,
which
is
which
is
fine.
They.
You
know
there
are
many
projects
in
the
cncf
that
are
not
kubernetes,
but
I
still
think
there
is
value
in
ensuring
that
our
needs
are
being
met
and
our
goals
are
aligned
because
I
won't
name
specific
names
or
events,
but
I
feel
like
there.
D
There
has
been
friction
in
the
past
and
there's
also
been
just
room
for
for
second
guessing
and
room
for
yeah
room
for
for
wheel,
spinning
and
second
guessing.
I
guess
and.
D
C
I
can
add
a
bit
about
what
I
wish
I'd
done
differently.
We've
we've
had
the
annual
health
check
report
now,
which
is
pretty
cool,
but
there
are
still
like.
When
I
look
at
some
working
groups,
I
mean
there's
still
some
groups
and
communities
where
I
have
no
idea
what's
going
on
and
unless
I
like
look,
I
make
an
active
effort
to
go
to
their
meetings
or
figure
out.
What's
going
on.
C
I
didn't
know
it
before
so
I
think
like
as
the
steering
committee
as
a
steering
committee
member,
I
think
I
would
have
it
would
have
been
nice
if
we
had
more
proactive
lease,
I
mean
we
have
still.
We
have
working
group
liaisons
now,
but
just
being
aware
of,
what's
going
on
in
all
pockets
of
the
community
would
have
been
nicer
to
catch
issues
early.
A
Okay
over
to
divya
for
the
next
candidate
question.
L
Okay,
thank
you.
So
I
wanted
to
ask
out
of
the
many
things
that
you
guys
oversee
and
work
on
as
a
committee.
What
is
one
of
the
most
challenging
aspects
of
the
work
that
is
being
done
or
has
been
done?
You
know
completed
in
the
sense
and
that's
obviously
barring
the
current
pandemic
situation,
but
I
wanted
to
understand
what
was
one
of
the
most
challenging
things
that
you
guys
had
to
work
on
as
a
company.
I
I
think
charter
review
is
a
a
difficult
topic
because
I
think
back
early
in
the
creation
of
ziggs
like
if
we
didn't
spend
as
much
time
as
we
did
reviewing
individual
charters.
We
probably
would
have
had
more
conflict
within
the
project
on
areas
of
shared
responsibility.
I
So
I
think
in
the
early
days
of
kubernetes
having
a
keen
awareness
on
what
the
actual
project
was,
what
it's
made
up
of
and
where
tensions
might
arise
among
interest
groups
is
actually
a
harder
thing
than
many
might
appreciate,
and
so
good
charter
review
is
always
a
thing
that
looks
easy
but
is
actually
probably
difficult
in
practice.
The
other
thing
that
goes
with
that
is
just
kind
of
like
clarity
and
communication
or
conciseness
oftentimes.
I
I
Responding
well
to
feedback,
because
usually
all
the
feedback
is
positively
intended
is,
is
just
a
hard
soft
skill,
and
so,
if
I
I
I
would
say,
if
you
didn't,
have
an
abundance
of
patience
before
joining
steering,
you
will
grow
it
and
it
will
help
a
lot
of
other
areas
of
your
life.
I
think,
but
I
know
for
for
myself.
I
I
think
clarity
of
communication,
a
good
understanding
on
the
general
project,
nature
and
being
patient,
is
probably
like
the
hardest
things
that
all
of
us
have
to
deal
with
a
bit
in
steering.
D
Back
and
forth,
we
had
with
the
cncf
over
funding
for
the
contributor
summit
and
that
it
was
important
to
us
that
it'd
not
be
super
under
branded.
We
didn't
want
to
see
vendors
logos
everywhere.
D
We
wanted
to
see
contributors
there
and
they
focus
on
community
and
there
was.
It
was
really
difficult
to
get
clear
and
transparent
accountability
on
where
the
money
was
going
and
why-
and
we
continually
had
to
take
a
stand
there.
I
think
it
made.
Some
of
us
feel
like
we
were
taking
crazy
pills
and
I'm
really
grateful
that
the
steering
committee
is
open
to
expressing
vulnerability
and
being
supportive,
because
that's
that's
something
I
think
we
cared
a
lot
about.
D
A
D
There
are
those
of
us
who
have
some
experience
in
the
openstack
community
and
didn't
necessarily
want
a
repeat
of
what
that
evolved
into,
and
I
I
mean
you
know
it's
a
little
bit
difficult
to
say
it's
one
hundred
percent
been
solved
given
the
state
of
duke
cons
this
year,
but
I
do
think
we
have
a
much
clearer
set
of
expectations
and
agreements
in
place
to
uphold
this
particular
value.
D
A
A
Anything
that
involves
public
relations,
anything
that
involves
the
kubernetes
steering
committee,
making
a
statement
whatever
the
audience
of
that
statement
is
if
it's,
if
it's
going
to
be
public
and
we
are
making
a
statement
on
behalf
of
the
committee
on
behalf
of
the
project,
there
is
an
immense
amount
of
thought
that
goes
into
first.
A
Should
we
make
a
statement-
and
that's
like
that
being
like
the
key
initial
question
like?
Is
this
something
we
should
speak
out
on?
Is
it
more
powerful
or
does
it
get
us
the
the
outcome
that
we
want
if
we
just
remain
silent
and
if
we
do
choose
to
respond,
how
do
we
respond
in
what
format
do
we
respond?
What
do
we
say?
What
is
the
wording?
A
You
know
how
much
detail?
Do
we
go
into
how
little
d,
like
you
know,
do
we
make
it
brief
and
more
powerful,
like
there's
there's
so
many
different
ways
to
write?
Something
and
words
are
very
important,
so
anytime
we're
making
a
public
statement
on
anything.
It
is
it's
challenging,
but
you
know
very
necessary
for
us
to
go
through
that
process
and
that's
something
that
you
you
know
from
the
outside.
A
You
see
the
result
of
that,
whether
that
is,
you
know,
silence
whether
that
is
a
very
carefully
thought
out
statement
coming
from
the
steering
committee,
but
behind
every
every
statement
that
you
see
that
the
kubernetes
steering
commit
committee
has
made-
and
this
is
both
like
you
know
during
my
time
on
the
committee
and
from
you
know
what
I've
seen
historically,
basically
back
to
the
original
bootstrap
committee
anytime.
This
committee
has
spoken
out
and
said
anything
there's
a
ton
of
thought
that
goes
into
that
and
there's
a
lot
of
the
back
and
forth
discussions
on.
A
Do
we
say
something
and
if
we
do
what
do
we
say,
because
you
know
yeah
when
we're
speaking
we're
not
just
speaking
as
individual
contributors
with
opinions,
we're
speaking
on
behalf
of
the
project,
so
yeah
there's
just
there's
a
lot
of
thought
process
that
goes
into
that.
K
A
Communications,
like
typically
when
the
syrian
committee
is
communicating
about
something
we
have
like
private
conversations
either.
You
know
through
our
tooling,
like
slack
or
google,
docs
or
or
you
know,
those
communication
meetings.
The
steering
committee
is
one
of
the
the
groups
in
the
project
that
is
permitted
to
have
you
know
a
private
channel
in
private
communications,
because
we
want
to
you
know,
because
we
need
to
answer
those
questions
like.
Is
it
something
that
we
should
talk
about?
A
Is
it
something
and
then
making
sure
that
we
kind
of
get
that
unified
voice
amongst
because
we're
you
know
we're
seven
individuals?
We,
we
definitely
have
different
opinions
on
things
and
when
we
start
out
a
discussion,
you
know
we're
not
always
on
the
same
page,
it's
actually
quite
refreshing.
A
One
thing
I
will
say
is
we
start
out
pretty
close,
and
I
think
that's
because
the
the
seven
of
us
on
the
current
committee
that
this
is
the
only
kind
of
version
of
the
committee
that
I've
worked
on,
that
the
seven
of
us
like
we're
all
starting
from
the
position
of
like
we
really
care
about
the
community
and
the
projects.
Health
first
over
anything
else
over,
you
know
our
own
interests
over.
You
know
our
employers
interests
for
sure.
You
know
we
care
about
the
project
and
the
project's
health
first
and
foremost.
A
So
a
lot
of
these
discussions.
We
do
start
at
least
like
pretty
close,
but
we're
not
always
on
the
same
page
to
start
so
we
do
have
those
private
communications,
like
slack
private
meetings,
you
know
the
working
docs
and
that
kind
of
stuff,
so
we
will
iterate
on
communications
before
before
we
we
put
them
out.
A
Okay,
steven
is
your
hand
up
for
another
candidate
question.
F
Yeah,
so
what's
next,
not
necessarily
for
the
steering
committee,
but
for
the
individuals
on
the
steering
committee.
I
know
that
you
were
initially
talking
about
having
to
having
to
shed
some
of
your
roles
and
do
things
a
little
differently
to
allow
that
steering
committee
time
slice
to
come
in.
So
as
it
moves
out.
What
do
you
plan
on
doing
next.
A
F
A
Well
I'll
I'll
say
at
least
for
for
for
myself,
so
I'm
you
know
I've
completed
a
year
of
my
two-year
term
on
steering,
so
I
still
have
a
year
ahead
of
me.
I
look
forward
to
continuing
the
key
things
that
we're
working
on,
like
the
annual
report
manual
report
stuff
and
like
looking
forward
to
you,
know
the
new
and
different
challenges
that
we're
going
to
face
in
in
in
2021.
A
I'm
sure
there
will
be.
You
know
some
different
perspectives
that
will
will
come
in
as
we
elect
the
three
seats
that
I
believe
are
are
up
this
year.
This
will
be
three
they'll
likely
be
three.
You
know
slightly
different
voices
than
the
ones
that
we've
had
different
opinions.
G
D
C
I
can
add
on
but
like
pretty
much
what
kristoff
said,
because
I
still
have
a
year
to
go.
I
don't
know
perfect,
but
because,
what's
gonna
happen
a
year
from
now
but
kind
of
the
next
year-
and
maybe
the
year
from
now-
would
be
to
I'm
not
sure
what
the
right
word
is,
but
maybe
like
coach
people
find
or
make
sure
that
we
have
more
engagement
with
the
community
so
that
when
the
next
cohort
of
candidates
come
up,
they're
so
also
big.
C
We
have
like
an
excellent
set
of
candidates,
but
we
need
to
make
sure
that
we
constantly
keep
having
such
a
good
cohort
so
kind
of
building
more
on
that
engagement,
something
for.
A
Okay,
next
kind
of
question
coming
from
bank.
Sorry
am
I:
how
do
you
pronounce
your
name?
I'm
not
sure.
I'm
saying
that
correctly.
K
A
Okay,
so
I'll
put
this
back
out
I'll
switch
one
more
time,
because
I
think
we've
had
some
more
folks
join,
so
we're
kind
of
a
back
and
forth
where
candidates
are
able
to
ask
questions
of
steering
to
kind
of
get
a
clarification
of.
A
You
know
what
the
role
of
steering
committee
is,
if
it
would
be
a
good
fit
for
them.
This
is
not
a
candidate
kind
of
like
pitch
speech.
This
is
more
trying
making
sure
that
candidates
have
the
information
that
they
need
to
to
ensure
that
this
job
would
either
be
be
the
right
fit
for
them
or
just
learn
more
about
what
steering
committee
does,
and
you
know
how
we
do
governance
in
kubernetes.
A
We
have
yeah
we'll
have
about
eight
minutes
left
of
time,
for
maybe
one
more
question
from
from
the
candidates.
If
there's
any
candidate
that
has
another
question
they'd
like
to
raise
to
us.
E
I'll
ask
one
question:
as
a
candidate,
I
haven't
declared
candidacy
or
anything,
but
I
just
want
to
ask
so
if
there
was
one
thing
that
you
would
change
over,
what
would
you
change
from
the
decisions
or
whatever
that
you
already
went
through
whether
it
is
the
outcome
or
the
process
either?
One
is
fine.
A
A
A
Yeah,
I'm
not
sure
that
I
have
something
specific.
That's
like
you
know
what
what
what
I
would
change
as
far
as
like
a
decision
or
outcome
that
we've
already
that
we've
already
made
like
the
ones
that
the
decisions
that
I
was
involved
with.
I
I
like
that
the
past
members
of
the
steering
committee
that
are
no
longer
serving
have,
I
don't
know
the
right
wording
for
it,
but
you're
all
a
bit
of
a
club
and
it's
never
in
one's
interest
to
kind
of
betray
what
one
individual
did
or
didn't
do
or
or
that
type
of
thing,
because
the
whole
point
is
that
you're
outwardly
speaking
as
a
body,
so
I
think
dim's
the
best
way
to
answer
that
is
in
a
in
a
private
retro
and
but
in
general
like
I,
I
think
it's
less
what
retroactively
looking
and
more
forward-looking
you
can.
E
No,
but
I
just
wanted
to
ask
a
question,
but
then
I
also
wanted
to
thank
lucky
for
you
know
taking
over
from
tim
sinclair
and
running
with
it,
and
it
was
so
happy
for
that.
Thanks
lucky.
E
D
Maybe
echo
derek's
answer
I
feel
like
it
took
the
committee
a
little
while
to
become
intentional
about
having
regular
private
meetings
and
that
clashed
a
little
bit
with
my
values
of
being
as
like,
open
and
transparent
as
possible.
I
very
much
did
not
want
the
steering
committee
to
be
yet
another
smoky
back
room
in
which
decisions
are
being
made,
but
you
know
given
some
of
the
answers
that
have
talked
about
sort
of
the
pr
component
of
this
role.
I
think
it
is
critically.
D
To
have
a
safe
space
where
we
can
bounce
ideas
around
and
come
to
consensus,
I
think,
having
meeting
regularly
privately
has
helped
us
avoid
the
situation
where
individual
members
are
picked
off
piecemeal,
as
somebody
tries
to
sponsor
shop
or
whatever
for
a
given
decision,
and
I
think
it's
it's
helped
us
stay
connected
and
support
each
other,
a
lot
more.
D
I
I
don't
know
I
just
have
these
memories
of,
like
I
think.
Maybe
it
was
more
of
a
bootstrap
committee.
It
was
bootstrap.
Members
were
also
part
of
the
committee,
like
it
was
impossible
to
find
time
for
us
to
meet
with
any
kind
of
regularity,
and
so
it
was
usually
just
like
in
person
at
kubecon,
where
we
could.
Finally,
let
our
hair
down
so
to
speak,
and
so
I
think,
like
moving
to
seven
members,
has
helped
with
that
somewhat.
D
But
I
also
think
just
being
intentional
that
the
private
meeting
is
an
important
space
for
us.
That
said,
it's
not
entirely
private.
We
still
keep
meeting
notes
for
those
private
meetings,
so
I
think
that's
that's
helped
balance
that
compromise
and
it's
not
a
dark
smoky
room,
but
it
is
a
safe,
supportive
space.
A
C
G
E
A
Okay,
well,
so
what
what
I
would
like
to
say
at
this
point
is
is
thank
you
to
for
the
candidates
for
for
showing
up
and
asking
insightful
questions.
Thank
you
to
my
fellow
syrian
committee
members
for
making
the
time
to
to
answer
these.
If
there's
specific
questions
that
candidates
that
you
have
that
that
come
up,
we,
our
inbox,
is
open.
You
can
reach
us
at
the
steering
committee
channel
in
slack.
A
We
have
steering
at
kubernetes.
Io
is
our
public
mailing
list
if
there's
something
specific
private
that
you'd
like
to
ask,
or
steering
dash
private
at
kubernetes,
dot,
io
and
good
luck
to
to
to
all
the
candidates
in
the
in
in
the
election
this
fall.
You
know
thank
you
for
at
least
putting
your
names
forward
to
serve
the
community.