►
Description
Speaker: Guinevere Saenger
A
So
I
know
everyone
has
been
here
all
day
and
you
all
must
be
super
tired.
So
let
me
wrap
this
up
with
a
couple
more
things
and
then
what
will
happen
is
we
are
actually
not
going
to
leave
this
room
for
the
Signet
and
greet
the
cig
meet
and
greet
will
come
to
us
because
room
sizes
and
tables
make
a
lot
more
sense.
Over
here,
I
have
people,
our
people
are
organizing
and
we,
you
will
get
a
chance
to
meet
sig
representatives
in
roughly
10
15
minutes.
A
All
right,
I
was
going
to
briefly
mention
our
release
cycle
kubernetes
releases
four
times
a
year.
That's
not
exactly
quarterly,
but
we
roughly
try
and
approach
that
that's
a
very
frequent
release
cycle
and
one
of
the
really
excellent
ways
to
get
involved,
contributing
is
by
being
on
the
release
team.
There
are
lots
of
people
on
the
release
team
that
have
done
that
are
doing
this.
A
Yeah.
It's
basically
a
three-month
release
cycle
during
the
feature
work
we
develop
new
features,
development
completion
and
then
during
code
freeze,
basically,
there
will
be
no
more
features
admitted
into
the
into
into
kubernetes
master.
Well,
the
release
branch
will
be
cut
and
the
only
thing
that
will
make
it
into
the
release
branch.
At
that
time,
our
bug
fixes.
A
A
Here
is
another
okay,
you
know
I
should
yeah
so
here's
another
slide
where
this
is.
This
is
kind
of
the
weekly
outline
on
how
long
it'll
take
for
you
know,
enhancements
development
and
when
we
are
going
to
cut
the
release
branch
when
code
freeze
ends
and
what
it
means.
The
only
repository
in
which
you're
going
to
run
this
run
into
this
by
the
way
is
currently
kubernetes
kubernetes.
A
A
This
slide
kind
of
is
a
little
bit
of
an
illustration
of
what
the
cherry-pick
process
looks
like
I
sort
of
explained
a
little
bit
about
this
earlier.
If
you
are
really
really
trying
hard
to
fix
a
bug
and
you
miss
the
deadline
or
you
really
really
think
that
this
needs
to
be
fixed
for
a
previous
still
supported
version
of
kubernetes.
A
So
what's
next
for
you
from
here
on
out,
please
use
this
conference
to
introduce
yourself
to
meet
people.
I
can
highly
recommend
the
cig,
intros
and
sig
deep
dives.
They
are
less
presentation
and
more
discussion
based,
not
to
say
there
won't
be
presentations,
but
generally
you
will
have
a
high
chance
of
being
able
to
ask
questions
and
meeting
people
and
back
to
membership.
Someone
asked
earlier
how
do
I
become
a
member?
A
The
definition
to
this
is
a
little
bit
squishy,
but
your
new
rule
of
thumb
is
once
you've
made
one
or
two
pull
request.
Contributions
or
you've
joined
a
team
and
organized
a
thing.
Then
you
should
get
to
sponsors
that
are
members
and
file
an
issue
against
kubernetes
org,
which
is
a
subgroup
of
kubernetes
communities
organization
and
apply
for
membership.
Basically,
what
will
happen?
You'll
open
an
issue-
you
say:
hey
I
should
be
a
member.
This
is
the
work.
A
I
did
and
then
you'll
ask
your
sponsors
to
add
a
plus-one
to
your
request
and
that
will
usually
have
you
become
a
member.
So
going
up.
The
contributor
ladder
is
a
is
a
pull
request
as
well
against
an
owner's
file.
Often
people
self
decide
that
hey
I
know
a
lot
about
this
part
now
and
I've
been
helping
out
a
lot.
I
should
probably
be
in
this
owner's
file.
A
So
you
can
I
mean
I
would
recommend
talking
to
people
first,
but
you
can
open
a
pull
request
and
say:
I
would
like
to
be
a
co
donor
here
and
be
and
have
reviewer
status.
Don't
wait
for
someone
to
add
you.
Everyone
is
really
really
busy,
but
if
you
suggest
hey,
maybe
I
should
be
in
this
owners.
File.
People
are
probably
going
to
depending
on
your
situation.
It's
it
can
be
a
good
move.
A
A
Contributions
can
be
a
ton
of
different
things.
Not
everyone
will
contribute
to
be
a
pull
request,
because
you
can
contribute
in
many
other
ways
that
don't
even
involve
code
and
are
still
incredibly
important.
This
does
also
not
mean
you
shouldn't
be
a
member.
So
if
you
do
a
lot
of
these
things,
please
apply
for
organ
Barcia.
A
On
a
more
personal
level,
we
have
several
mentoring
opportunities.
I
have
I,
have
a
link
at
the
bottom
of
this
section.
That
kind
of
gets
you
into
our
mentoring.
Our
current
mentoring
strategies
meet
our
contributors
is
I.
Think
a
bi-monthly
live
video
chat
where
current
contributors
answer
burning
questions
you
might
have
of
them:
google,
Summer
of
Code
and
outreach
e,
our
programs
that
are
available
to
students.
You
need
to
be
able
to
qualify,
I
already
mentioned
being
on
the
release
team.