►
From YouTube: [SIG ContribEx] KCSEU 2022 Planning Meeting for 20220613
Description
[SIG ContribEx] KCSEU 2022 Planning Meeting for 20220613
A
Okay,
welcome
everybody
to
the
contributor
summit,
europe
retro,
just
to
go
over
how
the
contributor
summit
went
and
everything
else,
partly
for
our
benefit
and
partly
for
the
benefit
of
the
next
contributor
summit
team.
The
everybody
already
has
should
have
up
the
retro
document.
Let
me
paste
that
again
for
anybody
to
join
later
and
then
we're
just
going
to
go
over
it
and
sort
of
add
things
as
we
go.
A
A
A
A
So
I
feel
like
that,
worked
out
a
lot
better
to
have
most
of
the
people
there
by
the
time
that
we
started
the.
I
thought
the
social
went
pretty
well,
the
two
things
actually
that
I
felt
worked
out
really
well
at
the
social
were
lockheed's
quiz
show
which
people
got
really
into
and
the
food
the
catering
was
excellent.
I
should
have
known
that
that
in
valencia,
heavy
apps
actually
means
whatever
it
was
18
pounds
of
paella.
A
B
B
A
A
A
So
yeah
I
mean
ideally
most
of
the
time.
If
we're
renting
a
venue,
it
would
potentially
be
like
one
of
the
things
that
works
out
well
for
a
smaller
one,
which
will
probably
not
be
detroit,
is
a
venue
where,
after
the
contributor
summit
ends,
they
just
open
up
to
the
public
and
therefore,
if
people
want
to
stay
hang
out
over
drinks.
A
A
And
that
includes
transportation
actually
worked
out.
Fine.
I
was
really
worried
about
getting
people
to
the
social
and,
and
it
doesn't
seem
to
have
been
a
problem
having
those
buses
was
great
and
most
of
the
people
took
the
bus
from
what
I
could
tell
and,
and
then
some
people
got
there
on
their
own.
A
A
D
A
Okay,
so
yeah
so
some
ahead
of
time,
some
the
day
of
and
and
doing
the
voting
on
site
morning
of
it's
hard
to
isolate
that
from
other
stuff
that
we're
doing
right,
because
there
was
obviously
a
lot
that
was
different
about
san,
diego
or
when's.
The
last.
When
was
the
previous
one
that
we
had
on
conference
stuff,
I
guess
we've
always
had
some
unconference
stuff,
but.
A
B
D
E
D
I
agree
with
what
puyo
wrote
there
in
the
comments
as
well.
Writing
people
actively
in
the
week
before
kubecon
helped
kick
the
github
thread
off.
Nobody
likes
to
be
the
first
one
to
propose
a
topic.
It
seems
yeah.
I
definitely
did
pain
the
person
who
put
the
first
one
was
like
hey.
I
know
you
have
an
idea.
Could
you
please,
like
put
it
in
there.
B
B
D
B
A
A
A
A
A
The
and
part
of,
and
one
of
things
contributing
to
problems
with
the
meet
and
greet
was
that
we
did
not
get
a
volunteer
for
a
meet
and
greet
coordinator,
and
so
I
was
basically
filling
in
with
meet
and
greet
organization,
to
the
extent
that
I
could
around
other
things
and
the
meet
and
greet
definitely
suffered
for
it.
Okay,
we
had
several
complaints
from
people.
Chris
calls
out
several
complaints
from
people
having
difficulty
finding
the
contributor
summit.
B
A
F
A
B
A
B
It
I
will
say
it
did
not
help
too,
that
the
the
room
well
like
the
room
numbers
and
all
that
were
named
similarly
so
like
there
is
a
bunch
of
people
wandering
around
the
main
building,
which
you
would
see
assume
is.
It
was
called
like
event
center
or
something
like
that.
The
one
that
we
were
in
was
called
like
a
vet
center
it
just.
I.
I
think
there
was
a
lot
of
things
that
lent
itself
to
confusion
at
that
location.
A
D
Tweeted
out
stuff
yeah,
I
think
that
short
of
like,
if
we
just
create
a
volunteer
role
where
somebody
is
just
going
back
and
forth
from
like
reg
or
from
wherever
people
are
showing
up
to
like
just
walk
back
and
forth
and
like
have
a
few
people.
Trade
off
during
the
day
to
you
know,
take
small
groups.
B
D
B
The
big
problem
is
just
like
this
isn't
so
much.
It
wasn't
so
much
an
issue
for
valencia,
where
we
had
a
smaller
amount
of
people.
We
all
kind
of
knew
each
other
who
was
going
to
be
there
for
north
america,
assume
we're
going
to
have
300
people
and
a
lot
of
people
have
never
met
other
people
before.
A
A
B
Honestly,
there's
not
much
more,
we
can
do.
We've
had
this
problem
every
single
time
like
there's
at
least
one
or
two
people,
that
just
don't
bother
with
registering,
don't
bother
doing
anything
like
that
at
all
yeah,
it's
just
going
to
be
a
given
that
there
will
be
at
least
a
couple
people
that
don't
yeah.
A
Oh
they're,
not
really
in
valencia,
but
they'd
missed
something
else.
You
know
I
and,
and
they
definitely
played
into
the
deciding
whether
or
not
somebody
ought
to
be
able
to
go
in,
because
we
actually
let
in
a
couple
of
people
who
were
substantial
contributors
to
other
cncf
projects,
but
not
to
kubernetes,
just
because
we
didn't
want
to
send
them
back.
Yeah.
A
A
D
A
A
A
So
a
recommendation
to
the
detroit
team
is
take
the
sort
of
marked
up
version
of
our
messaging
docs
from
this
and
use
that
as
a
basis
to
decide
well
in
advance.
What's
going
to
need
to
go
out
for
the
summit,
because
particularly
for
things
like
if
deb
is
sending
stuff
out
to
the
attendees
using
their
system,
apparently
there's
some
prep
that
goes
into
that.
A
B
So
we
do
have
a
commons
playbook
and
a
general
like
schedule
that
we
try
and
follow
it's
just
that,
honestly
to
it.
It
always
wound
up
being
the
thing
that
got
bumped
off
the
list
of
people's
tasks
yeah
we
we
could
use
more
people
that
help
with
that.
The
other
thing
is
like
on
the
twitter
side
of
things.
There
is
a
request
open
in
kubernetes
steering
to
help
with
all
the
scheduling
of
the
tweet.
That
will
help
with
scheduling
all
that
stuff.
So
you
can
have
a
more
uniform.
B
You
know
messaging
front.
I
guess
is
a
way
to
figure
it
like
right
now,
it's
all
for
every
tweet,
it's
either
caslin
or
chris,
going
in
and
doing
it
by
hand
or
a
whole
slew
of
issues
that
they
then
have
to
time.
The
lgtm
approve,
or
you
know,
hold,
cancel
to
get
the
timing
right.
So
there's
there
is
some
stuff
that
should
help
with
that.
For,
for
detroit
yeah.
A
I'm
actually
gonna
message:
I'm
gonna
go
back
up
to
something
that
went
well
because
it
just
occurred
to
me
related
to
messaging,
which
is.
This
is
the
first
contributor
summit,
where
we've
really
had
full
access
to
the
contributor
site
and
being
able
to
constantly
update
that
site
was
actually
quite
useful.
A
A
A
A
A
A
Yeah,
so
whether
it's
a
deck
or
something
else,
we
need
to
do
a
no
before
you
go
for
staff
just
so
we
remember
all
the
things
we
need
to
remember.
I
one
person
objected
to
needing
to
register
for
the
social.
I
don't
think,
there's
really
anything
we
can
do
about
that.
I'm
gonna
pass
this
along.
Three
people
volunteer
to
help
with
detroit
and
for
to
help
with
amsterdam,
so
I
will
pass
along
those
emails
in
case
you
don't
already
know
about
those
people.
A
A
A
I
was
curious
about
communication
just
because
that
had
been
a
difficult
thing
in
terms
of
the
amount
of
effort
for
us
and
despite
some
of
the
complaints
about
having
difficulty
finding
things.
Mostly
people
just
said
that
they
found
out
some
things
at
the
last
minute,
but
but
nobody
said
that
they
missed
things
entirely,
because
they
couldn't
find
information.
A
B
A
Yeah,
the
yeah,
I
mean
mind
you
considering
who
we
are
the
yeah
and
so
the
other
two
ones
that
got
a
lot
of
responses.
You
know
again,
a
third
of
the
people.
Each
is
more
planned
sessions
alongside
the
unconference
sessions
and
more
rooms
and
time
slots
for
sig
meetings.
Those
I
find
interesting
because
we
didn't
turn
down
the
only
sig
meeting
we
turned
down.
A
B
A
A
A
D
Mean
I
think,
that's
fine,
but
like
the
hallways
were
pretty
cavernous
and
so
like
folks,
having
conversations
out
there
during
sessions
was
really
distracting
and
like
we
couldn't
really
close
the
doors
on
every
one
of
them.
So,
okay,
if
that's
the
case
for
next
time,
maybe
we
have
like
an
area.
That's
for
that
or
we
just
have
like
you
know,
quiet
zone
when,
like
a
talk,
is
happening
because
a
couple
times
I
was
ushering
folks
out
of
that
main
hallway
in
front
of
the
auditorium,
so
that
folks
inside
could
hear.
D
A
D
D
Like
a
little
bit
like,
if
we
can
like
just
make
it
so
or
just
like,
let
people
know
once
we
do
the
walkthroughs
like
okay,
hey,
we
should
like
move
the
people
to
a
particular
area,
yeah
pouya's
right,
there's
the
the
main
issue
was
the
hallway
noise
being
very
transparent
towards
the
main
room
and
yeah.
If
we
had
it
out
in
the
like
in
the
stair
room,
then
that
would
probably
okay.
C
F
B
A
A
A
A
The
because
and
and
one
of
the
ones
we
specifically
had
was
a
team.
It
wasn't
even
a
subproject,
so
the
I
one
of
the
calls
that
we
had
and
I've
seen
this
on.
Slack
too,
is
that
they're
people
who
are
wanting
to
spread
out
the
contributor
summit
over
two
days,
and
I
think
we'll
continue
to
hear
that
yep
until
we
try
it
at
which
point
we'll
get
a
bunch
of
people
telling
us,
we
should
go
back
to
one
day,
the
so.
B
And
I
think
the
the
big
problem
is
now
that
the
kubecon
collocated
events
are
now
across
two
days
like
we
used
to
have
our
summit
before
the
rest
of
the
day.
Zero
events,
so
it's
kind
of
nice
so
like
a
lot
of
the
people
that
attend
have
to
go,
help
run
their
vendor
specific
events,
and
that
is
no
longer
the
case.
It's
kind
of
a
crap
shoot
whether
you're
going
to
be
doing
like
your
vendor
or
your
employer,
whatever
you're
associated
with
is
doing
something
on
monday
or
tuesday.
A
I
wouldn't
it
would
be
a
killer
for
a
lot
of
people
yep
the
I
mean
I
would
say
if
a
team
wanted
to
take
the
plunge
and
stretch
it
out
over
two
days,
then
the
answer
would
be
sunday
monday,
but
the
problem
with
the
two-day
thing
is
that
effectively
you'd
be
getting
two
different
audiences
on
one.
On
each
day.
A
B
The
other
thing
would
potentially
be
doing
like
we
did
this.
I
think
in
I
think,
we've
actually
offered
this
several
times
is
so
cigs.
If
they
want
to
do
a
meeting
or
if
they
want
to
schedule
something
specific,
they
can
do
it.
They
can
take
a
slot
on
the
following
day.
Essentially,
yeah
we've
offered
that
a
few
times
in
the
past
am
I
right.
Deb.
A
B
So
something
else
regarding
our
cons
and
messaging
and
all
that
is
that
we've
usually
sent
the
same
message
to
both
dev
and
leeds
list.
We
might
want
to
have
a
separate
set
of
messaging,
basically
tailored,
for
you
know,
I
think,
just
like
kubecon
of
the
maintainer
track
sessions.
If
you,
if
you
want
to
reserve
a
space,
send
an
independent
comms
message
to
the
leads
list.
A
C
C
A
C
C
A
C
C
D
Like
the
staff
who
was
serving
food
was
pretty
stretched
thin
because
there
was,
there
were
a
lot
of
times
where
folks
were
trying
to
get
their
attention.
I
remember
one
time
we
ran
out
of
spoons
or
something
and
they
were
like
running
around
trying
to
get
silverware
or
like
flatware,
and
it
was
difficulty
nailing
them
down,
and
I
did
hear
some
complaints
that
there
weren't
enough
vegan
options.
C
A
A
Okay,
yeah
well,
the
one
thing
I
could
say
actually
doing
about
with
the
social
is:
if
we
have
a
situation
like
this,
because
it's
probably
going
to
be
always
true
that
past
apps
are
not
well
labeled,
that
we
should
announce
where
the
information
on
ingredients
is
out
loud
at
the
beginning
of
the
social
and
that'll
help
people
the.
So
we.
C
B
A
B
A
A
E
Hello,
can
you
hear
me
yep?
Okay,
my
voice
is
still
not
completely
back.
Sorry,
for
that
I
was
active
in
chat.
Yeah
I
mean
in
in
total,
I
think
for
the
for
the
the
limited
amount
of
time
and
limited
amount
of
organizers.
This
went
extremely
well
and
we
can
take
a
lot
of
experience
with
us
into
the
next
one
and
bring
the
next
team
a
bit
a
bit
of
certainty
in
planning.
A
Yeah,
I
I
mean
I
feel
like
it
went
well
like
I
feel.
Like
people
had
meetings,
people
did
sessions,
they
discussed
stuff
that
was
important
to
kubernetes
development,
and
that
is,
after
all,
what
the
contributor
summit
is
for:
yeah,
the
and
and
if
there
was
a
major
problem
with
the
contributor
summit,
it
was
the
one
we
can't
control,
which
is
obviously
a
lot
of
key
people.
Couldn't
get
be
there
because
of
travel
restrictions.