►
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.
For more information: https://github.com/kubernetes/community/blob/master/mentoring/meet-our-contributors.md
A
A
This
is
mentors
on
demand,
specifically
upstream
mentors
on
demand
and
that's
important
to
us,
because
we
like
to
grow
our
community,
and
that
includes
all
roles
in
our
membership.
Our
membership
is
located
at
our
community
repo.
If
you
are
interested,
we
can
link
that
later,
but
these
roles
are
things
like
just
basic
contributor,
member,
reviewer,
approver
or
sub
project
owner,
and
we
like
to
get
people
up
those
ladders.
A
This
is
the
best
way
to
do
that
by
answering
your
questions
in
order
for
you
to
continue
your
career
path
with
within
kubernetes
contributing,
as
always,
we
do
have
a
code
of
conduct
that
is
to
be
respectful
to
each
other.
That
is
on
all
of
our
communication
mediums.
So
this
is
zoom.
That's
includes
our
meet
our
contributor
slack
channel
where
you
answer
and
ask
questions
and
everything
along
those
lines.
A
Today
we
are
joined
by
two
awesome
steering
committee
members,
DIMMs
being
our
newest
one
Aaron
being
someone
that
was
just
free,
electives,
ASR
pre
Q
con
madness.
Special
Ivan
got
my
nails
done
for
the
occasion,
so
we
have
some
questions
that
are
queued
up
in
my
DMS
again.
If
you'd
like
to
ask
us
questions,
do
so
in
the
meet
our
contributor
slack
channel.
You
can
also
find
me
on
Twitter
and
DM
me
there.
If
you'd
rather
be
anonymous,
you
can
also
be
anonymous
in
the
flat
channel
as
well.
A
A
B
My
nickname
is
dimps,
I
have
a
longer
name
so
ping
me
later.
He
didn't
want
to
know
that.
So
I
am
I
worked
for
huawei
and
I
spend
you
know.
Cuban
editors
is
my
job
per
se.
I
spend
a
whole
lot
of
time
on
cuban
artists
in
various
six,
including
things
like
the
cloud
provider
stuff.
I'm
I
work
on
OpenStack
as
well,
so
there
is
a
lot
of
overlap
between
the
two.
So
that's
what
I
do
over
to
you?
Aaron.
C
Hello,
oh
I
am
Aaron
Berger,
also
known
as
Aaron
of
cig
beard.
I
have
been
involved
with
community
since,
before
it
went,
1.0,
I,
tofind
its
sake,
testing
I
am
an
active
participant
in
CID,
contributor,
experiencing
architecture,
sake,
release
and
generally
six
that
are
horizontal
or
cross-cutting
across
the
project.
C
They
I've
been
relatively
actively
involved
in
conformance
testing,
so
I've
popped
up
in
the
CN
CF
conformance
working
group,
so
his
dims
and
I
was
the
bit
actively
involved
in
kubernetes
releases
since
once
one
about
for
deleting
things
like
release,
notes
or
CI
signal
or
issue
triage.
Most
recently,
I
was
released,
lead
shadow,
which
surprised
means
I'm
gonna,
be
released,
lead
for
114
to
start
the
new
year.
A
B
Yeah
sorry,
so
the
main
thing
that
we've
been
working
on
is
are
the
charters
for
the
various
C
groups.
That
was
the
main
focus
we've
been
trying
to
see
if
we
could
wrap
it
up
by
cube
con,
but
I
think
we
still
have
a
few
things
left.
So
Charter
is
basically
for
each
cig.
They
write
down
what
they
would
like
to
do
and
how
they
would
like
to
do
it
and
who
are
the
people
and
what
are
the
processes,
and
you
know
how
they're
going
to
work
as
a
team.
B
What
are
the
sub
projects
and
things
like
that?
We
wanted
each
sig
to
document
what
they
do
and
how
they
want
to
do
it,
and
that
has
been
the
primary
focus.
They've
been
a
few
other
things
as
well
that
that
is
always
on
like
there
are
issues
around
licenses
that
we
work
on
a
little
bit.
We
are
probably
going
to
start
using
some
tools
to
publish
information
about
what
dependencies
that
we
draw
in
and
what
licenses
they
fall
under
and
things
like
that
as
well
Aaron.
What
else
did
we
do?
Thank.
C
You
for
giving
me
Hanukkah
look
at
our
agenda.
She
refused,
but
she
captured
the
bulk
of
it.
I
actually
had
scraped
through
our
progress
last
week.
Getting
ready
for
the
meeting
today,
so
sig
p.m.
is
basically
the
only
sake
left
to
have
have
yet
to
actually
draft
a
charter,
with
the
exception
of
cloud
SIG's
likes
to
sure
drafted
a
charter
before
we
had
this
canonical
template
that
she
described
but
and
then
sick,
GCP
and
Sega
up
and
stack
haven't
drafted
charters.
C
Yet
but
I
know
both
of
those
stakes
are
anticipating
some
kind
of
merging
or
folding
with
sig
cloud
provider
that
still
needs
to
be
kind
of
tossed
out.
So
we
definitely
focused
on
charters,
because
we've
looked
at
say
at
the
contributor
summit
that
you
know
hey.
We
finally
know
what
here
and
we
can
start
to
better
to
find
those
boundaries
and
how
sakes
should
interact
and
see
if
all
of
that
may
cents
I
think
we
are
also
supposed
to
be
putting
together.
C
C
Delegate
it
to
them
and
be
sort
of
the
guiding
you
know,
do
the
steering
instead
of
the
implementation,
because
many
of
us
are
so
actively
involved
in
so
many
areas
of
the
project
that
relying
on
us
is
the
the
critical
path
is,
is
doomed
to
bottom
lacking,
so
yeah
I
think
that's
about
the
bulk
of
it,
though
there
have
been
two
working
groups
that
have
come
at
the
steering
committee,
one
related
to
the
migration
infrastructure
from
Google
to
the
CNC
F
and
another
one
related
to
what
does
LTS
even
mean?
Do
we
want
to
LTS?
C
C
It's
the
committee
steering
repo
and
we
have
a
project
in
there
and
that's
just
the
steer,
Middies
backlog.
So
every
meeting
we
go
through
that
board
and
we
kind
of
go
in
reverse
order.
You
know
what's
blocked.
Why
is
it
blocked?
Give
me
unblock
at
this
time
what's
in
progress
and
then
a
backlog
which
was
roughly
prioritized,
but
it's
been
kind
of
shuffled
around.
C
So
there's
that
and
then
yes,
the
state
architecture
also
has
a
tracking
board
under
kubernetes
SIG's,
slash
architecture,
tracking
I.
Guess
we
bring
that
up,
because
the
steering
committee
really
shouldn't
be
involved
in
the
technical
decisions
that
guide
the
project.
We
are
more
of
the
opinion
that
state
architecture
should
be
the
forum
for
those
discussions,
but
if
there
is
disagreement
that
cannot
possibly
be
resolved
within
that
sig.
The
steering
committee
is
the
place,
for
you
know
like
escalation
of
last
resort,
right.
B
So,
in
general,
it's
we
are
pushing
down
the
decision
making
process
to
like
the
six
and
the
working
groups
and
the
six
push
it
down
to
their
sub
projects
and
and
when
things
need
to
be
bubbled
back
up,
then
they
can
be
bubble
back
up
to
the
steering
committee.
If
there
is
issues
around
things
or
you
know
things
not
happening
and.
B
C
C
We
really
want
to
make
sure
a
sig
has
gone
through
a
good
faith
effort
to
try
and
resolve
the
situation
internally
before
they
escalate
it
to
steering,
and
then
at
that
point
we
would
prefer
to
have
the
discussion
happen
publicly
on
the
steering
mailing
list.
We
do
have
a
private
mailing
list,
but
it's
more
for
topics
that
are
sensitive
in
nature
sake
violations,
although
really
those
should
be
going
to
the
code
of
conduct
committee
issues
that
may
have
to
do
with
security
embargo,
those
or
other
things
of
that
nature.
C
So
if
you're
not
sure-
and
you
want
to
keep
it
quiet-
you're
free
to
email,
the
privates
steering
private
email
address,
but
we
we
may
choose
to
take
it
public.
If
we
feel
like
that's
the
more
appropriate
forum
and
I
think
the
resolution
we
would
try
to
reach
would
not
necessarily
be
to
make
our
own
decision
but
to
try
and
drive
consensus
and
push
back
down
once
we
found
a
way
to
make
consensus.
A
C
A
B
I
think
I
learn
more
in
the
face-to-face
meeting
in
Seattle
and
my
main
concern
would
be
to
somehow
get
brain
dumps
from
various
people
who
have
been
active
for
a
really
long
time
in
the
steering
committee
and
elsewhere,
because
mainly
because
the
steering
committee
is
right
now
13
people
and
we
are
going
to
go
down
to
7
next
year,
so
I
think
we
need
to
figure
out
a
way
to
capture
whatever
we
can.
So
we
don't.
B
C
Yes,
certainly
well
over
there
in
person,
I'm
sure
we'll
get
a
lot
of
feedback
on
what
people's
needs
are
from
the
project.
I
think
the
steering
committee
was
put
together
last
year
with
a
set
of
clear
gaps
that
needed
to
be
filled,
and
it
could
be
that
some
of
those
are
now
already
filled.
It's
important
to
be
filled
so
I'd
like
to
I
think
between
the
run
up
to
cube
con
and
the
holidays.
It's
a
good
time
to
kind
of
step
back
and
rethink
what
it
is
that
we're
doing.
C
I
think
his
point
about
the
committee.
Reducing
in
by
nearly
half
is
a
very
valid
one.
We
need
to
appreciate
what
our
velocity
has
been
and
find
ways
to
maintain
that,
with
even
fewer
people,
I'm
sure
that
tribal
and
institutional
knowledge,
that's
still
wrapped
up
in
the
body
of
13.
That
could
stand
to
be
documented
and
meet.
C
I
personally
feel
like
there's
some
vestigial
stuff
or
final
cleanup
and
wrap-up
of
some
of
the
six
and
working
groups
that
I
think
if
we
cleaned
it
up
would
provide
a
better
pattern
for
people
to
follow
or
a
cleaner,
more
well
understood
framework.
When
I
say
that
I'm
talking
about
the
idea
that
we
have
said
repeatedly,
that
working
groups
are
supposed
to
be
temporary
and
ephemeral
in
nature
that
disband
once
their
stated
goals
complete
and
yet
we
seem
to
have
many
working
groups
that
have
remained
around
in
perpetuity
and
then
I
alluded
to
earlier.
C
How
there's
there
are
many,
many
different
SIG's
for
individual
clouds,
where
maybe
it
makes
more
sense
to
have
them
folded
under
sick
cloud
provider
as
some
kind
of
sub
project,
or
something
in
a
way
that
doesn't
make
them
feel
like
they've
lost
any
decision-making
power.
But
that
also
makes
it
much
clearer
for
end-users
to
understand
which
part
of
the
project
do
they
want
to
engage
with
when
they
want
to
accomplish
thing
X,
or
they
have
a
problem
with
thing.
C
B
The
other
thing
I
want
to
you
know
peek
into,
is
also
the
health
of
the
different
projects.
You
know
there
have
been
some
concerns
about
some
projects.
You
know
the
loss
either
it's
the
velocity
or
the
security
posture,
or
things
like
that.
So
I
would
like
to
you
know,
look
into
that
as
well,
since
we
are
a
mono
rip,
it's
hard
to
actually
see
what
everybody
does
as
well,
so
it
would,
it
would
make
sense
for
us
to
you
know,
figure
out
a
better
way
to
see
no
projects.
Health.
A
B
C
C
We
generally
delegate
all
of
that
to
the
project
security
team.
Then
they
have
their
own
operating
policies
where
we're
trying
to
decide
whether
or
not
team
is
the
right
word
for
that
particular
entity.
Since
this
project
has
committees
and
sakes
and
working
groups,
maybe
we
want
to
find
a
way
to
call
them
one
of
those
things.
Instead
of
this
special
one-off,
they
have
some
pretty
good
vetting
policies
to
make
sure
that
people
of
appropriate
trust
levels
are
in
that
team.
C
They
have
mandated
that
every
single
repository
across
the
project
has
a
list
of
people
who
can
be
trusted
as
security
contacts
for
the
first
point
of
escalation
and
they've
generally
been
very
rock-solid
and
nothing
but
professional
speaking
with
my
released
hat
on
so
my
sig
testing,
slash
coworker,
awesome
state
testing.
You
had
on
many
hats.
C
Generally
speaking,
we
need
to
quiet
the
cues
for
a
little
while
make
sure
everything
is
stable,
so
that
releases
can
be
cut,
and
then
we
can
allow
changes
to
tool
and
again
and
we
kind
of
have
to
be
quiet
while
that
happens,
so
the
fix
for
this
was
introduced
well
well
before
we
were
made
aware
of
the
security
issue,
but
then
we
needed
to
become
involved
once
it
turned
to
rolling
this
out
at
the
appropriate
time.
I
personally
was
really
happy
with
the
way
that
whole
process
worked.
C
It's
actually
not
super
clear
to
me
how
well
it's
been
perceived
outside
of
the
little
bubble
within
which
I
operate.
I
know
there
was
some
ZDNet
article
that
sounded
super
scary,
but,
from
my
perspective,
I
feel
like
it
was
appropriately
fixed
and
triaged
and
the
side
effects
of
it
were
made
pretty
well
known,
and
it
was
back
ported
to
all
of
the
releases
that
we
support.
According
to
our
documented
support
policy,
so
yeah,
hopefully
James
do
you
have
anything
to
fill
in
from
there.
B
Yeah
I
wanted
to
bring
up
a
couple
of
things
here.
One
is
if
you
are
in
a
company
where
you
need
to
be
aware
of
these
things
earlier,
because
you
are
serving
other
customers
who
use
your
product
that
kind
of
stuff.
Then
there
is
a
male
enlist.
We
do
have
a
pub
we
have.
We
have
published
a
security
release
process
I
threw
that
link
on
to
the
meat
our
contributors
channel.
So
please
go
take
a
look
at
that.
B
It
has
information
on
how
you
would
join
one
of
these
distributed
private
mailing
lists
for
this
kind
of
information.
The
other
thing
I
would
like
to
point
out
is:
there
is
still
active
discussion
going
on
in
a
few
of
github
issues,
especially
people
worried
about
exactly
what
this
means.
How
do
what
do
they
need
to
switch
off?
How
do
they
figure
out
from
the
logs?
B
How
do
they
look
at
their
own
environment
and
see
if
they
are
vulnerable
or
not
art,
so
things
like
that
there
are
several
issues
and
Jordan
is
actually
documenting
quite
a
bit
of
stuff.
Let
me
get
you
the
issue
number,
it's
seven,
one,
six,
seven
one!
So
please
go
look
at
that
issue
and
no,
no,
not
that
one.
Let
me
find
out
the
correct
one:
okay,
it
is
let's
see
if
this
is
the
right
one,
seven
one
four
one,
one
yeah,
that's
the
one!
B
So
this
morning,
Jordan
added
a
simple
cube:
CTL
command,
which
will
tell
you
whether
you
are
running
any
of
the
aggregated
API
servers,
and
if
you
are,
then
you
are
definitely
vulnerable.
Even
if
you're
not
running
one
of
those
services,
there
is
another
auerbach
related
stuff
which
is
documented
in
seven
one,
four
one
one.
So
please
go
read
that
and
if
you
are
still
confused,
then
come
to
the
Cuban,
it
is
slack.
There
is
a
Cuban
artist.
Security
Channel
come
talk
to
us.
There
hope
that
helps
back
to
Paris.
That's.
A
Good
and
it
looks
like
brendan
actually
just
joined
us
as
well
I'll,
let
him
get
settled
in
and
we
can
do
a
quick
intro
for
Brendan
and
get
him
in
the
loop
here
alright.
So
that
brings
us
to
the
next
happening
of
this
week,
which
I
feel
like
this
week.
It's
only
Wednesday
and
we've
had
release.
We've
had
a
security
incident
and
we're
prepping
for
cube
con.
So
it's,
but
actually
it
very
smoothly.
A
C
Oh
I,
don't
sure.
Okay,
so
you've
probably
heard
this
stuff
before
but
I'm
happy
to
see
that
Canadian,
my
GA
during
this
release
and
I'm
also
happy
to
see
we
got
CSI
storage
drivers
GA
at
least
the
out
of
treat
ones
and
that
the
interface
for
CSI
went
of
window.
So
it's
stable
enough
that
the
next
steps
are
to
begin
hoarding
the
entry
storage
drivers
to
out
of
tree,
thus
making
the
core
of
communities
smaller.
I
love
the
leading
things.
C
It's
great
I,
also
love
putting
external
repos
on
the
same
footing
as
functionality
that
is
core
to
kubernetes.
So
I'm
really
happy
that
we
are
headed
along
that
path.
I
do
think
the
release
overall
went
relatively
smoothly.
This
was
as
it
was,
a
shortened
cycle
and
we
were
aggressive
about
reminding
people
of
that
act.
Early
and
often
known
and
people
paid
attention
to
that.
That
I
really
appreciate
everyone's
responsiveness.
C
There
I
do
you
think
we
had
one
kerfuffle
in
the
scope
of
what
it
meant
for
windows,
containers
going
GA
to
be
considered
beta
or
stable
or
whatever,
and
while
I'm
not
super
thrilled
at
the
bumpiness
of
that
process.
I
think
it
triggered
some
extraordinarily
necessary
conversation
and
revealed
a
number
of
perhaps
undocumented
assumptions
that
really
need
to
be
written
down.
C
So
personally,
I
plan
on
taking
carrying
that
conversation
forward
to
try
and
drive
a
little
more
of
a
formal,
documented
process
for
how
we
graduate
things
between
the
different
phases
and
what
level
of
scrutiny
or
technical
review
is
required
for
features
to
actually
land
in
a
given
release
as
part
of
the
114
release
cycle.
So,
even
though
it
was
a
bumping
right,
there,
I
think
it
was
like
is
really
great
conversation
to
have,
and
finally,
just
I
guess,
Tooting.
C
My
own
horn
here
I'm
happy
that
the
community
agreed
that
it
did
not
make
sense
for
a
hosted
version
of
kubernetes.
That's
not
under
community
control
to
block
the
release
of
kubernetes,
and
so
we
collectively
agreed
that,
while
it
may
be
useful
signal
to
see
how
kubernetes
describing
on
gke
it's
not
something
that
should
block
the
open
source
version
of
communities
from
going
out
the
door
and
that
we're
now
going
to
be
making
continued
progress
on
refining
what
it
means
to
be
able
to
block
kubernetes.
C
B
The
only
other
notable
stuff
you
missed
was
the
coldly
honest
one.
We've
been
marching
towards
cody,
honest
being
the
default
DNS
server
for
Cuba
notice,
I
think
that's!
Finally,
wrapped
up,
we
had
a
few
hiccups
in
112,
but
then
everything
got
wrapped
up
in
113.
Then
please
use
Kody
Ana's
switch
over
from
cube
DNS.
B
If
you
haven't
already-
and
you
know
start
using
that
other
than
that
so
relating
to
the
Windows
stuff
I
think
it
uncovered
a
few
more
things
that
we
got
to
talk
about
conformance
and
what
it
means
especially
around
if
we
need
to
have
profiles
and
what
do
profiles
mean
if
at
all,
so
that
is
another
one
of
the
tough
conversations
we
are
going
to
have
in
Seattle
I
believe
there
is
a
meeting
on
Thursday
if
you're
interested.
Please
show
up
we're
going
to
talk
about
the
current
state
of
the
performance.
B
B
Privilege
is
not
a
lot
for
example,
or
or
windows
for
that
matter,
and
how
do
we
bring
all
those
aspects
into
the
conformance
testing
while
still
preserving
the
you
know
the
the
importance
of
conformance
right
now,
because
you
know
we
have
to
be
able
that's
only
hard
stick
that
we
have
right
now
and
we
have
so
many
distributions,
and
so
many
hosted
versions
of
human
it
is,
it
would
be.
Hot
conformance
is
the
only
thing
that
we
that
are
standing
between
us
and
chaos
at
this
point,
so
we
need
to
stand
strengthened.
A
E
Yeah
I
mean
I
was
sort
of
seconds.
A
discussion
about
Windows
I
think
it
goes
to
show
for
anyone.
Who's
ever
been
frustrated
by
how
the
coronated
process
works.
I
think
that
the
windows
thing
shows
that
effectively
everybody
no
matter
how
involved
in
the
project
you
are,
can
get
seriously
frustrated
by
how
the
process
works
and,
and
we
try
and
you
know
we
try
and
learn
and
make
these
things
better
and
so
I
guess
that's
the
most
important
thing
is
every
time
you
feel
frustrated.
E
Make
sure
that
somebody
is
learning
from
what
you're
frustrated
by
and
I
know.
Paris
is
a
lot
of
work
to
the
contribute,
their
experience
and
others
to
make
it
better.
So
that's
what
I,
that's
all
that's
all
I
would
say.
Is
that,
like
we
are
all
sort
of
trying
to
do
a
continuous
improvement
here
and
and
we
uncover
generally,
whenever
there
are
these
things
that
happen.
E
We
uncover
a
lot
of
places
where
we
had
assumptions
and
we
didn't
write
something
down
and
it
turns
out
that
different
people's
assumptions
were
different,
and
so
that's
that's
always
good
to
learn
and
clarifies
I'm
excited
to
see
the
work
that
we're
gonna
do
there
and
I
do
think.
There
are
some
interesting
conversations
that
we
deferred
that
we
realize
before
any
more
around
profiles
and
things
like
that.
E
F
B
E
Yeah
I
think
one
of
the
challenges
we
face
in
the
project
in
general
is
there's
a
lot
of
goalposts
moving.
That
happens
because
there's
a
lot
of
people
who
care
but
are
busy
and
they
come
in
at
different
times
and
I-
think
that's
that's
been
a
problem
forever
and
I.
Don't
know
that
we've
never
really
effectively
solved
it,
but
that's
probably
something
that
we
should
think
about
is
how
do
we
avoid
giving
everybody
a
sense
of
the
goalposts
to
keep
moving,
and
it
was
one
other
thing:
I
want
to
clarify
about
what
what
Aaron
said.
E
Currently,
what
we're
moving
towards
is
a
world
where
effectively,
if
you
can't
reproduce
it,
it
can't
block
kubernetes
really.
So
we
want
to
really
be
in
a
world
where
anybody
in
the
community
can,
if
they
have
a
bug,
can
reproduce
it
and
fix
it
so
that
you
know
they
can't.
You
can't
be
in
a
situation
where
you
have
a
PR
I
really
want
to
urge
that
you
can't
reproduce
the
bug,
that's
in
DKA
or
aks,
or
you
know
whatever
it
happens
to
be,
because
you
don't
have
access.
E
That
is
the
structure,
so
I
think
that's
a
really
important
milestone
for
a
project
similar
I
think
actually
to
the
work
that
we're
doing
and
DIMMs
assembly
involved
here
in
lifting
the
call
the
terminated
infrastructure
to
be
things
that
are
totally
D&D
and
CNCs
controlled.
Those
are
an
important
milestone,
basically
breaking
down
barriers
to
anybody
else.
A
One
of
the
contributors
would
like
to
know:
what's
something
that
the
average
contributor,
meaning
somebody
that's
not
necessarily
in
an
owner's
file
but
they're
still,
you
know,
maybe
casually
are
a
little
bit
more
than
casually
contributing
at
this
point.
What
do
they
need
to
know
about
the
steering
committee
and,
in
the
same
breath,
what
do
they
really
need
to
know
where
some
takeaways
that
they
need
to
know
about
our
governance
model?
That's
important
to
them
as
this
type
of
contributor
or
like?
A
E
E
I,
don't
know
if
necessarily
that
I
want
to
tell
everything
using
agree
that
they
should
aspire
to.
You
know
I,
think
it's
any
great.
If
you
have
a
community
member,
can
most
users
give
it
anything
contribute
you
know
an
hour
every
month
or
two
hours
every
month,
I
think
that's
great
I
wouldn't
say
I
what
we
want
to
make
sure
that
it's
possible.
Obviously,
but
I,
don't
know
that
we
want
to
drive
everybody
there.
C
I
think
I
would
agree
with
both
of
them,
but
I
don't
want
to
make
the
steering
committee
sound
super
unattractive,
I
do
think
I
couldn't
yeah
I.
Think
brendan,
summed
it
up
perfectly
that
our
our
job
is
to
remain
invisible,
because
if
we've
done
it
perfectly,
you
should
have
no
authority,
because
everybody
else
already
knows
what
authority
they
have,
and
that
is
sufficient
authority
to
drag
the
project
forward.
C
I
think
the
biggest
challenge
that
we
face
is
deciding
when
it
is
more
appropriate
to
take
the
pragmatic
solution
to
solve
today's
instance
of
the
problem
versus
trying
to
defend
against
inappropriate
so
any
instances
of
the
class
of
the
problem
right
there
too
often,
we
can
be
prone
to
bike
shedding
or
future
tripping.
Thinking
like
what
happens
if
people
misinterpret
this
or
feel
that
they
can
distort
or
contort
this
and
I
think
it's
it's
important
to
recognize.
C
E
And
I
think
that's
a
good
point
and
I
in
a
second
kind
of
maybe
a
little
too
slipped
in
saying
we
should.
You
should
know
that
we
exist.
I.
Do
think
that
there's
a
role
for
thinking
about
the
future
and
and
so
like
I-
think
the
steering
committee
is
sort
of
uniquely
positioned
to
think
about
problems
for
the
project
writ
large
or
to
think
about
things
that
aren't
necessarily
pressing
problems
now,
but
we
could
tell
will
be
problems
in
my
book,
so
you
know
just
as
a
concrete
example.
E
The
the
nodejs
dependency
stuff
really
freaks
me
out
right.
I
we're
now
responsible
for
building
and
shipping
these
binaries
that
people
put
on
mission-critical
machines
all
over
the
world.
I
think
we
need
to
need
to
be
careful
with
that
responsibility
and-
and
I
think
we
should
do
more-
we
need
to
do
more
there.
So
that's
the
kind
of
stuff
I
think
that's
during
committee.
We
start
to
think
about,
and
then
hopefully
we
figure
out
who
the
right
people
are
to
delegate.
B
Right
so
the
another
thing
that
I
would
add
here
is
you
need
to
know
who
the
current
set
of
13
people
are,
and
so,
if
there
is
any
ever
any
issue
you
you
can
at
least
approach
some
of
us.
So
you
should
at
least
know
who
you
have
elected
to
the
body,
since
this
is
an
elected
position
so
and
please
make
sure
that
you
can
vote
in
the
next
election
and
make
sure
that
you're
eligible
to
vote
because
there's
a
criteria
for
you
know
getting
vote
as
well.
One.
C
I
was
just
gonna
unpack
the
nodejs
dependency
thing,
because
I've
seen
a
Brendan
of
her
to
use
that
shorthand
a
couple
of
times,
I'm,
not
sure.
If
everybody
knows
what
that
implies,
there
was
a
malicious
actor
who
patched
in
sort
of
a
backdoor
to
some
random,
no
js'
library,
and
then
they
sometime
later
they
removed
it.
And
so,
if
you
went
to
look
at
the
repo,
you
didn't
notice
that
there
was
a
backdoor
there,
but
there
were
many
people
who
had
a
specific
version
of
a
nodejs
and
it's
he
pulled
into
their
tree.
C
That
did
have
that
backdoor.
So,
basically,
as
a
project,
you
need
to
take
full
responsibility
for
a
thorough
on
it
and
review
of
every
single
third-party
dependencies
visited
or
not
that
we
end
up
pulling
into
the
kubernetes
codebase.
And
so
this
is
why
it's
really
important
that
we,
you
know
we're
starting
kind
of
from
the
licensing
perspective,
is
the
appropriate
license
involved
in
all
of
our
dependencies.
But
then
we
need
to
further
really
consider,
what's
the
appropriate
level
of
review
necessary
to
pull
in
updates
to
our
dependencies.
C
We've
often
encountered
times
where
people
will
update
a
dependency
and
vendor.
Just
that's
like
there's
a
newer
version
out
there,
let's
update
to
the
latest
version
and
we're
in
maybe
kind
of
disinclined
to
do
that
unless
there's
a
good
reason
to
do
that,
especially
now
that
we
should
consider,
maybe
somebody
needs
to
go
and
actually
review
the
code
that
changed
with
the
fine-tooth
comb
to
make
sure
that
no,
you
know
sneaky
backdoors
are
finding
their
way
into
our
code
base.
As
ultimately,
even
somebody
else
wrote
the
code.
C
B
Right,
let
me
add
one
so
we
had
this
major
discussion
about.
Can
we
blindly
ask
people
to
submit
dependency
updates
and
then
we
went
back
and
forth
in
several
issues
and
PRS
and
then
B
V
and
we
ended
up
writing
down
a
list
of
things
that
would
that
needs
to
happen
for
a
dependency
to
be
updated.
So,
for
example,
we
said
that
is
it
adding?
B
Is
it
changing
stuff
to
make
it
better?
If
it
is,
then,
are
there
more
test
cases
the
most
more
test
coverage?
You
know
there
are
several
criteria
that
we
came
up
with.
We
have
listed
this
down
in
the
same
same
place
where
we
have
the
instructions
for
updating
the
dependencies.
So
if
you
want
to
update
a
dependency-
because
you
are
the
dependency
that
we
have
in
KK
is
old
and
you
need
a
new
dependency,
you
know
login
issue
come
talk
to
us
and
then
we'll
figure
out
the
best
way
forward.
A
All
right
and
I
did
follow
up
with
Justin's
question
and
asking
him
if
he
had
any
follow-ups,
but
I
think
we
are
good
to
go
there.
We
had
a
few
questions,
come
in
specifically
about
Q
Khan
and
we
have
like
I'd,
say
a
little
bit
more
than
ten
minutes
left,
so
I'm
gonna
try
to
combine
some
of
these
questions
as
they're
similar
all
right.
One
contributor
says
that
they
feel
like
they
are
missing
out
on
serious
networking
opportunities
with
other
contributors.
A
They
want
to
somehow
get
plugged
into
face-to-face
I
suggested
meetup
calm,
but
they
were
also
just
yes
about
you
specifically.
Are
there
other
face-to-face
kubernetes
events
that
you
go
to
through
out
the
year,
especially
locally
in
your
communities?
And
can
you
talk
a
little
bit
about
the
other
opportunities
that
you
see
for
face-to-face
meetings
with
contributors.
C
So
personally,
just
at
Kuk
on
any
of
the.
So
if
you're,
not
fortunate
enough
to
be
able
to
make
the
contributor
I
would
encourage
you
to
attend
any
of
the
sake
talks
for
a
sake
that
you're
interested
in
that
you
know,
I
mentioned
up
top
the
sinks
that
I'm
involved
in
you'll
generally
find
on
that
those
those
talks
as
well
either
giving
them
or
helping
out
those
who
are
giving
them
beyond
that.
C
I
find,
sadly,
that
I'm
not
really
is
able
to
go
to
kubernetes
meetups
for
local
meetups
in
the
Seattle
area,
as
I
once
was
able
to
so
happy
to
make
myself
as
available
as
possible
on
slack
and
have
a
remote
conversation
via
zoom
or
whatever.
If
you
need
to
have
a
higher
bandwidth
medium
for
short,
but
getting
to
places
physically,
it
seems
to
be
a
little
bit
more
difficult
than
it
used
to
be
and
I
miss
it.
I
really
do.
B
Maybe
slack
you
know
I
work
from
home
and
you
know
that's
my
main
communication,
medium
with
everybody,
and
so
definitely
you
know
the
intro
talks.
The
deep
dive
talks
will
be
people
that
that
you
recognize
and
I
believe
in
our
badges.
We
have
the
twitter
handle,
or
you
know
in
slack,
handle
printed
on
that
as
well.
Isn't
that
Paris,
so
the
hardest
part
is
to
figure
out
from
the
slack
and
who,
who
you
really
are
you
know,
Erin
I
knew
as
expe
long
time
before.
I
knew
him
bizarre
answer.
B
If
we
can
figure
out
a
way
to
make
that
process
easier,
we
should
we
should
try
to
do
that,
but
yeah
definite
the
local
meetups
are
important
as
well.
But
the
thing
that
is
different
with
us
is
we
do
have
the
weekly
meetings
which
are
on
video,
so
all
of
them
are
on
video,
so
you
should
drop
by
in
the
meetings
and
even
if
you
have
the
fly
on
the
wall
for
some
time
yeah,
so
you
should.
You
should
definitely
do
that.
Yes,.
A
E
E
Today
it
it
varies,
but
it
moves
around
the
roads
around
the
country
and
I
have
found
it
to
be
a
pretty
interesting
practitioner
practitioner
place
to
meet
people
who
are
actually
doing
stuff,
which
is
the
most
interesting
part,
I,
think
to
learn
like
what
people
are
actually
doing
in
the
real
world.
Now.
A
B
Have
to
mention
that
we
have
country-specific
and
location-specific
slack
channels.
That
is
the
best
place
where
you
can
find
people
in
your
own
time
zone
so
there,
for
example,
the
CN
devils
for
china
and
I
and
Eva's
for
the
for
the
India
folks
and
try
to
find
people,
and
you
know,
exchange
tips,
trade,
PRS
issues.
What
what
not
so,
please
do
that
as
well
and.
A
Read
last
night
that
half
of
slocks
traffic
actually
comes
out
of
the
United
States
I
did
not
know
that
I
thought
that
that
was
but
would
be
a
higher
percentage
number
for
for
the
United
States.
To
be
honest,
but
that's
great
news.
That
means
them
more
more
folks
are
going
to
be
able
to
get
plugged
in
into
our
ecosystem.
A
If
you
cannot
get
plugged
in
though,
for
instance,
the
flock
is
AWOL
for
you
and
you
cannot
get
plugged
into
that
network,
we
do
have
discussed
kubernetes
I/o,
it's
a
very
similar
feel
except
it's
forums,
there's
a
lot
more
user
conversation
than
contributors,
but
start
it.
That's
that's
how
we
get
it
is
if
you
start
it.
So,
let's
see
next
question.
I
think
that
most
of
these
questions
are:
how
can
folks
meet
you
at
cube
con?
To
be
honest,
that's
I
think
the
the
TLDR
there.
A
C
B
About
you,
there
is
some
talks
about
sick
cloud
provider,
so
I
will
definitely
be
there
and
it's
important
work
it's
going
slowly
and
we
need
more
people
to
help
as
well
there.
So,
if
you're
around
and
if
you
run
your
stuff
in
the
public
clouds
or
private
clouds-
and
you
need
deeper
integration-
come
talk
to
us.
Please.
E
I
have
to
admit
that
I
have
not
looked
at
the
schedule
yet
other
than
to
see
when
I
had
to
dismiss
her
I,
actually
loved
the
hallway
track.
Like
that's
my
favorite
part,
whether
it's
at
the
booth
or
just
literally
alcohol,
you
know
I,
that's
where
right.
That's,
where
I
tend
to
hang
out
I
like
the
informal
conversations
more
than
the
PowerPoint,
even
my
own
power
fight.
A
A
C
My
other
little
pro
tip
I,
don't
know
if
it's
gonna
be
on
the
badges
that
this
conference
or
not
but
put
your
github
ID
or
your
slack
ID
on
your
badge.
I
will
definitely
do
that
because,
yes,
there
are
some
people,
I
only
know
I'm
finding
called
Steve
XP,
it's
totally
cool,
so
I
think
that's
that's
a
great
way.
I
recognize.
Perhaps
my
beard
is
not
super
anonymous,
but
there
are
a
lot
of
people
who
I
wouldn't
recognize
if
I
didn't
know
what
they're
slacking.
That's
super
helpful.
B
A
A
We
have
over
a
hundred
people
coming
for
that
and
then
there's
also
a
second
session,
which
is
a
tutorial
I,
believe
it's
on
Tuesday
and
that's
building
and
running
communities
from
source
and
submitting
your
first
PR,
that's
about
an
hour
and
a
half
to
two
hours,
long
I
believe
so
that's
a
condensed
version
of
Monday
and
it
looks
like
they
are
going
to
be
at
capacity
as
well.
So
if
you
are
interested
in
going
to
that,
you
should
definitely
get
there
early.
A
It
looks
like
they
have
well
over
150
people
that
are
interested
in
that
session,
so
there
is
so
much
interest
in
minetti's
contributing
which
is
awesome.
What
is
your
best
advice
for
these
folks
that
we
are
about
to
onboard
here,
hundreds
actually
with
200
plus
within
the
next
week?
If
you
are,
if
you
were
a
first-time
contributor
today,
what
are
one?
You
know
less
than
a
handful
of
things
that
you
think
that
they
should
either
be
plugged
into
or
reading
about
or
communicating
with.
E
My
first
tip
is:
don't
forget
the
non-core,
repos,
okay,
there's
a
lot
of
work
that
happens
not
in
the
core
communities,
communities
and
often
times
the
growth
under
staff
and
easier
to
get
into.
Maybe
those
things
go
hand
in
hand,
but
that's
a
great
way
to
get
in
I.
Think
the
main
repo
is
well
that's
jumping
into
the
deep
end
for
sure,
okay,
so
the
other
side
of
that
is,
if
you
jump
into
the
deep
end,
you
should
expect
to
have
to
struggle
for
a
while
that.
A
B
One
quick
way
to
figure
out
what
is
happening
in
the
projects
is
looking
at
the
in-hand
enhancements
that
are
being
filed
to
get
a
general
direction
of
where
the
project
is
going.
Where
are
people
going
to
spend
their
time?
So
that's
a
one
good
way
to
you
know
get.
As
you
know,
what
is
the
work
that
is
gonna
be
done
in
the
neck
up
coming
release
or
releases.
Then
you
find
people
who
whose
work
you
can
follow.
B
For
example,
there's
several
people
like
it
take
Aaron,
for
example,
right
see
what
what
Adam
is
up
to
and
what
kind
of
things
these
involve
this
so
and
then
follow
along
their
full
requests
and
issues
and
see
how
you
can
help
out.
You
know
that's
another
way
to
get
to
know
people
as
well
right.
So
so
it's
important
to
understand
so
there
might
be
different
ways
of
doing
things,
but
the
project
might
have
might
have
settled
down.
So
you
need
to
figure
out
what
are
the
norms
of
the
contribution?
B
You
know
you
might
have
a
specific
way
of
doing
something,
but
then
the
project
is
typically
used
to
something
else.
Then
you
add
up
to
that.
So
little
tips
like
that
will
help
a
long
way.
You
know
always
be
browsing
issues
and
PRS.
If
you
have,
when
you
have
time,
you
don't
have
to
do
it
every
day.
You
can
do
it
once
a
week
and
you
know
try
to
help
out
little
ways
that
you
can.
C
Minute
you
another
another
strong
vote
for
the
hallway
track.
Remember
that
there
probably
a
lot
more
people
if
you
feel
just
as
awkward
or
uncomfortable
as
you
do,
and
it's
totally
okay
and
remember,
like
all
of
those
super
cool
awesome
talks
are
going
to
be
recorded.
So
if
you're
just
going
to
listen
to
the
talk,
you
can
get
the
same
information
by
watching
a
video
later,
because
CN
CFO
supposed
slides
and
videos
ahead
of
time.
A
lot
of
speakers.
C
B
E
Only
last
the
last
pro
tip
I
would
add,
is
github
notifications,
don't
work
for
most
of
the
core
contributors
and
just
too
much
noise
and
so
like,
if
you
put
at
somebody
or
ever,
and
you
expect
them
to
respond,
it's
not
going
to
happen.
You
should
probably
think
I'm
on
black
or
something
like
that
and
most
of
us,
because
of
that
don't
mind
if
you
think
about
black
about
a
PR
or
something
like
that.
A
A
It's
definitely
pretty
significant,
so
I'm
excited
to
see
how
it
goes
and
on
the
recorded
note,
if
you
cannot
get
into
the
new
contributor
workshop
on
Monday,
which
we
have
officially
closed
to
even
the
wait
list
at
this
point
that
will
be
recorded.
So
it's
going
to
be
up
on
YouTube.
There
actually
is
already
a
first
shot
of
the
one
that
we
did
at
Copenhagen
on
YouTube.
If
you'll
want
to
check
that
out,
it's
awesome.
It's
chunked
into
sections,
there's
an
outline
in
the
repo
in
the
community
repo.
A
So
that's
awesome,
not
sure
if
the
tutorials
are
going
to
be
reported
a
cube
con,
but
there
is
a
there's
also
a
chance
that
the
the
other
second
tutorial
will
be
recorded
as
well.
So
there's
definitely
going
to
be
a
lot
of
video
content
floating
around
the
interwebs
post,
cube
con
related
to
upstream,
recruiting
or
contributing
that
is
it
for
us
today.