►
From YouTube: SIG Contributor Experience Intro – Paris Pittman, Google & Elsie Phillips, CoreOS (Any Skill Level)
Description
Want to view more sessions and keep the conversations going? Join us for KubeCon + CloudNativeCon North America in Seattle, December 11 - 13, 2018 (http://bit.ly/KCCNCNA18) or in Shanghai, November 14-15 (http://bit.ly/kccncchina18)
SIG Contributor Experience Intro – Paris Pittman, Google & Elsie Phillips, CoreOS (Any Skill Level)
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 following projects: https://git.k8s.io/sig-contributor-experience/projects.md and have information on how to get involved.
About Paris
Paris is a Developer Relations Program Manager on the Google Cloud Open Source Strategy team focusing on Kubernetes Community. She has 13 years of professional experience in attracting and retaining engineering talent for organizations and open source projects. She has also been organizing communities in one form or another for over 20 years, and at one point ran enough meetups to subsist solely on the free pizza leftovers.
About Elsie
Elsie herds the CoreOS Community and Co-Leads the Kubernetes Contributor Experience SIG. She's a northwest native who got her start in open source working at the Oregon State University Open Source Lab. In her free time she throws wild one woman dance parties and makes a mean vegan chocolate chip cookie.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! 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.
A
B
A
A
B
A
A
B
A
We
definitely
had
to
start
somewhere,
that's
for
sure,
as
you
can
see
in
the
next
coming
slides.
We
work
on
a
lot
I
think
yesterday
and
the
contributor
experience
update
after
we
were
done.
I
had
a
lot
of
folks
come
up
to
me
and
said:
oh
wow,
I
did
not
know
your
save
worked
on
this
much
I'm
like
well,
when
you
have
a
community
of
you,
know,
I.
Think
thirteen
hundred
at
this
point
there's
a
lot
of
contributors
who
have
a
lot
of
needs.
A
So
we
have
a
couple
of
principles
that
are
actually
guiding
us
this
year,
I
initially
called
them
mottos,
but
I
think
these
are
more
principles
and
what
we're
gonna
do
is
go
through
those
based
off
of
the
sub
projects.
We
have
split
up
the
the
special
interest
group
into
sub
projects,
so
it's
different
areas
of
the
community
repo
that
we
own
through
owners
files
and
first
principle,
is
if
it's
not
automated
it
better.
A
Damn
well
be
documented
and
that's
very
important
for
us,
because,
as
we
grew
from
one
individual
sera
Novotny,
who
built
the
community
into
many
different
community
managers
and
also
full-time
engineers
who
helped
us
with
workflow,
we
have
a
lot
of
people
who
do
do
you
know
smaller
tasks
or
one
task
which
leads
us
into
like
achieving
a
spoof
'less
sake.
So
spoof
would,
in
this
case,
would
be
single
point
of
human
failure.
We,
for
instance,
Jorge
Castro,
who
works
at
hep,
do
as
a
full-time
community
manager
at
one
point.
A
What's
the
only
person
that
could
use
our
YouTube
account
and
do
live-streaming
and
things
like
that?
Now
we
have
that
cleared
up,
and
now
we
have
multiple
players
in
the
community
who
are
working
on
many
different
facets
of
of
the
project
growing.
Our
contributors
you'll
also
see
what
the
mentoring
sub
a
project
that
super
important,
that
we
grow
our
contributors
and
I'm,
not
just
talking
about
new
contributors
either.
A
New
contributors
is
just
one
aspect
of
that,
but
we're
really
talking
about
moving
people
through
owners
files
so
that
we
don't
have
any
bottlenecks
and
then,
of
course,
that
all
contributors
should
have
the
same
experience
across
the
board.
And
the
board
in
this
case
would
be
our
many
repos
we're
talking,
60
plus
20
in
incue
bation,
plus
many
others
that
are
related,
like
the
concept
of
kubernetes
cigs
repos.
A
So
the
first
sub
project
that
we
own
that
I
just
mentioned
previously
is
mentoring,
so
we
actually
are
attacking
mentoring
in
many
different
ways.
One
of
them
is
reducing
the
time.
Burden.
I
actually
have
a
talk
in
another
talk
in
two
hours
and
I'm,
giving
a
mentoring-
and
these
are
the
programs
that
we're
in
current
that
are
currently
in
build
stage
right
now.
A
The
first
one
is
the
one
on
one,
our
very
briefly:
that's
just
a
concept
of
one
time:
one
mentor
one
mentee
one
hour
and
this
reduced
that
time
burden
of
oh,
you
always
have
to
meet
with
your
mentor,
and
this
is
actually
pretty
determining
goals.
So
their
goals
would
be
for
the
mentee
to
say
that
they
want
a
code
based
or
they
want
pair
programming,
and
then
we
match
them
up
accordingly,
and
then
we
have
group
mentoring,
which
I
could
talk
a
whole
hour
on,
but
we
don't
have
the
time
for
that.
C
A
For
group
mentoring,
that's
really
playing
off
the
concept
of
peer
mentoring
and
a
four
to
one
ratio
for
being
four
mentees
to
one
mentor,
and
we
essentially
build
the
foundations
of
clear
communication
framework
and
it's
a
three
month
program
at
a
self-paced
semi
structure,
learning
environment
meet
our
contributors
is
a
once
a
month
program,
Carolyn
and
Aaron,
and
several
others
that
are
actually
in
the
room.
Right
now
have
been
on
that
as
mentors,
and
that
is
a
really
quick
way
for
people
to
get
mentoring
type
of
conversations.
Eric's.
A
You
think
questions
addressed
so
there's
been
questions
like.
What's
your
favorite
color,
how
do
I
become
an
approver?
What
are
your
tips
on
which
they
should
I
join
just
very
rapid
kind
of
traffic
kind
of
questions?
Then
we
have
outreach
e
and
google
Summer
of
Code
who
helped
us
with
more
of
a
student
type
of
intern.
Feel
outreach
e
is
also
awesome
because
they
really
they've
really
addressed
the
underrepresented
in
tech
issue,
and
without
addressing
that
in
your
mentoring
programs.
A
Then
you
shouldn't
necessarily
have
a
mentoring
program,
so
we
think
that
that's
highly
critical
for
us
and
then
we
of
course
have
mentoring
at
events.
So
it's
some
cube
cons
and
some
other
events
we'll
do
speed,
speed,
networking
and
speed
mentoring
and
then,
of
course,
there's
a
release
team.
The
release
team
actually
has
shadow
rolls
built
into
that
and
that's
an
awesome
way
to
achieve
a
mentor,
because
naturally,
this
person-
that's
the
first
and
the
role,
for
instance,
like
the
release
lead,
josh.
Burkas
is
actually
here
for
this
release.
A
Hey
Josh
and
so
josh
is
actually
going
to
be
mentoring,
the
shadow
troll
for
that.
So
that's
a
really
cool
way
to
do
succession
planning.
So
for
this
we
actually
need
Mentors
I
will
when
we
upload
the
slides
I'll,
actually
include
the
link
to
the
mentee
mentor
forum.
So
if
anybody
out
here
would
like
to
participate
in
any
of
these
programs,
we
would
love
to
have
you
and
then
also
I'm,
looking
for
folks
to
help
us
automate
with
this
process.
B
So
next
we're
diving
into
to
my
baby
in
the
project
which
is
death
stats,
so
the
Linux
Foundation
graciously
hired
a
contractor
actually
for
us
to
have
this
large
conglomerate
dashboard
put
together.
His
name
is
Lucas
and
he's
done
a
fabulous
job.
I'm
gonna
do
a
soft
plug
in
the
next
slot
of
talks.
There's
an
entire
talk
devoted
to
this.
So
if
you
want
more,
more
of
this
come
check
that
out
in
the
next
hour.
B
Currently
there
are
46
graphs
in
the
dashboard
and
a
subset
of
our
sig
has
been
meeting
once
a
week
to
work
on
pairing
those
graphs
down
and
writing
detailed
descriptions.
So
anybody
can
quickly
look
at
the
graphs
and
understand
what's
going
on
giving
them
names
that
make
a
little
bit
more
sense
and
doing
that
kind
of
work.
B
And
so
we
have
also
recently
set
up
a
system
for
people
who
would
like
to
make
requests
for
changes
or
for
new
dashboards,
and
so
it
is
a
github
project
in
the
repository
and
I've
linked
to
it
right
there,
and
so
people
can
create
card
with
a
thorough
description
of
their
request,
and
that
subcommittee
will
look
at
it,
make
sure
that
it
makes
sense.
And
then,
if
it's
approved,
then
we'll
go
ahead
and
assign
that
issue
to
Lukas.
Who
will
go
ahead
and
do
that
work.
B
B
B
So
how
you
can
help
us
with
this
is
to
go
in
and
look
at
it
and
see
where
we
miss
stuff.
Prs
are
more
than
welcome
and
then
especially
the
reviewer
guide
section.
We
need
help
with
it's
currently
just
tips,
and
so
we
need
help
flushing
it
out
and
making
it
more
hearty.
And
then
another
upcoming
piece
of
documentation
that
we're
working
on
is
the
developer
guide
and
Ryan.
Jarmon
is
heading
that
up
right
now
and
we're
requesting
feedback
May
3rd
at
do
you
know
if
that
time
is
Pacific.
A
A
A
Time
yep
all
right,
then,
of
course
we
are
working
on
many
other
different
kinds
of
contributor
documentation
just
outside
of
the
regular
read
knees,
and
things
like
that
that
you
see
that
other
open-source
projects
have
we're
actually
going
to
be
separating
out
a
lot
of
contributor
information
versus
user
information.
We
realized
that
our
community
is
actually
users
plus
contributors,
which
we
know
that
can
get
a
little
hairy,
especially
when
you're
trying
to
find
information,
and
especially
when
you're
throwing
the
word
developer
around
developer
in
our
case
could
mean
a
current
IDs
developer.
A
That's
at
a
company
and
they're
an
end
user
or
kid
mean
kubernetes,
developer
and
they're,
actually
pushing
code
upstream
and
working
on
like
testing
infra
or
something
like
that.
So
we're
actually
planning
a
new
contributor
web
site.
This
is
going
to
be
spun
off
of
the
kubernetes
io
and
in
its
own
domain,
and
this
will
have
very,
very
contributor,
centric
information,
so
it'll
have
like
a
C
or
sake
updates
that
are
on
YouTube.
It
will
have
all
of
our
developer
guide
information,
contributor,
guide
information
it'll,
essentially
be
a
one-stop
shop
for
contributors.
A
We're
also
toying
with
the
idea
of
having
a
Twitter
a
Twitter
contributor
chat
to
a
Twitter
contributor
channel
and
many
other
contributor
focused
communication
platforms.
We
actually
have
a
cap
in
process
for
that
and
for
folks
who
don't
know
what
a
cap,
it's
a
community,
it's
the
kubernetes
enhancement
proposal,
so
we've
adopted
that
as
part
of
our
decision-making
process
and
that
cap
is
addressing
the
website
and
loved
to
have
feedback
on
that,
so
feel
free
to
go
ahead
and
comment
on
that
issue.
A
Jorge
Castro
is
actually
going
to
be
leading
that
up,
it'll
be
built
on
Hugo
and
then
we've
got
label
documentation.
Aaron's
who's
in
the
audience
has
been
working
a
ton
on
this.
This
is
really
helping
us
with
issue
triage
and
with
just
overall
organization
of
the
project.
I
left
the
the
first
bullet
up,
because
just
wanted
to
give
you
an
example.
A
Some
of
the
conversations
that
we
have
in
contributor
experience,
one
of
which
of
late,
is
the
Help
Wanted
issue,
especially
because
we
have
a
lot
of
new
contributors
that
on
board
frequently
and
a
lot
of
the
feedback
that
we
get
is
that
the
Help
Wanted
label
seems
like
it
is
for
people
who
are
very
experienced
with
the
projects
and
like
a
cig
would
just
need
you
know
another
extra
pair
of
hands
that's
experienced
and
not
necessarily
a
good
starter
issue.
We
at
one
point
in
time
had
a
four
new
contributors
label.
A
If
you,
a
member
of
our
mailing
list,
you'll
see
that
we
have
a
lot
of
conversations
around
issue
hygiene
and
excuse
me
and
labeling
as
well,
and
we've
set
some
guidelines:
asada
EV,
Susan
who's.
In
the
audience
has
has
done
a
lot
of
great
work
with
us.
Thanks
thanks
thought
of
take
a
look
at
those
guidelines
and
we've
been
thinking
about
adopting
those
across
the
worg.
B
B
A
I
can't
overemphasize
actually
the
last
bullet,
which
is
the
feedback
piece,
because
the
project
is
so
large
that
some
folks
may
miss
our
conversations
about
LG
TM,
for
instance,
I
feel,
like
we've,
been
having
this
conversation
for
six
months.
At
this
point,
however,
some
people
in
the
in
the
org
or
still
are
just
now
hearing
about
this
and
come
to
us
and
say
why'd.
You
change
my
workflow,
even
though
we
may
have
already
gone
through
like
a
lazy
consensus
process
which
is
laid
out
in
our
Charter.
A
A
Our
next
slide
arcs
not
slide.
Our
next
sub
project
is
the
community
management
element,
and
many
of
you
may
be
familiar
with
some
of
the
activities
that
we
do
here,
because
these
are
more
of
our
visible,
visible
projects.
If
you
will,
first
and
foremost,
is
slack,
we
we
don't
technically
own
slack,
C
and
C
F
does,
however,
we
own
the
moderation
of
it
as
well
as
carrying
out
some
of
the
policies
and
procedures
that
we've
laid
forth.
A
We
did
recently
create
a
slack
moderation
guidelines,
so
you
can
see
that,
but
just
to
give
you
sort
of
a
sense
of
how
big
slack
is
we
have
thirty.
Five
thousand
people
on
our
slack
I
was
in
I
feel
like
I
was
in
a
talk
a
while
ago,
where
somebody
said:
oh,
six
thousand
people's
and
our
slack
and
that's
so
huge
and
like
whoa
Oh.
Ours
must
be
gigantic,
but
it's
really
it's
really
cool.
A
We
have
about
four
four
active
moderators,
only
four
35,000
people,
so
that's
that's
awesome
and
we
have
about
160
or
actually
170
I.
Think
at
this
point,
the
last
time
of
the
analytics
channels.
We
don't
keep
private
channels
unless
they're,
unless
they
have
to
do
with
code
of
conduct,
issues
or
mentoring,
so
very
creating
very
safe
environments,
but
we
do
not
allow
for
private
channels
in
other
ways,
mailing
lists.
We
actually
are
about
to
take
over
the
ownership
of
this,
and
this
is
has
to
do
with
the
single
point
of
human
failure
principle
right
now.
A
We
have
a
few
veterans
if
you
will,
of
the
project's
first,
first
and
foremost,
Brian
grant,
who
technically
owns
a
lot
of
our
mailing
lists.
So
contributor
experience
is
going
to
be
taking
over
the
ownership
of
this,
which
will
be
very
similar
to
like
our
slack
Administration
guidelines,
George
cash
or
actually
just
threw
together
a
moderation
catch-all
guidelines
for
us,
that's
going
to
supersede
the
slack
ID
lines,
so
we
put
into
place
so
that
we
can
have
all
of
our
communication
platforms
running
on
the
same
moderation
guidelines.
A
So
again
that
would
be
kubernetes
development
and
kubernetes
users.
Those
are
just
the
shorthand
of
those.
We
also
run
the
weekly
community
meeting
that
most
of
you
are
probably
familiar
with
that
happens
on
Thursdays
in
the
morning.
These
are
running
pretty
smoothly
at
this
point.
I
think
we've
got
this
down
to
a
well-oiled
machine,
with
the
exception
of
we
want
to
make
some
possible
adjustment
to
the
demos
we
also
participate
in
road
shows
for
contributor
experience.
Specifically.
This
is
our
first
time
that
we
did
at
this
quarter.
A
We
are
looking
at
other
forms
of
communication,
especially
other
platforms,
whether
that's
to
replace
flack,
whether
that's
to
replace
Google
Groups.
Who
knows
at
this
point.
But
what
we
know
is
that
we're
give
discourse
a
test
run
and
we
actually
have
a
cap
in
for
that
and
George
is
going
through.
The
motions
of
the
cap
as
well
as
the
test,
and
the
test
is
going
to
be
a
three
month
period
on
discourse
and
see
what
kind
of
activity
that
we
can
get
there
and
to
kind
of
compare
and
contrast
what
we
currently
have
already.
A
What's
this
me
or
you,
this
is
you
okay
and
then
we
also
have
events
higher
here,
and
these
are
updates
deep
dives.
But
then
you
also
have
contributor
summit,
and
then
we
also
have
things
like
speed,
networking
and
mentoring
that
I
mentioned
earlier
in
the
mentoring
side,
but
just
kind
of
any
event,
that's
geared
towards
contributors.
We
probably
place
at
least
some
part
in
that,
if
not
full
ownership
of,
and
just
to
kind
of
give
you
a
really
cool
data
point.
A
So
what
are
we
looking
for?
What
are
we
looking
forward
to
in
the
future?
Again
the
communication
platforms?
We
would
like
to
get
a
better
strategy
around
this.
We
know
that
we're
kind
of
in
this
inundated
state
of
oh,
my
gosh.
We
have
too
many
communication
platforms.
I
mean
I,
have
a
list
right
now
going
I
think
it's
about
20
that
we
all
monitor
in
some
sense,
whether
it's
Twitter
reddit
slack,
like
45,
mailing
groups
or
mailing
lists.
Zoom
calls,
which
are
our
weekly
updates.
I
mean
you
name
it.
A
We
are
probably
on
it,
and
that
is
if
that's
kind
of
crazy
for
us
as
as
chairs
and
leads,
and
members
of
this
sake,
that's
most
likely
crazy
for
the
rest
of
our
community.
So
we're
gonna
be
really
looking
to
iron
those
things
out
at
some
point
and
then,
of
course,
we're
going
to
be
looking
to
scale
the
new
contributors
workshop
that
we
had
yesterday.
A
A
Half
of
them
are
already,
but
going
on
a
mentoring,
drive
and
really
just
getting
some
data
around
what
works
and
what
doesn't
and
then,
of
course,
complete
mentoring
issues
may
complete
contributor
documentation.
So
this
because
this
may
include
videos.
We've
got
this
concept
going
going
around
right
now
about
doing
contributor
videos
kind
of
like
the
just
for
funk
if
anybody's
familiar
with
golang
and
and
taking
that
one
step
farther.
But
as
Elsie
mentioned
earlier,
with
the
developer
guide
and
the
complete
contributor
guide,
we
should
be
pretty
much
set
there
so
get
involved.
A
We
need
all
the
help
we
can
get.
We
actually
have
a
very
active
cig,
I'd,
say
roughly
15
active
contributors
about
20
about
200
folks,
who
will
either
way
in
chime
in
in
some
some
fashion.
Here's
our
many
different
ways
to
reach
out
to
us.
Send
me
a
pigeon
at
Google,
I'll,
find
it
and
try
out
Help
Wanted
issue,
we're
also
in
the
process
too,
of
taking
in
our
own
medicine,
of
what
we're
trying
to
dish
out
with
Help
Wanted
as
well,
so
feel
free
to
give
that
a
spin.
Any
questions
Karen.
D
D
A
Yeah
no
I
mean
that
that's
the
that's
the
exact
issue
that
we're
trying
to
tackle
now
and
that's
why
we've
been
trying
to
do
like
the
road
shows
and
things
like
that.
We're
really
trying
hard
to
make
it
so
that
the
contributor
has
a
very
similar
experience.
We
know
in
some
cases
that
it's
not
going
to
be
the
exact
experience
for,
for
you
know
whatever
you
know,
technology
reason
you
know
insert
here,
but
we're
working
on
that
and
that's
that
use
case
right.
A
There
is
exactly
what
drives
us
to
do
that,
because
we
want
you
to
contribute
to
other
facets
of
the
project,
but
definitely
you
know.
Maybe
we
can
talk
offline
about
some
of
the
ways
that
it's
extremely
different
and
then
work
with
your
sig
and
in
getting
engaged
in
helping
to
make
that
smoother
of
a
process.
Yeah.
C
C
C
C
A
You're,
that's
actually
a
rare
story.
I'm
not
gonna
lie
like
it's.
That's
rare
Aaron.
You
agree:
yeah
yeah,
that's
rare
yeah!
No,
no!
It's!
It's
rare
because,
usually
you
need,
like
a
sake
label
to
even
get
attention
on
your
PR
and
that's
what
the
label
definitions
at
Aaron's
talking
about.
That's.
Why
he's
getting
so
passionate
right
now?
And
we
hear
from
many
many
new
contributors
that
their
PRS
never
get
looked
at
and
and
that's
because
they're
not
necessarily
contacting
the
right.
People
are
knowing
the
right
avenues,
so
you
clearly
hit
a
sweet
spot.
A
Your
code
is
a
plus
yeah
yeah
that
got
to
but
yeah
you
knew
kind
of.
You
may
have
already
been
an
open
source
enough
to
kind
of
know
who
to
target
exactly
and
a
lot
of
our
contributors
that
I've
encountered.
This
would
be
their
first
time
contributing
to
open
source
period
so
and
then
they're
coming
into
our
large
huge
testing
and
front
environment,
that's
very
different
than
ours,
or
than
most
so
that's
another
kind
of
hurdle
that
they
have
to
get
over.
So
one
Congrats
on
that
PR
acceptance
and
and
number
two.
A
D
A
Yes,
yes,
yep,
and
this
also
has
to
do
with
education
as
well,
so,
but
the
more
people
like
yourself
that
can
help
us
push
the
help
us
push
these
communications
the
better,
because
right
now
all
we're
seeing
is
the
people
of
contributor
experience
that
are
pushing
these
and
cigs
and
not
necessarily
the
cig
members
themselves.
So
we
really
need
to
change
that
change
that
narrative.
It
would
be
really
helpful
if
we
had
almost
contributor
experience
advocates
in
everything
that
we
have
and
to
give
folks.
A
Yes,
please,
yes,
I
think,
yes,
we
even
have
claps
back
there
from
Gwen
and
it's
important
that
we
figure
out
a
way
to
communicate
better
within
this
environment
and
I
think
the
only
way
to
do
that
is
through
advocacy
because
it
works,
and
it's
really
the
only
way
we're
gonna
get
our
message
across.
Just
because
again,
you
know
how
many
PRS
and
issues
and
emails
and
alerts
and
slack
messages
and
stuff
you
get
just
from
a
Service
Catalog
perspective,
not
even
necessarily
from
like
the
holistic
project
perspective.