►
From YouTube: Kubernetes Meet Our Contributors 20180606
Description
Interested in working on Kubernetes development? Join us on the first Wednesday of every month! https://github.com/kubernetes/community/blob/master/mentoring/meet-our-contributors.md
A
All
right,
everyone
welcome
to
June's
edition
of
meet
our
contributors.
My
name
is
Paris
I
work
at
Google
doing
kubernetes
community
management.
This
is
mentors
on
demand,
a
web
series
for
all
things:
kubernetes
development
and
community.
We
welcome
you
from
livestream
on
youtube.
If
you
are
joining
us
today
to
ask
questions,
we
do
have
some
rules
and
where
to
post
your
questions.
First
things.
First,
we
have
our
meet
our
contributors,
black
channel
on
the
kubernetes
slack
team.
A
A
If
you'd
like
to
remain
anonymous
on
slack,
my
DM
is
just
Paris
is
my
name,
PA
RIS
and
also,
if
for
the
panelists
that
are
here
today,
feel
free
to
ask
each
other
questions
as
well
feel
free
to
be
conversational
and
then
we'll
get
into
some
introductions
in
a
second.
Also.
Last
but
not
least,
we
do
have
a
code
of
conduct
for
all
of
our
forums,
so
that
includes
panelists,
as
well
as
anyone
asking
and
answering
questions
and
our
slack
channels.
A
B
Suppose
I'm
Steve
I
work
at
Red,
Hat
and
one
of
those
sig
testing
code
leads
I
got
started
at
Q
raised
because
be
testing
automation.
That's
the
customers
making
was
just
head
shoulders
above
a
lot
of
the
other
stuff
that
we
saw.
So
we
wanted
to
adopt
it
for
our
projects
if
I
had
and
once
you
contribute
back
to
the
sig
as
well.
C
I'm
Julia
I'm,
Lizzy
works
and
I've
worked
on
few
bodman
in
the
past
and
other
different
projects,
not
so
much
on
kubernetes
itself.
Lately,
as
many
things
are
in
different
vehicles
now-
and
you
know
it's
hard
to
define
what
defines
it
to
bring
this
project
with
software
anyway
said,
I've
been
working
on
a
lot
of
people
system
projects
were
at
different
things
and,
for
example,
yesterday
we
just
released
the
key
as
for
the
lamppost
at
the
lake
to
the
chop,
which
is
which
is
the
project
looking
for
contributors
as
well.
C
F
A
A
Both
George
and
I,
are
active
in
the
special
interest
group
for
a
contributor
experience
which
Carolyn
just
just
named
dropped
as
well,
so
we
are
always
looking
for
new
contributors
and
that
we
aim
to
make
the
contributor
experience
as
smooth
as
possible
and
as
awesome
as
possible
across
all
of
our
kubernetes
repos,
all
right.
So,
let's
get
into
the
questions.
Well,
actually,
first
things.
First,
thank
you
panelists!
So
much
for
joining
us
today.
I
just
wanted
to
give
you
a
quick
thanks
before
we
start
all
right.
We
have
several
questions
today,
Teague.
A
The
first
question
is
coming
from
him.
This
was
after
our
last
meeting
tribute
errs
so
Teague
says
that
I
have
my
first
couple
of
PRS
and
Service
Catalog,
and
it's
great
it
even
says
contributor.
Next
to
my
name
on
github,
we
would,
since
I
always
think
far
in
advance
about
my
career.
Tell
me
about
being
a
maintainer.
What
kind
of
people
are
maintained
errs
I
you,
you
should
think
about
being
a
maintainer
if
you
like
XYZ,
how
often
do
maintainer
get
to
contribute
in
general?
A
How
long
has
maintainer
has
been
a
part
where
the
community
is
a
contributor
before
they
became
a
maintainer?
What's
the
process
of
becoming
one?
Do
you
apply?
Are
you
selected,
etcetera,
so
I
think
a
cldr
is
tell
us
a
little
bit
about
maintainer
ship
within
the
communities
community.
Does
anybody
want
to
go
first,
I.
D
So
I'm
a
new
maintainer
for
a
Service
Catalog
and
can
kind
of
talk
about
how
I
got
sucked
into
that.
I
was
very
new
to
Service
Catalog,
but
because
I
just
been
hired
at
Microsoft,
and
it
was
my
full-time
job.
I
was
able
to
do
a
lot
of
significant
contributions
very
quickly,
almost
like
a
service,
catalog,
CLI
and
then
kind
of
took
on
a
lot
of
extra
things.
You
don't
just
become
a
maintainer
because
you
submitted
a
bunch
of
PRS.
D
People
are
looking
for
someone
who
one
isn't
in
it,
just
for
like
their
one
thing
that
they
needed
to
like
fix
in
kubernetes
or
whatever,
and
then
they're
moving
on.
It's
someone
who's
interested
in
the
project,
a
bit
more
long-term,
someone
who
is
friendly
and
easy
to
work
with
and
super
important
people
who
help
with
the
project
management
side
more
on
slack,
say
helping
new
people
may
be
watching
issues
as
they
come
in,
like
that
huge
firehose
and
helping
to
go
hey.
This
is
actually
do
this
or
I'd
love
to
help.
D
You
answer
that
question,
or
just
interacting
with
people
more
with
the
community
and
less
just
being
someone
who
is.
It
helps
to
be
reliable
on
pull
requests
and
it
helps
to
care
about
more
than
one
area,
but
at
least
in
my
mind
what
what
has
helped
me,
the
past,
become
a
maintainer
and
other
things
like
depth.
The
codependency
manager
as
well
was
jumping
in
and
starting
to
kind
of
just
act
as
a
general
point
of
contact,
the
lead
or
whatever
just
a
friendly
guide.
A
B
B
Is
this
pull
request,
moving
us
in
the
right
direction
and
as
soon
as
you're
answering
questions
like
that
about
in
10
and
less
so
you
know,
is
the
COO
here
well,
Burton
I
think
that's
when
he
starts
a
transition
into
it
more
of
a
maintain
interval,
and
that
comes
with
triaging
issues
that
are
coming
in.
You
know
keeping
up
to
date
with
all
the
changes
that
are
happening,
that
specific
part
of
the
codebase
and
giving
reviews
being
active
in
the
decision-making
process
for
that
code.
B
So
I
know
for
us
at
least
it's
not
like
a
super
formal
process,
but
as
soon
as
you
start
showing
you
know
that
level
of
contribution
and
that
level
of
involvement,
it
makes
sense
for
everyone
else
to
start.
Listening
to
your
opinion
on
what
you
have
to
say
there
and
then
you
slowly
become
you
hear
that.
F
Well,
I,
don't
have
so
much
to
it,
because
the
product
management
area
and
6:00
p.m.
internal
is
have
been
different
from
from
all
other,
like
more
technical
and
more
coding.
Six
at
the
same
time,
Dementors
is
stiffin
mentioned
before
so
you
have
to
be
active
if
you're
a
active
field
be
organized,
but
it's
community
and
one
day
you'll
be
promoted
to
be
maintained
and.
D
So
to
speak.
Oh,
how
do
you
become
a
reviewer?
How
do
you
become
approver?
How
do
you
become
a
maintainer
or
lead
in
this
thing,
but
one
of
the
things
that
I
guess
I
want
to
point
out
is
that
as
a
maintainer
there's,
an
increased
level
of
commitment
and
responsibility
that
is
is
when
it's.
Your
full-time
job
is
a
lot
easier
to
take
on
when
it's
not
your
full-time
job.
D
I
mean
even
as
an
envoy
person
for
six
months,
you
know
maintained
at
the
same
time
was
like
wildly
stressful,
so
I
just
want
to
point
out
that,
like
if
you're
totally
pumped
about
open
source,
but
you
don't
think
you'll
be
able
to
commit
to
basically
having
to
be
some
part
of
a
side,
job
or
gig
for
a
certain
period
of
time.
You
may
want
to
think
about
your
own
mental.
D
D
You
can
do
a
lot
of
the
things
that
are
associated
with
being
a
maintainer
without
actually
having
like
the
commitment,
and
that
may
be
a
good
place
to
hang
for
a
while
until
you're
there
so
super
invested.
You
really
just
need
to
be
a
maintainer
because
you're
out
of
strong
opinions
or
because
maybe
it's
become
somehow
related
to
your
job
and
someone's
gonna
help
support
you
in
doing
this
without
having
to
take
away
from
your
own
personal,
like
sanity,.
D
Shop,
a
day-long
workshop
before
gopher
yeah
and
a
big
part
of
this
is
talking
about
not
doing
that
first
PR
of
picking
a
project,
but
how
do
you
sustainably
just
be
involved
in
open
source?
How
do
you
move
up
these
ladders,
regardless
if
it's
kubernetes
or
or
NGO
or
Python
community,
or
anything
like
that
and
find
a
sweet
spot
so
that
it
doesn't?
It
doesn't
burn
you
out
and
also
kind
of
like
a
lot
of
things
we
talk
about
with
a
contributor
experience
related
to
like
how
do
you
welcome
two
people
in
your
community?
D
How
do
you
make
a
community?
That's
easy
for
people
to
join
and
have
it
be
inclusive?
There's
me
a
lot
of
stuff
like
that,
and
the
flipside
is
how
you
evaluate
a
community
for
these
things.
I,
don't
know
the
burnout
thing
I've
done
I
burned
out
and
had
to
like
quit
my
job
like
twice,
probably
because
of
stuff
like
this,
that's
near
and
dear
to
my
heart,
but
you
know
I,
don't
want
to
bring
people
in
and
then
immediately
set
them
up
for
her
take
six
months
down
the
road
yeah.
A
All
good
all
good
points,
Carolyn
all
right.
That
was
a
really
good
intro
question.
I
saw
it
let's
get
to
the
next
question.
The
next
question
is
also
from
T,
who
asks
great
questions
by
the
way
the
community
is
great.
It
makes
me
curious
about
other
projects
going
on
and
what
it's
like,
oh
I,
bet
yours,
gonna,
chime
in
on
this
one,
for
lack
of
a
better
word,
I
find
myself
to
be
project
promiscuous,
but
also
feel
loyal.
A
F
Yeah,
so
speaking
about
the
projects
within
CN
CF
and
within
within
the
existing
projects
in
CNC
of
projects
like,
for
example,
we
had
helm
that
was
a
part
of
cabinet
is
coming
in
what
it
was
like
that
affect
the
community
side
projects,
so
the
best
way
of
picking
up
the
right
project
for
you.
Where
can
you
contribute?
Where
can
you
work
on
and
where
I
can
you
find
some
benefits
being
a
contributor?
It's
like
the
dead
project,
where
you
can
the
dead
project
that
you
can
use
an
everyday
basis.
F
So,
for
example,
my
story
I've
been
involved
in
two
cabinet
it's
around
three
years
ago
and
how
I
made
my
first
metric
urban
areas
was,
was
about
like
I've,
been
reading
the
documentation
for
kubernetes
and
I
found,
if
you,
if
you
embrace
this,
where
can
I
submit
my
fix
and
after
that
I've
started
contributing
to
connect
us
on
the
databases.
So,
if
you
find
any
other
project,
not
only
kubernetes,
but
any
other
project
in
in
this
in
the
open
source
world
can
be
communities
it
can
be.
F
Any
other
cnc
of
project
can
be
even
any
other
open
source
project
internally.
Please
start
contributing
their.
Please
start
looking.
What
are
the
guidelines
for
the
traditions?
Are
there?
Some
of
the
projects
can
be
much
more
friendly
for
the
new
contributors,
as
we
are
here
to
be
noticed
some
or
not.
At
the
same
time,
all
the
open
source
projects
should
accept
any
external
links
to
any
kind
of
external
contributions,
and
even
if
your
first
contribution
will
be
denied,
you'll
receive
the
available
experience
of
watching
you.
F
The
next
with
your
next
mission,
also
speaking
about
contributions,
not
only
coding,
contributions
are
available
contribution,
but
also
runnin.
The
meetup
groups,
runnin,
the
local
communities
rentable
community
speaking
at
public
events
and
so
on,
are
all
a
source
of
community
contributions
and
actually
speaking
about
the
communities
community,
have
an
amazing
contributor
experience
group
who
is
which,
which
is
driving
this
oldest
effort.
D
A
B
Guess
I
would
say,
like
especially
inside
of
communities
or
I,
think
a
general
if
you're
looking
for
different
projects
that
contribute
to
in
my
personal
experience,
I
have
found
it
easier
to
contribute
the
things
I
use
so
technology
that
I'm
using
ideally
basis
if
I
notice.
There
are
things
that
are
you
know,
maybe
I
would
improve
or
something
bugging
me.
It
also
lets
you,
you
know,
make
a
little
bit
more
informed
of
a
decision
as
to
what
you're
going
to
work
on
instead
of
just
looking
at
an
issue
list
and
looking
for
Help
Wanted
tags.
B
Recession
and
day
to
day-
and
you
can
make
a
contribution
that
has
that
level
of
similarity
city
I
may
be
as
you're
using
super
daddy's
if
you're
noticing
oh
cool,
these
apps
are
really
awesome
and
we
go
look
at
suggest
or
low.
You
know:
API
servers
like
a
really
awesome
piece
of
equipment
there
in
the
middle.
Let
me
go
talk
to
those
people,
that's
how
I
personally
would
would
look
at
different
options.
D
I
think
that
there's
two
different
ways
to
kind
of
look
at
it,
so
one
like
I'm,
a
new
contributor
everywhere
I
go
I,
contribute
to
whatever
I
have
like
a
stake
in
or
an
itch
to
scratch,
or
whatever
a
bug
that
I've
hit.
It
was
kind
of
fun,
but
every
single
one
of
those
new
PRS
like
it
could
be
within
different
SIG's
or
it
could
be
completely
unrelated
project
with
different
languages
all
across
the
internet.
Is
you
get
a
feel
for?
Like?
D
Are
these
people
you
want
to
do
fun
stuff
with
or
not
because
part
of
the
reason
like
you're,
giving
up
your
time,
you're,
giving
them
honestly
free
work,
and
some
places
are
more
worthwhile
to
do
that
than
others.
So
like
say
here,
you're
not
really
sure
you
want
to
do
open-source,
we're
not
really
sure
like
who
are
the
fun
people
I'd
like
to
do
things
with.
It's
do
a
couple
good.
You
do
couple
PRS
in
different
areas.
One
you'll
start
seeing
some
of
the
same
people.
D
It's
not
just
like
one
cig,
I,
wonder
stays
by
themselves
like
you're
gonna
start
seeing
friendly
faces
in
all
these
different
ones,
and
some
people
may
be
in
a
great
position
to
help
mentor
and
bring
you
onto
the
cig.
And
if
you
just
do
one
and
try
to
stick
with
a
single
cig,
you
may
not
find
actually
that
there
is
another
place
somewhere
else
that
maybe
would
have
been
a
super
welcoming
home.
But
then,
after
a
point,
you
kind
of
realize,
like
these
people
are
fun.
D
I
like
chatting
with
them
on
slack
they've,
been
super
helpful
at
teaching,
meaning
ego
more
things
about
kubernetes
and
I
feel
like
they
appreciate
my
effort.
It's
welcome
and
that's
when
maybe
you
start
sticking
around
a
little
bit
more
and
it
may
not
be
one
stick.
It
may
just
be
wherever
I
find
Paris.
That's
where
I'm
gonna
be
to
things
like
that,
because
part
of
the
point
in
getting
an
open
source
is
easier,
scratching
an
itch
or
you're
you're
trying
to
be
a
member
in
in
this
community
in
the
criminals.
D
Community
is
big
and
you
can
end
up
going
many
places
and
seeing
the
same
people
are
dealing
building
up
a
reputation,
maybe
not
just
in
a
cig
but
across
the
whole
community,
so
go
where
it
interests
you
and
be
with
the
people
who
make
you
feel
like
this
was
the
right
choice
and
the
right
way
to
spend
your
time.
I
guess
be
my
recommendation.
A
B
F
A
Worry,
okay,
that
is
awesome
sounds
like
we've
got
some
good
open
source
citizens
on
the
call
which
is
awesome.
Alright,
next
question
is
from
Adm.
It
is
a
testing
related
question,
so
Steve
this
might
be
you
first.
Unless
anyone
else
wants
to
chime
in
they
asked.
Does
everything
really
need
an
end-to-end
test.
B
If,
in
order
to
test
something
appropriately,
I
think
if
it's
a
large
enough
like
component,
you
start
looking
at
testing
specific
parts
of
that
component
individually
in
unit
tests,
and
you
might,
for
instance,
if
it's
changed
at
keep
CTL
you're
going
to
end
up
writing
the
CFD
tests
in
fashion
stead.
End-To-End
testing
is
going
to
have
complex
like
cluster
level
or
you
know,
deployed
on
the
cluster
level.
B
Behaviors
you
want
to
validate,
and
ten
tests
are
pretty
heavyweight
and
so
generally
I
think
the
one
of
the
things
that
stick
testing
has
set
up
a
lot
of
types
of
their
contributors
in
our
in
our
meetings.
If
you
can
achieve
the
testing
without
actually
standing
up
a
cluster
without
meeting
an
edit
or
a
hollow
node,
don't
go
to
that
level
of
complexity
like
sometimes
they
might
be
really
simple.
B
As
you
just
chew
up
there
and
there's,
you
know
a
lot
of
fray
versus,
but
you
can
lean
on
when
you're
writing
an
end-to-end
test,
but
at
the
same
time,
you're
picking
up
a
huge
amount
of
complexity
and
I.
Think
one
of
the
things
that
you
always
need
to
keep
in
mind.
When
writing
tests
is
it's
always
a
trade-off?
B
It's
not
a
simple.
Oh
we
on
tests
are
always
good,
more
testing.
His
owns
better,
as
you
add
tests,
especially
tests
that
are
relying
on
never
connectivity,
you're,
adding
possibilities
and
flakes,
and
even
if
your
code
is
perfect
like,
for
instance,
if
you
had
a
test
that
was
reaching
on
it,
but
the
network
that
network
isn't
and
so
we're
busy
flakes
from
that,
sometimes
and
so
you're.
Adding
tests,
which
increase
would
like
likelihood
of
flakes
in
the
future
you're
adding
tests
that
increase
the
time
it
takes
to
run
actual
suite.
B
So
you
always
have
to
consider
the
test
of
the
trade-offs,
and
so,
if
you're
testing
a
fairly
simple
small
change
going
to
an
end-to-end
test
or
anyway,
it
may
not
be
the
right
solution.
However,
if
you're
reading
a
massive
component
and
test,
you
can
be
critical
to
make
sure
it
works
very
cool
yeah,
so
I
guess
I
would
think
about
it.
That
way,.
D
Have
just
one
thought
which
is
it
depends
on
where
it
is.
You
made
the
change,
no
one
likes
to
run
a
five-minute
test
and
then
iterate
on
it
and
then
figure
out
that
like
what
they
did
doesn't
work.
So
if
you
can
write
a
unit
or
an
integration
level
test
or
use
the
fake
client
or
something
like
that
and
you're
able
to
fully
exercise
the
interesting
parts
of
your
code
and
it's
error,
behaviors
and
edge
cases
like
you'll,
save
yourself
so
much
time
and
it'll
be
way
to
easier
to
debug.
D
A
All
right,
good
responses,
and
the
next
question
comes
from
de
BBC
Garcia
in
the
meet
our
contributor
slack
channel.
It
sounds
like
they're
coming
from
the
SIS
ops,
world
and
they're
only
an
enthusiast
about
golang,
but
they
want
to
start
contributing
to
kubernetes.
Is
how
difficult
is
it
to
get
set
up
in
terms
of
understanding
the
codebase
improver
Nettie's
and
do
a
first
PR?
Do
they
need
to
know
golang
to
do
so?
A
F
Answer
as
a
person
from
the
excess
of
Scrolls,
yes
take
it
away.
So
it's
not
it's
not
a
strain,
a
strong
requirement
for
you
to
know
going
to
contribute
something
to
the
villages.
That's
not
not.
On
the
devolved
code
base
of
the
Vanaras
consists
of
:
files.
We
have
enough
enough
documentation,
for
example,
enough
really
smells
enough
enough
items.
F
Where
can
you
contribute
based
in
your
sisters,
experience
we
can,
for
example,
the
communities
example
3
or
where
we're
collecting
the
best
examples
from
the
world
of
health
and
iran
in
cabinet
isn't
a
difference
in
errors,
and
if
you
have
learned
some
basic
concepts
and
if
you,
if
you
have
noticed
some
interest
in
scenarios
where
you
can
run
through
analysis,
some
implications
of
the
kubernetes
and
you'd
like
to
share
with
the
world,
please
submit
it,
be
our
objective
in
ODIs
example
straight.
So
the
basic
answer
is
no.
F
B
Say
I
say
also:
don't
I
mean
if
you
have
experience
with
code
just
in
general,
I
think
one
of
the
huge
upsides
of
going
as
a
language
is.
It
is
so
simple,
I
think
it's
got
a
pretty
small
feature
set
and
starting
off
without
being
a
go
language,
service,
perfect
and
I.
Think
I
mentioned
before
too,
like
looking
for
projects
that
you're
interested
in
contributing
to
I.
B
Think
one
of
the
things
that's
going
to
make
it
easier
as
a
contributor
is,
if
you
find
a
specific
part
of
kubernetes
that
you're
interested
in
maybe
looking
at
demos
for
the
different
stages
and
looking
at
something
that
really
piqued
your
interest.
Trying
to
understand
the
community
code
base
as
a
concept
I
think
will
be
impossible
for
most
mere
mortals
and
so
I,
wouldn't
necessarily
start
by
trying
to
read
from
the
top
down.
B
Oh
yeah,
fine,
fine,
a
demo!
That's
really
cool,
find
something
that
really
interests
you
and
then
seek
out
that
cig
and
look
for
help
issues
and
starts
small
and
if
you're
starting
small
you're
going
to
be
reading
just
a
little
bit
of
code
and
changing
just
a
little
bit
of
code
and
as
you
do
that
you're
going
to
gain
more
familiarity,
go
and
I.
F
D
Just
trying
to
be
polite,
no,
if
you're
experienced
with
code
in
general
I
like
to
dive
in
on
the
like
the
outer
edges
of
a
project
so
that
it's
easier
to
get
in
and
exercise
it.
So
the
CLI
or
edges
of
the
API
are
often
a
lot
easier
to
jump
in
when
you're
not
familiar
the
language,
because
you
don't
have
to
figure
out
how
to
like
get
a
whole
cluster
up
and
running
and
then
tweak
random
things
and
install
it.
D
If
I
play
the
home
game
for
PRS,
I
think
a
spot.
We're
like
maybe
they
have
lots
of
good,
first
PR
or
Help
Wanted
PRS,
but,
like
not,
everyone
can
do
that
one
issue,
but
you
can
always
just
kind
of
do
it,
along
with
them
at
home,
like
all
either
watch
their
PR.
If
I
know
cool
or
solve
it
and
watch
the
comments
as
they
come
in
and
see
like.
How
did
someone
solve
it?
What
are
some
of
the
feedback
pieces?
Maybe
they
got
on
the
language
in
particular,
some
goes
hey.
D
Did
you
know
what
channels
are
or
something
like
that
or
maybe
I'll
try
it
out
myself
and
then
see
when
someone
submits
a
final
PR,
four
and
it
gets
merged.
Does
that
look
anything
like
mine
and
that
just
kind
of
can
help
you
build
out
a
little
bit
more
comfort
with
an
area
of
code
and
see
how
other
people
are
doing
it
and
go?
Oh
actually,
I've
kind
of
done
that
myself
I
could
have
submitted
that
PR.
D
It
was
pretty
darn
close,
that's
another
good
way
to
do
stuff,
but
otherwise
I
would
say
that
if
you
are
very
new
to
programming,
make
sure
that
when
you
are
jumping
in
that
you
aren't
leaning
too
heavily
on
the
people
who
are
helping
you
to
teach
you
the
language,
that's
something
that
people
love
to
help.
But
if
you,
if
you
don't
know
the
language
like
make
sure
that
you're
doing
a
bit
of
due
diligence
on
your
own
part
as
well,
to
figure
out
how
to
set
up
your
machine
it
just
how
needy?
D
A
C
Yeah
well,
I
mean
I,
don't
see
the
the
difference
between
you
know
the
kind
of
personage
live
and
talk
about
ops
and
developers
like
I,
think
they
often
have
very
similar
skill
set.
It
just
concerns
a
bit
different
right.
Maybe
some
people
yeah
so
yeah,
but
like
what
people
think
one
side
was
pretty
good.
Equally
somebody
somebody
doesn't
doesn't
actually
when
I
write
code
and
would
you
contribute
to
the
project.
The
conversation
is
a
great
place
to
start.
A
A
H
B
Yeah
I
mean
the
fact
that
I
get
paid
to
contribute
to
keeping
at
ease
I'm
super
grateful,
that's
sort
of
a
miracle,
the
technology's
awesome.
It's
really
really
exciting
and
I
think
past.
That
too,
like
especially
in
suggesting
it's
very,
very
open
and
I
found
the
contributing
you
know
with
numbers
from
five
or
six
different,
like
companies
different
different
viewpoints,
different
focuses,
different
goals
like
we
just
make
it
work,
and
that's
super
awesome.
F
Second,
they
are
speaking
about
the
best
way
of
running
applications.
Botanicals
added
as
the
best
way
to
run
applications
are
running
them
in
containers,
but
kubernetes
is
the
best.
Is
the
best
tool
set
to
run
them
on
any
scale,
probably
except
a
few
local
left,
but
even
even
if
on
your
local
application,
dude
we're
skipping
areas.
At
the
same
time,
Dominica's
was
born
as
as
the
orchestration
orchestration
toolset,
but
today
is
not
only
it's
not
a
little
technology.
F
It's
that
really
big
ecosystem
and
a
big
group
of
smaller
big
projects
and
looking
at,
for
example,
the
scale
of
de-risking
conference
in
Copenhagen,
where,
with
more
than
4,000
attendees,
you
can
notice
that
not
only
not
all
these
people
were
interested
in
to
Banaras
itself,
not
only
environment.
Some
applications
whisk
the
notice,
but
there
have
been
so
many
people
who've
been
interested
in
some
other
certificate
ratios
positives
and
using.
D
F
D
It's
not
that's
not
why
I
contribute
to
it
like
I,
think.
A
lot
of
things
are
really
cool,
but
are
super
intimidating
or
scary
to
work
on
like
you'll,
never
see
me
like
I'm
a
Linux
kernel
maintainer.
What
was
trying
to
do
things
but
I've
always
been
really
interested
in
helping
other
developers
so
I'm
going.
You
always
find
me,
like
writing.
Little
C
lies
or
oh
I'm,
like
the
person
who's
like
setting
up
a
Jenkins,
build
or
eventually,
like
oh
I'll,
turn
this
into
ansible.
D
You
know
chef
or
something
for
you
and
then
and
then
I'm
like
I
can
make
one
master
build
script
to
rule
them
all.
I
hope
you
do
stuff,
and
then
here
are
all
these
things
that
can
help
you
debug
in
production
and,
like
those
are
the
things
I,
love,
I,
hate
being
on
a
call
and
like
I'm,
not
that
great
at
understanding,
customers
who
want
me,
but
I
I
like
doing
things
where,
because
it
feels
that
the
feedback
loop
is
very
strong
and
it
makes
you
feel
good
about
what
you're
doing
so.
D
You
know
I
liked
containers,
which
is
fun
and
I
started
using
kubernetes
for
my
own
silly
things
and
when
I
realized
how
nice
everyone
was
in
the
kubernetes
community
and
we're
just
super
welcoming
and
not
scary
and
weren't.
Calling
me
names
or
I
didn't
have
to
be
a
very
elite,
CS
type
person
who
knew
algorithms,
like
don't
tell
Microsoft
I,
don't
do
that
rhythms.
You
know
there
is
that
kind
of
stuff.
G
G
Think
now
you
know
we
figured
out
single
node
I
have
a
Linux
server
right,
like
that's
great,
but
you
know
at
some
point
as
you
move
up
the
stack
it's
like
the
problems
are
trying
to
solve
are
now
so
much
more
complicated
than
than
the
simple
projects
that
like
I,
started
out
with
right
and
I.
Just
think
it's
for
a
lot
of
people
I
think
there's
a
challenge
there
and
it
it
really
helps
that
kubernetes
is
kind
of
a
newer
project
as
well,
so
it
you
know
it
was
smart
enough
to
say.
G
Without
you
know
it
kind
of
turning
into
you
know
like
this
kind
of
elites,
only
kind
of
thing
right,
there's
like
there's,
always
a
place
for
you
to
go,
because
the
problem
is
so
complex,
I
think
it
draws
people
who
who,
like
that
kind
of
challenge,
you're
trying
to
solve
things
but
like
normal
people,
don't
get
to
mess
with
like
at
all
right.
You
know
five
years
ago
you
had
to
work
at
Google
or
at
Facebook,
or
something
to
see
these
kind
of
things.
Now
anyone
can
kind
of
get
started
into
this
thing.
A
So
next
question
actually
has
to
do
with
code
reviews
DM
from
a
current
member
who
is
active
in
many
SIG's
and
making
different
levels
of
contributions.
They're
kubernetes
path,
if
you
will
they'd
like
for
it
to
be
a
reviewer
in
an
owner's
file,
I
guess
for
some
folks,
also
watching
if
you
could,
if
panelists
could
just
maybe
describe
what
an
owner's
file
is,
but
anyway,
what
are
some
tips
for
kubernetes
code
reviews
and
how
they
can
do
them?
Well,.
A
It's
more
like
what,
when
they're
reviewing
I,
think
the
wording
was
a
little
off,
but
it's
like
more
like
how,
when
they're
reviewing
PRS,
what
are
some
tips
for
for
actually
reviewing
the
code
for
the
review
itself.
If
they're
the
review,
yeah
yeah,
it
sounds
like
they
want
to
be
a
review.
It
sounds
like
they
are
trying
to
get
some
experience
for
code
reviewing
under
their
belt
and
they
want
to
make
sure
that
they're
doing
it
right.
Yeah.
D
I
like
to
try
to
ignore
as
much
as
possible
how
I
would
have
solved
the
problem,
because
I
feel
it's
really
easy
to
derail
a
PR
by
basically
using
your
comments
to
turn
the
code
into
what
you
would
have
wanted
to
have
written.
So
that's
pretty
important
to
go.
I
may
have
a
feel
or
a
thought
about
what
I
see
here,
but
does
it
impact
the
final
solution?
D
Will
this
causes
problems
and
if
no
exhibit
and
just
be
like,
let
it
go
P
Elsa,
whatever
your
name
is
frozen,
and
so
that's
like
one
big
thing
another.
Is
that
I
like
to
use
it
as
an
opportunity
to
to
ask
questions
and
explore
different
avenues
of
things
like
one
I
use
my
reviews
as
a
way
to
learn
so
sometimes
you'll,
see
something
and
you'll
be
like
I
have
no
clue
what
they
just
did
and
you
can
have
a
couple
different
reactions
to
that.
D
You
could
look
at
it
and
be
like
what
the
heck
are
they
doing.
This
doesn't
make
any
sense
and
you
can
get
kind
of
like
grumpy
at
the
person
or
you
can
look
at
it
as
an
opportunity
to
go.
Maybe
they
know
something
about
the
language
that
I
don't
and
you
could
you
could
ask
about
that
and
go
hey.
What
are
you
doing?
I'm
just
curious
I
put
I'm
just
curious
in
front
of
a
ton
of
things
so
that
people
understand
it's,
not
a
criticism.
D
It's
a
me
seeking
some
a
little
bit
of
sharing
and
knowledge
from
them,
which
also
makes
the
relationship
with
with
people
alike
smoother.
If
you
don't
come
off
as
like
accusatory,
so
that's
that's
one
thing,
but
just
otherwise
try
to
just
check
some
of
the
boxes
of
like
if
this
goes
in
the
way
it
is
right
now.
Is
it
making
things
better?
D
Can
we
build
on
it
or
we
just
made
a
bad
committed
master
and
as
long
as
we're
avoiding
that
I
like
to-
and
this
is
maybe
just
a
service
catalog
same
thing-
I,
don't
know
if
this
is
a
big.
You
know
kubernetes
repo
thing,
but
we
really
like
the
concept
of
iterative
PRS.
So
we
may
come
up
with
like
a
another
thing.
We
want
to
be
able
to
do.
We
look
at
it
and
get
some
cool
idea
and
of
asking
them
to
continually
shove
more
things
into
their
PR
change
things
around
we
may
go.
D
This
is
perfectly
fine.
If
we
ship
this,
as
is
we've
got,
the
pass
is
not
going
to
cause
trouble
and
then
we'll
give
them
info
like
hey
as
a
follow-on.
If
you
could
give
us
another
PR
that
did
this.
That
would
be
super
helpful
and
it's
kind
of
nice
too,
because
it
helps
that
person
come
back
and
do
more
contributions
in
a
similar
area
and
it
builds
up
their
confidence
and
they're
more
likely
to
come
back
and
be
regular
contributors.
D
So
that's
kind
of
important
to
me
and
the
other
thing
is
when
you
have
feedback,
but
it's
not
going
to
cause
you
to
reject
the
PR
I
like
to
call
that
out
and
be
like
this
is
in
South
Carolina.
We
use
determine
it
which
I
I
was
not
familiar
with,
but
oftentimes
people
just
say
knit
this
or
I
usually
say
like
this
is
fine.
D
B
I
think
the
first
to
the
question
of
what
is
an
owner
smile
and
how
do
they
work
so
the
automation
that
we
are
running
for
they
keep.
Ladies
or
brings
up
ownership
of
code
into
directories
and
the
specific
owners
of
a
directory
are
listed
in
a
little
file
in
that
directory.
And
so,
when
you
create
a
PR
depending
on
which
file
you're
touching
people
that
are
those
zip
files,
are
actually
pulled
out
and
automatically
assigned
to
review
your
here.
So
as
far
as
owner
smiles,
like
that's
what
best
meeting
and
really.
B
A
proxy
for
being
a
maintainer
or
a
good
reviewer
for
that
for
that
area,
as
far
as
like
actual
reviews,
yeah
I,
think
because
I
have
some
really
good
points.
It's
like
you
have
to
keep
in
mind
at
all
times
that
yeah
writing
code
is
like,
like
an
artistic
process,
there's
never
one
right
way
of
doing
something
and
keeping
your
own
personal
opinions
of
how
you
would
solve
it.
Kind
of
back
is
super
super
positive
as
a
piece
of
feedback.
I
actually
had
a
list.
Since
this
question
came
up.
B
That's
the
other
point,
there's
questions
you
can
ask
as
a
reviewer
and
I
guess.
Some
of
these,
like
really
depend
on
how
comfortable
you
are
with.
This
is
a
piece
of
code,
but
is
this
a
change
that
we
want?
Does
it
move
in
the
right
direction
and
if
it's
not,
maybe
there
should
have
been
a
design
dog
that
came
up
first,
where
you
know
people
have
shout,
is
this
something
we
actually
are
looking
for
and
if
it
is,
how
do
we
want
to
get
there?
B
B
Is
the
code
here
follow
that
and
especially,
and
not
so
much
a
QA
system
for,
but
I
think
like
in
some
of
the
other
authentic
systems
that
I've
worked
on
personally
I,
sometimes
they're
bash
scripts
or
they're
Python
scripts-
and
you
know
things
are
kind
of
willy-nilly
put
it
when
you
start
breaking
those
abstractions
down
the
line,
you're
picking
it
up.
Ted.
B
Yeah,
if
it's
an
entirely
new
feature
being
added,
is
it
being
at
it
as
a
sub
component
of
something?
Are
we
testing
it?
How
does
it
fit
in
and
is
it
fitting
into
the
right
place
if
the
changes
going
in?
What's
the
impact
on
SAP
that
are
we
increasing
type
that,
if
we
are,
is
it
reasonable,
like
that's
another
thing
that
isn't
always
a
block
and
why
you
should
never
increase
tech,
that
I,
guess
and
I
think
you
know
the
comment
about
iterative
PR
is
an
example
of
this
like
oftentimes.
B
It
makes
a
lot
of
sense
to
get
something
in
that
works
is
pretty
cool,
but
you
maybe
has
second,
or
maybe
it
has
the
roof
room
for
improvement
later,
but
just
being
cognizant
that
you're
thinking
up
like
that
you're
doing
it
on
purpose
because
you
can
fix
it
later,
like
keeping
that
in
mind,
is
good
when
you're
doing
their
review
so
that
you
could
say
well
over
like
this
is
a
little
bit
too
much
or
like
this
is
cool.
We
can.
B
We
can
fix
it
later
and
are
you
leaving
the
code
that
you're
testing
in
a
good
place
for
somebody
else
to
come
in
after
you
are
there?
A
bunch
of
to
dues
is
a
kind
of
cryptic
like?
Are
you
holding
the
code
I
you,
the
person?
That's
writing
the
code
like?
Are
they
holding
the
key
sticking
them
or
are
they
leaving
it
in
a
place?
That's
like!
Oh,
you
know.
If
they
look
at
the
previous,
commit
it's
clear
where
this
is
going.
B
If
we're
fixing
a
bug,
I
think
it's
often
time
is
a
really
really
good
place
to
add
testing,
to
make
sure
that
that
bug
never
comes
up
again.
Sometimes
bug
fixes
of
that
test
involved.
You
have
to
think
about
okay.
So
why
are
we
not
going
to
have
the
same
problem
in
a
month?
Are
we
going
to
make
sure
this
doesn't
happen
again
and
then?
Similarly,
if
we're
adding
features
like,
is
it
tested
at
the
right
level?
B
B
You
know
you
don't
need
to
go
in
assuming
that,
assuming
nothing
right,
it's
fine
to
go
in
having
assumptions,
but
just
making
sure
that
you
keep
those
in
mind
so
that
in
the
future,
if
you're
changing
it,
if
someone
else
is
changing
it
like
that
code
is
still
going
to
be
working
and
then
I
think,
especially
as
you
are
reviewing
code,
maybe
that's
more
like
in
the
control
put
side
of
things
like:
what's
the
inside
a
failure
month,
is
it
reentrant?
Is
it
failsafe?
B
Is
it
going
to
clean
up
after
and
stuff
like
it's
an
eventually
consistent
system
that
drives
kubernetes
like
this
is
fit
into
that
failure
mode,
and
is
it
clear
how
this
code
is
supposed
to
fail?
He's
taking
care
of
failures
is
just
as
important
as
taking
care
of
the
happy
path
where
everything
works.
A
A
Ok,
yep
nope,
we're
good
and
all
right,
I
think
we
should
wrap
it
here
before
we
get
into
any
more
questions.
First
things.
First,
thank
you!
So
much
to
the
panelists,
you
all
were
very
awesome.
I
love
all
of
your
different
perspectives,
you're
in
so
many
different
things
and
different
projects
and
different
parts
of
the
communities.
So
it's
lovely
having
all
of
your
voices
here
thanks
to
George
for
live-streaming
us
and
making
us
as
awesome
as
possible.
A
Hopefully
we
all
look
beautiful
on
the
Internet
George,
you
better
be
doing
your
job
and
our
next
session
is
going
to
be
in
about
four
and
a
half
hours.
If
you're
watching
watching
us
live
if
you're
recorded,
then
you'll
just
hit
play
or
if
you're
watching
the
recording
you'll
just
hit
play
so
I
will
see
everyone
on
the
kubernetes
interwebs.
Thank
you.
So
much
see
you
later
bye.
Everybody.