►
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 - Paris Pittman, Google & Elsie Phillips, Red Hat
We will be covering what contributor experience is, how we help the project, the projects we are current working on (if the talk were today: mentoring, automated workflows, new contributor onboarding, communication pipelines, etc.), and how folks can get involved
To Learn More: https://sched.co/GrcT
A
B
So
sync
planning
this
is
the
stuff
that
we
as
a
thing
in
its
various
chairs
and
tech
leads,
do
from
a
strategy
perspective.
Okay,
so
we
are
so
close
right
now
to
merging
a
charter.
I
feel
like
we've,
never
been
close
on
the
key
armors
in
our
life.
At
this
point,
the
Charter
is
significant
that
I
wanted
to
bring
out
now.
This
is
something
that
the
steering
committee
has
said
that
all
of
our
special
interest
groups
need
the
Charter,
really
defines
our
scope.
B
We
also
created
a
project
board.
We've
also
been
doing
a
lot
of
management
related
activities.
There
are
so
many
projects
that
are
going
on
right
now
and
contributor
experience.
It's
super
critical
that
we
figure
out
a
way
to
to
really
put
this
all
together,
so
that
we
can
communicate
out
better
what
we're
doing
and
also
close
in
the
feedback
loops
and
also
really
give
out,
rewards
and
recognition
for
our
contributors
that
are
doing
hard
work
here.
Some
of
them
are
paid
full
time.
B
Some
of
them
are
not
so
I
think
it's
very
important
that
we
do
some
kind
of
reward
and
recognition
and
I
think
that's
going
to
actually
stem
from
us
having
better
project
management,
so
I'm
just
gonna
go
ahead
and
skip
down
to
that
next
bullet.
We
actually
put
out
a
roll
recently
on
our
new
contributor
roll
board,
which
I'll
get
to
in
a
second,
but
this
is
just
a
call
out
for
volunteers
who
want
to
take
on
this
kind
of
project
management
responsibilities.
We're
thinking
like
launch
timelines
things
along
that
line.
B
9
a.m.
in
the
somebody
do
UTC
maths,
yes
before
I
am
something
like
that
UTC
we
did
that
because
we
do
realize
that
we
are
awarding
contributors
from
outside
of
the
United
States
and
we
should
be
friendly
to
them.
So
we
can
hear
their
feedback
so
that
we
can
close
and
open
those
feedback
loops
from
a
global
perspective
and
briefly
we're
just
going
to
be
doing
a
face
to
face
meeting
in
2019.
So
look
out
for
that,
so
we're
gonna
break
this
down
by
some
projects.
B
Some
projects
are
sort
of
like
programs
that
you
just
think
that
each
state
has,
in
this
case
the
sway
the
mentoring
other
SIG's
have
things
are
very
specific
to
code.
So
it's
a
certain
parts
of
the
code
base
that
they
own
and
the
projects
that
involve
with
that
that
certain
code
base.
This
again
is
mentoring,
so
we
are
doing
so
much
work
with
trying
to
think
of
ways
where
we
can
and
hence
the
the
contributor
onboarding
experience,
both
from
a
new
and
current
contributor
perspective.
B
We
do
have
a
lot
of
casual
contributors
and,
if,
like
me,
one
and
two
and
interesting
a
handful
of
contributions,
so
how
do
we
make
their
own
voiding
experience
centers
so
that
they
want
to
remain
active
with
the
group?
So
all
of
these
mentoring
programs
that
we've
created
or
that
are
in
flight
or
what-have-you
answer
a
lot
of
those
different
personas.
C
B
They're
all
very
creative
in
the
sense
that
we're
looking
out
for
our
contributors
time
time
we
think,
is
a
killer
and
mentor
programs.
We
just
did
a
survey
recently
and
it
was
something
very
very
high.
I
think
was
like
I.
Don't
have
the
number
of
top
of
my
head,
unfortunately,
I
think
was
about.
40%
number
said
that
they
just
don't
have
the
time
to
mentor
and
that's
really
unfortunate,
so
we
are
going
to
hopefully
create
these
programs
that
will
alleviate
some
of
that.
One
of
them,
and
my
favorite
right
now
is
meet
arbitrators.
B
New
York
contributors
is
a
monthly
of
web
series
that
we
have
on
YouTube
and
that
has
anywhere
from
75
to
200
plus
views
a
month
and
people
come
on
who
are
heard
of
strength
contributors,
so
we're
between
three
to
six
and
they
answer
questions
that
people
would
normally
ask
a
mentor.
So
things
like,
what's
your
advice
for
me
on
getting
to
an
approver,
and
this
thing,
what
is
your
advice
to
me
for
pickiness
thinning?
Why
is
my
test
flaking?
What's
your
favorite
color,
it
really
just
depends
like
that's
the
relationship.
Some
people
want
to
build.
B
So
we
give
it
to
them:
that's
kind
of
scalable
mentoring,
so
we're
cutting
out
that
link
timer
and
like
the
ambiguous
goal
setting
and
everything
like
that
and
just
giving
people
what
they
need.
I've
noticed
in
kubernetes,
especially
that
as
long
as
we
get
the
new
contributors
into
their
first
PR
they're,
usually
pretty
good
at
navigating
the
of
it,
and
then
once
we
get
the
current
contributors
on
board
with
the
membership
process
and
why
they
should
go
up
the
ladder
in
the
membership
process.
They're,
usually
pretty
bored
too.
B
So
it's
like
I
think
we
need
to
just
get
better
at
educating
those
things
and
that's
this
is
where
these
these
programs
colleges.
So
we
also
have
the
one
on
one
our
in
group
mentoring.
Both
of
these
programs
are
very
new
concepts.
Open
source
I've
worked
with
them
in
other
businesses,
my
past,
in
some
kind
of
format,
but
the
one-on-one
mentoring
is
sort
of
like
traditional
mentoring
in
the
sense
where
you're
going
to
get
matched
with
someone.
B
B
Or
do
you
want
a
pair
of
program
doing
an
AMA
which
is
a
little
bit
more
ambiguous
than
the
mentor
at
least
knows,
and
it's
going
to
be
ambiguous
so
the
never
days
on
the
same
page
and
then
that
also
alleviates
the
mentors
looking
for
it.
Also
alleviates
like
the
mentors
against
like
need
to
feel
like
they
have
to
always
communicate
with
their
mentee.
B
So
it's
just
because
it's
already
been
established
upfront.
It
just
one
time
one
shot
anyway.
So
it's
one
time
one
shot
with
a
maintainer
for
one
hour
and
then
group
mentoring,
really
TLDR,
experiment,
Orion
and
I.
Think
a
lot
of
us
get
large
benefit
from
seeing
your
peers
and
finding
their
experiences
and
then
also.
This
is
also
another
one
where
we
preset
their
goals
ahead
of
time.
So
if
your
tips,
we
take
ten
people
who,
let's
say
look
the
test
that
we
ran,
was
ten
members
to
two
reviewer
and.
B
So
ten
members,
two
reviewers
and
three
months
and
we
took
three
mentors
and
we
put
them
in
a
pro,
a
private
slack
channel
so
that
they
could
have
like
a
safe
learning
environment
where
they
didn't
feel
like
they
were
going
to
be
minted
and
they
taught
them
code
review
skills.
At
the
end
of
the
three
months,
we
had
six
people
graduate
in
two
owners
files
and
it
was
really
wonderful
to
watch
them
kind
of
grow
together
and
it's
very
interesting.
So
the
both
of
those
things
are
actually
in
a
testing
phase.
B
There's
a
lot
of
administrative
things
that
needs
to
get
worked
out,
especially
with
the
one-on-one
our
how
we
talk
to
each
other
about
our
time.
Availability
like,
for
instance,
like
it's
very
hard
to
get
people's
availability
these
days
and
calendars
are
very
hard
and
there's
no
81
API
solution.
That's
going
to
allow
us
to
look
into
your
availability,
just
laughing
he's
been
working
on
this.
For
months
with
me,
we
tried
doodle,
we've
tried
so
many
creative
things
on
like
how
can
we
make
it
so
easy
for
you
to
go?
B
B
Ii,
which
is
really
hitting
another
market
for
us,
which
is
fresh
perspectives
and
fresh
perspectives,
meaning
maybe
folks
that
aren't
necessary
in
the
kubernetes
world.
Yet
who
want
to
hear
one
and
who
want
to
and
have
a
cycle
and
being
an
open-source
contributor
I'm,
not
gonna,
go
too
far
into
google
Summer
of
Code
I.
B
Today
we
had
a
meeting
and
he's
gonna
split
it
into
two
different
kinds
of
her
sonís
he's
gonna.
Do
an
upstream
developer
for
kubernetes
and
he's
gonna.
Do
a
kubernetes
developer
building
on
top
of
it.
So
so
we're
gonna
break
it
down
and
and
hopefully
like
clear
up
some
of
that
ambiguity
there
and
then,
of
course,
few
comments
being
networking
and
new
contributor
workshops.
Speed
networking
allows
us
to
have
all
of
you
here
in
this
place
already.
So
it's
not
too
much
of
a
time
garden
out
of
you.
B
If
you're
already
here,
you
might
as
well,
do
it
kind
of
an
attitude.
So
that's
that
new
contributor
workshops
we're
actually
going
to
hit
in
a
second
with
LLC's,
with
LC
review
and
new
contributor
playground.
The
best
thing
that
I
want
to
have
as
a
takeaway
here
is
to
please
spread
the
word
about
this
stuff.
B
A
Okay,
as
Paris
mentioned,
we
have
a
new
contributor
playground,
so
I
know
that
when
I
was
make,
my
first
contribution
to
the
kubernetes
community
I
was
really
intimidated.
The
community
has
some
unique
processes
that
are,
they
can
be
really
emitting
from
the
outside,
and
so
we
wanted
to
help
address
this,
and
so
we've
recently
rolled
out
this
playground
to
do
that.
It
lets
people
will
test
out
CI
and
the
owners
files
before
they
make
their
first
contribution
to
give
them
that
confidence.
A
B
A
It's
okay,
good!
You
go
yeah!
So,
as
Barry
said,
we're
always
happy
I'm,
a
contributor
guy.
We
have
a
really
good
foundation
for
it
right
now,
but
as
always,
this
is
an
open
source
community.
So
it's
a
living
document.
Please
poke
holes
in
it
and
review
it,
we're
as
no
documentation
for
open
source
testico
still
very
quickly,
and
so,
if
we
can
get
some
help,
keeping
it
up
to
date,
that
would
be
wonderful,
the
contributor
site.
A
A
B
All
right
community
management
I
really
think
that
this
is
a
a
large
part
of
our
sake.
If
this
is
a
lot
of
our
transactional
work,
a
lot
of
our
communication
pipelines,
events
and
things
like
that,
we're
definitely
not
gonna
I
mean
we
can
do
a
whole
hour,
I
think
on
this
topic.
So
let's
get
started
so
communication
is
sort
of
the
sub-project
sub-project.
B
Not
really
don't
quote
me,
but
like
that's,
how
I
look
at
it
in
my
head
of
community
management
and
we
realized
that
the
community
at
this
point
is
so
so
large
that
we
really
need
to
work
on
a
sort
of
a
communication
roadmap.
If
you
will,
because
we
do
have
so
many
channels,
we
just
recently
did
an
inventory
of
them
and
we're
talking
like
over
a
hundred
google
groups
slack.
It's
like
I
think
we're
like
50/50
actual
platforms
that
we
use
all
of
them.
We
moderate.
We
do
moderation,
guidelines,
it's
a
extent.
It's
definitely
extensive.
B
So
with
that
said,
we're
trying
to
figure
out
a
how
to
reduce
that
toil
B,
how
to
better
document
that,
and
that's
all
inflate,
as
you
can
see
from
a
lot
of
this,
a
lot
of
the
stuff
up
here.
Some
of
the
other
things
that
we
modify,
that
we
moderate
is
zoom
and
YouTube.
This
is
really
how
how
kubernetes
is
so
transparent,
because
all
of
these
meanings
that
we
have
are
indeed
on
YouTube
and
things
along
those
lines.
A
Pert,
so
a
huge
thank
you
to
him
so
why
we
rolled
this
out
was
we
realized
that
slack
is
a
little
bit
of
a
walled
garden.
You
can't
really
surface
a
lot
of
the
knowledge
in
slack
via
search
engine
until
we
needed
something
to
bridge
the
gap
between
our
mailing
lists
and
Stack
Overflow,
and
we
really
saw
that
this
is
where
discus
could
fit
in
for
us
and
so
definitely
go
check
that
out
and
participate.
B
B
C
B
Kubernetes
developer
development
or
actually
just
kubernetes
dev
at
Google,
Groups
comm,
that's
sort
of
the
main
artery
of
the
project
as
a
relates
to
decision
on
a
mailing
list
is
concerned
for
all
contributors.
Saints
have
their
mailing
list.
16
software
church
groups
working
groups
of
our
mailing
list
or
WGS,
as
some
people
refer
them
to,
and
then
we
also
a
slack
that
we're
going
to
be
using
utilizing
more
and
hopefully,
maybe
you
in
some
automated
ways.
The
blog
we're
probably
saying
above
are
separate
Twitter
as
well.
B
Next
and
then
events,
this
is
definitely
one
of
the
larger
transactional
things
of
our
group.
Yesterday,
I'll
get
to
the
last
one,
just
because
it's
so
fresh
yesterday
we
hosted
or
some
may
actually
it's
now
a
1.5,
a
event.
Sunday
we
hosted
our
contributor
summit
and
we
had
roughly
I
think
370
folks
sign
up.
320
show
108
on
the
wait
list
and
we
broke
it
down
into
35
sessions
and
it
was
a
awesome
day.
We
are
hoping
to
continue
that
in
next
year
and
we're
actually
poking
a
box
of
what
else
he
mentioned.
B
The
new
contributor
workshop
at
all
of
the
events
were
a
little
bit
uncertain
as
to
what
we
want
to
do
for
the
other
events,
as
it
relates
to
an
all
attending
contributors
on
it.
I
mean
at
this
point
in
time,
I
think
we
just
don't
have
the
staff
volunteer
or
paid
to
do
full
summits
all
year
round
for
meetings,
Shanghai,
Europe
and
North
America.
B
We
help
to
do
steering
committee
elections,
so
that
happens
every
year.
I
don't
want
to
show
of
hands,
but
like
how
many
of
you
voted
like
it's
definitely
vote.
This
is
something
that
we
take
care
of
the
steering
committee
again
LC
mentioned
the
meeting
or
servicing
operational
arm.
The
Syrian
Committee
were
to
say,
set
the
governance.
We
do
the
thing
and
that's
it.
Next
year
the
steering
committee
actually
reduces
down
the
seven
from
thirteen.
B
They
had
a
boot
shop
steering
committee
when
they
form
so
next
year
will
definitely
be
an
interesting
year
for
us
as
far
as
elections
are
concerned,
so
watch
out
for
that,
oh
and
shouts
to
George,
Castro
and
a
or
wherever
he
is
oh
he's
here
for
helping
us
out
with
running
that
election
last
night.
Okay
and.
C
C
Friction
points
year
over
year
that
we've
been
working
on
this
year
is
to
have
you
know
we
have
a
hundred
and
seventy
or
so
repositories
now
across
13,
github
words
and
across
all
of
that
that
spends.
We
want
our
contributors
to
have
a
consistent
experience
when
opening
up
a
PR
understanding
like
the
steps
they
need
to
go
through
to
take
their
PR
from
code
they're
submitting
to
actually
getting
merged
into
that
repo.
C
We
formed
to
to
do
that.
We
in
the
last
year,
we
formed
a
github
administration
team
that
we
mapped
with
trusted
contributors
from
around
the
community
who
are
able
to
take
action
on
on
kind
of
a
more
a
more
level
basis.
Previously,
it
was
mostly
a
bunch
of
legacy
Googlers
who
had
this
this
high
level
of
access
to
things,
but
we
wanted
a.
C
We
want
the
community
dome
this
Prost,
so
we
have
a
team
now
of
contributors,
that's
able
to
process
requests,
create
repos
and
offer
kind
of
a
support
experience
to
to
those
who
are
trying
to
get
things
done
to
get
them.
We
also
have
started
automating
a
bunch
of
art
of
our
tasks
so
that
things
like
you
know
a
basic.
C
Time
is
inviting
new
members
to
our
organization,
so
we
have
developed
some
automation
around
that
to
our
membership
into
the
cuvette.
Zorak's
is
defined
in
gala
files
in
I
get
hungry,
follow
along
with
basically
everything
else
we
do,
and
we
have
to
have
a
process
hello
to
Bob
and
Steven
who
helped
us
kind
of
process.
Those
membership
requests
provide
the
friendly
face
to
new
equipment
coming
in
and
then,
but
the
actual
work
of
inviting
people
to
the
org
is
now
done
by
odd.
C
So
we
kind
of
delegate
out
things
that
were
previously
privileged
tasks
to
the
communities
the
community
may
have
all
of
those
of
those
procedures
in
the
next
year.
We're
looking
more
at
doing
doing
more
automation,
doing
more
around
that
that
consistent
experience
around
the
repos
and
continuously
improving
that
us,
as
Paris
mentioned
and
in
particular
a
friction
point
right
now-
is
cherry-picking
taking
taking
a
piece
of
code
that
we've
got
in
a
master
but
actually
cherry-picking
it
back
to
branches.
C
A
A
Take
us
home
we're
gonna
talk
about
my
baby.
Does
death
in
the
interest
of
time?
I'm
just
gonna
go
through
this.
So
in
the
last
year
we've
made
a
lot
of
improvements
to
deaf
status.
It's
making
it
more
usable
for
the
wider
community,
but
specifically
the
chairs
and
tech
needs
to
do
this.
We
started
out
by
pruning
some
of
the
less
used
grafts
and
then
grouping
them
into
four
groups
to
make
them
more
discoverable
to
the
wider
community.
A
Actually
based
off
of
this
data,
it
has
informed
our
sink
in
creating
a
that
additional
meeting
time
in
Asia,
because
that
localization
data
told
us
that
we
had
a
significant
contributor
base
in
Asia
and
that
we
needed
to
start
becoming
more
friendly
to
that
group
in
the
new
year.
We're
planning
on
flushing
out
the
user's
guide
that
we
started
a
couple
of
months
ago.
A
We
would
really
like
to
create
a
guide
that
really
lays
out
for
leads
how
to
use
the
dashboards
and
their
decision-making
processes
like
a
really
like
a
top
five
graphs
for
running
your
safe
right
now.
We
know
that
there
are
a
lot
of
graphs
and
it
can
be
kind
of
overwhelming,
and
so
we
think
that
that
guide
will
really
help
with
that.
We
also
want
to
make
the
site
more
vocal,
friendly.
A
Difference,
of
course,
being
that
good
first
issues
for
people
that
have
never
contributed
and
are
looking
for
their
their
entry
into
the
pool
and
that
for
the
help-wanted
levels,
those
are
for
people
that
are
a
little
bit
more
experienced,
and
then
we
also
host
on
the
roll
board.
As
Paris
mentioned,
we
recently
posted
for
a
project
manager
Club.
If
you
want
to
do
that
for
us,
we
would
love
that.
A
We
are
going
to
continue
to
try
and
help
the
chairs,
but
the
chairs
to
do
at
the
end
of
the
day,
have
a
responsibility
to
upload
their
meetings,
to
YouTube,
to
fix
their
zoom
settings
and
to
continue
to
give
the
community
updates
in
the
Thursday
meetings
and
then,
of
course,
file
issues.
When
you
see
problems
where
to
find
us,
you'll
find
us
on
what
our
Wednesday
weekly
calls
and
then,
of
course,
the
fourth
Wednesday.
We
have
that
Asia
Pacific
friendly
time.
You
can
find
us
in
the
contributor
experience,
watch
Channel
and
on
the
mailing
lists.