►
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
State of Kubernetes Contributor Community - Paris Pittman, Google
The Kubernetes contributor community spans the globe reaching over 26,000 people since the start of the project. If we grow on the same trajectory as years past, expect to cross 30,000 by Barcelona. (eek - a prediction!) What does the contributor landscape look like after 5 years in the land of open source? In this talk, I'll highlight: -who are our contributors now?, -new programs that have been created to help scale the community, -stories as told through data on our communication platforms, -and give recognition throughout
https://sched.co/MPZb
A
A
This
talk
was
actually
inspired
by
a
recent
talk
that
I
heard
of
Tim
Hawkins
I
run
the
Bay
Area
kubernetes
Meetup,
and
we
did
this
little
mini
conference
and
he
decided
to
do
a
keynote
and
talk
a
little
bit
about
the
non-technical
aspects
of
kubernetes.
This
is
not
a
technical
vision
talk.
This
is
not
a
state
of
the
project,
like
you've
already
heard
on
the
main
stage
at
cube
con.
If
that's
what
you're
expecting
I
no
harm,
no
foul,
you
can
totally
leave
now
or
zone
out
in
your
computer.
A
B
A
So,
who
makes
up
this
community
31,000
contributors
I'm
her
I'm
sure
you've
heard
this
number
before
Nikita
and
Lucas
I
believe
during
their
keynote
had
this
as
well.
You
probably
hear
this
often,
as
this
really
represents
one
of
the
largest
open-source
contributor
bases
out
there
and
also
depending
on
your
definition
of
contributor.
So
how
do
we
define
ours?
Pr
creators
issue
filers,
committers
reviewers,
so
how
many
of
you
by
a
raise
of
hands,
have
done
one
of
those
four
kubernetes.
A
So
I'm
one
of
those
contributors,
my
name,
is
Paris
Pittman
I
work
at
Google
cloud
I'm
on
the
open-source
strategy
team
I've
been
working
on
upstream
kubernetes
for
about
22
months
now
and
having
the
time
of
my
life,
I
co-chair
the
special
interest
group
for
contributor
experience.
We
have
a
bunch
of
hooligans
just
kidding.
They
are
the
best
sig
that
we
have
and
I'm
biased.
A
So
at
the
time
of
filling
out,
this
CFP
I
didn't
want
to
give
myself
a
pat
on
the
back
I,
don't
know
if
anybody
still
and
the
CFPB
I
didn't
see.
I
said
so.
We
have
26,000
contributors
at
the
time
of
writing
this
and
then
I
predicted
that
we
would
have
at
least
30
by
the
time
I
delivered.
The
talk
so
Miss
Cleo
psychic
over
here
was
on
target.
A
So
I
just
had
to
point
that
out
so
now,
let's
break
this
huge
31,000
number
down
a
bit
to
sort
of
show
the
funnel,
because
that's
not
necessarily
the
whole
story.
3,000
of
them
are
committers.
What's
the
difference
between
a
committer
and
a
contributor,
a
committer
is
someone
who
made
or
authored
a
committer
PR
and
pushed
it
up.
These
folks
are
generally
called
approvers
and
our
owners
files
things
get
a
little
hairy
here,
but
it's
important
to
break
these
personas
down
as
many
assume
that
everything's
covered
meaning
we
have.
We
don't
need
any
new
contributors.
A
A
So
it's
just
a
really
really
vast
landscape.
So
now
that
sort
of
puts
some
perspective
on
that
31,000
number,
these
contributors
are
spread
across
many
regions,
I
attempted
to
do
a
pie
chart
and
it
looked
like
a
lot
of
slices
of
different
colors
with
the
United
States
being
the
largest
chunk.
But
this
is
our
top
ten
right
now
showing
on
the
screen.
A
So
what
groups
do
these
contributors
belong
to
this?
This
diagram
by
Brian
Graham
shows
the
relationships
between
SIG's
working
groups,
committees
and
things
like
that
that
have
all
sprung
to
life
over
the
last
two
years
as
well
as
those
have
been
here
since
the
start.
After
five
years,
we
have
several
new
committees
to
help
steer
the
project
forward,
most
notably
the
steering
committee
that
graduated
from
a
that
originally
started.
A
As
a
bootstrap
committee,
graduated
had
an
election
and
then
has
also
had
another
election
this
year,
we're
gonna
do
the
same
song
and
dance,
and
every
year
go
forward.
We're
gonna
keep
going
with
elections,
this
year's
elections.
This
year's
election
is
actually
super
special
because
we
have
twelve
members
right
now
and
the
committee
is
going
to
be
reduced
to
seven.
This
is
definitely
a
space
to
watch
if
you're
interested
in
either
a
running
for
steering
committee,
because
we
would
definitely
love
to
have
you.
A
We've
also
seen
working
groups,
bring
the
life
and
retire
through
these
fight
last
five
years
and
I
think
people
might
get
maybe
nervous
when
they
see
you
know
a
working
group
getting
decommissioned
or
retired.
You
know
whatever
word
you
choose
and
that's
really
not
the
case
working
group.
The
whole
entire
purpose
of
a
working
group
is
to
be
temporary.
It's
to
work
across
SIG's
going.
You
know
just
looking
here,
working
across
FIGS
and
once
the
job
is
done,
it's
done
and
then
the
sig
will
absorb
that
work.
A
The
the
percentage
of
the
change
is
getting
wider
and
wider,
meaning
the
new
guard
of
folks
are
coming
in
and
replacing
some
of
our
older
folks
that
have
been
in
some
of
these
chair
roles
for
a
long
time.
So
just
an
example
of
these
changes
this
year
alone,
so
we're
in
May.
So
we're
almost
halfway
through
the
year.
Just
just
play
with
me
here
and
we've
already
had
14
changes
that
brings
things
like
chair
training,
tech,
lead,
training,
making
sure
that
they're
up
to
speed
and
that's
a
lot
of
work.
So
it's
14.
A
And
then
also
another
really
really
cool
thing
that
has
just
sprung
a
life
as
well
is
the
addition
of
user
groups.
User
groups
is
a
space
where
users
can
come
and
work
with
folks
and
cigs
and
give
feedback
and
have
a
much
a
much
more
tailored
feedback
loop
to
their
process.
It's
not
necessarily
intended
to
be
temporary,
so
it's
not
necessary
working
group,
but
it's
something
that
will
help
help.
You
know,
like
I,
said
close
feedback
loops.
A
A
You
say
how
is
this
happening?
You
all
are
crushing
work.
We
do
four
releases
a
year
and
we're
just
chugging
out
we're
just
chugging
out
code
well
mainly
through
sub
projects
as
we
grow
through
the
years
for
finessing.
Our
art
organization
and
some
projects
are
owned
by
SIG's
and
what
sub
projects
are
is
identifying
areas
of
the
project
that
you
own,
so
certain
parts
of
the
codebase,
certain
parts
of
the
dock
base
etc.
A
So
like,
for
instance,
if
you
work
in
you
know,
the
engineering
department
at
your
employer
sure
there's
45
different
mini
engineering
things
within
that
department,
it's
very
similar
to
that.
So
each
one
of
those
departments
has
different
owners
and
they
work
together.
So
this
actually
makes
them
move
faster
and
work
quicker.
A
Last
time,
I
checked
in
cluster
I
think
cluster
lifecycle.
They
have
the
highest
with
over
15
right
now,
I
think
like
a
PMI
machinery
might
be
next
or
something
yes,
so
the
cool
part
now
is
these
sub
projects
get
to
meet
independently
and
then
they
just
kind
of
report
up
into
their
SIG's
again
cuz
when
we're
chugging
out
so
much
work.
You
know,
I
know
from
experience
for
a
contributor
experience
from
from
the
country.
A
Yes,
I
also
anticipate
much
more
sub
projects
in
the
future
and,
as
we
go
through
different
code
organization
activities
and
things
like
that,
so
how
these
groups
operate
and
make
decisions
has
become
much
smoother
through
implementation
of
charters
across
the
board.
This
is
something
that
the
steering
committee
worked
super
diligently
with.
They
actually
paired
some
of
the
committee
members
to
cig
chairs
to
just
kind
of
walk
them
along
through
this
process.
A
Again,
some
of
our
chairs
are
not
trained
at
being
chairs,
so
when
you
say,
fill
out
a
charter,
it's
super
important
to
give
them
templates,
and
things
like
that.
So
the
steering
committee
definitely
did
a
really
great
job
in
making
sure
that
everybody
has
a
charter,
and
this
is
great
for
both
new
and
current
contributors
who
are
confused
as
and
say
what
the
heck
does
this
they
do
like.
A
A
Also
during
the
114
release,
I
think
that
was
called
quatre
Nettie's
yeah
quatre
Nettie's,
the
team
implemented
all
caps
for
the
first
release
cycle
caps
for
those
I
will
explain.
Caps
caps
for
those
who
don't
know
is
kubernetes
enhancement,
proposals
very
similar
to
Python
enhancement
proposals.
They
were
that
pretty
much
modeled
off
of
that
caps
help
us
with
defining
features,
editions,
major
major
removals
of
things
and
just
really
major
changes
that
could
potentially
be
breaking
or
a
cross,
sig,
etc.
A
So
that
people
have
a
wider
view
of
them,
and
this
has
really
really
really
improved
the
project.
I
think
by
a
lot.
We
have
a
lot
to
do
in
this
area
because
not
all
SIG's
are
on
the
cap,
train
and
some
are,
and
then
we
also
have
a
lot
of
process
and
improvement
to
do
around
the
tooling
of
them,
as
well
as
like
deadline,
refinement
and
stuff
like
that.
A
There's
been
quite
a
few
conversations
as
of
late
around,
like
deadlines
for
tabs
as
it
relates
to
code
freeze
and
all
the
other
awesome
release,
deadlines,
but
go
forward.
Caps
will
be
the
future
and
so
like.
If
you
ever
want
to
know
the
stuff
that's
going
into
kubernetes
and
get
a
kind
of
a
grip
on
it
or
a
handle.
That's
where
you
would
look.
A
We
like
to
talk-
that's
definitely
I,
think
no
stranger
to
anyone
in
this
room,
especially
here
at
cube
con,
where
my
voice
is
almost
going
out
right
now,
but
we
have
several
just
contributor
focus
channels,
because
when
you
look
at
community,
when
you
look
at
kubernetes
as
a
whole
from
the
word
community
right
community
means
to
us
end-user
and
contributor.
So
we
have
millions
of
channels
for
all
of
those
things,
anything
that
you
can
hit.
A
We
we
have,
but
we
do
have
quite
a
few
contributor
focus
channels,
specifically
the
kubernetes
dev
mailing
list
and
then
also
the
kubernetes
blog.
A
lot
of
our
contributors
do
read
that,
but
actually
going
back
to
the
point
about
the
end
users,
the
cool
part,
the
cool
thing
about
our
contributor
base,
specifically
in
this
open
source
project,
is
that
I
might
say:
I'm
gonna,
throw
out
a
number
of
99%
of
them
or
most
likely
end
users.
So
they
have
that
relationship
already.
A
So,
even
if
they
are
reading
and
user
channels,
they
might
still
be
able
to
pick
up
on
some
of
that
contributor.
Contributor
information,
but
slack
slack,
is
definitely
our
sort
of
lifeline
artery
of
the
contributor
project
as
far
as
getting
work
done.
So
when
people
always
Lee
I,
know,
I
said
some
projects
before
when
people
are
all
well
how'd,
you
get
work
done
and
through
sub
projects.
Sure
that's
accurate,
but
honestly
I
really
think
we
get
work
done
because
of
the
real-time
communication
that
we
have
compared
to
other
open-source
projects.
A
This
is
both
a
benefit
and
a
detriment
because
running
open
source
communities
with
proprietary
tools
is
not
wonderful
and
it's
important
to
make
sure
that
you
get
those
things
right,
those
things
being
moderation
and
communication
policies
and
things
along
those
lines.
But
we
did.
We
did
a
poll.
We
did
a
contributor
experience
survey
last
year.
82
percent
of
the
respondents
said
that
slack
was
useful.
Don't
get
me
wrong.
I
bet
you
the
other
remaining
where
you
know
IRC.
C
B
A
The
topic
of
emojis
and
slack
because,
of
course
that's
why
we
use
slack
as
the
emojis
I
did
an
emoji
talk
at
the
last
coupon
and
I
actually
wanted
to
use
a
slide
here.
Cuz,
it's
really
cool.
This
was
an
analysis
so
that
this
is
fine
dog
emoji,
as
it
relates
to
all
the
channels
and
it
actually
peaks
during
release
periods.
C
A
A
Scalings
hard
something
I
feel
like
I've
had
to
learn
painfully
throughout
the
years
is
removing
myself
or
a
manual
process.
Retro
actively
can
be
super
difficult
and
I.
Think
we
see
that
a
lot
in
kubernetes
today,
where
we
have
set
up
these
community
processes
and
things
like
that
and
then
we're
trying
to
back
them
out
and
go.
Oh
no.
We
need
to
automate
this
and
then
without
breaking
everything,
so
that
is
definitely
hard,
but
we
have
some
other
scaling
challenges
that
I
kind
of
wanted
to
bring
up
today.
A
A
That's
the
expectation
people
are
coming
to
this
table
and
they
at
least
respect
that,
and
they
at
least
expect
respect
they
they
want
to
be
communicated
with
if
something's
not
going
right.
They
want
to
know
if
you
are
busy
and
not
going
to
be
able
to
merge
PRS.
They
want
to
know
if
you're
going
to
be
out
for
two
weeks
and
can't
do
something
they
want
to
know
so.
A
Contributors
who
submit
features
are
expected
to
stick
around
for
over
a
year
because
of
the
GA
process.
That's
not
necessarily
an
expectation
that
I
think
a
lot
of
contributors
go
in
with
when
they're
submitting
a
feature,
usually
when
they
submit
a
feature.
It's
just
super
excited,
I
I'm,
either
fixing
something
or
making
something
better,
and
you
know
short
term.
You
know
short
term
hazy.
A
A
So
it's
really
important
that
we
ask
we
listen.
We
be
explicit
with
both
new
and
current
contributors
as
much
as
possible.
I
tell
all
of
my
chair,
I,
tell
all
of
our
chairs
I
tell
our
tech
leads.
If
you
feel
like
you
communicated
something,
you
should
probably
do
it
three
more
times.
There's
that
many
people
in
the
project
now
that
you
absolutely
have
to
overly
communicate.
A
Many
of
them
want
to
want
to
come
want
to
climb
the
ladder,
so
that's
an
expectation
that
I
just
mentioned,
for
this
is
again
another
thing
from
from
our
contributor
experience
survey.
81%
of
them
said
yes,
they're
going
to
climb
the
ladder.
What's
the
ladder,
reviewer
approver
owner
things
like
that,
so
and
then
over
here
you
can
also
see
42
percent
said
they
want
mentorship.
A
A
Recently,
read
rusts
blog
on
scaling
empathy
did
anybody
else,
read
that
so
good
really
really
good?
Yes,
you
should
definitely
check
it
out.
It's
so
resonated
with
me,
because
it
was
talking
about
how
you
know
the
hardest
part
about
working
in
open-source
is
working
in
the
open
and
how
building
features
and
things
like
that
can
be
challenging
when
you're
putting
your
heart
and
soul
into
it,
and
then
someone
comes
and
just
cuts
it
up.
So
building
empathy
is
super
hard
and
figuring
out
how
to
scale
that
is
even
harder.
A
A
A
Besides,
it's
really
important
to
know
your
limits
burnout
to
think
mental
health
again
going
back
to
this
might
be
a
second
job
for
you.
Communicating
expectations
again
helps
with
us.
If
you
find
contributors
are
looking
for
quick
turnarounds
that
aren't
feasible.
So
what
should
we
focus
on
scalable
mentoring,
I
preached
about
this
I
think
I'm.
Looking
at
around
the
room
and
I.
Think
half
of
you
have
heard
at
least
one
hour
tirade
of
mine
on
this
building
roles
and
teams.
Is
everybody
here
familiar
with
the
kubernetes
release
team?
A
They
have
a
lead
and
then
they
have
shadows.
Why
can't
we
do
that
for
everything
that
is
natural
doing
by
learning?
So
we
are
so
many
of
our
SIG's
right
now
are
doing
that
and
contributor
experience
for
setting
up
a
marketing
team,
not
like
cube
con
I'm
talking
about
marketing
contributors
and
their
stories
and
putting
humans
behind
it
on
blogs,
live
code,
reviews,
API
reviews
and
triage
videos
on
YouTube
as
a
how-to
video,
that's
scalable!
You
then,
when
people
say
oh
I,
don't
know
how
to
triage
your
issues.
A
You
say:
oh
here's,
this
video
and
then
now
50
people
understand
how
to
triage
your
issues.
We
also
do
meet
our
contributors.
Now
it's
a
monthly
monthly
series
on
YouTube
that
we
live
stream
every
first
Wednesday
two
sessions
and
we
have
between
three
and
six
contributors
on
the
line,
and
we
ask
questions
I'll,
reinsert
questions
from
current
contributors
and
a
lot
of
new
contributors
as
well
about
their
journey
through
the
process
and
things
that
they
would
ask
a
normal
mentor
in
a
one-on-one
relationship.
A
Without
that
time,
burden
I
get
mostly
direct
messages
because
people
want
to
be
anonymous
there.
There
are
plenty
of
people
in
our
community
that
are
still
confused
by
what,
if
some
project
is
so
it's
important
that
we
get
those
things
out
in
that
kind
of
a
scalable
way,
also
q
Con,
we
ran
actually
we
have
another
session
this
afternoon
for
speed
mentoring,
where
we
put
people
in
little
pods,
not
one-on-one,
and
do
mentoring
and
pods,
and
do
this
sort
of
round
the
circle,
and
we
can
own
board
hundreds
of
people.
A
This
is
a
Tim
ISM,
Tim,
Aachen,
ISM,
slowing
down
and
being
more
careful
tons
of
release
process.
Conversations
going
on
as
I
mentioned,
we're
still
pumping
releases
out
every
four
months.
Is
that
something
we
want
to
do?
There's
a
long
term?
There's
an
LTS
working
group.
Also,
that's
sprung
up,
so
these
conversations
are
live
and
ongoing.
A
Something
else
that
we
should
really
focus
on
is
rewards,
recognitions
and
incentives,
as
the
new
guard
rolls
through,
they
aren't
incentivized
the
way
that
others
are
in
the
past.
I'm
sure
many
folks
in
here
know
other
people
who
have
contributed
to
a
source
for
quite
a
long
time,
and
this
is
especially
true
in
these
chop.
Wood
carry
water
rolls
when
there's
not
too
much
incentive.
A
When
you
don't
have
code
ownership,
when
you
don't
have
dock
ownership
like
what
is
the
real
incentive
to
be
a
chair
here,
I
might
not
be
able
to
tell
you
that,
but
these
are
things
like
project
management
being
a
facilitator
and
things
along
those
lines,
but
if
we
can
think
about
how
to
maybe
create
roles
and
create
other
incentives
may
be
learning
incentives,
then
maybe
this
could
maybe
this
could
help
us
out
and
that's
it.
Thank
you
so
much
to
all
of
our
contributors.
You
all
are
amazing.
A
Amazing
humans,
we're
blazing
the
trail
on
so
many
issues
when
people
say
to
me,
oh,
what's
the
tell
me,
you
know
tell
me
what
other
slack
community
has
seventy
thousand
people
in
it?
Who
can
we
turn
to
to
look
at
this?
I
say
we
are?
We
are
those
people
we
have
one
of
the
largest
slack
channels
in
the
world.
A
D
So
I
would
like
to
be
a
contributor,
so
I'm
not
right
now,
besides
bring
and
a
couple
of
little
bugs
for
documentation,
I've
got
an
idea
for
kubernetes,
that's
at
least
for
the
project
that
isn't
being
touched
on
at
all,
which
would
be
open
source
vendor-neutral
training.
There
isn't
any
right
now.
So,
where
would
I
go
to
begin
that
journey?
I'm.
A
D
Each
vendor
has
her
own
way
of
installing,
so
that's
fine,
but
from
after
installing.
Well,
how
do
I
use
coop
CTL,
no
I
can
go
to
the
docks
and
I
can
probably
get
some
out
of
it,
but
there's
no
training
course
telling
me:
how
do
you
keep
CTL?
You
might
find
some
random
YouTube
videos
from
3
years
ago,
but
you're
not
gonna,
find
anything
up-to-date,
you're
not
going
to
find
anything
up
to
open
source.
Ok,.
A
B
C
Yeah
in
the
next
doc
suppose
you
have
a
cat,
a
coder
courses
that
are
open
source
R&D,
hope
you
can
make
pull
requests
and,
for
example,
I
ran
the
meetup
here
in
Barcelona
flow
technology
foundation,
and
we
run
into
the
jams
each
month
open
to
everyone
and
all
the
content
we
make
is
published
in
github.
So
you
can
like
check
the
content,
get
the
slides,
use
them
change
in
it's
our
open
source,
so
I
can
follow.
I'll
show
you
all
this
material
we're
making
use
them.
I.