►
From YouTube: Kubernetes SIG-ContribEX 20181003
Description
Developing and sustaining a healthy community of contributors is critical to scaling the project and growing the ecosystem. We need to ensure our contributors are happy and productive, and that there are not bottlenecks hindering the project in, for example: feature velocity, community scaling, pull request latency, and absolute numbers of open pull requests and open issues.
B
My
name
is
Paris
I
work
at
Google,
I'm,
a
community
manager
here
and
today
we
will
have
our
usual
show
and
that
comprises
of
both
a
intro,
a
project
board
update
as
well
as
a
little
bit
of
an
open
mic
Ben
session
dos
gosh
session.
However,
we
look
like
to
frame
it.
So
first
things.
First,
we
do
have
a
code
of
conduct,
so
please
be
excellent
to
each
other.
B
If
anybody
would
like
to
read
the
code
of
conduct
that
is
inside
of
the
community
repo
and
if
there
are
any
new
contributors
on
the
line
that
would
like
to
introduce
themselves,
you
can
speak
now
or
forever
hold
your
peace.
It's
definitely
not
required,
but
if
you've
never
joined
our
call
before
and
would
like
to
feel
free
to
interrupt
me
at
any
time.
C
C
B
So
great
welcome
to
kubernetes
a
lots
of
welcome
messages
and
chat
too,
and
we
can
definitely
get
you
started
a
lot
of
people
on
this
call
right
now
actually
started
contributing
to
kubernetes,
especially
the
codebase,
through
contributor
experience
through
helping
out
other
contributors.
You
have
a
fresh
mindset
where
a
bunch
of
us
have
been
on
the
project
for
a
while
and
we
don't
necessarily
see
holes
and
gaps
in
our
contributor
documentation.
So
definitely,
as
you
get
ramped
up
feel
free
to
poke
holes.
In
anything,
you
see.
Okay,.
B
There
anybody
else
on
the
line
I
think
we
see
mostly
regular
folks
all
right
all
right,
let's
get
on
with
our
show.
First
things:
first,
we
do
run
three
programs
regularly.
That's
the
Thursday
community
meeting,
that
is
our
monthly
user
office
our
session
and
then
the
third
is
meet
our
contributors
which
what
is
going
off
today.
Our
first
session
already
went
off
and
then
this
afternoon
is
the
steering
committee
session.
B
B
Awesome
and
deep
just
for
your
knowledge,
every
Thursday,
we
have
a
community
meeting
that
happens
at
10
a.m.
Pacific
and
that
goes
live
on
YouTube
as
well.
So
you
don't
necessarily
need
to
join
the
call
to
listen
in
I'm,
not
Sauer
sings.
Give
me
updates
and
that's
where
you
can
also
hear
if
they
need
new
contributors
and
things
like
that
for
me,
target
yeah
for
meet
our
contributors.
I
will
put
a
call
out
for
help.
We
do
have
a
couple
of
holes
in
the
in
the
next
couple
of
months.
B
Nothing
that's
alarming
by
any
means,
but
we
do
have
one
or
two
slots
for
from
session.
So
if
anybody
on
the
line
was
like
to
be
a
mentor
and
help
out
or
if
you're
a
part
of
another
sig
that
needs
a
certain
type
of
contributor,
this
is
an
awesome
way
to
promote
that,
because
we
have
new
and
current
contributors
that
listen
on
this
call,
and
that's
it
for
me
for
our
program
updates.
B
This
isn't
necessarily
something
that
I
want
to
want
us
to
go
into
in-depth
in
especially
details
on
this
call,
since
we
only
have
an
hour-
and
you
can
clearly
see
that
we
have
enough
projects
to
talk
about,
for
probably
the
next
to
at
least
update
meetings,
so
where
I
wanted
to
start
was
the
blocked
column
and
I
believe
Erin,
you
put
some.
You
put
some
cards
there
yesterday
that
you're
currently
blocked
on.
Did
you
want
to
give
us
an
update
and
see
how
we
can
help?
Yes,.
D
I'm
blocked
on
two
things:
again:
it's
the
wrong
screen.
I
swear
I'll,
get
this
right.
One
of
these
days,
second
screen
cool.
All
right,
hey
we're!
Looking
at
our
awesome
project
board.
The
first
black
item
was
here
last
week
and
we
discussed
it
it's
the
idea
that
we
want
to
remove
right
access
from
kubernetes
kubernetes
to
get
things
done.
It's
a
long
trail
of
whoa
I
updated
its
status
after
we
talked
last
week
to
say
it
remains
blocked
because
of
these
things
there
is
no
way
I'm
getting
to
this
in
the
recent
future.
D
Unless
anybody
here
has
cycles
to
spend
on
this,
I'd
like
to
propose
multi
lists
in
their
backlog,
because
it's
blocked
because
of
just
lack
of
resources,
no
objections.
I
will
do
that
after
this
next
thing,
Matt
Hicks,
the
same
guy
who
was
responsible
for
the
hassan
sauce
that
is
per
repo
labels
from
the
label
sync
tool
and
a
number
of
other
things
first
put
forth
a
proposal
to
change
our
use
of,
maybe
I'll
just
do
it
this
way
to
change
our
use
of
okay
to
test
and
needs
okay
to
test
the
state
of
today.
D
Is
that
a
needs?
Okay
to
test
label
is
automatically
applied
to
any
pull
request
that
comes
from
non
trusted
member
and
it
requires
a
trusted
member
to
issue
a
/
okay
to
test
command,
which
will
then
remove
that
label.
This
is
weird
because
it's
kind
of
the
opposite
of
the
way
many
of
our
others.
Labels
were
such
as
applying
/l
GTM
say
a
PR
looks
good
to
them.
Instead
of
the
inverse
of
like
this
PR
doesn't
have
no
GTM.
D
The
thought
is
by
inverting
this
label
relationship
it'll,
make
it
clear
when
a
PR
is
truly
okay
to
test,
because
over
the
past
couple
of
years,
we've
had
these
random
cases
where
a
home
request
will
have
its
jobs
run
for
whatever
reason,
but
then
it
still
has
the
like
needs.
Okay
to
test
label
and
slash
retest
doesn't
work
so
we're
hoping
that
by
applying
a
green
label
that
says
yes,
this
PR
is
okay
to
test.
It's
a
more
explicit
confirmation,
he'll
be
a
better
contributor
experience
for
everybody
involved.
D
I
wasn't
around
for
the
original
discussion
of
this,
but
I
believe
was
the
discussion
on.
It
has
gone
through
it's
a
testing,
so
I
just
wanted
to
run
this
through,
say,
contributor
experience,
I,
believe
I
saw
it
in
the
common
trail.
That
Christophe
was
largely
in
favor
of
this.
So
maybe
you
have
already
talked
about
this,
but
after
you
have
any
thoughts,
comments
concerns.
Please
drop
them
in
this
poll,
request.
Otherwise
I'm
going
to
remove
the
hold
and
go
pinging
for
LG
teams
later
today.
D
That
is
a
really
good
question,
I'm,
not
sure,
so
the
merging
of
that
PR
will
magically
make.
That
thing
happen,
that's
more!
The
this
person
is
piloting
this
change
through
cap.
So
this
is
their
description
of
the
plan
and
if
you
find
they're
missing
that
step
in
the
plan,
I
think
that
would
be
very
colors
to
add
to
the
PR.
B
All
right,
okay,
so
I
wanted
to
see
if
anybody
wanted
to
stand
up
with
anything
that
is
currently
in
progress
right
now
that
you
have
updates
with
that,
you
wanted
to
address
to
us
and
or
ask
for
feedback
or
help
that
would
include
folks
from
either
the
non-code
contributor
guide,
an
update.
That
would
also
include
Kristof,
if
he's
on
for
github
management
and
also
include
me
for
steering
committee
stuff,
election
stuff
and
communication
communication
stuff.
Oh
and
lc2,
you
have
a
card
in
there
for
dev
stats.
F
F
B
B
D
Because
that
kind
of
ties
into
you
sub
project
details
in
sake,
CMO
dev
stats-
is
one
of
the
few
projects.
That's
not
following
our
accepted
format.
Chris
some
project
is
considered
to
be
a
thing
that
yeah
some
project
is
code
somewhere
in
the
myriad
kubernetes
repos
that
we
have
in
dev.
Stats
currently
doesn't
have
code
in
there.
So
a
document
that
describes
our
involvement,
a
use
of
dev
stats
is
literally
all
we
need
to
justify
the
existence
of
that's
that's
as
a
sub
project
should
be
their
experience
back.
D
Some
project
details,
in
a
sake
CMO
Steven
Augustus,
put
forth
the
PR.
That
was
maybe
add
things
like
contacts
for
sub
projects,
but
I'm
putting
the
brakes
on
that
until
I've
had
a
chance
to
discuss
this
with
Brian
grant
in
the
context
of
steering
committee,
but
and
if
we
can't
get
back
on
I'm,
bringing
it
up
as
a
topic
and
save
architecture.
Tomorrow,
homes
better
understand
what
will
meet
the
intensive
sub
projects
for
making
them
useful
to
use.
B
H
F
Have
a
question
regarding
the
dev
stats,
we're
looking
to
use
this
for
another
CN
CF
project,
the
harbour
project
I
was
recently
added
into
the
sandbox
and
I'm
kind
of
wondering
how
how
to
pull
out
information
from
it.
I
understand
that
we
have
all
the
data
in
there,
but
what
are
some
good
visualizations
were
some
good
sets
of
information
that
we
get
out
of.
H
H
H
H
F
H
D
Another
source
of
information
might
be
taking
a
look
at
all
those
some
of
these
might
be
kubernetes
specific.
The
graphs
we've
presented
to
the
kubernetes
community
in
the
past
have
generally
been
selected
to
be
like
really
obvious,
actionable
graphs.
That
can
tell
a
pretty
clear
story,
so
you
might
find
some
good
ones
there.
Okay,.
B
We're
gonna
put
some
of
the
like
stuff.
We
regularly
look
at
on
Elsie's
recommendation
list
so
that
you
can
see
kind
of
like
what
we
care
about
if
you
will
I'm
when
we
care
about
all
of
it.
But
it's
it's
a
lot
of
dashboard,
so
I
understand
where
you're
coming
from
all
right.
Anybody
else
want
to
stand
up
before
I
stand
up
regarding
steering
committee,
stuff
and
communication
stuff
and
the
like.
I
Thing
that
I
just
wanted
to
bring
up
talking
with
all
and
so
on.
Github
administration,
I
mentioned
last
meeting
that
we
have
per
bolos
up
and
running
to
do
all
the
organ
veidt's
we're
now
at
a
point
where
I've
been
able
to
write
and
merge
some
documentation
on
like
what
the
human
component
of
that
process
is.
B
I'm,
so
excited
I'm
super
excited
about
all
the
work
that
Christophe
and
team
is
doing.
So
thanks
a
ton
for
all
of
your
efforts,
Christophe
all
right,
all
right,
so
I'm
gonna
stand
up
about
a
couple
of
things.
First,
things
first
steering
committee
election
and
today
y'all
I'm
super
pumped
about
that.
If
you
are
listening
to
this
either
recording
or
otherwise,
please
vote.
B
If
you
are
an
eligible
voter,
if
you
do
not
know
already
where
to
find
the
eligible
voter
list,
its
voters
that
voters
thought
md
if
you
search
within
the
community
repo,
it's
under
the
events
which
is
unbelie--
under
the
elections,
the
results
will
be
announced
tomorrow
at
the
community
meeting,
which
is
thursday
october
4th
by
a
steering
committee
member
that
is
TBD.
So
I'm
working
on
some
announcement
stuff
today,
I'm
also
working
on
making
sure
that
we
have
all
the
final
reminders
out,
and
then
we
close
the
poll
at
6
p.m.
B
B
All
right,
we'll
also
publish
some
data
and
it'll
be
fun,
so
that's
it
for
steering
committee
stuff,
so
we'll
wrap
that
up
this
week,
whoo
and
then
communication
platform
stuff.
We
are
super
underway
with
the
humongous
issue,
that
is,
communication
and
collaboration
platforms
for
all
assessment.
This
is
making
sure
that
we
are
using
all
the
right
communication
platforms
for
the
right
things
and
producing
artifacts.
Accordingly,
those
artifacts
are
going
to
be
like
a
communication
roadmap
of
Q
of
kubernetes,
where
to
go
for
what?
B
How
who
and
why
I
definitely
still
need
help
with
that
I
know.
I
know
Arnold,
who
is
on
the
line.
Right
now
has
been
doing
an
awesome
job
chopping,
water
chopping,
wood
carrying
water.
You
can
leech
off
water
unless
you're
a
surfer,
I
guess,
but
we've
been
doing
a
lot
of
data
entry
and
I
know
that
does
not
sound
awesome.
B
So
that's
why
I
think
it's
great
that
he's
been
helping
me
out,
but
if
you'd
like
to
help
out
with
that,
that's
just
pretty
much
less
doing
an
inventory
of
the
humongous
sprawl
we
have
who
owns
what?
Why
so
that,
if
we
would
like
to
centralize
these
things
that
we
know
exactly
who
to
go
to
where
to
go
to
and
why
the
second
piece
of
that
issue
is
the
survey
like
who's
doing?
Who
is
using
what?
Why
and
how?
B
B
There
are
tons
of
stories
that
can
be
drawn
from
this.
It
is
a
awesome,
awesome,
survey,
I'm,
so
I'm
really
excited
to
dig
into
this.
I
will
give
you
a
quick
data
point.
Does
anybody
want
to
guess
the
most
popular
well
I'm?
Sorry
technically
was
in
popularity.
It
was
based
off
of
most
usefulness.
Does
anybody
want
to
guess
what
was
the
most
useful
section
of
the
Thursday
community
meeting.
B
No
I
think
I
think
that's
actually.
You
know
people
think
it's
super
useful
to
get
that
that
quick,
that
quick,
30
second
to
one
minute
information
about
about
release
so
I
think
that's
a
section
that
we
should
continue
to
finesse
in
the
community
meeting,
because
clearly
people
are
getting
a
lot
out
of
it.
Quick.
J
B
And
you're
very
popular
in
slack
as
well
so
shouts
to
the
release
team
for
being
a
artery
of
information,
so
yeah.
We
can
definitely
draw
other
stories
out
from
that
too,
like
who
thought
it
was
even
more
useful.
New
contributors
or
current
contributors,
stuff,
like
that
Josh
I
know,
is
a
date
ahead.
So
Josh
you
can
have
the
raw
data
as
soon
as
I
am
done
with
it,
and
anybody
else
I
would
like
to
whip
up
pretty
graphs
feel
free.
B
B
All
right
cool
all
right
so
for
those
that
are
looking
for
issues
to
work
on
or
places
to
help
they're
tons
of
help
on
it
and
good
first
issue.
Labels
on
our
project
boards
so
feel
free
to
dig
into
any
of
those
just
announced
on
the
on
the
thread
that
you'd
like
either
help
or
that
you
are
working
on
it
and
we
will
gladly
take
it
all
right.
So,
let's
move
to
the
open
mic,
it
looks
like
Quinn.
You
have
the
first
item
on
the
open
mic.
K
Yeah,
so
actually,
technically,
this
is
not
my
idea.
One
of
the
attendees
at
the
new
contributor
workshop
at
KU,
Khan
in
Copenhagen,
said
that
a
really
great
addition
to
the
workshop
would
be.
If
we
can,
she
call
it
a
speed-dating
session.
I,
don't
know
if
speed
dating
is
the
right
word
for
this,
but
basically
a
meetup
between
six
and
new
contributors.
K
The
reason
I
don't
want
to
say,
speed
dating,
is
because
at
this
point,
I
want
to
do
it
at
the
end
of
the
workshop,
when
people
kind
of
knew
what
SIG's
are
and
where
to
find
this,
the
stakes
that
they
might
be
interested
in
working
with
and
since
there
should
be
a
lot
of
representatives
for
the
regular
contributor
workshop,
I
shouldn't
say
regular
either
for
the
current
contributor
summit.
It
would
be
amazing
if
we
could
have
like
I,
don't
know
tables
where
it
says.
You
know
this
is
sick
testing.
K
This
is
like
steak,
you
know
Federation
or
I,
don't
remember
what
it
was
called
now
and
and
then
new
contributors
who
would
have
that
by
now
been
like
spending
several
hours.
Thinking
about
how
they
might
want
to
contribute
can
go
and
find
people
from
those
SIG's
and
actually
talk
to
humans
and
get
some
direct
mentoring
since
we're
already
all
in
the
same
place.
So
I
need
some
volunteers
from
the
six
and
I
was
just
kind
of
wondering
where
this
falls
into.
K
B
You
should
make
it
a
issue
for
events
and
do
area.
You
can
do
area
community
management
and
then
yeah
I
would
put
that
I
would
set.
The
issue
was
like
needs
volunteers.
For
this
thing,
and
then
what
we
can
do
is
we
can
socialize
it
within
the
sig
leads
and
then
maybe
get
each
one
of
them
to
like
assign
someone
or
bring
someone
or
something
along
those
lines,
especially
if
they're
one.
So
we
know
that
have
help
wanted
labels
and
stuff
like
that.
K
Yeah
and
it
doesn't
have
to
be
six
either
I
mean
it
could
be
sub
projects
right.
So
so
what
I
did
last
coop
con
I,
basically
just
told
everyone
I'm,
ed,
hi
I,
want
to
have
some
technical
issues
to
work
on
and
then
Phil
wit
Brock
from
6co
I
was
like.
Oh,
we
have
this
new
tween.
Do
you
want
to
contribute
and
I
got
to
work
on
some
Help,
Wanted
or
good
first
issues,
and
it
was
awesome.
It
was
really
really
great
and
I
just
kind
of
want
that
to
be
there
for
everybody
or
not.
B
I
would
just
because
we're
looking
right
now,
you
were
looking
for
both
SIG's
/
sub
project
support,
as
well
as
volunteers,
to
help
you,
okay,
so
that'll
be
a
good
place
to
poke
people
when
we're
advertising
for
the
help
to
get
more
information.
So
just
pretty
much
kind
of
like
do
a
knowledge
dump
in
the
issue
with
what
you
just
talked
about
like
we're
looking
for
XYZ
because
of
XYZ
mm-hmm,
and
then
we
can
track
it
to
in
the
Monday.
K
B
You
all
right,
I
guess.
On
that
same
note,
if
anybody
would
like
to
help
out
with
contributor
summit
stuff,
Josh
I
don't
know
if
you
need
anything
for
Shanghai,
but
for
Seattle
we
will
need
some
on-site
support
and
I.
Think
no
was
on
the
line
right
now,
Noah's
going
to
be
managing
a
sort
of
staff
ambassador
thing
for
us,
because
we're
gonna
have
a
lot
of
rooms.
Those
rooms
are
going
to
need
to
be
kept
on
time,
especially
the
ones
that
have
open
discussions.
B
B
B
D
Guess
when
a
heads
up
I'll
give
you
all
is
that
I
think
the
automation
that
we've
rolled
out
to
every
kubernetes
repo
and
like
kubernetes
and
kubernetes
sakes
and
kubernetes
client
is
coming
to
congrat
ease
incubator
real
soon
now
there
were
a
couple
repos
that
had
a
minor
configs
that
I
will
be
chatting
with
by
the
way.
Was
this
meeting
recorded
I
just
noticed
a
little
like
red
dot?
Was
it
up
there
yeah.