►
From YouTube: Kubernetes Meet Our Contributors 20191002
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 out this page for more information: https://github.com/kubernetes/community/blob/master/mentoring/meet-our-contributors.md
A
Hello,
welcome
to
October's
edition
of
kubernetes
meet
our
contributors.
I
am
joined
here
today
with
an
awesome
esteemed
panel
of
upstream
kubernetes
contributors,
there's
30
over
35,000
of
you
y'all.
We
have
a
mini-city
at
this
point.
I
am
NOT
the
mayor,
unfortunately,
but
my
name
is
Paris
I
do
work
at
Google
I'm
an
upstream
contributor
as
well.
Today
we
are
here
to
answer
all
kinds
of
questions
related
to
things
like
governance.
Why
is
your
test
flaking?
Why
aren't
you
getting
an
answer?
How
do
you
get
an
answer?
How
we
decide
on
things?
A
Everything
is
fair
game
here.
Who
mutters
is
what
is
mutters
everything
in
between
any
kind
of
jargon,
questions
we
get
that
a
lot.
What's
the
LG
TM,
what's
an
SDTM
that
we
could
go
on
and
on
and
on
first
things.
First,
we
do
have
a
code
of
conduct
what
that
means,
as
we
try
to
be
excellent
to
each
other,
that's
all
of
our
mentors
on
this
panel.
That's
you
asking
and
answering
questions
that
are
in
both
our
slack,
twitter,
etc.
So
just
be
awesome
to
each
other.
A
We
have
a
great
community
that
is
supportive
and
we're
here
to
help.
So
where
do
you
ask
questions,
you
say
mainly
and
me
meet
our
contributors
slack
channel?
If
you
need
a
slack,
invite
if
you're
joining
us
from
Twitter
or
somewhere
else
right
now,
that's
slack
k8s
I/o
for
an
invite
and
again
meet
our
contributors
is
the
room
that
we're
in
so
say
hello
to
us.
A
You
can
also
DM
me
privately
on
slack.
That's
where
the
large
majority
of
the
questions
do
come
from
people
might
be
embarrassed
to
ask
what
a
cig
is
again
or
ask
some
of
that
jargon,
and
that's
totally
cool
with
us
and
we're
here
for
that
or
tweets
Twitter,
whatever
I'll
get
to
it.
I'll
find
your
question.
Ask
one
of
the
folks
that
you
know
when
the
panel
will
get
it
and
we'll
answer
it.
A
We
only
do
have
50
minutes,
though
we
usually
go
right
up
to
that
50
minute
mark
and
we
can
maybe
do
interactive
things
with
you,
depending
on,
depending
on
the
panelists.
So
if
you
want
to
do
a
certain
code
base,
walk
through
ask
us
if
we
can
fulfill
that,
we
can
do
it
and
if
not,
then
we
can
get
you
someone
that
can
some
quick
announcements
and
then
I'm
gonna
stop
talking
and
then
other
people
will
start
talking,
which
is
even
better.
First,
we
have
a
contributor
summit
coming
up.
A
It's
in
November,
17th
and
18th
at
cube.
Con
I
hear
quite
a
few
of
you
are
going
at
least
I.
Think
it's
over
10,000
of
you
at
this
point
or
something
and
please
join
us,
the
pre
celebration
of
cube
con.
If
you
will
for
our
stream
contributors,
there
is
I
believe
only
a
hundred
tickets
left,
the
new
contributor
workshops
already
sold
out
so
consider
this
your
warning
and
not
necessarily
an
announcement.
A
You
can
find
that
on
the
cube
con
website
with
the
instructions
on
how
to
register
all
right
and
then
last
but
not
least,
we
do
what
have
outreach
e
applications
out?
What
this
means
is.
We
have
three
internships
available
that
are
paid
for
upstream
work.
What
amazing
we
can
talk
about
those
in
a
second
and
I'm
sure
we're
gonna
have
some
questions
from
outreach
e
interested
applicants
there
and
we
also
Nikita
on
the
line
who's
very
familiar
with
the
program.
A
B
A
C
D
My
nickname
is
Dimps,
I
have
a
longer
name
if
you
want
to
find
out
so
I
am
active
in
cig
architecture
and
some
of
the
cross-cutting
SIG's
like
cig
testing,
and
things
like
that,
I'm
very
interested
in
trying
to
get
new
people
into
the
community,
because
I
was
one
once
a
little
while
ago,
and
people
were
very
welcoming
to
me
so
hit
me
up
with
anything
that
you
need
to
get.
You
started
anything
else.
That's
it!
That's.
A
E
Have
a
longer
name,
it's
actually
cured
and
I'm
active
in
the
contributor
community,
usually
I'm.
Also
doing
a
presentation
at
the
contributor
summit
and
I
do
a
lot
of
work
with
at
Keuka
at
the
diversity
luncheons
and
things
like
that.
Oh
I,.
E
Fortunately,
I
have
that
open,
so
I
can
give
the
title
of
my
talk.
Okay,
it's
breaking
down
barriers
to
community's
contribution
for
neurodiverse
community
members,
and
that
is
a
50
minute
talk
starting
at
10:30
on
the
18th.
If
you
would
like
to
join
please
come
see
me
I
will
be
very
happy
to
see
you
awesome.
A
G
Totally
my
fault
I'm,
mostly
just
I
hanging
out
around
here
and
helping
to
stream
I,
do
have
a
talk
with
Don
Foster,
though
at
cube
con
called
the
week
in
the
life
of
the
kubernetes
community,
which
will
cover
a
lot
of
this
stuff
so
year.
If
you're
interested
in
diving
in
it's
kind
of
a
beginner
beginner
talk
of
all
the
places
that
you
can
plug
yourself
in
and
I
will
leave
a
URL
for
that
in
the
chat.
A
All
right:
well,
that
is
our
panelists
again
I'm
Parris.
It's
so
awesome
having
everyone
here
with
us
today.
Our
first
question
does
come
in
from
my
direct
messages
and
slack.
It
sounds
like
it
might
be,
a
potential
outreach
e
intern
and
they
would
like
to
know,
of
course,
the
infamous
cig
jargon.
What's
a
sake,
I
see
it
everywhere
and
they
don't
under
so
I
guess
in
the
same
in
the
same
breath,
how
is
the
community
structured
so
we'll
start
there
damaged?
You
should
take
this
one.
Oh
sure,.
D
So
the
way
we
are
structured
as
Cuba
notice,
the
entire
kubernetes
project
is
under
CN
CF
CN
CF
is
a
foundation
and
the
Cuban
artists
over
all
the
folks
in
charge
are
the
steering
committee
and
the
steering
committee
essentially
talks
to
CNCs
that's
right
at
the
top.
But
then
the
steering
committee
doesn't
do
any
work
as
such,
it
delegates
most
of
its
authority
to
what
we
call
special
interest
groups.
So
special
interest
groups
like
there
are
there's
one
for
signal,
sick
testing.
You
know
you
name
it.
D
We
have
a
sig
for
it,
and
special
interest
groups
themselves
are
responsible
for
code.
They
are
responsible
for
coming
up
with
ideas
for
new
features
and
go
and
implement
them.
You
know,
add
test
cases,
everything
happen.
Everything
happens
in
a
sig.
So
if
you
are
interested
in
like
how
how
we
interact
with
docker
or
continuity
go
to
signal,
if
we
want
to
know
how
we
do
into
n
testing
what
CI
jobs
are
there
and
things
like
that
go
to
seek
testing.
D
If
you
are
interested
in
the
release,
artifacts
then
go
to
cig
release,
so
that's
the
hierarchy
and
under
six
they
break
up
into
sub
projects,
for
example
in
cig
architecture.
We
have
multiple
sub
projects,
one
for
conformance
testing
and
you
know
we
break
down
different
areas
like
one
for
you
know,
so
we
have
like
four
or
five
I
I,
don't
recall
exactly
all
of
them
at
this
time,
but
that's
the
whole
overall
structure.
We
have
the
steering
committee,
the
special
interest
groups
and
sub
projects
and
then
aleeah's.
D
D
That's
related
to
the
sig.
If
you
join
the
queue
bonitas
dev
mailing
list,
you
automatically
get,
you
know
added
to
a
bunch
of
things
as
well.
You
will
get
Canton
calendar
invites
you
will
get
access
to
the
documents
as
well.
So
that's
the
kind
of
structure.
So
if
you
want
to
come,
say
hi,
there
will
be
these
meetings
for
each
of
the
six
that
we
have
published
calendars
for
as
well.
So
you
know
don't
be
shy.
There's
only
one
way
to
do
this,
which
is
to
show
up-
and
you
know,
ask
questions.
A
A
They
said
that
they
are
showing
up,
but
it
seems
like,
since
they
don't
work
on
it,
full-time
that
it's
hard
to
pick
up
projects
that
matter.
So
what
is
your
advice
for
those
folks
on
I?
Guess
just
now
they
are
showing
up
and
how
do
they
get
ramped
that?
How
do
they
get
like
quickly,
ramped
up
and
on
something
that
matters
I.
C
Yeah
I
mean
I,
think
it's
it's
a
difficult
one
like
I
myself,
I'm
not
paid
to
work
on
upstream
kubernetes
features,
so
I've
definitely
felt
that
before,
where
you
see
a
lot
of
big
things
going
on
and
you
you
know,
you
kind
of
want
to
be
doing
something
similar
to
that
too.
I
guess
I've,
just
kind
of
managed
to
well
what
I
try
and
focus
on
things
that
at
least
I
can
justify
as
part
of
why,
otherwise
do
so,
I
didn't
get
to
introduce
myself,
but
I
run
the
SERP
manager.
A
H
C
No
I
I'm
from
the
UK
and
I
run
a
project
called
SAP
manager,
which
is
a
certificate
management
tool
for
kube
Nettie's.
You
may
have
heard
of
I've
used
Cubist's
quite
a
while
now
and
work
a
lot
where
I
work
as
much
as
I
can
in
sig
API
machinery
and
a
bit
in
cig
testing
and
also
help
out
on
the
kind
as
well
keep
Nettie's
and
docker
and
a
qubit
he
sinks
along
with
Ben
and
many
other
people.
C
it's
quite
a
few
of
us
working
on
that
yeah
I
mean
going
back
to
what
we
were
saying,
though,
and
how
to
kind
of
spend
time
with
in
SIG's,
whilst
you're
not
necessarily
paid
to
work
on
that
full
time.
So
it's
difficult
to
get
the
time
like
I,
say:
I,
try
and
find
requirements
like
I've
got
that
allows
me
to
justify
upstream
and
just
sort
of
pick
up
those
smaller
bits.
C
They
aren't
necessarily
huge
I
haven't
had
to
go
through
the
process
of
writing
a
cap
from
scratch,
myself,
yeah
I've
kind
of
looked
at
ones
that
I'm
interested
in
and
tried
to
provide
feedback,
but
yeah.
It's
kind
of
just
picking
up
those
smaller
bits
and
I
think
over
time.
You
find
yourself
becoming
more
and
more
familiar
with
the
areas
in
which
you
have
worked
and
doing
more
and
more
work
there
until
you
actually
find
yourself
in
a
position
where
you
are
able
to
then
review
other
people's
code
and
be
a
more
active
part
of
that.
E
Yeah
for
me,
I
don't
need
to
do
this
either
and
I
actually
started
out
with
writing
content.
I,
don't
I,
don't
program
at
all,
so
I
actually
just
work
on
communication.
Some.
E
Either
one
of
those
I
think
was
Barcelona
at
the
Barcelona
diversity
launch
it
cook
on
a
blog
post
about
that
and
then
and
also
I'm,
doing
some
work
on
the
contributors
site
content.
So
that's
that
and
for
me,
I
I
got
started
with
content,
because
that's
what
I
know
how
to
do
and
I
figure
I
can
write
a
blog
post.
I
can
and
I
did
a
couple,
tiny
changes.
You
know
just
grammatically
or
what
not
to
some
open
issues
that
had
good
first
issue
label.
E
So
that's
where
I
started
to
was
just
making
minor
grammatical
changes
that
I
knew
I
could
do,
and
those
are
just
little
things.
But
then
it
ramped
up
to
you
know
writing
a
blog
post
or
something
you
doesn't
always
have
to
be
code.
You
can
start
by
writing
content
and
improving
Docs.
You
can
get
involved
by
improving
Doc's,
even
just
in
the
community
in
general,
just
starting
there.
Just
writing
content
is
a
good
place
to
start
to.
You
doesn't
always
have
to
be
code.
Yeah.
A
H
A
About
it,
so
the
infamous
time
management
is
people
always
see.
Kubernetes
is
this
gigantic
landscape,
especially
when
you
look
at
the
cig
list
again
saying
being
special
interest
groups,
the
projects
/
like
30-plus
of
them?
How
do
how
do
we
do
it,
especially
again
if
you're
not
full-time,
even
full-time
people
on
the
project
are
like
in
either
maybe
a
silo
for
a
reason
or
whatever.
A
D
B
B
These
are
just
like
really
small
things,
but
if
there's
pressure
that
I'm
interested
in
or
project
that
I'm
contributing
to
I
will
sort
of
add
those
words
to
as
they
turn
for
anything
keywords
and
slack,
so
that
like
if
someone
mentions
it
in
a
chat,
you'll
get
a
notification
for
it.
Sometimes
I
don't
go
through
if
all
the
shots,
but
I
will
still
get
pinged.
If
someone
is
talking
about
something
that
I'm
interested
in
yeah,
that's
me.
That's
proved
to
be
also
helpful
if
it
can
also
add
to
a
lot
of
noise.
So
it's
it.
B
D
Can
always
talk,
so
what
I
would
say
is
like
sandbox,
your
time
don't
spend
too
much
time
on
any
one
specific
thing,
and
you
know
just
the
final
hose
of
Cuban
artists.
You
know
if
you're
following
issues
or
PRS
or
or
the
slack
is,
is
crazy
and
you
cannot
pay
attention
to
everything
all
the
time
and
you
don't
have
to
you
should
not.
You
know,
go
through
the
meeting
notes.
You
know
of
the
things
that
you're
interested
in
you
know.
D
So
the
other
thing
that
I
would
say
is
like
get
to
know
the
people.
You
know
if
you
are
joining
a
cig
call,
and
you
hear
something
from
say:
Jordan
or
you
know
some
Brian
or
Tim
feel
free
to
ping
them
and
ask
them
and
talk
to
them
about
it
later.
We
are
all
people
here,
you
know.
Yes,
some
of
us,
you
know,
for
example,
Brian
or
Tim
might
be
very
busy,
but
then
they'll
still
make
time.
So
please
don't
hesitate
to
ask
questions
either
on
email
or
slack.
You
know
privately
as
well.
A
Was
just
the
near
thing
you,
like
I'm,
a
new
contributor,
you
said
we.
We
talked
about
mailing
lists
and
texts,
all
kinds
of
ways
to
communicate
in
there,
I
guess
what?
If
you
have
to
give
tips
about
communication
with
the
project
and
say
I'ma
go
I'ma
go
developer
and
they
are
starting
to
contribute.
What
are
some
tips
for
communication?
Would
you
tell
them
to
read
caps
as
like
a
good
first,
a
good
first
point:
what
are
some
communication
methods
that
you
think
are
really
good
for
folks
to
monitor.
C
Letty's
enhancement
proposal,
so
basically
in
order
to
communicate
and
a
larger
feature
changes
or
even
feature
changes
that
just
need
a
bit
more
discussion
and
needs
to
be
communicated.
Clearly,
we
write
documents
called
kept
so
keep
Nettie's
enhancement,
proposals
that
clearly
outline
first
of
all,
what
we're
trying
to
do
and
a
bit
of
background
and
then
a
summary
of
how
it's
going
to
be
done
and
then
also
goes
into
detail
as
to
like,
what's
required
in
order
to
do
that.
C
How
we're
going
to
classify
this
change
as
being
like
alpha
grade
beta
grade
stable
kind
of
talk
them
through
that
whole
process,
and
some
of
them
are
obviously
a
lot
more
extensive
than
others,
and
some
are
quite
small.
Just
they're
useful
for
just
communicating
I,
think
ideas
between
people
and
making
a
record
of
that,
and
so
we
can
incrementally
track
progress
of
things
changing
so
yeah
I
mean
I
personally.
Ask
someone
who
isn't
necessarily
writing
these
things.
C
So
often
I
find
it
really
interesting
to
look
at
caps
just
to
keep
a
tab
on
what
is
going
on
in
the
project,
because
there's
always
a
lot
of
interesting
things
come
up
and
it's
yeah,
it's
pretty
cool
to
see
a
lot
of
features
that
I've
wanted
for
a
while
and
then
see
actual
keps
coming
up
about
it.
Be
it's
like
a
really
clear
signal
that
there
is
some
progress
in
that
area
or
whatever
else
I.
C
Think
that
said
like
to
keep
up
on
day
to
day
development.
I
think
slack
does
tend
to
be
where
a
lot
of
chat
happens
in
the
sig
channels
and
like
corresponding
working
group
channels
beneath
that
I
think
not
sure
if
Tim's
explained
working
groups
earlier
when
you're
talking
about
the
structure,
but
it's
kind
of
cross
well,
when
certain
projects
require
more
involvement
than
just
a
single
sig.
C
So
if
something
involves
say
a
security
issue
with
the
cubelet
and
it's
like
a
long-term
goal
to
achieve
there,
that
might
involve,
say
sig,
auth
and
sig
sig,
node
or
something
like
that
and
working
group
could
be
formed
for
that.
So
it's
to
solve
a
more
specific
problem
and
yeah
this
similar
working
group
channels
on
slack
to
see
I
find
that
useful,
I
honestly
get
a
lot
of
mailing
list.
C
C
C
D
Do
want
to
go
back
to
the
NGO
developer,
starting
out
question
a
little
bit
more.
So,
for
example,
simple
things
to
do
if
you're,
a
good
helper
you
you
are
just
looking
at
the
codebase
and
you're
just
starting
out
the
the
easiest
thing
to
figure
out
is
like
look
at
our
unit
test
and
see
which
unit
tests
don't
have
good
coverage
right
of
the
packages
that
the
key
looking
at.
So
you
can
add
a
unit
test.
D
Okay,
what
is
the
step
of
whatever
git
hub
related
stuff
that
you
need
to
do
and
then,
once
you
are
able
to
open
a
PR,
then
you
know:
how
do
you
deal
with
all
the
bots
yelling
at
you
saying
this
is
broken
or
that
is
broke
and
then
help
and
figure
out
how
to
fix
them.
So
you
will
get
the
manual
steps
of
how
to
contribute
and
get
into
the
get
something
into
the
project.
That's
always,
you
know
a
good
start
for
anybody.
Who's
starting
off.
A
On
them,
for
those
who
are
just
joining
us
we're
halfway
through
right
now,
my
name
is
Paris.
We're
here
answering
questions
about
upstream
contributing
to
kubernetes
the
beast
that
insecure
brunetti
is
35
plus
thousand
of
you
humongous
crew.
If
you'd
like
to
ask
questions
and
you
want
to
participate,
please
please
join
us
we're
in
meet
our
contributors
and
currently
slack.
However,
most
people
do
direct
message
me
on
slack,
which
is
totally
fine
too
I'm.
Just
my
name.
You'll
find
me.
A
Please
join
us
dims
thanks.
That
was
a
good
answer,
so
I
do
have
a
DM
from
a
current
contributor
and
they're,
pretty
much
asking
me
for
tips
on
influencing
large
change,
so
if
they
have
either
a
proposed
solution
for
a
large
change
or
something
that
they
think
needs
that
they're
recommending
for
a
change,
etc-
and
you
know
they
get
quick
noes
wuts,
any
tips
advice
there
for
that
kind
of
an
impact.
I
B
I
think
it's
my
opinion,
so
I
think
like
talking
to
people
getting
the
general
idea
across
like
hey
I
wanted
15
people
on
slack.
It
doesn't
even
have
to
be
meetings
that
does
this
idea
sound
good?
B
D
I
can
always
add
so
so
the
way
to
do
this
is
not
like.
You
show
up
one
one
fine
day
with
a
thousand
line
patch
and
say
this
is
my
patch,
you
gotta
accept
it.
That's
not
gonna
work.
You
know
you
can
forget
about
getting
a
large
sized
chunk
of
code
in
you
know,
just
by
saying
okay,
this
is
the
path
this
works.
For
me,
this
works
in
my
environment.
Now,
please
merge
this,
that's
not
going
to
work.
What
you
need
to
do
is
that
you
have
to
make
the
pain
obvious.
D
You
have
to
explain
the
issues
that
you're
facing
and
then
you
you
can't
propose
solutions,
but
then
don't
be
married
to
one
single
implementation
of
something
that
you
did
to
be
like
the
final
one
that
gets
in
because
there
is.
This
is
a
community.
Everybody
has
opinions,
and
it's
not
just
that.
You
probably
don't
have
the
history
and
the
context
for
some
of
these
changes.
D
So
the
people
who
have
worked
on
it
before
probably
know
and
probably
have
ruled
out
some
things
earlier
because
of
either
the
stage
the
project
was
in
or
the
stage
the
code
was
in
or
the
stage
of
the
you
know
the
things
that
we
render
and
things
like
that.
So
you
know
try
to
understand
the
context
first
and,
like
Nikita,
said
the
best
way
to
do
that
is
by
you
know,
talking
to
people
and
use
all
the
communication
mechanisms
you
have
you
start
with.
D
You
can
start
with
a
an
email
thread
or
a
Google
Doc
to
outline
the
possibilities
you
can
open
up
issues
and
link
them
to
existing
issues.
To
show
that
you
know
this
is
not
something
that
you
are
facing,
but
other
people
have
asked
for
it.
We
have
like
2,200
2,300
issues
and
that
are
open
right
now,
so
you
you
can
practically
find
justification
for
a
whole
bunch
of
things
just
by
going
do
your
homework.
Basically
right.
D
Do
your
homework
in
terms
of
get
history
going
through
issues
trying
to
understand
the
context
or
reading
the
old
Google
Docs,
and
this
can
be
done.
This
is
not
a
big
deal,
but
just
don't
show
up
with
code
and
say:
okay,
this
is
this
is
what
needs
to
get
it.
That's
not
going
to
work
yeah
that
that
would
be
basically
my
suggestion.
There
I.
B
Just
want
to
highlight
something
that
else
mentioned
about
not
like
showing
up
one
day
with
a
large
change,
because
if
it's
a
huge
change,
especially
same
API
trail
or
something
like
that,
we
need
people
who
would
maintain
it
even
after
the
change
was
answer.
So
there
are
some
bugs
or
something
like
that.
So
if
you
just
come
up,
I
mean
if
you
have,
if
you
have
some
previous
contributions,
it's
easier
to
trust
people.
It's
like
it's
easy
for
others
to
trust
you
that
you're
gonna
stay
and
maintain
the
change
too.
So
that's
also.
A
A
So
I
do
I,
have
another
current
contributor
question
in
my
DMS,
but
we
can
actually
fit
it
too,
pretty
much
all
each
one
of
you
right
now
or
active
in
certain
groups
name
or
give
one
very,
very
specific
example
of
an
opportunity
that
you
have
in
your
group.
That
is
a
current
need
for
that.
You're
like
we
really
need
someone
on
this
just
one
because
I
guarantee
you
all
hi.
You
all
have
many
many
examples.
Mutters.
What
about
you
in
some
of
your
groups.
C
C
C
I
think
I'd
struggle
there,
but
yeah
I
mean
there's
loads
of
different
areas
to
get
involved
in
like
in
the
community
side
of
things.
That
was
something
I
realized
a
little
while
ago
and
applying
that
slight
moderation
stuff
to
help
out
there,
and
it's
actually
really
interesting
to
get
an
idea
of
community
building,
as
it
were,
yeah.
A
D
D
So
this
is
a
group
that
is
involved
in
trying
to
move.
You
know
the
responsibility
of
much
of
the
infrastructure
that
cuban
it
is
relies
on,
like
all
the
bots
that
we
run,
including
the
publishing
board,
that
Makita
takes
care
of.
So
there's
a
lot
of
infrastructure
behind
the
scenes.
So
we
want
all
of
them
to
move
to
community
hands,
there's
a
lot
of
things
that
are
currently
maintained
by
Googlers,
and
we
would
like
to
make
sure
that
you
know
they
move
to
CNC
of
properties.
D
So
there
is
a
working
group
doing
just
this
work,
and
this
is
nothing
to
do
with
code
that
ends
up
in
KK,
but
this
is
a
lot
of
the
infrastructure,
including
for
their
testing
CI,
and
things
like
that.
So,
if
you're
interested
in
that
kind
of
work,
there's
a
whole
bunch
of
things
to
do,
and
it's
like
kate's
infra
working
group.
So
that's
one
and
the
other
thing
that
I
wanted
to
call
out
here
is
a
core
organization.
D
Maintenance
is
everybody
likes
features,
everybody
wants
features,
but
then
we
have
to
pay
down
our
tech
debt
and
we
have
a
lot
of
things
that
we
have
to
do
in
just
the
day-to-day
maintenance
of
the
core.
You
know
simple
things
like
okay
go,
1:13
is
coming
out.
What
are
the
things
that
we
need
to
go
do
for
that
right.
That's
one
example.
Then
some
some
somebody
stopped
working
on
some
dependencies,
then
is
there
anything
that
we
can
switch
around
to?
How
do
we
restructure
the
code
in
KK?
D
So
we
can
pull
some
components
out
because
somebody
needs
to
use
it
without
rendering
all
of
Cuba
notice.
So
these
are
things
you
know
that
don't
really
need
active
participation
in
like
the
future
focused
or
feature
focused
stuff-
and
this
can
be
this
kiss
always
need
to
be
needs
to
be
happening
and
there's
a
bunch
of
these
things,
and
for
this
we
have
a
sub
project
in
signal
detection
called
code
organization.
So
if
you're
interested
in
this
kind
of
maintenance,
oriented
long-term
thinking
kind
of
thing,
so
please
come
and
help
there
as
well.
A
E
This
can
help
us
with
the
contributor
site.
It
is
a
different
repository
I
believe
it's
got
the
main
community
site.
It
does
have
its
own.
Please
get
in
touch
with
myself
or
Parris.
If
you
want
to
be
funneled
there
and
you
can
find
out
how
you
can
contribute,
there's
a
lot
of
places
where
we
need
help.
It's
not
all
just
code.
We
do
need
help
with
content.
We
need
help
with
organizational
things.
E
All
that
sort
of
stuff
definitely
get
in
touch
with
us
and
then
there's
also,
if
I'm,
pretty
sure
that
we're
looking
for
people
to
help
in
tribute
for
content
or
a
lot
of
stuff
surrounding
the
diversity
of
lunch,
coming
up
that
click
on
North
America,
probably
at
some
point,
so
you
can
help
there.
If
you,
if
that
interests
you
again,
it
doesn't
have
to
be
code,
it
can
be
content.
Please
get
involved,
reach
up
to
me,
reach
out
to
Paris.
E
D
So
they
would
really
appreciate
help
in
terms
of
just
organizing
the
work
it
could
be
just
issue
triage
or
PR,
triage
and
surface
things
like
okay,
these
pr's
are
ready,
you
know,
can
somebody
please,
you
know,
take
care
of
this
and
we
always
have
newcomers
who
have
who
struggle
to
get
some
code
through
and
if
you
turn
out
to
be
like
somebody
who
can
wet
the
code
and
and
tell
the
people
basically
look
this
this
stuff
is
ready
already
taken
a
look
at
it.
You
know
and
build
your
trust
there.
D
Then
you,
you
are
essentially
helping
the
project
out,
even
though
you're
not
doing
any
work
as
such.
You
are
looking
at
your
reviewing
the
code
and
making
sure
that
everything
is.
You
know
all
the
things
that
the
cygnets
usually
look
for.
Are
there
right
so
then
offer
to
pair
program
in
the
sense
that
you
know
look
over
other
people's
shoulders
when
they
are
doing
stuff,
so,
for
example,
I
always
go
and
look
at
what
Jordan
is
doing
or
you
know
Jim
Hawkins
doing
them
things
like
that,
so
I
follow
along
other
people's
work.
D
I
go
look
at
what
peers
they
are
working
on.
How
do
they
do
the
reviews
and
things
like
that
and
I
I
learn
from
what
they
do
as
well,
so
you
can
do
the
same
like
pick,
somebody
in
like
say,
Saud
or
you
know,
Michelle
right
in
sick
storage
and
then
follow
along
what
they
are
doing
and
see
and
see
see
where
you
can
help
them
out.
A
B
Like
to
specific
things
in
my
mind,
right
now,
so
one
is
coding.
Related
thing
in
one
is
a
non
coding
one.
So
I'll
go
with
it
on
coding,
one
first,
so
in
sick
contributor
experience,
we're
like
setting
up
a
new
team
called
triage
team,
and
we
also
have
a
new
stat
channel
fired
call
in
sick
control
box
triage.
B
So
it's
a
very
like
new
team.
We
still
like
deciding
the
meetings
and
everything
so
I
think
it's
a
great
place
to
help
out,
because
we
have
so
many
issues
in
community
repo,
which
mainly
requires
someone
to
like
follow
up
with
other
people.
Another
six
and
almost
everyone
is
most
of
the
people,
are
bandwidth
and
straight
and
don't
have
the
bandwidth
do
all
of
this.
B
So
they
doing
this
skin
is
like
a
very
easy
place
to
start
in
my
opinion,
and
it's
also
a
way
to
like
get
to
know
everyone
else
like
who
is
who
what?
What
other
things
that
other
SIG's
work
on.
Everything
else
say
that
the
other
coding
related
aspect
that
I
had
in
mind
was
the
position
bottoms
just
mentioned.
So
it's
about
so
in
the
kubernetes
kubernetes
repo.
We
have
staging
directory
and
there
is
a
bot
which
publishes
are
copies
code
from
this
directory
to
individual
repos.
B
So
the
publishing
bot
is
responsible
for
copying
this
and
right
now
it's
just
about
three
people
like
me
them
and
Stephan
who
work
on
it
and
sometimes
it
breaks
and
when
it
breaks
it
causes
problem
to
a
lot
of
people,
especially
consumers
of
these
other
individual
repos,
and
everyone
uses
these
for,
like
everything
like
client
go,
is
like
one
of
the
big
ones
and
always
breaks
during
the
release.
Time
behind
in
the
release
time
and
when
it
breaks
usually
like
one
of
the
three
of
us
needs
to
take
care
of
it.
B
Usually
we
do
it
the
pre-credit
right
now,
but
I
feel
like.
We
could
also
use
more
people
in
case.
One
of
us
is
traveling,
we're
not
available
on
vacation
or
something
the
other
it's
written
and
go,
and
most
of
what
you
need
is
get
knowledge.
So
I
think
like
if
anyone's
interested
I
was
happy
to
help
out
even
getting
started.
A
A
B
B
D
I
do
yeah
I,
do
try
to
do
email,
zero,
twice
a
day
and
usually
I'm
able
to,
but
in
a
lot
of
this
icon,
but
I
do
have
a
bunch
of
email
filters
as
well
that
I
used
to
you
know
more
things
out,
like
you
know
the
queue
minutes
website,
I
move
it
to
a
separate
folder
and
I.
Do
it
on
demand
kind
of
thing,
but
then
I
look
for
like
Nikita,
said:
I,
look
for
keywords
of
the
things
that
I'm
interested
in
either
in
the
subject
or
I.
D
Look
for
the
names
of
the
people
I
like
I
mentioned
before,
and
then
I
do
a
rapid
filter
and
you
know
skip
a
bunch
of
things
that
I
that
I
don't
pay
attention
to.
But
then
it
becomes
harder
during
the
release
time
because
you
have
to
pay
more
attention,
especially
when
we
cut
betas
and
our
c1
or
c2
or
those
kinds
of
things,
because
you
don't
know
at
that
point
what
issue
might
be.
You
know
a
showstopper
for
their
release
and
things
like
that.
D
So
it
becomes
harder
at
that
time,
but
you
know
other
than
that.
Yeah
I'm
fortunate
enough
that
you
know
my
employer
paced
me
to
do
this:
the
full-time
job.
It
is
way
too
difficult
for
people
who
do
this
on
a
part-time
basis.
So
that's
another
thing
that
I'm
trying
to
change
in
the
sense
that
we
have
to
switch.
D
You
know
the
mode
of
our
thinking
from
like
Nikita
mentioned
the
West
Coast
time
to
around
the
clock,
and
also
going
from
fully
paid
contributors
who
work
on
Cuban.
It
is
full-time
to
part-time
contributors.
You
know
over
the
long
haul
use
a
long
tail
of
contributions.
This
is
already
happening
with
a
bunch
of
things
that
we
are
doing
for
you
know,
folks,
from
India
and
China.
You
know
that
helps
take
care
of
spreading
the
load
around
the
globe.
D
There
is
a
lot
of
new
people
coming
in
from
India
and
China,
as
for
sure
they
are
helping
out
with
even
for
things
like
translations
right
language,
translations
of
the
documentation,
and
things
like
that
as
well.
So
I
was
happy
to
see
the
Hindi
translation
for
some
of
the
things.
So
so,
basically,
I
want
to
be
I
want
to
make
sure
that
sick,
contra
max
starts
thinking
more
about
how
we
can
change
the
mode
that
we
work.
How
do
we
make
it
easier
review?
D
Bandwidth
is
a
constraint
for
sure
right,
and
one
of
the
things
that
we
are
trying
to
do
here
is
look
through
owner
files
and
see
owners
and
reviewers
for
both
all
right.
So
try
to
look
through
those
to
see
if
people
who
have
kind
of
like
dropped
out
of
you
know
they
used
to
be
active
in
Cuba
notice,
but
not
active
anymore,
and
we
still
assign
issues
and
you
know,
pull
requests
to
them
for
reviews
and
you
know
getting
to
getting
them
to
work
on
something.
D
We
start
making
sure
that
the
people
who
are
not
active
anymore
are,
you
know,
move
to
emeritus
status
and
then
people
who
are
currently
active
and
reviewing
and
coding
get
added
to
the
owners
files.
So
if
you
are
active
in
a
specific
area,
please
talk
to
the
cygnets
and
ask
to
be
added
as
a
reviewer.
That
would
definitely
help
not
just
you,
but
there
are
other
people
who
are
struggling
to
contribute
as
well.
A
A
What
I'm
checking
my
other
areas
to
just
to
make
sure
I
haven't
missed
anybody,
questions
that
are
relating
to
common
pitfalls
that
you
see
with
contributors
either,
whether
that's
with
tooling,
whether
that's
with
github
infrastructure,
whether
that's
with
communication
and
what
are
some
common
pitfalls
that
you
see
from
contributors
that
either
maybe
a
you
wish
you
knew
before
or
B.
You
wish.
You
had
a
megaphone
to
announce
from
a
high
rooftop
somewhere.
D
Okay,
so
if
I
want
to
use
a
megaphone,
then
I
would
say:
if
you
want
to
learn
about.
You
know
the
process
itself,
then
you
know
pick
up
a
typo
or
some
small
change
and
get
it
true
and
don't
keep
doing
the
same
thing
over
and
over
again
right
in
doing
do
one
or
two
and
then
switch
to
doing
some
more
meaningful
work,
and
if
you
can't
find
meaningful
work,
come
see
us
and
we'll
tell
you,
you
know
what
is
important
and
what
would
be
of
use
to
everybody
right.
D
So
it's
a
useful
tool
too,
but
don't
try
to
do
this,
for
the
statistics
that
show
up
in
dev
stats
or
something
like
that
or
you
know
it's
not
you're,
not
here
trying
to
collect
badges
as
such.
You
are
here
too.
You
know
what
I
use
Cuban
artists
for
is
to
make
myself
more
knowledgeable
in
the
areas
that
I
don't
know
about.
So
it
is
I
use
it
to
educate
myself
and
improve
my
knowledge
as
such,
but
then
in
don't
game
for
stats.
Basically,.
A
C
Yeah
I
mean
I'd,
say
I
think
so.
I
mentioned
it
earlier
again
like
on
the
like
people,
diving
in
with
big
chunks
and
just
kind
of
making
big
change
there
I
think
if
you
have
got
an
idea
for
something
jumping
onto
something
like
a
slack
channel
first,
just
to
put
it
out
there
and
then
saying
look.
Can
we
chat
about
this
at
the
next
bi-weekly
meeting
or
the?
However
often
the
six
meetings
are,
you
can
actually
get
a
surprising
amount
of
traction,
I
think
on
that
sort
of
thing.
C
As
long
as
it's
something
you
can
kind
of
come
up
with.
Well,
if
there's
something
that's
either
been
discussed
in
the
past
and
there's
been
some
idea
as
to
how
it
can
be
done
or
if
there
is
or
if
you're
able
to
actually
come
up
with
some
simple
way
to
implement
it.
I
think
again,
Nikita
you
mentioned
before
about
kind
of
big
changes
require
long
term
main
tailors
on
there.
C
So
there
is
that
to
bear
in
mind,
but
and
if
you
can
find
those
smaller
areas,
just
their
little
needs
and
kind
of
communicating
with
sinks
first
actually
having
that
chat
and
then
going
from
there
and
working
with
them
yeah
and
then,
like
I,
guess
they're
to
get
side
on
that
train.
There's
a
few
issues
that
are
labeled
specifically
for
that
with
a
Help
Wanted
could
first
issue
and
so
on.
So
that's
all
it's
just
quite
good.
B
I
had
a
microphone
so
something
that
I
notice
in
older
peers
is
that
people
have
someone
in
a
PR
but
they're,
not
getting
reviews
like
Vince
mentioned.
We
have
lots
of
reviewers
are
not
actively
reviewing
right
now,
because
maybe
they've
moved
on
from
project
bring
people
on
slack
about
it.
You
might
not
get
a
response,
even
if
you
get
assigned
someone
on
CC,
someone
on
it
and
a
good
place.
B
If
you
don't
know
which,
like
channel
to
ask
where
to
ask
essentially,
is
the
PR
review
strong
and
students
for
initiating
that
we've
I've,
seen
like
lots
of
PR
Scott,
lgt
I'm
not
approve,
or
at
least
get
like
the
next
steps
for
those
PRS
mentioned
when
someone
puts
it
out
there
so
I
think,
like
lots
of
people
complain
like
hey
this?
Isn't
this
PR
isn't
getting
reviewed?
It's
been
like
a
month.
I
know
it's
not
ideal,
but
definitely
like
thing
on
sac.
D
The
other
thing
here
is
patience
if
you
just
have
one
PR
in
flight-
and
you
are
just
looking
at
that
PR
to
see
if
somebody
has
commented
and
something
some
progress
is
happening
or
not,
then
you
are
very
likely
to
get
frustrated
because
of
the
review.
Time
lag
right
so
have
a
bunch
of
things
in
progress,
so
at
least
you
know
it
doesn't
feel
as
bad,
which
is
what
I
do
for
my
own
peers
as
well.
J
A
D
A
And
Rin
I
think
you're
gonna
actually
have
a
good
perspective
here,
since
you
have
a
few
PRS
and
you're
about
now.
What's
what's
one
thing
that
you
wish,
you
knew
then
that
you
know
now
about
contributing
upstream
it
can
be
little.
It
can
be
meta.
What's
with
something
that
pops
into
your
mind
or
something
that
you've
said
like
wow
wish,
I
knew
this
was
here
before.
E
E
E
E
E
A
A
E
A
Cool
that
was
a
good
response
and
that
wraps
our
show
for
October
we're
doing
this
again
in
November.
For
those
of
you
that
are
listening
and
that
you
can
vote
for
the
steering
committee
I.
Think
today
is
your
last
day.
That's
all
I
have
to
say
about
that
cool
panelists,
you're,
awesome,
I,
really
appreciate
you
George.
You
too
thank
you
for
y'all
the
YouTube
magic
that
goes
on
behind
the
scenes,
and
that's
it.
We're
out
see
you
next
time.