►
From YouTube: Kubernetes Meet Our Contributors March 2019 1st Session
Description
When Slack seems like it’s going too fast, and you just need a quick answer from a human...
Meet Our Contributors gives you a monthly one-hour opportunity to ask questions about our upstream community, watch interviews with our contributors, and participate in peer code reviews.
Check this out for more information: https://github.com/kubernetes/community/blob/master/mentoring/meet-our-contributors.md
A
Hi,
everyone
welcome
to
marches
edition
of
kubernetes
meet
our
contributors.
My
name
is
Paris
I
work
at
Google.
Today
we
are
joined
by
several
upstream
contributors
in
various
facets
of
kubernetes.
It's
really
awesome
to
have
everyone
here
and
all
of
you
or
I
think
even
different
time
zones
and
different
places
all
on
the
North
America
content
continent,
of
course,
but
yeah.
Nonetheless,
at
least
we
have
some
good
mix
today.
A
Thank
you
all
for
joining
I
know.
Everybody
here
has
super
busy
schedules,
but
this
is
super
important
to
us
as
its
inventory
initiative,
and
we
know
that
people
learn
differently
and
get
information
and
consume
information
differently,
and
this
is
one
of
those
ways
that
we
can
help
out
a
mass
of
folks
in
a
short
one-hour
time
period.
So,
thank
you
so
much
for
joining
us.
As
always,
we
do
have
a
code
of
conduct
that
we
adhere
to,
so
please
be
excellent
to
each
other.
A
I
will
get
into
a
second
on
how
to
participate,
but
wherever
you're
participating,
whether
it's
this
on
the
Zune
call
as
a
panelist
or
a
Twitter
follower
asking
questions
via
DMS,
please
be
respectful
to
each
other.
We
all
we
all
are
learning
together
now
how
to
ask
questions.
The
most
important
part
of
the
day
I
did
send
a
tweet
out
earlier,
and
many
kubernetes
folks
have
retweeted
it.
A
You
can
either
ask
on
Twitter
there
or
you
can
ask
in
the
slack
channel
on
kubernetes
that
is
meet
our
contributors,
and
then
you
can
also
ask
on
the
discuss
thread
that
we've
also
posted,
which
is
discussed.
Kubernetes
I/o
so
pick
your
communication,
medium
poison
there
and
get
us
your
questions,
we'll
find
it
we'll
find
a
way
to
get
them
and
we'll
get
them
answered
so
really
quickly.
A
B
Hi
I'm
on
Carolyn
Van,
Slyke
I
work
in
Microsoft
I,
just
recently
moved
to
a
really
cool
team.
It's
the
X
Deus
group.
They
worked
on
things
like
helm
and
draft,
and
the
new
thing
I'm
working
on
is
cloud
native
application
bundles.
They
call
it
scene
AB,
which
is
the
silliest
name,
but
whatever
and
I
work
on
the
command
line
tool
for
it,
which
is
called
Porter
and
I
used
to
be
the
chair
for
Service
Catalog
I've
worked
on
that
for
about
a
year
and
I
also
leave
the
go
group.
B
A
That's
me
awesome
and
thanks
for
everything
Carolyn
you
do
awesome,
work,
Thanks
and
Carolyn
will
also
probably
I'm
sure
later
into
the
hour,
talked
about
all
the
goodwill
she
does
for
new
contributors
as
well.
So
thanks
a
ton
for
all
your
work
with
being
welcoming
to
folks
in
the
community,
Carolyn
and
then
Mike.
What's
up
with
you,
hi.
C
My
name
is
my
explained:
I'm
based
out
of
snowy
Boston
and
I've,
been
working
with
kubernetes
for
before
it
hit
one
dot.
Oh
I
was
experimenting
it
with
it
at
PayPal
and
then
I
joined
a
start-up
and
they
said
what
should
we
start
with
from
day?
One
and
I
said:
let's
try
this
kubernetes
thing
and
at
the
time
there
wasn't
a
great
way
to
deploy
kubernetes
and
if
you've
been
around
a
long
time,
you
seem
like
it
can
be
hard
to
start
from
scratch
with
kubernetes
and
so
I
built
it
from
scratch.
C
How
we
ran
kubernetes
and
then
a
project
called
cops,
came
along
and
was
finally
ready
for
production
code
and
I.
Think
Andrew
was
actually
contributing
code
to
it
at
that
time
and
and
I
was
like.
Oh,
let's
switch
over
to
this
thing
and
over
time,
I
started
diving
in
more
to
cops
and
every
you
know,
I
wanted
to
add
internal
load-balancing
to
the
API
servers,
so
they
weren't
on
the
public
Internet,
and
so
that
was
like
my
first
contribution
and
I
worked
my
way
up
through
that
you
know
and
startup
life
roles.
C
Then
you
move
on,
and
so
now
I
met
Sonos
working
on
the
Sonos
cloud,
moving
everything
over
to
kubernetes
and
and
cops
and
all
sorts
of
cool
stuff.
There
I
am
a
member
of
cig
cluster
life
cycle
I'm
a
cops
maintainer
I
also
started
the
Boston
cops
Boston
kubernetes
Meetup
a
bunch
of
years
ago
and
yeah.
That's
me,
I
think
I
also
got
involved
with
Paris
when
I
got
I
did
the
mentoring
program
with
Chris
loved.
C
A
D
A
D
D
I
was
really
so
when
I
was
looking
at
digitalocean
I
was
really
interested
in,
like
cloud
provider
integrations
and
making
sure
that
you
know.
People
who
wanted
to
run
kubernetes
on
digitalocean
had
a
had
a
really
good
integration
story
for
that,
and
so
I
started
a
lot
of
trying
to
add
the
digital
Ocean
Club
provider
to
kubernetes,
and
then
I
got
sidetracked
into
the
whole
kind
of
like
external
cloud
provider.
Initiative
and
I
ended
up
taking
a
lead
on
that,
because
no
one
else
really
wanted
to
take
up
that
work.
D
A
And
I'm
I
have
a
feeling
we'll
get
a
cig
cloud
provider
question
so
I
will
hold
off
on
mine
as
well,
and
that's
the
other
thing.
I
did
tell
the
panelists
as
well
before
we
started
that
they
too
can
ask
each
other
questions,
because
mentoring
isn't
necessarily
about
mentoring,
someone,
that's
junior,
but
it's
about
mentoring,
each
other
through
our
challenging
times
and
fun
times
as
well.
All
right.
A
B
B
It
I
just
started
in
Microsoft
and
I
was
told.
Basically,
you
are
going
to
be
contributor
to
Service
Catalog
and
we
have
a
command
line
tool,
SP
cat,
that
we
want
to
contribute
Service
Catalog
and
we
written
some
of
the
command
line,
tool
and
I've
been
there
for
a
month
and
I'd
like
filled
it
out
a
lot
more
and
wanted
to
gift
it.
B
If
you've
been
an
opensource
long
enough.
You
know
that
no
one
wants
your
gift
of
code,
like
a
giant
like
oddly
wrapped
in
pine
I've
got
tape
all
over
and
why
not
there
so
I
could
try
to
like
match
the
code
in
their
repo
and
show
where
I'm
going
with
it,
but
at
the
same
time
I
haven't
wanted
to
just
like
make
it
totally
complete,
because
what,
if
they
didn't
want
it,
then
we'd
wasted
a
ton
of
time
and
I
was
being
knitted
to
death
because
it
wasn't
finished.
B
But
at
the
same
time,
if
it
had
been
finished,
they
would
have
been
mad
at
me
for
through
that
as
well.
The
politics
of
it
were
just
so
intense
beyond
anything.
I
had
ever
encountered
an
open-source
before
and
then
I
was
trying
to
navigate
like
the
feedback,
which
was
do
I
need
to
listen
to
this
person.
Do
I
have
to
change
every
single
thing
based
on
every
single
piece
of
feedback,
or
can
I
go.
B
B
So
it's
constantly
like
talking
to
a
manager
or
to
other
people
on
the
team
trying
to
figure
this
out,
and
it
was
really
hard
to
to
go
over
so
I
think
it
took
like
a
month,
and
it
was
many
meetings
and
things
like
that,
and
we
decided
never
to
do
something
like
this
again,
not
only
gifting
code,
but
to
have
a
large
PR
that
needed
to
be
perfect
before
we
could
merge
it,
and
that
was
a
problem
with
the
sig.
If
the
concept
was
a
PR
had
to
be
perfect
to
merge.
B
This
is
inspired
an
idea
that
we've
kind
of
done
like
Aaron
Schlessinger,
is
another
person
who
did
this
use.
My
manager
I
gave
a
follow-on
PR,
which
is
as
long
as
the
PR
is
good
enough
that
it's
not
going
to
hurt
the
codebase
if
it
goes
in
it
goes
in,
and
then
we
make
PRS
and
issues
that
promise
to
fix
certain
things
or
change
certain
things
or
have
those
design
discussions.
B
B
Pr
now
so,
instead
of
like
one
big
one,
I
get
in
the
skeleton
for
something
and
then
five
other
people
are
able
to
tack
and
like
have
an
argument
about
how
to
do
something
in
an
issue
and
then
somebody
else
is
able
to
contribute
one
thing
and
another
and
another.
It
means
that
masters
maybe
a
little
more
unstable,
but
you
don't
end
up
with
them,
PR
that
takes
a
month
or
two
or
three.
D
D
D
What
the
intention
of
the
proposal
is,
the
implementation
details
and
one
of
the
nicest
things
is
that
there
needs
to
be
an
approver
from
the
sig
and
usually
that
approver
also
has
access
to
approve
your
PRS,
and
so
it
really
helps
streamline
some
of
the
initiatives
that
people
have
instead
of
like
people
just
like
opening
these
huge
PRS
and
then
yeah
like
having
them
reviewed
for
over
months,
it
usually
like,
gets
merged.
Maybe
in
like
a
few
weeks,
instead,
yeah.
B
We
eventually
this
thing
started
doing
caps,
but
we
didn't
even
have
a
process
to
do
them
at
the
time
and
yeah
I.
Think
that's
something
that
if
SIG's
it's
hard
to
figure
out
like
do
we
do
what
the
main
kubernetes
group
does.
Or
do
we
do
our
own
thing,
I,
don't
know
if
other
SIG's
have
that
problem
or
not
as.
A
B
A
cig
is
a
special
interest
group
and
it's
a
group
of
people
who
sign
up
to
say
we're
interested
in
a
problem
or
a
set
of
problems
and
related
code
and
questions
that
isn't
part
of
core
kubernetes,
so
Service
Catalog
isn't
in
Korakuen
at
ease
it's
a
set
of
code.
That
goes
it's
in
the
incubator.
Nowadays
they
would
go
inside
of
the
kubernetes
SIG's
organization.
B
There's
other
ones
for
networking.
I
know
there's
so
many
to
list
like,
of
course,
my
mind
is
blankey.
When
you
ask
me
to
list
them,
but
there's
one
for
apps
contributor
experience.
It
could
be
anything
really
as
long
as
a
bunch
of
people
are
willing
to
get
together
and
argue
on
the
regular
basis.
You
can
do
it
I.
D
D
The
sake
we're
like
you,
know,
cofounders
of
kubernetes
or
like
API
reviewers
or
like
top
level
owners,
and
so
a
lot
of
a
lot
of
what
we
thought
were
priorities
for
sake
weren't,
always
in
line
with
what
some
of
the
like
the
kind
of
like
technical
leads
of
the
entire
project
had
in
mind,
and
so
there
was
a
lot
of
like
that's.
Why
I
like
we
gravitate
towards
keps,
because
then
we
can
make
the
cap
and
make
sure
that
those
people
review
it
but
yeah.
There
was
a
there's
this,
like
long
period
where
we
were.
D
C
My
most
challenging
PR
was
probably
either
my
first
or
my
second
I
feel
like
I.
My
first
PR
was
probably
like
a
Docs
change
or
something,
but
my
second
PR,
where
it
was
like
actual
code
work
on
cops.
Specifically
if
you've
ever
looked
at
how
cops
works.
You
know
you're
talking
about
the
complexity
of
running
kubernetes,
but
then
you're
also
talking
about
running
it
on,
in
my
case,
AWS
and
then
you're
talking
about
you
know,
the
clouds
form
oh,
not
cloud
formation,
but
you
know
the
scripts
to
make
the
auto
scaling
groups
work.
C
The
actual
you
know,
networking
components
to
make
sure
the
networking
works
and
then
starts
up.
Oh
my
now
it's
a
whole
nother
world.
You
know
we
pulled
down
two
different
components
in
order
to
actually
get
the
instance
starting
up
with
our
code
with
the
cops
code,
and
then
we
start
pulling
in
kubernetes
core
components
and
there's
a
lot.
C
C
You
know,
because
if
you
look
at
the
way
these
things
work,
if
it
generally
pulls
from
open
source
to
do
a
lot
of
docker
containers
that
do
this
and
do
that
on
the
box,
and
you
know
if
you're,
just
a
user
of
cops,
for
instance,
it's
it
just
kind
of
you
click
it,
and
you
know
you
get
an
instance
up
in
two
or
three
minutes
now.
If
that
instance
doesn't
do
what
you
expect
it
to
do
now,
you
got
to
figure
out
how
to
SSH
into
it.
C
You
got
to
figure
out
how
to
see
what
each
of
these
components
are.
What
is
an
Oda?
What
are
what
are
all
these
different
pieces
that
just
magically
makes
kubernetes
chug
on
cops,
and
so
my
first
one
was
definitely
like
it
wasn't.
Even
the
code
I
was
changing,
it
was
how
do
you
do
all
of
that
and
how
do
you
do
it
in
a
dev
environment
to
make
sure
that
whatever
I'm
gonna
contribute
isn't
gonna
break?
C
Anything
else
you
know
and
I
feel,
like
part
of
it
to
me,
was
also
like
I've,
been
like
a
lurker
for
so
long,
just
like
looking
at
github
issues
and
and
seeing
so
many
people
do
really
great
things
that
I'm,
like
oh
wow,
that's
a
great
idea.
I
wish
I
could
contribute
something
and
then
I
was
like.
Why
doesn't
this
exist?
Everyone
probably
needs
this.
C
You
don't
want
this
public
on
the
Internet
and
I
dove
in
and
I
just
I
didn't
want
to
disappoint
all
those
people
that
I
had
seen
working
on
the
project
for
so
long
and
I
didn't
want
to
be
embarrassed
for
my
first
like
real
PR,
but
then
it
turned
out.
You
know
once
the
review
came
in,
everyone
was
kind
of
like
all
right
great.
C
You
missed
this
one
thing
this
test
here
you
know,
but
besides
that,
let's
get
this
into
master,
so
we
can
kind
of
get
this
rolling
and
I
would
I
would
honestly
just
say
the
hardest
thing
for
me
was
the
first.
You
know
the
first
real
big
PR
once
you
get
that
one
in
everyone
beyond
that,
you
can
kind
of
look
back
at
that
PR
and
be
like
what
did
I
miss.
What
could
I
have
done?
Better
hadn't
happened.
You
know
my
communication
been
better
and
whatnot.
That's.
C
Yeah
I
feel
like
that's
one
of
the
hardest
parts
about
kubernetes.
To
be
honest
like
it's,
it's
always
changing.
You
know
and
then
like
if
you
upgrade
to
a
new
version,
even
just
like
the
the
API
has
changed
and
you
know
you
go
to
create
a
an
object
and
it's
a
new
version
of
an
API
and
if
you're
not
watching,
you
don't
really
know
what's
happening
in
the
whole
kubernetes
ecosystem
and
in
my
role
at
Sonos.
C
That's
part
of
my
job
is
to
like
figure
these
things
out
and
one
of
the
things
that
I
tell
people
is
the
kubernetes
blog
is
amazing,
I
to
it
and
slack
so.
I
get
a
notification
any
time,
there's
a
new
blog
post
and
I.
Just
it's
great
just
to
like
it's
not
gonna,
be
everything,
but
it's
like
hey.
This
new
thing
is
coming
in
the
next
version
or
I.
Also
look
at
the
release,
notes
for
major
kubernetes
versions.
You
know
and
read
through
those
and
yeah.
C
You
know
you
can't
get
too
deep
on
on
some
of
those
things,
but
just
being
open
to
the
changes
that
that
are
coming
upstream
and
a
lot
of
blog
posts
and,
and
then
there's
things
like
communication
and
and
also
the
I
guess.
The
podcast
to
the
podcast
has
been
grated
in
the
past
year
like
really
see
what
new
things
are
happening
and
in
the
ecosystem
and
everything.
D
And
I
think
in
reality
that
you,
you
kind
of
can't
like
in
some
sense
you
don't
like
you
can't
keep
up
with
everything
and
so
like.
You
hope
that
any
breaking
change
is,
you
know,
put
in
the
release,
notes
and
is
vocalize
very
well
but
implementation
details.
You
know
internal
API
changes
like
those
things
like
you,
you
won't
know
about
it
until
you
have
to
deal
with
it
yourself
that.
A
B
I
don't
want
to
stay
like
I
know,
people
say
you
can't
I'm
saying
I,
don't
want
to
I,
guess
I'm,
just
I
/
we're
about
burnout
lately
and
part
of
burnout
is
thinking
that
you
should
want
to
stay
up
to
date
and
that's
my
question.
The
question
I
understand
where
it's
coming
from
and
I
used
to
want
to
be
like
that,
because
I
felt
that
it
would
somehow
help
me
to
be
able
to
have
an
informed
opinion
about
every
single
thing
about
this,
but
in
reality,
like
I,
have
a
little
area
of
kubernetes.
B
That
is
important
for
me
to
have
opinions
about
know
about
and
beyond
that
being
aware
of
things
so
most
part
and
knowing
every
single
thing
that's
changing
about.
It
is
not
helpful
and
just
adds
to
this
emotional,
like
burden
and
so
I'm
actually
happier
not
trying
to
pretend
to
be
superwoman
I
guess
so
things
are
important
to
what
it
takes
to
do
my
job
well,
but
I
don't
need
to
be
because
my
dogs
were
a
low
leveled
in
the
like
the
trenches
right
I'm,
not
someone
who
needs
to
know
kubernetes
at
50,000
feet.
B
C
I
love
the
way
he
just
said
that
that's
that
spot
on
and
I
think
that
originally
when
kubernetes
first
started
it
was
so
there
was
a
lot
less
and
there
was
a
lot
less
content
out
there.
So
you
kind
of
had
to
hoard
it
everything
you
could
find.
It
was
like.
Alright
I
need
to
digest.
This
I
need
to
learn
this.
Oh
yeah,
that's
the
only
way.
I'm
gonna
do
this,
but
now
there's
just
so
much
out
there.
C
So
if
you
haven't
worked
on
auto-scaling
for
a
while
and
then
you
know,
I
like,
for
instance,
I
work
with
a
lot
of
users
and
they're
like
oh,
we
need
to
learn
how
to
use
the
horizontal
pod
autoscaler.
Alright,
let's
go
find
info,
you
know,
and
and
so
you
don't
need
to
always
stay
on
top
you.
The
info
is
out
there.
Now
it's
it's
that's
a
great
point.
C
A
Plug
for
say,
architecture,
they
meet
I,
think
by
weekly
on
Thursdays
I.
Think
their
next
meeting
is
not
this
Thursday,
but
next
Thursday,
and
if
you
just
google
cig
architecture,
kubernetes
github
that
you'll
get
right
to
the
github
page.
So
all
right,
then
we
have
we.
We
have
just
questions
rolling
in
at
this
point,
so
I
think
we
are
filled
for
the
hour.
But
third
direct
message:
question
from
slack.
A
What
do
you
think
is
a
priority
for
the
crew
for
the
kubernetes
community
to
focus
on
right
now?
Obviously,
all
your
answers
might
be
different
and
that's
totally
okay
and
it
might
be
even
you
know,
a
semi
personal
response
and
that's
cool.
So
in
your
in
your
opinions,
what
do
you
think
it's
a
priority
for
us
to
focus
on
right
now,
I.
B
B
Ways
to
respond
to
things
that
push
them
towards
burnout,
not
just
encouraging
them
to
tell
them
the
word
self-care,
but
to
give
them
like
I
mentioned
etiquette
before,
like
I,
don't
know
how
to
respond
to
certain
things
now.
I
have
to
spend
a
lot
of
time
like
going
through
like
what.
If
I
say
this,
how
will
they
respond
like
that
type
of
stuff?
B
Is
this
emotional
overload,
like
this
mental
overhead,
giving
main
painters
better
ways
to
deal
with
things
and
then
giving
them
like
concrete
ideas
for
how
they
could
organize
their
day
and
being
able
to
say
I?
Just
do
these
things
and
here's
how
I
can
offload
this
type
of
work
and
just
giving
more
tips
and
tricks
in
their
tool?
B
Who's
like
yeah
I
can
do
this
now
and
some
tired
person
goes
great.
I'm
gonna
put
you
through
the
meat
grinder
and
then
they
hand
it
off
to
the
next
person
and
they
they
get
six
months
on
to
them,
and
then
it
just
this
keeps
happening
and
like
we
need
to
set
up
something.
That's
more
sustainable
and
you
can't
just
say
like
carve
out
time
for
yourself.
We
need
something,
a
lot
more
concrete.
B
Hearing
a
lot
from
community
years
is
that
we've
built
a
really
interesting
infrastructure
with
kate's,
but
when
it
comes
to
end
users,
platform
and
I've
heard
a
lot
of
calls
for
a
sick
user
experience
and
I'd
be
really
interesting
to
see
what
we
could
build
on
top
of
companies.
Instead
of
adding
more
to
the
feature,
soup
I
would
love
to
see
cqx
that
actually
says.
What
can
we
build
on
top
of
this
and
then
makes
I?
Don't
know
this
path,
I?
B
A
D
Just
wanted
to
respond
to
your
point:
I
couldn't
effing
utley
relate
to
I
can
definitely
likes
that,
because,
when
I
first
became
a
Seco
chair,
I
had
this
idea
that
being
a
co-chair
meant,
you
know,
like
voting
all
the
code
and
like
reviewing
all
the
PRS
and
like
getting
all
the
commits
in,
but
I
think
over
time.
I'm
realizing
more
and
more,
that
being
a
co-chair,
actually
means
like
raising
mindshare
on,
like
what
the
efforts
of
the
cigar
and
like
echoing,
that
to
the
community
making
sure
everyone
is
on
the
same
page.
D
Making
sure
that,
like
the
caps
that
are
in
place
can
be
implemented
easily
by
new
contributors
and
other
people
and
I
think
worse.
A
lot
of
the
SIG's
are
stuck
are
still
stuck
in
that
mentality,
that
oh
I'm
I'm,
a
tech
lead
or
a
co-chair
of
the
sake.
And
so
my
goal
is
to
just
review
all
the
PRS
and
so
I.
Think
we
need
to
yeah,
like
one
of
the
priorities
should
be
like
shifting
that
mentality
towards
like
you're,
not
just
reviewing
code
but
like
yeah
you're,
making
sure
that
everyone
is
on
the
same
page.
D
A
E
C
That's
a
great
question:
well,
it's
I!
Guess
it's
been
around
for
a
while,
but
just
getting
more
people
involved,
because
that
kind
of,
at
the
end
of
the
day
helps
everyone
to
what
Carolyn
and
Andrew
were
both
saying
is
like
the
more
people
that
can
help
the
more
people
submitting
PR
the
mohair
PRS.
The
reviewers
can
review
the
more
pr's.
C
They
review,
the
more
likely
they'll
move
up
to
approver
and
then
they
can
take
the
load
off
the
current
approvers
and
and
that's
kind
of
how
things
have
worked
for
a
while,
and
you
know
as
they
eluded
to
a
lot
of
times.
People
burn
out
and
and
move
on
or
just
disappear
from
project,
and
then
they
pop
their
head
back
up
later
and
and
so
I
guess.
C
My
thing
would
be
really
you
know,
for
people
to
you
know,
don't
just
open
an
issue
on
something
that
that
you're
experiencing
trying
to
figure
out
a
solution,
and
if
you
don't
know
the
whole
solution,
that's
fine,
like
I,
think
github
just
opened
up
a
thing,
the
other
day
of
draft
PRS
and
stuff
I,
don't
know
if
we've
enabled
it
but
like
I'm
always
like.
If
you
mark
your
your
PR
is
work
in
progress.
A
Yeah
that
work
in
progress
is
something
that
we
don't
necessarily
talk
about
a
lot
I
think
as
a
community,
maybe
something
we
can
bring
up
and
contributor
experience
in
general,
just
like
as
far
as
like
etiquette,
you
know
it's
concerned
and
things
like
that
and
then
Andrew
did.
You
have
anything
else
to
add
to
that.
As
far
as
community
focus.
D
I
guess
stability
and
extensibility
I
think
we're
all
heading
towards
that
idea
that
you
know
kubernetes
is
a
platform
for
platforms
and
so
making
sure
it's
it's
stable
and
making
sure
there's
the
extension
points
are
a
right
and
that
it's
it's
gonna
be
set
up
perfectly
for
more
platforms
to
be
built.
On
top
of
it.
I
think
that's
really
important.
Right
now,.
A
Cool
all
right,
I'm,
sorry
I'm,
getting
like
getting
through
my
DMS
here
all
right.
We
have
a
question
on
discussed
at
kubernetes
that
I,
oh,
oh,
this
is
actually
from
a
doir
at
large
just
completed
his
outreach
internship
with
kubernetes.
He
actually
did
it
with
contributor
experience.
We
have
a
massive
devil
filter.
What
this
is
as
a
bunch
of
developer,
documentation
for
people
building
upstream
kubernetes
that
need
things
like
API
conventions
and
whatnot.
This
is
inside
of
the
community.
A
Repository
and
Edward
really
helped
us
with
some
new
structure
for
that,
so
that
technical,
technical
folks
can
help
us
with
updating
Doc's.
So
they
don't
need
to
hit
the
root
of
the
folder
and
things
like
that.
But
ed
wants
to
know.
While
contributing
have
you
ever
had
to
use
the
kubernetes
developer
guide
and
if
not,
when
you're
looking
for
documentation.
Where
do
you
look
for
it.
D
A
That's
good
feedback,
because
we
actually
don't
hear
that
I
mean
we
don't
have
analytics
against
our
Doc's.
You
know
so,
like
that's
the
that's
the
tough
part
when
we're
trying
to
talk
about
discoverability
and
how
Doc's
are
structured
and
things
like
that,
and
we
just
don't
have
that
info
I
mean
we
we've
assumed
that
we've
made
that
assumption.
A
So
that's
a
very
popular
doc,
just
based
on
the
changes
that
come
through
and
how
often
and
things
like
that,
but
still
just
like
hearing
that
from
you
I
think
it's
super
important
and
people
like
Eduardo
are
constantly
making
changes
to.
It,
need
to
hear
that
stuff
to
Carolyn
and
Mike.
What
about
you
all?
Did
you
use
any
of
the
docs
inside
of
the
developer
guide
and
what's
your
general
sense
of
like
how
how
things
should
go
in
there?
A
B
Just
recently
used
the
logging
conventions
because
we
were
trying
to
switch
over
from
having
no
conventions
in
service
catalog
to
trying
to
follow
kubernetes.
So
maybe
she
found
that
incredibly
useful.
It's
still.
Sometimes
we
were
still
struggling,
though
with
like
something
new
at
the
docks.
Unfortunately,
it
was
like
there's
numbers.
You
know,
log
level,
three
log
level,
four
log
level:
five.
B
We
were
still
struggling
to
figure
out
how
to
make
sure
that
when
people
were
using
three
four
five
in
code
that
they
were
using
the
right
one
like
when
you
had
a
person
submitting
us
a
PR-
and
we
saw
three
four
five
in
the
code-
we'd
have
to
go
back
to
that
dock
and
reference
and
make
sure
that
they
were
using
three
four
five
appropriately
and
we
weren't
quite
sure
how
to
make
sure
like
consistently
that
that
was
happening.
So
we
keep
going
back
to
the
dock,
but
it's
still
something
that
we
struggle
with.
I.
B
C
I
guess
I
can
I
could
be
the
bad
person
in
the
room
and
say
that
I
didn't
even
know
this
existed,
but
it's
awesome.
I
I'm
shocked
that
I
had
never
heard
of
it.
Granted
a
lot
of
what
I
work
on
is
more
downstream
on
the
cop
stuff
of
like
hey,
look,
there's
this
feature,
let's
implement
it
and
make
sure
that
you
know
we
can
use
it
in
the
cops
ecosystem,
but
we
have
our
own
docks
similar
to
this
and
they're.
C
A
A
So
then
we,
let's
do
two
ooh
Carolyn's
question,
so
Carolyn
recently
stepped
down
from
a
project
service
catalog,
and
she
can
talk
to
us
a
little
bit
about
what
it's
like
to
run
out
of
steam
and
how
to
pick
a
new
project
within
the
kubernetes
ecosystem.
Give
us
some
tips
give
us
some
of
those
hot
takes
yeah.
B
It
was
hard
took
months,
it's
kind
of
weird,
because
when
I
like
help
new
people
and
when
I
came
in
I
was
so
excited
to
pick
a
project
right,
you
make
all
of
these
commitments,
maybe
just
to
yourself
you're,
like
I'm,
going
to
become
a
contributor
I
may
become
a
maintainer
I'm,
going
to
figure
out
how
to
do
releases.
All
the
other
releases.
Every
week,
I'll
help
bring
out
new
contributors.
B
I'll
answer
questions,
I'll
be
a
reviewer
and
then
at
some
point
the
project
either
doesn't
get
you
excited
anymore
or
you've
finished
whatever
it
is,
got
you
excited
in
the
first
place
when
I
got
that
CLI
and
I
got
defaulting,
and
all
these
various
features
I
was
really
excited
about
we're
in
and
those
the
projects
stabilized,
and
there
just
wasn't
as
many
things
to
do
that
either
me
or
my
company
cared
about
and
I
move
teams,
I
moved
to
the
home
team
and
I
start
working
on
different
stuff
and
Microsoft
was
like
that's
cute
Carolyn,
but
you
know
you
need
to
do
these
other
things
you
can
work
on
Service
Catalog
on
Sundays
I
was
like
oh
okay,
maybe
not,
and
then
all
of
a
sudden
that
had
to
unpack
how
do
I
let
go
of
all
these
commitments
without
feeling
like
a
horrible
person.
B
Well,
Paris
hate
me
like
these
really
awesome
went
through
my
head
and
it
took
me
months
to
figure
out
how
to
set
all
these
things
down,
because
I
was
like
one
of
the
signals
I'm
the
most
active
chair
I
was
at
the
time
the
most
active
person,
submitting
PRS
and
doing
reviews,
and
it's
like
it
made
me
feel
personally
responsible
for
whether
or
not
the
cig
lived
or
died,
and
that
was
like
awful
so
eventually
like
I
got
over
it.
But
like
that's
another
reason.
B
Actually,
one
of
the
things
I
was
really
excited
about
fit
inside
gaps
really
well
as
just
as
well
there.
So
that's
a
cap
that
got
passed
through
with
his
help
and
it
didn't
have
to
die
just
because
I
moved
off
to
do
something
else,
which
was
a
huge
weight
off
my
shoulders,
which
was
great
and
then
I
was
able
to
step
down
as
a
chair
and
get
someone
else
set
up
instead
and
I
moved
on
to
a
project
that
is
super
new.
B
This
one
is
a
little
out
of
runway
cloud
native
application,
bundles,
which
has
some
command-line
tools,
because
that's
where
I
love
to
live
as
close
to
the
user
as
possible,
and
some
of
those
tools
were
hoping
to
eventually
get
into
like
duffle
or
Porter,
where
we'd
also
like
to
eventually
contribute
to
the
CNCs
and
they
interact
with
things
like
communities
and
things
like
that.
So
maybe
they're
not
like
part
of
the
ecosystem,
I
think
of
them
as
probably
ecosystem,
because
they
work
with
kubernetes.
B
They
work
with
how
they
work
with
all
these
things
that
my
cluster
so
I.
Think
of
them
as
the
same
thing
and
I'm
I've
already
started
finding
new
contributors
building
up
new
guides
figuring
out
to
make
things
work
better
and
taking
all
the
things
I
learned
that
made
it
so
hard
to
put
down
these
commitments
and
trying
to
make
sure
that
they
aren't
single
person.
Commitments
to
begin
with
next
time.
So
we'll
see
I,
don't
know
talk
to
me
again
in
two
years
as
I
start
the
cycle
all
over
again.
B
C
Sure
yeah
I
mean
so
I
changed
jobs
about
six
months
ago.
From
a
start
up,
and
at
that
point
you
know,
I
was
running.
The
kubernetes
meetup
here
in
Boston
and
I
was
getting
deeply
involved
in
cops
because
it
was
like
well
if
I'm
running,
cops
and
I'm
I
need
to
make
changes
to
cops,
I
might
as
a
little
like
dive
head
on
into
cops,
and
so
it
was
a
lot
of
cops
and
then
we
moved
on.
C
You
know
when
I,
when
I
change
jobs,
it
was
like
I
had
to
start
over
from
scratch
like
rebuild
everything
internally
at
Sonos,
and
it
was
just
more
like
I.
Can't
I
can't
manage
all
this
stress
of
building
a
new
thing,
giving
guidance
to
the
rest
of
my
team
on
how
to
build
it
right
since
I've
been
around
longer
than
any
of
them
on
this
stuff,
and-
and
you
know
what
how
do
I
keep
myself
healthy,
you
know
for
for
my
family
and
I
have
a
puppy.
That's
that's
a
lot
of
work
as
well.
C
So,
like
you
know,
it's
you
have
all
these
things
that
build
and
and
I
can
definitely
relate
to
them.
100%
and
I've
had
to
step
back
a
little
bit
from
from
the
meetup
here
in
Boston,
just
because
it
takes
a
lot
of
work.
I
appreciate
the
work,
Paris
and
and
and
Jorge,
and
everyone
does
to
pull
these
things
together,
because
it
is
a
lot
to
do
anything.
Even
even
you
know
this,
the
smallest
events
are
amazing
amounts
of
work,
and
so
I've
just
had
to
like
back
away
from
some
of
my
commitments.
C
I
hadn't
stepped
out
of
them,
but
I've
had
to
like
just
dip.
My
toe
in
you
know
sometimes
and
and
stay
a
little
bit
on
the
outside
and
then
kind
of
come
up
with
some
new
structure
structure
so
that
I
don't
get
burned
out,
but
I
think
there.
There
is
a
time
where
I
get
like
this
close,
where
you're,
just
like
I
need
to
go
on
a
vacation
for
a
month
and
not
look
at
any
of
this
stuff.
A
C
Well,
and
for
me
specifically
I'm,
try
try
my
best
to
make
sure
specific
to
the
meetup
that
it's
not
like
one
company
coming
in
and
selling
their
new
kubernetes
product
and
that's
remarkably
hard
to
find
people
that
are
like
you
can
you
can
work
on
a
product
you
can
come
on
in
and
and
mention
your
product
and
talk
about
it.
I'm
totally
cool
with
that,
but,
like
I,
want
everyone
to
come
in
and
be
passionate
about,
kubernetes
and
and
the
stuff
we're
building
and
and
the
companies
that
come
in
and
say.
C
A
B
No
I
just
want
to
say:
I
want
to
start
up
meetup
with
no
speakers,
because
having
brought
a
couple
and
that's
the
hardest
thing,
is
you
have
to
deal
with
the
tap
down
so
like
entertain?
Someone
answer,
however,
often
you're
doing
it
and
if
you
could
just
say,
I'm,
not
a
space
they're,
giving
us
pizza
and
the
hardest
thing
I
have
to
do,
is
put
on
pants
and
show
up
at
somebody's
office
like
once
a
month
like
I
can
handle
that
and
if
we
show
up
and
chat
and
have
a
good
time,
that's
cool.
B
And
if
someone
wants
to
show
something,
that's
fine
but
there's
zero
commitments
from
us
and
anyone
like.
If
that
doesn't
make
a
fun
meet
up,
then
that's
fine
natural
falls
apart,
but
there's
no
commitments,
I'm
gonna
be
a
fun
Meetup.
Maybe
would
take
some
of
the
burnout
factor
out
of
it
because
I
people
always
people,
do
they
just
show
up
and
sit
in
the
chair
and
then
expect
you
to
feed
them.
Pizza
and
I
retain
them
for
an
hour
which
is
not
fun
as
an
organizer
I.
D
Definitely
I
agree
with
you
hundred
percent.
I
I
don't
I
kind
of
stopped
going
to
the
meetup
in
Toronto,
because
I
would
go
there
sit
down
for
two
hours,
listen
to
talks
and
then
like
and
then
by
then
it's
like
9
o'clock,
they're
going
to
sleeves
it'd,
be
great.
Just
like
I
want
to
hear
people's
community
stories.
D
B
C
Totally
and
that's
that's
actually
one
of
the
things
we've
tried
to
do
like
we
were
packing.
Three
speakers
in
you
know:
35
40
minutes
each
with
a
with
a
couple
breaks
and
all
that
stuff,
but
but
yeah
we
like
eventually
we're
just
like
wait,
a
second
the
best
meetup
we
had
I
think
one
time
we
had
one
speaker
and
then
it
was
just
like
I
got
up
there
and
was
like
what
do
you
guys
want
to
talk
about?
C
Let's
shoot
out
some
topics
and
then
you
know
someone
asked
about
networking
and
I
was
like
alright,
who
in
the
room
knows
about
kubernetes
networking,
and
luckily
one
of
the
other
guys
was
like
well
deep
into
calico,
and
so
like
talked
about
how
calico
works,
you
know
those
it's
so
cool
when
it
just
like
organically
comes
together.
You
know
and
and
I
agree.
Those
are
the
most
fun
meetups
and
that's
some
helpful
feedback
for
me
as
well.
So
we'll
we'll
try
to
do
that
here
in
Boston,
more
yeah.
A
That's
it's
still,
there's
still
a
lot
of
curation
I
think
even
in
the
ones
that
seem
unstructured.
You
know
from
an
organizer
perspective,
I
do
the
Bay
Area
kubernetes
meetup,
and
it's
we
always
revert
back
to
the
lecture
style
because
from
a
organizers
perspective
when
contents
coming
in
it
just
seems
so
much
easier.
Just
so
like
book,
the
lecture
and
I
mean
a
lot
of
the
times.
It's
good
content,
but
then
it's
just
like
you
know
what
Andrews
saying
it's
there's
no
networking
there
at
all.
A
You
know
I
would
be
the
first
one
to
tell
you
that
the
meetup
does
not
have
any
networking
very
limited
networking
and
then
now
trying
to
press
retro
actively
change
that
culture
is
it's
pretty
difficult,
so
for
all
of
you
aspiring
meetup
organizers
out
there
we
aspire.
Well,
we
encourage
you
to
figure
out
how
to
deliver
creative
content
to
us
anyway.
All
right
I
think
that's
it
for
questions,
though
I
am
looking
one
more
time
through
all
of
the
different
various
mediums
here
and
unless
anybody
has
other
questions,
I'll
do
a
wrap
up.
A
I,
don't
see
anything
else
when
I'm
gonna
leave
for
more
place,
one
more
place
and
that's
a
no
all
right.
Well
we're
wrapping
things
up.
Thank
you.
So
much
to
Jorge,
Castro
Jorge
come
off
of
you.
Can't
wave
to
us
come
off
hey
thanks!
So
much
for
Jorge,
helping
our
YouTube
stream
stay
nice
and
steady
and
make
sure
that
people
can
hear
us.
That's
a
thing
and
thanks
again
to
all
of
the
people
who
joined
our
little
mentoring
panel,
Shin
big
circus
today
appreciate
all
of
you
and
your
words
of
wisdom.
A
Each
one
of
you
are
extremely
valuable
to
the
project
and
wish
you
much
success
all
right,
and
that
is
it.
We
will
see
you
next
month,
that
is
April
6th,
I
believe
don'tmove.
Actually,
let
me
get
a
calendar.
Am
I
right?
Am
I
right?
April
3rd
I
was
wrong
same
time,
7:30
a.m.
Pacific,
1
p.m.
Pacific
and
we're
out
see
you.