►
Description
Speaker: Guinevere Saenger
A
A
This
is
a
huge
honor
for
me
to
be
up
here
and
help
you
all
get
started
so
we're
running
a
tiny
bit
behind
because
of
room
shuffling,
which
is
fine,
but
let's
get
right
into
it,
and
we
have
a
couple
introduction
things.
First
of
all,
welcome
to
Seattle
welcome
to
cube
con.
This
is
one
of
our
really
cool
ferry
boats
out
on
Puget
Sound.
A
So,
two
years
ago,
if
you
had
even
heard
about
kubernetes
that
was
sort
of
very
rare,
it
was
a
relatively
small
project
and
everyone
who
was
a
contributor
kind
of
knew
everyone
else.
Everyone
knew
all
the
moving
parts,
and
so
the
crew
was
kind
of
more
like
on,
like
a
small
little
sailing
ship,
where
you
know,
sometimes
you
get
doused
with
water.
Sometimes
you
fall
in,
and
people
have
to
fish
you
out,
but
in
general
you
know
everyone
and
you
kind
of
make
it
work.
A
That's
not
the
case
today.
Today
there
is
a
lot
of
rooms.
It
might
take
you
days
to
explore
the
entire
ship
and
I
mean
frankly,
sometimes
weeks,
and
it's
kind
of
important
that
you
know
what
your
place
is
and
who
to
talk
to.
If
you
want
to
fix
something
or
improve
something,
or
you
know
generally
make
the
ship
better.
A
We
also
now
have
a
fair
number
of
rules
and
processes.
Again,
this
isn't
too
increase
bureaucracy.
This
is
really
more
to
make
sure
that
everyone
knows
what
they're
doing
what
other
people
are
doing,
because
it's
just
become
an
enormous,
enormous
project,
which
is
great,
but
it
can
be
really
daunting
to
get
started,
which
is
why
you're
all
here
I
would
like
to
take
some
time
to
introduce
today's
mentors
that
are
here.
I
am
going
to
be
R.
A
Sankar
I
am
a
member
of
sig
contributor
experience,
you're
going
to
learn
all
about
SIG's
later
Josh
and
Noah
are
in
the
back.
You
don't
have
to
oh
yeah
I
guess
you
have
to
do
and
they
are
about
their
handing
out
some
pens
and
notepads
which
we
are
going
to
use
in
a
minute
later
on.
Tim
pepper
is
going
to
talk
to
you
about
local
test
and
build
of
the
kubernetes
project.
A
So
those
of
you
who
have
forked
and
cloned
that
repo
can
follow
along
and
it's
going
to
be
useful
for
everyone
and
that's
Tim
Mischel
is
going
to
give
you
a
tour
of
the
kubernetes
test
grid
which
she
actually
wrote.
So
this
is
really
really
exciting.
To
have
her
here
and
zach
is
going
to
talk
about
Doc's
contributions.
A
A
A
A
Great
I
also
see
that
we
have
pretty
good
concentration
of
people
at
each
table,
so
you
don't
have
to
do
that
great.
So
the
note
pads
you
just
got
does
every
table
have
a
note
pad
in
some
pens
awesome.
I
I
had
one
more
question:
is
there
anyone
in
the
room
that
has
contributed
to
a
kubernetes
project,
any
project
in
the
ecosystem?
A
A
A
A
A
Awesome:
let's
see
that
should
work
great,
so
if
I
could
have
everyone
at
the
table
write
down
their
github
handle
on
the
notepad
as
we
go
on,
if
you
have
already
committed
a
pull
request
or
open
a
pull
request
in
any
of
the
kubernetes
repositories,
I
want
you
to
put
a
star
next
to
your
name.
This
is
going
to
be
important
for
the
exercise
we're
going
to
do
this
afternoon.
That
is
all
this
is.
You
are
not
selling
your
souls
to
github
or,
to
me,
I
mean
I,
can't
vouch
for
Kelsey
great.
A
Awesome
so
today
we
are
going
to
walk
you
from
hey
I'm
new.
What's
going
on
all
the
way
to
meeting
people
that
can
further
continue
your
journey
as
a
contributor
after
coop
con
is
over,
so
we
will
all
have
a
chance
to
meet
some
folks
that
can
help.
You
continue
on
your
personal
journey,
we're
going
to
talk
about
where
to
contribute.
A
I
already
mentioned
the
test
script
or
the
dog
contributions,
we're
going
to
talk
a
little
bit
about
the
release
cycle,
because
that
is
another
way
to
contribute
to
contribute
and
and
then
we'll
round
out
the
day
with
meeting
people
from
all
the
kubernetes
six.
Well,
not
all
of
them,
but
the
ones
that
are
here
and
are
excited
to
have
new
members
awesome.
A
So
who
can
contribute
to
kubernetes?
Anyone
can
contribute
to
kubernetes
anyone
who's
excited
about
it.
Anyone
who
has
anyone
can
bring
something
to
the
table.
You
do
not
have
to
be
a
developer,
you
can
be
a
community
organizer,
you
can
write
docs.
There
are
many
many
ways
to
contribute
to
the
project
and
we
are
going
to
talk
about
a
lot
of
them.
In
general,
there
are
three
types
of
contributors:
there's
individuals
who
are
excited
about
the
project.
A
A
A
I
should
talk
a
little
bit
about
the
cloud
native
computing
foundation.
They
are
the
foundation
that
drives
the
kubernetes
project,
the
they
are
a
sub
foundation
of
the
Linux
Foundation.
In
my
mind,
they
are
almost
entirely
the
same,
but
that's
because
I'm
in
the
kubernetes
sphere,
the
cognitive
computing
foundation
promotes
a
cloud
native
open
source
stack.
A
Okay,
thank
goodness
I
was
like
alright,
so
joining
the
kubernetes
community
is
a
lot
like
choosing
your
own
adventure
book,
because
we
have
suggestions
for
you
how
to
get
started.
I'm
sure
everyone
in
this
room
knows
about
the
core
repository
kubernetes
in
the
kubernetes
project
on
github,
but
there
are
many
many
paths
to
get
started.
A
So
if
you're
here,
you
probably
have
a
reason
to
want
to
contribute
to
kubernetes
and
I'm
going
to
ask
folks
to
stand
up
if
the
description
applies
to
you,
how
many
of
you
use
kubernetes
a
lot
and
want
to
just
be
involved
in
the
project
to
improve
your
knowledge,
all
right,
very
cool,
that's
great!
How
many
of
you
thank
you?
How
many
of
you
have
already
contributed?
A
patch
I
asked
that
earlier
so
stand
up
again,
though,
so
everyone
can
remember
who
you
are.
A
A
So
maybe
you
are
not
involved
with
kubernetes
directly,
but
with
like
one
of
the
many
sub
projects.
For
example,
helm
is
a
really
really
big
one
any
home
folks
in
here
yeah,
so
those
are
also
ways
to
become
involved
in
the
community.
It's
it's
like
I
tell
people
it
does
not
have
to
be
core
kubernetes.
So.
A
Let's
go
ahead,
and
so
this
kind
of
flows
into
the
next
thing,
since
so
many
of
you
are
here
because
if
your
job
requiring
you
to
work
into
kubernetes,
some
of
you
might
be
in
a
situation
where
you
want
to
learn
it,
but
you're
not
entirely
sure
how
to
talk
to
your
boss
about
that.
So
there
are,
there
are.
There
are
some
logical
paths
to
get
started?
For
example,
if
you
work
for
a
storage
vendor,
you
could
start
with
container
storage
interface
in
the
kubernetes
community
and
kind
of
say.
Well,
you
know
this
seems
relevant.
A
A
So
in
this
community
a
lot
of
people
kind
of
have
an
origin
story.
I
got
started
via
the
contributor
experience.
I
was
asked
by
a
co-worker
to
submit
a
pull
request
to
a
kubernetes
project
and
it
turned
out.
It
was
really
really
really
hard
which
one
of
you
had
no
problem
at
all
signing
up
for
the
CLA,
but
not
everyone
right.
A
Some
people
had
struggles,
I
needed
to
get
in
touch
with
the
with
the
folks
at
the
support
center
who
had
to
email
the
help
desk
I
totally
had
to
email
the
help
desk
the
first
time.
So
my
first
issue
in
the
community
said
your
documentation
is
outdated
and
confusing.
That
was
literally
the
title.
I.
Don't
recommend
opening
with
that
clearly
I'm
still
here,
so
I
didn't
get
in
too
much
trouble,
but
we
have
a
code
of
conduct
and
we
should
be
polite
to
people
and
all
that
stuff.
A
So
I
wanted
you
all
to
think
about
your
origin
story.
Do
you
want
to
fix
bugs?
Do
you
want
to?
Are
you
excited
about?
Maybe
shipping
a
new
feature?
Do
you
want
to
learn
about
kubernetes
because
you're
new
to
it?
Do
you
want
to
learn
yet
you
get
the
idea.
I've
talked
about
it
a
lot.
It's
your
turn
to
talk
at
your
table
kind
of
go
around,
introduce
yourself.
What's
your
work
on
what
you're
interested
in
with
regards
to
kubernetes
go.