►
From YouTube: Kubernetes Meet Our Contributors Session 1 20190403
Description
When Slack seems like it’s going too fast, and you just need a quick answer from a human...
Meet Our Contributors gives you a monthly one-hour opportunity to ask questions about our upstream community, watch interviews with our contributors, and participate in peer code reviews.
Check this out for more information: https://github.com/kubernetes/community/blob/master/mentoring/meet-our-contributors.md
A
Hello,
everyone
welcome
to
April's
edition
of
kubernetes
meet
our
contributors.
My
name
is
Paris
I
work
at
Google,
I
have
a
panel
for
you
today.
If
you
are
coming
to
us
from
the
west
coast
like
I,
am
you
are
bright
and
early
at
7:30
in
the
morning,
hello
to
everyone
around
the
world,
wherever
you
are?
If
you
are
listening
in
right
now,
what
this
is,
if
you've
tuned
in
for
the
first
time
and
you're
like
I've,
no
idea
the
link
that
I
just
clicked,
then
I
click
just
clicked
on
on
Twitter.
What
is
this?
A
Who
are
these
people's
faces?
What
we
do
here
is
we
help
our
upstream
kubernetes
contributors
with
questions
that
they
have,
whether
they're
new
contributors
or
current
contributors
in
their
journey.
We
have
different
levels
in
in
community
membership
for
upstream
contributing
what
that
means.
Is
it's
our
decision
makers
here,
so
people
that
are
reviewing
code,
approving
code
and
doing
all
kinds
of
fun
stuff
with
the
community
and
helping
out
our
upstream.
A
These
people
come
from
all
kinds
of
backgrounds
and
all
kinds
of
companies
and
have
all
kinds
of
experiences
that
they
can
and
want
to
share
with
you.
So
this
is
a
super
cool.
Show
you're
allowed
to
ask
anything
you
want.
If
you
want
to
know
something
about,
our
contributors
feel
free
to
ask
if
you
want
to
know
about
their
journey
or,
if
you'd
like
to
know,
even
maybe
a
technical
question
and
see
if
they
can
tackle
that
likewise
you're
testing
a
game,
that's
always
a
favorite.
A
So
let's
get
started
first
things.
First,
we
do
have
a
code
of
conduct,
of
course,
that
we
adhere
to
please
the
excellent
to
each
other.
Whether
you
are
asking
or
answering
questions
on
many
of
our
channels-
and
that
brings
us
to
where
are
those
channels.
Those
channels
are
on
flak.
Mainly
it's
meet
our
contributors.
Hashtag
meet
our
contributors
on
slack
gates,
IO.
If
you
need
an
invite
there,
of
course,
I
will
also
take
direct
messages
there.
A
My
screen
name
is
Paris
that
you
see
on
zoom'
right
now
and
that's
if
you'd
like
to
remain
anonymous,
which
is
perfectly
fine
or
publicly
ask
in
chat,
and
you
can
see
that
we
already
have
quite
a
few
questions
queued
up
for
today,
probably
so
many
so
that
I
think
we're
we're
probably
full
for
this,
but
don't
worry.
We
have
another
session
at
one
o'clock
and
we'll
have
our
storage
crew
on
there
doing
a
CSI,
codebase
tour
and
some
other
really
cool
fun
stuff.
So,
but
that
said,
let's
do
some
intros
Valerie.
A
A
B
B
Get
usually
stuff
around
like
the
architecture
or
like
community
structure
and
how
things
like
hey.
We
want
to
get
this
out.
What
does
that
actually
look
like
in
terms
of
like
the
really
structure
and
so
on,
very
cool,
so.
A
B
A
B
It
was
actually
coop
con
Barcelona,
I,
wound
up
meeting
a
lot
of
concurrent
contributors
and
kind
of
it
felt
like
a
bit
of
a
wall
had
been
broken
down
like
we
know
that
it's
always
people
building
open-source,
but
at
the
same
time,
it's
kind
of
just
a
bunch
of
icons
and
I've
been
interested
in
building
2
beta
systems
for
a
long
time
and
I
kind
of
just
thought.
Ok,
this
is
like
a
very
accessible
and
welcoming
community.
That's
working
on
stuff
that
I
find
really
fascinating
to
use
and
find
the
workings
of
very
fascinating.
A
B
I
would
say
that-
and
this
is
something
that
sig
p.m.
is
making
a
lot
of
progress
on
kind
of
having
a
strong
overall
vision
of
how
everything's
working
together
we
it's
often
joked
about
the
communities,
might
become
OpenStack
v2.
We're
definitely
reaching
it
very
high
amount
of
future
complexity
that,
even
if
you
configure
your
system
in
a
simple
way,
you
still
have
to
know
about
so
many
bizarre
edge
cases.
C
Sort
of
leggy
backing
up
that
a
little
bit
sig
Kim,
just
general
project
management.
We
have
a
lot
of
good
developers
and
a
lot
of
good
contributors
but
sort
of
hurting.
All
the
cats
can
be
quite
the
challenge
and
a
little
bit
more
direction.
There
would
certainly
help
there's
other
things:
I've
really
helped
sort
of
Drive.
How
we're
developing
features
like
refinement
of
the
kept
process
or
raised
enhancement
proposal,
but
it's
definitely
something
that
like
could
use
a
bit
more
help.
Long
term.
A
For
sure,
and
in
the
ambiguity
that
is
your
first
PR
talk
to
me
in
Valerie
a
little
bit
about
your
experience,
is
there
like
what
was
what
was
if
you
could
go
back
and
tell
yourself
one
thing
like
what
would
that
one
thing
be,
and
what
would
that
be
a
good
tip
for
another
new
contributor
that
it's
laying
China
lay
at
their
first
PR.
B
B
I,
try
to
pick
something
as
easy
as
possible
to
really
ease
your
way
in
and
don't
be
afraid
to
kind
of
ask
help
ask
for
contacts
and
pester
people
who
review
my
first
pair
that
I
did
was
actually
merged
very
recently.
This
might
be
doing
a
lot
of
work
since
then,
just
because
it
was
hard
to
get
eyes
on
it.
Mcafee.
C
Was
that
a
pyaari
or
an
issue
times
like
a
good
first
issue
or
Help
Wanted
I
just.
B
B
A
B
Definitely
I
involved
with
a
couple
things
mostly
Signet
work
and
it's
been
really
helpful
to
kind
of
always
have
the
context
of.
What's
going
on
to
actually
talk
to
people
like
now,
I'm
kind
of
trying
to
focus
a
bit
on
two
proxies
so
now
that
that's
an
established
thing,
I
can
sleep
up
in
the
meetings.
People
are
messaging.
Sorry
messaging,
you
a
ticket
saying
hey!
Do
you
want
to
work
on
this?
So
it's
a
way
to
get
much
more
of
a
hold
in
the
project,
so.
A
All
right
no
well
hold
you
do
that
alright,
alright
Valerie's
next
visit.
Everyone
is
a
cube
proxy
code
based
or
cool
alright.
So
then,
let's
get
back
to
Jeff's
next
question
and
then
we'll
get
on
to
nikita's
as
a
contributor.
What's
one
tool
that
you
could
not
live
without
and
I
want
to
tack
on
a
question,
what's
one
tool
that
you
wish
you
knew
before
that
you
know
now,
because
we
do
have
quite
a
few
tools,
tips
and
tricks
and
platforms
and
communication
lines,
etc.
A
B
What
about
you
Valerie?
The
tools
that
I
definitely
can't
manage
without
now
is
Kenda
communities
and
docker.
It's
a
lifesaver
for
me
to
be
able
to
test
us
and.
C
In
far
too
many
for
my
own
good,
but
really
it's
mostly
the
ones-
the
the
the
selects
I'm
closer
and
involved
in
so
sig
contributor
experience,
cig
release
is
really
nice
just
to
sort
of
keep
an
eye
on
things.
Cig,
testing,
testing.
Ops
are
also
good
places,
just
an
idea
of
sort
of
the
overall
state
of
our
CI
infrastructure.
C
A
Variable,
yes,
I
definitely
agree
with
that.
I
also
think
I
want
to
tack
on
slack
admins
if
y'all
need
anything
out
there
in
the
world.
Slack
admins
are
there
for
you
and,
of
course,
contributed
your
summit
channel.
If
anybody
is
ever
going
to
a
contributor
summit
and
want
to
lurk
in
there
and
get
the
latest
information
about
the
summits
Valerie,
what
about
you?
What
are
some
channels
that
you
think
are
super
useful
and
slack.
B
Aside
from
like
the
obvious
sinks,
I'm
involved
in
channels
definitely
echo
what
Bob
said
about
safe
testing
every
now
and
then
there
is
a
testing
in
CI
issue
and
it's
nice
to
not
be
totally
blocked
in
banging
my
head
against
the
wall.
Oh,
that
is
super
helpful
for
just
answering
pretty
basic
questions
about
the
building
or
how
the
project
works.
I
leaned
on
it
a
lot
in
my
first
couple
weeks
and
now
it's
kind
of
it
makes
me
feel
proud
to
actually
build
the
answer.
Questions
in
that
and
then
again,
yeah
yeah.
C
A
Alright
and
then
Nikita
has
a
slew
of
questions
for
us,
and
all
of
them
are
wonderful
one
question:
how
do
you
think
people
can
ramp
up
the
contributor
ladder
and
for
folks
that
don't
know
what
our
contributor
ladder
is?
It
would
be
non-member
a
member
that
would
be
to
the
github
repository
and
then
member
reviewer,
approver
and
some
project
owner
and
actually
before
we
even
go
there
Bob.
Do
you
want
to
explain
a
little
bit
about
what
owners
files
are
just
in
case
people
are
listening,
who
or
like
what
the
heck?
C
Sort
of
the
reviewer
improver
system
is
a
way
that,
like
certain
users,
can
be
hoped
that
are
the
owners
of
that
specific
section
of
the
code
base.
Usually
when
you
create
an
issue
or
PR
against
their
PR
against
something,
it
will
there's
a
lot
like
8ci,
but
that
will
try
and
like
automatically
assign
people
from
those
lists
to
be
able
to
both
sort
of
review
your
PR
and
then
approve
it.
C
C
A
D
A
A
Alright,
now
we
were
digging
into
Nikita's
question
about
how
folks
can
grow
up
the
contributor
ladder
and
we
were
digging
into
I
said:
take
it
in
twice
I,
don't
like
that,
what
owner's
files
are
to
begin
with
and
why
people
even
want
to
grow
into
a
ladder.
So
why
would
people
want
to
grow
into
an
owner's
file
or
grow
through
the
contributor
ladder
with
drippin
Eddie's
like
what
are
some?
What
are
some
value
adds,
or
what
are
some
reasons?
Why
or
benefits.
E
C
Usually,
once
you've
been
added
to
sort
of
as
a
reviewer
or
into
an
onus
file,
that
means
you've
sort
of
established
yourself
in
that
section
and
that
sort
of
means
that
you
know
the
bots
and
other
things
that
can
automatically
assign
work
essentially
work
to
you
or
like
review
PRS
and
like
that
you've
sort
of
essentially
become
trusted
enough
to
evaluate
the
codebase
and
evaluate
the
PRS
within
that
subsection
and
sort
of
once
you've,
you
know,
participate
enough
in
a
certain
section.
You
have
enough
PRS,
you
will
get
promoted
to
a
reviewer.
C
D
D
We
can
hear
about
like
the
corporate
stuff
promotion,
but
it's
more
about
a
white
community
recognition,
and
so,
if
you
are
in
the
bonus
file,
that
means
that
this
error
of
community
absolutely
respects
you
and
realizing
you
that
some
specific
items
that
you
can
give
you
can
do
there
so
don't
be
confused
again,
always
be
some
kind
of
some
kind
of
like
corporate
promotion.
Work
like
it
shouldn't
be
your
primary
goal
just
to
be
headed
to
the
bonus
file,
and
it's
all.
But
it's
it's
like
about
issues
in
the
community
and
respect
from.
A
B
Find
it
a
bit
difficult
because
by
nature
of
being
kind
of
a
very
huge
in
distributed
community,
it's
often
there's
not
often
a
very
clear
on
ramp.
You're
gonna
have
to
wander
around
and
get
lost
and
figure
things
out
for
yourself.
So
right
now,
I'm
trying
to
focus
more
on
specific
areas,
because
I
have
limited
time
and
try
to
seek
out
stuff
that
I
can
review
and
help
with
that
is
contributing
to
those
areas.
Even
if
it
doesn't
come
up
right
away.
A
C
D
Mentioning
some
kind
of
owners
file,
you
should
understand
everything
that
happens
in
that
codebase.
You
should
understand
all
the
processes
and
all
the
information
display
secure.
So
you
are
the
person
who
is
responsible
for
all
the
other
actions
that
can
happen
or
cannot
happen
in
that
specific
area,
so
understanding
on
what's
happening
there.
What
should
you
do?
What
should
you
not
do?
What
other
people
do
get.
C
For
me,
be,
if
you
start
focusing
on
a
specific
area,
you
can
also
look
for
issues
that
target
that
area.
One
thing
for
me
recently
was
just
that
the
communications
directory
and
the
community
repo
I
wound
up
just
rewriting
a
bunch
of
the
guides,
for
you
know,
YouTube
slack
guidelines,
things
like
that
and
after
I
entreated
enough
to
it,
it
was
then
felt
like
you
know.
A
Congrats
again,
all
right
now
Nikita
has
a
different
question.
If
you're
starting
to
work
on
a
new
area
of
the
project,
what
kind
of
workflow
do
you
use
for
instance?
Do
you
first
look
at
the
issue
list?
Do
you
ask
on
slack
for
issues?
Do
you
start
lurking
in
meetings?
What's
your
first
attempt
and
Valerie
I
think
we
kind
of
heard
this
from
you
earlier
as
to
wait?
Yours
once
did
you
have
any?
Did
you
have
any
like
I
guess
workflow
there?
As
far
as
like
all
right,
let's
try
a
cig
meetings.
First.
B
It
wasn't
anything
too
structured,
usually
I
tried
to
kind
of
get
more
context
about
the
codebase
in
general,
before
diving
into
just
skimming
code
before
going
into
a
specific
issue
that
might
be
like
going
through.
Canaries
docks,
especially
a
lot
of
areas.
I
haven't
really
touched
an
end
user,
so
the
details
aren't
familiar
once
I
kind
of
understand
what
it's
actually
doing.
That's
a
good
time
to
recode
and
once
I
have
kind
of
got
a
rough
idea
of
what
the
code
tree
of
a
component
is.
Then
it's
a
lot
easier
to
dive
into
specific
issues.
B
What
were
some
of
those
docks
that
you
just
mentioned?
I'm
curious,
so
the
official
kubernetes
Doc's
can
be
a
little
bit
messy
to
find
things,
but
there's
gold
mines
of
information
in
there
about
how
different
components
work,
especially
with
stuff
like
the
blog
posts.
We're
like
a
cig
member,
we'll
do
a
deep
dive
in
something
that.
C
For
me,
it's
like
I'd
start
sort
of
backing
up.
That
is
focus
on
the
specific
code
base
that
you're
interested
in
and
then
definitely
get
involved
with
the
sig
and
a
good
place
to
sort
of
getting
a
idea
of
the
pulse
of
what's
going
on
recently
in
the
sig
is
to
read
their
meeting
notes
and
that
will
sort
of
get
you
up
to
date
on
sort
of
everything,
that's
been
going
on
and
give
you
a
little
bit
the
history
lino.
C
C
C
One
thing
actually,
a
lot
of
people
think
that,
like
when
coming
this
new
to
entry,
but
they
have
to
do
stuff
to
you.
You
know
the
koreans,
kubernetes
repo,
and
they
don't
actually
realize
that.
There's
this
whole
slew
of
other
sub
projects
and
other
things
that
are
all
involved
in
this,
then
this
grand
old
thing
of
kubernetes-
and
sometimes
it's
a
lot
easier
to
actually
jump
into
a
sub-project
we're
out.
There
aren't
necessarily
all
that
release
restrictions
that
there
are
with
various
committees.
C
You
know
interacting
with
the
community
in
a
more
say
personal
manner,
and
can
possibly
sort
of
spring
bit
springboard
back
to
working
on
the
like
main
miscarries
project,
see
like
a
lot
of
stuff
with
with
queue
builder
and
some
of
the
other
things
and
a
cigs
are
sort
of
focused
on
you
know,
building
your
own
controllers
and
getting
and
getting
an
idea
of
how
that
entire
sort
of
system
works.
You
see
the
sort
of
the
fundamentals
to
possibly
jump
back
and
start
doing
other
things
and
the
main
you
know,
Eddie's
kubernetes.
A
D
D
If
this,
this
project
of
a
project
is
specific,
so
you
can
interact
with
second
immittance
for
the
midi
notes,
work
with
them
with
us,
like
Sharon
Stone,
but
again
the
first.
The
first
item
that
you
should
do
if
you
are
interested
in
some
repair
for
yourself,
please
start
with
the
documentation,
which
is
there
in
the
file
on
github,
for
the
trip
for.
A
B
C
Well,
for
me,
it
was
not
not
much
stuff,
that's
actually
like
public,
but
in
the
research
software
engineering
side
say:
I
live
and
breathe.
Academia,
it's
all
things.
That's
not
very
discoverable
in
bitbucket.
A
D
Sir
sure
Kim
Panetta's
is
familiar.
Kinetise
was
my
first
project
to
be
so
huge
death
I
used
to
work
with
a
services
community.
Specifically,
we
spoken
stick
before
curing
kubernetes
and
actually
one
of
the
reasons
why
I
was
so
excited
about
this
community
project
was
I
was
dead
fact.
We
must
understand
enough
that
fact
that
kinetise
community
is
way
easier.
It's
communities
community
as
and
versus
project,
is
way
easier
for
a
new
promise
to
contribute
to,
rather
than
any
other
consoles
project
potential
experiences.
A
E
D
D
D
A
C
Of
my
day,
job
work
is
honestly
operations
related,
at
least
these
days
more
process
management,
and
you
know
I
spin
up
and
manage
several
urbanized
clusters
for
our
researchers
here
at
the
University
of
Michigan
and
I
work,
several
other
researchers
at
other
academic
institutions.
It
honestly
doesn't
have
too
much
to
do
with
any
of
my
upstream
work
and
that's
sort
of
been
an
interesting
relationship
with
my
job,
but
talk.
A
About
that
a
little
bit
like
how
do
you,
how
do
you
juggle?
How
do
you
juggle
both
I
mean
knowing
that,
like
there
are
two
different
sort
of
responsibilities
where
it's
like,
if
you're
developing
on
crew
natives
and
then
you
want
to
develop
upstream
kubernetes,
it
kind
of
like,
with
the
exception
of
time,
goes
hand
in
hand.
How
do
you,
how
do
you
juggle
like
what
are
some
things
that
you
do,
the
jungle
things.
C
B
I
think
kind
of
the
mentality
and
the
priorities
have
been
the
biggest
difference
for
me
in
a
really
positive
way.
In
most,
open-source
community
is
certainly
in
communities.
There's
a
huge
like
client
and
end
user
focus
that
well,
every
company
wants
to
have
that.
I.
Don't
think
that
every
developer
winds
up
having
that,
but
in
open
source
we
care
so
much
about
the
quality
of
what
we're
putting
out.
We
would
kind
of
rather
work
on
bug,
fixes
and
churn
out
features
and.
B
A
A
D
It
were
studded,
like
my
contributions,
started
as
my
let's
golet's
of
the
project,
because
it
was
outside
of
my
day
job
before
injuries.
You
know
bananas
and
other
cloud
native
oppressors
project
my
day,
job
but
I'm,
still
highly
passionate
about
it
and
I
see
no
reason
why
I
can't
even
spend
my
personal
time
working
on
some
items
directly.
E
D
B
Because
working
on
career
days
is
like
80,
90
percent
of
Hobby
from
you,
I
do
have
the
luxury
of
stepping
back
when
I
need
to
other
than
that
I
just
try
to
stay
stuff
out
as
much
as
I
can
and
make
sure
that
there's
always
that
time
to
do
something
that
I
find
kind
of
enriching
and
relaxing,
as
well
as
just
the
basics
like
have
I
eaten
properly,
have
I
slept
well
enough,
because
things
go
downhill
very
quickly.
If
anything
essentially
gets
neglected.
A
Yes,
I
call
that
hangry
and
when
it
escalates
it
gets
fierce.
So
no
I,
definitely
on
the
sleep
and
food
train
as
basic
as
that
sounds
that
is
so
essential.
I
forget
all
the
time
like
just
being
in
front
of
this
box
for
12
hours
and
like
oh
I,
didn't
eat
it.
That's
that's
not
good,
so
ya
know.
Eating
and
sleeping
is
very
good.
Y'all
trust
me
alright,
that
actually
it
is
it
I
think
we've
ran
through
all
of
the
questions.
I'm
gonna
give
for
one
last
call
for
questions
in
the
in
the
chat
here.
A
C
Get
involved
in
ask
questions.
Early
people
are
generally
very
happy
to
answer
them,
especially
if
it's
you
know
trying
to
work
towards
a
specific
issue
you
have,
if
you're,
if
you
can
like
link
the
issue
or
something
that
you're
working
on,
don't
be
afraid
to
ask
questions.
I
guess
this
is
the
big
one.
D
A
B
Communicating
and
coordinating
definitely
also
gets
a
plus-one
for
me.
I
spent
a
very
long
time
on
a
test
ticket
and
the
reason
why
I
couldn't
make
my
test
work
is
because
the
behavior
had
actually
progressed
took
me
quite
a
while
to
reach
out
to
the
sig
and
figure
out
that
the
reason
why
I
couldn't
get
things
to
work
with,
because
they
did
not.
B
A
Good
tips,
y'all
good
session
I,
think
I
actually
see
somebody
typing
in
flack
right
now,
I'm
gonna
give
them
up
they're,
not
taking
any
more
all
right.
Dogs
last
call
all
right.
We
have
one
more
session
left
today
for
those
that
are
still
listening.
We
have
our
storage
crew
on
and
we
also
have
the
Emeritus
mini
cube,
maintainer
Matt
Rickard
on
as
well
at
one
o'clock,
so
that'll
be
a
good
session.