►
From YouTube: SIG Contributor Experience Deep Dive - Alison Dowdney, Weaveworks & Christoph Blecker, Red Hat
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. 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, Weaveworks & Christoph Blecker, Red Hat
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
A
B
B
B
If
you
have
no
idea
where
to
contribute,
then
we'd
be
honored
to
be
your
first
sick.
It's
not
uncommon
for
people
to
hang
out
with
us
while
they
learn
how
the
project
works
and
then
eventually
move
on
to
a
sig.
That
more
is
more
closely
tied
to
a
specific
part
of
the
project
that
they're
interested
in
okay,
but
like
what
do
you
do,
while
most
other
cigs
are
focused
on
a
specific
part
of
the
project
contributor
experience
spans
the
entire
scope
of
kubernetes
and
how
folks
contribute
to
it?
B
We
interact
with
contributors
at
all
levels,
both
those
just
starting
out
with
us
and
who
may
need
assistance,
learning
about
how
to
contribute,
as
well
as
folks
in
leadership
positions,
providing
them
with
the
tools
and
processes
to
be
successful.
A
lot
of
what
we
do
is
centered
around
defining
policies
and
providing
consistent
guidance
for
folks.
B
We
strive
to
give
contributors
a
consistent
experience
across
a
project,
no
matter
what
sig
or
piece
of
code
or
documentation
that
they're
interacting
with
like
any
sig.
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
our
contributor
site
is
a
great
first
spot
to
kind
of
go.
Look
at
that
information.
There's
a
couple
links
in
the
in
the
slides.
B
B
We
organize
the
work
we
do
into
sub-projects,
just
like
any
other
sig.
This
allows
us
to
split
things
out
and
then
delegate
that
work
out
to
to
responsible
for
parties.
Some
examples
include
our
contributor
site
and
community
repo,
which
house
details
like
the
central
sig
list
and
our
community
calendar.
A
So
all
these
sub
projects,
so
community
management,
is
one
and
community
management
is
at
its
core
community
operations.
So
first
thing
in
this
list
here
we've
got
mailing
lists
and
calendars.
So
if
you're
familiar
with
kubernetes,
you
probably
might
have
signed
up
for
some
of
the
mailing
lists
here.
So
we
have
like
mailing
lists
for
all
the
different
segs
and
they're
all
hosted
on
google
groups.
Collectively
we
have
about
50
different
calendars
and
mailing
lists
all
which
play
an
important
role
in
the
running
of
the
entire
project.
A
Currently
we're
working
on
an
effort
to
move
all
the
mailing
lists
from
google
groups,
so
groups.google.com
to
kate's
dot,
io
under
g
suite,
which
will
help
which
will
help
us
scale
more
and
more
larger,
because
I
think
one
of
the
big
issues
with
the
current
setup
is
you
know
it
can't.
It
doesn't
have
the
right
capacity
and
you
know,
there's
more
issues
and
yeah.
So
next
up
so
more
about
mailing
lists
and
calendars,
so
a
six
mailing
list
provides
a
place
for
for
six
specific
communication.
A
You
can
ask
questions,
facilitate
decision
making,
have
discussions
and
share
meeting
notes
with
others.
So,
by
subscribing
to
a
six
mailing
list,
you'll
be
automatically
invited
to
all
the
meetings
on
that
six
calendar
so
that
you,
as
a
contributor,
only
have
to
worry
about
signing
up
for
the
mailing
list.
You're
interested
in
then
filtering
out
your
emails
as
needed.
A
So
next
up
we
have
youtube.com
kubernetes
community,
it's
the
channel
home
to
all
of
our
youtube
videos.
So
here
you'll
find
recordings
of
sig
meetings
as
well
as
top
level
meetings
which
includes
our
monthly
commuting
community
meeting
meet
our
contributors.
We've
got
instructional
videos,
code,
walkthroughs,
there's
even
the
contributor
workshop.
All
recordings
of
that
are
available
on
the
kubernetes
community
youtube
and
many
more
that
I
probably
couldn't
listen
this
time
here.
A
So
we
also
from
time
to
day
time
do
a
bit
of
like
live
streaming
and
we
live
stream
special
events
and
meetings.
So
so,
for
example,
we
had
the
events
for
the
contributor
celebration
held
december
last
year,
so
you
might
have
seen
on
the
kubernetes
community
youtube
like
there's
a
there's.
The
live,
like
recording
of
the
the
kubernetes
bake
off
that
we
had
the
cloud
native
bake
off.
So
by
subscribing
to
this
channel.
A
You'll
be
kept
up
to
date
with
what's
happening
in
the
community,
so
make
sure
you
go
to
kubernetes.com.
I
mean
youtube.
Kubernetes.Com
go
to
youtube.com
kubernetes
community,
hit
that
subscribe
button
and
mash
that
bell
button.
Yes
got
the
youtube
hype.
Words
there,
so
community
repo,
so
kubernetes
community
is
where
our
community
repo
lives.
So
in
here
we
will
find
things
such
as
governance,
election
procedures,
values,
code
of
conduct
and
and
yeah
any
project
that
revolves
around
the
kubernetes
project
as
a
whole
is
owned
by
this
project.
A
So
another
thing
about
elections
that
I'll
just
chime
in
on
this
note
here
there
is
a
currently
you
know
there
is
a
an
election
happening
for
the
steering
committee.
You
can
check
that
out
online.
If
you
just
go
on
kubernetes
community
and
you
see
in
the
there'll,
be
an
elections
folder,
I
believe,
and
yeah
it'll
be
right
there.
So
I
forgot
to
put
that
in
the
notes
here
so
zoom.
We
help
with
managing
the
licenses
needed
for
seg
chairs
so
that
they
can
use
zoom
to
record
their
meetings.
A
So
if
you're,
not
a
sig
chair
or
lead,
you
don't
really
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
zoom
up
to
date.
This
makes
this
easy.
This
makes
it
easier
for
us
to
use
new
features
in
zoom
and
helps
keep
you
secure.
A
Discuss.Kates.Io
is
our
end
user
forum
and
it's
powered
by
discourse.
It's
a
more
user-friendly
way
to
have
discussions.
It's
a
great
resource
if
you
want
to
learn
more
or
have
questions
about
operating
kubernetes
like
so,
for
instance,
if
you
go
into
that
discuss.k
io
right
now
on
your
phone
you'll
see
there's
so
many
like
threads
and
things
where
people
are
asking
help.
I'm
stuck
on
this.
A
We
wouldn't
have
an
amazing
community
like
this,
as
we
do
today
without
like
our
moderators
and
we're
always
looking
for
more
moderators
across
all
time
zones.
So,
if
you're
experiencing
it,
if
you're
experienced
with
community
moderation
like
you've,
managed
some
slack
or
some
discord
or
something
like
that,
we
would
love
to
hear
from
you
because
yeah
we,
we
always
use
my
help
so
yeah.
A
So
you've
just
heard
about
all
these
different
communications
platforms
that
we
have
so
with
all
these
different
platforms.
It
can
be
very
challenging
to
reach
our
contributors,
which
brings
us
to
our
wonderful
marketing
team,
aka,
contributor
comms,
who
help
us
engage
with
our
upstream
community.
So
contributor.coms
used
to
be
a
very
small
group
under
community
management
and
it's
since
grown
becoming
a
and
it
became
like
an
official
subgroup
of
sig
contributor
experience
in
november
of
last
year.
A
So
yeah
and
keslan's
doing
some
really
awesome
work
there
and
helping
like
with
those
efforts,
so
I
just
want
to
shout
out
to
them
right
now
like.
Thank
you.
Thank
you,
our
marketing
team,
so
there's
a
talk
linked
here
in
the
slides.
If
you
want
to
learn
more
about
the
marketing
team,
it's
story
or
the
backstory,
you
know,
if
you
want
to
learn
more,
so
do
go
check
that
out.
So
next
up
our
contributor
documentation.
So
it's
a
set
of
living
documents
which
cover
you
know
two
broad
areas.
A
A
So
our
developer
guide
provides
information,
provides
contributors
with
information
on
how
to
contribute
to
six
specific
areas
of
the
project.
So
things
like,
how
do
you
set
up
your
specific?
How
do
you
set
up
your
development
environment
if
you're
going
to
contribute
to
say
6
cli?
How
do
you
set
up
like
how
do
you
just
yeah
specific
stuff,
yeah,
so
api
conventions
and
style
guides
stuff
like
that?
A
What
is
this
signal
about
like
being
able
to
understand
how
you
know
to
contribute
like
how
to
how
to
set
yourself
up
it's
great?
So
a
little
went
on
a
little
bit
of
a
ramble
tangent
there
so
on
both
these
areas,
we're
both
looking
for
help
revising
them,
especially
from
new
contributors
who
can
approach
them
with
kind
of
a
fresh
perspective,
because
I
think
we
a
lot
of
people
like
who
are
experienced.
We
can
kind
of
miss
things
out
and
we're
like.
A
Oh,
we
already
had
this
thing
installed
and
it
and
it
just
kind
of
goes
under
the
radar
there.
So
yeah
definitely
check
that
out.
If
you're
like
looking
for
something
to
contribute
to
so
next
up,
we
have
the
contributor
site
at
kates.dev.
So
it's
the
contributor
site
which
went
live
towards
the
end
of
august
last
year
is
a
hub
for
contributor,
docs
and
information.
It's
got
the
contributor
guide,
which
we
just
mentioned,
the
community
calendar
the
release,
information
and
much
much
more.
At
the
moment.
A
A
Next
up,
we
have
devstats
so,
and
you
probably
might
have
seen
the
talk
earlier
in
the
conference.
I
believe
dr
dawn
foster
did
a
really
good
talk
about
beyond
stars
and
for
stars
and
forks.
You
know
measuring
the
health
of
your
cncf
project
and
it
touches
a
lot
on
dev
stats.
So
I'll
link
that
later
but
anyway
for
people
who
aren't
familiar
with
dev
sets
devstats
is
a
tool
that
helps
us
visualize,
github
activity.
A
It
uses
the
github
archives
and
data
to
crunch
a
bunch
of
stats
and
then
calculate
you
know
github
events,
so
this
can
give
us
huge
things
like
how
quickly
prs
are
getting
reviewed.
How
quickly
are
things
like
getting
seen
approved
who's
contributing
it's?
Where
someone
we
got
it's
where
we
got
some
of
the
numbers
for
that.
First
slide
that
you
saw
earlier
about
our
number
of
contributors.
We've
been
revisiting
the
boards,
so
we
can
get
more
actionable
metrics.
A
B
Thanks
alison,
so
with
the
pandemic,
impacting
everyone
we
kind
of
needed
to
adjust
our
strategy
for
how
we
hosted
and
manage
contributor
events.
We
would
normally
host
multiple
contributor
summits
a
year
to
allow
people
to
kind
of
come
together
and
learn,
but
that
didn't
didn't,
for
obvious
reasons,
didn't
didn't
quite
work
out.
The
way
we
expected
to
we
pulled
our
contributors,
and
you
know,
with
with
everything,
that's
kind
of
gone
on
the
last
18
months.
B
We
had
a
contributor
celebration
on
on
monday
night,
we're
looking
to
kind
of
put
more
emphasis
on
on
some
of
those
those
social
events
to
allow
to
bring
our
contributors
together,
both
in
person
as
well
as
in
in
virtual
settings-
and
you
know
a
great
example
of
that
is
we
had
last
year
we
had
a
contributor
celebration
event
near
the
end
of
the
year
where
we
had
like
trivia
and
board
games.
We
had
things
like
a
contributor
bake
off
as
alison
mentioned
earlier.
B
B
So
this
is
the
sub
project
where
the
github
management
team
manages
how
contributors
interact
with
github.
We
have
a
number
of
different
organizations
and
lots
of
repos,
and
you
know
again
going
back
to
our
what
I
was
saying
earlier
like
we
want
people
to
have
a
consistent
experience
as
they're
contributing
to
like
200
plus
different
repos.
We
wanted
that
to
be
like
a
want
to
feel
the
same
as
you're
interacting
with
each
of
them.
B
B
This
is
for
multiple
reasons.
Number
one:
the
old
tool
wasn't
actually
open
source.
It
was
a
a
closed
source
product,
so
we
wanted
to
move
to
something.
That
was
that
we
could
enhance
that.
We
could
see
the
code.
We
could
make
changes
if
we
needed
to
as
well
as
the
old
cla
tool.
If
you
ever
used
it
like
it
wasn't.
B
It
was
very
opaque
as
far
as
if
you
hit
a
problem
with
it,
if,
if
you've
signed
the
cla
and
it's
working
for
you,
it
just
works,
and
you
don't
need
to
think
about
it.
But
if
you
ever
have
problems
with
it,
it's
very
hard
to
kind
of
diagnose
those
errors
and
figure
out
what
what
the
root
cause
the
actual
problem
is.
So
the
new
system
will
have
a
lot
more
clarity
and
transparency
around.
B
So
I
want
to
talk
about
mentoring
for
a
moment,
but
I
need
to
go
over
a
couple
prerequisites
first.
So
if
you
haven't
seen
this
before,
this
is
our
contributor
ladder.
So
this
is
the
this.
Is
the
process
and
kind
of
a
path
that
we
have
created
as
far
as
allowing
contributors
to
kind
of
understand
how
our
project
is
organized
and
to
facilitate
growth
within
the
project?
B
So
when
somebody
starts
out
new
they're,
a
non-member
contributor,
when
once
you've
kind
of
got
some
contributions
under
your
belt,
you've
developed
some
relationships,
you
can
get
some
sponsors
to
put
in
an
application
to
become
an
org
member.
Once
you
become
an
org
member,
there's
some
benefits
there,
like
we
trust
the
tests
that
you're
running,
and
so
you
don't
need
to
wait
for
somebody
to
okay
that
it's
like
safe
to
test
your
your
pr.
B
Continuing
your
undergrowth,
you
become
the
next
step
as
an
approver.
Approvers
are
people
who
actually
have
commit
rights
to
a
repo,
so
the
the
people
who
have
approver
rights
over
a
particular
part
of
the
code.
It
doesn't
necessarily
need
to
be
an
entire
repo,
but
people
who
have
approval
rights
over
part
of
our
code
base.
B
So
our
sub
project
owners
are
the
people
who
are
setting
the
kind
of
the
vision
for
a
particular
area
of
code
they're.
The
people
who
are
who
are
coordinate
kind
of
those
larger
like
design
architectural
kind
decisions
for
that
part
of
the
code,
they're
also
people
who
are
going
to
liaise
with
other
sub-project
owners
other
parts
of
the
code
base.
B
So
this
is
very
important
to
us,
because
it
shows
that
kind
of
growth
pattern
as
we
as
we
want
to
mentor
people
and
grow
people
within
the
project.
So
that
brings
me
to
mentoring.
Mentoring
is
essential
to
our
overall
project
health.
This
is
this
is
something
that
we
we
can't
say
enough.
So
we
we've
done
things
in
contributor
experience.
B
B
So
a
couple
examples
I
I
want
to
be
respectful
time,
so
I'm
just
going
to
skim
through
a
couple
of
these
examples.
One
of
them
is
meteor
contributors,
so
major
contributors
is
like
a
live
streamed.
Ask
me
anything
panel
where
we
kind
of
gather
some
experienced
contributors
and
people
can
submit
questions
and
have
these
experience.
Contributors
answer
those
specific
questions.
B
Those
are
like
very
common
things
that
come
up
when
we
bring
those
those
experts
in
another
one
is
is
like
we,
we
do
things
like
google,
summer
of
code
and
outreachy
interns
where
we
can
support
people.
You
know
not
just
getting
involved
with
the
project,
but
also
being
able
to
work
with
these
programs,
provide
financial
support
for
for
new
contributors
who
are
who
are
engaging
with
our
project,
to
help
us
out
on
like
very
specific,
guided
projects
and
then
receive
support
for
it.
B
A
Thank
you
very
much
christoph,
so
we
looked
at
what
contrabex
does
and
the
different
kinds
of
subprojects,
in
the
sake.
So
now,
let's
try
understand
how
you
you
and
the
audience
audience
and
you
watching
online
can
get,
can
get
right
and
like
jump
in
and
start
contributing
to
all
these
many
sub
projects.
A
So
before
I
talk
about
the
more
about
this
first
things,
first,
I
want
to
call
out
that,
no
matter
what
people
are
the
center
of
kubernetes,
like
everyone,
who's,
like
you
know
out
here,
supporting
like
everyone
here
like
you,
know
people,
it's
all
what
makes
it
happen
around
here
so
especially
for
this
sig.
It
is
our
mission
to
make
contributing
to
kubernetes
easier
and
to
ensure
we
have
a
diverse
and
sustainable
contributor
base.
So
let's
see
how
you
can
get
involved,
so
I
really
recommend
us
a
good
starting
point.
A
You
can
join
sig
meetings,
so
sick
meetings
help
you
get
an
idea
of
who
is
who?
What
is
what
and
what
kind
of
the
context
and
what
people
are
working
on.
So
if
you
join
the
sex,
mailing
list,
like
I
mentioned,
like
you'll,
automatically,
get
an
invite
for
the
the
sigs
weekly
meeting
so
to
ensure
meetings,
stay
accessible
for
people
around
the
globe.
Contrabex
has
asynchronous
meetings
on
slack
every
alternative
week
too.
So,
if
you
and
and
as
well,
if
you
miss
any
meeting,
don't
worry
they're
all
recorded
on
youtube.
A
So,
and
even
I
myself,
you
know
there's
only
so
much
time
in
the
day
and
even
though
I'm
present
at
most
of
the
zoom
meetings,
I
usually
go
and
back
and
watch
watch
them
again.
So
I
can
make
sure
that
oh
is
there
anything
like
you
know
we
missed
out
in
meeting
notes
or
like
is
there
anything
like?
I
didn't
really
fully
kind
of
grasp
at
the
time.
So
with
that
when
you
join
a
meeting,
we're
gonna
go
sorry.
A
So
so
with
that,
here's
a
couple
tips
on
you
know
joining
your
first
sig
meeting.
So
when
you
join
a
meeting
like
especially
if
it's
your
first
time
like
you're
gonna,
feel
you're
gonna
feel
a
bit
overwhelmed.
So
there
are
so
many
people
having
discussions
about
things
that
you
might
not
be
that
familiar
with,
and
nothing
might
make
that
much
sense
at
the
time.
A
What's
on
the
roadmap,
this
makes
the
information
digestible
and
helps
you
not
feel
incredibly
overwhelmed
with
everything.
Now
another
thing
like
we
usually
ask:
if,
like
there's
anyone
new
on
the
call
or
at
the
at
the
start
of
the
meeting,
we
we
say
if
we
like
notice,
there's
a
bunch
of
new
people,
we'll
we'll
try,
our
best
to
say,
do
do
a
round
of
introductions
because
I
can
find,
if
you're
new
to
a
community.
It
can
be
very
overwhelming
to
write
your
hand
up
and
say:
oh
hello,
I'm
here.
A
I
want
to
do
something
so
yeah
another
thing
about
with
these
sig
meetings
as
well,
usually
at
the
at
the
end
of
the
contrabex
one.
We
have
time
for
just
chatting
just
questions
and
answers.
So
if
you've
got
like
something
that
you
want
to
bring
like,
how
do
I?
Where
do
I
get
started
or
like
you
know,
can
you
recommend
me
a
good
issue
or
something
or
some
way
to
look
at
something
for
them
to
look
out
like
yeah?
That's
a
it's!
A
really
good
entry
point.
A
So
next
slide
I'll
wrap
this
up
quickly.
There's
also
plenty
of
non-code
related
paths
available.
So,
for
instance,
we
have
you,
know
the
stream
team,
slack
administrator
and
highly
active
contributor
marketing
team,
so
you
don't
necessarily
need
to
know
how
to
contribute
to
our
sig.
So,
finally,
if
you
want
to
reach
out
to
us,
you
can
find
us
on
github
and
on
the
kubernetes
slack
at
these
handles
our
home
page
has
also
has
all
the
details
and
more
that
you
saw
in
this
presentation.
A
A
C
B
I
I'm
not
entirely
sure
so.
The
way
the
way
could
tribex
works
without
reaching
is
we
kind
of
coordinate
the
the
our
our
work
with
the
between
all
the
different
things
in
the
project,
so
the
different
sigs
kind
of
come
to
us.
What
we
do
kind
of
a
call
like
hey,
if
you
know
we're
not
coordinating
this
year's
outreachy
programs
and
that
kind
of
stuff.
B
I
don't
think
we
have
anything
from
us
right
now,
but
we
also
coordinate
with
the
other
cigs
as
far
as
like
making
making
sure
that,
like
that,
they
they
know
like
what
what
the
deadlines
are
for
every
g
and
and
helping
them
kind
of.
Like
put
applications
together
to
start
outreach
programs,
so
I
don't
know
of
anything
off
the
top
of
my
head
right
now,
but
the
the
very
common
answer
that
you'll
hear
from
most
of
the
stuff
is
come
reach
out
to
us
in
the
sig
contrabax
channel.
B
So
there
are
two
clearly
defined
governance
roles
that
all
sigs
have
they're
as
the
chair
and
the
tech
lead.
So
the
tech
lead,
like
my
primary
responsibilities,
are
doing
things
like
when
we
have
applications
for
like
new
sub-projects
for
the
sig
nikita
and
myself.
Who
who
share
this
role
for
controvex,
we
kind
of
we
look
it
over.
B
We
make
sure
that
it
kind
of
works
with
our
sig
charter
and
the
things
that
are
defining
make
sure
that
it's
something
that
our
sig
is
explicitly
responsible
for
and
then
we
kind
of
approve
the
creation
of
that
sub-project
or
trying
to
get
it
refined.
We
work
with
other
tech
leads
for
for
other
cigs
to
do
that
kind
of
same
roles.
If
there's
like
the
scope
is
not
clearly
defined
and
and
trying
to
like,
do
some
interpretation
of
the
charters
and
also
working
with
the
steering
committee
in
that
regard.
B
As
far
as
making
sure
that
you
know
the
right
thing
lands
with
the
right
sig
and
the
other
thing
is,
we
are
a
technical
escalation
point
within
the
sig.
So
if
a
particular
sub
project
either
doesn't
know
whether
something
is
kind
of
the
right
direction
as
far
as
our
overall
direction
and
vision
and
where
we
want
to
go
for
for
the
project,
we
kind
of
act
as
a
technical
escalation
point
for
that
so
and
it
can
be.
Sometimes
it's
really
big
things.
B
Sometimes
it's
really
small
things
as
far
as
making
sure
that,
like
a
contributor
flow,
you
know
as
far
as
maybe
adding
a
label
to
a
repo,
and
what
that
looks
like
like.
Does
that
making
sure
that
we
kind
of
understand
the
impact
of
that
particular
action
on
the
contributing
workflow
and
making
sure
that
it
aligns
with
our
charter
and
kind
of
our
established
practices
and
that
kind
of
stuff.