►
Description
We hold a Contributor Workshop at Kubecon to introduce people who are interested in learning how to contribute to Kubernetes. You can check out the Contributor's Guide as a complement to these videos: https://github.com/kubernetes/community/tree/master/contributors/guide
A
A
A
A
A
A
A
A
So
as
we're
going
through
the
day,.
If
you
get
questions
or
you're
starting
to
get
a
little
bit
more
curious
about
a
particular
thing
or
you've
come
explicitly
wanting
to
know
about
scheduling
or
scalability
or
something
like
that,
you'll
get
a
chance
to
hopefully
meet
some
of
those
people
a
little
bit
face
to
face..
A
A
A
okay,.
So
then
we'll
go
a
little
more
into
sigs,,
but
specifically
how
those
tie
into
the
way
we
use
github
and
then
because
this
session
is
about
people
new
to
open
source,,
we'll
talk
about
a
little
bit
of
open
source
generalities,,
but
then
bring
that
back
into
how
we
do
pull
requests
in
kubernetes,
talk
about
the
bots
that
you'll
interact
with
doing
pull
requests.
A
On
getting
your
dev
environment
set
up.,
then
we'll
have
the
break
at
lunch,
and
that
may
also
provide
us
some
time
to
do
some
downloading
and
tinkering
on
the
machines,
depending
on
where
you
are.
afternoon.
We'll
start
out
with
the
final
dev
environment
check
and
hopefully
you'll
all
be
up
to
the
point
to
be
able
to
actually
go
into
the
build
systems
and
we'll
try
and
make
a
few
things.
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
[Audience
member]
(mumbles)
yeah,.
I
guess
so.
go
ahead
and
do
these,
if
you
get
through
the
other,
stuff,
try
and
do
these.
what
this'll
do
is
prepopulate
a
few
docker
containers
on
your
laptop
that
we'll
be
using
later
in
the
afternoon
and
instead
of
at
the
point
that
you
run
the
command
at
pulling
these
containers
from
the
internet,.
A
A
A
A
A
A
A
A
So
if
you
look
at
things,
here,
you'll
get
the
impression
that
this
is
just
a
normal
github
workflow,
if
you're
familiar
with
that..
But
we've
put
some
effort
into
trying
to
make
sure
that
there's
consistency,
because
there's
just
so
much
going
on.,
it
would
be
easy
for
it
to
just
kind
of
all
flake
every
which
way.
A
A
A
A
A
A
A
A
A
A
A
A
A
That's
for
flaky
tests.,
it's
not
just
outright
failing
tests,,
but
it's
a
wobbly,
test,
kind,
cleanup.,
there's
a
whole
bunch
of
them.
and
again,.
You
just
say
/kind
and
the
kind
that
you
want
to
assign.,
and
this
is
really
useful
for
triage,
as
somebody
is
trying
to
figure
out,
or
maybe
you
already
understand
that
it's
a
failing
test
or
there's
actually
automation.
Now
that
notices
failing
tests
and
creates
the
bugs,
labels
them
as
failing
test,,
and
then
somebody
who
wants
to
help
improve
tests
can
go,
find
all
the
currently
failing,
tests.
A
Priority.,
this
can
be
a
tricky
one..
This
is
not
required
because
it's
a
little
bit
more
subjective,,
but
at
some
point,
maybe,
as
a
sigs
leadership
has
triaged
a
bug.
they'll
decide
like,
oh,.
This
is
a
really
big
deal,
or,
eh,,
we're
gonna,
put
this
on
the
backlog
or
somewhere
in
between
and
they'll,
apply
this
label
and
again,.
A
This
is
assigned
for
the
humans..
If
you're
someone
new
coming
to
the
project,,
you
may
want
to
start
out
by
looking
at
the
backlog
where
something
that's
just
kind
of
sitting
there
that
I
could
kind
of
dabble
at
for
a
bit
and
get
some
orientation,,
but
then
also
be
giving
real
value
to
the
project.
Still
because
it's
sitting
there.
A
A
Is
it
a
support?
Question?
we
don't
use
git
or
github
to
answer
support
questions.
we
redirect
people
to
stackoverflow
or
discourse
or
slack.,
or
did
somebody
who
actually
triaged
the
problem,
couldn't
reproduce
it..
All
of
this
is
about
leaving
cookie
crumbs
of
what
has
happened
for
triage
at
the
given
point.
A
A
A
A
A
A
It's
not
just
writing
a
piece
of
code,
publishing
and
api..
Somebody's
gonna
use
your
api
and
it's
not
gonna
work
the
way
they
expect
it,
and
you
have
to
figure
out
some
common
ground
there.
If
you're
gonna
actually
collaborate.,
it's
not
just
telling
them,
well,
you're
doing
it,
wrong.,
there's
all
sorts
of
things.
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
during
that
time:
there's
a
period
of
code
freeze..
So
if
you
come
along,
and
it's
actually,,
it
starts
next
week..
So
if
you
come
out
of
here,
really
excited,
you've
got
some
idea,
you've
hacked
around
for
some
cool
little
extension
or
fix,
or
something
and
you
throw
it
out.
There,
people
probably
aren't
gonna
review
it
because
it's
code
freeze
time
and
they
aren't
gonna,
be
able
to
merge
it
anyway..
A
A
Because
we'll
have
finished
the
release
and
we'll
be
starting
the
next
one.,
so
you
get
sort
of
this
cadence
of
things
and
it
can
trip
you
up,,
especially
if
you're
here,
because
your
boss
told
you,
you
got
to
get
this
feature
into.
Kubernetes.
well,
you've
got
to
understand
the
timeline
and
when
and
how
to
slot
major
changes.
In.
A
A
A
A
A
A
A
A
So
we
need
you
to
understand
what
it
is
that
kubernetes
is
and
the
how
and
why
we
do
things
and
to
build
consensus
across
all
the
different
people
here
too,
so
that
you're
not
pulling
the
project
in
one
direction
and
somebody
pulling
it
in
a
contradictory
direction
that
when
we
see
similar
people
doing
similar
things
like
cluster
provisioning,,
that
at
some
point
we
say,
hey,.
Let's
have
a
cluster
api..
A
A
A
A
A
A
A
A
A
A
A
A
A
So
any
code
that
matches
all
of
the
label
requirements
around
having
been
reviewed
and
approved
and
have
release
notes
if
needed
and
has
had
testing
and
the
tests
pass
when
all
of
those
quality
criteria
are
met.
On
an
automated
basis,,
we
have
a
thing
called
tide
that
will
actually
merge
them
in,
and
this
is,.
A
A
A
A
I
found
somewhere
in
the
code,
a
comment
that
was
completely
wrong
and
it
referenced
a
website
for
more
information
completely
wrong,,
but
I
was
able
to
google
search,,
find
it
and
find
the
right
information..
So
I
was
like,
well,
I'll,
just
pr
this
fix
so
that
anybody
else
who
stumbles
on
this
later
won't
have
it..
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
But
that
doesn't
mean
everybody's
going
to
and
know
that,
just
because
one
person
really
liked
it
or
didn't,
that
doesn't
mean
your
code
is
completely
wrong
or
completely
successful..
There's
a
fuzziness
here
and
you
have
to
figure
out
how
to
bring
the
different
opinions
of
different
reviewers
together
to
kind
of
collaboratively
move
the
state
of
things
forward.