►
From YouTube: Deep Dive: Contributor Experience SIG - Elsie Phillips, Red Hat & Paris Pittman, Google
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
Deep Dive: Contributor Experience SIG - Elsie Phillips, Red Hat & Paris Pittman, Google
Join us for a live session of the weekly contributor experience meeting! Meet members of the SIG in person and learn how you can contribute. Check out the agenda [here] (https://docs.google.com/document/d/1qf-02B7EOrItQgwXFxgqZ5qjW0mtfu5qkYIF1Hl4ZLI/edit)
https://sched.co/MPjE
A
All
right
I
got
a
mic:
yay
hi
I'm,
Carol,
Chen
I
work
for
Red
Hat
I'm,
the
anvil
community,
/,
Event,
Manager
and
recently
I'm,
starting
to
learn
about
kubernetes
operators
with
ansible,
so
I'm
interested
to
learn
more
about
either.
You
know
joining
more
about
the
kubernetes
community
and
also
the
CEO
of
how
you
see
here,
sell
things.
C
D
F
H
J
L
L
M
N
O
P
F
P
So
you
can
ask
hey,
you
know
how
do
I
sign
the
claa
cuz?
That
always
seems
to
be
a
problem.
You
know
so
any
kind
of
contributor
related
I
want
to
help,
but
I
can't
or
I
want
to
help
but
learn
more.
We
try
to
do
that
and
meet
our
contributors
and
we
run
at
the
same
time
the
first
and
Thursdays
every
month
to
get
people,
consistency,
Wednesdays,
that's
what
I
said
right.
Okay,
my
bad!
P
We
should
probably
put
a
link
in
the
notes
on
where
they
can
find
the
calendar,
because
all
these
things
are
on
the
community
calendar
and
it's
not
so
obvious
where
to
find
the
community
calendar,
and
then
we
do
a
community
meeting
every
Thursday.
That
is
also
open
to
everybody
in
the
project
and
these
cigs
rotate
in
and
they
give
status
reports
of
what's
happening
in
the
project,
cuz,
it's
impossible
for
one
person.
P
So
that's
the
meeting
where,
if
you're
in
a
sick
and
kind
of
doing
what
you're
doing
you
find
out
what's
happening
in
other
SIG's,
we
do
release
announcements,
we
do
hey.
You
know
we
turn
on
a
new
bit
of
github
automation
and
make
your
job
a
little
bit
easier.
We
do
a
cap
of
the
week,
the
what
oh
we
do
a
demo,
so
we
ask
people
from
around
the
community
if
they
want
to
do
a
demo
for
the
core
developers,
they
get
ten
minutes
and
we
keep
that
all
open-source
and
up
screamish.
P
P
Yes,
yes,
so
I
published
a
notes
on
the
forums
every
week,
but
they're
the
raw
notes
that,
like
we
didn't,
do
a
good
job
taking
and
then
Noah
takes
that
in
turns
like
that
into
humans,
and
that's
called
usually
Josh
and
Noah.
Do
a
newsletter
called
this
week
last
week
in
kubernetes
development,
which
is
also
a
blog
lkw
d
info
yeah,
and
they
basically
translate
all
the
stuff
that
happens
in
the
community
meeting
for
the
rest
of
us
to
understand.
P
O
O
O
Q
Q
It
was
a
little
hard
to
find
yes
and
I.
Think
that's
a
common
theme
across
this
entire
conference
here
that
things
are
hard
to
find,
especially
diet,
coke,
apparently
so
on
Monday
we
had
over
300
people
registered
for
a
contributor
summit
that
is
new
and
current
contributors.
We
had
roughly
a
hundred
and
thirty
new
contributors
registered.
Not
everyone
could
come,
of
course,
as
we
did
have
some
drop
off,
but
we
led
and
have
two
great
workshops.
Q
One
for
people
who
were
new
to
github
new
to
open
source
in
general
had
never
contributed
to
an
open
source
project
before
so.
Kubernetes
was
essentially
their
first
open
source
project
that
they
contributed
to.
That
was
Tim,
pepper,
who
led
that,
and
then
we
had
a
201
session
that
gwynevere
over
here
led
for
people
who
were
knowledgeable
about
github
and
had
contributed
to
open
source
projects
before
so
yeah.
We
got
a
lot
of
new
contributors
through
that
event,
and
we
also
had
new
contributors
were
roughly
130
people
registered
I'm.
Not
yes,.
Q
Q
J
So
two
very
recent
things
that
we've
done
as
far
as
github
automation,
stuff.
We
turned
on
I
think
like
a
week
ago.
No,
actually
these
were
both
within
the
last
week
that
we
turn
about
two
new
features
on.
So
the
first
feature
that
we
turned
on
was
github
review
statuses.
So
if
you,
if
you
have
like
about
say
maybe
four
months
ago
or
so,
if
I
remember
it
correctly,
github
rolled
out
a
feature
that
you
can
set
a
status
on
your
github
profile
and
you
can
indicate
you
could
set
like
a
little
status
message.
J
The
that
basically,
is
just
a
flag
that
when,
when
the
blunderbuss,
which
is
one
of
the
the
automation
plugins
that
that
handles
that
when
it
goes
to
say
like
hey,
you
are
the
next
person
kind
of
in
line
to
get
assigned.
Oh
I'm,
detecting
that
you
are
unavailable.
I'm
just
gonna,
go
to
next
in
the
list.
Questions.
J
Get
github
is
fantastic,
it
is
a
github.
Get
up
is
a
fantastic
product
at
the
scale
that
kubernetes
is
using.
It,
though,
there's
a
lot
of
gaps
that
we
have
to
bridge
and
the
we
this
is.
This
is
an
example
of
where
we
can
take
a
get,
a
feature
that
github
has
rolled
out
and
gives
us
that
piece
of
information.
So
there
is
a
there's,
a
UI
element
that
you
would
go
into
your
github
profile
and
set
what
your
status
is.
J
Now
we,
our
bots,
can
just
consume
that
when
we're
doing
the
rapid
automation
around
things
like
assigning
out
reviewers,
we
can
use
that
piece
of
information
to
better
assign
out
reviewers,
which,
both
from
a
like
the
health
of
a
reviewer
standpoint.
It
allows
people
to
take
steps
back
if
they
are,
if
they're
taking
time
off.
For
some
reason,
they
can
temporarily
take
themselves
out
of
that.
Just
getting
flooded
with
new
PRS,
especially
like
when
you
get
as
you
progress
through
the
project.
J
It
kind
of
benefits
on
both
ends
both
the
existing
and
the
new
contributors.
So
that's
one
feature
that
we
rolled
out
in
the
last
week,
the
other
one
that
we
turned
on
it
was.
There
was
kind
of
like
a
long
tail
in
the
development
cycle
that
we
just
didn't
end
up
turning
it
on
for
everybody,
but
we
developed
a
plugin
that
our
automation
will
now
detect
when
you
open
your
very
first
PR
in
a
repo
github
again.
J
This
is
the
thing
that
github
exposes
this
piece
of
information
in
a
UI
element
that
says
it's
your
first
time
contributor
to
a
repo.
We
now
take
that
information
and
the
bot
actually
will
put
an
extra
message
on
your
first
PR
saying:
hey
I,
I
just
noticed
this
is
your
very
first
PR
of
the
repo
thanks
for
that.
J
The
focus
for
a
long
time
has
been
on
the
kubernetes
kubernetes
repository
the
core
one,
but
you
would
sometimes
get
an
inconsistent
experience
going
and
in
into
other
repos
and
then
having
to
learn.
Okay,
so
I
don't
know
the
maintainer
this
repo.
What
is
the
contributing
experience
like
so
the
automation
pieces,
where
we've
had
them
turned
on
in
like
small
little
silos?
We
want
to
turn
them
on
across
everything.
J
So
right
now,
if
you
have
never
opened
a
PR
and
a
repo,
even
if
you're
honestly,
even
if
your
existing
member,
if
you
have
never
opened
a
PR
in
a
specific
repo
before
the
bot,
will
say,
hi.
Here's
the
repo
specific
contributing
guidelines
and
here's
our
general
contributor
guide
so
that
what
that
got
turned
on
like
two
days
before
to
keep
Khan.
J
So
our
our
github
footprint
right
now,
if
you're
interested
by
the
way
there
is
a
there's,
a
talk.
There's
a
talk
tomorrow
afternoon
on
a
piece
of
automation
called
pure
bolos.
That
myself
and
my
colleague
Eric
theta
at
Google,
is
putting
on
about
some
of
our
automation,
I'm,
just
gonna
plug
that
right
there
that's
tomorrow,
but
our
github
footprint.
J
So
it's
it's
a
it's
a
fairly
big
footprint
and
we've
developed
like
if
you
have
not,
if
you
have
not
opened
a
PR
against
a
kubernetes
repo
before
we
have
a
lot
of
automation
in
place
to
kind
of
help
us
deal
with
some
of
that
at
scale.
We
built
our
own
CI
system
from
the
ground
up
that
runs
every
PR
building
kubernetes
on
kubernetes.
We
spin
up,
if
you
open
a
up
here
against
any
of
the
core
repos
that
touch
the
the
core
framework
of
kubernetes.
J
We
spin
up,
maybe
like
15
different
clusters
on
demand
to
test
and
run
through
end
to
ends
of
every
piece
of
code,
both
both
the
stuff
you've
touched
and
the
stuff
you
haven't
touched
to
make
sure
we
don't
have
regressions
like
we
test
everything
very
thoroughly
it
takes
like
if
you
open
it.
If
you
open
the
we're
working
on
this
right
now,
if
you
open
up
PR
you
to
get
a
full
complete,
successful
signal
will
take
you
about
an
hour
we're
trying
to
bring
that
down
like
it's
about.
J
We
need
to
split
out
more
tests
and
generate
more
clusters
to
do
things
in
parallel
simultaneously,
but
takes
about
an
hour,
but
we
run
through
the
full
kubernetes
end-to-end
suite
every
time
you
push
a
commit
to
a
PR
and
one
of
the
other
one
of
the
other
kind
of
gaps
in
github
that
we
have
to
overcome
is
there's
a
lot
of
get
ups.
Permissions
model
is
not
very
granular,
so
we
have
developed
a
lot
of
automation
around
being
able
to
safely
delegate
permissions
out
to
people
to
like
trust.
J
Our
contributors,
trust
the
people
in
our
community
to
do
the
right
thing
on
PRS,
without
necessarily
giving
everybody
a
commitment
and
right
access
to
everything.
But
we
can
trust
people
to
assign
things
lgt,
em
things
close
things
out.
Do
what
do
what
we
need
to
do
to
keep
that
velocity
going,
because
if
we
don't
spread
out
the
load,
we're
never
gonna
get
like
right
now,
as
you
can
see,
there
are.
J
Yeah,
so
that's
that's
like
what
we've
got
going
on
very
recently.
There
are
constantly
different
things
going
on
the
tooling
that
we
have
is
kind
of
it's
a
shared
jurisdiction
thing.
We
collaborate
with
sig
testing
on
all
of
these
infrastructure
pieces
because
it
all
runs
in
the
one
CI
system,
contributor
experience.
We
focus
on
that
end-to-end
from
the
time
you
start
a
PR
to
the
time
you
close
that
PR.
What
do
those
automation
pieces
look
like.
J
There's
plenty
there's
plenty
or
like
either
on
the
community
repo
or
the
test
info
repo
that
are
both
if
you
go
to
the
kubernetes
org
they're,
both
in
this
six
repos
up
at
the
top.
These
are
like
six
of
our
oldest
repos.
What
some
of
the
core
ones,
but
in
particular,
test,
emprah
and
community,
are
where
you'll
find
issues
and
they'll
be
labeled
with
help
wanted
good
first
issue:
there's
lots
of
little
things
in
there
as
far
as
like
automation,
pieces
that
we
specifically
have
already
identified
that
we
would
like
help
with
and
work
on.
J
But
if
you
and
this
this
is
a
call
to
literally
every
person
in
this
room.
If
you
come
across
a
friction
point
in
something
that
you're
doing
on
github,
please
let
us
know
we.
We
encourage
that
feedback
at
any
point
in
time
and
that's
no
matter
what
feature
set
you're
looking
for
we've
have
automation
around
project
boards.
We
have
automation
around
issues.
We
have
automation
around
PRS,
please
let
us
know
if
you've
run
into
any
friction
points,
because
then
we
can,
we
can
work
and
see
if
we
can
collect
that
information
together
and
see.
R
I
came
late,
I
was
just
running
the
most
amazing
diversity
lunch
in
my
life
we
had
200
people,
pair
programming,
hands-on,
kubernetes
support
and
talking
about
awesome
topics.
So
I
just
had
to
tell
people
about
that.
But
the
second
thing
that
I
wanted
to
say
is:
there
is
a
mentoring
session.
Tomorrow,
two
sessions,
60%
of
the
people,
asked
contributing
questions
to
all
kinds
of
projects.
And
yes,
everybody
in
here
is
a
mentor
I,
don't
care
if
you
have
zero
years
of
experience.
The
idea
here
is
it's
about
the
journey,
not
the
solution.
R
P
So
I
think
we've
done
enough
talking,
but
I
did
have
some
questions
for
the
audience
of
any
of
you,
like
you,
have
any
feedback
like
did
you
try
to
contribute
and
it
was
like
a
totally
wonderful
experience
and
then
you
came
out
empowered
or
dude
like
go
and
stuff
was
fluorophore
or
you
tried
to
CLA
and
you
got
an
error
and
then
he
had
to
email
something
and
they
get
back
to
you
in
30
hours
or
whatever.
Are
we
taping
this
okay?
P
C
C
S
I
mean
enjoying
it
quite
like
during
this
year
after
at
all,
from
Nikita
on
that
was
really
inspiring
and
I
think
that
they
found
because
I'm
trying
to
run
run
a
meet-up
here
in
Barcelona
I'm
doing
like
an
errand
each
week
and
the
last
week
we
did
a
contributor
experience.
One
like
we
got
like
22
PL,
put
request
the
same
day
for
the
Spanish
documentation
was
amazing.
The
people
doesn't
know
that
is
that
easy
to
get
into
the
community
I
think
the
most
the
problem
that
I
think
that
Corning
will
have
is
visibility.
S
The
people
sis
Fernandez,
has
something
that
runs
in
in
Red
Hat
Google
and
this
kind
of
genius
places,
and
they
have
like
far
far
away
from
from
auto
rich
and
it's
not
true
and
I,
think
we
need
to
focus
on
how
we
can
make
these
more
visible
to
everyone.
So
you
know
I'm
not
afraid
they
can
join
hopping
and
all
the
prefer.
S
S
T
Hey
okay,
I've
been
contributing
like
for
more
than
two
years.
I
probably
have
like
80
plus
PR
merged.
Already
in
at
the
beginning.
It
felt
very
easy:
I
can
remember
like
Janet
coup,
and
everything
was
like
giving
super
fast
feedback
on
my
peers.
It
was
enjoyable,
then
it
became
more
difficult.
So
then
I
contributed
more
to
test
infra,
because
I
still
had
this
like
quick
feedback
and
yeah.
T
O
Thank
you
so
much
for
that
feedback.
I
think
we
actually
need
to
go,
but
we
can
take
this
out
into
the
hallway
as
well
to
continue
to
the
discussion.
So
thank
you
all
so
much
for
joining
regular
meetings.
Wednesdays
at
10:00
and
Pacific
I
should
know
what
it
is
here.
I,
don't
off
the
top
of
my
head.