►
Description
Don’t miss out! Join us at our upcoming hybrid event: KubeCon + CloudNativeCon North America 2022 from October 24-28 in Detroit (and online!). 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 - Alison Dowdney, Kasten By Veeam; Christoph Blecker, Red Hat; Bob Killen, Google
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
Hello,
everyone
and
welcome
to
this
intro
to
sega
kubernetes
computer
experience.
We
are
one
of
many
special
interest
groups
within
the
kubernetes
project
and
in
this
talk,
we're
going
to
go
over
a
little
bit
about
who
we
are
and
what
we
do
and
how
we
do
it
with
that.
I'm
bob
killen
co-chair
of
sick
contributor
experience
alongside
you,
although
not
listed
here,
is
my
co-chair
allison
and
I
am
based
out
of
minnesota
in
the
united
states
and
I
work
for
google
also
on
the
project.
I'm
a
member
of
the
kubernetes
steering
committee
that.
B
So
no
matter
how
you
slice
it,
the
kubernetes
is
a
extremely
large
project
and
at
the
core
of
it,
it's
the
contributors
that
really
bring
a
project
to
life.
So
of
all
the
numbers
that
we're
showing
up
here
about
activity
and
size
of
the
project.
That's
the
one
that
I
really
want
to
draw
your
attention
to.
B
So
who
is
contributor
experience?
What
is
contributor
experience
summed
up.
We
are
a
cross-cutting
special
interest
group
that
focuses
on
the
experience
and
workflow
of
all
contributors
to
the
project,
both
experienced
and
brand
new
we're
made
up
of
folks
of
different
backgrounds,
companies
and
interests,
but
all
with
the
focus
to
make
kubernetes
a
better
place
to
contribute.
If
you
have
no
idea
where
to
contribute,
then
we'd
be
honored
to
be
your
first
sig.
B
B
A
lot
of
what
we
do
is
centered
around
defining
policies
and
providing
consistent
guidance
for
folks
providing
consistent
guidance
for
folks.
We
strive
to
give
contributors
a
consistent
experience
across
the
entire
project,
no
matter
which
sig
or
piece
of
code
or
documentation
you're
interacting
with
like
any
sig.
We
have
meetings
and
details
about
how
to
reach
us
on
our
contributor
site,
no
matter
which
sig
you're
wanting
to
get
involved
with.
This
is
a
great
first
place
to
go
and
look
for
information
up
on
kates.dev.
B
B
A
Swap
again
I'll
pick
things
up
with
community
management,
so
in
a
project
like
kubernetes
that
is
literally,
you
know
at
this
point
a
medium
to
large
size,
business
with
70
000
contributors,
there's
a
lot
of
things
that
go
into
sort
of
just
managing
how
the
community
operates.
That
really
starts
with
our
mailing
lists
and
calendars.
A
In
kubernetes
we
have
over
100
different
mailing
lists
and
oodles
of
calendars.
The
mailing
lists
are
generally
places
to
ask
questions:
we've
used
them
to
facilitate
decision
making.
We
share
out
meeting
notes
and
all
sorts
of
stuff
to
them.
You
can
actually
join
the
like.
If
you
join
a
six
specific
mailing
list,
you
will
automatically
get
access
to
all
their
calendar
invites
their
notes
and
a
whole
lot
of
other
stuff.
A
Transparency
is
also
important
to
us,
so
all
those
meetings
I
was
talking
about
that
you
can
get
access
to
by
joining
the
sig
mailing
lists,
we
publish
them
to
youtube.
We
also
have
all
sorts
of
other
stuff
on
youtube
from
like
code,
walkthroughs
sort
of
like
focus
things
on
like
recordings
from
the
various
contributor
summits
that
we
do
other
things
on
how
to
debug
test
flakes
to
random
sort
of
community
things
like
a
giant
three
hour,
long
bake
off
that
we
did.
A
We
are
also
stewards
of
the
community
repo,
and
this
is
sort
of
the
meta
meta
repo
for
kubernetes,
where
we
store
all
our
things
like
our
governance,
documentations,
our
election
procedures,
you'll
find
our
values
and
code
of
conduct,
and
this
sort
of
is
the
like.
I
want
to
say,
like
sort
of
help
desk
for
for
the
project,
but.
C
A
A
Otherwise
it's
all
kind
of
manual
collection
and
not
so
much
funness.
If
this
is
something
you
have
experience
with,
please
reach
out
to
me,
we
could
use
your
help.
Other
things
we
do
is
we
manage.
We
actually
have
like
an
instance
of
discourse
called
discuss.
Dot
com
is
the
I
o,
which
is
sort
of
our
end
user,
focused
community
forum.
It's
where
you
can
go
to
like
ask
general
questions
about
how
to
you
know,
use
kubernetes
or
problems
with
your
deployment.
A
Now
across
all
these
platforms.
We
also
have
a
slew
of
moderators
that
sort
of
just
help
our
community
safe.
We
have
in
the
root
of
the
root
of
k
community
but
like
in
the
k
community
repo.
We
have
a
list
of
moderators
that
we
try
and
make
sure
we
have
staffed
across
at
least
the
majority
of
time
zones.
So
that
way,
we
can
rapidly
respond
to
something.
A
Now,
we've
sort
of
tackled
the
community
part
I'll
tackle
the
next
sub
project
contributor.coms.
This
is
also
formally
known
as
the
like
marketing
subproject,
under
kubernetes
or
under
sig
controbex.
So
you
heard
about
all
those
different
communication
platforms
with
so
many
different
platforms
and
outlets.
A
Next
we
have
our
contributor
doc
sub
project
and,
as
pretty
much
like
all
developers,
do
the
first
thing
they
go
to
as
I'm
just
trying.
It
is
the
docs.
So
we
have
sort
of
a
set
of
docs
that
cover
two
broad
areas
and
that's
our
contributor
guide,
which
is
sort
of
the
general
how
to
get
on
ramped
into
the
project,
how
general
processes
go,
and
then
we
have
our
developer
guide,
which
tends
to
be
a
very
specific
docs
for
how
to
contribute
to
certain
areas
of
the
project.
A
A
B
B
We
decided
on
a
conference
style
of
meeting
due
to
like
uncertain
attendance
and
staffing
and
that
kind
of
stuff,
but
it
was
actually
very
well
attended.
We
had
a
bunch
of
different
topics
that
that
we
got
some
good
feedback
on
and
folks
talking
about
ways
to
improve
the
the
project.
Specific
areas
like
gateway,
api
or
much
more
general
topics
like
how
do
we
sustain
code
quality
across
a
very
broad
code
base.
B
Github
management,
so
this
is
another
another
sub
project
within
us.
We
have
bit
based
on
the
size
of
the
project,
the
number
of
repos,
the
number
of
organizations
within
github.
We
have
quite
a
large
footprint
that
requires
a
a
team
to
manage
the
the
team
has
done
a
lot
over
the
last
year,
a
couple
kind
of
key
things.
We
swapped
our
cla
system.
We
used
to
be
on
a
closed
source
system
that
was
not
very
flexible.
We
couldn't
really
figure
out
some
bugs
in
it.
B
There's
very
few
people
who
had
access
to
be
able
to
triage
things.
We
moved
over
to
easy
cla,
which
is
a
new
open
source
linux
foundation
project
which
will
hopefully
speed
up
that
process
of
both
identifying
and
fixing
bugs
in
our
cla
system,
as
well
as
making
the
whole
process
more
more
transparent.
With
more
people
having
access,
we
had
a
couple
new
github,
admins,
arno
and
nabroom
who've
been
helping
out
scale
our
processes.
B
We
we
get
a
large
number
of
requests
for
membership
to
our
github
organizations
as
well
as
requests
for
new
things
like
repos
or
integrations,
and
things
like
that.
So
we
added
a
couple
new,
github
and
mins
who
are
able
to
to
help
streamline
this
area
and
we're
going
to
continue
with
further
improvements
in
in
process
there.
B
So
the
next
area
is
mentoring,
but
I
want
to
go
a
little
talk
for
a
second
about
a
prerequisite
before
before
I
get
into
what
the
mentoring
subprojects
are
like.
So
this
is
our
contributor
ladder,
so
we
use
this
to
kind
of
track
and
talk
about
the
journey
of
a
contributor
as
they
join
the
project,
start
contributing
and
move
up
through
the
different
levels
of
trust
and
collaboration
in
the
project
getting
more
like
abilities
as
well
as
new
skills
along
the
way.
B
So
you
start
as
a
non-member
contributor
just
opening
prs.
Anybody
can
open
up
a
pr
against
any
part
of
our
code
base
and
and
contribute
once
you've
been
around
for
a
while,
and
you
get
more
familiar
with
the
project,
you
may
get
a
couple
sponsors
and
apply
to
become
a
member,
so
that
gets
you
some
bonus.
Things
like
your
tests
will
automatically
run.
You
don't
need
to
ask
somebody
to
start
your
start.
B
We
have
group
mentoring,
cohorts
that
are
usually
specifically
focused
on
a
specific
area
or
need
within
the
project.
Where
you
know
a
small
group
of
folks,
maybe
like
10
or
15
folks,
will
be
mentored
with
the
goal
of
some
of
them
becoming
a
reviewer
becoming
a
member
at
the
end
of
the
at
the
end
of
the
cycle.
If
they
they
stick
with
it.
So
our
mentoring
programs
are
very,
very
important
to
us,
but
we've
also
needed
to
scale
back
some
of
our
programs.
B
B
B
So
and
slack
as
a
tool
is
great,
but
it's
also
not
designed
as
like
a
public
tool
in
that
way.
So
there's
a
lot
of
things
that
they
don't
necessarily
have
like
moderation
tools.
They
expect,
if
you're,
using
it
in
a
corporate
environment,
and
you
have
a
problem
with
somebody-
you'll
go
and
talk
to
a
manager,
hr
or
somebody
to
help
deal
with
it.
But
in
our
case
we
need
a
moderation
team
who's
able
to
respond
to
to
issues.
So
we
built
some
tooling
around
it.
B
We
have
moderator
robots,
we
have
bots
that
can
send
announcements
to
a
bunch
of
different
channels.
At
the
same
time,
we
also
have
things
where
we
new
people
will
come
into
our
slack
and
maybe
won't
necessarily
understand
the
like
the
culture,
the
values
that
we're
trying
to
drive
within
kubernetes.
A
So
touched
on
this
a
little
bit
throughout
the
presentation,
but
a
few
things
on
how
you
can
contribute
to
the
project.
Well
contribute
controversy,
we
sort
of
you
know.
Oh
yeah,
we
went
over
a
lot
of
the
little
stuff
and
we
one
thing
I
do
want
to
try
is
that
we
need
people
with
a
whole
variety
of
different
skills
to
help
and
grow
and
grow
and
sustain
not
just
contributes,
but
the
project
at
large.
A
A
A
First,
big
thing
is:
join
the
sig
mailing
list.
That's
when
you'll
get
the
meeting
invites
join
committee.
Slack
join
the
sig
slack
you'll
be
able
to
find
this
list
of
them
and,
like
the
communist
community,
repo,
if
you
want
to
join
the
sig
specific
ones,
otherwise,
just
kind
of
browse
around,
though,
are
there
are
like
500
channels,
so
maybe
not
the
best
suggestion.
A
Actually,
the
other
thing
is
most
sigs
actually
reserve
time
for
new
people
to
introduce
themselves
co-chairs
and
members
of
kubernetes
are
usually
on
the
lookout
for
new
people
to
like
sort
of
help
make.
You
feel
welcome
help
you
with
like
finding
work
to
do
in
the
project
direct
you
to
help
wanted
or
good
first
issues
and
sort
of
shepherding
you
along
the
path.
A
A
A
So
last
thing:
if
you
want
to
reach
out
to
us,
that's
our
like
github
handles
within
there.
Most
of
us
are
also
like
available
across
twitter
slack.
All
that
other
fun
stuff
you'll
be
able
to
find
us
all
over
github.
You
can
read
more
about
us
in
the
k.
Community
read
for
sick
contributes,
join
the
mailing
list
join
slack,
and
I
hope
you,
you
know
wind
up
joining
and
have
fun
in
our
sick.
A
B
C
A
So
the
question
was
about
shadow
programs
and
where
they
are
in
the
community,
the
main
one
being
the
release
team.
That's
probably
the
most
well
known.
I
know
docs
has
done
a
few.
We
are
actually
talking
about
implementing
some
in
sick
intruder
experience.
There's
a
couple
other
sigs
that
are,
you
know
just
starting
to
approach
this
idea,
I
will
say
like
a
lot
of
a
lot
of
the
cigs.
Don't
have
shadow
programs
out
yet
but
are
interested
in
getting
started.
B
Yeah,
there's
a
number
of
groups
that
have
introduced
something
similar
to
it,
where
shadow
programs
really
shine
is
where
cigs
have
named
roles,
which
is
something
that
we're
encouraging
and
a
lot
more
sigs
are
taking
us
up
on.
As
far
as
defining
here's
a
particular
role.
Here's
a
like
a
run
book
for
that
role,
so
that
people
know
what
are
my
responsibilities.
What
do
I
have
to
do?
Even
how
long
I
have
to
do
it
for
and
rotating
folks,
through
a
lot
of
those
things
that
have
been
fairly
successful
at
sig
release.
B
We
want
them
to
be
able
to
see
your
contributions
and
to
see
not
just
a
one-off
pr
here
and
there,
but
the
idea
is
is
that
you
are
somebody
who's,
contributing
a
couple,
different
things
and
you're
having
conversations
you're
showing
up
to
sig
meetings,
you're
actively
participating
in
some
way,
the
the
criteria
for
being
a
reviewer.
There
is
a
defined
document
in
the
community
repo
that
says
who
is
a
reviewer?
B
What
what
is
that
that
criteria
to
figure
out
who
it
qualifies
for
that,
but
typically,
if
you're,
opening
up
prs
and
they're
getting
reviewed,
whether
they're
in
you
know
docs
or
code
or
policy
or
any
other
part
of
our
project,
because
all
of
it
all
of
it
exists
in
github.
If
you're
opening
prs
for
that
kind
of
stuff
that,
if
you're
speaking
to
the
people
who
are
actually
reviewing
and
merging
your
things,
those
are
the
folks
who
are
typically
eligible
to
sponsor
you,
one
of
the
other
key
things.
B
There
is
just
to
make
sure
that
we
have
neutrality
in
the
project
and
that
you
are
again
talking
to
folks.
Your
sponsors
cannot
be
from
the
same
company
and
the
idea
there
is.
We
don't
want
there
to
ever
be
a
part
of
the
project
where
it's
like.
Oh
yeah,
I'm
employed
by
xcompany.
That
automatically
gets
me
rights
into
the
project.
Nope,
that's
not
the
case.
You
need
to
build
relationships,
not
just
inside
your
company
but
with
other
folks
in
the
community
bob.
Do
you
have
anything
to
add
to
that.
B
E
So
if
you
were
leading
a
cig
or
a
working
group
and
were
interested
in
mentorship
and
shadow
program
and
those
kinds
of
things,
what
kind
of
roles
like,
surely
you
may
not
have
a
shadow
program
for
like
a
chair,
but
what
kind
of
you
you
mentioned?
Name
roles
like
what
does
that
look
like
what?
How
how
could
we
integrate
those
kinds
of
programs
in
okay.
A
A
Okay,
someone's
going
to
like
hold
this
role
for
a
year
or
two
years,
and
then
it's
their
job
to
either.
You
know
potentially
hold
it
again
or
think
about
finding
someone
else
to
take
over
that
role.
This
is
sort
of
the
idea
of
having
like
terms
associated
with
with
it,
and
there
can
be
more
than
one
people
in
that
specific.
You
know
role.
We've
seen
this
with
like
release,
managers
and
the
whole
like
release
manager
associate
program.
A
B
Bug
triage
is
also
a
common
one,
that
a
lot
of
different
cigs
have
like
a
rotate
like
some
sort
of
rotation
of
who's,
going
to
triage.
The
incoming
bugs
identify
things
that
are
duplicates,
identify
things
that
are
actual
real
bugs
or
things
that
are
expected
behavior
and
we
can
just
close
close
the
butt,
because
it's
not
actually
about.
E
A
B
The
bet
the
best
way
like
when,
when
a
sega
is
like
thinking
about
this
and
talking
about
how
to
define
those
roles,
is
to
make
them
small,
scoped
and
like
very
well
defined.
You
know
something
like
a
ci
signal
role,
for
example,
or
a
bug,
triage
role,
they're
roles
where,
like
you
could
have
it
be
where
somebody
like
tries
bug,
picks
it
up,
goes
and
fixes
it
close.
B
The
bug,
the
entire
life
cycle
of
it,
but
usually
that's
way
too
much,
especially
with
the
volume
of
things
coming
in
so
scoping
them
smaller
and
more
closely
to
to
what
it
is
where
it's
like.
Okay,
my
only
job
here
is
to
just
triage
it,
and
then
I
can
rely
on
the
rest
of
the
sig
and
other
folks
to
come.
Help
do
the
actual
fix
things.
C
So
I
know
about
google,
summer
of
code
and
outreachy.
They
are
good
programs,
they're,
good
programs
for
students
who-
and
you
know
it
gives
you
a
quick
quick
start,
but
these
programs-
I
don't
know
if
they
are
more
suitable
for
professionals-
I'm
not
a
student
and
I've
participated
in
g-sock
before
so.
I
cannot
do
it
again,
but
I
want
to
contribute
to
kubernetes.
C
You
know
there
are
a
lot
of
things
I
could
do,
but
sometimes
I'm
not
motivated
enough,
but
I'm
wondering
if
there
could
be
some
programs
for
professionals
as
well
or
non-student,
which
are
kind
of
like
gsoc
or
outreachy,
where
you
have
a
mentor
assignment
and
you
can
work
on
a
specific
issue.
I'm
not
sure
if
I'm
making
sense,
I'm
just
thinking
out
loud.
So.
A
So
the
the
question
was
things
like
gsoc
and
outreachy
are
really
targeted
towards,
like
students
and
getting
started.
There
isn't
really
a
program
out
there
that
targets,
people
that
that
doesn't
necessarily
apply
to
you,
potentially
people
that
are
like
out
of
college
already
sort
of
in
the
field,
but
are
looking
to
get
like
start
contributing
things.
I
I
do
believe
the
lfx
mentoring
program
does
apply.
B
The
so
the
big
issue,
with
a
lot
of
those
programs
and
one
of
the
reasons
why
we've
kind
of
put
a
pause
on
outreachy
and
gsog,
as
as
programs
they're
very
energy
intensive,
because,
typically
those
programs
are
like
assigning
one
mentor
to
one
mentee
and
then
they're
focused
on
a
particular
project.
There's
definitely
value
to
that.
But
it
requires
a
lot
of
maintainer
time
which,
in
our
current
state,
where
we're
like
we're
having
problems
finding
maintainers
and
maintainers
are
getting
burned
out.
B
That's
why
we're
focusing
on
some
of
these
programs,
where
it's
a
group
mentoring
where,
instead
of
a
one-to-one,
it's
a
one-to-n
kind
of
relationship,
we're
mentoring,
a
group
of
people
to
try
and
all
build
them
up
into
that
same
role
in
a
much
more
general
way,
as
opposed
to
a
mentor
mentorship
program
where
it's
like
a
one-on-one
relationship
for
a
particular
project.
They
definitely
have
their
place
and
they're
very
high
value
programs
that
we've
had
tons
of
phenomenal
people
that
have
gone
through
those
programs
in
our
project.