►
From YouTube: A Week in the Life of the Kubernetes Community - Dawn Foster, Pivotal & Jorge Castro, VMware
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
A Week in the Life of the Kubernetes Community - Dawn Foster, Pivotal & Jorge Castro, VMware
You’re new to Kubernetes and interested in contributing, but when you start poking through the community pages, you find a bunch of SIGs and so many meetings. What’s a SIG? Where should you start? Which meetings should you attend? How can you participate? In this talk, Jorge and Dawn from SIG Contributor Experience will live out a week within the Kubernetes community by walking the audience through what happens in this busy community. As part of the day by day tour of the community, we will cover: * Getting started and locating meeting calendars * Finding and participating in SIGs * Attending meetings and what to expect * How to get involved * Where to get help New contributors, users interested in contributing, engineering managers whose teams are contributing, and anyone interested in learning about new ways to get involved in the Kubernetes community will benefit from attending.
https://sched.co/UaVn
A
B
So
I've
worked
on
lots
of
projects
that
was
a
puppet
for
a
while,
as
director
of
community
I
was
the
community
lead
for
Intel's,
open
source,
Technology,
Center
and
now
I'm
doing
open
source
kubernetes
contributors
strategy
and
the
program
that
goes
along
with
it
at
pivotal,
open
source
could
be
a
really
small
world,
sometimes
right.
Well,
we
both
work
on
kubernetes.
Now,
we've
actually
known
each
other
and
work
together
when
I
was
a
puppet
and
George
is
at
canonical,
and
we
were
both
working
on
config
management
ages
ago,
open.
A
Source
is
big,
but
it's
not
that
big.
When
you
do
this
professionally
for
a
long
time,
you
meet
a
lot
of
people
who
work
on
different
projects
and
who
tend
to
know
each
other,
so
you
might
ended
up
meeting
someone
down
the
road
software
evolves
and
changes
constantly
and
while
you're
gonna
end
up
becoming
an
expert
in
the
software,
there's
no
better
investment
than
in
the
people
that
you
will
be
collaborating
with
throughout
your
open-source
career.
A
A
You
can
merely
just
consume
kubernetes
as
a
product
and
that's
totally
fine,
but
something
open-source
has
taught
us
is
that
getting
involved
and
contributing
ensures
that
your
organization
has
the
knowledge
and
expertise
to
shape
the
thing
that
runs
our
platform
so
think
of
it
as
an
investment,
it's
nice
to
be
able
to
use
a
tool
with
enough
proficiency,
instead
of
just
blindly
trusting
that
something
works
in
production,
so
you
might
say
I'm
gonna
get
into
kubernetes.
Your
boss
told
you
we
got
a
kubernetes.
What
do
you
do
you
Google?
A
You
end
up
at
the
web
site,
you
end
up
at
the
community
page
and
that
leads
you
to
the
community
repo.
You
might
find
the
calendar
so
we're
gonna
kind
of
give
you
a
deep
dive
or
a
guide
light.
Think
of
us
as
a
lighthouse
on
all
of
this
stuff
that
you're
gonna
find
on
the
Internet
and
kind
of
give
you
a
general
idea
of
where
to
go.
So
you
can
find
out
what
you
need
to
be
successful,
so
we're
gonna
do
some
definitions
here.
A
How
many
of
you
been
here
in
the
term
SIG's
a
week
right,
special
interest
group?
This
is
the
basic
working
unit
of
kubernetes
SIG's
own
specific
sections
of
code.
So
when
you
look
in
the
community
repo,
you
will
find
that
each
part
is
assigned
to
a
separate
sig.
Sig
meetings
are
all
public.
All
of
their
meetings
are
recorded
and
available
to
YouTube,
and
anyone
in
the
community
can
participate
in
a
sig
meeting.
There
are
no
secret
cabal
meetings
of
any
kind,
so
you
definitely
want
to
check
those
out
in
tern.
A
Sig's
are
divided
into
working
groups.
This
is
very
large
complicated
as
we
get
more
contributors.
We
have
to
subdivide
things
even
further,
so
you
might
see
in
a
sig
a
certain
amount
of
sub
projects
that
kind
of
divides
all
the
things
that
the
SIG's
are
responsible
for
into
more
much
more
Manimal
chunks,
and
each
of
these
sub
projects
might
have
their
own
meetings
thrown
YouTube
videos
and
things
of
that
nature.
A
Further
on,
we
have
working
groups,
so
sometimes
there
might
be
a
thing
that
needs
to
involve
multiple
SIG's,
because
you
can't
just
change
a
thing
and
affect
a
bunch
of
people
right.
So,
while
SIG's
do
concentrate
on
their
areas
of
the
code,
they
do
need
to
be
loosely
coupled
enough
to
work
together
when
something
touches
things
across
the
codebase.
So
they
might
do
something
like
former
working
group
as
a
temporary
working
unit
that
they
can
collaborate
with.
A
You
know,
maybe
for
a
year
six
months
or
whatever,
and
then,
when
they
accomplished
their
mission,
we
merely
fold
the
working
group
back.
These
are
constantly
evolving,
adding
and
being
removed.
There
are
three
committees,
a
steering
committee
which
we'll
get
to
later
the
product
security
committee,
which
is
the
ones
that
publish
all
the
Seavey's
that
you
see,
and
the
last
is
the
code
of
conduct
committee
which
handles
code
of
conduct
issues,
and
then
we
have
user
groups
which
is
our
newest
construct.
A
These
are
more
formalized
ways
for
users
to
be
able
to
support
themselves
and
organize
around
not
developing
kubernetes,
but
helping
you
find
a
place
for
you
to
get
help
among
people
that
have
might
have
similar
goals
as
you
and
then
the
a
group
might
be
able
to
feed
that
information
back
to
the
developers.
So
we
have
a
nice
tight
feedback
loop
from
what
we're
building
to
what
people
are
actually
using
and
how
they're
using
it.
A
So
like
everything
else
in
qubit
divinities,
we
define
the
community
with
a
yellow
file.
I'd
love
to
have
a
really
great
URL
for
you,
but
just
go
to
google
and
type
zig
zag
yam,
oh
yeah.
It
is
a
thing,
but
so
each
one
of
these
things,
the
cig
name,
what
they
do
when
they
meet
the
zoom
URL
of
the
link
to
their
notes.
The
link
to
their
archives,
all
of
these
things
are
maintained
in
a
llamó
file
and
of
course
we
don't
make
you
read
that
we
we
do
generate
a
user
friendly
page.
A
This
is
a
cig
list.
This
is
a
thing
that
sits
on
my
bookmarks
toolbar
and
what
we
do
is
we
give
you
a
nice
lead
of
who
the
co-chairs
are.
The
people
and
the
links
like
I,
said
to
the
YouTube
videos,
their
meetings
and
things
like
that,
and
then
we
take
all
of
that,
and
then
you
draw
it
into
a
pretty
air
picture
here.
A
Do
not
be
overwhelmed
when
you
see
this,
you
know
like
how
do
I
get
involved
with
kubernetes,
and
you
start
with
this
picture
and
you're
like
I'm
out
of
here
and
you're
walking
out
of
the
room
right.
This
is
very
complex
software.
What
we're
trying
to
do
here
when
you
build
a
platform
is
a
thing.
So
don't
even
worry
if,
if
this
is
too
complex
for
you,
the
people
who
created
this
can't
even
recite
this
to
you
so
and
that's
totally
fine,
that's
totally
fine
distributed
systems.
A
You
can
just
do
your
one
little
thing
and
as
long
as
you're
doing
your
thing,
everything
will
be
fine.
So
this
is
just
a
diagram
of
all
those
things.
A
lot
of
their
titles
are
self
descriptive,
but
we'll
get
into
some
of
them
here
in
a
little
bit
and
of
course,
here's
the
calendar
or
SIG's
yamo.
You
can
just
add
that
to
your
calendar
and
all
of
the
meanings
that
we're
about
to
go
through
will
be
available
to
you
and
the
calendar
entries
have
again
the
link
to
the
notes
and
they're.
A
You
know
YouTube
links
and
all
that
kind
of
good
stuff,
so
we're
going
to
start
with
Monday
and
it
would
be
crazy
for
any
project
to
schedule
things
on
Mondays,
but
we
have
to
do
a
bunch
of
stuff,
so
we
have
to
so.
There
are
lots
of
things
here,
we're
not
going
to
cover
each
one.
Kristof
Aniki,
to
have
a
sig
contributor
experience
deep
dive
today
at
425
the
rooms
just
changed.
A
So
there
are
a
few,
a
few
cigs
that
meet
on
on
Monday
I'm
gonna.
Just
talk
about
a
few
of
them
here
say:
gaps
might
be
a
place.
That
is
interesting
for
a
lot
of
you.
The
purpose
for
this
sake
is
to
discuss,
running
and
defining
applications
in
kubernetes
right.
So
this
is
places
where
you
find
people
from
helm
compose
and
the
workload
API.
This
is
a
very
large
sig
and
is
usually
a
place
that
lots
of
people
participate
and
then
the
second
one
I
want
to
talk
about
a
little
bit
of
sig
release.
A
A
They
have
little
play
books
on
what
your
job
is
and
you
can
just
read
the
whole
thing
and
it's
a
really
fun
and
positive
way
to
contribute
with
a
lot
of
experts
who
will
ensure
that
if
you
want
to
participate
that
you
will
succeed,
it's
a
really
fantastic
I've
done
it
three
times
and
they're,
not
Tuesday,
multiple.
Oh
sorry,
we're
still
on
Monday,
we
haven't
even
gotten
to
Tuesday
sit
cluster
life-cycle
is
a
very
large
sig.
A
You
will
find
them
on
every
slide
from
now
on,
so
they
have
20
sub
projects
and
they
have
something
going
on
every
single
day.
This
sake
concentrates
on
everything
from
the
insulation
to
kubernetes,
to
it's
time
for
an
upgrade.
What
do
I
do
so?
There's
a
lot
of
stuff
on
their
plate,
so
you're
going
to
see
a
lot
of
that
if
you're
interested
in
that.
B
So
Tuesday's
Tuesday's
are
actually
our
biggest
day.
We
have
17
meetings
on
Tuesdays
alone,
we're
a
global
community
right.
We
have
meetings
around
the
world
across
a
whole
bunch
of
different
time
zones
and,
as
you
can
see
from
the
slide,
the
kubernetes
meeting
schedule
is
absolutely
bonkers
on
certain
days
and
Tuesday
is
one
of
those
days.
So
we
give
each
zig
full
control
over
their
own
schedules
for
meetings
at
time
zones
that
they
choose,
which
is
how
we
end
up
with
meetings
scheduled
across
wildly
different
time
zones.
B
So
it
can
be
hard,
as
as
a
project,
to
find
people
to
host
meetings
in
certain
time
zones
and
grow
participation
in
various
regions.
So,
if
you're
interested
in
growing
participation
in
a
particular
part
of
the
project
in
a
particular
region,
that's
something
that
that
we
do
a
lot
of
now,
because
the
eight
regular
sig
meetings
on
the
last
slide
we're
not
enough
to
keep
us
busy.
We
also
have
five
sub
project
meetings
across
four
SIG's
on
Tuesdays.
Several
news
are
office
hours,
which
are
places
where
anyone
can
bring
questions
or
topics
for
discussion.
B
So
these
are
a
really
great
place
to
get
started
with
a
sig,
especially
if
you
come
in
with
some
questions
and
just
keep
it
going
because
it's
Tuesday
and
there
are
so
many
meetings.
We
also
have
four
working
group
meetings,
including
some
interesting
topics
like
long
term
support
and
multi-tenancy,
which
are
big
areas
for
for
kubernetes,
in
particular,.
A
A
So
if
you're
absolutely
confused
and
all
of
these
words
for
those
things
are
confusing
to
you,
consider
us
your
homeroom
like
in
school
right,
you
would
go,
I
have
no
place
to
be,
and
we
have
a
selection
of
people
here
raise
your
hands
who
our
entire
task
is
just
to
like
find
you
a
home
here
right,
so
don't
feel
free
to
stop
by
a
said,
contributor
experience
meeting
hop
on
a
few
times.
I've
had
people
come
and
then
say
and
then
hey.
You
know
I
kind
of
found.
A
My
thing
and
networking
I'm
not
gonna,
be
around
anymore
and
it's
like
well,
that's
that's
awesome
for
you,
but
feel
free
to
use
us
as
a
resource
to
getting
you
where
you
need
to
be
sick.
Claw
provider
I
want
to
point
out
those
of
you
that
might
have
been
casually
following
kubernetes
in
the
past.
There
used
to
be
six
for
each
of
the
cloud
providers,
saying
AWS
sake,
OpenStack,
sick,
Azure
and
so
on.
What's
happening
now
is
that
has
all
been
consolidated
as
sub
projects
underneath
sig
cloud
providers.
So
just
a
note
there.
A
So
if
you're
interested
in
cloud
provider
stuff
said
cloud
providers
the
place
to
be,
and
then
lastly
I
want
to
talk
about
work
group
kubernetes
are
kate's
infra.
So
this
is
especially
if
you
come
from
an
Operations
background.
This
is
an
excellent
place.
That's
always
looking
for
volunteers.
These
are
the
people
that
are
running
the
infrastructure.
To
do
the
things
that
we
need
to
publish,
kubernetes,
binaries,
make
releases
happens
and
all
that
kind
of
stuff
you
know
someone
has
to
run
DNS
for
kuberan
and
ease
down
IO
right.
A
So
if
you
have
that
kind
of
expertise,
if
you're
a
necessary
or
something
that
is
a
fantastic
place
to
get
started,
and
then
these
are
the
other
things
that
meet
on
Wednesday.
The
one
I
want
to
point
out
here
is
cig.
Api
machinery
remember
kubernetes
is
all
about
api's.
So
if
you're
building
and
extending
kubernetes
keeping
an
eye
on
this
SIG
will
end
up
saving
you
lots
of
time,
api's
change,
they
get
deprecated,
and
this
is
a
place.
A
We
do
have
two
special
programs
that
meet
on
Wednesdays,
also
on
the
first
Wednesday
of
every
month.
We
have
our
meet
our
contributors
program.
This
is
where
we
go
and
do
a
live
stream
on
YouTube.
You
join
slack
and
you
can
ask
your
banana
teas
maintainer
x'
questions
about
contributing
to
kubernetes.
So
maybe
you
need
help
doing
your
first
pull
request.
Maybe
you
need
help
doing
a
Code
walkthrough.
Maybe
you
have
an
architecture
question
these.
You
can
submit
these
questions
either
as
yourself
or
anonymously.
A
It's
just
a
safe
place
where
you
say
you
know
what
there's
a
bunch
of
experienced
contributors
here
and
I
have
questions
about
how
to
actually
get
involved,
and
then
this
is
just
a
place
where
you
can
ask
a
lot
of
questions
and
it
is
really
fun
program
to
be
involved
in
the
second.
One
is
kubernetes
office
hours.
A
This
is
a
sister
program
that
we
asked
kubernetes
experts
to
just
sit
on
a
panel
and
again
we
just
live
stream
on
YouTube
for
an
hour,
and
we
try
to
answer
as
many
user
questions
for
people
that
are
using
and
consuming
kubernetes.
So
we
make
this
a
fun
program.
We
give
away
t-shirts,
we
livestream
the
YouTube
channel
on
the
side.
We
have
people
from
the
community
that
joined
sharing
their
resources,
links
blog
posts
and
it's
a
really
fun
place
to
be.
A
This
is
on
the
third
Wednesday
of
every
month
and
it
is
a
it's
a
good
investment
if
you
know
kubernetes,
but
you
don't
have
a
lot
of
time.
We
can
just
put
you
on
the
rotation
of
panelists
and
you
can
get
involved.
That's
where
Chris
McCarty
started
and
office
hours.
One
hour
a
month-
and
this
Cube
cottony
is
doing-
is
very
first
cube
con
talk,
so
you
can
start
small
and
then,
as
you
feel,
confident
feel
free
to
move
on
on
your
journey.
B
Okay,
so
now
we're
up
to
Thor's
day
where
we
also
have
a
whole
bunch
of
meetings,
so
like
API
machinery,
which
George
talked
about
think
architecture
meets
on
Thursdays,
and
it's
also
a
really
interesting
and
important
sake
to
know
about.
If
you
do
anything
related
to
architecture,
they
maintain
and
evolve
the
design
of
kubernetes
to
maintain
architectural
consistency
across
the
project.
B
So
this
includes
API
governance
to
help
establish
conventions
and
consistency
across
both
the
system
and
the
user
facing
api's
and
like
George
mentioned
kubernetes,
has
a
huge
focus
on
api's
they're,
also
responsible
for
conformance
definitions
and
code
organization.
So,
if
you're
building
kubernetes
distributions,
this
is
incredibly
important
and
if
you're
involved
in
kubernetes
at
all,
it
really
is
kind
of
a
good
idea
to
at
least
sort
of
keep
an
eye
on
what
they're
doing
within
cig
architecture,
and
you
can
find
their
regular
cig
meeting
here
on
Thursdays.
B
We
also
I
mentioned
earlier
the
global
nature
of
the
community.
We
have
our
contributor
experience
a
pack
time
zone
meetings
on
Thursdays,
so
it's
a
it's
a
glut,
we're
a
global
community
with
a
meeting
for
almost
everyone,
regardless
of
where
you
are
in
the
world,
and
what
you're
interested
in
sick
docks
really
does
demonstrate.
The
global
nature
of
the
community,
with
teams
focused
on
German
Spanish,
French,
Hindi,
Indonesian,
Italian,
Japanese,
Korean,
Portuguese,
Chinese,
and
probably
some
others
that
I'm
forgetting
about
but
sick
docks
is
really
a
great
place
to
start
contributing
anyone.
B
Absolutely
anyone
can
contribute
to
documentation
and
not
just
for
localization
right
I
just
talked
about
localization,
but
having
people
who
are
new
to
the
project
review
the
docs
and
make
suggestions
or
contributions
can
be
really
really
valuable
for
the
project.
So
don't
underestimate
the
importance
of
having
new
people
with
fresh
eyes
and
different
assumptions,
who
can
maybe
find
errors
notice
some
gaps
or
help
improve
some
places
where
something
maybe
isn't
as
clear
as
it
could
be
so
sick
docks
is
really
a
great
place
to
get
started
as
a
contributor
and
that's
a
super
friendly
sink.
B
But
community
meetings
are
one
of
the
best
ways
to
stay
up-to-date
on
a
huge
variety
of
things
happening
across
the
entire
kubernetes
community.
We
meet
on
Thursdays
10
a.m.
Pacific.
We
have
shout
outs,
announcements
updates
from
6:00
and
working
groups
and
we're
in
the
process
of
changing
these
from
weekly,
something
a
little
less
frequent,
so
stay
tuned.
B
While
we
sort
of
figure
out
the
details,
but
the
next
one
is
on
December
5th,
which
is
the
week
after
the
US
Thanksgiving
holiday
coming
up,
and
the
best
part
is
that
anyone
can
sign
up
to
host
the
meeting
which
George
says
is
just
like
hosting
Saturday,
Night,
Live
and
I.
Think
he's
exaggerating
a
little
bit,
but
it's
still
loads
of
fun
to
host
the
community
meeting.
I've
done
it
a
few
times
and
it's
yeah.
It's
just
a
lot
of
fun.
B
So
Friday's
we
can
relax
a
little
bit
fewer
meetings
super
light
meeting
days
you
just
relax,
get
maybe
a
head
start
into
the
weekend,
which
is
why
this
is
a
picture
of
kubernetes
relaxing
on
the
beach
with
a
pretty
cocktail.
That's
not
me
unless,
like
me,
all
of
my
work
meetings
get
scheduled
on
Friday,
so
instead
of
having
kubernetes
meetings
at
Friday,
I
just
seemed
done
dose
a
bunch
of
work
meetings
which
cuts
into
my
relaxing
on
the
beach
with
fruity
drinks
time.
But
it
is
nice
to
have
one
late
meeting
day
for
the
project.
A
There
are
some
other
activities
that
are
happening
outside
of
kubernetes
as
well
that
we
just
want
you
to
be
cognizant
of
I'll
get
to
that
in
a
second.
But
first
let
me
hit
elections.
So
once
a
year
in
the
fall,
we
do
have
elections.
This
is
for
the
kubernetes
steering
committee,
it's
a
seven
member
body
who
oversees
the
governance
of
the
kubernetes
project,
and
these
are
fully
elected
members
by
the
contributors
of
kubernetes
and
just
like
a
cig.
They
published
notes.
A
They
have
public
meetings,
they
have
a
youtube
archive
of
all
the
stuff
that
you
can
check
out
and
there's
a
lot
of
great
information
in
there
of
the
current
kubernetes
organizational
members.
Eight
hundred
and
fifty
nine
people
were
eligible
to
vote.
So
that's
really
the
core
group
of
kubernetes
contributors.
There.
B
And
we,
of
course,
have
cube
con
date
of
concert
you're
here.
You
know
that.
But
did
you
also
know
that
we
do
them
in
China
and
the
EU?
So
the
next
events
in
Amsterdam
at
the
end
of
March,
and
we
also
do
contributor
summits
the
day
before
every
cube
con.
So
if
you
missed
the
one
on
Monday
for
this
cube
con,
you
can
try
again
in
Amsterdam.
B
We
also
have
kubernetes
forums,
so
the
next
two
are
in
Seoul
and
Sydney,
and
those
are
coming
up
in
December
and
the
forum's
are
joint
events
that
run
consecutively
for
two
days,
each
in
two
cities
in
kind
of
the
same
region
during
the
same
week
with
the
idea
that
they
can
sort
of
get
speakers
that
kind
of
a
two-for-one
discount.
So
they
get
some
just
be
getting
to
events
in
the
same
region
and
it
cuts
down
on
travel
costs
and
they
can
get
some
better
speakers
that
way.
A
So
so
far,
we've
only
been
overwhelming
you
with
kubernetes,
but
there's
an
entire
CN
CF
landscape
of
other
projects
that
we
just
want
you
to
be
aware
of.
Specifically
when
I
say
SIG's
storage
I
could
be
talking
about
kubernetes,
six
storage
or
I
could
be
talking
about
60
that
lives
at
the
CN
CF
level.
So
just
be
cognizant
that
as
part
of
the
CN
CF
as
those
projects
evolve
and
get
larger,
and
things
like
that
that
you
might
start
seeing
some
of
the
similar
terminal
odd
terminology
in
those
areas
as
well.
A
So
in
conclusion,
there's
a
lot
going
on.
It
can
be
overwhelming,
so
don't
try
to
consume
it
all
at
once.
Just
pick
an
area
and
dive
in
we've
thrown
a
lot
at
you
this
morning.
So
come
to
Christophe
and
Nikita's
talk
at
4:25.
Today
it
says
same
contributor
experienced
deep
dive,
we're
planning
on
having
as
many
members
of
the
sig
there
as
possible
to
help
you
out.
There
are
Sigma
ting
's
happening
all
week
throughout
cube
con
and
cloud
native
con.
A
You
see
them
on
the
schedule,
so
that's
just
a
place
that
you
can
attend
those
meetings.
If
you're
interested
in
those
things,
the
people
who
are
members
and
contributors,
those
things
are
wearing
buttons
that
look
like
this.
That
says,
what's
sig,
they
are
working
on.
So
that's
a
good
way
to
kind
of
see
what
someone's
interested
in
and
knowing
that
you
can
approach
them
and
let
them
know
hey
I'm
interested
in
whatever
you're
interested
in
to
start
a
conversation.
And
lastly,
please
come
find
us
we're
busy.
A
We
have
lots
of
people
who
are
in
different
steps
of
the
journey.
Some
people
have
been
here
since
the
inception
of
the
project.
Some
people
literally
started
when
they
got
to
keep
Khan
on
their
journey.
So,
as
we
mentioned
earlier,
the
software
is
gonna
continue
to
change
all
the
time,
but
the
people
are
the
things
that
you
take
with
you.
So
we
look
forward
to
making
you
part
of
this
wonderful
family.
Thank
you.
A
Over
the
course
of
the
last
two
years,
we've
we've
ensured
so
SIG's,
initially
everything
kind
of
grew
organically
and
over
the
past
two
years
the
steering
committee
has
been
working
with
SIG's.
To
do
a
few
things.
A
each
sig
has
a
charter
now.
So
when
you
go
into
sake
and
you
click
on
those
links,
I
showed
you
you'll
see
a
charter
of
what
a
sig
is
responsible
for
and
what
they
are
not
responsible
for
and
what
steering
has
been
working
on.
A
The
past
two
years
is
ensuring
that
every
piece
of
code
or
whatever,
has
an
owner.
So
if
you
actually
browse
in
the
in
the
code
tree
itself,
you'll
see
a
little
file
called
owners
and
it
will
say
who
owns
that
section
of
code
and
as
you
go
up
the
tree,
it
gets
bigger
and
it's
groups
eventually
start
to
show
up
instead
of
individuals
and
things
like
that.
So
yes,
however,
it's
not
just
github.com
slash,
kubernetes,
slash,
kubernetes,
there's
also
other
parts
of
the
code
base
inside
the
github
organization
that
have
coverage
as
well.
B
A
Yes,
so
it
depends
on
your
expertise
like
I'm
I
like
to
tell
people
you
know,
if
it's
your
first
day,
don't
like
go
to
API
machinery
inspect,
to
figure
it
out
right,
there's
not
like
a
lot
of
there's
complicated
stuff
in
there.
So
you
do
what
I
tell
people
is
you
know?
What
are
you
into?
Are
you
into
networking?
Are
you
into
you
know,
I,
can't
think
of
anything
right
now.
Do.
A
B
B
I
think
all
of
the
things
are
looking
for
help
in
some
way
or
another,
and
a
good
place
to
start
out
as
if
you're
interested
in
a
particular
area
have
a
look
at
the
good
first
issues
and
github
a
good
place
to
start,
but
it
is,
it
does
depend
a
lot
more
on
your
on
your
expertise.
So
not
you
like
API
machinery,
is
not
gonna,
be
everybody's
Jam
same
thing
with
like
stick
node,
there's
some
some
things
where
you
need
kind
of
particular
types
of
X.
Yes,
there.
A
Be
dragons
in
there
and
if
you
do
to
come
to
the
contributor
experience
deep
dive,
we
actually
do
have
a
contributor
guide
that
tells
you,
okay,
here's
how
you
find
a
cig,
here's
how
you
find
their
beginner
bugs,
which
is
you
know,
good
first
issue,
bugs
we
ask
SIG's
to
maintain
a
list
of
Help
Wanted
issues,
things
of
that
nature.
So
answer
your
question!
Awesome
cool!
You
had
a
gentleman
in
the
back.
A
E
B
F
B
F
Thank
you
so
much
for
the
presentation.
Kubernetes
is
obviously
a
really
important
milestone
in
the
history
of
open-source
and
I
was
wondering
if
you
could
talk
a
little
bit
about
how
the
structure
of
the
project
has
is
different
than
other
projects
in
the
history
of
open-source
and
maybe
how
it's
changed
over
time
in
its
own
development
as
well.
I.
G
B
I
would
say
one
of
the
one
of
the
differences
with
with
kubernetes
from
a
lot
of
other
projects
is
that
it
is.
The
scale
is
different
right.
It's
a
massive
project,
so
I'm
not
on
that
hand.
It's
kind
of
more
similar
to
things
like
the
Linux
kernel,
for
example.
So,
and
we
actually
have
things
kind
of
organized
in
similar
ways
right
like
the
kernel
has
maintained,
errs
files,
kubernetes
has
has
owner's
files
and
this
house
sort
of
evolved
organically
over
the
over
the
history
of
the
project.
Yeah.
A
And
I
like
to
add
the
thing
that
drew
me
to
kubernetes
initially,
is
it
built
on
the
shoulders
of
giants
and
we're
able
to
look
at
how
other
projects
had
and
then
made
specific
decisions
about
being
explicit
about
things
so
in
the
in
the
community
repo
there's
a
file
called
values,
MD
that
says
the
kubernetes
community
values
right,
so
we
say
explicitly.
You
know.
Community
comes
first
before
companies,
you
know,
and
we
make
that
explicit.
A
If
I
was
here
trying
to
sell
you
VMware
all
day
right,
nobody,
nobody
wants
to
see
that
write
an
explicit
code
of
conduct
immediately
as
soon
as
you
want.
You
know
that,
isn't
that
you
know
now
we
think
about
that
back
when
I
started
an
open-source
being
friendly
to
Pete,
it
was
like
a
test.
You
had
to
run
the
gauntlet
or
getting
yelled
at
and
then
someday
I'll
get
to
yell
at
someone
and
then
someone.
A
B
We
also
have
really
good
documentation
around
what
we
call
the
contributor
ladder,
which
is
kind
of
how
you
move
up
into
additional
areas
of
responsibility
within
the
project.
So
I
feel
like
that
is
I,
think
documented
more
clearly
than
what
I've
seen
in
lots
of
other
projects.
So
it's
kind
of
clear
what
you
need
to
do
to
become
an
organ
member,
which
is
the
first
step
and
reviewer
and
moving
on
into
areas
of
more
and
more
responsibility.
So
it
is
a
bit
more
I,
think
a
gala
Terry
and
then
some
others.
G
G
B
Example
of
what
works
really
really
well
is
that
we,
we
have
put
a
lot
of
discipline
around
making
sure
that
SIG's
are
videotaping
their
meetings
and
getting
them
put
on
YouTube.
So
if
you
miss
a
meeting
or
if
you're
in
a
time
zone
where
the
meeting
is
just
not
not
convenient,
for
you
being
able
to
go
back
and
look
at
previous
videos
or
if
you
want
to
join
a
cig
and
you're
kind
of
curious,
what
what
happens?
You
can
go
back
and
review
review
the
videos,
but
not
just
the
videos.
B
A
And
I'll
be
happy
to
share
failure.
In
the
two-and-a-half
years
that
I've
been
working
in
kubernetes,
there
has
always
been
over
a
thousand
open
pool
requests
and
nothing
really
ruins
your
day.
Then
a
contributor
who's
frustrated
that
shows
up,
says:
hey
I
pushed
this
a
year
ago
and
I've
tried
everything
and
then
it
just
saps.
A
You
know
the
energy
out
of
us,
so
it's
something
that
we
you
know
at
this
scale,
it's
very
difficult
right
and
trying
to
ensure
that
we're
assigning
PRS
to
people
who
are
active
so
we're
constantly
trying
to
clean
up
owners
files
trying
to
ensure
that
people
aren't
getting
overloaded.
How
do
we
even
it
out?
How
do
we
make
the
queue
easier?
How
do
we
make
those
overloaded
developers
be
able
to
mentor
new
people,
so
they
can
help
out.
So
that's
an
area
where
we're
constantly
improving.
A
B
D
B
H
Can
you
put
yourself
in
the
shoes
of
someone
who
has
never
contributed
is
not
involved
in
any
SIG's
yet
goes
on
to
github.com
kubernetes
kubernetes
finds
an
issue:
that's
labeled
good
first
issue,
SiC
Doc's,
Help
Wanted
and
goes
oh.
That
sounds
like
something
I
could
do
and
what
would
be
you
know
what
what
you
would
do.
H
B
I
mean
so
we
have,
we
have
pretty
good
contributor
documentation,
so
I
can
say
this,
because
I
I
got
involved
in
the
Qbert
Nettie's
community,
I
think
probably
probably
about
a
year
ago.
So
so
this
is
all
kind
of
relatively
recent
for
me
from
a
kubernetes
standpoint,
but
the
the
docs
are
pretty
good
for
the
can
for
contributing
so
kind
of
running
running
through
the
contributor
md
files
and
and
really
sort
of
just
kind
of
following
along
the
process,
because
there's
some
hoops,
you
need
to
jump
through
CLA
signing
and
things
like
that.
B
A
So
you
know
I
I
introduced
myself
and
I
said:
hey
I'm
gonna
work
this
and
they
kind
of
said.
Okay,
this
little
area.
You
know
you're
good
work
on
that
and
then,
as
I
started
to
do
my
pull
requests
and
get
easier
on
it.
They
knew
I
was
just
getting
started,
so
they
were
supported
and
over
time,
I
was
able
to
ramp
up
my
contributions
and
then
at
some
point
they
put
you
in
charge
of
stuff.
I
So
I
think
it's
interesting
perhaps
to
contribute
to
kubernetes
and
be
an
open-source
guy.
You
know
a
lot
of
cool
people
are
doing
it.
I'd
like
to
be
cool
too,
but
writing
code.
You
know
contributing
to
kubernetes
is
not
my
day.
Job
I
understand
for
some
people
it
is
I've
got
friends
and
family
I
like
to
see
sometimes
and
I,
wouldn't
want
to
just
jump
in
all
enthusiastic
and
then
kind
of
bail.
What
do
you
guys?
B
It
depends,
it
depends
a
lot
on
the
amount
of
time
that
you
have
to
to
commit
to
it,
but
there
you
know
there
are
loads
of
ways
you
can
get
involved.
That
are
kind
of
you
know,
lower
lower
time
commitments.
So
one
of
the
things
that
I
do
like
if
I
have
an
extra
five
or
ten
minutes
and
I'm
waiting
for
a
meeting
to
start
all
like
pop
into
the
issues
in
kubernetes
community
or
pull
requests
and
do
a
couple
of
quick
reviews.
B
So
that's
something
that
you
can
do
kind
of
any
time
and
doesn't
involve
a
lot
of
big
heavy
time
commitments,
but
I
would
say,
be
kind
of
be
kind
of
careful
about
what
you
do
commit
to
you,
based
on
the
time
that
you
have.
So
if
you
don't
have
a
lot
of
time
like
signing
up
to
lead
some
part
of
the
release,
it's
probably
not
a
good
idea,
because
you're
gonna,
let
people
down
you're,
probably
not
gonna-
want
to
be
on
the
contributor
summit.
B
Organizing
team,
if
you
don't
have
a
lot
of
time
to
commit
to
that
so
I
would
just
say
you
know,
be
be
realistic
about
the
amount
of
time
that
you
have
to
contribute
and
then
pick
some
contributions
that
you
think
you
can
reasonably
make
given
the
time
that
you
have
involved.
But
you
don't
need
to
have
like
loads
of
time
in
order
to
make
really
valuable
contributions.
I
mean
I.
B
I
spend
a
lot
of
time
doing
other
things
at
pivotal,
related
to
kind
of
our
like
strategy
and
stuff,
and
so
I
don't
spend
a
ton
of
time
in
the
community,
but
I
feel
like
I
I,
feel
like
I've
sort
of
gotten
a
good
balance
for,
for
the
amount
of
time
that
I
have
to
spend
and
getting
benefit
in
the
community.
Yeah.
A
And
I
have
two
things
to
say
to
that.
First,
as
Kelsey
said
I
like
to
be
the
wingman,
you
know
I
like
to
be
like
help.
Other
people
succeed
and
things
like
that.
Don't
look
at
people
who
get
paid
to
work
on
kubernetes
every
day
is
like
the
end
goal
right
going.
Your
own
pace
right.
You
know
whatever
month,
whatever
it
is,
you
got
to
do.
A
We're
gonna
appreciate
every
contribution
that
you
make
number
two
a
lot
of
people
that
do
work
on
it,
we're
kind
of
trained
and
figure
out
how
to
ensure
that
you
don't
set
yourself
up
for
a
trap
right
so,
like
the
release,
team
isn't
gonna,
give
you
a
hugely
responsible
thing
unless
you've
shadowed
before,
and
you
know
what
you're
doing
so
slowly
over
time,
we've
kind
of
ensured
that
we
don't
let
you
paint
yourself
into
a
corner.
You
know
yeah
cool.