►
From YouTube: Kubernetes Meet Our Contributors 20180404 (US Edition)
Description
Come join us, first Wednesday of every month! https://github.com/kubernetes/community/blob/master/mentoring/meet-our-contributors.md
C
B
B
We
have
a
wonderful
array
of
upstream
contributors
with
us
today
who
will
be
taking
questions
from
the
meter,
contributor,
slack
channel
and
also
toggle,
if
I
can
between
Twitter
as
well.
So
if
you
are
on
Twitter
watching
this,
if
you
want
a
hashtag
k8s
moc
for
kubernetes
meet,
our
contributors
will
go
ahead
and
answer
your
questions
there
as
well.
If
we
can
get
to
those
this
series
as
a
part
of
our
mentor
evening's
race,
these
are
your
mentors
on
demand.
B
If
you
are
out
there
looking
for
a
mentor
every
month,
we're
here
at
the
same
time
same
place,
and
these
folks
can
answer
your
questions
that
range
from
how
they
got
into
open
source
wash
kubernetes
all
the
way
to
all
the
way
to
buy.
As
my
end-to-end
test,
failing
and
I
have
no
idea
what
I'm
doing
or
what's
they
do,
I
join
really
anything
in
between
there.
So
first
thing
we're
gonna
do
right.
Now
is
just
do
some
quick
introductions,
Carolyn,
why
don't
you
go
first,
yeah.
D
Sure
so
this
is
my
first
time
doing
meet
our
contributors.
I'm,
pretty
new
to
being
a
community's
contributor.
I
was
hired
in
November
on
the
Microsoft
Azure
z--,
as
your
container
team
and
I'm
pretty
much
paid
work
on
a
percent
of
the
time
when
Service
Catalog,
which
is
the
most
awesome
thing
in
the
world.
It
was
like
my
life's
goal
to
do
open
source,
full-time
and
the
way
I
got
into
kubernetes
actually
was
playing
around
with,
like
ripping
videos
to
make.
My
in-home
like
DIY,
Netflix
and
I,
have
like
a
little
poni
cluster.
D
D
E
Can't
live
up
to
that
there's
hi
I'm,
Aaron,
Creek
and
Berger.
My
user
name
is
sniff
XP
on
you
know:
github
Twitter
and
LinkedIn
SoundCloud
Tumblr.
All
the
places
I
have
been
with
the
kubernetes
project
since,
before
it
went,
1.0
I've
been
on
this
epic
tiny
request
of
doing
platform
as
a
service
and
cloud
and
DevOps
type
things
before
I
ran
into
the
nice
abstractions
and
simplicity.
That
kubernetes
has
provided
I
helped
co-found.
E
The
special
interest
group
around
testing
kubernetes
I've,
also
been
an
active
participant
in
special
interest
groups
around
scalability
architecture
and
contributor
experience,
and,
lastly,
I
am
an
elected
member
of
the
kubernetes
steering
committee,
which
means
I
have
meetings
about
meetings
about
documents
about
passion.
It's
great.
C
Next,
all
right,
I'm
going
to
hear
I
am
actually
a
co-worker
of
Aaron's
and
Sampson,
and
we
have
been
officially
since
last
August
but
unofficially,
for
about
a
year.
I
am
very
new
to
kubernetes
and
also
fairly
new
to
tech.
I
attend
an
ADA
developers
Academy
in
Seattle,
which
is
how
I
joined
Sampson
as
an
intern
and
then
as
an
employee.
C
C
B
A
Am
on
George
Castro
I
work
at
hep,
do
where
I'm
the
community
manager
and
I
mostly
do
a
lot
of
work.
It's
a
contributor
experience
with
all
of
these
five
people.
Putting
on
programs
like
this
with,
so
that
all
of
you
watch
you
can
have
a
good
time
and
do
stuff
so
as
I'm
going
I'll
probably
kill
my
video
but
I
like
to
toss
things
at
the
slack
and
I
make
sure
that
the
stream
is
running
well,
so
I'll,
chime.
F
B
B
But
first
question
is
actually
a
similar
question
that
we
had
earlier
timeslot,
but
this
is
based
off
of
your
experience.
So
that's
the
best
part.
If
there
is
one
thing
that
you
could
tell
both
a
new
contributor
as
well
as
a
current
contributor
that
you
don't
think,
gets
a
lot
of
either
press
or
it's
not
talked
about
enough
or
just
any
kind
of
tip
or
advice.
That's
I'm
asking
for
two
one
for
a
new
and
one
for
a
current.
What
would
that
be?
And
whoever
wants
to
jump
in
to.
A
Go
it
looks
like
Jordan
talking
I'm
interrupting
first
like
if
I
built
a
time
machine
to
talk
to
myself
like
a
year
ago,
because
it
hasn't
been
that
long.
The
number
one
thing
I
would
tell
myself
stop
trying
to
figure
out
the
whole
thing.
It's
impossible
like
the
people
who
wrote
it
and
everything
don't
even
know
it's
it's
it's
a
huge
beats.
It's
distributed.
Everything
is
eventually
consistent
at
some
point,
is
kind
of
like
the
mantra.
A
I've
been
learning
from
things
so
like
if
you
think
that
you
like
it,
was
a
point
of
frustration
for
me
that
you
know
I'm
two
weeks
in
I,
still
don't
get
it
I
got
it
up
and
running,
but
I
don't
understand
every
single
little
part
like
as
soon
as
I
realize
that
oh
nobody
does
it's
distributed.
People
have
areas,
some
people
are
wide
and
shallow.
Some
people
are
deep
but
narrow.
That's
totally!
A
Okay,
don't
don't
don't
flip
out
because
you
can't
it's
it's
it's
almost
like
UNIX
in
a
way
right
where
everyday,
I'm
learning
a
new
shell
thing,
or
something
like
that.
It's
like
it's
it's
similar
to
that.
So
that's!
That's!
Like
the
one
thing,
I've
noticed
with
people
there,
I
just
don't
get
it
like
it's,
okay,
nobody,
nobody
does
so.
B
D
Yeah
sure
I
actually
did
an
entire
workshop
for
rights,
B
code
about
being
a
new
contributor
and
how
you
can
get
it's
open
source
and
one
of
the
things
that
I
like
to
really
stress
for
people
when
you're
new
is
one
try
to
understand
like
what
your
expectations
are
for.
Why
you're
contributing
in
the
first
place
and
kind
of
stay?
True
that
as
you
move
along.
D
So
if
you're
interested
in
learning
and
try
to
focus
on
that,
don't
get
like
really
hung
up
on,
like
I,
should
keep
skilling
up
and
doing
things
on
the
back
end
or
move
somewhere
else
or
whatever
like.
If
you
have
fun
on
the
CLI
like
keep
hanging
out
there,
that's
still
a
cool
place
to
be,
and
don't
let
like
the
crushing
guilt
of
like
trying
to
keep
up
with
the
firehose
kind
of
give.
D
So
you
don't
have
to
like
jump
in
and
like
do
the
hard
stuff
and
understand
everything
instantly
and
then
the
other
thing
is
remember
that
you're
gonna
be
a
first-time
contributor
for
the
rest
of
your
life
with
open
source.
There's
always
another
project.
Were
you
jumping
on
and
you're
brand
new
in
starting
over
again
and
that's
true
for
everybody?
So
it's
just
kind
of
fun
to
think
about
I've,
no.
C
C
C
E
Okay,
so
I'll
teach
you
things,
but
this
is
for
both
new
contributors
and
current
contributors.
Remember
that
there
are
humans
on
the
other
side
of
the
keyboard,
so
oftentimes
I'm,
not
saying
this
is
users
watching,
but
there
are
people
who
will
like
file
a
bug
and
then
get
really
upset
that
that
bug
isn't
immediately
addressed
or
similarly
as
a
new
contributor,
you
might
bring
that
new
super
valuable
perspective
about
something.
That's
blindingly
obviously
broken
that
everybody
else
seems
to
be
ignoring,
and
you
think
like
look
if
I
is
a
news
person
and
encountering
this
like.
E
E
Milady's
season
contributors
can
kind
of
suffer
the
same
problem
as
well,
so
it
is
like
to
underscore
Carolyn's
point:
it's
a
fantastic
opportunity.
What
seems
blindingly
obvious
to
you?
First,
it
may
be
blindingly
obvious
to
others,
but
it
may
not.
A
lot
of
us
have
trained
ourselves
on
what
to
overlook
when
to
look
past.
E
The
other
implication
of
there
are
humans
on
the
other
side
of
the
keyboard
is
that
it
is
possible
to
go
like
you're,
not
just
talking
to
some
faceless
machine
when
you
open
up
a
full
request
and
it's
it's,
their
life
was
forever
I
can't
underscore
enough
how
vibrant
the
slack
community
is
for
kubernetes.
So
if
you're,
not
a
participant
in
slack
I
highly
recommend
joining
you
know
not.
E
Everybody
has
like
their
github
handle
matching
their
their
slack
username,
but
many
people
do,
and
you
can
also
usually
figure
out
the
special
interest
group-
that's
relevant
to
you,
if
not
just
general
questions
into
the
kubernetes
dev
channel
can
often
point
you
in
the
right
direction
of
which
place
to
go.
Asked
asked
that
question
similarly
to
two
experienced
contributors,
I
think
remembering
that
there
are
humans
on
the
other
side
of
the
keyboard.
E
So,
there's
all
that
the
second
thing
is
I
will
post
this
link
in
slack
I
recently
did
a
table
to
help
explain
the
we
used
to
have
220
github
labels
on
the
kubernetes
kubernetes
repo.
We
now
have
like
170
something.
So
if
you
go
to
that
page
that
I
posted
in
the
meter
contributor
slack
channel,
what
you
will
see
is
this
page
here
which
describes
all
of
the
various
github
labels
that
end
up
landing
on
your
pull
request
and
who
can
apply
them
and
why
they're
there
and
what
part
of
our
automation
is
applying.
E
B
Awesome
suggestions,
I
love
the
one
about
the
pull
request,
descriptions,
that's
a
good
one.
The
next
question
is
about
an
event
that
we
are
running
it
Hume
con
Copenhagen
it's
for
the
contributor
summit,
which
is
all
made
first
George
myself,
Josh
burkas,
when
several
others
are
planning
this
fine
adventure
for
contributors
for
an
all-day
experience.
The
question
is
from
Lee
and
slack
and
she
wants
to
know
what
types
of
things
she
can
expect
and
what
could
she
prepare?
B
If
anything,
we
are
in
the
process
of
planning
as
we
speak,
so
some
of
the
agenda
items
aren't
are
not
done,
but
Gwyn
or
anyone
else.
The
line
that's
been
to
past
contribute.
Your
experience
or
contributor
summits
can
at
least
fill
you
in
on
what
we've
done
before
and
Gwyn
can
also
fill
us
in
on
some
of
the
ideas
that
are
floating
around
for
the
new
contributor
summit.
So
Gwen,
why
don't
you
start
with
some
of
that
stuff?
Oh
yeah,.
C
Actually,
this
will
be
my
first
contributor
summit
so
that
that's
gonna
be
great.
However,
I
think
what
I
would
really
like
to
do
is
to
for
for
there
to
be
a
place
where
people
can
actually
bring
their
computers
and
like
follow
along
like
live
instructions,
for
example,
just
you
know
bring
in
your
machine
and
we'll
walk
you
through
how
to
sign
the
legal
documentation
to
be
a
contributor
will
maybe
do
a
demonstration
pull
request.
I
did
that
at
scale.
C
C
This
is
what
our
standard
github
workflow
is,
whether
you
have
cloned
the
repository
or
you
need
to
just
update
the
repository
that
you've
already
cloned,
because
these
are
these
are
all
things
that
are
sort
of
little
places
and
the
contributor
guide
that
are
available
for
reading.
But
it
might
be
really
nice
to
have
somebody
just
walk
you
through
or
even
just
be
there
for
questions.
So
a
lot
of
it
I
hope
will
be
a
workshop
format
rather
than
just
straight-up
lecture
yeah.
A
It
looks
like
the
schedule
right
now.
It
says
like
sessions
in
session
session,
so
we
noticed
that
this
I
noticed
that
this
morning
that
maybe
we
should
put
a
little
bit
more
detail
in
there.
As
far
as
you
know,
the
first
hour,
I,
don't
know
getting
started,
setting
up
your
laptop
er
or
whatever
right
right.
C
Yeah
we're
currently
brainstorming
and
but
but
those
will
be,
and
then
we
will
have
more
in-depth
topics
such
as
how
does
testing
work
and
how
do
I,
you
know
figure
out
which
repository
to
contribute
to
how
do
I
find
a
cig,
though
both
technical
and
community
oriented,
deep,
dives
I,
don't
want
it
necessarily
well
deep
dive
has
maybe
a
special
meaning,
but
really
just
kind
of
focus
in
a
little
bit
more
on
that
as
well.
Oh.
E
Sorry
I
cannot
about
my
experience
with
previous
summits.
Maybe
you've
addressed
some
of
these
with
this
currents
on
it.
So,
like
I
made
a
mistake,
including
the
previous
summits,
the
same
thing
that
that's
the
place
where
the
community
was
going
to
talk
something
over
and
then
come
to
a
decision
at
the
end
and
like
that,
didn't
really
happen
for
a
lot
of
a
big
ugly
hairball
topics.
E
There
was
a
lot
of
refreshing
or
memories
of
like
why
we
were
addressing
this
problem
in
the
first
place
and
some
of
the
possible
solutions,
but
we
never
really
got
you
got
to
like
a
decision.
The
one
exception
to
that
I
think
was
like
the
signal
interest
group
basically
came
out
of
their
session
around
pod
identity,
with
like
action
items
in
a
roadmap
and
like
they
knew
what
they
had
to
do,
and
they
were
just
gonna
go
execute
on
that.
E
E
D
D
C
D
Pretty
Swank
travel
budgets,
but
the
other
thing
that
I
found
incredibly
helpful
for
jump-starting
me
in
the
sig
was
getting
to
know
these
people
face
to
face.
Even
if
I
had
nothing
interesting
to
say,
as
long
as
they
knew,
I
was
like
a
legitimate
person
and
that,
like
I,
have
no
idea
what
they
thought.
I
was
before,
but
I'm
sure
was
horrible
and
it
just
made
me
feel
like
it
was
a
humanizing
experience
so
that
when
I
did
want
to
get
say
a
feature
and/or
asked
for
help.
D
C
C
C
Just
he's
just
spent
his
afternoon
going
over,
like
his
special
get
patch
tricks
with
me
on
how
to
make
my
pull
requests
more
readable
and
more
more
structured,
more
logically
structured
after
it
kind
of
made
a
big
hash
out
of
them,
and
he
just
you
know
he
doesn't
he's
not.
He
doesn't
work
at
Samsung
he's
just
like
some
person
from
the
kubernetes
community
and
he's
just.
C
He
just
took
it
on
himself
to
just
show
me
some
ropes
just
on
the
on
one
topic
and
I,
just
I
just
think
the
opportunities
for
that
sort
of
thing
are
really
amazing
and
I.
Just
I'm
I'm,
really
cognizant
of
looking
for
opportunities
to
pass
it
on
down
to
the
next
step.
On
the
ladder
just
like
Aaron
said
earlier,
yeah.
A
A
Never
thought
of
that.
You
know,
because
in
the
community
repo
yeah,
okay,
we're
editing
a
lot
of
markdown,
we
kind
of
use
it
like
it
really
slow,
Google,
Docs
right
but
like
he
was
like
teaching
me
to
like
get
into
the
good
habit
right
like
I,
would
do
git
commit
a
at
all
the
time
he
was
like.
No,
never
just
assume
you
want
to
commit
everything.
How
are
you
going
to
stash
stuff
and
and
do
this
kind
of
stuff
and
I
was
like?
Oh
it?
It
wasn't
obvious
to
me.
A
A
C
B
Just
want
to
add
something
to
that
when
you
said
that
you
were
looking
to
get
back
you're,
actually
giving
back
right
now,
so
definitely
I
reanalyze
the
term
mentor,
because
it
doesn't
necessarily
mean
you
know
this
is
you
know
one
one-on-one
pairing
we're
all
here
answering
questions
for
upstream
contributors,
so
you
are
definitely
giving
back
and
thanks
for
that
all
right.
Next
question:
I
have
a
feeling.
Erin
and
I
will
be
answering
most
of
this,
but
the
individual
would
like
to
know
what
the
process
of
proposing
a
new
working
group
is
Erin.
E
E
I
believe
that
the
community
as
a
whole
is
getting
to
a
point
where
they
are
suffering
from
life,
so
your
working
group
or
meeting
Fernau
and
we
are
kind
of
collectively
revisiting
or
trying
to
understand
what
the
definitions
of
these
things
are
and
why
they
are
necessary.
So
I
will
share
my
screen
just
so.
We
have
something
to
look
at
while
I'm
talking
about
this
stuff.
I've
shared
these
links
in
the
meetup
channel
or
in
the
meaner
contributors
channel
as
well.
I,
don't
know
why
that
thing
is
there
minimize
it?
E
So
here's
like
a
governance,
talk
that
I
would
probably
point
you
to
today.
That's
not
under
a
full
request
and
it
just
sort
of
talks
about
the
different
kinds
of
groups
that
there
are
within
the
community.
There's
special
interest
groups,
sub
projects,
working
groups
and
committees,
special
interest
groups-
are
things
they're
supposed
to
have
sort
of
a
formalized
structure.
E
We
spend
a
lot
of
time
figuring
out
like
what
is
a
lead
meet
or
what's
a
chair
mean
or
technically
it's
a
group
of
people
who
collectively
are
interested
in
some
facet
of
kubernetes
and
then
both
vertical,
horizontal
or
stuff.
That
has
to
do
with
getting
the
project
out
the
door
and
it's
you
know
this
long-lived
thing
that
has
a
lot
of
formal
structure
in
there.
Working
hurts
were
intended
to
be
a
way
to
allow
people
to
have
ongoing
sort
of
formal
ish
discussions,
but
that
didn't
necessarily
need
all
of
this
governance
stuff
around
them.
E
E
If
you
just
want
a
group
of
people
to
get
together
and
collaborate
on
something
working,
groups
are
kind
of
for
the
level
of
formalism.
I
think
where,
if
you
want
like
ongoing
discussion
over
continuing
you
after
it's,
that
sort
of
thing,
I'm
gesturing
illogically
hand,
so
I'm
actually
get
a
stop.
Sharing
we're
skating
for
a
second.
The
the
one
of
the
things
to
keep
in
mind
is
that
working
groups
are
not
expected
to
actually
own
code.
E
It's
just
supposed
to
be
mostly
for
the
collaboration
and
communication
and
discussion
aspects,
not
for
the
like
shepherding
with
code
code,
ultimately
is
supposed
to
live
with
SIG's,
and
so
that
brings
me
to
this
other
thing:
the
the
sub
project,
which
that's
basically
like
a
subset
of
people
who
are
all
interested
in
one
specific
effort
or
project.
It
usually
corresponds
to
a
single
repository,
so
like
helm,
for
example,
would
be
a
subcontract.
E
Some
projects
are
owned
by
SIG's,
that's
mostly
because
there
are
hundreds
of
sub
projects,
and
you
need
some
method
of
hierarchy
to
make
them
a
little
more
easily
discoverable.
But
some
projects
can
also
span
multiple
directories,
so
another
example
would
be
like
the
workloads
API
lives
in
a
number
of
different
package
and
utils
directories
and
API
directories
and
the
kubernetes
repo.
But
it's
all
one
thing
which
it
moved
in
lump
sum
to
from
beta
to
stable
in
communities
for
not
last
year
right.
E
So
if
you're
interested
in
just
like
one
specific
project,
maybe
you're
thinking
about
a
sub-project
here,
then
maybe
you're,
trying
to
figure
out
like
what's
the
appropriate
sync
to
to
home
that.
Finally,
the
last
thing:
well,
the
reason
I'm
talking
about
this
at
length
and
the
reason
I'm
mentioning
the
community
is
kind
of
coming
to
some
sort
of
figuring
out.
What's
going
on
is
we
recently
had
two
folks
proposed
working
groups?
E
One
around
one
was
a
working
group
idea
around
developer
tools
which,
like
turned
into
a
thread
this
long,
that
managed
to
even
trip
like
spam
detection
and
make
people
get
really
like
some
people
thought
that
somebody
personally
was
going
through
and
deleting
messages,
and
it's
just
like
it's
one
of
the
highest
traffic
trends.
We've
had
because
we're
just
trying
to
figure
out
as
a
community
does
it
make
sense
to
have
another
one
of
these?
E
Where
should
we
put
it
so,
if
you're
interested
in
going
through
that
level
of
doing
like
now,
the
informal
process
is
to
kind
of
ask
the
community
what
they
think
about
the
scope
of
your
work.
So
you
sort
of
say:
hey
here's,
the
working
group
I'm
proposing
I'm,
suggesting
we
talk
about
these
things,
I'm,
suggesting,
though
here
are
some
projects
that
sort
of
interest
us
and
try
and
hash
out
with
the
community
what
the
scope
of
this
is
and
whether
it
makes
sense
to
yes.
A
B
Try
to
find
a
cig
that
will
sponsor
you
first
and
work
with
them
on
whether
or
not
it's
a
sub
project
or
working
group
after
that
proposed
the
working
group
to
kubernetes
dev
Google
Groups
calm
for
wait
for
some
kind
of
plus
one
week
for
other
states
to
chime.
In
that
say
they
might
be
interested
and
then
once
it's
a
go
and
there's
no
major
exceptions.
Five,
if
you'll
create
your
working
group,
that's
very
similar
to
the
sake
structure,
so
that
you
have
things
like
zoom
and
Google,
Groups
and
slack
slot
channels
etc.
C
A
C
A
For
dinner
tonight,
no,
but
I
also
wanted
to
add
that,
like
the
temptation
to
add
things
like
since
in
working
group,
sound
great
and
they're
relatively
easy
to
make,
but
there's
also
overhead
there,
so
every
Sigma
crate,
that's
one
more
signal
has
to
do
a
status
update
during
the
community
meeting.
That's
one
more
playlist!
We
have
to
manage
on
YouTube,
you
know
like
there's
it
just
kind
of
keeps
adding
up
and
of
course
you
know
we
want
to
enable
people
to
do
a
lot
of
things
right.
But
at
some
point
it's
like
you
know.
A
If
it's
a
Thursday
afternoon,
you
want
to
hang
out
with
four
or
five
people,
send
an
email
and
just
do
it
yeah,
you
know
and
then
maybe
maybe
consider
structures
more
formal
structures
later
on
when
you're
like
okay,
we
should
actually
start
like
writing
stuff
down,
and
you
know
things
like
that.
Yes,.
E
So
they
weren't
aware
that
there
was
like
ongoing
discussion
of
where
mini
cave
is
headed
things
like
that
so
and
I'll
also
just
volunteer
myself
as
somebody
to
pinging
offline,
if
you're
trying
to
figure
out
what
you're
trying
to
do
and
where
you
think
you
should
go
totally
happy
to
have
that
discussion,
but
everything
out
like
I
could
not
agree
more
on
the
storages
point
other
than
like
it.
Discoverability
is
helpful.
Also,
like
you
know,
bragging
about
it
on
slack
or
bragging
about
it
and
your
cigs
mailing
list,
or
something
like
that
is
usually
cool.
E
A
Because
it
would
be
a
shame
if
there
there's
a
group
out
there
and
having
a
bunch
of
meetings
and
they're,
not
recording
them
and
putting
on
the
channel
and
then
it's
like.
Oh
it
was
anyone
taking
notes
and
while
it's
great
to
just
talk,
sometimes
you
know,
we
also
have
to
think
about
efficiency
and
and
how
we.
B
B
A
B
E
E
Keep
having
the
discussion
on
mailing
list
I
think
because
I
think
his
point
is
also
that
it
could
maybe
span
say
close
to
life
cycle
which
could
be
interested
in
managing
other
nodes,
so,
like
I'm,
seeing
a
lot
of
plus
ones.
My
god
is
telling
me
it's
because
IOT
is
like
a
really
hot
phrase,
and
so
maybe
a
working
group
could
make
sense
but
kind
of
keep
having
a
discussion.
I
think
try
and
continue
to
try
and
engage
the
steering
committee.
E
The
the
PR
that
I
went
sort
of
trying
to
clarify
these
things
definitely
appreciate
your
input.
There
I'm
like
what
would
clarify
this
process
for
you
and
again,
but
underscore
George's
point
like
think
about
what
this
is
why
you
want
to
form
this
working
group?
What
are
you
trying
to
accomplish
with
it,
but
I'll
try
and
see
if
I
can
have
my
two
cents
to
the
thread
player.
C
One
of
the
thing
that
helps
me
sort
of
stay
organized
that
I
really
like
is
the
concept
of
an
area
within
you
know
within
a
repository,
and
that
is
it
kind
of
a
little
bit
of
a
smaller
unit
of
code
or
documentation
or
interest
that
is
much
easier
to
assign
to
whichever
sake
it
is
and
and
it
can
correspond
with
owner's
files
and
Bach
commands
and
all
that
good
stuff.
So
it's
already
kind
of
integrated
but
I,
really
like
it,
because
it
sort
of
trickles
down.
Logically,
you
go
to
the
repository.
C
You
find
the
areas
and
then
it's
fairly
easy
to
communicate
with
the
few
people
who
are
going
to
be
your
main
points
of
contact.
It's
a
little
I'm
sure
it's
it's
it's
it's!
It's
not
really
the
same
thing
as
a
working
group
at
all,
but
but
personally,
I,
really
like
it
as
an
organism
or
II
'el
tool
to
keep
things
like
in
a
logical
flow
of
like
dependency
and
and
collaboration.
C
C
B
B
D
New
contributors,
so
please
please,
please,
if
you
hop
on
a
cig,
Service
Catalog
and
just
ask
their
or
DM
me
directly.
If
I'm
distracted,
I've
been
curating
like
or
a
dozen
different
Help
Wanted
good
first
PRS,
that
are
really
awesome.
If,
especially,
if
you're
new
to
kubernetes
as
well,
sometimes
it
can
be
a
little
overwhelming
to
get
a
full
environment
set
up
and
everything
like
that
and
a
lot
of
the
issues
that
I
have
are
a
little
bit
smaller
in
scope.
And
you
don't
need
to
understand
like
how
come.
D
And
we
have
little
tiny
things
really
doc.
We
have
stuff
on
the
the
CLI
side
or
smaller
things
on
the
API
side.
That
I
would
love
to
help
someone
get
up
and
running
with
and
I'm,
not
like
Yoda
I.
Don't
have
all
the
answers,
but
I
know
lots
of
people
who
help
me
and
then
I
can
maybe
for
you
along
to
someone
else.
But
yes,
we
love
having
new
people
work
with
us
great.
A
B
E
Have
served
on
the
release
team
in
a
variety
of
roles.
First,
you
are
welcome
to
come
and
participate
during
regular
release
meetings,
even
if
you're,
not
a
number
of
the
midis
team,
just
to
get
a
sense
of
how
we
as
a
community
work,
it's
one
of
the
highest
areas
of
collaboration
that
I've
seen
in
the
project
I've
served
on
it,
as
somebody
who
has
written
release,
notes
unist
on
the
issue
triage
who
has
done
CI
signal
reporting
and
just
generally
helped
to
Shepherd
things
along.
E
We
definitely
recognize
people
who
notice
when
things
are
kind
of
finding
ways
you
can
contribute,
are
just
kind
of
like
keeping
track
of
what
are
all
these
issues
and
PRS
and
as
everything
in
flight
the
way
it's
supposed
to
be,
but
you
don't
really
have
to
be
an
organization
member
or
have
any
crazy
superpowers
to
do.
It
is
a
good
opportunity
to
work
what
what
you
can
do
with
increased
privileges
and
whatnot,
and
it's
a
fantastic
way
to
contribute
to
to
the
project
without
necessarily
having
to
write
any
code.
E
It's
there's
seriously
so
much
stuff
going
on
that.
It's
it's
a
lot
to
keep
track
of,
so
any
and
all
health
is
really
greatly
appreciated.
We're
almost
constantly
saved
by
people
who
pitch
in
and
help
out,
even
though
they're,
not
formally
staff
members
or
on
the
release
team
or
whatever,
and
it's
it's
just
all
the
emojis
in
the
release
channel.
Just
so
many
and.
A
I
I,
what
I
have
for
the
people
on
the
stream
that
I
josh
says
the
six
scalability
is
always
looking
for
performance
geeks
and
as
the
111
release
lead.
Yes,
he's
looking
for
three
more
shadows,
so
consider
that
your
call
for
yes,
you
should
mention
that
at
the
community
meeting
tomorrow,
you
know
if
you're
listening
still,
oh
and.
E
One
up
there
nope
another
brag
to
the
release
team.
You
usually
get
some
kind
of
swag
out
of
it.
If
you
buy
that
sort
of
thing.
Wait.
Never
that's
that's
developer
summit!
Oh
yeah!
There
we
go,
you
can
get
that
sort
of
stuff
and
I
believe
the
one
time
release
team
may
be
getting
left
shark
t-shirts
so
yeah.
What
is
what's.
E
C
Think
I
think
in
one
of
my
talks,
I
made
I
made
an
entire
slide
out
of
the
fact
that
on
github,
pull,
requests,
hearts
and
smiles
and
thumbs
up
abound,
which
I
just
I
didn't
even
know.
That
was
a
thing
before
hims
just
but
people
are
just
like
yay,
sorry
and
it
just
it
just
makes
me
feel
a
little
bit
more
at
ease
and
to
get
warm
and
fuzzies
right
cuz.
C
D
B
And
we
definitely
appreciate
all
contributors
here
so
clap
for
everybody
next
question:
alright,
so
a
couple
folks
have
asked
about
communication
and
what
s
LasR
on
on
PRS
when
submitting
things
so
sounds
like
they're
having
an
issue
with
just
folks
looking
at
their
pull
requests.
What
are
some
tips
that
you
can
give
to
these
folks
to
get
responses
either
faster
or
better
responses?
E
Okay,
so
github
notifications
are
effectively
broken
like
if
you
act,
somebody's
name,
it
might
go
into
a
get
a
notification
inbox
that
has
a
thousand
number
of
notifications,
so
some
people
use
a
lot
of
like
filters
in
their
email,
and
so,
if
you
use
that
it
might
work,
I
personally
use
github
issue,
query
that
looks
for
like
issues
that
I've
commented
on
or
issues
that
are
assigned
to
me.
So
what
I'm
trying
to
say
is
with
pull
requests
like
requests
to
review
from
somebody.
E
E
E
You
so
if
I
go
to
goober
Nader,
so
when
I
go
to
PR
dashboard
here,
this
is
something
that
shows
all
the
pull
requests
that
supposedly
need.
My
attention
are
in
coming
at
me
or
pull
requests
that
I
have
pop
going
and
what
the
status
of
those
is
we're
working
on.
Improving
that
for
sure,
so
that's
by
hey,
I
am
beat
earlier.
I
said
like
there
are
humans
behind
the
keyboard,
humans
are
might
might
be
more
accessible
on
slack,
one
might
be
more
accessible
via
email.
If
you
can
reach
out
to
me
directly.
E
I
have
also
shared
this
advice
on
this
meeting
before
like
please
don't
go
stock
people,
please,
don't
immediately
like
open
a
poll
request
and
go
after
them
or
ping
them
repeatedly.
People
have
lives
like
we
don't
really
have
a
great,
publicly
accessible
way
for
somebody
to
denote
that
they're
on
vacation
or
that
maybe
they
have
left
the
project,
and
so
it's
possible
that
you're
you're,
like
barking
up
the
wrong
tree.
E
When
you
try
and
go,
you
know
why
isn't
this
person
responding
through
my
Polo
class,
so
another
thing
that
I've
advocated
doing
before
is
generally
speaking.
If
you're
spending
a
pull
request
to
kubernetes
kubernetes,
this
is
usually
the
place
where
only
quests
kind
of
hang
out
the
longest.
There's
a
bot
that
comments
about
needing
approval
from
people
and
it
links
these
owners
files.
So
that's
where
it
gets
the
list
of
people
that
need
to
there's
a
long
winded
thing.
E
I
can
I
can
link,
but
basically
like
want
to
make
sure
that
people
who
have
ownership
of
the
various
files
that
your
pull
request
touches,
have
taken
a
look
at
it
and
made
sure
that
it's
doing
the
right
thing.
That's
usually
the
longest
hold
up,
and
so
the
bots
will
suggest
one
person
from
those
owners
files
again
like
I
said
there
could
be
a
reason
that
the
person's
just
not
responding
they're,
not
around
whatever.
There
are
other
people
in
those
files
that
you
can
reach
out
to.
E
We
can
do
the
same
thing
so
like
I
said,
above
all,
try
to
remember
there
humans.
On
the
other
side,
we
can't
get
swamped
and
overload
and
yeah
I
recognize
it's
not
ideal.
We
even
have
a
dashboard
on
the
thing
called
dev
stats.
That's
trying
to
to
show
what
our
cycle
time
is
for
Paul
requests
and
we're
trying
to
drive
that
down,
but
we're
really
not
at
that
SLA
point.
I
know.
E
One
of
the
improvements
we've
made
is
like
the
time
from
somebody
opening
up
the
cola
quest
to
the
first
time
an
actual
human
being
has
commented
on
it.
It
was
not
full
request.
Author
has
gone
down
over
time,
so
if
you're
used
to
dealing
on
pull
requests
and
having
them
like
responded
to
and
merged
on
the
order
of
hours,
try
and
think
more
on
the
order
of
like
dates,
at
least
if
weeks,
it's
a
large
pull
request
like
if
it's
a
large
pull
request,
that's
changing
a
ton
of
files
and
adding
a
ton
of
functionality.
E
E
So
Tim
Hakan
is
one
of
the
unfortunate
people
whose
name
is
in
the
root
owners
file.
So
if
there
are
files
like
further
down
the
tree
that
don't
have
have
somebody
who
can
own
just
that
file
it'll
fall
back
until
it
reaches
the
root
of
the
repo,
and
so,
if
folks,
like
Tim,
Hawking
kind
of
have
a
lot
of
pull
requests
to
look
at.
So
that's
why
I
like
try
to
find
people
who
don't
have
this
much
on
their
plate
and
then.
C
Yeah,
so
another
really
great
way
to
not
stock
some
individual,
but
still
get
attention
is
to
just
sort
of
you
know,
make
a
general
question
in
slack
and
if
you
know
the
related
slack
channel
for
that
group
or
cig
or
whatever
it
is
just
kind
of
say,
hey
I've
had
this
pull
request.
Can
someone
would
someone
mind
taking
a
look
at
it?
That's
a
way
to
reach
more
a
general
group
of
people
without
any
having
to
be
there
and
getting
pained
and
just
monopolizing
their
time.
C
C
Why
is
my
pull
request,
not
getting
reviewed,
and
there
are
a
lot
of
suggestions
right
there
and
as
as
always,
remember,
there's
humans.
On
the
other
end,
people
I
use
common
sense,
I
mean
do
duping
someone
with
a
you
know.
Please
take
another
look
if
the
situation
warrants
but
keep
in
mind.
Also
on
Aaron
said
it's
gonna
be
on
a
range
of
days
before
you
know
you
can't
repeatedly
pink
someone
within
an
hour.
That's
just
not
not
happening
so
there's
there's
actually
quite
a
lot
of
resources
in
this
document.
D
So
what
I
do
is
in
the
repository
and
github
I
go
to
the
top
and
I
type
commenter
:,
and
then
my
username.
It
helps
me
see
everything
that
I've
commented
on
and
that's
extremely
helpful,
especially
when
you're,
not
a
member,
yet
so
that
you
can
find
where
you've
been
participating
and
sort
that
by
like
activity
and
kind
of
use,
that
to
kind
of
stay
in
touch
with
like
where
you've
been
kind
of
playing
around
and
then
otherwise
I
would
say
please
to
get
personal
when
someone
doesn't
get
back
to
you
quickly.
D
It's
never
like
some
implement
implicit
judgment
of
your
Polar
quest
or
anything
like
that.
It's
just
quite
literally
a
lot
of
people
involved.
Even
when
it's
their
job,
it
may
not
be
like
their
top
priority
that,
like
their
boss,
is
like
hounding
them
every
day.
So
sometimes
it'll
take
a
couple
days
before
they
can
resurface
and
and
and
look
at
PRS
I
knew
I.
Do
that,
like
every
couple
days
like
I
really
day,
I'll
come
in
and
dive
in
and
do
a
bunch
of
PRS.
So
if
it
takes
a
while,
it's
not
you
that's.
E
There
we
go
so
this
is
something
called
proud,
proud
us
a
lot
of
our
automation
when
you
type
slash
transition
of
the
thing
in
response.
We
recently
had
somebody
put
together
a
page
that
shows
like
you're
all
requests
and
why
your
pull
request
is
emerging
yet
so,
in
this
case,
I
have
a
pull,
request,
open
and
it
says:
there's
a
label
that
needs
to
be
added.
What
is
the
label
that
needs
to
be
added,
LP
p.m.
E
so
I
know:
I
need
to
go,
get
somebody
to
help
you
TM
in
this
case,
this
other
pull
request
is
emerging
because
it
has
two
forbidden.
Labels
needs
release
and
do
not
merge
hold,
and
it's
also
missing
somebody
to
lgq
we're
working
on
improving
like
what
the
helped
here
says,
like
we'd
like
to
get
to
the
point
where
you
can
look
at
this
label
and
understand
what
you
have
to
do
to
get
rid
of
it.
E
So
if
you
use
your
github
token
to
start
query
and
github
API
and
then
they'll
show
you
before
your
PRS,
you
know
what
do
you
have
to
do
like
all
the
tests
are
passing
and
great
that
sort
of
stuff
so
we'll
be
working
on
improving
this
I'll
probably
have
a
lot
more
to
say
about
this
at
coop
Conniff,
kubernetes
community
meetings.
Before
that.
B
Typically,
we
have
these
on
the
first
Wednesday
of
every
month,
and
the
first
Wednesday
of
every
month
next
month
falls
on
cue
cons,
so
in
the
midst
of
trying
to
figure
that
out
as
we
speak,
but
first
of
all,
thanks
to
everybody
that
asked
questions
today,
my
advice
is:
keep
asking
questions.
That's
the
best
thing.
Second,
thanks
is
to
all
the
contributors
that
joined
us
today.
You
are
all
awesome
mentors
and
should
be
should
be
thanked.
Thank
you
to
Aaron.
Thank
you
to
Carolyn.
Thank
you
to
Gwyn
thanks
to
George.
B
A
G
A
B
I'd
love
to
have
all
of
you
back
at
some
point
to
I
said:
oh,
hopefully,
you
can
join
us.
Aaron
is
a
semi-regular,
since
a
lot
of
a
lot
of
his
area
touches
the
tooling
for
upstream
contributors
and
tooling
needs
to
be
a
hot
topic.
We
do
have
some
of
the
awesomest
tooling,
though,
in
the
open
source
field,
so
I
am
biased,
but.