►
From YouTube: Meet Our Contributors 20180905
Description
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.
See https://contributor.kubernetes.io/mentoring/meet-our-contributors/ for more information
A
Sorry
ready,
let's
go
alright
hi
everyone
welcome
to
the
September
edition
of
meet
our
contributors.
This
is
our
first
session
of
the
day.
The
next
session
will
begin
at
1
p.m.
Pacific
and
that's
8
p.m.
UTC
check
your
local
timezone.
For
that
today,
we're
joined
by
three
awesome
contributors
to
kubernetes
and
also
George,
who
is
community
manager?
We'll
do
some
introductions
in
a
second
first
things.
First,
we
do
abide
by
the
code
of
conduct
that
the
CNC
F
has.
A
So
if
you
are
in
the
meet
our
contributors
select
Channel
right
now,
hanging
out
with
us
or
if
you're,
on
Twitter
or
anything
like
that.
Please
be
excellent
to
each
other
panelists.
You
are
allowed
to
ask
each
other
questions.
Mentorship
does
not
mean
it's
a
one-way
street,
so
feel
free
to
ask
each
other
any
questions
as
well,
and
then,
let's
see
I,
think
that's
it.
For
me,
my
name
is
Paris
I
work
at
Google
and
my
career
DS
community
manager
and
let's
go
with
some
introductions
Joel.
A
B
Hi
I'm
Joel
I
work
for
startup
in
Shoreditch,
London
called
pusher
I'm
a
cloud
infrastructure
engineer,
so
my
day-to-day
mainly
is
running
Kiva
Nettie's
we've
got
a
bunch
of
products
that
run
on
top
of
the
platform,
so
yeah,
that's
sort
of
where
I
go
into
communities.
When
I
joined
the
company
15
months
ago,
I
started
working
at
kubernetes
and
since
then
have
been
sort
of
fixing
bugs
and
stuff
when
I
can
and
contributing
back
as
much
as
possible.
Yay.
E
D
I'm
a
contributor
for
almost
three
years:
I'm
I'm,
a
co-lead
of
culture
of
CPM,
the
sig
that
is
focused
on
different
aspects
of
product
and
program
management
within
communities.
Community
I
am
NOT.
A
developer.
I
am
not
focused
on
developing
a
code
but
I'm
here
to
help
you
with
making
decisions
in
any
non
contribute
non
non
coding
specifics
in
contributions
to
cabinets.
D
F
Everybody
so
I
have
to
protect
my
camera
from
the
cat,
which
just
arrived:
I'm
Stefan
I'm
working
for
Palakkad
as
a
developer
and
I'm
a
devotee
in
Europe,
so
you
can
kind
soul,
I
started
with
kubernetes
when
I
was
freelancing
for
measles.
Actually,
I
put
me
on
to
the
comedian's
project.
I
worked
on
that
from
my
notes.
We
have
years
ago
nearly
get
plenty
of
contributions
in
all
areas
recently
mainly
focus
on
custom
resource
definitions.
Those
guys
are
behind
that
API
server
in
general,
in
epi,
machine
Yui
and
a
lot
of
reviews
and
approvals.
F
E
A
Thanks
to
George
for
making
us
live
right
now,
this
will
also
be
recorded.
So
if
you
need
to
jump
off
for
any
reason
because
you're
in
a
meeting
or
what
have
you,
you
can
always
check
back
with
us
in
a
few
hours
on
the
YouTube
channel,
because
we
will
have
the
have
this
broadcasted
all
right.
Let's
go
into
our
first
question.
This
is
from
a
from
a
DM
that
I
received
on
slack
also
for
those
who
are
watching
and
want
to
engage
with
us.
A
We're
in
the
meet
our
contributor
slack
channel
on
the
Cates
instance
also
going
to
be
checking
Twitter
periodically,
but
not
as
much
as
slack.
So,
if
you
pass
your
your
Twitter
comment
as
k8s
MOC
for
kubernetes
meet
our
contributors,
I
will
find
it
now.
First
question
is:
do
you
remember
your
first
contribution?
A
B
I
actually
do
yeah.
It
was
only
about
a
year
ago
it
was
the
cluster
autoscaler.
There
was
quite
a
large
bug
which
I
actually
fixed
like
on
a
Saturday,
because
we
saw
it
hit
our
production
instances
on
the
Friday
evening
caused
a
page
event,
so
someone
got
woken
up
and
then
on
the
Saturday
I
was
like.
That
is
a
really
big
bug
we
eat
fix
us.
So
it's
been
like
all
day.
B
Saturday
hunting
for
I
think
what
the
bug
was
was
that,
if
no
because
it
was
part
of
the
crust
water,
scalers,
dynamic
discovery
of
auto-scaling
groups
in
Natal
us,
if
nothing
matched,
then
it
would
return
all
auto-scaling
groups.
So
one
of
the
cluster
water
skaters
that
was
running
on
one
of
our
test
clusters,
someone
disabled
all
of
the
auto-scaling
groups
from
the
cluster
autoscaler
and
then
suddenly
it
had
all
of
the
auto-scaling
groups
because
of
the
way
they
dress.
Api
works
and
started
randomly
turning
instances
off
in
different
clusters.
B
So
yeah
that
was
quite
a
big
thing
for
us
and
I.
Remember,
spending
a
whole
day
looking
for
it
and
finding
it
and
at
the
end
of
it
they
opened
a
PR
back
to
it
and
I.
Remember
one
of
the
contributors
with
a
comment
below
named
now,
but
he
was
just
like
okay,
this
fix
of
this
issue
this
issue
this
issue
this
issue,
because
there
were
so
many
issues
that
all
like
be
opened,
but
no
one
had
worked
out.
What
quite
what
it
was
so
I
was
quite
proud
of
that
one.
It
was.
B
B
In
terms
of
like
opening,
the
PR,
like
I,
found
the
contributing
docs
very
terse,
like
they
were
a
bit
hard
to
read
to
be
honest,
I
kind
of
sort
of
skimmed
over
bits
of
bone
because
it
just
didn't
seem
relevant,
but
you
know
like
there
is
the
humanities,
see
I
pop
tells
you
what
to
do
most
of
the
time
anyway.
So
I
think
that's
one
of
the
things
I've
sort
of
got
used
to
it's
like
tells
you
to
approve
approvers
and
stuff.
So
you
just
do
as
it
says,.
A
A
Oh,
please
feedback
is
more
than
appreciated
if
you
want
to
give
us
direct
feedback
file,
an
issue
or
feel
free
to
visit
us
in
the
in
the
kubernetes
Sinkin
Trebek
slack
channel,
always
soliciting
feedback,
so
Joel
I'd
love
to
hear
what
the
what
you
think
is
better
or
neat
still
needs
work
from
the
from
the
new
dock
and
the
rest
of
you,
your
Stefan,
for
do
you
remember
your
first
contribution
and,
and
what
was
the
hardest
part
about
it.
I
remember.
D
But
definitely
I
suppose
the
discussion
was
about
github
contribution
to
given
ettus
codebase,
and
my
first
contribution
was
fixing
a
few
lines
in
documentation,
two
minutes
so
as
I
mentioned
before,
I'm,
not
a
developer
but
I'm
a
person
who
is
distraught
and
DevOps
experience.
And
a
few
years
ago,
selected
kubernetes
started
to
look
into
given
it
as
good
DevOps
solution.
First
of
all,
for
my
personal
purposes
and
for
satisfying
my
engineering
needs
and
at
some
point
of
time,
I
figured
out
that
some
parts
of
documentation
was
incomplete
and
I
found
a
way.
How.
E
D
Submit
well,
first
of
all,
what
I
can
submit
there
I
found
a
way.
How
can
I
submit
it
to
to
Burnett
his
code
place
because
it
was
terribly
easy
given
different
different
episodes.
Projects
I
had
experience
working
on
so
that
first,
my
first
contribution
just
a
few
lines
in
documentation,
but
that
was
the
amazing
start
for
me
because
figured
out
that
it
was
terribly
easy
and
it
opened.
E
A
Awesome
and
docks
are
indeed
a
great
way:
I
call
them
the
gateway
drug
to
the
community,
because
it's
easy
for
users
to
jump
in
and
figure
things
out
and
figure
out
where
holes
are
and
then
also
get
used
to
how
we
do
business.
So
it's
definitely
a
good
example.
Your
thank
you
and
then
Stefano.
What
about
you?
I
didn't.
F
Fourteen
thousand
two
hundred
fifty
nine
so
like
fifty
was
fifty
thousand
Piazza
goes
over
at
the
wrong
time
ago,
was
about
just
moving
some
code
into
a
function
so
basically,
in
effect,
doing
very
simple,
but
it
cleaned
up
the
codes
and
made
it
a
bit
better
than
it
was
before
so
wasn't
complicated.
I.
F
F
The
second
thing
which
I
remember:
maybe
it's
much
better
today,
I'm
not
so
sure,
but
if
you
want
to
change
something,
get
to
tests
and
changing
something
just
as
a
code
and
it
compiles.
That's
fine
is
first
step
but,
most
importantly,
get
your
development
environment.
It
will
shake
where
you
can
really
test
the
whole
cluster,
so
there
are
ways
using
docker
into
cars
as
a
as
a
script
in
the
heck
directory
called
local,
faster,
a
complete
cluster
which
can
also
launch
pots
I'm
get
those
ready
in
your
on
your
notebook
on
your
on
your
computer.
F
So
you
can
test
things
and
last
but
not
least,
we
have
a
lot
of
integration
and
end-to-end
tests,
which
you
can
run
even
without
docker.
So
if
you
change
something
in
the
API
server
and
some
controller
you
can
run,
then
you
will
be
using
integration.
Your
end-to-end
tests-
and
this
can
be
just
fun
on
your
local
notebook.
It
only
competitive
was
that
was
just
process
which
ones
may
be
a
net
CD
which
you
need
and
yeah.
F
A
F
I
suppose
the
second
question,
of
course
you
have
slack
so
go
to
the
community
of
staff
general.
There
are
many
many
people
and
they
are
very
helpful.
That's
a
good
point.
There
are
plenty
of
blog
posts,
of
course,
and
just
documentation,
it's
usually
hard
to
find
those
things.
So
I
cannot
just
give
you
a
link
now
because
I
don't
know
either
so
I
have
to
go
before
it
or
even
ask
in
the
intersection.
So
I
think
that's
the
best
thing
for
me
to
do
if
Google
doesn't
hurt.
F
The
first
question
is
about
our
process:
how
to
get
code
into
a
project.
We
have
a
two
step
process,
so
we
need
to
have
use.
You
want
somebody
to
give
you
a
so-called
LG
Chem
it.
So
it
looks
good
to
me
comment
in
your
PR
on
github,
and
this
are
usually
quite
experienced
people
in
the
codebase.
You
are
changing
and
when
they
help
us
a
code
after
a
few
hours
of
abuse,
usually
they
will
gives
us
LG,
Chem
and
those
mentioned
in
those
files
called
owner
owner
kept
the
case.
F
Just
look
in
the
repositories
they
are
laying
around
in
the
packages.
The
second
step
is
approval.
You
need
somebody
who
really
owns
the
code,
and
these
are
many
far
fewer
people
who
owns
the
code,
maybe
three
or
so
a
two,
maybe
five
and
one
of
them
at
the
end,
has
to
agree
that
this
change
is
a
good
direction.
F
He
doesn't
say
we
look
into
every
detail,
you
change
every
comma,
but
he
says
this
is
a
good
direction
we
want
to
go
to,
and
this
is
usually
what
you
have
to
get
at
the
end
and
it's
often
harder
to
get
and
again
think
those
people.
If
they
don't
answer
after
several
days,
then
they
usually
do
most
of
people
are
approachable,
so
yeah,
usually
just
as
a
background
just
mentioning
people
and
get
up
requests
in
issues.
Mentoring.
F
People
is
this:
it's
usually
not
enough,
because
there
are
so
many
notifications
you
get
to
have
that
people
just
don't
see
you
especially
requests.
So
don't
be
surprised
if
you
just
mention
somebody
and
he
doesn't
answer
it-
it's
not
that
he
doesn't
want
to
answer.
Maybe
it's
just.
He
doesn't
see
that
you
support
something
and
you
request
some
information
or
some
approval
or
something
like
that.
A
Awesome
very
good
advice.
Yes,
we
do
have
50,000
people
on
our
slack
instance,
so
the
there
definitely
is
a
lot
of
noise
as
people
consider,
but
at
the
same
time
it's
still
very
useful
and
you
will
eventually
get
an
answer
from
someone.
There's
also
discussed
kubernetes
I/o.
So
if
folks
want
to
talk
about
their
tips
specifically
for
setting
up
their
dev
environment
as
well,
that's
a
great
place
to
do
so.
There's
all
types
of
tips
and
tricks
it
sort
of
fills
a
gap
between
our
official
Docs
and
Stack
Overflow.
A
So
please
feel
free
to
use
that
as
a
as
a
resource
for
those
listening
all
right.
Next
question
has
to
do
with
our
jargon
and
what
the
individual
means
by
that
is
what
are
some
term
and
what
is
some
of
the
terminology
related
to
kubernetes?
Seven
just
said
one
which
was
LG
e
TM.
That
kind
of
tripped
you
up
in
the
beginning
of
your
contributions,
s
or
still
just
still
trips,
you
out,
and
you
have
to
look
it
up.
What
are
some
of
those
Dargan
terms
and
or
kubernetes
related
words?
B
Just
trying
to
think
of
examples
like,
as
you
say,
service
is
a
bit
of
a
weird
term,
but
it's
Li
guess
whenever
I
talk
about
running
stuff
on
community,
so
I
want
to
run
this
service
on
Kiva
nettings.
But
then
you
say
service
and
you
actually
mean
like
a
micro
service.
You
don't
mean
a
service
so
that
no
one
does,
but
that's
a
prime
example
of
some
weird
terminology
that
given
as
these
gets.
D
I
remembered
that
the
first
first
kubernetes
related
term,
that
was
really
confusing
for
me,
was
bought
and
it
was
really
confusing,
because
my
initial
assumption,
when
I
started
looking
to
Banaras,
was
that
cabinet
is
management
dinners,
but
a
frame
dirt
out
and
documentation.
That
unit
is
management
parts,
so
I
had
spent
not
so
much
time
but
bit
I'm
Lauren
what
the
plots
are
and
what
is
their
difference,
waste
containers
and
twist
other
other
projects
in
communities
and
specifically
what
the
main
reasons
were
given
a
task
is.
D
D
At
the
same
time,
if,
if
you
as
a
new
contributor
to
Cuban
artists
here,
looking
to
to
the
definition
of
saw
specific
term
that
we
have
in
common,
it
is
special
from
the
operational
experience
I
have
to
mention
it.
We
have
standardized
glossary
on
cabinet.
Is
that
your
website,
where
you
can
find
all
the
common
terms
that
we
years
in
Cuban
areas
in
Cuba
natives
as
technology
project
and
in
command,
is
an
open
source
project?
A
community.
A
F
There's
plenty
you
own
testing,
so
we
have
a
mechanism,
let's
call
it
a
submit
queue
which
collects
all
PRS,
which
are
approved
and
lt
kempt,
its
retesting.
Everything
and
your
PR
has
to
go
through
this
submit
queue,
and
there
are
certain
words
for
it,
like
everything
should
between.
Of
course,
every
test
should
be
green,
not
every
because
exceptions.
So
some
tests
are
optional
as
they
are
not
activated
and
submit
you
anyways.
Everything
about
is
testing.
It's
not
trivial,
because
it's
pretty
huge
and
if
something
goes
wrong,
it's
very
hard
to
understand.
Is
it
your
fault?
F
Often
it
is.
But
often
it's
not
your
fault,
just
a
flake.
We
call
it
a
flake
when
something
goes
wrong
which
just
goes
wrong
every
once
and
then
so.
Every
I
know
100
100
or
something
like
that
and
it
shows
up
in
your
PR
and
you
are
lost
if
you
debug,
and
you
can
usually
do
retest
this
your
PR
and
hope
it
goes
away.
And
if
it
was
not
your
fault
that
you
introduced
this
flake,
this
is
fine.
Maybe
it
comes
back,
then
you
should
maybe
look
bit
deeper
yeah.
F
So
those
testing
things
I
think
say
if
they
changed
I'm
saying
our
awesome
test
team
was
on
testing
still
today
it's
some
some
sometimes
yeah.
It's
complicated
to
really
understand
what's
going
on
and
if
something
is
wrong
to
debug
it,
then
this
term
of
sick
I
think
this
is
also
very
special
in
our
community,
especially
interest
groups.
So
at
some
point
we
notice
that
not
everybody
can
understand
everything.
I
discuss
everything,
so
we
introduce
special
interest
groups,
I
think
that
26
or
something
like
that
nowadays
for
many
topics
and
just
look
Susan
s.
F
There
documented
I'm,
not
sure
where
exactly
I
was
kept
at
me.
I
guess
and
look
for
those
which
are
interested
for
you
and
just
join
them
and
listen
once
a
week
or
every
two
weeks
depending
on
the
sick-
and
this
is
a
discussion,
stand,
get
to
know
the
people
around
and
what
are
the
hot
topics
and
if
you
have
a
new
topic,
bring
it
in
and
that
it's
discussed
there.
A
Awesome
that
was
great
explanation.
Thank
you
for
that.
All
right,
we
do
have
a
semi
large
question
asked.
So
what
I'm
gonna
do
is
see.
If
you
all
can
do
it.
If
not
it's
fine,
because
we
can
do
it
on
a
next
session,
but
an
individual
in
the
meet
our
contributors
select
channel
wants
to
know.
If
you
can
talk
about
the
kubernetes
kubernetes
repo,
specifically
tips
on
how
its
laid
out,
if
you
can
talk
about
the
directory
structure,
etc,
and
maybe
we
could
do
like
a
screen
share
and
you
could
talk
through
it.
A
If
that's
something
that
you
feel
comfortable
with,
we
can
do
it.
We
still
have
like
20-ish
minutes
left
to
to
broadcast,
but
what
I
can
do
now
is
ask
another
question
and
you
can
think
about
if
you
can
answer
that
so
I'm
gonna
pause
that
question
and
go
to
another
one
and
in
the
meantime,
if
anybody
wants
to
kind
of
take
a
quick
look
through
Kay
Kay,
that's
what
we
call
it
for
the
speaking
of
jargon
and
if
anybody
wants
to
look
through
that
and
see,
if
you
can
talk
to
it,
that
would
be
awesome.
A
D
So
I
would
say
that
cabinet
this
is
my
primary
versus
project,
for
it,
I
contribute
to
as
a
developer,
educate
for
C
and
C
F.
We
have
not
only
given
at
his
but
around
20
other
projects
and
I'm,
not
contributing
to
the
code
base
to
all
them,
but
also
contribute
to
some
of
them
in
in
the
different
ways.
At
the
same
time,
our
communities
was
their
first
project
which
picked
up
as
open-source
project
where
I'd
like
to
which
I'd
like
to
contribute
on
a
regular
basis.
D
I
had
experience
with
the
different
projects
and
I
was
not
really
excited
about
the
openness
of
them
and
community
orientation
of
them.
So
this
was
my
choice
a
few
years
ago,
because
it's
openness
and
the
way
how
can
here
get
started
from
there
from
there
early
beginning?
How
can
you
get
started
as
a
person
who
never
contributed
anything
to
any
any
popular
versus
project
or
what
what
can
be
here
or
successful
possible?
So
that
was
the
reason
why
I
chose
to
Denarius,
because
it's
pretty
open.
We
are
an
open
community.
A
D
Yes,
I
would
also
mention,
and
now
the
reason
why
should
you
consider
contributing
to
the
net
is
not
only
because
of
death.
We
need
your
openness
that
it
could
because
of
the
project
popular
from
the
technology
perspective.
So
a
community
is
one
of
one
of
the
most
highest
velocity
projects
in
the
world
in
the
world
world
resource
and
it
can.
It
can
be
conferred
from
the
specific
verses
projects
like
Linux,
chromium,
no
GS
or
just
a
few,
and
if
you
are
contributing
to
communities,
you
are
definitely
contributing
to
the
upstream.
B
B
B
Yes,
I
actually
commuted
to
a
few
other
projects
around
the
same
sort
of
space
in
terms
of
projects
that
we're
using
within
our
cognizes
infrastructure
of
pressure.
So
there's
one
called
Korres
Dex
that
size
of
oh
I,
DC
proxy,
because
we
used
sort
of
single
sign-on
I've
actually
contributed
scipios
up
to
that
as
well.
B
Another
one
in
a
similar
space,
the
bit
the
OAuth
proxy
that
we've
continued
to
and
as
well
as
that
we
actually
have
a
few
open
source,
repos
ourselves
so
again,
similar
sort
of
space
all
stuff
to
do
with
how
we
run
our
people
Nettie's
projects.
But
you
know
we're
writing
these
tools.
Custom
controllers!
That
kind
of
thing.
Why
not
share
them
with
other
people?
Why
not
have
them
have
the
ability
to
go
and
use
our
code?
B
You
know
like
why,
when
you
are
solving
a
problem,
if
like
I'm,
not
sharing
it
and
making
someone
else
solve
the
same
problem,
so
I'm
quite
passionate
about
doing
and
been
really
pushing
it
for
open
sourcing
as
much
as
you
can
for
sure
in
terms
of
our
instruction
code,
the
years
or
the
YK
minetti's.
It's
just
because
I
work
on
it
day
to
day
and
I
spend
my
40
hours
a
week
working
with
few
minutes.
A
F
So
yeah
similar
like
someone
before
so
I,
could
you
be
through
a
lot
of
projects
around
kubernetes?
So
not
everything
is
inconvenience
kubernetes.
So
there
are
many
repositories
which
I
touchy
and
there
and
of
course,
I'm
working
for
net
head,
so
this
OpenShift
some
product
on
top
of
kubernetes
and
computing
there
as
well
all
open
source,
of
course
yeah.
So
I
would
try
to.
She
has
a
screen.
Let
me
see.
A
F
I
won't
talk
about
all
of
those
directories
like
20
here,
I
pick
a
few
yeah
I.
Let's
start,
maybe
with
this
package
PKG,
it's
the
main
package
we're
all
not
all,
but
traditionally
there
was
all
code
of
kubernetes.
Basically,
everything
which
made
the
newest
project
was
here.
Nowadays,
we've
moved
out
a
lot.
You
will
see
in
a
second
where
other
things
are
today,
but
you
still
find
a
lot
of
things.
So,
for
example,
if
I
go
here
to
package
controller,
you
will
find
a
whole
list
of
controllers.
F
Controllers
might
be
a
term
for
you
controllers,
operators
and
those
are
those
for
fajitas
resources.
For
example,
you
find
all
the
replica
set
logic
here
or
deployment
logic.
So
for
the
resources
you
know
from
kubernetes,
always
a
business
project,
behind-the-scenes
everything,
that's
good,
hula
mentor
is
doing.
This
is
here
in
this
directory,
like
30
40,
different
controllers.
I,
don't
go
into
details
here,
but
it's
also
really
interesting.
F
If
you
want
to
learn
from
codes
just
know,
pin
to
replica
set
for
example,
and
and
see
how
a
replica
set,
the
logic
of
replica
said,
is
implemented
in
kubernetes,
I
talked
about
owner
fired,
so
here's
one
of
those
owner
files,
just
owners,
employer
capital
case,
and
you
see
where
four
approvers
and
one
reviewer
and
this
owner
file
is
rated
for
all
subdirectories
under
controllers.
If
there's
no
other
owner
file,
which
replaces
this
one,
so
those
four
people
can
approve
the
changes
in
controllers
as
well.
F
F
They
are
different
people,
so
they'll
just
approve
us
and
for
people
who
want
to
review
changes
in
here
controllers,
as
I
said
where
the
important
quarter
of
code
we
have
API
is
workaround,
so
here's
something
could
API
is
I
will
not
talk
much
about
that,
because
there's
a
better
place
to
look
for
that,
but
you
find
all
API
is
here,
but
no
it's
not
those
API
switch.
You
actually
use.
So
I
don't
want
to
dive
too
much
into
this
package
structure.
F
It's
pretty
huge
I
go
back
to
the
top
level
and
show
where
the
other
code
is
so
package.
There's
a
lot
of
code.
We
have
CMD,
which
are
the
commands.
So
if
you
go
into
CMD,
of
course
you
find
things
like
hyper
cube.
So
if
you
have
started
at
less
than
yourself,
you
have
probably
you
swipe
at
you
before
everybody
has
used
to
control.
So
if
you
control
is
the
top-level
file
for
the
command
to
control,
so
that's
probably
a
main
function,
but
much
more
and
all
those
binaries
you
find
here.
F
So
it's
pretty
easy
to
get
an
entry
point.
If
you
look
for
for
how
something
works
in
kubernetes,
so
CMD
in
package,
we
have
this
heck
directory.
Heck
is
a
bunch
of
strippers
scripts.
You
have
to
use
if
you
want
to
do
changes.
For
example,
when
you
change
something.
Quite
often
you
have
to
update
something
you
have
to
update
generate
the
code
until
you
find
all
those
update
scripts
just
update
all
you
can
wonder
it
takes
like
40
minutes
or
so
and
then
everything
is
updated.
F
Takes
long,
it
works
yes,
but
usually
so
I
never
called
that
I
usually
see
from
from
CIA
were
just
running
against
my
peers.
What
must
be
changed,
I
must
be
updated
and
then
I
won
the
right
script.
So
here's
a
bunch
of
I
know
30
different
update
scripts,
for
example,
it
says
Cochin
involved,
so
we
change
something
and
says
there
must
be
a
change
in
a
client
or
in
some
API
code
or
the
copy
code.
F
This
is
the
fire
to
call
before
you
B,
of
course,
if
you're
new
in
this
codebase
it's
hard
to
really
tell
which
one
must
be
one.
So
maybe
it's
easier
to
one
just
update
all
after
you
notice
that
your
PR
is
not
green,
because
something
is
missing,
so
update,
always
a
very
important
one,
and
there
are
a
couple
of
test
scripts
here:
how
to
run
tests
for
intubation
or
just
go
test
unit
tests
also
document
it
as
well.
F
So
if
you
look
for
those
scripts,
he
and
suppository
you're
able
to
find
some
documentation
last
but
not
least,
as
a
staging
directory.
So
if
you
have
programmed
anything
in
kubernetes,
you
probably
know
a
couple
of
those
projects,
so
client
go
so
when
a
permanent
one,
it's
our
client,
basically
the
API
one
here
Kate
as
API.
It
includes
all
at
the
ice
we
expose,
which
can
be
used
by
third
parties,
those
repositories
they
are
inside
of
our
main
repository.
F
So
if
you
want
to
change
something,
do
it
here
in
the
staging
those
directories
all
also
circuits
under
staging
they
export
it
to
the
real
directories
under
github,
so
I
hope
you
can
see
that
if
I
go
here
into
kubernetes
client
go.
This
is
what
you
use
in
go
code.
If
you
program
against
our
API,
it's
just
a
copy
of
what
you
find.
What
you
find
inside
of
the
staging,
so
staging
is
a
prime
instance
of
the
source
code.
F
So
if
you
change
something,
do
it
here,
but
if
you,
if
you
consume
our
our
repositories
to
in
the
actual
published
repository
so
under
github
communities,
crying
go
as
I
say
it's
a
couple
of
them.
Some
of
them.
You
see
here
as
a
PR
machine.
We
usually
use
this
API
server.
If
you
program
an
API
server,
those
are
really
important.
A
lot
of
them
are
like
Elise
was
already
pouring
kubernetes,
where
the
internal
yeah
just
both
of
them.
We
don't
have
enough
time
to.
We
talked
to
them
here.
F
Take
a
look
post,
the
code
in
general.
This
is
yeah.
It's
one
suggestion
quit.
Is
this
huge?
So
the
code
base
is
really
huge:
try
to
get
ready
some
kind
of
debugger,
some
IDE
like
years
code
like
öland,
try
to
get
a
debugger
working.
This
helps
a
lot
to
really
trace
when
something
happens.
Where
it
happens,
that's
I
think
it's
a
very
important
into
when
you
find
your
way
through
this
code
base,
don't
be
afraid,
it's
big!
It
takes
time.
It
takes
time
for
everybody
to
really
find
the
way.
F
Yeah,
maybe
the
last
thing
I
want
to
mention.
We
have
plenty
of
those
other
tests
which
are
one
in
CI
against.
You
will
request.
We
have
many
unit
tests,
of
course,
unit
tests
as
usually
and
goes.
They
are
just
files
inside
of
the
packages
and
then
we
have
an
addition,
something
that's
also
an
acronym.
Of
course.
We
use
end
to
end.
So
it's
end
to
end
tests
are
those
which
are
warning
against
the
really
trust
us
so
I
know
I
just
pick
one
here
so
which
you
find
everything
about
storage.
F
So,
for
example,
what
we
have
here
if
you
want
to
use
NFS
here,
our
complete
end-to-end
test,
running
against
real,
complete
kubernetes
in
a
real
deployment
on
GCE
on
AWS,
or
something
like
that
next
to
enter
in
tests.
We
have
integration
tests.
So
there's
one
directory
under
test
is
called
integration.
F
They
are
more
than
unit
tests,
but
they
are
not
running
against
a
complete
cluster,
so
they
are
kind
of
artificial.
Sometimes
you
may
be
I
server,
but
they
don't
use.
What's
it
juice
containers
at
all,
so
they
are
level
between
unit
tests
and
end-to-end
tests,
and
you
see
the
nicely
sorted
according
to
some
topics.
So,
if
you
I
know,
you
want
to
change
something
in
the
cooter
handling,
good
chances.
It
says
a
quota
directory
here,
and
this
is
the
case.
So
here
has,
for
example,
depending
on
the
topic
you
are
working
on.
F
A
That
was
an
awesome,
tip
and
awesome
tour
by
the
way
that
so
this
was
our
first
impromptu
tour
on
meter
contributors.
So
thank
you
so
much
for
doing
that
and
for
those
listening.
We
are
more
than
welcome
to
do
things
like
that
in
the
future.
You
just
give
us
a
24
plus
our
lead
time
we
can
make
for
folks
like
Stefan
Joel
or
our
on
the
line
to
to
best
answer
those.
Thank
you
again
for
that.
Alright
I
have
more
questions
than
we
have
time
for
so
I'm
gonna.
A
Do
those
in
the
order
that
they
came
in?
Let's
see,
Oh
Nikita
has
a
question
and
made
our
contributors.
What
are
your
suggestions
for
reviewers?
How
does
one
become
a
good
reviewer
and
also,
as
she
said,
etc,
but
I
know
some
other
folks
in
the
channel.
We're
also
talking
about
how
even
members
which
is
the
first
rung
on
our
ladder,
can
review.
So
what's
the
point,
an
owner's
file
is
a
reviewer,
so
that's
a
Multi
multi
prone
question
there.
A
F
So
let
us
say
make
sure
that's
a
quality
of
Coates.
It's
on
the
right
level
like
they
really
go,
every
little
change.
You
do
every
line,
usually
you
do,
they
might
look
picky,
sometimes
or
pedantic,
but
this
is
important
somehow,
because
if
everybody
follows
any
kind
of
style
without
any
uniformity,
the
whole
project
gets
harder
to
maintain.
So
there's
a
reason
for
that.
All
of
us
usually
is
a
so
yeah.
F
They
want
to
improve
code.
Sometimes
it's
about
taste.
This
can
happen
but
say
they
have
where
they
post
different
tensions.
Usually
so
it's
fine
to
discuss
things
or
to
say
well,
this
is
maybe
not
my
opinion
or
it's
a
different
style.
That's
all
fine,
but
they
have
good
intentions
to
improve
code,
and
this
brings
me
to
maybe
is
a
second
part
of
the
question
how
to
get
it
with
a
viewer.
F
F
This
is
not
necessary,
but
the
best
way
to
become
a
lab
you
enough
already
or
whatever
this
means
just
start
lab.
You
look
in
in
some
components
you
you
care
about.
We
deeply
care
about
and
just
start
have
you
in
any
kind
of
PR.
Everybody
is
happy
about
values,
I'm,
just
very
important.
Everybody
is
happy
about
reviews.
I'm,
the
worst
thing
for
contributors
is
say,
contribute
some
things.
They
prove
something
a
PR
and
nobody
cares.
F
So
if
you
have
you,
that's
already
the
first
step
and
it's
very
good
for
the
people
who
contribute
code
and
don't
be
frightened
if
the
person
who
who
for
something
is
the
well-known
person
as
a
project
yeah
do
your
best.
If
you
have
you,
if
you
see
something
start
with
things
which
are,
maybe
not
so
deep,
just
apply
your
knowledge.
If
you
think
this
is
not
good
styling
go
comment
on
it
and
get
known
in
this
component.
That's
as
easy.
F
F
Approver
is
the
next
step.
So
if
you
want
to
be
owner
and
approver,
this
means
you
must
be
reviewer
for
at
least
a
few
months,
and
you
must
be
well
known
and
accepted
to
be
some
kind
of
instance,
as
a
reviewer
for
this
component.
But
this
is
the
same
way
just
to
have
use
now
ready.
Many
have
used
good
quality
proofs
that
you
know
the
codes
that
you
give
value
back
as
a
reviewer,
and
then
you
can
become
a
covert.
That's
the
same
same
way,
works.
B
A
B
I
think
that's
good,
because
you
know
they
don't
waste
their
time.
Looking
your
code,
if
the
motive
is
wrong,
know
that
if
they've
got
any
questions
about
what
the
code
is
going
to
change
first
and
you
know,
but
if
you're
going
to
be
reviewing
code,
you
don't
want
to
be
reviewing
it
and
not
not
actually
understand.
What's
going
on
explaining
your
decisions
as
well
is
a
very
good
thing.
So
I
had
a
tailor
with
the
comment
yesterday
and.
B
A
Does
anyone
want
to
give
any
shoutouts
individual
shoutouts
any
good
reviewers
that
they
know
not
to
put
you
on
the
spot,
but
feel
free
to
give
a
shout
out
to
anyone
that
you
see
that's
doing
good
reviews?
I
know
your
is
a
good
reviewer
for
the
community
repo.
He
is
an
issue
triage
captain
there.
So
that's
my
shout
out
personally
Stefan.
Do
you
want
to
give
any
shoutouts
to
anyone
that
you
see
doing
great
reviews
so.
F
I
personally,
like
reviewers,
who
are
reliable,
likes
I,
come
back
to
your
questions
and
you
can
just
rely
on
them
to
to
answer
everything
divides
within
I
know,
one
two
or
three
days:
it's
awful
when
you
write
something
and
there's
silence
for
three
weeks
or
three
months
say
a
couple
of
them.
As
my
colleague
Johnny
trait,
for
example,
it
is
one
of
the
most
awesome.
Febby
was
just
a
volume.
He
does
is
incredible,
and
also
quality
is
very
important.
He's
just
these
things
in
your
code,
which
you
didn't
think
about
it.
All.
F
It
improves
your
code,
but
there
are
many
many
other
reviewers.
Many
of
them
are
overloaded.
So
this
is
how
us
my
main
problem,
I
think.
So
there
are
a
lot
of
people
who
are
today
in
poor
files,
but
they
don't
have
the
time
to
to
look
in
on
every
PR.
That's
why
I
say
we
want
more
and
more
reviewers,
so
they
bring
a
lot
of
value.
A
Jordan
is
indeed
awesome.
He
was
on
our
last
month's
edition
and
I.
Think
one
of
his
questions
was
personally
towards
him
of
how
do
you
do
it?
How
do
you
manage
your
time,
so
folks
are
interested
in
checking
out
how
Jordan
manage
his
time
check
out
last
month's
episode,
all
right
so
now
let
me
go
to
our
next
question
here.
F
So
I
can
answer
it
really.
Briefly.
Very
short:
no,
there
is
no
automatic
way.
I
said
update
all
always
works,
but
this
takes
ages.
So
I
think
it's
just
experience.
Look
at
the
output
of
CI,
so
I,
usually
I
mean
I
I
called
update
scripts
before
I
submit
something
where
I
know
it
changed,
but
it
happens
every
second
time
or
more
often
that
something
is
missing.
So
I
have
to
call
something
after
C
is
wet.
F
Just
look
at
the
outputs,
and
usually
this
gives
you
a
hint
I,
don't
think,
there's
much
more
one
can
say
our
CI
is
pretty
good
in
catching
missing
updates.
So
this
is
pretty
good,
but
still
you
have
to
look
in
into
log
files.
We
don't
have
an
artificial
intelligence
which
derives
the
scripts.
You
have
two
one.
This
would
be
cool,
but
I
haven't
seen
anything
like
that.
A
A
Yeah
there
was
some
questions
about
those
kubernetes
have
a
buddy
mentor
system
for
new
contributors.
One
of
them
is
this
that
we're
all
on
I
think
the
what
we've
been
trying
to
experiment
with
is:
how
can
we
break
down
the
old
walls
of
mentoring?
What
I
mean
by
that
is
having
one
mentee
you
have.
You
have
dedicated
time.
A
So
we
are
in
the
middle
of
developing
that
we
ran
a
few
tests
and
the
tests
had
some
works
that
we
need
to
do.
For
instance,
how
do
we?
How
do
we
agree
upon
an
environment
to
do
pair
programming?
We
did
I
didn't
say:
I
was
just
like.
Oh,
let
developers
figure
it
out
on
their
own.
Well,
apparently,
there
are
billions
of
ways
to
PI
our
program,
so
we're
trying
to
figure
out
how
to
suggest
the
best
way
we
also
Google
Summer
of
Code
and
outreach
e.
Both
of
those
are
third-party
mentoring
initiatives.
A
So
we've
tested
both
and
both
are
good
to
go
and
then
we'll
also
have
mentoring
eventually,
which
is
an
awesome
program
that
will
help
mentors,
do
do
mentoring
in
groups
for
SIG's
that
are
in
need
of
a
certain
level.
So,
for
instance,
if
you're
saying
is
in
need
of
more
reviewers,
we
can
do
a
group
of
members
to
reviewers
type
of
a
cohort
class,
so
that
is
coming
as
well.
A
There's
about
seven
programs
that
are
either
in
development
or
launched
at
this
point,
I'd
consider
this
one
launched
same
as
Google
Summer
of
Code
and
outreach
ease.
So
three
of
those
programs
are
are
in
the
works.
We
do
need
lots
of
help
on
the
process,
design
and
program
design
side
for
those,
so
if
anybody's
listening,
that
wants
to
help
out
with
that,
please
come
to
contributor
experience
and
talk
to
me
and
we
can
definitely
work
something
out
there.
All
right
and
I
know
we
have
less
than
two
minutes
left
and
I.
F
A
Well,
that
wraps
up
today's
session
for
those
that
did
not
have
a
question
addressed
during
this
session,
whether
you're
in
my
direct
messages
or
in
the
in
the
Select
channel
or
in
my
Twitter
direct
messages,
we
will
get
to
you
on
the
next
session
and
again
the
next
session
will
feature
seven
out
of
12
of
our
steering
committee
members,
PS
I
heard
they
have
an
election
coming
up,
so
might
be
good
to
ask
all
of
your
governance.
Why
questions?
Why
do
we
do
this?