►
From YouTube: SIG Contributor Experience Deep Dive - B. Killen, A. Dowdney, C. Blecker, N. Raghunath
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
SIG Contributor Experience Deep Dive - Bob Killen, Google; Alison Dowdney, Weaveworks; Christoph Blecker, Red Hat; Nikhita Raghunath, VMware
The Kubernetes Contributor Experience Special Interest Group (SIG) is tasked with developing and sustaining a healthy contributor community. Things like feature velocity, community scaling, mentoring, pull request latency, and more all fall within scope of the SIG. In this talk, we will provide an introduction to SIG Contributor Experience, its role within the project, and dive into the various subprojects that support its mission. Additionally, we will provide a general community update and go over how you can get involved.
A
B
C
D
D
We
are
going
to
break
this
up
into
sections
and
talk
to
you
today
about
who
we
are
and
what
we
do,
no
matter
how
you
slice
it
kubernetes
is
a
large
project
and
at
the
core
of
it,
is
the
contributors
that
really
bring
this
project
to
life
of
all
the
numbers.
On
this
page,
that's
the
one
that
I
draw
your
attention
to.
D
If
you
have
no
idea
where
to
contribute,
then
we'd
be
honored
to
be
your
first
sig.
It's
not
uncommon
for
folks
to
hang
out
with
us
while
they
learn
how
the
project
works
and
then
eventually
move
on
to
a
seg.
That
is
more
closely
tied
to
a
specific
part
of
the
project
that
they're
interested
in
okay,
but
like
what
do
you
do
well?
Most
of
the
other
things
are
focused
on
a
specific
part
of
the
project
contributor
experience
spans
the
entire
scope
of
kubernetes
and
how
folks
contribute
contribute
to
it.
D
A
lot
of
what
we
do
is
centered
around
defining
policies
and
providing
consistent
guidance
for
folks.
We
strive
to
give
contributors
a
consistent
experience
across
across
the
project,
no
matter
which
sig
or
piece
of
code
or
documentation
you're
interacting
with
like
any
sick.
We
have
meetings
and
details
about
how
to
reach
us
on
the
contributor
site,
no
matter
which
sig
you're
wanting
to
get
involved
with.
This
is
a
great
first
spot
to
go.
Look
for
information.
D
D
D
A
Community
management
is
really
at
its
core
community
operations.
First,
we
have
mailing
listing
calendars.
All
of
our
mailing
lists
and
calendars
for
all
the
different
sigs
are
hosted
on
google
groups.
Collectively
we
have
over
50
different
calendars
and
mailing
lists,
all
of
which
play
an
important
role
in
the
running
of
the
entire
project.
A
A
A
A
We
also
from
time
to
time
do
live
streams
of
special
events
and
meetings.
This
includes
things
like
meet
our
contributors
and
the
events
from
the
contributor
celebration
held
in
december
last
year.
Subscribing
to
this
channel
will
keep
you
up
to
date
with
what's
happening
in
the
community,
so
make
sure
you
go
to
youtube.com
kubernetes
community
hit
that
subscribe
button
and
smash
the
bell
button,
also,
if
you're
confident
with
streaming
and
would
like
to
help
out
with
our
channel,
we
would
love
to
hear
from
you.
A
A
We
also
help
out
with
zoom
we
help
with
managing
the
licenses
needed
for
sig
chairs
so
that
they
can
use
zoom
to
record
their
meetings
if
you're,
not
a
sig,
chair
or
lead.
You
don't
need
to
worry
about
this,
but
if
you
know
how
to
administer
these
tools,
we
can
always
use
more
help.
If
that's
not
your
forte,
you
as
a
contributor
can
still
help
us
out
by
keeping
your
zoom
client
up
to
date.
This
makes
it
easier
for
us
to
use
new
features
in
zoom
and
helps
keep
you
secure.
A
Disqus.Case.Io
is
our
end
user
forum
powered
by
discourse?
It's
a
more
user-friendly
way
to
have
discussions
and
a
great
resource.
If
you
want
to
learn
more
or
have
questions
about
operating
kubernetes
with
all
these
different
platforms,
we
rely
on
moderators.
We
strive
to
make
our
communications
platforms
a
safe
and
inclusive
space.
We
will
not
have
a
wonderful
community,
like
we
do
today
without
our
moderators
and
are
always
looking
out
for
more
moderators
across
all
time
zones.
If
you're
an
experienced
community
moderator,
we
would
love
to
hear
from
you.
A
This
brings
us
to
the
comms
team
who
help
us
engage
with
our
upstream
community
contributor
comms
used
to
be
a
small
group
under
community
management
and
has,
since
grown,
becoming
an
official
subproject
in
november
of
last
year.
There's
a
talk
linked
here
in
the
slides
about
the
marketing
team.
If
you'd
like
to
learn
more,
our
contributor
documentation
is
a
set
of
living
documents
which
cover
two
broad
areas.
A
A
Our
developer
guide
provides
contributors
with
information
on
how
to
contribute
to
six
specific
areas
of
the
project.
Things
like
setting
up
your
development
environment,
api
conventions,
style
guides
are
all
covered
here.
It's
currently
undergoing
audits
and
updates
to
ensure
that
the
information
provided
is
accurate.
A
This
brings
us
to
the
contributor
site
at
kates.dev.
The
contributor
site
which
went
live
towards
the
end
of
august
last
year
is
a
hub
for
contributor,
docs
and
information.
It
contains
our
contributor
guide,
the
community
calendar
release
information
and
much
more
at
the
moment.
The
developer
guide
isn't
surfaced
on
the
website,
but
we
hope
to
have
it
there
in
the
future.
Devstance
is
a
tool
to
help
visualize
github
activity.
B
With
the
pandemic,
impacting
everyone
we've
had
to
adjust
our
strategy
for
hosting
and
managing
contributor
events.
We
actually
polled
our
contributors,
and
only
10
of
the
respondents
were
interested
in
doing
something
sort
of
like
more
regular
structured
content
with
80
of
them
actually
prefer
to
do
something.
Social
people
honestly
miss
the
holly
track
and
sitting
on.
Another
call
is
just
not
something
anyone
really
wants
to
do
so.
We
decided
to
put
together
a
computer
celebration,
an
event
that
was
focused
on
fun
and
letting
people
sort
of
get
together
and
hang
out
in
a
stress-free
setting.
B
We
offered
multiple
ways
for
people
to
participate
if
they
wanted
to
chat
or
just
watch.
You
know
that
was
perfectly
fine
for
those
that
did
want
to
participate.
We
had
trivia,
video
and
board
games,
and
even
things
like
contributor
awards,
we
want
to
be
hosting
a
bake
off,
and
the
bake
off
itself
is
actually
the
number
one
video
on
the
youtube
channel,
at
least
within
the
past
couple
of
years.
B
Now,
with
that,
out
of
the
way
that
takes
us
to
github
management,
this
sub
project,
along
with
the
github
m
team,
manages
how
contributors
interact
with
github,
along
with
things
like
you
know,
creating
and
managing
repos
one
of
the
things
that
achievements
we've
had
within
the
past
year.
If
you
happen
to
watch
our
kubecon
eu
session
last
year,
you
know
that
we
are
working
on
retiring.
B
The
kubernetes
incubator,
org
incubator
was
an
idea
sort
of
several
years
ago.
Do
you
like
try
out
some
things
and
they
decide
to
accept
those
projects
into
the
into
kubernetes
or
spin
them
back
out
again?
That
process
had
a
slip
of
issues,
so
the
incubator
process
was
replaced,
and
that
was
I
think
three
years
ago
now
now
those
three
that
three
years
ago
thing
is
true.
B
The
other
big
initiative
that
has
honestly
been
on
everyone's
mind
is
the
renaming
of
the
default
branch,
and
you
know
github
has
made
it
easier,
but
with
our
ci
scripts
and
a
slew
of
automation,
not
to
mention
it's
for,
like
200
plus
repos,
that's
a
significant
amount
of
effort
for
us.
We
have
worked
out
a
lot
of
the
kinks
and
are
now
moving
forward
with
it,
but
it's
a
little
complicated
and
we've
put
together
a
guide
for
our
contributors
that
you
can
find
at
keats.dev
our
contributor
website.
B
B
Like
certain
areas
of
the
code
base,
you
start
reviewing
pr's
and
eventually
you
get
pr
into
an
owner's
file
as
a
reviewer.
You
start
getting
work
assigned
to
you.
You
start
getting
more
familiar
with
a
specific
area
of
that
code
base.
You
become
a
sub
subject
matter
expert
in
that
area,
so
you've
you've
reviewed
a
bunch
of
pr's
at
that
point,
you're
sort
of
ready
to
become
an
approver.
You
start
to
learn
after
that.
You
start
to
learn
more
about
other
areas.
B
Under
that
sick,
you
may
become
a
higher
level
approver
for
that
entire
subproject,
and
at
that
point
you
are
starting
to
help
set
goals,
outline
the
milestones
and
sort
of
set
the
just
sort
of
lead
that
area
of
the
project,
and
this
is
sort
of
the
the
top
end
of
the
ladder.
But
for
many,
the
first
big
hurdle
is
making
the
jump
from
non-member
to
member.
B
So
mentoring
is
really
how
we
bring
on
new
contributors
and
help
our
current
contributors
grow
into
roles
and
become
sub
project
owners
or
future
sick
leads.
Some
of
our
programs
haven't
been
as
active
as
they
once
were
just
within
the
general
seat
of
the
world,
but
it's
something
that's
still
like
very
important
to
us.
B
B
B
B
B
These
are
often
like,
very
well
scoped,
with
a
lead
and
one
or
more
shadows,
with
the
assumption
that
at
least
one
of
the
shadows
will
eventually
take
over
the
takeover
for
elite
sort
of
creating
this
self-sustaining
cycle.
This
has
actually
been
used
to
like
great
effect
within
our
release
and
events
team.
B
B
B
Maintaining
a
safe
space
for
a
120
000
slack
users
can
definitely
be
a
challenge.
Slack
is
not
really
designed
for
open
communities;
they
just
expect
you
to
go
to
hr
if
you
have
a
problem
with
someone
and
that
really
doesn't
work
well
for
us.
So
we've
built
out
a
lot
of
moderator
functionality
such
as
reporting
messages
and
we've.
Now,
even
sort
of
like
extend
this
a
little
bit
with
some
various
like
word
detection.
B
The
other
thing
is:
this
is
more
focused
for
our
contributor
comms.
Is
we've
now
rolled
out
an
announcebot
that
lets
us
send
messages
to
like
out
to
a
big
list
of
channels
and
going
forward
we'll
be
using
this
thing
for
like
various
release
and
announcements
and
other
like
sort
of
community-wide
deadlines
or
other
just
like
community-wide
interesting
things,
and
with
that
I've
covered
everything
and
I
will
hand
it
over
to
nikita
to
wrap
things
up.
C
C
C
So
with
that,
let's
see
how
you
can
actually
get
involved,
I
really
recommend
joining
the
sig
meetings
to
get
an
idea
of
who
is
who
and
what
people
are
working
on.
If
you
join
the
six
mailing
list,
you
will
automatically
get
an
invite
for
the
meeting
and
also
like,
since
we
spread
across
the
globe
to
ensure
that
meetings
stay
accessible
for
everyone.
Sick
country
backs
has
asynchronous
meetings
on
slack
every
alternate
week
as
well,
and
if
you
miss
any
meeting,
don't
worry
because
they're
all
recorded
on
youtube
and
there's
honestly
only
so
much
time.
C
When
you
join
a
meeting,
you
are
definitely
going
to
feel
overwhelmed.
There
are
so
many
people
having
discussions
about
absolutely
foreign
concepts
and
nothing
makes
sense
to
you.
So
my
advice
in
this
case
is
to
take
it
slow,
don't
rush
it
and
don't
try
to
understand
everything
in
one
go,
because
chances
are
that
you
will
not
be
able
to
and
you'll
mostly
end
up
feeling
discouraged.
C
That's
where
so.
My
advice
is
to
look
around
and
try
to
get
an
idea
of
who
is
who
and
what
they're
working
on
so
understand
the
broad
ideas
behind
the
tasks
that
people
are
working
on.
That
they're
talking
in
meetings,
for
example,
like
try
to
understand
like
baby
bob,
is
working
on
the
feature
called
x
and
mata
is
working
on
another
thing.
C
Additionally,
we
have
plenty
of
non-code
related
opportunities.
Like
the
stream
team,
the
slack
administration
team
and
the
very
highly
active
contributor
marketing
team,
I
really
recommend
joining
them,
so
please
don't
feel
like
you
necessarily
need
to
know
how
to
code
to
contribute
to
the
six
non-code
roles
are
also
available.
C
So,
finally,
I'll
try
to
keep
this
short.
If
you
want
to
reach
out
to
us,
you
can
find
us
on
github
and
on
the
community
slack
at
these
handles.
You
can
also
join
the
sick
countrybacks
channel
on
the
community
slack
to
reach
out
to
us.
Our
home
page
also
has
details
and
more
that
we
signed
this
presentation
already.
I
look
forward
to
see
you
on
the
country
box,
mailing
list
and
slack
channel,
and
I
hope
you
decide
to
contribute
to
a
wonderful
site.