►
From YouTube: Kubernetes Meet Our Contributors 20181003
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.
See https://contributor.kubernetes.io/mentoring/meet-our-contributors/ for more information
A
Hi,
everyone
welcome
to
October
I,
can't
believe
it's
October
already
his
edition
of
meet
our
contributors
today
is
Wednesday
after
our
third,
my
name
is
Paris
Pittman
I'm,
a
community
manager
for
kubernetes
at
Google.
Today
we
have
a
lovely
esteemed
panelists
of
mentors
for
you,
the
majority
of
them
actually
have
a
University
of
Michigan
connection,
believe
it
or
not
so
U
of
M
is
taking
over
taking
over
today
in
some
weird
way,
of
course,
weird
way.
Is
it
like
the
weird
that
it's
common,
not
love?
A
You
love,
love,
you
all
you
again,
folks,
I
don't
want
to
get
any
view
of
em
tweets
at
me
or
anything
like
that.
Anyway,
this
is
a
mentors
on
demand
series.
We
constantly
hear
from
contributors
that
they
would
like
mentors.
That
is
a
very
resource,
heavy
initiative.
So
what
we're
doing
is
putting
contributors
on
the
line
for
an
hour
to
ask
any
questions
that
you
would
normally
have
for
a
mentor
things
like
how
do
I
get
started
or
I'm
an
approver
and
I'd
like
to
be
a
maintainer.
A
A
So
right
now
we
have
about
six
questions
queued
up
and
we
will
cut
the
section
short
today.
If
we
don't
have
any
more
so
it'll
give
some
folks
back
their
time,
all
right
and
lastly,
we
do
have
a
code
of
conduct.
That
means
we
all
like
to
treat
each
other
with
respect
on
any
communication
forum
we
have
and
right
now
we
are
fiddling
with
slack
Twitter,
zoom,
YouTube,
etc.
So
everybody
that's
on
any
of
those
channels,
please
be
respectful
to
each
other
and
please
be
awesome.
A
The
steering
committee
Edition
is
later
on
so
at
1
p.m.
Pacific.
A
p.m.
UTC
check
your
time
zone.
We
have
three
awesome
steering
committee
members
with
us
to
answer
your
governance,
related
questions
or
really
anything
because
they,
some
of
them,
do
know
everything.
Almost
we
have
Brandon
burns,
we
have
Aaron
quicken
Berger
and
we
have
Timothy
st.
Clair
on
with
us
at
one
o'clock
Pacific.
So
please
join
us
there.
All
right,
let's
go
right
into
intros,
for
our
mentors
I
will
go
left
to
right.
A
B
Hi,
my
name
is
Jeffrey
Sica
I,
currently
work
at
the
university
of
michigan,
advanced
research,
computing
technology
services.
I
facilitate
faculty
members,
doing
research
and
other
people
doing
research,
and
we
also
maintain
a
couple
kubernetes
clusters
here
that
we
let
researchers
consume
and
publish
services.
I
am
also
part
of
sidqin
Trebek's
and
sig
UI.
So
that's
kind
of
my
role
in
the
kubernetes
project.
C
D
My
name
is
Dan
Miceli,
I
alumni,
blue
I'm,
currently
working
for
Google
GE
and
pro
team,
but
I'm
mostly
working
for
community,
basically
like
everything
behind
your
car,
that's
why
my
car
gets
tested
and
how
it
gets
merged,
mostly
in
stick
testing,
but
also
part
of
the
country
backs
and
also
stick
release.
A
Thanks
then,
for
joining
today,
I
know
US
Pacific,
Coast
time,
folks
like
to
start
things
after
10
a.m.
and
for
us
it
is
7:40
a.m.
right
now.
So
we
are,
we
are
ready
for
breakfast
at
the
very
least,
alright
and
I'm
Steven
I
think
you're
joining
us
from
the
East
Coast
right.
So
your
your
day
is
already
begun.
A
B
E
Have
no
affiliation
with
the
University
of
Michigan
I
work
for
Red
Hat
right
now,
as
a
specialist
solutions
architect
for
the
openshift
Tiger
team,
so
I
sell
kubernetes
to
you
on
the
community
side.
I
am
the
product
management
chair
for
sick
I,
formerly
did
release
team
stuff
so
for
release
the
111
112
release
and
I'm
the
sick.
As
your
chair.
A
Also
and
thanks
for
all
your
help
with
future
and
past
releases,
so
it's
awesome
the
way
they
all
wrangle.
Folks
in
that,
especially
because
it's
a
lot
of
hard
work,
but
it
pays
off.
So
thank
you
so
much
for
for
all
your
work
with
the
release
team,
all
right.
So,
let's
get
right
into
the
first
question.
I
received
that
on
direct
message
this
morning,
what
the
heck
is
tied,
I've
been
hearing
and
reading
a
lot
about
it.
A
D
Answered
that
so,
if
you
don't
know
tied,
you
probably
know
something:
Cod
Simic
you
some
curious
was
something
that
managing
merge.
Your
PR
after
you
collect
like
LG
TM
approval
labels
and
all
your
test
passes,
but
we
have
a
concept
issue
as
the
cibecue,
for
example,
it
only
works
covenant.
It
only
works
for
communities,
communities,
which
means,
if
you
want
to
have
some
a
queue
on
another
communities,
repo
you
need
to
like
deploy
another
instance
and
also
like
rebooting.
It
is
super
stateful.
That's
why
we
migrated
to
tied
tied
as
a
tidy.
D
A
D
Anyone
opens
a
PR
under
their
PR
status
page.
They
will
see
like
hey
little
contacts,
they
hide
and
what's
going
on
with
tied.
That
means
is
your
PR
currently
able
to
merge,
being
tight
will
say:
hey
your
PR
k--
currently
cannot
merge
because
you
fail
this
required
test
or
your
PR
doesn't
have
a
led
em
label
and
we
have
a
so
pro
has
a
PR
dashboard.
If
you're
clicking
to
the
status,
you
will
see
like
exactly
what
your
PR
is
missing
or
it
can
be
merged
into
master
or
into
the
Hat.
A
E
Magic
if
tide
is
working
properly
and
all
of
the
the
wizardry
that
happens
on
the
test
and
foresight
is
going
well,
you
you
have
a
really
great
experience
in
terms
of
like
submitting
getting
reviews
for
ours,
so
tight.
It's
just
kind
of
the
thing
that
takes
a
batches,
takes
a
batch
of
submitted
and
and
merged
things,
or
rather,
and
washes
them
in
and
washes
them
out.
I
aaron
has
a
way
better
explanation,
but
yeah
I
mean
if,
if
everything
is
happening
well
on
the
test
in
prasad,
you
kind
of
kind.
A
Awesome
all
right,
let's
question
the
age-old
question
and
open
source
of
how
exactly
do
you
manage
your
time,
especially
when
it
comes
to
the
fact
that
I
think
I
can
speak
for
a
lot
of
us,
not
necessarily
all
of
us
on
this
panel,
but
I
know
that
a
lot
of
us
have
kubernetes
as
even
a
hobby
and
and
also
a
job,
some
some
component
of
kubernetes
anyway.
So
how
do
we
manage
time
when
things
like
your
hobbies
and
your
work
sort
of
blur
and
then
just
a
general?
How
do
you
manage
your
time.
B
So
I
tend
to
keep
just
checklists
of
everything
that
I
need
to
do
down
to
like
the
small
bite-sized
piece,
and
then
it
feels
really
satisfying
checking
them
off.
Even
if
it's
like
a
hobby,
I'll
break
down
like
a
pet
project
into
those
little
bite-sized
chunks.
So
I
can
kind
of
try
and
manage
my
time
between
that
and
other
things
like
housework
and
whatnot.
So
it
it
comes
down
to
just
for
me,
organizing
things
and
at
least
either
keeping
a
physical
checklist
or
a
mental
checklist.
E
So
I
get
a
chunk
of
my
day.
That's
dedicated
to
or
chunk
of
my
week
or
month,
that's
dedicated
specifically
to
community
evangelism
and
making
sure
I
mean
it.
It's
it's
great
because,
like
things
that
I
learned
from
the
community
I
take
back
to
my
team
and
things
that
I
learned
from
my
team
I
take
back
to
the
community.
So
managing
my
time,
wise
I,
think
urban
net
is
is
both
and
a
hobby
for
me.
So
I
I
will
pop
up
at
3:00
a.m.
and
go
oh
I.
Think
I
can
fix
this.
D
You
see
so
for
me,
I'm,
actually
pretty
badass
time
management
so
normally
keeps
my
email
open,
like
with
tap
to
me,
like
with
anything
assigned
to
me
UCC
to
me,
I
tend
to
reply
like
immediately
or
every
quickly,
or
also
reacts
to
strike
teams
a
promise
down
or
hey.
My
PR
is
not
merging.
Can
you
take
likewise
that
also
have
a
little
trick
whenever
I
don't
have
time
by
assigned
issue
to
Ben
who
is
like
typing
2x
faster
than
me.
A
C
It's
pretty
similar
to
Jeff,
but
that
really
shouldn't
come
as
any
surprise.
If
you
know
he
and
he
and
I
I
have
a
little
like
I
use.
Google
keep
and
I
just
have
like
a
list
of
all
the
tasks
and
things
like
that
and
I
just
don't
turn
through
them.
He
and
I.
We
don't
really
work
on
criminals
for
our
day
job.
It's
definitely
a
big
hobby
for
both
of
us.
A
All
right
and
the
meet
our
contributors
room
is
lighting
up
right
now,
with
questions,
I've
got
two
on
a
thread
and
then
we've
got
three
in
the
room.
First
question:
they
came
in
this
individual
knows
basic
golang
and
some
JavaScript
also
some
advanced
Python
and
intermediate
skills
on
shell.
Where
do
they
start
getting?
Where
do
they
start
getting
their
hands
dirty
with
kubernetes?
Where
do
they
start
getting?
What
do
they
start
contributing?
A
They
read
a
lot
of
detail
yesterday
and
end
up
spending
about
six
to
eight
hours
on
it,
but
at
the
end
of
it
they
still
feel
kind
of
clueless
as
far
as
where
they
actually
contribute
in
the
process.
They
also
found
a
few
bugs,
but
didn't
know
where
to
log
them
how
to
file
what
labels
to
use
and
so
on
what
is
either
your
suggestions
or
your
yeah
I
guess
just
suggestions
on
maybe
a
critical
path
for
this
individual
to
start
contributing
yeah.
E
So
I
can
I
can
say
for
sure,
I
think
a
lot
of
your
contributions
will
depend
on
where
your
interests
lie.
So
there
are
people
who
naturally
gravitate
toward
socks
or
testing
or
are
kubernetes
core
or
they're.
You
know
they're
working
on
a
specific
cloud
provider
and
they
want
to
contribute
the
cloud
provider
code
right,
so
I
would
say,
try
to
figure
out
where
your
interests
lie.
Exactly
it's
such
a
vast
project
that
we
have
an
opportunity
to
contribute
everywhere.
E
What
I
can
say
is
that
all
of
the
magic
that
that
son
was
talking
about
that's
infra,
that's
inferred,
I
think
is
a
really
great
way
to
contribute
back
to
the
project.
It's
a
lot
of
magic
gremlins
in
the
background,
but
it
helps
it
helps
the
velocity
of
the
overall
project.
If
you
contribute
their
Doc's
is
another
great
place
to
contribute,
because
this
is
essentially
a
lot
of
people's
ingress
point
for
the
project
so
being
able
to
read
good,
consistent,
technically
intense
dr.
D
Another
great
way
to
start
I
would
say
is
probably
look
for
help
wanted
label
most
of
them,
maybe
Steve
just
made
them.
So
those
are
two
issues
that
maintainer
think
example.
People,
like
me,
I
think
this
can
be
a
pretty
good
first
time
issue
for
a
new
country
that
it's
pretty
straight
forward
and
feel
free
just
to
send
the
send
us
a
PR
to
fixing
that
issue
or
add
this
new
feature.
D
E
C
Honestly
was
covered
pretty
well
one
of
the
best
ways
and
just
like
sort
of
learn
to
get
started
there.
The
computer
guide
in
the
community
repo-
and
there
was
a
great
video
from
Copenhagen
I'm,
the
new
contributor
workshop,
and
there
definitely
will
be
one
run
again
at
both
at
Shanghai
and
later
on.
In
Seattle.
A
Good
plug
good
plug
I
was
gonna.
Do
it?
If
you
didn't
do
it?
Yes,
there
is
a
new
contributor
workshop
in
Seattle
and
it
is
quickly
filling
up
y'all.
So
if
you
have
not
purchased
your
ticket
yet
for
the
contributor
summit
for
especially
for
the
new
contributor
workshop,
please
do
so
as
soon
as
possible.
It
will
sell
out.
But
to
this
individuals
question
there
is
a
cig
list,
cigs
or
special
interest
group.
A
That's
what
owns
the
code
in
kubernetes
and
if
you
have
a
lot
of
this
advanced
and
intermediate
skills
with
shell
and
some
go
that
I'm
sure
you
could
help
out
with
groups
like
test
them
for
who
deal
with
a
lot
of
automation
and
some
other
groups
as
well
and
then
to
capitalize
on
that
I
know.
A
lot
of
folks
will
join
multiple
SIG's
when
they're
first
getting
started,
especially
those
that
have
interests
they
have
interest
with.
A
So,
for
instance,
if
you're
interested
in
ipv6,
you
probably
should
join
SiC
networking
and
you
could
be
a
fly
on
the
wall
of
their
meetings
because
you
do
not
have
to
you
know
immediately
jump
into
a
meeting
and
start
adding
value
right
away.
You
can
see
kind
of
how
they
do
things.
What
their
inner
workings
is
like.
A
That's
very
important,
because
then
you
get
to
to
know
how
how
exactly
they
assign
work
and
then
also
some
of
our
special
interest
groups
in
the
beginning
of
their
meetings
will
even
say:
do
I
have
any
new
contributors
on
the
line.
Please
introduce
yourselves
because
that
will
also
establish
your
intent
and
you'll
gain
credibility
with
the
group,
and
then
they
can
start
sort
of
mentoring
you
on
an
unofficial
basis.
That's
really
how
it
happened.
Unofficially,
within
kubernetes.
A
It's
people
see
that
there's
that
there's
helpful
folks
out
there
that
are
willing
to
contribute
sort
of
certain
skills,
and
then
they
put
things
like
labels
out
there
like
what's
then
and
Steven
we're
talking
about
because
they
know
that
there's
a
pool
of
people
out
there
that
are
going
to
help
them
so
there's
a
good.
First
issue
label:
there's
a
Help
Wanted
label
and
then
always
comment
on
the
PR
and
say
that
I'd
like
to
do
this,
but
I
just
mean
some
help.
A
That's
just
kind
of
my
two
cents,
I
think,
but
when
I
first
owned
boarded
to
the
project,
I
know
I
joined
almost
every
se.
Gwich'in
is
it's
like
thirty
close,
like
thirty
plus
at
the
time
now
it's
like
forty
plus,
but
it
just
helped
me
kind
of
figure
out
like
where
gaps
are
where
holes
are
where
people
need
help
with
and
where
they
can
add
value
and
then
Steven
and
a
you
had
a
hand
raised
yeah.
E
So
I
I
just
wanted
to
note
that,
like
if
you
join
a
cig
meeting
or
some
some
event
or
something
like
don't
be
afraid
to
speak
up
and
say
hi,
we
are
all
really
really
friendly,
I,
think
I
think
and
we're
we're
happy
to
have
new
contributors
and
figure
out
how
to
kind
of
guide
you
on
that
path.
So
please
I
noticed
occasionally
some
people.
If
there
are
new
contributors,
they
may
be
silent
on
the
Signum
eating's,
but
you
don't
need
to
do
that.
Say.
Hi
say
what's
up,
ask
how
you
can
help.
Definitely.
A
Awesome
and
then
we
are
also
working
on
sort
of
a
non
code
guide
as
well.
So
if
you're,
if
you're
on
the
line
right
now
watching
us
or
listening
to
us,
just
know
that
we
are
putting
together
a
guide
that
will
give
tips
on
contributing
to
kubernetes
and
other
ways.
That's
not
necessarily
code,
because
there's
tons
of
us
that
do-
and
this
will
be
the
documentation
of
that
in
a
similar
question.
A
Someone
in
the
chat
also
asked
for
like
a
janitor
list
of
projects,
is
there
some
in
some
way
that
they
can
find
out
like
little
little
itty-bitty
things
that
need
work.
I
know
we
now
have
the
discuss
board,
but
does
anybody
want
to
add
to
that
outside
of
the
labels
for
help
wanted
and
good
first
issue?
There's.
C
Actually,
a
roll
board
I'll
discuss
now
to
where
you
can
like
cigs
and
groups,
can
let's
sort
of
close
request
for
you
know
looking
for
help
in
specific
areas,
or
you
know
if
you
have
a
certain
set
of
skills.
Like
you
mentioned,
you
know,
I
thought
that
post
that
there
and
know
they'll
check
in
every
once
in
a
while
and
in
like
pinging
about
it.
A
B
I
can
go
I,
guess,
oh
well,
no
one
else
jumped
up
so
the
ladder
goes
like
this.
You
can
just
start
contributing
and
you
don't
have
to
be
kubernetes
or
member.
Eventually,
after
a
certain
period
of
time,
you
can
apply
to
become
a
kubernetes
org
member.
That
requires
and
I'm
probably
the
worst
person
to
be
saying
this.
So
please
correct
me:
when
I'm
wrong,
you
need
to
current
people
in
owner's
files
to
vouch,
for
you,
I
think
to
become
an
organ
umber
or
is
that
higher
up?
So
it's
it's
members.
E
E
D
Can
easily
find
sponsors
when
you
find
your
when
you
open
up
here
and
find
your
reviewers
because
you're
most
likely
being
correcting,
was
our
reviewers
say
hey?
Can
you
fix
this
knit,
and
can
you
bike
shed
this
name
and
after
few
rounds
you
probably
get
along
or
not
with
your
reviewers,
and
you
only
apply
after
you
like
have
a
few
contributions,
so
you
probably
know
a
lot
of
people
within
that
sig
already.
A
Yep
and
usually
like
I
mentioned
previously,
with
the
word
intent
when
you're
introducing
yourself
to
people,
especially
at
sick
meetings,
or
what
have
you
and
you
are
a
new
contributor
or
even
a
current
contributor
to
current
contributors.
I
think
also
are
doing
this
well,
which
is
communicating
what
their
kind
of
career
path
and
intent
is
within
the
project.
But
once
you
declare
that
I
think
that's
when
people
start
kind
of
opening
up
and
saying
okay,
this
isn't
someone!
That's
just
gonna,
come
in
and
fix
like
a
period
on
our
documentation
or
something
like
that.
A
This
is
someone
that
wants
to
definitely
dig
in
and
contribute
more
with
us
and
then
you'll
start
to
find
that
your
sponsors
will
come
much
easier
when
you
say
I
have
the
intentions
of
becoming
a
member
of
the
kubernetes
organization,
and
then
folks
will
start
to
talk
to
you
about
that.
So
definitely
let
folks
know
who
you
are.
Why
you're
here,
what
you
like
about
kubernetes
and
that
really
starts
good
conversations,
because
then,
like
these
three
folks
found
out
there,
they
were
University
of
Michigan,
grads
and
now
they're
best
friends
for
life
all
right.
A
Well,
this
individual
wants
to
know
what
are
some
common
trends
that
you
see
as
reviewers
and
above
when
it
comes
to
either
PRS,
not
merging
or
getting
rejected.
So
what
are
some
things
that
you
can
tell
other
other
contributors
to
look
out
for
that?
You
feel
like
are
common
things
that
you
see
for
folks,
not
getting
PRS
merged.
E
So
I
think,
first
and
foremost,
if
you're
understand
the
scope
of
the
work
that
you're
going
to
do
and
decide
if
it's
big
in
scope
or
smaller
in
scope,
something
that
you
can
something
that
you
can
tackle
and
is
not.
You
know
it
doesn't
cause
undue
friction
on
the
project.
I
think
that
would
be
one
of
the
first
parts,
if
you
think
you're
going
to
be
tackling
something.
Larger,
definitely
speak
to
the
sig
right,
because,
like
these,
these
features,
roll
into,
like
an
enhancement,
will
roll
into
some
bigger
statement
of
work.
E
For
that
sake,
so,
if
it's
already
planned,
you
want
to
make
sure
that
you're
not
stepping
on
anyone's
toes
and
if
there
is
a
previous
design
proposal
or
kept
for
that
that
feature
that
you're
you're
you
want
to
bring
to
bear
it.
It's
under
it's
good
to
understand
like
what
people's
intent
was
in
designing
it
before
going
forward
with
it.
So
definitely
work
with
your
work
with
the
sake.
E
Work
with
like
Sen
was
saying
that
known
like
reviewers
and
approvers
that
you
already
have
relationships
with
before
you
decide
to
tackle
something
large
secondarily,
I
would
say
test
failing
test
failures
are
the
things
that
keep
keep
yours
from
from
merging
so
be
aware
of.
So
you
know
we
have
multiple
repos,
so
it's
not
just
it's
not
just
to
Connecticut
Burnett
is
it's
it's
community
and-
and
you
know
everything
everything
in
between
testing
for
cloud
providers.
Things
like
that
make
sure
you
understand
the
the
testing,
the
testing
structure
for
this
specific
repo
traits.
D
What's
yours,
yeah,
so
sorry,
SCA,
testing,
Berliner,
I,
would
say:
I've
seen
things
that
people
assign
me
a
giant
PR
without
any
contacts.
So
that's
something
s
a
reviewer,
I,
probably
don't
wanna,
see.
I
will
probably
ask
you
for
a
design
dog
before
you
like,
send
a
giant
change
or
at
least
open
an
issue
to
discuss
or
discuss
under
and
existing
issue.
D
E
A
A
B
D
C
Think,
especially
when
you
have
limited
sets
of
time,
this
might
be
up
from
an
honest
hunch.
You
can
actually
get
back
like
I,
don't
you
actually
dedicate
to
something
don't
take
on
something
bigger
than
you
really
should,
and
it
can
kind
of
like
you'll
really
want
to,
but
in
general
it's
better.
If
you
you
tackle
something,
you
know
you
can
actually
complete
and
work
on.
E
So
yeah
so
I
think
I
think
that
kind
of
why
we're
here
speaks
to
the
intent
being
a
maintainer
is
hard
or
being
anywhere
near
maintainer.
Maintainer
ship
is
hard
for
a
large
project
like
this,
and
the
only
way
that
we're
going
to
continue
to
succeed
is
if
we
multiplex
those
efforts
and
get
more
contributors
involved,
so
we're
hoping
that
we
can
build
us,
build
a
framework
for
contributors
to
get
involved
and
kind
of
push
them
up
to
to
approver
and
maintain
their
status
for
the
project
overall,
having
more
people
will
help
us.
A
Hey
definitely
and
I
think
having
more
people
who
are
reviewing
and
approving
will
also
help
us.
So
if
you
are
a
member
currently
right
now-
and
you
have
done
a
few
contributions-
and
you
feel
like
being
a
reviewer-
is
something
that
you
really
would
like
to
do.
Talk
to
the
technical
leads
of
the
cig
talk
to
people
in
the
owners
files.
Let
them
know
that
something
that
you'd
like
to
do,
because
if
they
know
that
you'd
like
to
do
it,
then
there
might
be
mentorship
opportunities.
Just
homegrown.
A
E
D
E
A
What
channels
do
you
all
use
to
feel
like
you
are
super
up-to-date
with
what's
going
on,
especially
with
what
you
need
specifically,
because
everybody
does
need
a
little
bit
something
different
from
project
as
far
as
communication
is
concerned.
So
what
channels
are
they
that
are
super
useful
to
folks
that
they
should
be
plugged
into.
E
So,
first
and
foremost,
I
I
slack
is
primarily
my
communication
mechanism.
Email
failing
that,
but
an
email
is
a
mostly
a
firehose,
I
think
learning
what
you
don't
want
to
learn
is
important
too.
So
there
is
too
much
information
going
around
so
understanding
how
to
filter
that
down
whether
it's
heat
using
email
filters
or
making
sure
that
slack
is
on
do
not
disturb
all
the
time.
E
So
I'll
just
read
off
some
of
the
channels
that
I'm
in
that
I
think
are
super
useful
right
now
in
flack
contributor
summit,
diversity,
Cates,
infra
team,
shake
architecture,
say
cash
or
say
cloud
provider
or
say
contrib,
X,
SiC,
docs,
say
p.m.
sake,
release
and
sake
testing.
Those
are
my
those
are
my
top
ones.
B
I'd
like
to
second
a
few
of
those
sigdoc
cig
release
and
cig
testing
from
a
general
point
of
view,
without
going
into
like
specific
what
you're
working
on
for
your
day
job
those
always
provide
a
lot
of
information
that
is
useful
both
in
the
state
of
the
project
and
if
there's
any
problems,
another
one
is
also
kubernetes
security
channel.
Oh.
A
E
E
All
of
the
things
that
I
mentioned
I
subscribe
to
their
mailing
lists
as
well,
depending
on
how
interested
I
am
day-to-day
I'm
a
filter
again
down
to
the
daily
digest,
and
then
once
you
start
seeing
yourself
really
really
involved
in
in
the
repos
day
to
day,
you
may
want
to
filter
figure
out
how
to
filter
your
github
notifications
as
well,
because
that's
a
crazy
firehose,
so
I
watch.
I
watch
k
community
of
repo
wise
I,
also
watched
the
futures
repo,
so
I
can
kind
of
understand
what
should
be
what
is
coming
down.
E
D
If
you
really
want
to
know
alike,
this
is
a
terrible
idea,
but
I
want
to
mention
because
I
tried
it
once.
If
you
want
to
really
want
to
know
like
everything
is
going
on
in
kubernetes
org,
you
can
subscribe
to
feed
about
good,
which
that's
a
group
feel
free
to
try
out
and
you'll
get.
Are
the
common
like
bit
about
react
to
each
PR.
D
Feel
about
is
a
robot
created
by
Eric
FINA.
Basically,
people
are
are
basically
asking
him
like
hey
my
PR
his
plate,
and
my
PR
has
already
got
LGD
Amanda
proves,
but
it's
not
merged
due
to
testing
things.
What
do
I
do
and
normally
they
asking
stick
testing,
because
it's
a
testing
failure,
so
someone
will
go
in
there
PRN
slash
retest
to
trigger
their
failed
test,
but
that
seems
to
happen
more
and
more
often,
and
so
first
thing.
First,
we
probably
need
to
deflate
our
tests
who
make
our
tests
better.
D
A
E
So
it's
not
my
first,
but
it
kind
of
led
I
everything
was
leading
to
kubernetes.
So
my
story
for
getting
more
involved
in
the
upstream
community
was
that
I
was
working
on
tectonic
at
Curless
and
there
were
some.
There
were
some
things
that
I
wanted
to
know
about.
Adjure
that
I
didn't
know
yet
or
didn't
exist,
either
in
the
terraform
side
or
the
cloud
provider
side.
So
I
kind
of
started
pushing
up
a
stack,
so
first
I
went
to
the
terraform
project
and
I
was
a
Kate.
It
doesn't
do
this
thing.
C
E
I'll,
try
that
but
I
still
needed
information
from
the
kubernetes
group,
so
I
started
hanging
out
and
say:
gosh
your
meetings
and
and
just
like
sucking
up
as
much
as
I
could
and
then
I
was
like.
Okay,
I
have
enough
tools
now
to
go
finish,
the
terraform
thing
and
then
add
it
to
tectonic
and
and
then
go
make
a
customer
have
a
right.
So
it
was
kind
of
this
nice
little
chain,
but
everything
was
leading
to
kubernetes
and
everything
kind
of
pushed
back
into
Guilford
stuff.
D
B
Yes,
oh
wow,
echo,
sorry,
we
do
a
lot
of
I
shouldn't,
say
a
lot,
but
a
bunch
of
the
development
we
do
in-house.
We
also
open
source,
but
I
mean
that's
like
specific
resources
and
containers
that
we
build
for
our
purposes.
We
open
source
and
people
can
pull
them
kubernetes.
The
kubernetes
is
definitely
the
like
largest
and
I
would
consider
like
first
big
open
source
project
that
I've
worked
on
the.
C
Other
thing
is,
we
tend
to
do
a
lot
of
like
other
research
software
engineering
projects,
but
those
tend
to
like
live
off
and
bucket.
There
places
that
aren't
nearly
as
open
as
discoverable
as
all
these
other
things,
but
you'll
find
them
in
like
a
bunch
of
different
HPC
centers,
and
things
like
that
today
is
by
far
the
biggest
and
most
public
project,
though.
A
Yeah
we
actually
asked
that
on
the
last
contributor
survey
that
we
did
and
I
did
peruse
the
raw
data
last
night
and
it
does
look
like
a
good
amount
of
our
respondents,
have
kubernetes
as
a
first-time
open
source
project,
so
I
think
that's
really
cool,
and
especially
since
kubernetes
is
so
large
and
I.
Think
it's
a
good
good
data
point
all
right,
and
then
we
have
a
debugging
tool
question.
So
we're
switching
context
completely.
B
For
me
personally,
one
of
the
biggest
value
ads
that
I
got
was
I
use,
visual
code
Microsoft
code,
and
it
has
a
slew
of
integrations,
including
it
checks
schema.
So
that
helps
it'll
actually
tell
you.
If,
like
you,
were
missing
something
that's
required
or
if
something's
wrong,
and
then
you
can
also
integrate
that
with
your
golang
environment
and
then
I
mean
from
there
it's
just
having
a
good
IDE.
D
So
one
thing
to
add
is
when
you
debugging,
like
été
test,
we
have
a
triage
dashboard
which
is
go
doc,
a
stylist
at
church.
You
can
basically,
when
you
see
your
IDI,
it
has
its
feeling
you
can
search
for.
Is
it
failing
a
crop?
It's
just
like
a
far
across
the
world?
Is
it
like?
I
introduced
the
failure,
or
it's
like
a
generic
flake
across
the
project,
it's
very
useful
when
we
actually
debugging
with
these
blocking
issues.
C
E
C
E
E
You
can
take
a
look
at
and
kind
of
understand
like
how
we're
building
the
containers
and
we're
running
certain
tests
for
those
containers
and
then
and
then
tearing
that
stuff
down
and
then
pushing
it
out
so
I
think
that's
one
good
resource
just
checking
the
hack
repo
for
for
each
of
the
respective
repos
that
you
look
at
I.
Think
a
really
good
debugging
tool
is
people
right
just
being
able
to
bounce
ideas
off
of
people
in
the
community.
You
often.
C
D
Also,
one
more
tip
is:
don't
be
shy.
You
probably
cannot
predict
like
what
this
change
will
rate
just
send
your
PR
and
as
long
as
I
mean
hinder
at
a
okay
to
test
label,
just
utilize,
the
eye
to
see
hey,
I
break
those
two
tests
and
you
can
give
a
public
good,
Maeterlinck,
probably
sick,
testing
or
other
six
say
hey.
Can
someone
help
me
to
figure
out
why
those
two
tests
is
failing?
Is
it
due
to
my
changes,
or
is
there
some
breakage
going
on.
E
So
that's
that
essentially
says
like
your
new
contributor,
so
you
have
to
sign
the
CLA
first
and
then,
and
then
after
that,
I
will
say
that
everyone
who
is
on
the
project-
that's
super
generous
with
marking
things
neat:
okay,
to
test
right,
which,
okay
to
test
the
okay
to
slash,
okay,
to
test
command
will
remove
the
need
to
okay
to
test
label,
and
that
will
cause
some
CIA
stuff
to
kick
off.
I
think
you
need
to
be.
E
A
We're
learning
together,
y'all,
we
are
learning
together.
Well,
that's
it!
That's
it
for
our
show.
Today
you
have
at
least
five
minutes
of
your
life
back
same
with
our
folks
that
are
watching
next
month
is
will
be
here
for
November.
If
anybody
out
there
is
interested
in
being
a
panelist
as
a
mentor.
Please
reach
out
to
me
on
slack
in
the
in
the
meet
our
contributors
channel
or
direct
message
me
and
then
our
next
addition
today,
just
as
a
reminder
is
that
1
p.m.
Pacific
a
p.m.
A
UTC,
and
that
is
our
steering
committee
Edition
and
yes,
you
can
ask
them.
While
your
test
is
flaking,
I
would
love
to
know
if
they
would
dig
into
that.
I
might
ask
myself
and
again
anything
all
things:
project,
governance,
related
PS.
We
have
a
steering
committee
election
going
on
and,
yes,
it
ends
in
a
few
hours.
If
you
have
not
voted,
please
do
so
and
that's
it
for
me
panelists.
Thank
you
so
much
if
you
could
stay
on
after
we
cut
the
stream.
That
would
be
awesome,
but
that's
it
for
us
today.