►
From YouTube: Kubernetes Meet Our Contributors 20191204
Description
Our last edition of Meet Our Contributors for the year. Join us - Taylor Dolezal (@onlydole), Kelsey Hightower (@kelseyhightower), Paris Pittman and a few other contributors for live upstream q&a, post kubecon story time, and your monthly dose of random!
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 out this page for more information: https://github.com/kubernetes/community/blob/master/mentoring/meet-our-contributors.md
A
All
right
welcome
everybody
to
meet
our
contributors
for
December
2019.
This
is
the
last
meet
our
contributors
for
for
the
year.
I'd
like
to
thank
everyone
for
joining
us
meet.
Our
contributors
is
the
livestream
where
we
bring
kubernetes
contributors
on
this
livestream,
and
then
you
can
ask
them
questions
what
it
was
like
to
do
their
first
contribution,
what
you
know
how
to
do
a
pull
request:
we've
had
architect
diagrams
or
the
whiteboard.
Basically
anything
that
would
help
you
contribute
to
kubernetes
or
get
started
with
kubernetes.
A
So
we've
got
a
bunch
of
questions
lining
up
in
chat.
Welcome
those
of
you
joining
us
on
youtube.
The
way
it
works
is
I
hop
into
hash,
meet
our
contributors
on
kubernetes
slacks,
which,
if
you
follow
the
directions
below
in
the
youtube
link,
you
should
be
able
to
see
there
and
then
just
ask
your
question
and
then
we're
gonna
ask
our
panel
of
experts,
the
questions
and
they're
gonna
talk
about
their
experiences,
how
they
got
started,
contributing
to
kubernetes
and
all
that
kind
of
good
stuff.
So
please
give
us
a
sound
check.
A
How
do
we
sound
feel
free
to
type
remember
that
your
chat
is
being
broadcast
along
with
everyone's
faces,
and
also
please
remember
that
the
kubernetes
code
of
conduct
is
in
effect,
so
please
be
excellent
to
each
other.
All
right
with
that.
Let's
do
some
quick
introductions.
Let's
do
a
Taylor
and
Kelsey
finish
us
off.
B
Welcome
everyone:
my
name
is
eros
varetsky
I
am
a
developer
educated
cloud
native
computing
foundation
ACNC
if
I'm
also
contributed
to
communities
community
for
a
pretty
long
time
since
q4
2015,
so
around
four
years
and
I'm
mostly
focused
on
the
non
non
coding
errors
of
cabin
era,
so
I
used
to
be
sure,
CP
I'm,
a
co-founder
and
CEO
and
chair
of
CPM
I'm,
actively
involved
into
the
life
of
C
contributor
experience
these
days
and
many
others
community
besides
the
general
científico
system.
So
he
addressed
in
this
errors
today.
C
My
name
is
Taylor
Dolezal
I
work
at
what
does
he
Studios
I,
mostly
work
with
the
systems,
engineers
developers
and
we're
growing?
Our
set
reliability.
Engineering
team
I
got
started
with
Cooper
days.
About
a
year
ago,
I'd
say
working
with
the
cig
release.
Group
I
got
to
serve
on
releases
one
14
15
and
16
1
17
I
moved
over
to
the
release
manager,
associate
position
so
get
to
work
with
a
bunch
of
some
people
in
that
camp
other
than
that
and
yeah.
It's
raining
in
all
it
it's
it's
interesting.
A
A
Awesome
and
with
that
everyone
please
keep
your
questions
about
weather
baby
Yoda
is
rendered
on
kubernetes
to
the
end
of
the
show,
we're
gonna
appreciate
that
real
quick.
You
can
also
ask
questions
anonymously.
So
if
there's
a
question
that
you
want
to
ask-
and
you
prefer
not
to
you-
prefer
to
remain
anonymous-
feel
free
to
PM
me
in
slack.
I
am
Castro
J
Oh
Laura
welcome.
Laura
has
the
first
question
of
the
day
to
kick
us
off
says
what
was
your
first
contribution
experience
like
to
the
kubernetes
projects?
D
Yeah
I'll
start
I
was
contributing
back
when
there's
a
very
small
number
of
contributors
and
the
project
was
less
complex
right.
I
remember,
I
could
be
read
all
the
source
code
in
one
repository,
you
could
almost
follow
the
code
from
this
entry
point
to
what
it's
actually
doing,
and
there
were
a
lot
of
things
to
work
on
right.
We
didn't
have
a
lot
of
native
cloud
support.
There
was
no
volumes,
there
was
no
namespaces,
and
at
that
time
we
didn't
know
if
kubernetes
is
going
to
be
the
thing
it
is
today.
D
So
any
contribution
was
super.
Welcome.
There
was
a
lot
less
competition
between
people
working
in
the
same
places,
so
I
found
that
one
pretty
I
would
say
easy
in
terms
of
finding
what
to
actually
work
on
and
I
think.
The
last
thing
is:
what
is
your
motivation
right
so
at
that
time,
I
was
working
at
core
OS
and
I
really
wanted
to
make
it
easier
for
core
OS
knows
to
register
register
themselves,
created
a
cloud
provider
and
I
think
the
hard
part's
now
is.
What
is
your
motivation
right?
D
Some
people
contribute
to
build
up
their
reputation
in
the
community,
some
people
work
at
a
provider
or
maybe
a
vendor,
and
they
want
to
make
their
support
a
little
better,
so
I
think
going
forward.
What
is
your
motivation
for
contributing?
Maybe
you're
scratching
your
own?
Itch
you
read
into
a
bug:
that's
probably
the
best
place
to
start
versus
trying
to
prove
yourself
by
working
on
the
scheduler
or
some
very
complex
component.
C
The
project
and
the
communications
role
really
struck
my
eye
and
so
I
applied
to
that
and
and
luckily
got
accepted,
and
then
at
that
point
in
time
got
pulled
right
into
the
release
and
it
was
just
a
very
active,
very
engaged
community.
Before
then
it
was
you
know,
I
have
a
couple
requests
and
smaller
projects.
You
know
whether
it
be
a
typo
or
just
a
conditional
that
needs
fixing,
but
very
very
different
experience
like
what's
into
that.
C
In
terms
of
the
amount
of
people
that
are
ready
to
kind
of
talk
with
you
and
engage
with
you
and
a
lot
more
process,
rather
than
just
a
nice
little,
here's
how
you
submit
a
PR,
you
have
a
you
know,
you
have
handbooks
and
you
have
just
kind
of
it's.
It's
a
lot
harder
to
not
know
what's
going
on.
If
you
start
looking
at
the
documentation,
if
you
know
where
to
start
looking.
D
Yeah
I
think
the
key
for
most
people
just
get
that
first
pull
request
and
like
I,
don't
I,
don't
care
how
legendary
your
software
development
skills
are
you'll,
probably
just
better
off
starting
with
the
smallest
change.
You
can
and
get
it
merged
a
hundred
percent
right,
and
that
way
you
can
go
through
the
process.
B
I
was
about
to
say
the
same
Kelsey,
so
my
first
contribution
was,
as
I
mentioned
before
it
was
like
around
four
years
ago.
So
remember
it
was
November
2015
and
to
be
noticed
1.0.
That
six
was
the
actual
release
of
those
time.
So
it
was
like
wait
way
long
time
ago
and
we
definitely
had
way
smaller
codebase
and
we've
also
had
the
way
smaller
group
of
people
who
were
actually
considered
as
the
contributors
to
this
community
and
among
in
myself.
B
So
my
first
contribution
was
fixing
the
fixing
a
few
lines
in
the
documentation
and
a
few
lines
in
a
batch
script
that
allowed
it
allowed
us
to
deploy
a
few
minutes
faster
on
labert
waist
caress
notes.
So
it's
currently
deprecated,
so
you
won't
be
able
to
find
it
create
these
days
in
given
a
test
documentation.
But
four
years
ago
it
was
a
pretty
pretty
popular
way
of
deploying
kubernetes
using
their
best
scripts,
so
especially
for
the
for
the
testing
purposes
and
I
was
trying
to
do
the
same.
B
For
my
of
myself,
so
I
was
trying
to
deploy
given
Edison
my
machine
and
my
cluster
I
had
some
issues
was
doing
that
and
I
figured
out
that
the
best
route
is
inconsistent
debate
and
the
documentation
also
needs
some.
So
it
was
my
first
contribution
and
it
was
my
first
PR
and
I
still
remember
and
I
still
remember
how
how
excited
I
was,
after
it
was
merged.
I,
remember,
multiple
contributions
that
myself
and
other
folks
together
with
me.
B
We
did
after
that,
but
still
the
first
Paris
is
the
most
important,
but
another
thing
that
I'd
like
to
highlight
that
not
only
the
codebase,
not
only
writing
a
code
or
even
writing
documentation
is
the
efficient
way.
Is
the
only
efficient
way
to
get
started?
Please
cabinet
us.
As
a
contributor,
there
are
multiple
people
who
are
successful
product
managers,
for
example
in
their
daily
life,
and
it
would
like
to
contribute
to
some
some
experience
from
their
product
management
world
to
Cuban
areas.
B
A
Right
moving
on
MPD
asks-
and
this
is
a
popular
question-
I'm
really
interested
in
the
panel's
opinions
on
this.
Sometimes
it's
hard
to
get
in
a
particular
task
to
get
the
complexity
of
the
system
and
our
lack
of
knowledge
of
the
developer.
Are
there
any
Cata
code
or
workshops
provided
by
the
communities
and
SIG's
focuses
certain
parts
of
kubernetes.
It
came.
What's
the
correct
way
to
get
your
hands
dirty
and
if
you
don't
know
about
any
of
these
programs,
that
SIG's
might
do
maybe
highlight
how
you
figured
out.
You
know
what
section
yeah.
D
I
would
say,
patience
is
number
one,
because
this
stuff
is
hard,
I
mean
it's
probably
even
harder.
Now,
like
you
got
to
have
patience.
This
is
why
I
think
having
a
clear
motivating
factor
about
why
you're
contributing
it's
going
to
save
you
from
getting
frustrated.
It's
not
a
competition.
The
goal
isn't
to
try
to
get
to
the
top
of
the
Top
Contributors
list.
D
The
goal
is
to
try
to
do
something
meaningful
to
yourself,
maybe
to
your
company
or
to
your
own
situation,
because
there's
a
lot
of
contributors,
so
I
think
the
most
important
contributions
you
can
do
are
the
ones
where
you're
personally
motivated
to
do
them,
whether
it's
a
very
small
or
a
big
overhaul,
you're
gonna,
need
that.
The
reason
why
I'd
say
that
is
that
you're
gonna
have
to
go
and
seek
someone
out.
D
I
think
that
can
help
pair
with
you
and
be
also
as
patient
with
you
that
you're
going
to
need
to
be
with
yourself
and
also
there's
gonna
be
a
lot
of
homework.
You
need
to
do
meaning
if
you
jump
into
slack
and
you
ask
someone
to
explain
how
the
scheduler
works.
That's
really
not
fair
to
the
person
that
you're
asking
that
they're
gonna,
because
they're
probably
get
asked
this
a
thousand
times.
D
You're
gonna
have
to
spend
a
lot
of
time,
bumping
your
head
against
the
wall
progressively
learning
and
then
come
back
with
very
specific
questions,
so
that
people
can
just
show
that
hey
you're
meeting
them
halfway
I'm
on
other
people
are
probably
more
likely
to
give
you
a
little
bit
more
help.
If
we
see
you
kind
of
putting
some
personal
investment
into
the
game
and.
A
D
So
I
just
started
like
assuming
that
you
know
and
I've
been
contributing
to
a
project
for
a
very
long
time
and
been
a
maintainer,
very
mini
project.
So
I
said
hey.
Let
me
first
get
Cooper
days
installed
right,
like
let's
just
get
it
installed
and
then
break
it
and
ask
myself
what
do
I
not
like
about
the
current
setup
and
then
I
would
drill
down
to
try
to
find
the
place
in
code.
That's
causing
the
thing
I
don't
like,
and
until
I
can
find
that
place
in
the
codebase.
D
That's
the
root
cause
of
the
thing,
then
that's
what
I
would
do
on
my
own
as
far
as
I
could
and
if
I
couldn't
find
that
place,
then
my
question
would
be
very
targeted
where
in
the
co
base,
is
this
happening
and
then
I
would
go
back
to
do
a
little
bit
more
self-study
and
then
what
that
showed?
Maintainer
x'
is
that
wow.
This
person
is
really
investing
their
time.
I
can
tell
that
they're
really
trying
as
much
as
they
can
before.
They
are
kind
of
asking
questions,
so
that
was
my
approach.
D
A
C
C
The
other
thing
is
I
really
liked
taking
a
demo
project
and
just
getting
that
set
up,
and
you
know
again
breaking
it,
seeing
how
these
components
fit
together,
understanding
it
because,
if
you're
just
copying
and
pasting
what's
on
stackoverflow
it's
it
is,
you
can
do
it,
but
it's
really
hard
to
understand.
What's
going
on
the
other
thing,
that's
really
helpful
too.
Is
you
know
again
not
slapping
someone
directly
and
having
them
answer
a
popular
question
that
they
get
asked
but
trying
to
find
the
special
interest
group?
C
That's
going
on
everybody,
and
so
you
can
come,
you
can
just
listen.
We
can
just
gonna
be
a
fly
on
the
wall,
hear
what's
going
on
what
are
people
talking
about
in
sig
Auto
scale
and
what
are
people
talking
about
and
sig
p.m.
what's
happening
within
these
different
groups
that
are
talking
about
kubernetes?
You
might
hear
something
that's
relevant
to
what
you're
looking
for.
It's
also
worth
looking
at
those
agendas.
Those
are
in
Google
Docs
as
well.
So
it's
it
is.
C
It
is
difficult
to
try
to
get
a
sense
in
a
bearing
of
what
at
times
you
know
what
you,
what
you
might
want
to
actually
listen
for,
but
there
are
people
out
in
the
community.
I
think
that's
an
easier
question
to
ask
and
get
an
answer
on
that.
What
the
schedule
is,
but
where
can
I
go
to
hear
about
it
and.
B
So
this
workshop
was
intended
for
those
people
who
have
nearly
zero
or
some
basic
Combinator's
about
contributing
to
communities
about
Dylan,
Thompson
or
breaking
Sampson
losing
combinators,
and
they
would
like
to
get
some
new
experience
was
that
some
mentorship
from
the
more
experienced
people
more
experienced
contributors
from
community.
So
if
you,
if
you
have
a
chance,
if
you
are
planning
to
visit
next
cube
con
in
Amsterdam
or
the
next
next
one
in
North,
America
or
the
next
one
in
Shanghai,
so
the
day
we
planned
the
new
contributor
workshops
there.
B
A
And
before
moving
on,
I
would
like
to
point
out
that
some
SIG's
do
have
onboarding
program
so
say:
cluster
life
cycle
this
year
did
a
onboarding
session
where
they
just
had
a
whole
bunch
of
new
people
showed
up
and
they
sat
there
and
kind
of
walk
through
the
major
parts
of
the
cig.
How
they're,
organized
and
kind
of
you
know
gave
everyone
kind
of
a
heads
up
on
a
baseline
on
how
to
contribute
to
that
saying
and
that's
something
we
can
definitely
do
a
better
job
across
the
project.
Jeff
has
a
question.
A
D
Yeah
sustainability,
I
think
Makena
was
kind
of
around
this
idea
around
marathons
I
think
the
most
important
thing
is
the
sustainability
of
yourself.
Forget
the
project.
You
personally
make
sure
that
this
whole
thing
is
sustainable
for
you.
The
project
will
take
care
of
itself
and
I
think
for
their
project
itself.
I
think
uber
neighs
did
a
really
good
job
around
that
1.0
timeframe
defining
what
it
is
and
what
it
isn't.
What
score
was
some
extension
and
I
think
CR
DS
really
helped
with
the
sustainability
of
the
project.
D
The
fact
that
you
can
create
a
custom
resource
definition
have
that
we
have
that
feel
like
a
first-class
part
of
kubernetes
without
it
having
to
live
in
the
core
and
I.
Think
that's
kind
of
the
number
one
thing
that
we
did
to
make
the
project
sustainable
for
the
long
term
and
to
give
the
entire
ecosystem
a
place
to
either
do
development
inside
of
the
core
or
outside
of
the
core
and
I
think.
As
long
as
we
keep
those
principles
high,
then
the
project
will
have
sustainability.
B
Right
and
to
it
so,
a
few
years
ago
we
had
only
one
repo,
it
was
kubernetes
kubernetes
wanna
get
help.
Today
we
have
a
bit
less
than
one
hundred
three
birds
that
are
spread
across
multiple
organizations.
So
that's
actually
the
follow
up
after
those
processes
that
Kelsey
also
described
when
when
we
as
the
community,
we
decided
what
is
the
core
and
what
are
their
organic
parts
of
our
system
or
the
common
areas
project
itself.
C
I,
do
I
really
do
like
that
too.
In
terms
of
the
metaphor
of
the
marathon
I
have
seen
a
couple.
People
within
the
kubernetes
community
just
take
on
a
lot
and
just
you
know
just
enter
into
burnout,
which
has
been
unfortunate,
I'd
like
to
see
that
there
are
kind
of
that,
the
inherent
mentoring
within
a
lot
of
the
special
interest
groups
and
in
which
you'll
have
shadows
and
people
who
watch
the
process,
and
then
people
rotate
out
and
even
people
that
are
experienced.
I
like
that.
C
There's
the
opportunity
for
them
to
become
like
an
emeritus
lead,
and
so
they
can
still
kind
of
offer
guidance
and
help
and
still
be
there,
but
they
don't
have
to
be.
You
know
in
the
weeds
doing
the
day-to-day
or
the
really
nitty
gritty
work.
It's
it's
so
important
it
everyone
that
comes
to
communities
and
wants
to
help
out.
C
That's
that's
an
incredible
thing,
but
don't
don't
take
yourself
for
granted
and
don't
you
know,
bring
up
all
the
gas
in
your
tank
so
to
speak,
because
it's
that's
that's
not
worth
it
and
then
at
that
point
in
time
you
put
yourself
in
danger
and
and
you
know,
and
then
you
can
you
whether
you
want
or
not
you're
forced
to
leave
that
community
within
that
capacity.
So
it's
always
important
to
help
train
up
other
people
and
just
get
more
people
involved
when
it
comes
to
sustainability.
D
I
want
to
double
down
on
what
Taylor
just
said.
This
idea
of
sharing
knowledge
right
when
I
wrote
Cooper
days
the
hard
way
and
the
reason
why
I
maintain
it
for
years,
I
watched
Tim
Hawkins,
do
it
Brian
grant
do
it.
You
need
to
almost
teach
everyone
else,
everything
you
know
so
that
they
can
continue
where
you
need
to
eventually
leave
off
and
I.
Think
that
is
like
the
number
one
thing
you
can
do.
A
D
Well,
when
I
joined
there
was
no
dots
on
how
to
install
the
damn
thing
like
it
was
I.
Remember
the
press
release
coming
out,
you
know
Brendan
burns.
Did
the
you
know,
presentation
at
dr.
car
and
I
was
like.
Oh
that's,
sweet
I'm
working
at
core
OS
at
the
time
we
have
Fleet
so
I'm
like.
How
does
this
thing
compare
to
Fleet?
Let
me
just
go.
Install
it
and
I
go
to
github
as
like.
D
Readme,
hey,
awesome
project
figure
it
out
so
I
spent
like
two
days
just
grinding
trying
to
in
figure
out
how
to
install
what
the
hell
is
a
couplet.
What
is
the
scheduler
piece?
Where
does
it
go?
There
is
no
authentication
at
the
time
right.
The
API
server
has
no
art
back
no
off
whatsoever,
you're
supposed
to
put
Engine
X
in
front
of
it.
So
I
spent
a
couple
of
days
getting
at
work
on
VMware
fusion
and
I
was
like
I.
Don't
know
if
this
is
the
future.
D
D
Yes,
yes,
CD
was
there
in
the
very
beginning,
but
I
had
a
lot
of
experience
coming
from
core
OS,
so
I
kind
of
knew
how
that
part
work,
but
you
got
to
remember:
there's
all
these
other
binaries
controller
manager,
this
just
so
many
little
pieces
that
you
had
no
idea
what
the
flags
were
right,
you're,
really
literally
running
binaries
and
say:
oh,
what
does
that
flag
mean?
What
does
it
do?
How
does
he
even
talk
to
doctor?
C
I'd
say
just
really:
the
drinking
from
the
fire
hose
so
I
was
I
was
lucky
that
there
was
a
good
amount
of
documentation
when,
when
I
started
getting
involved
with
community,
but
it
was
just
a
I.
Just
really
I
got
really
worried
because
a
lot
of
the
time
you
know
you
really
do
kind
of
have
to
think
about
in
destroying
a
new
job.
You
give
yourself
a
little
bit
of
slack
the
first
week
or
two.
C
You
know
to
kind
of
get
your
bearings
about
to
and
understand
where
the
wiki
is,
where
all
the
documentation
is,
where
any
perceived
or
actual
gaps
are
within
your
pure
understanding
kind
of
help
fix
those
gaps,
and
so
I'd
say
that
was
really
the
biggest
thing.
It's
kind
of
just
finding
my
footing
and
finding
out
what
are
what
is
expected
of
me
in
this
role
and
and
how
do
I
want
to
what's
the
most
meaningful
way
I
can
help
out.
B
Would
say
that
my
biggest
pain
point
was
to
almost
understand
how
inclusive
and
welcoming
this
community
is
so
communities
wasn't.
My
first
project
was
the
first
project
of
this
scale
were
I
was
I
was
considering
contributing
to
I.
Had
some
experience
was
the
different
big
open
source
projects
and
I
don't
want
to
say
that
I
had
issues,
but
I
haven't
felt
that
those
communities
were
so
welcoming
for
the
new
people,
especially
for
many
people
with
some,
not
so
good
knowledge
of,
for
example,
programming
as
I
am
I'm.
B
Not
so
I
have
some
different
skills
that
might
be
useful
for
some
community,
but
I
wasn't
sure
if
my
skills
could
be
useful
for
the
risk.
But
when
I
showed
up
at
my
first
Sigma
Thien
and
when
I
showed
up
at
my
first
community
meeting,
I
was
extremely
excited
about
people
who
were
surrounding
me
on
the
video
call
and
how
I
felt
that
during
different
ways,
how
can
I
contribute
here?
B
How
my
current
knowledge,
which
is
not
again,
which
is
not
the
coding
knowledge
but
knowledge
in
the
different
spaces
in
different
areas
and
help
here
and
can
help
move
move
forward?
This
project,
so
that
was
the
biggest
pain
point
to
the
beginning,
but
was
my
probably
most
exciting
point
later
after
that,
after
of
that,
I
figured
out
all
the
sins.
How
how
does
how
do
these
things
work
in
this
community?
B
A
Awesome
we're
about
halfway
through
if
you're,
just
joining
us
on
YouTube.
This
is
the
meet
our
contributors
for
December
2019.
Follow
the
instructions
below
to
ask
a
question
in
the
select
channel
which
are
live
streaming
here
on
the
right.
Whatever
side
that
is
so
welcome,
we
are
still
taking
questions
we're
up
on
questions
as
their
mark
II
posted
a
link
of
playlists
that
we
have
of
code
walkthroughs
that
we
try
to
do
these
sessions.
A
So
those
of
you
out
there,
if
you
know
a
little
piece
of
code
or
something
or
part
of
kubernetes-
and
you
want
to
share
that
with
the
community.
We
hop
on
a
zoom
call,
I
record
it
for
you
and
we
try
to
crank
those
out
so
definitely
check
out
that
playlist
that
Marky
posted
and
we'll
give
the
audience
a
few
quests.
A
few
minutes
here
to
ask
some
questions.
A
It
seems
really
like
a
high
bar,
it's
like
well,
how
am
I
gonna
even
compete
with
these
people,
where
they're
doing
all
this
stuff
and
Here
I
am
with
a
few
hours
a
week
Taylor
you
have
a
day
job
and
you've
just
launched,
probably
one
of
the
biggest
products
that
you'll
ever
launch
in
your
entire
career.
How
do
you
manage
this?
What
do
you
tell
your
boss
like?
How
does
this
work,
because
you
led
the
release,
notes
or
not
the
release
notes,
but
the
comms
team
during
this
right,
correct.
C
C
All
the
lawyers
are
happy,
but
when
it
comes
down
to
that,
I
did
want
to
pick
a
role
that
didn't
kind
of
impact
that
directly
so
so
I
read
code,
I
work
with
that
for
my
day,
job
I
manage
sites
and
and
trying
to
make
sure
everything's,
reliable
and
resilient
and
robust.
But
it's
it's
one
thing
to
do
that.
You
know
from
a
nine-to-five
or
beyond
capacity,
and
it's
it's
it's
it's.
It
can
be
very
taxing
again.
We
talked
about
burnout.
C
You
know
you
want
to
be
sensitive
to
yourself
and
make
sure
that
you're
not
burning
the
candle
at
both
ends.
The
the
Khans
group
really
helped
me
out
with
that,
and
working
with
cig
docks
really
helped
with
that,
because
I
could
go
home
and
kind
of
be
a
technical,
editor
and
review
things
that
that
was
that
was
really
fantastic.
C
To
do
right
now,
I
don't
get
paid
to
work
on
open
source,
so
this
is
absolutely
a
passion
project
and
so
that
to
me
that
makes
a
little
bit
more
meaningful
and,
and
that
kind
of
gets
me
fired
up.
So
even
if
you
have
like
a
rough
day-
or
you
know
just
a
huge
block
of
meetings,
the
taking
a
look
at
kubernetes
could'
getting
to
talk
with
with
all
the
friends
and
contributors
that
I
have
in
that
capacity
are
really
fun.
I.
B
Can
speak
from
my
from
my
experience
so
now
I
have
a
day
job.
That
is
absolutely
bananas,
because
her
work
at
CMC
F,
but
before
she
and
Sierra,
was
working
at
a
different
company
which
was
also
the
open
source
company,
but
a
dead
point
of
time.
They
had
nearly
zero
focus
on
communities,
but
accidentally
the
good.
The
good
point
for
me
was
my
location
in
my
timezone.
B
So
what
else
could
don't
know
me
I'm
based
in
Ukraine,
and
we
have
ten
hours
difference,
please
the
Pacific
time
zone
so
and
a
few
years
ago
today
is
it's?
It's
not
it's
not
so
big
case
these
days,
but
a
few
years
ago,
kubernetes
development,
mostly
North,
American
time
zone,
centric
to
be
there
Pacific
time
zone
centric.
B
So
most
of
the
meetings
have
happened
and
a
Pacific
friendly
Pacific
friendly
time
most
of
the
conversations
in
the
melon
list
and
when
those
conversations
happen,
Pacific
friendly
time-
and
that
was
good
for
me
to
have
my
big
job
in
their
regular
Ukrainian
day
hours
and
in
the
night
to
have
conversations
with
the
communities
committee
that
man
that
I
had
to
spend
more
of
my
personal
time
on
doing
things
for
communities
as
well.
But
it
also
meant
that
I
shouldn't
shouldn't
use
my
business
time
to
work
on
kubernetes
as
a
no
process
project.
B
So
that
was
the
good
point
for
me.
After
that,
I
I
was
able
to
switch
these
things
off
and
after
that,
I
was
able
to
work
into
the
natives
on
a
full-time
as
my
day
job
even
before.
Cn
CF,
but
beginner
as
the
person
was
living
in
a
different
time
zone
and
was
able
to
handle
the
things
from
the
from
the
different
time
was
surprisingly.
But
it
was
a
good
good
thing
for
me.
A
D
Good,
so
competing
is
just
going
to
be
a
losing
battle,
you're
just
going
to
lose.
If
you're
trying
to
compete,
you're
just
going
to
lose
period,
I,
don't
care
if
you're
not
competing
with
anyone
else
in
a
particular
part
of
the
co
base,
so
I
think
the
right
way
to
approach
it.
If
you
want
a
specific
support
for
a
GP
you,
let's
just
throw
that
one
out
there
there's
two
ways
of
going
about
it.
You
can
get
someone
else
to
do
it
like
you
write
up
what
needs
to
happen.
D
What
the
UX
looks
like
what
it
feels
like
and
open
an
issue
bonus
points
if
you
don't
have
to
touch
your
keyboard
after
that,
like
someone
goes
and
says:
hey,
I,
work
at
said:
GPU
provider
and
I
just
merged
the
PR.
That
does
exactly
what
you
want,
like
your
boss,
should
give
you
a
gold
star
right.
Just
put
it
on
your
t-shirt.
When
you
walk
into
work
BAM,
you
did
it
that's
the
most
efficient
thing
you
can
do
and
be
very
clear
on
what
needs
to
happen
and
I
think
most
of
the
kubernetes
process.
D
These
days,
you
have
to
do
that
step.
First,
all
right,
you
have
to
describe
what
you
want
and
why
so,
if
you
take
care
of
that
part
and
someone
else
writes
the
code,
that
is
equally
a
great
contribution
to
the
project
now,
if
no
one
wants
to
work
on
that
thing,
then
things
get
a
little
bit
harder
now,
you're
gonna
have
to
be
the
one
that
takes
on
full
responsibility
for
getting
that
thing
to
come
to
life,
and
that's
just
gonna
be
a
bigger
time.
D
Investment
on
your
part,
so
you're
kind
of
competing
with
your
own
priorities
in
your
own
time.
So
does
it
make
sense
for
you
to
be
doing
this
and
then
sometimes
it
will
and
you'll
see
it
through,
even
if
it
takes
six
months
to
a
year,
you're
competing
with
the
ability
to
get
it
done.
I
think
is
the
most
important
thing
to
look
at.
A
All
right
ass
kind
of
a
silly
question:
there
are
no
silly
questions,
but
I
always
find
a
gigantic
ecosystems,
a
bit
intimidating
to
get
started
with.
Do
you
also
get
a
bit
lost
with
all
the
different
projects
and
code
names
across
the
ecosystem,
especially
as
new
ones
coming
in
all
the
time
like
when
you
see
the
landscape,
I'm
picturing,
the
picture
of
all
these
logos?
Well,.
D
I
have
to
drop
in
a
second
and
I
apologize,
there's
kind
of
a
last-minute
thing
for
me,
so
I'm
gonna
answer
this
one
and
then
politely
drop
off.
There
are
too
many
projects
just
like
there's
too
many
things
in
the
world
and
what
I've
learned
is
my
trick
is
most
of
the
fundamentals
are
the
same.
Every
time,
I
look
at
a
new
logo
that
shows
up
on
the
landscape
and
I
peel
back.
D
The
covers
is
typically
something
either
moving
bytes
around
in
a
certain
way,
with
some
rules
or
policy
or
something
running
some
process
on
something.
That's
it.
Those
are
pretty
much
two
fundamentals.
If
you
understand
the
fundamentals,
then
the
logo
start
to
make
sense
there.
You
can
start
to
put
a
different
question
to
the
logos.
Why
does
this
project
exist?
Maybe
it's
trying
to
make
a
thing
that
was
once
expensive,
cheap,
maybe
is
try
to
foster
a
new
set
of
extensions
and
exploratory
learning
that
we
can
do
in
public.
D
Some
of
these
projects
have
really
great
api's,
fluidy,
kubernetes
itself,
so
I
think
asking
the.
Why
is
this
thing
now
showing
up
re-implementing
the
very
fundamentals
that
I
understand?
Then
none
of
this
feels
overwhelming
to
me.
The
only
thing
that's
overwhelming
now
is
why
the
hell
are
there,
so
many
logos
and
because
some
of
these
things
consolidate,
like
we
saw
with
the
open
tracing
world
right,
there's
some
overlapping
project
that
just
really
need
to
really
figure
it
out
and
maybe
combine
forces
and
I
think
we'll
be
better
off.
So
that's
my
answer.
D
A
C
Great
question
I'd
say
honestly:
it's
it's
the
best
technical
answer.
Everest,
it
depends
right.
That's
that's.
Definitely
an
answer.
I
would
say
honestly,
it
does
vary.
I'd,
say
anywhere
from
five
to
morning
hours
depending
on.
You
know
how
much,
how
much
time
you
have.
You
know
first
layer
on
the
weekend,
but
I
love
it
fantastic
yeah,.
B
A
B
Would
say
that
I
spent
most
of
my
time
in
cabin
areas
and
on
kubernetes
related
projects
like
helm,
is
probably
the
second
project
in
my
in
my
business
time
determine
focused
on
the
C&C
air
project.
I'm
also
focused
on
some
different
CNC
of
wide
star
from
the
foundation
wide
stuff,
but
that's
again,
that's
open
source
related,
but
even
on
my
you
know
like
on
my
non-business
hours.
I
try
to
spend
most
of
my
time
at
open
source
projects,
even
not
as
it
can,
even
not
as
a
contributor,
but
this
is
a
consumer.
B
A
A
The
community
meeting
programs
like
this
that
are
kind
of
they
never
change
right
I'm,
like
that,
a
predetermined
workload
in
your
cloud
that
you
want
to
pre
allocate
and
then,
depending
on
the
cycle,
if
I'm
on
the
release
team
I'll
do
more
upstream
lately,
though,
however,
I've
been
more
internally
as
well
as
my
company
has
been
acquiring
other
companies
to
stop,
there's
like
a
lot
of
people
that
like
need
help
figure
out
how
do
I
board
into
kubernetes.
So
we
kind
of
figuring
figuring
all
that
stuff
out
so
I've
been.
A
This
cycle
is
probably
the
least
amount
of
time.
I've
worked
directly
upstream,
which
I'm
sad
about,
but
I
will
fix
in
January.
So
hopefully
that
answers
the
quest,
because
you
got
a
cycle
in
and
out
you
know.
Sometimes
you
just
got
to
do
something
a
little
bit
different
every
time.
Let's
see
what
other
questions
do
we
have?
We
have
about
15
minutes.
We
don't
have
to
go
the
other
way.
Let's
see
what
the
audience
says
audience.
Are
you
having
a
good
time
so
far,
please
feel
free
to
type
your
feedback.
We
always
love
it.
C
So
so
I
got
to
work
with
I
got
to
work
with
awesome
people
kind
of
upstream
to
to
the
whole
Disney
Plus
launch.
So
Disney
is
a
giant
place,
and
so
there
are
a
bunch
of
different
sections.
There
are
people
that
run
the
parks.
There
are
people
that
run
the
director
consumer
products
and
so
I
work
for
the
studios.
We
create
the
content
and
then
we
we
ship
over
that
content
to
the
direct
consumer
groups
and
so
I.
C
A
A
Me,
let
me
rephrase
Jeff's
question
then,
since
you
both
have
been
contributing
virtually
for
a
long
time
and
I
know
a
has
been
there
physically,
so
I'm
gonna
ignore
you
for
a
second
pretending
that
you
actually
get
to
physically
sit
down
with
like
a
laptop
and
do
the
kind
of
happen
with
discussions.
What
are
some
of
the
things
that
you
could
do
in
real
life
that
you
kind
of
can't
do
async
Rizzoli
via
like
a
github
PR
right
like
what
do
you?
Let
me
just
encompass
that
to
all
of
kube
Khan
in
general.
A
C
Was
really
incredible,
I
mean
and
I
think
that
everybody
I
feel
like
everybody
says
that
were
it's
like
it
was
just
so
great
and
talked
to
people
really.
It
is
great
putting
you
know
a
name
to
a
face
and
an
actual
body
typically
to
see
the
head,
but
it
was
just
kind
of
great
to
really
talk
to
all
the
people
that
I've
worked
with.
You
know
yourself,
yourselves,
included
and
and
kind
of
just
talk
about.
Who
is
this
person
behind?
C
A
B
A
B
Legendary
Cube
Khan,
who
is
the
president
election
combined,
so
we
had,
we
had
around
1,000
people
there
at
the
big
event
and
cubic
on
itself
and
I'd
say
dead.
Demographics
of
they
went
there
most
of
people
not
most,
but
many
people
who
have
attended
determined
as
the
ADA
knees
were
also
the
contributors
to
communities.
So
I
would
say
that
that
tip
con
itself
was
there
scaled
our
portion
of
the
contributors
on
it.
We
also
had
the
contributor
summit.
It
was
called
the
developer
solid
as
far
as
I
remember,
who
later
renamed
it
to
contributor
summit.
B
So
it
was
the
next
day
after
the
big
event
of
the
cube,
calm
and
it
was
it
has.
It
has
happened
in
like
an
extremely
intimidating
atmosphere.
We
had
around
maybe
20
or
30
people
nur
up
to
50,
not
more,
and
we
have
been
able
to
chat
with
each
other
to
meet
every
single
person
during
face-to-face
you're
in
the
whole
day,
and
we
were
able
to
have
some
conversations
even
having
almost
a
singletrack
conversation,
so
that
was
the
life
of
their
cabin
areas
of
the
cabin
and
excommunicated
it
again.
B
Today
we
have
the
size
of
of
the
community
summit
itself
around
the
size
of
their
first
cube,
console
or
the
similar
events
at
the
beginning
of
the
kinetics
life
and
the
funniest
story.
That
I
remember
from
my
first
days
from
actually
first
day
in
Seattle,
it's
at
Keep
Calm,
when
I
was
checking
into
my
hotel.
I
was
staying
in
line
before
before
checking
into
a
hotel
and
I
never
met
any
almost
any
single
person
before
a
good
from
the
governor's
community
before
that
was
my
first
good.
B
Con
I
was
contributing
to
the
net
as
for
a
long
time,
but
there
were
just
a
few
people
from
the
community
who,
on
ahead
a
chance
to
meet
face
to
face
before
so
the
total.
So
my
first
event
when
I
had
a
chance
to
meet
all
these
people
together,
face
to
face
in
the
same
place
and
I
was
surprised.
Why
are
they
in
decline
to
try
to
check
into
my
hotel?
Multiple
people
show
up
to
me,
raise
their
hand
and,
like
told
me,
hi,
ho,
hi
done
and,
and
so
on.
I
was
I
was
surprised.
B
How
do
you
know
me
like
I?
Don't
know
my
face
only
so
my
photos,
I
was
surprised
about
it.
So
I
would
say
that
the
contributor
summit
these
days
also
happening
in
the
same
atmosphere
as
we
head
as
we
head
contributor
summits
and
somehow
keep
on
itself
years
ago.
They
keep
cornice,
notably
different.
We
had
around
twenty
twelve
thousand
people
s
time
in
San,
Diego
and
the
audience
could
be
also
different.
We
have
way
more
end
users.
B
We
have
way
more
Enterprise
focus
of
communities
itself
these
days
comparing
to
the
old
days,
and
that
also
means
that
we
have
more
vendors
there,
more
enterprise
companies
that
are
trying
to
consume
the
scene,
but
the
group
of
contributors,
the
contributors,
see
remain
the
same
people
may
people
may
be
different
because
still
I
mentioned,
we
have
the
shadow
program.
We
have
different
people
who
stepping
down
some
people
happen
up,
but
but
the
general
ecosystem
of
the
contributors
still
remains
the
same.
B
A
C
Yeah
to
serve
on
all
them
to
score
all
the
points
no
I'm
saying
I
really
want
to
see
the
community
grow.
I
want
to
kind
of
help
feed
into
that
the
more
people
that
understand
could
burn
at
ease,
even
if
it
is
in
a
distributed
way.
That's
that's
gonna,
be
incredible.
Personally,
I
do
want
to
kind
of
dig
into
the
core,
and
now
that
I've
got
my
footing
about
me
now
that
I've
kind
of
got
my
hand
written
map.
C
As
far
as
where
we're
you,
which
people
can
I
talk
to
which
groups
can
I
get
involved
with
I,
definitely
want
to
understand
more
the
the
core
kubernetes
and
find
out
components
and
pieces
that
I
can
actually
start
working
on
and
in
talking
with
people
about
that's.
So
that's
that's
gonna,
my
next
level
up
personally,
but
and
to
just
help
any
one
of
you
that
needs
help.
C
If
you
need
help
orienting
yourself
or
you
do
the
question
about
who
do
I
start
talking
to
here's,
some
things
I'm
interested
in
I'm,
more
than
happy
to
kind
of
help,
be
a
lighthouse
and
gonna
put
me
in
the
right
direction.
So
don't
be
a
stranger
reach
out
I'm
more
than
happy,
not
beyond
my
friend,
all
right.
A
A
Feedback,
everyone
is
very
approachable,
wants
you
to
succeed
at
coop
con
contributors,
some
it
was
great
and
the
tooling
around
contributing
is
definitely
getting
better
using
kind.
I
wonder
if
old
kelsey,
when
he
got
started,
he
would
have
had
kind
like
it's
almost
like
a
life
changer
comparing
this
stuff,
but
I
had
to
start
all
right
and
with
that,
thank
you.
Everyone
for
joining
thanks,
Laura
Troy,
Mahesh,
G,
fede,
k,
YP,
Tammy,
o
destroyer,
everyone
who
joined
and
ask
questions.
A
We
really
appreciate
you
all
dropping
by
and
with
that
this
will
conclude
meet
our
contributors
for
2019
and
we'll
be
back
at
the
New.
Year
Paris
will
be
back
and
she
will
let
you
know
when
the
next
one
is
I'm
gonna
guess
it's
gonna
be
the
first
Wednesday,
but
who
knows
because
it's
the
first
of
the
year
I
think
New
Year's
Eve
is
Tuesday
or
Wednesday,
so
we
don't
know
how
it's
gonna
work
out.
So
keep
an
eye
on
this
space,
and
we
will
definitely
let
you
know
ahead
of
time
and
with
that
thanks
everyone.