►
From YouTube: Kubernetes Meet Our Contributors 20200506
Description
Meet Our Contributors gives you a monthly one-hour opportunity to ask questions about our upstream community, watch interviews with our contributors, and participate in peer code reviews., Paris Pittman (@parispittman) and a few other contributors for live upstream q&a, post Kubecon storytime, and your monthly dose of random!
When Slack seems like it’s going too fast, and you just need a quick answer from a human...
Meet Our Contributors gives you a monthly one-hour opportunity to ask questions about our upstream community, watch interviews with our contributors, and participate in peer code reviews.
Check out this page for more information: https://github.com/kubernetes/community/blob/master/mentoring/programs/meet-our-contributors.md
A
All
right,
everyone
welcome
to
May
edition
of
kubernetes
meet
our
contributors.
My
name
is
Paris
I.
Do
this
monthly
on
the
first
Wednesday,
it's
nice
to
see.
And/Or
hear
you
again.
If
you
are
either
joining
us
on
the
panel
is
Evette
or
joining
us
live
as
a
newbie
or
someone
that
is
inexperienced
and
contributing
with
us
for
a
long
time.
This
show
is
for
you
to
ask
questions.
A
I
see,
we
see
a
lot
of
you
ask
questions
and
the
kubernetes
dead,
slack
channel
on
mailing
lists
on
twitter.
This
is
a
live
version
of
that
and
we
will
try
to
get
you
to
where
you
need
to
go
on
your
journey
here.
Just
some
house
rules.
First,
we
do
have
a
code
of
conduct.
Please
be
excellent
to
each
other.
This
includes
in
the
meet
our
contributors,
slack
channel
or
really
any
slack
channel
twitter,
any
forum
that
we
are
playing
in
at
that
moment.
A
If
you'd
like
to
ask
questions,
you
can
do
so
in
two
different
ways.
You
can
do
that
anonymously
or
you
can
do
that
publicly.
Publicly
is
better
because
we
get
to
talk
to
you.
Live
anonymously
is
via
DM
direct
message
on
slack,
and
my
display
name
is
right
here
on
zoom'
as
well.
That's
Paris
you'll
actually
find
two
terraces
on
this
lock
channel
these
days,
so
hello
to
the
other
Paris
out
there
and
the
last
but
not
least,
the
public
questions
can
be
asked
and
addressed
in
the
slack
channel.
A
B
My
name
is
Aaron
frickin
burger.
You
can
find
me
as
at
spiff
XP
on
all
the
places
github
twitter
slack
whatever.
I
am
currently
the
chair
of
sync
testing
and
an
organizer
of
the
case,
central
working
group
and
a
member
of
the
steering
committee.
My
interest
is
primarily
I.
Don't
know
what
it
is
you
people
do
here,
but
I
want
to
help
you.
Do
it
better,
faster
and
stronger,
so
I
work
primarily
on
the
infrastructure
that
helps
run
tests
and
make
tests
usable
for
the
community
and
then
in
case
infra.
B
C
Brady
Bunch,
my
name
is
J
Beal
I
am
one
of
the
leads
on
the
security
and
the
third
party
security
audit
working
group,
and,
let's
see
my
contribution
so
far,
have
been
outside
of
sort
of
working
there
and
leading
there.
It's
it's
a
no
code
yet,
but
the
documentation
which
has
been,
which
has
been
really
fun
and
if
we
get
a
chance,
I'll
show
you
how
easy
that
is
to
contribute
to.
Yes,.
A
C
Yeah
a
job
is
day
job
as
at
in
Guardian
from
the
CTO,
and
we
do
lots
of
kubernetes
penetration
testing
and
security
on
it
and
by
and
pre
you
know,
pre
pre
I
was
gonna,
say
pre
deployment,
but
you
know
pre
cluster
build
help
and
so
on
so
I'm
yeah.
This
has
been
there's
been
a
blast,
I
didn't
for
a
couple
of
years
and
I
really
I've
really
loved
the
new
cloud
native
world
awesome.
A
This
just
proves
that
there's
so
many
types
of
contributors,
y'all
and
that's
what
I'd
like
to
do
on
this
show
is
make
it
so
that
all
the
mentors
here
are
from
different
backgrounds
and
contribute
in
different
ways,
so
that
folks
can
get
a
really
clear
sense
of
of
all
the
onboarding
paths
and
different
things
so
less
than
a
lot,
not
least
Monica
new
to
the
show
Monica.
Would
you
like
to
introduce
yourself.
D
I'm
Monica
I'm,
actually
a
site
reliability
engineer
at
V
we're.
Currently,
my
primary
involvement
has
been
with
the
cloud
provider
sig
mostly
with
OpenStack,
so
I
know
that's
kind
of
a
weird
away.
That's
from
a
previous
life,
but
you
know
been
in
smaller
changes
like
doc,
updates
and
things
you
know
finally
bugs
or
something
that's
my
area,
I
guess,
I'm
more
of
a
new
contributors,
so
I
would
definitely
love
to
encourage.
You
know
newer
contributors
to
come
out
there
and
even
people
that
don't
consider
themselves
developers.
D
I,
don't
you
know
pretend
to
be
a
go
developer
at
all
or
anything,
but
you
know
just
being
out
there
and
trying
and
following
tutorials
and
not
being
you
know
that
deep
dive
level
of
technical
there
as
an
operator
of
kubernetes,
you
know
it's
something
that
I
still
get
to
work
with
a
bunch
and
you
know,
like
said
help
out,
encourage
other
people
to
try
to
step
up.
Yes,
it's
awesome.
A
Thank
you
so
much
for
joining
us
today,
so
lovely
to
meet
you
face
to
face
for
the
first
time,
and
so
the
other
ground
rules
is
to
that
I
didn't
mentioned
before.
Is
you
all
can
ask
each
other
questions?
J,
Aaron,
Monica
you've
never
necessarily
met
each
other
before
and
if
you
have
questions
during
this
time,
just
butt
in
okay.
So
that's
the
that's.
The
ground
rules
all
right.
So
let's
go
right
into
the
first
one
and
it's
actually
kind
of
silly,
which
is
good.
It'll
kick
us
off
in
a
silly
tip.
A
B
Okay,
so
actually,
this
shirt
is
for
me
getting
to
serve
on
the
1:14
release
team
of
kubernetes
as
the
release
lead.
So
back
in
the
day
in
my
very
early
days
of
working
with
kubernetes
I
started,
helping
out
with
release
process.
It's
something
we're
like
the
entire
community
can
help
build
and
curate
a
release
of
kubernetes.
So
I
started
out
with
kubernetes
one
for
helping
with
release
notes.
B
You
know
doing
Docs
changes
and
stuff
and
work
my
way
through
some
other
roles
like
issue,
triage
or
CI
signal,
where
I'm
trying
to
help
figure
out
like
which
test
failures
are
real
or
meaningful,
and
eventually
all
the
way
through
to
release
lead.
Now,
one
of
the
jobs
of
release
lead
was
to
help
keep
the
community
informed
about.
What's
going
on
with
the
release,
what
milestones
and
deadlines
do
they
need
to
be
aware
of
things
of
that
nature,
and
so
back
what
I
was
doing
this
we
had.
B
The
community
meeting
happened,
weekly
and
so
I
felt
like
at
some
times.
It
can
be
a
bit
of
like
a
boring
process,
read
out
a
laundry
list,
the
process
and
so
I
thought,
maybe
to
help
keep
people
showing
up
or
at
least
check
it
out
each
week,
I
would
wear
a
different
cat
t-shirt
each
and
every
week.
B
So
that's
our
nephew,
13
cat
t-shirts
I
have
yet
I
should
like
make
a
collage
of
all
of
them,
so
that
was
pretty
fun
and
then
each
release
lead
gets
to
make
some
sort
of
like
exclusive
swag
for
members
of
the
release
team,
and
so
of
course
it
had
to
be
a
cat
t-shirt
and
I
was
like
okay.
So
basically,
I
want
three
Wolf
Moon,
but
the
wolves
are
cats
and
the
moon
is
kubernetes
and
I
think
it
came
out
pretty
well
tuning.
A
B
C
B
B
C
Jay,
what
about
you
literally
I,
literally,
don't
have
a
single
cat,
t-shirt
and-
and
at
this
point
it
feels
a
little
deficient
and
are
wondering
if
I
should
be
hunting
around
the
kubernetes
project
to
see
what
what
what
swag
you
can
get
it's
different
with
lots
and
lots
of
contributions
to
different
areas.
It's
like
a
whole
Wow,
yeah,
yeah.
A
You
know
what
we
should.
Actually
you
know
what
I
do.
I
have
a
contributor
summit,
one
two,
so
you
also
get
the
you
also
get
different
varieties.
This
was
the
Barcelona
one
from
Josh
Burgess.
So
yes,
so
there
are
ample
ways
of
getting
exclusive
schwag
within
the
project.
When
you
contribute
so
I
guess
the
the
TLDR
there
is
there's
other
fun
besides
flipping
bits.
So
that's
the
good.
The
good
news
is
that
there
is
tons
of
other
stuff.
You.
C
A
A
They
just
were
curious
about
your
journeys
honestly
and
in
this
case
journey
being
extreme,
so
you
set
a
little
bit
in
your
bios
about
what
you
do
upstream
and
how
you've
got
involved,
but
take
us
through
that,
like
maybe
first
PR,
that
you
did
and
also
the
why
behind
it,
what
were
you
like
motivated
because
you
are
employed?
Were
you
motivated?
Because
you
wanted
to
change
a
doc,
because
you
were
reading
the
dog
just
take
us
through
kind
of
how
you
got
here
really
Monica?
D
Bit
about
the,
why,
yes,
you
know
previously
I
worked
like
I
was
open
stack,
and
so
you
know
there
was
an
issue
that
came
up
an
open
stack,
documentation.
I
would
you
know,
try
to
update
it,
because
I
saw
that
it
was
wrong
and
said:
well,
that's
easy
enough
to
fix
you
know,
and
so
the
same
they
gotta
happen
once
I
got
over
to
kubernetes.
So
for
me
it
was
just
waiting
for
an
opportunity
to
be
able
to
contribute.
You
know
I
gone
through
trying
to
figure
out.
Oh
my
gosh.
D
Look
at
all
these
tags.
You
know,
like
you
know,
help
need
it,
and
you
know
first
time
is
your
first
time
or
something
you
know
different
types
like
to
help
new
people
get
in
and
it
was
super
overwhelming.
So
just
seeing
something
small
like
oh,
my
gosh,
like
I,
can
actually
tackle
that
I
can
help.
You
know.
I
just
want
to
be
able
to
contribute
in
some
way.
I
start
like
I
wasn't
gonna
be
able
to
start
off
with,
like
adding
new
features
to
something
like
that.
That
was
a
little
beyond
me.
D
D
Oh
what
is
it
called
like
the
signature
and,
like
you
say,
like
I'm,
the
like
that
nothing
like
since
a
we
made
the
contributor
agreement
right
so
doing
that
and
kinda
understand
how
that
works
in
a
reading
through
the
flow
was
pretty
straightforward
and
then
doing
the
PR
where
you
get
the
automated
bot
comment.
Oh
my
gosh.
What
is
this?
What
is
this?
Why
was
it
rejected?
D
Just
really,
you
know
wanted
to
to
help
out
there.
That's
why
I
did
it.
I
certainly
were
kubernetes
on
a
daily
basis.
So
it's
always
good
to
make
something
better
that
you
work
with
every
day,
but
it
wasn't
like
you.
You
know
you
have
to
contribute.
You
know
from
employer,
they
didn't
you
know
whatever
they
good.
If
you
do
it's
fine,
if
you
know
but
yeah,
it's
premature,
you
got
the
support.
D
C
So
the
I
I
started
getting
before
before
trying
to
get
before
trying
to
help
in
the
project
itself.
I
started
working
on
some
tools,
I'm,
creating
some
tools
and
like
one
of
those
is
one
of
those
that
is
an
intentionally
invulnerable.
Corday's
cluster
and
another
is
a
it's
kind
of
a
attack
tool.
It's
useful
if
you're
on
a
pen
test
and
so
he's
getting
like
I,
was
really
interested
in
figuring
out
how
I
could
help
on
kubernetes
playing
from
that
attacker.
C
You
know
playing
from
that
attacker
and
defender
perspective
and,
and
so
I
ended
up.
Just
kind
of
I
I
saw
I
think
what
motivated
me
was.
I
saw,
Jeff's
Brazil
was
talking
about
multi-tenancy
in
a
tweet
and
I
said
wow.
It
sounds
like
they're,
really
just
still
trying
to
figure
out
the
multi-tenancy
model
for
kubernetes.
C
That's
you
know
like
if
somebody
on
the
out
as
somebody
who
plays
insecurity
all
day
that
was
horrifying
and
and
yet
it's
an
open
source
project
that
it's
something
like
you
know
like
and
and
it's
a
horrifying
is
often
really
really
like.
That's
what
gets
security
people
are
really
interested
like
okay,
cool?
What
you
know,
what's
that
look
like
what
can
I
learn
about?
C
What
can
I
do
there
and
so
I
showed
up
to
the
multi-tenancy
working
group
and
and
just
tried
to
listen
and
then
contribute
and
showed
up
to
the
third-party
security
audit
working
group
and,
and
there
I
just
I
found
there
was
a
lot
I
could
contribute,
because
you
know
I
was
I
was
I
was
from
a
company
that
did
a
ton
of
you
know
of
did
a
ton
of
kind
of
security
audits,
not
the
kind
that
we
do
for
kubernetes
like
more
Network
focused
and
not
code
on
it
and
I
thought.
Oh
wait.
C
I
can
help
here,
I
I
know
what
it's
like
to
be
to
be.
The
third
party
I
bet
I
can
help
I
bet.
I
can
help
us
find
a
third
party
and
help
manage
and
answer
questions,
and
just
you
know,
help
help.
Somebody
get
commit,
sorry
help
a
firm
get
connected
in
and
understand
like
get
connected
with
what
they
have
to
figure
out
in
order
to
audit
our
source
code.
C
For
me
like
for
somebody,
who's
just
figuring
out
a
contribute
like
you've,
become
experience
with
cribben
I.
Do
she
transferred
how
to
get
in
Monica
brought
this
up
to
like?
For
me,
the
first
contributions
I
made
were
to
documentation,
and
it
was
literally
I
was
I,
was
building
this
intentionally
vulnerable
cluster
and
the
pod
security
policies
didn't
work.
The
way
work
is
their
own
work.
We're
document
just
got
a
little
tiny
bit
wrong
in
terms
of
how
you
set
them,
and
so
I'm
like
well,
okay,
I
can
write,
you
know
I
better.
C
C
Monica
was
talking
about
and
and
and
submit
in
my
first
pull
request
against
Docs,
and
that
was
I
was
kind
of
fun
and
it
was,
and
it
was
pretty
easy-
I
mean
I
I'm,
just
I'm
really
I've
been
really
impressed
with
how
easy
the
the
Kerr
Bernays
organization
makes
it
and
how
open
they
were
to
you
know.
Somebody
who
hadn't
ever
contributed
before
saying,
hey
I
think
I
found
something
I
can
you
know
I
think
I
found
something.
What
do
you
think
of
this
wait?
Long,
winded,
no.
A
D
D
You
know
and
then
going
to
like
the
new
contributors
of
it
and
really
being
encouraged
to
do
that
and
then
actually
trying
it
I
mean
they
really
do,
whoever
they
is
really
do
want
anybody
to
contribute,
and
it
really
is
possibly
you
don't
have
to
be
technical
and
that's
one
of
the
things
I
think
I
was
really
amazed.
You
know,
I
didn't
want
to
be
super
competitive
with
how
many
get
commits
or
something
you
know.
How
much
have
you
done?
What
is
your
chart?
D
A
B
So
I
started
as
a
consumer
of
kubernetes
back
in
2015
slightly
before
I
went
1.0
I
didn't
land,
my
first
full
request.
It
looks
like
until
October
50
luck,
he
looked,
dude
I
didn't
know
the
thing,
but
like
I,
considered
myself,
a
member
of
the
community
long
before
I
had
landed.
My
first
pole
request
because
even
back
then
in
those
early
days,
while
there
were
no
cigs
and
whatever
there
was
the
community
meeting
where
I
could
show
up
and
sort
of
hear
what
was
going
on,
asked
questions
of
community
members
so
on
and
so
forth.
B
I
really
wish
the
meet
our
contributors
that
was
around
back
then
I
think
that
would
have
been
really
great.
So
the
first
PR
I
landed
was
a
code.
I
didn't
write.
I,
just
cherry
picked
a
fix
from
the
master
branch
in
to
release
branch,
because
I
was
deploying
kubernetes
was
a
thing
called
hypercube,
which
is
now
deprecated,
but
there
was
a
bug
and
I
needed
the
bug
to
work
on
my
branch
and
then
I
was
doing
this
to
deploy
thousand
no
kubernetes
cluster
to
prove
that
it
could
work
in
a
thousand
nodes
while
kubernetes.
B
Officially
only
supported
a
hundred
notes
in
as
of
that
release,
which
led
to
us
eventually
forming
the
first
sink
for
kubernetes,
the
scalability
sake
where
we
helped
to
like
document
and
define
what
kubernetes
should
officially
support
and
what
metrics
there
were
and
stuff.
But
so
that
was
that
was
how
I
got
started
and
then
just
to
go
a
bit
further
from
that,
like
I
I
was
really
interested
in
how
kubernetes
was
tested
publicly.
B
It
felt
like
at
the
time
a
lot
of
the
tests
that
were
driving
kubernetes
and
that
people
were
paying
attention
to
weren't,
actually
publicly
accessible.
They
were
on
some
Jenkins
server,
hidden
behind
the
walls
of
google.com,
where
they
were
also
running
on
Travis,
where
they
were
also
running
on
shapeable.
A
So
you
submit
a
PR
or
want
to
submit
a
PR
or
want
to
submit
an
issue
etc,
and
you
need
to
find
this
thing
called
a
cig
and
for
those
who
are
watching
and
they're
like,
what's
a
saying
whose
sake
is
a
special
interest
group,
that's
how
we
break
down
the
codebase.
Those
are
the
people
bodies
of
people
that
own
that
thing.
So
you've
got
a
contributor
here
and
I'm
gonna
share
my
screen
so
that
you
see
the
deets.
A
A
D
So
for
me,
I,
so
I
see
right
there
in
the
chat
window.
It
says
like
the
labels,
it
needs
a
sig
right.
So
obviously
that
you
know
the
issue
doesn't
have
that
right
now.
So
that's
why
you're
asking
so
for
me
what
I'm?
Looking
for
what
you
know,
what
sig
it
is
I'm
gonna
go
we'll
probably
look
at
the
relevant
code.
Maybe
do
like
a
look
at
the
log,
the
history.
D
You
know
they
get
blamed
whatever
it
might
be
to
see
you
know
what
are
their
commits
were
put
around
that
code
if
it's
in,
like
part
of
a
module
or
something
just
the
general
area,
and
then
look
at
other
issues
and
see
what
the
other
issues
have
had.
First
part
like
as
far
as
the
cig
label,
because
I
the
labels
are
pretty
good.
I
feel
like
whenever
I
look
for
an
issue,
there's
usually
already
a
bug
open
and
or
something
very
close
to
it.
D
So
it
usually
it's
not
too
hard
to
find
a
cig
and
then
I
mean
there's
the
list
of
all
of
the
kubernetes
SIG's
right,
which
can
be
kind
of
like
it's
big
and
you
might
not
even
clean,
oh
well,
what
what
just
cloud
provider
mean
and
then
inside
a
cloud
provider
like
there's
a
ton
of
different
components
to
that,
so
that
can
be
difficult,
but
if
you've
got
a
general
idea.
Well,
it's
you
know:
it's
testing
related.
You
can
kind
of
drill
down.
You
know
and
get
the
idea
from
that
as
well.
Finding.
A
Other
issues
and
PRS
that
are
similar
that
do
you
have
say
labels
is
a
perfect,
is
a
perfect
way
if
you
don't
necessarily
know
the
like
the
owners
method
and
like
how
their
mapping
it
from
charters
and
stuff.
So
that's
awesome
example:
J
you're,
doing
security
on
it
and
need
to
find
a
piece
of
code
and
who
owns
it.
That's.
C
C
C
You
know
you're
you're
likely
to
be
piling
everyone's
like
it'll,
be
piling
on
the
same
person,
so
I'm
I,
don't
know
it's
almost
like.
Do
you
round-robin
on
prime
message
or
you
just
where
do
you
just
hit
a
group
or
best
you
just
hit
the
you
just
hit
the
channel
and
mention
the
names
unless
you're
dealing
with
something
that
might
be?
You
know
embargoed,
but
so
yeah.
C
For
me,
it's
it's
slacks
been
slacks,
been
really
good
and
asking
the
people
I
know
who
they
know
has
been
good,
but
honestly,
slacks
been
pretty
slacks
been
pretty
great
and
and
the
project
is
I'm
actually
I've
actually
been
pretty
pretty
surprised
that
nobody's
been.
It's
never
felt,
I,
don't
know
if
you
ever
have
this
fear,
but
it's
but
I
have
certainly
when
you,
you
know
when
you
come
in
something
new.
C
It's
like
are
people
gonna
be
like
you
know
who
I
am
I'm
Way
too
important
to
answer
your
question
you
know
are
way
too
important
to
handle
that,
like
at
the
very
least,
if
anybody's
way
too
busy
they'll,
you
know,
they'll
punch,
it
they'll,
introduce
you
to
somebody
else
and
that's
perfect,
but
everyone's
always
been
really
friendly
and
and
I've
really
appreciate
that
I
appreciate
it
that
quite
a
bit.
Oh.
C
Either
that
or
it's
like
a
big
evil,
you
know
big
evil
or
or
everyone's
where
they've
got
cookies
and
smiles.
And
you
don't
know
you
don't
know
how
evil
it
is
until
you're
until
you're
sitting
where
Aaron
and
Paris
are
where
they
had
to.
You
know
or
they've
done
so
much
like
somebody
finally
says,
oh
by
the
way,
it's
the
it's
the
evil
empire
in
here.
Somehow
it's.
A
That's
a
good
Jay
thank
you
and
for
folks
that
are
joining
us
from
Twitter
and
they're,
like
slack
what
slack,
what
kubernetes
slack
slack
decades,
that
I
owe
for
your
invite
I
think
most
of
the
people
that
watch
us
with
that
watch.
This
program
by
the
way
are
on
slack
because
they
get
a
lot
of
messages
through
there
about
this
program.
But
if
you're
out
there
and
just
joining
us
slack
aides,
io,
k,
8s
I,
know
it's.
C
A
That
we
are
about
30
minutes
into
this
journey,
so
we're
about
half
done
for
folks
that
are
just
joining
us
and
there
are
wondering
what
the
heck
is
going
on
here,
whether
you're
joining
us
from
Twitter
slack
kubernetes
dev
mailing
list,
whatever,
wherever
you
found
us
if
you're
just
joining
and
you'd
like
to
ask
questions,
please
do
the
meet
our
contributor
slack
channel
is
where
you
can
ask
publicly,
or
you
can
direct
message
me.
My
message
is
or
my
handle
is
Paris
and.
A
B
I,
don't
think
I
have
a
super
technical
answer,
I'm,
so
sorry
in
Paris
I
would
do
kind
of
what
Jenny
suggested.
I
think
I
searched
for
no
execute
paint
manager
in
the
code
to
see
like
what
file
it
lived
in
and
some
in
the
path
to
get
there
had
the
words
node
and
scheduler,
so
I
probably
go
ask
either
sig
note
or
sig
scheduling
in
slack.
If
nobody
responded
for
a
while
I
might
act
like
the
chairs
of
the
tech
leads
and
I
would
presume.
If
that's
not
the
right
place
to
ask
about
it,.
D
B
Would
probably
point
me
in
the
direction
of
another
channel
yeah,
the
the
slightly
more
technical
answer?
I
could
give
doesn't
really
work
super
well
for
issues
but
like
if
you
are
submitting
a
full
request.
We
have
a
feature
where
the
label
will
automatically
get
applied
to
your
PR,
based
on
their
call
the
owners
files
that
live
in
folders
along
the
way,
which
is
actually
how
this
person
said
they
could
know
who,
like
which
individuals
owned
the
code.
C
B
C
B
B
C
If
you
felt
really
bad
about
that,
you
know
like
you
could
do
you
could
you
could
file
an
issue,
but
you
know
anywhere
that
I
in
a
lot
of
places
anywhere,
there's
a
just
a
chance
for
a
full
request.
If
it's
something
really
really
straightforward,
the
pull
request
is
probably
kinder
to
the
whole
project
than
the
than
the
issue.
A
Is
that
like
I
want
that
on
a
shirt?
Actually,
that
is
that's
a
good
phrase.
I've!
Never
really
put
it
that
way
before
Aaron
I
thought
you
were
gonna
mention
so
I
thought.
You're
gonna
mention
this.
The
C
word,
which
is
Charter.
That's
what
I
thought
I
thought
you
were
gonna
go
to
the
Charter
method,
which
is.
A
A
D
Ever
doing
that,
I
mean
I'm.
A
new
contributor
I
do
have
that
feeling
of
like
I'm
too
new
like
I'm.
Nobody
I
would
never
go
bother.
Somebody
that's
like
the
owner,
the
head
or
something
of
a
saying
so
I've
never
felt
that
way.
I
mean
like
Jay
was
saying,
everybody
is
super
nice
and
helpful,
and
they
never.
You
know,
there's
never
a
dumb
question
right,
but
I
still
feel
like.
Oh,
my
gosh
I
wouldn't
go
and
ask
someone.
That's
just
that's
ridiculous.
D
A
So
in
this
in
this
SIG
list,
each
one
of
these
groups
has
a
charter
and
in
the
Charter
they
have
the
top
of
the
root
of
what
we
call
a
sub-project
and
their
owners
file
listed.
So
if
you
can
figure
out
the
kind
of
the
tree
of
where
things
go,
and
you
have
a
few
cigs,
you
can
always
kind
of
look
here
as
a
kind
of
a
backwards
method
as
well.
I've
done
that
I've
used
this
before
myself.
A
Well,
I
can
clearly
see
kind
of
what
the
tree
looks
like
and
I
probably
can
take
a
guess
on
a
few
of
the
SIG's
or
what
they
would
be,
and
then
you
can
just
go
and
look
at
charters.
Turner's
are
awesome,
yay
charters,
all
right,
so
we
do
have
another
question
in
chat.
Actually
it
was
DMS
and
I
put
it
in
chat
and
they
want
to
know
how
they
can
help
fix
flaky
tests.
They
see,
they
say
we
see
flaky
tests,
but
does
that
mean
state
testing
owns
it?
How
do
they
find
out?
A
A
B
B
B
That
gets
it
out
of
the
critical
path,
and
then
you
link
to
a
couple
of
tools
that
might
help
you
chase
down
if
you're
looking
for
a
particular
plate
or
you're,
just
looking
to
be
like
helpful
of
the
most
like
painful
flake,
and
today,
this
flakes
latest
link
is
a
report
that
shows
for
this.
This
text
is
way
too
small
for
this
job.
The
pull
community
ETH
ECE
job.
B
These
are
the
top
ten
tests
that,
like
the
most
and
the
flake,
is
defined
as
the
test
has
both
passed
and
failed
against
the
same
commit,
even
though
nothing
has
changed,
and
so
network
should
set.
Tcp
closed.
Wait:
timeout
is
the
freakiest
thing,
so
I'm
just
going
to
copy
this
text
here
and
I'm
gonna
go
back
to
my
favorite
tool
of
all
time,
which
is
go
Cates,
so
I
realize
now
how
this
text
is
probably
makeable,
cocaine's
IO
triage.
B
B
For
example,
I
can
see
that
something
started
happening
around
the
middle
of
May
4th
or
between
May
4th
and
late
May,
4th
I,
guess
that
has
caused
a
new
failure.
Cluster
to
start
happening.
A
bunch
and
I
can
see
that
failure
cluster.
It
looks
to
be
basically
the
same
test
as
failing,
and
it
looks
like
it's
failing
across
a
bunch
of
different
chops.
I
can
use
these
spark
lines
to
see
like
Oh.
B
Actually,
you
know
what
it
turns
out:
they're,
a
bunch
of
different
tests
that
are
all
failing
in
this
particular
way
and
it
looks
like
it's
failing
across
a
couple:
different
jobs
and
then
I
can
click.
This
link
to
go
see
like
the
latest
example
of
the
job,
but
so
for
my
purposes,
talking
about.
What's
that,
flaky
is
tested
whose
network
should
set
TCP
closed,
wait
so
I'll
hit
that
and
now
it
looks
like
this
particular
error
seems
to
be
what's
happening
for
that
test
or
this
error
so
on
and
so
forth.
B
So
that
gives
me
some
insight
that
I
could
use
to
then
go
look
at
the
test
and
see
like
okay.
So
why
would
that
error
happen?
And
at
that
point
maybe
I
could
try
to
reproducing
the
test.
Failure
myself
if
I
didn't
have
access
to
a
cloud,
I
would
probably
try
reproducing
the
test
there
on
kind
which
is
kubernetes
in
dr.
which
I
forgot,
where
I
put
a
link
to
that.
B
I'm
not
say
exact
a
that
case.
The
AIA
will
get
you
there
and
this
would
tell
you
how
to
like
download
and
install
kind-
and
there
are
all
sorts
of
guides
here,
including
how
to
run
end-to-end
tests
against
kind.
If
you
can't
reproduce
it
against
kind,
I
kind
of
don't
know
what
to
tell
you
from
there,
but
definitely
it
would
be
helpful
to
you
open
an
issue
to
describe
what
troubleshooting
has
been
done
against
this
test
to
call
Italy,
thus
far
I
have
pardon.
Can
you
show
us
how
he
gets
the
test
yeah
so.
B
So
the
file
name
in
question
here
is
kubernetes
test
e
to
EQ
proxy.
So
we're
going
to
look
for
this
file
in
the
codebase
I.
Don't,
unfortunately,
have
a
link.
I
can
click
to
get
there
so
I'm
just
gonna
have
to
new
test
e
TV
network
to
proxies
so
I'm
going
to
test
ET
e
network
to
proxy.
And
what
long
did
it
say?
It
was
failing
at
2:08
so
down
here,
208.
So
if
the
failure
is
happening
here,
waiting
for
the
pods
to
get
ready
for
whatever
reason,
anyway
cool,
hopefully
that
is
helpful.
B
Fix
things
like
you
taste
fixing
flaky
tests
is
amazing
and
super
duper.
Incredibly
helpful
flakes
are
the
bane
of
our
existence.
They
are
definitely
what
prevent
us
from
merging
code
faster
than
you
could.
It
is
definitely
really
frustrating
when
I
submit
a
PR,
that's
like
a
one
line,
Docs
change
and
then
suddenly
there
are
a
bunch
of
random
test
failures
and
all
these
jobs
I've
never
heard
of
before
less
that
about
so
like.
If
you
don't
have
the
time
to
address
that,
because
I
recognize
not
everybody
does
that's
fine.
B
C
I
was
really
cool
and,
for
me,
part
of
what
was
really
close
when
you
showed
us
the
top
10
and
I'm
and
I'm
looking
at
the
line
for
one
of
those
being
like
that,
one
looks
like
that.
One
looks
like
something:
I
might
be
able
to
figure
out
like
that's
like
okay,
you
told
me
what's
like
that.
Top
10
shows
me
like
what
you
might
care
about
most
or
what
might?
C
A
C
That
was
really
cool
to
see
and
Aaron
like
I.
Imagine
like
so
you
know,
I
think
it's
no
I
think
it's
no
accident
that
Manik
and
I
have
both
talked
about
how
we've
had
you
know
early
successes
as
contributors
with
with
changing
you
know,
with
with
seeing
something
in
the
docks
and
wanting
to
change
it,
because
it
was
pretty
easy
and
you're
not
that
worried
about
really.
You
know
like
that.
C
If
we
wanted
to
try
to
contribute
to
fix
the
flaky
test,
is
there
anything
we
need
to
do
before,
just
like
grabbing
kind
or
grabbing
our
own
cloud,
cluster
and
and
building
and
testing
or
and
then
trying
to
fix
the
test?
Like?
Do
we
reach
out
to
somebody
who
have
to
join
sig
testing
like
what
we
have
to
do
if
we
want
to
go
fix
it
fast?
Thank.
C
B
Tried
to
put
a
little
one
of
my
pain
points
is
people
think
that
state
testing
implements
all
of
the
tests
and-
and
we
don't-
we
are
here
to
empower
other
people
to
write
whatever
tests
they
need
to
and
to
make
sure
that
they
get
actionable
results
from
those
tests.
But
we
often
don't
like
I,
said
I,
don't
understand
the
very
specific
business
logic
of
a
lot
of
kubernetes,
even
for
as
long
as
I've
been
on
this
project,
there
is
vast
amounts
of
it
that
I
do
not
comprehend.
So
it
comes
to
troubleshooting
a
specific
test.
B
I'm,
probably
just
as
good
at
this
as
the
rest
of
you
are
I'm.
Gonna
have
to
be
learning
a
lot
of
stuff
from
scratch.
So
if
I
do
you
need
some
domain
expertise
to
figure
out
like
what
is
expected?
Behavior
here,
I'm,
probably
gonna,
try
to
ask
questions
of
the
sig
in
question,
and
thankfully,
most
of
our
end-to-end
tests
have
the
Signum
embedded
within
them.
B
B
That
are
continuously
flaking.
They
tend
to
care
most
about
tests
and
jobs
that
live
on
the
release,
blocking
and
release
informing
test
grade
dashboards,
which
I
don't
think
I
had
time
to
show
test
grade
to
you,
but
those
are
often
where,
like
humans
might
be
more
prone
to
paying
attention
and
pinging
stuff.
So
having
a
dialogue
on
those
issues
is
helpful
and
then
maybe
having
an
ask
in
the
CI
signal,
chat,
inhuman,
any
slack
they
may
be
able
to
help
point
you
in
the
right
direction.
A
C
Other
the
other
thing
came
up
for
me
was
like
wait.
Aaron,
you
showed
me
some
cool
links
like,
but
how
do
I
find
them
myself
and
someone
who's
been
posting
them.
People
have
been
posting
them
into
the
slack
channel.
So
if
you're
watching
the
zoom
recording
of
this,
the
links
are
in
this.
The
I've
never
been
on.
This
show
that
it's
all
goes
away.
I'm,
sorry,
but
yeah
you're,
watching
the
zoom
recording
of
this
go
hit
the
slack
channel
they
get
the
links
for
all
the
stuff
people
been
talking
about.
There's.
A
A
All
right,
I'm,
looking
right
now,
I
think
that
might
have
been
it
for
our
questions
as
well.
Paris
did
you
want
to
ask
about
the
new
contributor
summit?
Yes,
thank
you.
I
was
like
I'm
trying
to
think
of
what
I
shelled
I
know
that
I
pushed
something
to
side.
Yes,
tell
me
tell
me
on
us
rather
tell
us
about
your
experience
with
new
contributor
workshop
and
for
folks
that
are
on
the
line
and
watching
who
have
no
idea
what
it
is.
A
D
Basically,
at
the
coop
con
right
at
the
communities,
conferences,
there's
some
a
ton
of
different
workshops
right
for
lots
of
stuff.
So
one
of
the
workshops
that
you
guys
found
at
Paris,
obviously
is
involved
with,
is
to
contribute,
contribute
at
workshops.
So
there
was
what
a
new
contributor
workshop
and
then
there
was
an
intermediate
I
think
so
it
was
well
I.
Think
was
all
it
was
like
a
day
zero.
Wasn't
it
I
think?
So?
Basically,
you
know
we
came
into
room
and
there's
I,
don't
even
know
like
over
a
hundred
people.
D
For
sure
I
mean
there
was
a
ton
of
people
in
the
workshop
and
I
think
this
area
did
the
intermediate
one,
and
you
know
we
had
an
intro.
You
know
get
to
sit
at
the
table
with
a
bunch
of
different
people
and,
as
I
was
sitting
at
people
with
some
like
Google
and
Amazon,
and
and
not
even
like
people
that
are
heavy
into.
You
know,
they've
already
done
this
right,
they're
intermediate
or
beginners
and
they're
just
getting
into
trying
to
learn,
and
even
people
like
one
person
was
a
project
manager
right,
not
someone.
D
You
would
typically
think,
like.
Oh
they're
gonna
go
and
be
a
contributor,
but
just
everyone
was
an
you
know
interested
in
getting
involved
right
in
Germany,
so
yeah.
So
we
had,
you
know
walking
through
opening
your
first
PR.
We
talked
about
the
different
SIG's
kind
of
going
through
some
stuff
into
a
ton
of
questions.
You
know
there
this
year
there
were
a
couple
technical
issues.
You
know
with
the
wireless
there,
unfortunately,
but
yeah
it
was.
D
It
was
a
really
positive
experience
that
it
was
very
nice
to
get
the
sweatshirt
I
thought
that
was
super
nice
I
didn't
expect
that
at
all
that
was
a
nice
surprise
and
honestly
just
getting
to
talk
with
the
other
people.
The
table
like
what
are
you
doing
with
kubernetes
how
you're
getting
about
like
hearing
their
stories
was
really
cool
and
it
really
it
gets.
You
really
motivated
I
think
to
go
in
and
go
forth
and
contribute
right.
I
think
that's
a
really
good
part
of
the
experience
too.
Oh
darn.
A
We
should
have
had
this
on
May
4
dang,
it
dang
it
I,
didn't
plan
this
right
that
for
the
first
Wednesday
always
kicks
us
anyway.
Money,
oh
yeah,
that's
awesome!
Thank
you!
So
much
for
attending
to
and
just
being
helpful
with
everyone
around
you.
It's
a
very
nice
peer
mentoring,
environment
and
thank
you
for
participating
in
that
all
right.
Well,
that
pretty
much
wraps
up
the
May
edition
of
meet
our
contributors,
I
usually
like
to
go
out
with
a
pretty
ambiguous
tip,
meaning
tip
for
either
new
or
aspiring
or
current
contributors.
A
Anything
that's
on
the
top
of
your
mind.
Right
now
that
you
want
contributors
to
know.
Like
I
said
it
can
be
ambiguous.
It
can
be
very
detailed.
Some
people,
like
Erin
in
the
past,
have
said
sake.
Testing
doesn't
earn
your
flaky
tests
things
like
things
like
that.
So
why
don't
you?
Somebody
go
first
and
kick
us
off
into
the
end
here:
any
tips,
tricks
or
advice
for
new
or
current
contributors.
C
Yeah
I
had
one
more
but
oh
yeah
issues,
pages
trolling
issues,
throwing
the
issues
pages,
trolling
that
as
Erin
was
showing
us
the
broken
tests.
You
know
the
flaky
tests
page,
you
know,
go
looking
for
stuff,
you
can
do
and
then
the
last
one
I
think
is
the
classic.
For
me.
Is
the
classic
open
source
scratch
your
own
itch
find
that
thing?
That's
you
know
find
that
thing
that
you're
interested
in
because
it's
either
annoying
to
you
or
you
have
a
vision
for
you
know
for
a
way
you
could
help.
C
So
the
third
party
security
on
a
working
group
is
is
absolutely
absolutely
absolutely
eager
for
help.
Sigilyph
is
a
good
place.
If
is
also
good
for
security
related
topics,
the
PFC
is
there
there.
If
you
have
something,
if
you
have
a
vulnerability
that
that,
if
you
have
a
vulnerability
report,
PSC
is
one
place.
The
bug
bounties
another
hack
come
join,
all
the
slack
channels
for
every
single
one
of
those
groups,
including
the
security.
Our
working
group
I
can't
wait
to
see
you
there.
A
D
Go
I'll
just
say:
I'm
I
posted
in
the
slack
channel
as
well.
I
always
use
the
labels
so
I'm,
like
you
know
what
I
want
to
try
and
do
something,
and
even
after
today,
I'm
like
I
need
to
contribute
more
I
need
to
do
something
so
I'm
already
looking
at
the
labels
for
a
good
first
issue
or
documentation
like
I,
have
done
a
first
issue,
but
still
you
know,
some
of
them
are
at
least
kind
of
more
entry
level.
D
If
you
will
so
go
use
those
labels,
they
are
super
helpful
and
truly
you
don't
have
to
be
this.
Like
super
knowledgeable,
developer,
you
know,
experience
is
up,
you
can
go,
read
the
docs
I
love
that
cheat
sheet.
They
contribute
sheet
that
you
just
share.
That's
awesome,
I
didn't
know
that
was
there,
you
know,
go
look,
there's
a
ton
of
stuff
out
there.
Just
just
take
a
look
and
give
it
a
shot.
You
know
what
you
have
to
lose.
That
is.
A
B
I
just
want
to
underscore
how
important
Docs
fixes
are
the
like.
How
understandable
and
well-written
and
complete
our
Docs
are
is
something
that
those
of
us
who
have
been
on
the
project
for
I
are
completely
blind
too,
like
we
just
don't
have
the
fresh
eyes
for
it
anymore.
So
that's
an
incredibly
valuable
thing
that
you
can
bring
to
the
table
as
a
new
contributor.
It's
something
that
many
of
us
don't
have
so
I
think
started
with
thought.
B
Fixins
is
a
totally
appropriate
place
to
start,
and
if
that's
all
you
do
that
scene,
that's
great
too,
like
seriously,
we
could
use
the
help
I'll
put
in
another
plug
for
the
kitchen
for
a
working
group.
So
that's
where
we
are
looking
for
ways
to
do
stand-up
and
manage
the
infrastructure
that
helps
run
the
kubernetes
project.
It
is
mostly
a
volunteer
effort
run
by
people
who
contribute
to
the
communities
project,
but
may
not
necessarily
have
a
great
amazing
operational
experience
of
running
stuff
on
kubernetes.
B
So
if
you're
out
there-
and
you
happen
to
like
you-
use
kubernetes
in
your
day
job,
so
you
know
how
to
like
run
things
and
manage
it
and
stuff.
We
could
really
use
your
help
or
expertise
and
again
from
a
perspective
of
dots
or
from
a
perspective
of
how
organized
things
are
just
sharing
like
what
you've
done
that
works
for
you.
It's
all
super
super
helpful
and
appreciated.