►
From YouTube: [SIG-ContribEx] KCSEU 2023 Retrospective for 20230501
Description
[SIG-ContribEx] KCSEU 2023 Retrospective for 20230501
A
A
We
are
here
to
talk
about
all
the
things
that
happened.
What
went
well,
what
didn't
go
well,
what
we
can
do
better
and
what
still
needs
to
be
done
as
follow-up
work,
because,
just
because
the
Summit
is
over,
it
does
not
mean
our
jobs
are
done.
A
Okay,
they
don't
really
have
a
formal
agenda
for
this
one,
because
this
is
more
of
a
group
thing.
C
A
C
A
To
take
a
note,
so,
let's
see
where
do
we
want
to
start
things
that
went
well
always
start
with
an
upbeat
thing?
Let's
see
Josh
says
signage
was
good.
A
I
agree
Brienne
had
these
arrows
that
were
great
for
pointing
people
in
right
directions.
Yeah
now.
B
I
ended
up
waiting
up
in
the
sort
of
upper
coffee
area,
though
just
to
direct
people
around
the
corner.
Okay,.
A
Yeah,
there's
not
really
much.
You
can
do
about
that
with
I
mean
based
on
the
space
that
you
have.
It
was
very
difficult
from
the
plans
to
see
what
that
was
actually
going
to
be
like
because
it
looked
like
we
were
going
to
walk
in
the
door
and
just
be
there
not
knowing
that
there
was
actually
like
walls
in
the
way
and
you
couldn't
go
through
and
yeah.
C
B
A
Now,
if
we
have
people
on
site,
we
had
one
person
who
was
supposed
who
was
in
Amsterdam
that
we
or
no
not
in
Amsterdam
in
the
Netherlands,
like
three
hours
away,
who
we
were
trying
to
get
to
go,
do
a
walk
through
the
site,
but
we
weren't
able
to
make
that
happen.
If
we
have
local
people,
we
should
probably
make
sure
that
we
have
somebody
doing
a
walk
through
the
site
at
some
point
before
we
get
there.
So
we
can
have
our
video
walk
through
or
something
yeah.
E
Just
that
that
will
also
you
know
depend
on
whether
the
whether
the
LF
can
get
that
taken
care
of
as
well,
because
it
has
to
be
coordinated
when
they
do
their
walkthroughs.
And
if
the
venue
is
okay
with
a
outside
member.
Also
walking
through.
E
They've
done
the
camera
thing
in
the
past,
I
just
I,
don't
think
Rianne
was
able
to
do
it
this
time
around.
A
B
I
mean
that
said.
Moving
on
to
the
second
item,
which
was
having
us
have
sort
of
our
own
complex,
that
was
this
one
wing
of
the
convention
center
was
awesome
because
one
of
the
problems
we've
had
with
some
past
contributor
Summits
is
the
inability
to
control
the
space
which
resulted
in
having
a
lot
of
sort
of
random
tourist
wandering
through
the
space,
and
we
did
not
have
that.
B
This
time,
the
and-
and
it
was
nice
but
to
you
when
you
combine
that,
with
the
enormous
amount
of
lounge
space
there
was
in
this
venue,
it
really
gave
people
what
I
think
they
want
most
out
of
a
contributor
Summit,
which
was
the
ability
to
sit
down
and
chat
with
other
contributors.
D
A
It
related
to
that
the
number
of
times
that
we
shouted
okay
sessions
are
starting
and
people
just
kind
of
look
and
be
like
okay,
we're
going
back
to
talking
because
we're
having
a
coffee
and
we're
sitting
at
a
table.
Yeah
I
think
focusing
on
that
as
I.
Don't
want
to
call
it
a
track
but
yeah
focusing
on
that
space
as
a
track.
B
I
I
think
for
any
future
contributor
Summit.
We
have
to
assume
that
at
any
time
after
the
opening
session,
50
of
the
attendees
are
going
to
be
sitting
or
standing
around.
You
know
in
the
hallway
or
in
the
common
space
talking,
because
that's
you
know
with.
However
many
we've
done
of
these
I
don't
know
eight.
You
know
10
contributor
Summits.
That
is
clearly
what
people
want
out
of
a
contributor,
Summit
and
and
I
am
I'm
into
just
embracing
that
yeah.
F
B
And
what
I'm
saying
is
when
we're
thinking
about
the
number
of
concurrent
sessions
we're
going
to
have
in
any
time
slot?
We
should
think
in
terms
of
only
50
of
the
attendees
being
in
those
sessions
and
they're
they're
50
not
being
in
right,
and
so,
if
you
look
at
those
numbers-
and
you
say,
hey
you
know,
50
is
80
people
and
we've
scheduled
five
concurrent
sessions.
We
might
want
to
cut
that
down
to
four.
If
you
follow
me,
yeah
the
because
this
was
something
reserved.
San
Diego
was
particularly
chronic
and
San.
B
Diego
I,
actually
measured.
70
of
people
were
out
in
the
hallway,
oh
the
so,
and
it
was
a
problem
because
we'd
scheduled
six
concurrent
sessions
and
some
of
the
sessions
had
no
audience
I.
A
A
I
didn't
see
any
I
mean
my
unconference
only
had
three
people
in
it
because
we
announced
it
and
said
it's
happening
right
now:
okay!
Well,
that's
fine,
but
that's
that's
an
announcement
issue.
Yeah.
F
Yeah
my
my
concern
right
is
that
a
lot
of
people
are
not
used
to
sort
of
like
how
to
how
to
be
like
welcoming
when
they're
like
talking
in
groups,
so
I
think
I
will
make
it
a
point
to
make
sure
that
we
talk
about
like
the
pizza,
like
Pac-Man
method
or
like
yeah,
try
to
make
sure
that
you
know
if
we're
gonna
do
this
intentionally,
that
we
actually
have
some
structure
in
place,
so
it
doesn't
end
up
leaving
people
feel
like.
Oh
well,
I,
don't
know
anybody
here.
E
Didn't
quite
pan
out
the
way
we
thought
it
would.
B
The
well
actually
one
of
the
things
I'm
thinking
about
is
actually
a
less
planned
version
of
that
like
what,
if
we
had
something
like
a
little
standing,
you
know
clipboard
or
whiteboard
on
the
tables,
so
that
if
a
group
of
people
get
together
who
happen
to
be
saved,
the
release
engineering
team,
they
can
just
write
release
engineering
team
on
the
thing
and
drop
it
in
the
center
of
the
table.
In
case
anybody.
You
know
who's
a
release.
Engineering
Shadow
wanders
by
they
can
join
but
require.
A
B
F
I
guess
I
guess
for
me
if
it's
gonna
be
like
a
sort
of
team
meeting
sort
of
thing
that
there
should
be
like
some,
like
perhaps
preparation
or
notification,
so
that
there
isn't
any
wondering
from
the
folks
that
are
there
but
I
think
for
you
know,
people
who
are
coming,
who
don't
necessarily
have
a
strong
affiliation
with
like
a
particular
group
or
they're,
just
trying
to
meet
people
and
feel
like
belonging
in
the
community.
You
know
like
not
necessarily
like.
F
B
Need
to
brainstorm
ideas,
we
need
to
assume
that
hallway
track
is
going
to
be
a
major
part
of
the
contributor
Summit
and
we
need
to
brainstorm
ideas
to
make
that
not
become
cliquish.
Yeah
yeah,
the
yeah
I
mean
because
really
what
people
are
doing
is
these
are
people
they've
worked
with
online
for
the
last
year
and
have
not
seen,
and
they
want
to
catch
up
with
them
right,
yes,
and
we
don't
want
to
disrupt
that.
We
just
want
to
make
it
inclusive.
B
F
B
B
One
of
the
things
I
was
going
to
say
and
I
didn't
actually
put
this
initiative.
Add
this
to
the
notes
is
I
felt
like
this
contributor
Summit
was
really
good
from
a
perspective
of
getting
useful
work
done.
If
you
follow
me
that
is
I
felt
like
one
of
the
things
that
hamstrung
Us
in
Detroit
was
that
for
so
many
of
the
sort
of
meeting
discussion.
If
sessions,
we
just
didn't
have
enough
of
the
right
people
in
the
room
to
actually
make
decisions,
and
it
was
different
in
this
one
right.
B
The
website
working
session,
the
the
LTS
session
right.
They
came
out
of
there
with
a
decision
to
resurrect
the
the
the
wglts.
B
You
know
and
other
things
that
bring
me
back
to
how
the
contributor
Summits
were
like.
You
know
four
years
ago
when,
when
they
really
were
sort
of
dominated
by
working
sessions
and
and
long
interminable
arguments
about
things
that
we
couldn't
fix,
the.
C
F
E
Website
I
I,
think
part
of
it
is
we're
now
sort
of
coming
out
of
the
post-coveted
era,
because
yeah
like
right
after
covet
and
people
getting
around
and
together
for
the
first
time
again,
you
know
it's
it's
much
more.
There
is
much
more
of
a
social
Focus
just
like
it's
been
forever
since
I've
seen
you
and
you
know,
want
to
catch
up
and
now
we're
getting
to
the
phase
of
where
we
can
do.
You
know
we
can
do
work
again
if.
B
That
makes
sense
the
I
mean.
The
other
thing
is
I
think
it's.
It
was
just
turnout,
as
in
I
remember
having
discussions
in
Detroit
where
we
were
like
okay.
These
are
some
good
ideas,
but
we
can't
really
do
anything
about
them,
because
X
person
isn't
here
the,
whereas
that
just
didn't
seem
to
happen
as
much
in
Amsterdam
and.
E
F
And
and
for
me
right
like
buying
that
explanation,
right
and
thinking
about
repeatability
and
how
to
replicate
it
right
like
what
what
needs
to
happen
right
like
it
was
in
Europe,
so
like
people,
if
they
were
paying
had
to
be
motivated,
had
to
come
out
of
pocket.
You
know
a
fair
amount
to
make
it
work,
whereas
now
we're
going
to
be
in
Chicago
like
does
that
diminish?
Perhaps
that
factor
or
like
what
do?
We
need
to
do
to
make
sure
that
the
next
time
is
still
like
fruitful
and
that's
the
way
this
one
I.
E
Think
part
of
it
is
like
there.
There
have
been
a
lot
of
these
sort
of
larger
topic
things
sort
of
circulating
in
the
background,
and
you
know
we
can't
necessarily
dictate
that
for
the
project
itself,
of
course,
so
like
before
the
LTS
discussion,
there's
been
a
large
discussion
going
on
about
like
expanding
skew
and
you
know,
maybe
we
don't
do
LTS.
E
Instead,
we
just
you
know
we
expand
our
SKU
support,
so
people
can
you
know
Skip
releases
for
upgrades
and
there
have
been
some
of
these
bigger
discussions,
sort
of
going
on
amongst
the
sigs
in
the
background
and
I
think
you
know
that's
part
of
what
fed
into
this
being
a
you
know.
More
successful
event
was
just
that
there.
There
are
these
background
issues
and
people
are
actively
working
and
they
want
to
get
together
and
meet
and
talk
about
them.
B
B
Actually
happened:
majority
of
people
chose
the
contributor
Summit.
If
you
follow
me
that
that
we
actually
had
less
people
unable
to
attend
session
because
of
their
obligations
outside
than
we've
had
in
the
past
no
mind,
you
I
might
be
wrong
about
that,
because
obviously
I
saw
the
people
who
chose
the
contributor
Summit
the,
but
it
does
feel
contrary
to
my
personal
expectations
like
the
Tuesday
conflicts
were
not
actually
as
bad
as
they've
been
as
the
as
the
mundane
conflicts
were
in
the
past.
There.
E
Were
a
lot
less
colos
yeah
and
also
most
of
the
vendors
decide
to
have
their
vendor
specific
events,
not
on
Tuesday
to
avoid
you
know,
conflict
with
you
know
all
the
colors,
whereas
before
with
it
being
two
days,
you
know
you
kind
of
had
to
pick
like.
Okay,
which
day
do
we
conflict
with
yeah.
B
F
I,
wasn't
there
for
most
of
the
day
right,
but
like
I
did
pop
by
the
like
Argo
con,
and
it
was
rammed
with
people
like
they're,
like
oh
yeah,
so
yeah
and
seeing
that
both
were
like
well
attended
and
seemingly
targeting
their
prospective
audiences.
You
know
that
was
that
was
interesting.
F
Contributor
or
something
that's
fair,
because
some
of
them
did
like
sell
out.
You
know
yeah
all
right,
yeah,
interesting.
B
Yeah
anyway,
I
would
still
like
to
do
contributor
survey
and
see
what
the
conflict
picture
looks
like,
but
right
now,
I'm
not
inclined
to
suggest
asking
for
a
time
slot
move.
B
I
I,
don't
see
evidence
that
it
would
be
a
net
benefit.
We.
C
C
F
G
B
H
A
note
about
surveys
in
general.
It
would
be
good
to
actually
have
that
survey
in
the
opening
remarks
link
like
in
the
slides
just
a
note
for
the
future,
because
generally
people
don't
check
their
email.
So
if
you
want
to
get
a
really
good
response,
either
have
it
in
opening
or
if
you
have
closing
remarks
which
we
didn't
have
something
where
it's
easily
posted
day
of
where
people
can
grab
it.
Qr.
C
A
F
Yeah
yeah
I
feel
like
having
QR
codes,
not
necessarily
as
like
an
entrance
ticket
to
the
like
contributor
celebration,
but
at
least
like
around
perhaps
and
I,
don't
know
if
there's
some
incentive
that
we
can
add
raffle.
F
B
Yeah
I
can
I
can
commit
to
throwing
in
a
kubernetes
beer
stein.
For
that.
H
Yeah
yeah,
but
anything
like
that
if
you
want
to
get
a
lot
of
responses
just
day
of
while
it's
front
front
of
mind,
is
better
than
an
email,
because
a
lot
of
people
miss
them.
Yeah.
H
There
you
go
get
people
to
show
up,
yeah,
yeah,
nice,
I
I
was
gonna,
say
one
of
the
things
I
I
said
lower,
but
I'll
mention
it.
Now
is
the
idea
of
maybe
having
specific
badges
just
for
contributor
Summit,
where
people
go
and
they
pick
them
up,
because
it's
a
little
easier
to
tell
you
could
put
the
QR
code
on
the
back
of
it
or
on
the
inside.
That
just
says.
Fill
this
out
show
up
at
Sig
meet
and
greet
hand
in
your
little
ticket.
H
A
All
right
and
actually
talking
about
QR
codes
leads
into
the
next
thing
on
the
list,
and
that
is
that
having
shortcuts
was
generally
useful,
having
the
short
lengths
having
the
QR
codes
around
being
able
to
paste
them
like
Brianne,
printing
out
the
QR
codes
as
stickers
and
slapping
them
on
signage
was
really
really
helpful
and
throw
also
throwing
them
up
in
the
intro
slides,
saying:
look,
we
know
you're
not
going
to
type
and
they're
like
here.
It
is
pull
out
your
phone
right
now
we're
leaving
this
up
for
10
seconds.
E
One
suggestion
when
we
do
put
that
up
with
the
notes
tell
people
to
remember
that
you
have
to
be
a
member
of
kdev
and
log
in
with
that
email
to
access
the
notes,
because
I
was
getting
dozens
of
access
requests
from
people
trying
to
do
stuff.
It's
just
like
we're
not
going
to
open
it
up
to
the
Internet
for
people
to
edit
it
yeah.
A
Sorry
I
got
it's
very
dusty
in
the
desert
right
now.
Okay,
what
else
went
well
going
back,
oh
being
able
to
say,
hey
the
celebration,
see
that
fence
over
there?
That's
it
like.
A
B
Pretty
much
venue
was
Barcelona
Maybe
somewhere,
where
we
had
a
very
nice
venue
like
it
was.
It
was
a
really
nice
place,
but
it
was
like
a
30-minute
train
ride
away
from
the
venue
and,
as
a
result,
turnout
was
like
10
people,
total
mm-hmm,
and
so
that
clearly
showed
us
the
limits
of
things
right,
because
San
Diego
it
was
about
three
quarters
of
a
kilometer
away,
still
packed
full
yeah
right.
A
E
Usually
something
that
we've
always
weighed
in
when
doing
our
venue
selection,
it's
it's
usually
like
we've
tried
to
stay
within
a
10
minute,
walk.
A
Maybe
we
even
look
at
a
Kate's
bus.
E
F
We
did
it
for
Valencia
as
well.
Yeah.
F
B
What's
next
so
things
that
didn't
work
so
well,
which
we
have
a
whole
variety
of
I'll,
kick
it
off,
because
I
put
the
first
one
in
there,
which
is,
there
was
some
kind
of
a
problem
with
the
magic
we
haven't
heard
back
from
cncf
events,
what
happened
but
somehow
a
minority
like
like
I,
don't
know
one
out
of
20
of
the
people
who
registered
did
not
get
contributor,
Summit
badges,
the
and
you
know
we
dealt
with
it
at
the
time,
but
it
was
obviously
a
bad
experience
for
some
of
them
and
it
would
be
nice
to
know
what
happens
to
it
doesn't
happen
in
Chicago.
G
Do
you
happen
to
know
their
names,
maybe
a
couple
names,
so
we
can
backtrack
and
verify
what's
happened?
We.
B
Can
back
scroll
through
Summit
staff
because
some
of
them
got
mentioned
there?
Okay,
I
did
notice
that
at
least
two
of
them
were
in
the
very
last
batch
of
people.
We
approved
I,
don't
know
about
the
others,
though,.
A
B
Well,
I
mean
I
would
say
actually
for
this
particular
coupon,
they're
literally
I
know
there
were
people
at
my
company
because
I
handled
the
list
of
who's
going
from
my
company,
who
were
not
definitely
approved
until
a
week
before
the
event.
B
Okay,
so
yeah
and
I
have
a
feeling
that
the
same
will
be
true
with
Chicago
from,
for
you
know,
a
minority
of
American
attendees,
where,
where
they're
effectively
going
to
be
contingent
approval
based
on
how
the
company
does
this
quarter
or
whether
or
not
one
of
their
co-workers
cancels.
B
And
so
I
think
we
need
to
come
up
with
a
way
to
encourage
people
to
register
earlier,
because
I
don't
think
we
can
realistically
close
registration
until
you
know
the
last
day
that
events
tells
us
they
can
accept
people.
H
F
H
Conferencebatches.Com
I
I've
now
been
telling
people
about
this
everywhere.
Ever
since
we
used
for
pi
Texas,
it
just
requires
a
printer.
You
can
print
them
day
of
which
is
kind
of
nice,
but
like
you,
can
get
them
in
all
kinds
of
different
kits.
But
the
nice
thing
about
having
a
badge
that
you
can
kind
of
clip
onto
your
current
badge.
Almost.
Is
that,
like
it's
easy?
Actually,
it's
really
easy
for
people
to
see
that
you're
supposed
to
be
there,
which
I
know
with
a
lot
of
Volunteers
in
various
spaces.
H
E
G
One
other
issue
is
this
time:
with
registration
on
system
we
did
not
close
registration
at
all
I
think
there
are
a
lot
of
people
who
are
registered
on
Saturday
and
even
Sunday.
I
was
supposed
to
be
Regis
closed
on
Thursday
or
Friday
before
the
event,
and
some
people
would
well
we
need.
Basically,
we
need
to
test
if
it's
actually
closed
or
not
I
guess,
maybe
that's
one
of
the
reasons
why
we
had
several
problems
with
registrations.
Oh.
G
G
E
So
one
thing
the
the
reg
team
was
not
added
to
the
community
group.
There
was
puya
was
added,
no
no
I,
don't
know
if
you
were
at
it
or
not,
but
we've
been
directing
all
the
reg
requests
to
community,
and
so
we
were,
we
were
getting
a
bunch
of
emails
with
people
asking
questions
and
like
hey,
I
I
have
these
food
restrictions?
Is
that
a
thing
and
like
the
only
people
that
saw
those
were
essentially
me
and
Josh.
A
A
E
The
the
next
thing
was
the
red
sheet
wasn't
frequently
being
updated
with
the
org
member
list,
so
a
lot
of
people
were
being
flagged
as
not
org
members,
but
were
actually
org
members
and
having
to
basically
go.
Do
a
manual
check
now.
A
Maybe
we
should
just
add
something
to
the
reg
field
that
says:
have
you
become
a?
Have?
You
become
an
org
member
in
the
last
three
months
we
can
just.
E
A
G
Yeah,
it
will
be.
One
of
the
reasons
is
because
it's
not
clear
who
approved
or
denied
and
I
think
it
would
be
good
to
have
that
feedback.
I,
don't
know
tracking
who
actually
approved
the
who
denied,
because
I'm
not
sure
I
wasn't
sure
as
well.
A
lot
of
people
are
trying
to
update
registrations
and
some
of
those
people
know
at
least
for
registrations.
There
were
at
least
three
or
four
Shadows
and
I'm,
not
sure,
they're,
all
very
deliberate
and
all
very
careful
with
approval
or
denial
and
I'd
like
to
have
a
tracking
that.
G
A
Okay,
yeah,
that's
a
good
idea
and
helps
address
one
of
the
things
farther
down
need
to
be
clear
on
who's
allowed
and
when
the
last
approvals
are
allowed
for
social
guests,
yeah.
E
A
E
Like
emails
to,
like
you,
know
a
couple
hours
before
the
social
asking
for
you
know,
guest
approvals
for
the
social
I
I
think
we
honestly
just
said
the
same
date
that
when
reg
closes,
you
have
to
email
us
before
reg
closes,
if
you're
bringing
a
guest
and
give
us
their
name.
A
A
A
B
The
operational
room
monitors
were
not
told
that
part
of
their
job
was
to
cut
speakers
off
when
they
were
over
time
because,
like
I
literally
actually
talked
to
one
of
the
room,
monitors
and
I
said
he's
over
time.
You
need
to
cut
him
off
and
the
room
monitor
said
I
I,
don't
do
that.
C
B
That's
nice,
so
so
that
was
a
a
Miss
in
the
room
instructions,
but
the
yeah,
because
it
yeah
that
cascaded,
because
we
had
another
issue
that
I
don't
know
how
we
could
have
anticipated
and
it's
actually
an
open
question
of.
How
can
we
anticipate
sort
of
issue?
Was
we
didn't
know
that
there
was
a
law
in
the
Netherlands
that
coffee
has
to
be
served
by
people
and
therefore
a
20-minute
coffee
break
was
nowhere
near
long
enough?
Oh
Lord
wait.
B
H
B
B
B
You
know
these
sorts
of
things,
the
I
kind
of
think
in
general,
in
in
terms
of
being
realistic
about
the
hallway
track
that
we
should
probably
plan
to
have
30
minute
breaks
and
and
not
try
for
a
15-minute
breaks,
because
I
don't
think
15
minute
breaks
are
ever
going
to
end
up
being
only
15
minutes.
Yeah.
A
E
B
C
H
But
I
was
gonna
say
the
the
Linux
Foundation
should
know
this.
They
should
know
all
of
that
information
so
like.
That
should
be
something
we
just
need
to
ask
every
time
or
that
needs
to
be
part
of
like
a
pre-planning
session
of
going
to
the
cncf
saying
what
weird
things
don't
we
know
about
like,
for
example,
I,
don't
know
if
anybody
else
knows,
but
apparently
the
all
the
entire
kubecon
EU
was
not
free
by
requirement,
and
they
didn't
tell
anybody.
A
H
Events
person
had
some
extra
peanuts
that
they
had
gotten
for
themselves,
and
so
they
had
just
had
them
sitting
on
our
booth,
we
had
a
cncf
staff
like
a
Linux,
Foundation
staff
person
come
bolting
up
to
the
booth,
because
apparently
they
had
told
the
Rye
that
it
had
to
be
completely
nut
free
throughout
all
of
the
conference.
Okay,.
D
H
B
But
we
always
have
to.
We
always
have
to
assume
that
there's
going
to
be
things
that
we
don't
hear
about
in
a
timely
fashion,
because
even
if
we
specifically
go
over
this
with
the
event
staff
yeah,
that
sort
of
information
like
the
nut
free
thing
might
be
something
that
only
one
member
of
their
event
staff
knows.
B
And
has
not
actually
circulated
among
the
total,
Linux
Foundation
event
staff
right,
so
the
people
who
are
arranging
the
catering
on
the
Linux
Foundation
side
were
made
aware
of
that,
along
with
a
whole
long
list
of
other
things
and
as
a
result,
they
just
didn't
pass
it
on
as
significant
the
so
there's
always
going
to
be
stuff
like
that.
I
mean
I.
Think
the
real
takeaway
from
this
is
just
make
the
breaks
30
minutes,
and
that
way
we
also
have
some
squeeze
time.
If
a
session's
running
late.
A
Having
that
that
kind
of
plays
into
the
the
next
point
that
you
had
brought
up,
where
you
talked
about
Josh
mentioned
the
Forum
sessions
needed
longer
time
slots,
is
that
inherent
to
The
Venue?
Is
that
inherent
to
things
that.
B
We
know
yeah,
so
these
were
the
ones
in
the
main
big
room,
right,
yeah
that
were
scheduled
this
30
minute
ones
that
were
largely
presentations.
The
problem
is
that
most
of
them
were
not
actually
presentations.
They
were
a
short
presentation
meant
to
start
a
discussion,
but
because
they
were
in
a
25
minute
time
slot.
There
wasn't
enough
time
for
a
discussion.
B
A
That's
that
I'd
put
that
back
on
in
the
reg
section,
actually,
almost
or
no,
because
cfps
are
going
to
fall
under
here.
People
request
their
time
slots
and
if
they
say
I
want
a
25
minute
slot
or
I
want
a
55
minute
slot,
which
is
an
option
for
them
to
select,
if
they
say
a
25
minute
slot
and
they
didn't,
they
actually
needed
more
there's
not
much.
We
can
do
if
they
underestimated
how
much
time
they're
gonna
need.
E
So
yeah
one
one
quick
thing:
we
have
12
minutes
left
at
least
for
the
scheduled
time.
Jesus
I
don't
have
anything
after
this
and
can
continue.
But
I
don't
know
about
other
folks.
A
You
know:
do
we
want
to
just
pick
up
with
a
part
two
next
week
and
keep
going
on?
This
is
Laura's.
B
If
you
don't
mind
my
driving
for
a
short
time,
I
think
we
can
actually
zip
through
most
of
the
what
went
wrong,
because
a
lot
of
these
are
just
things
we
needed
to
mention
to
keep
track
of
them.
So
we
try
to
avoid
them
next
time
like
the
well,
the
unconference
scheduling
is,
is
actually
not
one
of
those.
So
let
me
let
me
go
through
the
other
ones
that
are
just
quick
ones.
B
End
of
cfp
was
was
too
late
for
good
scheduling,
I,
which
we
mentioned
before
the
other.
One
is
the
schedule
we
didn't
get
up
any
kind
of
a
schedule
until
shortly
before,
like
not
even
one.
That
said,
the
contributor
summit
starts
at
X
time
and
ends
at
X
time,
even
if
we
didn't
have
anything
in
between
the
so
it's
something
I
think
we
need
to
actually
do
next.
Time
is
to
actually
have
the
schedule
arrive
in
various
stages.
B
You
know
first
general
timing,
then
specific
blank
schedule
and
then
the
full
schedule
I.
We
need
to
remember
to
request
power
for
the
workshop
room
because
it
didn't
have
any
the
the
shadow
thing
actually
I
think
we
need
to
revisit
that's
going
to
require
discussion.
B
We
just
have
to
anticipate
that's
going
to
be
the
case,
and
that
actually
should
be
what
the
Shadows
are
for,
but
the
as
we
mentioned
previously
is
we
should
create
more
Perler.
We
should
create
the
survey
in
advance
of
the
event,
one
of
the
other
things
that
came
down
to.
B
Oh,
this
should
have
gone
under
things
to
do
next
time,
and
we
didn't
mention
this
bad
thing.
So
the
the
Sig
meet
and
greet
was
poorly
attended
by
new
contributors
like
very
poorly,
despite
being
in
a
location
that
was
convenient
to
Launch
and
actually
sort
of
generally
Central
and
being
on
the
schedule.
B
Handbook
I
put
a
whole
schedule
of
announcements
that
were
supposed
to
be
made
to
the
Sig
meet
and
greet,
and
not
all
of
those
happened
because
of
the
hand
back
and
forth
between
Kim
and
Laura
the
yeah.
B
It
was
down
under
the
stairs
as
Laura
points
out,
but
they
didn't
put
big
signs
out,
but
the
other
big
thing
that
we
came
away
from
it
that
Laura
and
I
Kim
and
I
were
discussing
is
we
need
to
rename
it
people
don't
know
what
the
heck
a
sigma
and
greet
is
and
I
think
we
need
to
to
rename
it
to
make
it
more
generally
appealing
to
potential
new
contributors.
H
Yeah,
if,
if
you
go
down
underneath
the
things
we
should
do
next
time,
the
suggestion
was
kubernetes
new
contributor,
Brown
Bag
as
a
possible
option,
or
something
like
that
indicating
like
bring
your
lunch.
Come
sit,
come
discuss
with
people
who
are
doing
things.
B
Okay,
so
a
couple
discussion
items
here
so
first
of
all
unconference
scheduling,
so
we
had
had
the
the
issue
with
the
unconvert
slots.
Noah.
A
It
just
it's
easy
for
an
hour
to
get
away
from
you,
while
you're
on
site,
but
that
hour
makes
a
huge
difference
in
being
able
to
schedule
these
things
and
getting
them
attended
to
making
sure
people
know.
When
of
when
particular
topics
are
going
to
be
discussed.
B
Yeah,
the
we
didn't,
we
didn't
have
a
big
unconference
board.
The
way
we've
had
it.
Some
contributor
summons.
B
A
Doing
it
all
in
in
GitHub,
while
while
it
was
good
for
being
able
to
do
upvotes
I,
don't
think
it
was
as
prominent
in
people's
you
know,
it
wasn't,
as
in
your
face,
yeah
sure
and
having
someone
be
able
to
coordinate
the
two.
If
we're
gonna
do
GitHub
then
still
also
having
a
physical
board
and
saying
nope.
These
are
ahead
in
the
race
or
whatever
method
we
want
to
use
having
them.
A
B
E
For
the
I
I
would
also
just
flat
out
set,
you
must
be
an
org
member
or
sponsored
by
a
lead,
because
so
many
of
them
just
completely
utterly
flaked
out
yeah.
B
Well,
there's
some
of
the
stuff
one
I
think
I
think
we'll
want
to
make
some
exceptions
like,
for
example,
I'm
thinking
for
Chicago
drafting
a
member
of
our
event
staff
and
that's
somebody
who's,
not
an
organ
member
and
will
never
be
an
org
member.
But
they
would
be
super
useful
to
have
at
the
event
yeah.
B
Individual
exception,
rather
than
a
policy
the
so
I'm.
You
know
you.
Other
people
heard
me
this
in
the
release
team
I'm
very
much
a
fan
of
people
should
have
like
one
Shadow
or
if
they
have
a
task.
That
is
highly
distributable,
like
you
know,
maybe
two,
and
that
we
should
also
differentiate
between
shadows
and
staff.
B
If
you
follow
me,
that
is
like
look
at
this
Way
say,
say:
I'm
in
charge
of
operations
right
on
site,
right,
I,
have
a
shadow,
and
that's
somebody
who's
there
to
learn
the
job
and
take
over
if
I
get
sick
the
day
before
the
contributor,
something
right.
At
the
same
time,
I
have
like
five
staffers
who
are
going
to
be
like
room,
monitors
and
stuff,
but
those
are
not
Shadows
they're
different
from
Shadows.
A
B
No,
but
it's
the
same
as
true
as
registration
is
that
registration,
you
have
both
staffers
and
a
head
of
registration
Shadow.
A
lot
of
the
a
lot
of
the
roles
break
down
to
a
difference
between
shadows
and
volunteers,
the
and
and
I
think
it
would
also
change
people's
attitude
towards
their
expectation
of
doing
work.
B
D
A
B
Well,
because
what
right
again
operations?
This
is
a
nice
one.
Right
is
the
maximum
number
of
people
you
need
for
operations
is
like
the
number
of
rooms
you
have,
plus
one
the,
and
you
know,
and
reg
decides
how
many
people
they
need
right,
which
is
probably
generally
going
to
be
in
the
two
to
three
range.
I
Chat
about
comms
I'll,
say
it
aloud
as
well
comes
also
could
use
Volunteers
versus
Shadows
because
they're
those
who
we
want
to
train
to
be
able
to
take
over
the
role
of
deciding
which
comms
go
out,
and
there
are
those
who
would
like
to
volunteer
to
help
write
those
comms
and
just
contribute
that
way.
So
there's
a
difference.
There,
too.
A
We
got
we
got
two
minutes
by
the
way
for
anybody
that
is
gonna
need
to
drop
yeah.
What
do
we
got
left.
B
Well,
the
rest
of
it
is
going
to
be
things
we
should
do
next
time,
so
the
question
is
which
things
have
we
not
already
talked
about?
Yeah.
E
A
That's
big
yeah
pre-populating,
the
docs
yeah.
We
forgot
to
do
that.
We
talked
about
on
conference,
we
talked
about.
We
really
need
the
cfp
to
close
earlier.
A
Okay,
the
Shadows
is
a
big
one,
rename
the
meet
and
greet
at
least
one
person
from
cncf
stuff
meet
and
greet.
E
A
E
Brienne
was
supposed
to
be
there
yeah,
but
unfortunately
she
got
sick.
Oh.
B
H
The
material
Shaw
showed
up,
and
then
we
were
trying
to
kind
of
move
things
around.
We
might
need
to
kind
of
revisit
how
much
the
meet
and
greet
coordinator
does
like,
because
I
think
part
of
it
really
needs
to
be
the
day
of.
You
need
to
be
like
at
the
door
saying
hi
directing
people
where
they
need
to
go
kind
of
thing
that
might
need
to
be
like
Express
ex
expressly
written
down.
So.
G
B
H
B
B
And
and
yeah,
and-
and
that
was
the
case-
that
was
another
example
actually
of
the
Shadow
Dynamic,
not
quite
working
correctly,
because
one
of
the
things
that
we
should
be
doing
with
our
shadows,
if
you're
a
lead
for
a
section,
is
that
the
person
who
is
your
specific
Shadow?
You
should
be
working
with
them
every
time
you
do
something
and
therefore,
if
they
have
to
take
over
unexpectedly,
they
know
exactly
where
you
left
off
and.
D
A
I'm
I'm
100
certain
that
people
were
reaching
out
to
Bob,
even
though
Bob
wasn't
officially
running
it
and
I'm
willing
to
bet
people
were
reaching
out
to
you.
Josh
and
I
got
dragged
into
things
and
I'm
like
that's
great,
but
puya
and
Nigel
are
not
on
this
team,
and
there
are
three
people
that
are
leads
right
now,
including
the
shadow.
G
B
Oh
yeah,
let
me
go
back
and
just
drop
a
brief
note,
because
it's
just
you
know
things.
I
forgot
for
the
Retro
by
the
way,
so
I
felt
like
the
activities
that
we
did
at
the
social
were
very
suited
for
the
venue.
So
let
me
actually
put
that
in
there
yeah.
H
That's
probably
a
lot
easier
than
trying
to
remind
people-
oh
hey,
you're,
reaching
out
to
the
old
league.
Go
to
this
lead
Etc.
However,.
A
H
E
I
think
this
is
just
specifically
for
tagging.
People
like
hey,
if
you're
having
a
problem,
either
email
this
address
or
tag
the
slack
handle
in
the
contributor
Summit,
Channel
yeah.
D
E
D
B
D
D
B
E
Flake
one
would
probably
be
pretty
good
from
what
Antonio
ran
and
we've
run
the
deflating
one
in
the
past
as
a
general
one.
In
the
past
too,
yeah.
B
But
I
also
want
a
social
activity
for
new
org
members
yeah,
because
again
we
were
talking
about
before
the
problem,
with
the
hallway
track
and
potential
hook.
Engineers
is
that
one
of
the
big
portions
with
new
org
members?
We
don't
want
them
to
go
to
the
contributor
Summit,
not
talk
to
anybody.
E
B
Did
not
do
Bingo
and
I'm
not
sure
that
that's
what
we
should
go
back
to?
Okay,
because
at
least
in
Detroit
I'll
point
out
in
Detroit
only
like
eight
people
did
the
Bingo
and
I
know
we
had
no
more
new
org
members
than
that,
okay,
so
the
and
and
so
I
I
yeah
I
think
we
should
brainstorm
something
else.
A
Related
to
that
I
think
it
would
be
a
good
idea
to
make
it
a
formal
piece
of
running
the
summit
that
part
of
your
duty
as
lead
and
potentially
a
shadow
based
on
what
you
were
saying
earlier:
Josh
that
reviewing
the
rule
books
after
every
Summit
for
an
update
to
keep
them
more
updated.
B
B
B
E
No
because
I
know
I
wrote
a
separate
red
one,
Awards
is
separate
or
any
okay,
yeah
I
see
separate
at
least
registration
content,
marketing.
D
B
Well,
no
I.
In
the
past,
we've
had
separate
people,
but
it's
better.
If
we
have
the
volunteers,
it's
better
to
do
it.
That
way
because
running
an
unconference
is
its
own
thing,
and-
and
we
really
would
like
to
if
we
have
the
people,
it's
nice,
to
have
one
person
coordinating
the
pre-programmed
sessions
and
other
content.
Well,
a
second
person
focuses
only
on
the
unconference
I.
B
Yeah,
that's
fine!
If
we
have
eight
volunteers,
then
then
please,
let's
do
that
the
and
I
will
point
out
that
is
a
kubernetes
tradition
for
people
to
volunteer
to
be
a
shadow
thing
and
be
handed
a
lead
position.
D
B
The
so
yeah,
okay,
so
yeah.
We
need
to
straighten
some
of
that,
but
the
big
thing
is
to
actually
review
and
update
these,
because
a
lot
of
these
you
know
because
a
lot
of
these
are
either
going
to
be
incomplete
or
out
of
date.
A
B
A
B
E
Also
realized
that
the
the
reg
query
actually
isn't
in
the
reg
read
me:
there's
there's
a
part
of
it
in
a
commented
out
to
do
in
the
markdown
wow.
B
A
B
One
thing
on
run
books:
those
two
go
together
which
is
like
on
the
release
team.
One
of
the
items
in
the
runbook
should
have
a
section.
That
is
what
Shadows
are
doing
and
since
we've
explained,
there's
a
difference
between
shadows
and
volunteers
right,
here's
the
section
on
what
you
know
what
shadowing
this
is
like,
and
here's
the
section
on
the
volunteers
that
happen
in
the
section
generally
speaking
right,
the
volunteers
are
chosen
by
the
lead.
A
A
A
E
Was
like
I
can
comment
a
little
bit
on
that
one,
it's
just
like,
so
we
asked
for
the
like
to
push
to
do
stuff
all
in
GitHub
a
while
ago,
but
honestly
GitHub
is
not
great
for
spreadsheets
unless
you're
doing
like
an
actual
like
project
board,
but
that
doesn't
tie
into
everything
and
so
like
there's
an
old
template
that
Brienne
was
essentially
copying
and
putting
into
GitHub.
E
E
A
E
A
D
We'll
try
and
get
that.
A
I'm
gonna
start
on
the
runbook
for
Ops
this
week.
I'll
work
with
Frederico
too,
who
I
think
did
a
great
job
which
I
I
look
at
back
to
when
I
was
the
running
Ops
the
first
time
versus
running
Ops
like
the
fourth
or
fifth
time,
I
think
you
did
a
great
job.
E
I
I
thought
it
was
it
and
I
guess
it
is
not
I.
That's
my
my
mistake
on
that
one.
It's
there
there's
part
of
it
for
pulling
from
Dev
stats
in
a
commented
out
to
do
in
the
markdown,
but
if
you're
just
reading
the
markdown
markdown
doc
you're
never.
A
Going
to
see
it,
that
was
the
comment
you
mentioned:
yeah,
okay,
sure
I,
remember
what
we
talked
about
three
minutes
ago
on
it.
A
Can
you
can
you
link
that
in
then
yeah
it'll,
I'll
dump
it
in
there
work
with
Mars
and
get
that
in
there
Nigel's
gonna
be
running
The
Summit
in
Chicago,
I'm
gonna
back
him
up
anybody
else,
taking
any
lead
positions
that
they're
going
to
volunteer
for
Here
and
Now
did
not
think
so.
I
A
C
I
H
H
A
A
B
B
Diego
to
covid
and
our
first
two
contributor,
Summits
postcovid,
were
kind
of
thrown
together
at
the
last
minute
because
we
weren't
sure
if
we
were
having
one
or
not
yeah,
and
so
you
know
it's
and
prior
to
covid,
we
did
not
do
a
great
job
of
documenting
worlds.
B
So
so
you
know
we're
kind
of
having
to
rebuild
systems
and
even
for
those
of
us
who
have
been
at
every
contributor,
Summit
or
almost
everybody,
contributor
Summit
are
doing
the
whole.
What
did
we
do
in
Seattle?
Exactly
the
I
know,
we
did
something,
but
I
can't
remember
what
it
was
the
yeah.
So
so
there
was
a
lot
of
a
lot
of
even
with
this
one.
There
was
a
lot
of
remembering
a
little
late
things
that
we
were
supposed
to
have
taken
care
of
and
we're
not
in
docs
anymore.