►
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
Intro: Contributor Experience SIG - Elsie Phillips, Red Hat & Paris Pittman, Google
In this 30 minute session, we will explore the projects we have been working on with Contributor Experience and the future work we have on deck. We will provide an update to the and have information on how to get involved.
https://sched.co/UaiB
A
So
our
definition
of
contributor
is
is
very
broad,
because
we
also
want
to,
of
course,
capture
the
contributions
of
non-code
contributors.
So
how
we
think
of
this
is
anybody
that
makes
a
contribution
that
triggers
a
github
event.
So
this
might
look
like
filing
issues.
Prs
commits
comments,
stuff
like
that
so
hi
everybody.
My
name
is
Elsie
Phillips
and
I'm
a
contributor
and
also
a
co-chair
for
contributor
experience.
B
B
I
know
we've
tried
and
we've
ran
out
of
time,
every
time
that
we've
tried
so
so
and
for
the
purpose
of
the
talk
we
will
most
likely
be
giving
very
high-level
things.
So
if
you
want
to
go
into
any
kind
of
detail
afterwards
or
if
we
do
have
some
time
afterwards
for
questions,
please
by
all
means
the
github
management.
Part
of
this
talk
is
honestly
its
own
talk
and
guess
what
there's
plenty
of
them
on
YouTube
right
now
from
Christophe,
Aaron,
Craig
and
Berger,
Nikita,
etc.
B
B
So
we're
gonna
break
this
down
by
the
following:
we're
going
to
go
by
cell
project
and
also
hit
on
some
of
the
teams.
What
is
some
project
is
in
kubernetes
is
really
how
we
break
down
the
ownership
and
the
work
and
some
projects
or
areas
of
the
project
like
directories
of
code
or
Docs,
and
things
like
that.
They
all
have
like
a
root
owners
file
and
those
owners
are
called
sub
project
owners
and
that's
really
how
we
kick
things
off
and
I.
B
Think
right
now
we
have
like
over
a
hundred
and
eighty
or
some
sub
projects
within
within
kubernetes
itself.
If
that
gives
you
any
idea
of
the
magnitude
that
is
kubernetes
so
for
the
next
20
minutes
here
we
go
we're
going
to
talk
about
some
of
those
cool
sub
projects
up
there,
so
the
first
one,
the
one
that
I
think
is
most
important,
I
won't
lie
and
bias
is
mentoring
and
contributor
growth,
and
what
we
mean
here
is
not
necessarily
just
new
contributor
programs
either.
B
So
it's
really
important
that
we
do
succession
planning
for
contributors
and
so
we're
always
trying
to
figure
out
new
ways
and
new
mentoring
programs
around
how
we
can
get
people
at
scale.
Through
these
contributor
ladders,
you'll
hear
a
lot
of
open
source
projects,
including
ours,
talk
about
things
like
gee
sock,
which
is
google
Summer
of
Code,
and
also
outreach
e,
which
is
another
wonderful
third
party
internship
program
that
attracts
under-represented
folks
and
pays
them
yes.
B
B
These
are
the
some
of
the
mentoring
programs
that
we've
either
created,
tested,
shipped,
etc,
and
really
what
I
wanted?
To
put
this
a
lot
of
words
on
this
lie,
but
I
wanted
to
show
you
is
that,
when
creating
some
of
the
mentoring
programs,
we
take
a
lot
of
things
in
consideration.
One
of
those
things
is
learning
styles.
B
Luckily,
for
humans,
we're
not
all
the
same,
and
we
all
have
differences,
and
if
we
all
could
just
figure
things
out
by
reading
a
contributor
guide,
we
probably
wouldn't
have
half
the
problems
that
we
do,
but
we
don't
we
need.
We
need
other
things
right.
We
need
videos,
people
learn
on
video.
We
have
a
very
large
remote
distributed
team,
obviously
with
35,000
people
over
the
world.
Yes,
it
is
heavy
on
the
west
coast,
but
it's
also
heavy
now
in
other
markets
as
well.
B
I
see,
I,
see
shoutout
and
we've
also
do
we
also
do
contributor
workshops,
so
that's
both
online
and
recorded
really
scalable
solutions,
because
when
we
talk
about
mentoring,
usually
we're
talking
about
like
I'll,
fill
out
a
form
and
like
somebody,
randoms
gonna
match
with
you
and
that
kind
of
stuff
really
isn't
available.
So
these
are
scalable
solutions
and
things
that
still
match
our
values
and
still
have
a
lot
of
camaraderie
to
it.
A
And
so
we're
currently
doing
an
audit
and
we're
moving
inactive,
reviewers
and
approvers
and
giving
them
that
emeritus
status
moving
forward
in
the
next
quarter,
we'll
be
removing
inactive
org
members
and
creating
some
policies
and
procedures
around
that.
So
that's
transparent
for
people
who
counts
in
what
category.
A
Some
other
things
that
we're
working
to
address
in
the
sub
project
is
figuring
out
our
plan
forward
for
incubator.
We
made
the
decision
that
a
lot
of
that
should
actually
live
in
the
sig
orcs
and
so
will
be
deprecating
the
legacy,
kubernetes
incubator,
org
and
then
and
then
moving
everything
else,
moving
the
relevant
bits
still
back
into
the
SIG's
and
then
retiring
the
rest.
So
some
stats
around
that
we've
moved
seven
we've
retired
one,
and
then
we
still
have
seven
to
go
through
and
then
another
thing
that
we're
working
on
is
the
CLA
bot.
A
That's
generally
one
of
people's
first
experiences
with
the
project,
and
so
it's
really
really
important
that
that
experience
be
a
positive
one
that
it
it
works.
Well,
and
so
we've
been
talking
about
doing
a
second
iteration
of
the
CLA
bot
for
for
a
while
another
iteration
of
it
and
so
and
making
that
open-source,
and
so
we've
been
working
with
the
scene
CF
on
that
and
expect
to
see
that
that
next
iteration
around
March
2020.
A
Into
the
next
sub
project,
we're
going
to
talk
about
contributor
documentation,
we
like
to
joke
that
contributor
Docs
is
our
gateway
drug
to
contribution
you're
going
through
the
docs
and-
and
you
find
something
you're
like
oh,
like
this-
isn't
an
intimidating
thing
to
to
try
and
to
fix,
and
once
we
get
you
once,
we
think
that
we
can
get
you
again.
So
we
always
encourage
people
to
try
and
get
involved
in
contributed
ox.
A
It's
a
great
opportunity
for
for
new
people
to
the
project
to
offer
something
and
valuable
to
the
community,
which
is
a
fresh
pair
of
eyes.
We
have
a
bunch
of
great
assets
available
to
people,
a
contributor
guide,
contributor,
cheat
sheets,
the
developer
guide,
the
non
code,
contributor
guide
and
the
contributor
site.
A
We've
been
working
to
get
that
contributor
site
off
the
ground
for
a
little
bit
now
and
really
excited
to
have
an
outreach
intern
to
help
us
move
towards
that
finish,
line
on
the
project,
so
super
jazzed
about
that,
and
then
we're
also
really
excited
about
being
able
to
offer
the
contributor
cheat
sheet
in
several
other
languages.
Doing
some
localization
around
that.
We
think
that
it's
really
important,
that
this
project
be
friendly
to
non-native
English
speakers.
A
So
continuing
off
of
that
we
are,
we
created
actually
an
entire
team
in
our
sig
around
some
kind
of
internationalization
efforts
and
they're,
based
in
a
pack
and
they're
doing
an
amazing
job,
helping
to
create
dedicated
channels
for
those
regionalised
groups
and
creating
some
localized
events
as
well,
and
so,
if
you're
interested
in
participating
in
that
definitely
check
out
the
their
meetings
that
happened.
Nikita
remind
me
one.
A
Def
stats
is
another
sub
project
that
we
work
on.
It's
this
great
dashboard,
where
we
can
keep
an
eye
on
stats
related
to
the
community.
It
helps
SIG's
make
data-driven
decisions
about
policies
that
they
want
to
implement.
So
that's
all
publicly
available.
So
if
you're
interested
check
out
dev
stats,
dot,
kubernetes,
dot,
I
think
that
is
the
URL
yes
no
hand
this
back
over
to
Paris.
B
Another
sub
project
that
we
do
a
ton
of
ton
of
work
and
especially
transactional
work
and
policy,
and
things
along
that
line
is
community
management.
Community
management
here
is
pretty
much
anything.
That's
not
get
up
infra
for
the
most
part.
So
that's
things
like
that's
things
like
making
micro
groups
for
certain
personas.
One
of
those
is
sick,
chairs
and
tech
leads
because
they
all
need
different
kinds
of
information
to
them
at
different
kinds,
for
different
reasons,
and
you
can
imagine
if
you
work
in
a
company-
that's
35,000
people.
B
Large
communication
is
probably
up
there
with,
like
one
of
your
concerns,
I'm
sure,
like
I
work
at
Google,
so
you
know
100k,
plus
things
get
a
little
hairy
in
the
watering
down
of
communication.
So
this
is
something
that
we're
always
always
iterating
on
meaning
changes.
As
far
as
like
what
communication
platforms
to
bring
on,
how
can
we
consolidate?
B
B
So
that's
the
the
image
that
you
see
on
the
screen
right
now
is
a
part
of
the
communication
directory.
So
you
can
kind
of
get
a
gist
of
some
of
the
stuff
in
there
that
we
work
on
supporting
all
these
communication
streams
would
not
be
possible
without
our
moderator,
so
I
absolutely
wanted
to
shout
them
out.
Even
our
github
team
as
well,
these
folks
moderate
stuff
on
it
on
just
24/7
basis.
You
can
imagine
with
all
the
comments
that
we
get
on
github.
B
We
have
80,000
slack
members,
it's
just
out
of
this
world
as
far
as
the
communication
that's
going
on
with
it
within
this
project
and
I
guarantee
you
90%
of
these
people
aren't
paid
to
do
it.
So
this
is
one
of
our
most
selfless
roles
that
we
have
and
they're
actually
on
the
front
line,
taking
a
lot
of
emotional
abuse.
Sometimes
so
it's
very
important
that
you
think
in
it
that
you
really
think
in
moderator
these.
So
if
you
know
of
any
moderates,
do
we
have
any
moderators
in
the
room?
B
Actually
I
think
we've
got
github
team
right
in
the
front.
Can
we
embrace
hands?
I,
really
appreciate
you
all
seriously.
I
know
it's
like
it
seems
like
the
easiest
work
in
the
world
when
you're,
just
like.
Oh
okay,
I'll.
This
is
spam
or
okay,
like
just
marking
things,
but
it's
still
a
lot
of
work
out
of
your
day
to
do
that
kind
of
a
transactional
thing,
and
we
really
appreciate
it
because
not
only
it's
not
just
transactional,
but
it's
it's
something
that
helps
us
mold,
the
the
community
into
the
awesomeness
that
it
is
now.
B
Part
of
this
sub
project,
too,
is
contributor
surveys,
people
always
say:
oh
I'm,
not
feeling
that
another
survey-
you
don't
listen
to
me
anyway.
Well
guess
what
that's
not
true
boy.
Do
we
listen
yeah,
and
not
only
do
we
listen,
we
actually
take
action.
Last
year
we
ran
sort
of
our
first
major
one.
We
had
a
over
160
responses.
We
had
like
over
35
questions.
It
was
a
very
in-depth
survey
and
we
got
a
lot
of
really
great
stuff
out
of
it.
B
We've
remoulded
our
community
meeting
on
Thursdays
based
off
of
that
data,
and
we've
done
several
different
things.
Guess
what
winter's
call
me
and
annual
surveys
coming
out
and
we
are
almost
there
after
cube
con-
expect
some
emails
from
contributor
experience
if
you're
on
the
kubernetes
developer
mailing
list,
that's
where
you're
going
to
be
hit.
You'll,
probably
also
read
a
blog
post
about
it
on
career
Nettie's
blog
with
the
goal
of
having
really
pretty
graphs
and
really
awesome
things.
B
B
We
plan
these
events
and
it's
it's
super
super
awesome,
because
I
think
that
our
event
team
is
sort
of
first
of
its
kind
for
open
source
and
the
reason
why
it's
because
we've
modeled
it
off
of
the
release
team
and
the
release
team
within
kubernetes.
Has
this
awesome
shadowing
program
which
I
think
actually
Gwyn
has
a
talk?
Are
they
talking
at
the
same
time
right
now
or
was
that
right
before
this,
okay
catch,
the
recording
of
that
hey,
Gwyn
and
Gwyn
and
lucky
are
talking
about
the
mentoring
shadow
program?
B
That
is
the
release
team
and,
let
me
tell
y'all
the
like
shadow
programs
are
legit
the
best
way
to
like
run
a
mentoring
program
because
you're
already
doing
the
work
people
are
observing.
You
do
the
work.
You
can
even
kick
them
a
couple
of
side,
projects
and
side
tasks,
and
things
like
that.
You
create
these
role
books
and
then,
all
of
a
sudden,
you
have
an
event
lead
or
registration
lead,
a
marketing
lead
and
you've
just
made
yourself
an
event
team
from
like
a
corporate
sense.
B
Other
things
that
I
did
want
to
mention
to
just
even
for
recording
purposes,
just
because
it's
so
important
is
voting
in
Syrian
Committee
elections,
which
we
just
had
one
that's
where
I
was
elected.
Christoph
is
here
as
well.
He
was
elected
Nikita's
here
as
well.
She
was
elected
recently
we're
now
down
to
seven
members.
We
had
an
initial
boost
shop
committee
and
then
we
had
the
first
committee
come
on
and
that
had
13
members,
and
now
we
are
back
to
7,
which
will
have
for
the
remainder
of
the
time
unless
we
change
our
charter.
B
So
we
have
public
meetings
after
cube,
con
I
swear
we're
all
so
tired
and
so
I
just
wanted
to
bring
that
up
and
this
year
I
think
we
had
like
800
members
that
could
vote
so
that
was
really
super
cool.
That
meant
that
we
had
800
people
that
made
more
than
50
contributions
in
the
last
year,
which
means
the
active
ish
right.
A
It's
so
great
now
that
we've
we've
told
you
a
little
bit
about
our
sub
projects.
I
bet
you're
wondering
how
can
I
get
involved
with
this
awesome
important
work
so
I
have
the
answers
for
you.
So
first
come
to
our
meetings.
I
know
everybody
loves
meetings.
We
need
a
great
we're
fun
people,
the
people
in
our
sig
are
fun.
Our
meetings
are
fun.
A
Come
join
our
meetings,
9:30
a.m.
Pacific
time,
second,
be
a
mentor
I'm
sure
everyone
in
this
room
has
had
somebody
that
was
really
influential
to
where
they,
where
they
are
in
their
in
their
career
in
their
life,
help
pay
that
forward
to
to
people
who
are
interested
in
kubernetes,
and
we
have
many
avenues
for
that
as
well,
so
spread
communications
far
and
wide
to
your
contributor
communities.
A
B
Mostly
breaking
changes
on
github
workflows,
please
spread
the
word,
that's
really
where
it's
like.
We
didn't
hear
about
that
change,
and
so
yeah
helping
us
spread
the
word
with
stuff.
If,
like
you're
monitoring
our
mailing
list
and
you're
in
other
SIG's,
go
to
SIG's
and
say
hey,
did
you
hear
that
contribute
experience,
news
I
think
we
should
know
about
that?
That
kind
of
stuff
is
so
key
in
communities.
This
large
I
promise
that,
like
that
in
itself,
is
a
contribution.
If
I
could
give
you
a
github
event
for
it,
I
would.
A
Yeah,
if
you
don't
tell
us
how
you
feel
about
these
changes,
we
don't
know,
and
we
really
need
that
data.
So
that
is
a
gift
that
you
give
us.
So
please
also
use
good
first
issues
and
hop
wanted
labels.
This
is
a
big
project.
Getting
started
is
kind
of
intimidating
flagging
that
those
kind
of
issues
is
super
helpful
and
then,
finally,
we
have
these
teams
that
we're
trying
to
form
we
have
a
triage
team
and
we're
looking
to
start
a
marketing
team.
You
don't
have
to
be
a
marketer
to
be
part
of
the
marketing
team.
A
B
This
wouldn't
be
CN
CF
marketing,
our
creams,
like
ice.
Our
contributor
base
is
so
large
now
and
the
communication
is
so
much
that
marketing
will
help
us
target
communications.
Better,
set
up
cool
automation,
things
that
you
probably
see
with
like
HootSuite
Twitter
accounts,
the
whole
nine
yards
and
then
eventually,
even
like
own,
like
the
contributor
site,
so
really
just
making
us
a
little
bit
more
well
round
and
having
more
support
channels.
B
A
A
A
B
A
B
C
During
our
deep
dive,
we're
going
to
go
through
like
five
or
six
issues
that
we
could
really
use
help
on
things
that
are
slightly
more
technical.
But
we
just
need
people
who
are
willing
to
learn
willing
to
talk
willing
to
walk
through
some
of
these
issues
with
us
and
like
very
specific
things
that
we
could
really
use
help
in
getting
getting
involved
in
our
contributor
workflow.
B
B
Yes,
yep
I
actually
yeah,
it's
sort
of
like
an
outline
of
how
that
should
be
done.
So
yes,
and
no
there's
definitely
like
more
planning-
will
come
with
the
marketing
team
like
more
the
strategy
piece,
but
we
also
I
just
submitted
a
PR,
that's
still
sitting
not
because
of
the
reviewers,
but
because
I
they
made
changes
and
it's
coupon
and
I'm
freaking
busy,
but
there's
a
communication.
B
Dot
MD
file
in
the
community
in
the
community,
repo
that
I
just
completely
revamped
and
essentially
the
plan,
would
be
to
make
sure
that
all
of
those
are
covered
that
they
all
have.
People
who
are
submitting
kind
of
content
to
them
relating
to
contributors
and
I
mean
let's
just
clean
up
at
a
high
level.
B
Like
you
know
some
kind
of
weeklies,
cadence
or
check
you
know
every
once
in
a
while
I
think
we
have
like
a
very
small
number
of,
like
maybe
under
a
thousand
core
contributors
to
check
that
mailing
list,
but
we
have
maybe
over
three
thousand
so
I
feel
like
we
kind
of
only
hit,
maybe
one
third
of
our
contributors
at
any
time
at
best
and
then
that's
when
we
start
kind
of
doing
guerilla.
Marketing
techniques
like
all
of
us,
go
to
SIG's,
but
that's
not
scalable,
because
we
have
40
SIG's
and
working
groups.
B
So
that
means
all
of
us
are
just
literally
doing
keep
doing
columns
for
a
week,
because
all
we're
doing
is
going
into
SIG's.
Like
that's
what
we
did
for
contributor
summit
for
registration,
we
went
into
every
sig
and
hey,
don't
forget,
register
for
the
contributor
summit
and
then
like
we
had
chairs
like
every
week
repeated
that
kind
of
stuff.
So
there
could
be
a
much
more
organized
effort
around
that
I'm
sure
your
corporations
and
businesses
and
stuff
do
coms
and
marketing
like
butter,
so
trying
to
take
in
some
of
that
and
then
open
source.