►
Description
First ever New Contributor Workshop!
Speakers Josh Berkus and Guinevere Saenger walks us through how to contribute to the Kubernetes project.
You’ll learn everything from CLA signing, what a SIG is, the difference between a Working Group and a Subproject, where to ask questions, how to get involved with the community and give you an understanding of the different Kubernetes GitHub repositories.
A
Welcome
everybody
testing
there
we
go
welcome
everyone
like
George's
announcement
power
strips
are
on
order
in
in
theory,
they
will
arrive
before
the
end
of
the
workshop.
We
will
see
so
welcome
everyone
to
the
first
kubernetes
new
contributor
workshop.
This
is,
in
fact
the
first
time
that
we're
doing
this.
So
you
are
the
first
class.
Congratulations.
A
How
many
people
actually
have
how
many
people
filed
an
issue
against
kubernetes
or
one
of
the
clothes
accessories
great?
How
many
people
have
filed
the
PR
cool?
Ok,
so
got
a
few
PR
people
and-
and
the
people
have
already
filed
the
PR
before
kind
of
spread
around,
which
is
awesome.
The
smoke
on
board
its
kubernetes,
it's
an
open
project
becoming
a
contributor,
starts
with
contributing
and
we
will
be
helping.
You
make
that
contribution
as
effective
as
possible.
Now,
like
I
said,
this
is
the
first
time
we
doing
a
new
contributor
workshop.
A
A
A
We
don't
expect
you
to
retain
there
all
the
idea
is
for
you
to
learn
enough
things
that
you
know
where
to
go,
to
ask
further
questions
which
is
the
most
confusing
and
the
hardest
part
of
you
know,
which
slack
channel
do
I
ask
this
in
or
which
mailing
list
do
I
ask
this
on,
or
what's
the
word
for
that
and,
and
that
is
what
we're
trying
to
get
through
it.
I
mean
we're.
There's
going
to
be
hands-on.
A
Exercises
is
going
to
be
group
exercises
to
get
you
used
to
contributing,
but
really
this
is
mainly
about
orientation.
So
hopefully,
this
describes
everything.
The
room
we
just
asked
right
is
some
of
you
how
many
people
would
describe
themselves?
Basically
advanced
users
do
kubernetes
how
many
vote
beginning
users
of
kubernetes?
Okay,
that's
some
beginning
users.
A
A
Yeah,
that's
how
it
gets
started.
So
I
started
in
in
the
90s
with
a
different,
open
source
project
where
I
said
this
is
wrong.
This
is
not
this
back
and
they're
like
great
well,
the
broken
code
is
here
or
see
if
he
can
fix
it
and
then
18
years
of
contributions
later
before,
I
switch
to
kubernetes.
So
that's
how
it
starts.
So
we
are
going
to
have
a
full
lineup
of
people.
This
is
actually
changed
around
a
little
bit
at
the
last
minute
because
we
had
a
couple
of
people
with
travel
problems.
A
A
We've
swapped
that
role
twice,
but
a
bunch
of
people
from
different
parts
of
the
project
will
be
coming
to
talk
to
you
about
contributing
to
their
parts
of
the
project,
which
is
part
of
the
idea
here,
because
this
is
a
big
project
and
it
has
a
lot
of
pieces.
You
want
to
hear
from
different
people.
So
this
is
our
lineup
here
approximately
like
I
said
this
is
the
first
time
we've
done
this,
so
we
may
go
a
little
off
schedule
on
this.
A
You
know,
for
example,
the
tour
of
repositories
might
be
before,
after
the
break,
depending
on
how
things
work
out.
We're
gonna
actually
give
you
like
a
full
20
ish
minute
break,
because
we
think
you'll
need
it
me
a
lot
of
stuff
here
and
we're
going
to
be
going
through
a
lot
of
stuff.
So,
but
the
whole
goal
here
is
to
move
you
up.
A
This
stack
because
one
of
the
one
of
the
various
parts
of
the
project
I
participate
in
is
called
cig,
contribute
experience
which
is
who's
running
all
the
contributors
stuff
and
one
of
the
things
we
discussed
and
said
contribute
experiences
what's
going
on
to
the
future
of
the
project
and
what
we
need
more
than
anything
right
now
in
kubernetes
is
actually
senior
reviewers
and
the
only
way
that's
going
to
work
is
if
we
get
some
number
of
you
to
the
status
of
senior
reviewer.
So
that
is
our
goal.
B
You
Josh
hi,
everyone
are
you
awake
and
non
jet-lagged,
and
or
is
that
just
me
alright,
so
who
here
has
already
signed
this
ela
awesome?
Who
here
has
not
signed
the
CLA
cool?
This
is
great.
We're
gonna
be
ahead
of
schedule.
Did
anyone
run
into
trouble
with
anything
as
anyone
CLA
still
pending?
Nothing
like
that
excellent,
very
cool.
So
let
me
just
forward
to
these
slides,
because
this
is
something
we
don't
really
need
for
you,
it's
excellent,
very
cool,
so
our
next
section
is
going
to
be.
B
Where
do
I
even
get
started,
and
this
is
gonna
be
a
little
bit
of
a
big-picture
kind
of
Oh.
Are
we
having
some
people
joining
us
in
the
back?
Oh,
never
mind,
alright
cool,
so
who
here
remembers
to
choose
your
own
adventure
games
from
the
80s
and
all
that
and
later
and
I
I,
don't
know
I'm
a
huge
DMD
nerd.
B
There
are
so
many
different
contributor
origin
stories
out
there.
Some
people
come
basically
from
the
Linux
Foundation
or
just
a
community
background
and
just
want
to
build
the
community.
They
want
to
improve
how
everyone
is
interacting.
I
mean
there
are
people
in
the
project
whose
entire
job
title
is
community
member
I
mean
community
manager.
Sorry,
maybe
I
am
a
little
jet-lagged
so
and
that's
actually
really
really
important.
B
B
Stuff,
like
that
all
those
are
totally
valid
ways
to
contribute
to
to
the
community.
I,
don't
even
know
to
use
this
thing,
that's
right
now,
all
right.
So
one
of
the
first
really
concrete
examples
is:
you
can
contribute
to
the
docks,
especially
if
you
are
new
to
the
technology
in
general.
This
is
a
really
great
way
to
learn
about
it.
The
other
thing
what
we
get
out
of
it,
why?
Why
do
we
want
a
bunch
of
newcomers
contributing
to
the
docks?
B
Well,
because
if
it
is
not
clear
to
you
that
means
it's
also
not
clear
to
the
next
newcomer
and
newcomers
have
a
unique
perspective
in
terms
of
hey:
wait:
I,
don't
get
it.
What
does
this
mean?
So
please
contribute
to
the
documentation,
contribute
to
the
way
things
are
explained,
write
your
tutorials.
While
you
have
that
fresh
perspective,
we
love
that
I
noticed
III
wrote
some
some
I
made
some
comments
about
this
thing
called
a
cig.
That
is
a
concept
we
will
learn
more
about
throughout
the
day
brief
overview,
it's
called
a
special
interest
group.
B
B
Then
we
have
a
really
really
really
huge
and
complicated
test
setup
and
we
have
an
entire
sake
dedicated
just
a
testing.
In
fact,
there
are
people
whose
entire
jobs
involve
just
making
sure
that
the
kubernetes
tests
run
it's
they're,
a
friendly
bunch.
If
that's
your
jam,
go
ahead
and
check
out
a
little
bit
more.
What
what
they
do
most
of
their
code
is
written
and
go
so
speaking
of
code.
You
can
go
ahead
and
contribute
to
the
core
repository.
B
Yes,
you,
anyone
is
welcome
to
submit
pull
requests
to
open
issues
and
to
learn
about
what
makes
all
of
this
work
beneath
the
covers.
I
can't
really
tell
you,
which
SIG's
to
join
for
this
until
you've
sort
of
gotten
your
head
into
the
things
a
little
bit
deeper,
because
unfortunately,
kubernetes
is
a
huge
mono
repo,
so
the
command
line,
the
CLI,
the
the
related
projects,
a
lot
of
them
are
actually
under
one
core
repository
and
then
there's
also
related
projects
which
use
kubernetes
or
manage
kubernetes.
B
For
example,
helm
is
a
big
project
that
has
its
own
charts
repository
that
they're
called
helm
charts.
So
that's
another
area
where
you
can
contribute.
That's
maybe
not
the
core
repository,
but
is
absolutely
definitely
part
of
the
whole
community.
So
this
sort
of
rolls
into
you
know
what,
where
do,
I
find
my
absolute
very
first
topic
so
who
here,
maybe
maybe
maybe
some
one
of
you
has
already
used
kubernetes
and
found
a
bug
or
sound
something
that
they
would
want
fixed
or
maybe
I
I.
Remember
when
I
first
started
something
about
shutting
down.
B
Kubernetes
nodes
didn't
really
work
the
way
it
was
supposed
to
and
at
the
time
I
was
still
learning
so,
but
that
was
actually
kind
of
a
good
opportunity
to
fix
it.
So
sometimes
you
find
your
first
topic
very
naturally
as
part
of
what
you're
working
on
and
sometimes
you're
just
so
overwhelmed.
It's
just
like.
Where
do
I
start?
How
can
I,
how
can
I,
even
how
can
I
even
get
going
with
anything
like
this?
It's
super
it's
just
it's.
It
can
be
really
overwhelming.
B
So
what
I
did,
for
example,
was
I
tried
to
learn
about
how
to
contribute,
and
that
was
already
really
really
hard.
So
I
decided
to
document
the
contribute,
contributing
process
a
little
bit
more
in
depth
and
a
little
bit
more
easy
to
follow,
and
hopefully,
I
succeeded
we'll
go
over
that
hands-on
later
in
the
day.
So
this
is
sort
of
where
I
think
I'm
going
to
hand
it
over
to
Josh
so
that
he
can
kind
of
lead
you
through
a
little
sharing
exercise
with
your
tables.
A
End
of
things
or
somebody's
gonna
say:
hey
I
really
really
care
about
having
clear
documentation
and
that's
where
I
see
myself
going
so
we're
gonna,
take
about
10
12
minutes
for
you
to
just
go
around
your
tables
and
talk
to
each
other.
One
at
a
time
like
I
said,
introduce
yourself
explain
to
the
other
folks
at
your
table,
how
you
think
you
might
be
interested
in
contributing
to
kubernetes
and
and
then
go
on
to
the
next
person.
So
let's
go
ahead
and
get
started,
hey
folks,
so
how
many
tables
are
still
going?
A
A
A
A
How
many
people
are
really
interested
in
one
of
the
clothes
accessory
projects
like
Helmerich
uber,
or
something
like
that?
Oh
yeah,
lots
of
people,
okay,
and
how
many
people
you
are
more
focused
on
applications
on
top
of
kubernetes,
cool,
okay,
so
lots
of
stuff.
So
the
next
thing
up
is
I'm,
going
to
turn
it
back
over
to
my
co-presenters
going
to
talk
to
you
about.
B
Let's
talk
about
communication
I,
really
like
this
image,
I
really
like
capybaras,
they
are
the
world's
largest
rodent
and
they
have
this
weird
reputation
of
getting
along
with
everybody,
including
their
own
predator,
which
I'm
not
I.
Just
kind
of
don't
want
to
know
what
happened
in
the
bottom.
My
picture
there
I'm
a
little
worried
about
that
one,
but
I,
just
kind
of
feel
like
the
entire
kubernetes
project,
is
a
little
bit
like
one
giant
fuzzy
capybara,
because
there
are
so
many
different
people
in
it
and
there
is
a
place
for
everybody
and
I
actually
I.
B
Don't
just
believe
that
I
have
experienced
that
personally
and
I
believe.
The
reason
is
that
this
project
makes
a
huge
effort
at
creating
community
rather
than
just
technology
and
I,
think
that
the
technology
is
better
for
it,
because
we
get
more
voices
and
more
diverse
voices
and
more
different
people
coming
at
it
from
all
their
different
backgrounds.
I
mean
Josh.
Just
asked
you
hey.
What
are
all
these
different
people
in
this
room
interested
in
doing,
and
there
were
so
many
different
answers,
and
that
is
a
good
thing.
So.
B
When
I,
when
it
says
you
know,
with
a
lot
of
these
things,
it's
like
hey
sign
our
code
of
conduct-
hey
you
need
to
do
this
first
thing:
everybody's
just
kind
of
like
yeah,
so
in
my
opinion,
it
is
the
way
in
which
we
enforce
or
encourage
this
code
of
conduct.
We
follow
the
CNC
F
code
of
conduct.
It
is
not
very
long.
B
I
encourage
everyone
to
actually
read
it
and
reflect
on
it,
but,
as
with
all
of
these
things,
it
kind
of
boils
down
to
you,
know,
be
nice
and
be
respectful
and
try
to
do
your
very
best
at
assuming
the
very
best
of
other
people.
I
think
that
is
the
basic
core
concept
of
any
of
these
codes
of
conduct.
So
you
can
read
this
on
your
own
time,
but
from
my
perspective,
that
is
what
it
boils
down
to.
B
B
Well,
I
might
not
have
committed
all
of
them,
but
some
of
them
so
technical
questions.
If
you
have
questions
about
kubernetes
I'm,
not
sure
why
I've
said
if,
when
you
have
questions
about
kubernetes,
the
place
to
ask
them
is
not
github.
I
know
that
some
projects
do
this
differently
and
I
also
know
that
there
are
many
answers
to
be
found
when
searching
the
github
project.
But
please
do
not
open
an
issue
because
you
have
a
question
on
how
to
spin
up
a
cluster.
B
Well
done,
oh
all,
right.
We
have
some
people
excellent,
it's
it's!
Ok!
It's
ok!
We're
gonna!
Go
over
that!
This
is
great
then,
and
the
next
two
are
really
just
kind
of
related,
because
this
is
a
distributed
project.
A
lot
of
the
discussion
is
going
to
happen
on
github.
So
if
there's
an
issue,
you've
passionately
care
about
this
feature,
you
really
want
this
feature
expect
some
pushback
on
your
issue
expect
that
people
will
say
well.
B
We
would
love
to
do
that,
but
because
of
these
reasons
we
can't
and
it's
okay,
to
engage
in
a
discussion
as
long
as
you
stay
courteous,
it
is
also
important
that
you
follow
up
on
your
issue.
There's
nothing
more
frustrating
than
somebody
fixing
a
bug
and
then
needing
to
rebase
or
update
a
version,
and
it
just
sits
there.
Oh
I
feel
so
awful.
B
B
24
hours
of
the
day,
they
may
live
halfway
around
the
world
and
be
asleep
currently,
so
please
keep
all
those
things
in
mind
and
if
you
keep
these,
if
you
keep
these
three
basic
ideas
in
the
back
of
your
head,
you'll
probably
be
okay,
don't
do
what
I
did
I
tried
to
open.
My
very
first
poll
request
against
a
kubernetes
community,
repo
and
I,
found
it
very,
very
difficult
to
figure
to
figure
out
how
to
do
that.
So
I
opened
an
issue
and
it
said
what
did
it
say.
It
said:
documentation,
confusing
and
outdated.
B
That
was
the
title.
I'm
I
I
feel
kind
of
bad
about
that.
But
people
were
really
patient
and
kind
and
said
hey.
You
know.
We
know
that
our
contributor
guide
kind
of
sucks
you
want
to
help
us
fix
it.
Cuz,
that's
sort
of
the
open
source
idea:
hey
yeah,
you
know
it's
broken,
you
want
to
fix
it.
You
take
responsibility
for
the
project,
even
as
a
newcomer.
B
So
when
any
of
these
things
are,
when
you
ever
confused
about
something
go
ahead
and
ask
questions-
and
there
are
many
many
places
to
ask
questions
who
here
has
ever
run
into
this
issue-
where
they
had
a
question
and
didn't
really
know
where
to
ask
awesome
all
right.
So
this
is
where
I'm
going
to
take
you
on
a
little
slack
tour.
B
So
we
have.
There
are
so
many
channels
again.
It
is
super
overwhelming
I'm,
just
browsing
through
these
channels,
there's
not
a
whole
lot
that
there's
not
a
whole
lot
of
use
in
browsing
channels.
What
I
really
encourage
everyone
to
join
is
kubernetes.
You
SURS!
That's
where
a
lot
a
lot
of
questions
can
be
asked
and
will
be
getting
answered.
So
you'll
see
here,
just
browsing
just
browsing
that
channel
that
people
will
be
people
are
getting
help.
B
Then
there
is
also
the
I.
Don't
know
if
I
have
joined
that
one
kubernetes
novice,
that
is
for
you,
if
you
are
learning
I,
don't
know
why
I
didn't
join
that
one
and
I
personally,
as
a
member
of
sig
contributor
experience
encourage
you
all
to
join
the
sig
Country
Beck's
channel,
because
it
is
literally
the
SIG's
job
to
help
you
out
if
you
are
confused.
Even
if
your
question
has
nothing
to
do
with
contributing,
you
can
still
go
ahead
and
ask
help.
B
You
can
still
go
ahead
and
ask
hey.
Where
would
I
go,
find
help
for
this
thing?
And
someone
will
point
you
in
the
right
direction
again,
if
you're
patient
and
if
you
just
kind
of
keep
at
it
and
follow
through,
you
will
probably
get
your
answer.
Hooray.
We
have
two
new
members
on
sick
country,
vex,
channel
excellent.
B
So
so
those
are
some
basic
channels,
but
you
can
look
around
and
see.
Each
cig
also
has
their
own
channel.
So
once
you
find
your
area
of
interest
and
your
and
your
group
of
people
that
work
on
similar
things
and
that
are
excited
about
your
things,
you
can
find
out
what
sig
they
are
in
and
join
their
channel
as
well.
B
There
are
many
ways
to
communicate
and
all
of
them
unfortunately
take
some
effort
from
you.
I
mean
I.
Guess
that's
sort
of
how
communication
works.
There
are
community
meetings,
there's
the
big
kubernetes
community
meeting
once
a
week.
For
me
it's
on
Thursdays
at
10:00,
but
that's
totally
different
for
you.
I'll
show
you
the
calendar.
You
can
join
mailing
lists
and
if
you
already
are
active
on
github,
if
you
have
opened
an
issue
or
created
a
PR,
create
an
issue
open
to
PR
that
way
around
people
are
probably
going
to
come
and
comment.
B
It
is
totally
okay
to
add
at
their
user
name
on
that
discussion.
That
is
100%.
Okay,
don't
be
surprised
if
they
don't
react,
because
some
reviewers
and
contributors
get
so
much
noise
on
their
github
notifications
that
they
just
won't
notice,
don't
take
it
personally,
there
are
meetups
in
many
parts
of
the
world
and
and
again
for
help
to
get
started.
We
also
offer
kubernetes
office
hours
again.
That
is
I
will
show
you
where
to
find
all
that.
B
So,
let's
see
here,
we
have
people
joined
on
slack,
I,
hope
all
right
so
on
the
main
kubernetes
website,
kubernetes
io
community
I'm,
going
to
endeavour
to
put
all
of
these
links
in
a
bundle
at
the
bottom
of
the
slide
deck
once
that
gets
submitted
to
wherever
it
is.
This
is
sort
of
the
the
part
where
I
was
in
fact
a
little
bit
behind.
So
this
is
the
schedule
of
kubernetes
community
meetings.
B
B
That
there
is
the
kubernetes
community
meeting
at
10:00
a.m.
now.
If
you
already
know
a
lot
about
kubernetes
and
you
have
an
idea
of
what
the
different
parts
are,
this
communion
meeting
is
great
to
attend
when
I
first
started
learning
about
kubernetes
I
attended
the
first
community
meeting
my
very
first
week
at
work,
and
then
I
said
this
I
can't
I,
don't
even
know.
What's
going
on,
so
I
didn't
attend
for
half
a
year
and
then
half
a
year
later,
I
attended
again
and
magically
everything
made
sense.
B
So
this
is
where
I'm
gonna
ask
you
to
be
patient
with
yourself,
because,
as
Josh
said
in
the
very
beginning,
it's
a
big
topic.
So
this
is
also
where
you
can
find
all
the
meetings
for
all
the
different
SIG's
and
working
groups
and
one
of
the
best
ways
once
you
know
where
you
want
to
contribute.
One
of
the
best
ways
to
do
so
is
to
find
out
where
which
sig
is
responsible
for
your
area
of
interest
and
go
to
a
meeting
a
lot
of
the
time.
There's.
B
Maybe
only
ten
people
in
that
meeting
and
they
will
see
you
and
they
will
ask
you
to
introduce
yourself-
and
this
is
an
excellent
way
to
find
mentors
and
people
to
help
you
out,
even
if
they
don't
work
at
your
company.
It's
even
if
it's
not
even
about
kubernetes
I.
Had
someone
from
seed
contributor
experience
spend
three
hours
of
his
time
to
teach
me
some
get
tricks
it
just
because
that's
the
kind
of
community
we
have
I
already
mentioned,
there's
kubernetes
meetups
all
over
the
world.
B
B
Cnc
of
meetup
good
idea,
your
slack,
where
on
slack,
sitcom
Trebek's.
Thank
you
that's
what
I
was
looking
for?
Yes,
but
yep,
CN
CF!
Absolutely
somebody
will
point
you
in
the
right
direction
and
I
happen
to
know
the
person
who
can
set
you
up.
So
you
can
come
talk
to
me
as
well.
Who
here
does
not
have
a
meet-up
in
their
area.
B
Alright,
if
you
are
on
Twitter,
you
should
follow
kubernetes
I/o
on
twitter.
Just
for
you
know
updates.
This
is
the
latest
one
I
think
maybe
I
don't
know
that
I
necessarily
want
to
refresh
my
Twitter
feed
and
then
Google
Groups,
this
one's
a
little
tricky.
Is
there
anyone
who
has
tried
to
join
the
mailing
lists?
B
Yeah
Oh,
a
couple:
people
cool
any
troubles.
So
let
me
just
kind
of
walk
you
through
here.
I
think
the
trick
is
really
that
you
need
to
know
which
groups
are
good
to
join
for
so
there's
the
kubernetes
dev
at
Google
Groups,
that's
for
developing
on
the
core
repository,
but
I
really
encourage
joining
the
kubernetes
users,
because
that's
where
a
lot
of
questions
get
answered
and
asked.
B
B
Awesome
I
might
have
to
tweak
my
notifications
actually,
but
that's
okay
I'll
go
ahead
and
do
that
later
so
you'll
see,
there's
there's
a
lot
of
questions.
Kubernetes
ingress,
that's
actually
something
that
was
relevant
for
me
for
work.
Last
week,
it's
a
it's
a
pretty
useful
thing
to
have
in
your
inbox
and
to
be
able
to
access
all
right,
I,
think
all
right
cool,
so
I
really
encourage
you
all
to
just
go
ahead
and
join
those
Google
Groups
right
now.
B
If
you
can
just
that
way,
you
have
it-
and
maybe
you
won't
remember
everything
from
today's
presentation.
So
this
way
you'll
get
an
email
being
like
hey.
How
does
ingress
work?
Oh
I
think
it
works
this
way.
So
all
right.
There
are
more
ways
to
stay
in
touch
with
the
community
than
these,
but
these
are
basically
the
biggest
and
best
ones
and
they,
yes,
they
do
involve
you
having
to
reach
out
and
talking
and
meeting
people,
and
this
is
overall
a
good
thing.
We
are
trying
really
hard
to
keep
the
community
from
becoming
this
thing.
B
A
Hello,
we're
hearing
this
yeah
there
we
go
terrific,
okay,
so
we've
already
referred
to
kubernetes
sig
several
times.
Six-Six-Six
stands
for
special
interest
group
kind
of
sounds
like
a
meet-up.
Doesn't
it
the
I
was
kind
of
amused
at
this
use
of
SIG's.
The
reason
that
we're
actually
using
the
special
interest
group
term
comes
from
the
IETF
was
copy,
after
that
anybody
here
involved
with
the
IETF.
In
some
way
we
got
a
serious
network
geek.
Here
you
got
it.
We
got
one
person
there
so
in
the
I.
The
idea
for
anybody
is
not
familiar
with
it.
A
This
is
the
organization
that
determines
the
International
specifications
for
all
of
the
networking
and
Internet
things,
so
HTML
standard,
an
email
standard,
an
ipv6
and
everything
else,
and
the
way
they
divide
up
their
group,
their
work
is
departmentally
into
SIG's,
and
each
sig
is
kind
of
its
own
sub
project,
with
its
own
workload,
its
own
individual
leadership.
For
that
sake,
now,
in
this
case,
in
kubernetes,
we
have
some
specific
things
that
we
talked
about
with
six.
A
So
right
is
that
every
sig
is
going
to
have
a
charter,
although
for
some
six,
their
Charter
is
still
in
progress
because
we're
kind
of
introduced
the
charters
last
year
say
sig.
Who's
gonna
have
don't
charter
each
second
kubernetes
is
going
to
be
responsible
for
a
set
of
code,
although
that's
not
necessarily
kubernetes
code,
it
may
be
code
for
other
things
like
testing
code,
for
example,
but
every
sink
has
a
repository
or
directories
or
other
bits
of
code
that
they
are
responsible
for
some
SIG's
have
their
own
repos
under
the
kubernetes
organization.
A
Every
sig
automatically
gets
a
slack
channel
set
up
and
automatically
gets
a
mailing
list,
and
currently
the
mailing
lists
are
all
in
Google
Groups,
although
that
may
change
within
the
next
few
months,
because
is
anybody
here
from
China
there's
a
problem
with
Google
Groups
in
China?
It's
blocked
so
but
right
now
all
the
mailing
lists
are
in
Google
Groups,
and
so
each
one
gets
its
own
mailing
list.
Sig's
are
expected
to
have
meetings
and
as
far
as
I
know,
they
all
do.
A
The
meetings
tend
to
be
either
weekly
or
every
other
week.
Most
of
the
meetings
are
on
a
video
conferencing
system
called
zoom,
which
we
found
is
good
for
allowing
anybody
who
has
the
link
to
join
and
supporting
up
to
several
dozen
participants
the.
But
this
does
mean
that
a
few
of
you
may
have
platform
issues
to
work
out
in
terms
of
getting
the
zoom
thing
installed.
A
For
what
it's
worth
for
anybody
who's
running
containerized
desktop.
We
actually
got
zoomed
to
create
a
flat
pack
for
further
video
things,
so
you
can
run
it
even
on
a
container
as
desktop,
and
then
some
of
the
cigs
that
are
larger
and
busy
and
responsible
for
more
stuff
also
have
their
own
sub
projects.
Under
the
sake.
A
The
now
I
was
looking
at
the
whole
list
of
SIG's
that
we
have.
There
are
a
lot
of
them
and
I'm
like
ok,
one
of
the
things
that
really
helps
to
understand
this
is
to
come
up
with
some
categories
for
the
different
kinds
of
cigs
that
we
have.
So
these
categories
are
mine.
These
are
official
categories
at
all,
but
I
think
it'll
help
you
to
actually
sort
of
navigate
the
whole
group
of
SIG's
that
we
have
keeping
in
mind
by
the
way.
A
The
other
thing
important
thing
to
do
is
that
we
are
creating
new
SIG's
and
then
some
SIG's
are
shutting
down
on
a
fairly
regular
basis,
not
every
week,
but
certainly
like
every
kubernetes
release
cycle,
which
is
like
every
three
months
or
so
you'll
discover
that
the
list
of
SIG's
has
changed,
because
the
technology
is
changing
all
the
time
and
because
the
technology
is
changing
what
we
need
to
spend
our
time
on
changes.
So
these
different
sort
of
areas
of
SIG's
are.
A
A
Cid
UI
is
a
good
example
of
this,
so
the
cig,
UI
people
actually
care
about
the
dashboard
in
the
API
that
the
dashboard
consumes
or
more
con
1-6
scheduling,
right,
they're
in
charge
of
the
core
kubernetes
scheduler,
as
well
as
the
scheduling,
API,
and
so
other
things
related
to
scheduling.
You
know
six
storage,
everything
having
to
do
a
storage.
A
Some
of
these
are
actually
some
of
these
are
actually
a
little
bit
deceptive,
because
because
there
is
they
work
in
some
SIG's
have
broader
or
more
interesting
responsibilities
than
you
would
necessarily
know,
because,
for
example,
you
would
say
from
the
name:
sig
off
is
in
charge
of
authentication
and
the
authentication,
API
and
tokens,
and
that's
everything
which
they
are,
but
because
of
the
history.
The
project
sig
off,
has
actually
become
the
sig
for
everything
involving
security,
except
that
sig
network
also
has
security
responsibilities
for
obvious
reasons.
A
Okay,
no
someone
I
want.
So
if
you
go
to
the
community
repo
the
better
place
to
actually
find
all
of
this
information,
rather
than
from
my
slides,
although
with
not
the
cat,
not
with
the
categories
because,
like
I
said
I
made,
the
categories
up
is
that
we
have
I
what
how
do
I
get
out
of
this
okay,
there
we
go.
A
The
sorry
I
use
a
Linux
desktop.
So
always
the
OS
change
the.
So
if
you
actually
look
through
this,
we
have
a
whole
master
list
of
SIG's,
and
this
is
kept
reasonably
up-to-date.
It
may
trail
reality
by
a
couple
of
weeks.
The
SIG's
are
responsible
for
updating
their
own
information.
Sometimes
if
things
change,
particularly
because
a
sigelei
drops
out
that
may
not
be
reflected,
it
may
take
a
couple
of
weeks
to
get
updated,
but
there's
a
reasonably
updated
set
of
information.
A
So
this
is
a
sort
of
master
list
of
all
of
the
different
things
and
what
they
do
so
like
I
was
talking
about
sig
off
now.
What
we
have
here
is
we
have
the
master
list
of
what
the
sig
is.
Who
are
the
leads
when
their
meeting
time
is
slack
in
the
mailing
list
and
everything
else
the
so
and
if
you
actually
click
through
in
this
okay?
Why
is.
A
Okay,
the
so
you
actually
can
get
more
information.
Every
sig
maintains
a
page
in
here
that
has
more
information
and
again,
you
know
so
we
go
through
here
for
our
cig
structure.
Right
is
you
have
the
meetings
and
that
sort
of
thing
now,
the
other
way
to
get
the
meetings
is
to
subscribe
to
the
kubernetes
calendar,
which
is
a
Google
Calendar,
which
I
recommend
I
kind
of
sort
of
recommend
that
you
do
I
mean
I
subscribed
to
it.
A
A
Lead
needs
to
approve
this,
and
this
is
where
you
get
this
list
of
leads
now,
depending
on
the
SIG's
Charter,
every
signe
to
have
leads
and
depending
on
the
SIG's
charter,
those
leads
may
actually
be
divided
into
two
different
kinds,
or
they
might
not
most
of
the
SIG's.
You
just
have
a
list
of
leads
a
few
SIG's
divide
out
the
chairs,
who
are
in
charge
of
making
sure
that
the
sig
has
meetings
and
that
they're
taking
care
of
their
issues
and
everything
else
and
technical
leads
who
are
in
charge
of
the
actual
code.
A
A
Now
what
most
people
know
Sid
Koster
life
cycle
from
is
Kubb
admin
right
which
they,
which
they're
in
charge
of
as
a
sub
project,
but
also
they
are
in
charge
of
everything
having
to
do
with
upgrade
and
downgrade
of
kubernetes,
so
they
file
upgrade
and
downgrade
bugs
against
all
of
the
other
SIG's.
So
there's
a
sort
of
meta
issue:
sig
API
machinery
is
in
charge
of
the
implementation
of
the
kubernetes
api
and
since
the
kubernetes
api
really
defines
what
kubernetes
is,
or
the
collection
of
api's
their
stuff
sort
of
cuts
across
everything
else
in
cig.
A
A
So
if
you
join
one
of
these
SIG's
expect
to
get
handed
something
almost
immediately
the
because
they're
busy
and
then
we
have
a
whole
set
of
SIG's
that
are
devoted
to
aspects
of
running
the
project.
The
kubernetes
project,
so
CID
contributed
experience.
You've
already
heard
a
lot
about
cig
architecture
is
in
charge
of
anything
that
defines
the
sort
of
architecture
of
kubernetes
and
components
and
how
they
interact
with
each
other.
A
Cid
product
management
is
in
charge
of
looking
at
things
that
for
long
term,
kubernetes
development
they're
in
charge
of
the
whole
kept
process
you
hear
about
later
on
cig
release,
which
is
actually
my
primary
sig.
So,
by
the
way,
it's
really
I
didn't
introduce
myself
either
so
I'm
Josh
burkas
I
work
for
Red
Hat.
My
job
is
kubernetes
community
manager
at
Red,
Hat
on
the
kubernetes
project,
my
main
sig,
and
so
here
we're
getting
into
the
whole
sig
thing,
which
is
you
notice?
A
Unless
you
don't
like
sleeping
the
so
sig
releases
actually
means,
like
my
main
sig
I'm
lead
for
the
111
release
team,
which
which
rotates
around
and
we'll
talk
more
about
that
later
and
then
suggesting
obviously
is
in
charge
of
all
of
the
tests
for
kubernetes
and
so
for
running
the
project.
So
you've
got
these
also
as
ways
to
get
started,
and
one
of
the
nice
things
about
the
meta
six
is.
A
If
you
do
any
feature
implementation
at
all,
you
will
end
up
being
a
contributor
to
sig
knox,
because
you
are
required
to
supply
documentation
for
that
feature
or
to
get
someone
else
to
do
it
for
you
and
you
will
hear
from
sig
Docs
if
you
do
not
supply
that
documentation.
So
it's
a
big
one.
Now
here's
where
we
get
into
a
little
bit
of
chaos,
simply
because
things
are
changing
so
where
things
are
changing
is
in
addition
to
the
SIG's.
A
We
have
the
second
concept
called
working
groups
and
there's
still
a
number
of
groups
around
that
are
called
working
groups.
We
are
moving
from
working
groups
as
a
concept,
so
a
working
group
was
a
we're
moving
as
a
working
group
from
a
concept
to
sub
projects
as
a
concept,
because
a
lot
of
the
relationship
between
working
groups
and
SIG's
and
the
mission
of
working
groups
wasn't
really
all
that
clear
now
here
for
these
things,
what
I'm
talking
about
is
for
stuff,
that's
really
specific.
A
So,
for
example,
helm
you
know,
helm
is
under
sig
Apps,
which
is
in
charge
of
application,
API,
etc.
But
it's
something
fairly
specific
under
Sagat
I
mean
actually
in
this
case,
helm
is
a
separate
project,
so
it's
really
charts
weirdly.
It's
actually
charts
that
are
the
sub
project,
because
we
have
this
charts,
repo
and
kubernetes.
A
A
Big
Data,
which
you
know
is
I,
involve
with
pretty
much
everybody
looking
at
streaming
and
data
processing
and
databases
and
everything
else
on
the
kubernetes
platform.
And
then
they
have
this
machine
learning,
which
is
currently
defined
as
a
working
group,
which
will
probably
be
a
sub
project
in
the
future
because
the
same
thing.
So
this
is
our
current
list
of
working
groups,
but
expect
this
to
change
and,
unlike
the
SIG's
SIG's
change
about
quarterly
the
list
of
SIG's
changes.
A
The
working
group
list,
in
terms
of
which
work
groups
are
active
changes
rather
more
frequently
because,
for
example,
when
you
have
working
groups
that
are
goal-oriented
that
they're
saying
hey
the
entire
goal,
this
working
group
is
to
implement
these
six
features.
Then,
when
feature
number
six
is
done.
The
working
group
dissolves,
and
so
these
change
around
a
lot
more
frequently
and
I'm,
actually
pretty
sure
that
we're
due
to
do
an
audit
of
these
because
I
know
a
couple
of
these
are
no
longer
at
all
active
the
plus
we're
changing
to
the
sub-project
program.
A
So
one
of
your
hardest
things
getting
started
in
kubernetes
is
figuring
out
which
sig
you
want
to
start
with,
because
because
you
know,
dividing
up
the
whole
universe
of
kubernetes
into
30-odd
cigs
that
we
have
a
lot
of
the
divisions
are
not
necessarily
going
to
be
obvious
and
figuring
out.
How
that
relates
stacks
you
work
on
may
require
a
little
bit
of
trial
and
error,
so
we
talked
about
figuring
out
what
it
is
you're
interested
in
contributing
to.
A
So
once
you
have
the
things
you're
interested
in
contributing
to
the
second
step
is
to
actually
figure
out,
which
cig
does
that
so
I'd
actually
like
to
have
a
couple
of
people,
because
we
do
the
exercise
earlier
I
like
to
have
a
couple
of
people
who
are
willing
to
actually
raise
their
hand
but
Healy.
If
you
know
what
you're
interested
in
working
on.
But
you
don't
know
anything
about
the
SIG's
I'd
like
you
to
raise
your
hand
and
I
will
try
to
pick
a
sig
for
you.
A
Robotics
so
like
kubernetes
controlling
robotics,
see,
that's
a
good
one,
see
I,
don't
even
know.
Who
would
do
that.
So
that's
one
of
those
cases
where
you
actually
want
to
pop
into
a
couple
of
general
community
forums,
because
I
don't
actually
think
there
is
anyone
currently
doing
that
you
know
and
it's
not
a
specific
Ziglar
sponsibility
and
that's
the
sort
of
thing
that
might,
for
example,
end
up
being
a
sub
project
under,
say:
sig
note,
unless
we
eventually
get
a
Szigeti
which
is
not
impossible.
A
Yeah
analytics
has
stuff
going
on
right,
so
they're
you
going
to
have
sig
big
data
or
the
machine
learning
sub
project
under
sig,
big
data,
one
more
yeah,
okay,
observability
metrics,
so
sig
instrumentation
and
a
whole
variety
of
sub
projects
under
them,
and
then
that
branches
out
to
other
projects
right
heap,
stir
prometheus
things
that
are
not,
and
so
here's.
Your
second
thing,
which
is
there,
are
a
lot
of
things
that
are
intimately
tied
in
with
kubernetes
that
are
not
considered
under
kubernetes.
A
A
A
And
that
is-
and
that
is
a
it's
a
very
good
question
right
and
this
that's
one
of
the
questions
that
you
need
to
ask.
You
know
you
get
in
there,
which
is
it
possible
that
yeah,
so
okay,
I'm
gonna,
read
the
question
for
the
video
which
is
Bob
was
pointing
out
that
some
of
these
things
can
get
divided
up
because
there's
sig
instrumentation,
which
has
all
of
the
instrumentation
and
ties
into
all
the
metrics
and
other
information
for
the
kubernetes
cluster
itself.
A
But
sometimes
statistics
and
instrumentation
for
applications
running
on
top
of
the
cluster
might
be
handled
differently.
And
so,
if
that's,
what
you're
primarily
interested
in,
like
you
can
say,
hey
I'm
gonna,
be
running
Cassandra
on
kubernetes
I,
really
care
about
monitoring
my
Cassandra
nodes,
etc.
Then
that
might
actually
fall
under
sig
apps
instead,
and
so
you
can
always
start
your
joining
a
sig
with
the
question
by
saying:
hey
go
over
to
the
SIG's.
The
slack
is
good
for
this.
A
So
sometimes
areas
of
responsibility
for
very
specific
things
can
be
a
little
odd
because
they
got
in
here
like,
for
example,
we've
got
this
sub
practice
and
a
couple
of
sub
projects
in
kubernetes
that
have
to
do
with
having
kubernetes
control
virtualization,
so
kubernetes
control,
VMs
and
for
largely
historical
reasons.
That's
ended
up
under
sig
node,
which
is
in
charge
of
the
individual
machines,
and
so
you
wouldn't
know
that
off
the
bat.
And
so
you
have
to
ask
questions.
A
So
now,
in
the
event
that
what
you're
really
focused
on
is
a
sub
project,
like
so
you're
really
focused
on
machine
learning.
You
want
to
also
join
the
parent
sig
of
that
sub
project
and
preferably
attend
their
sig
meetings.
If
you're
going
to
be
attending
meetings
at
all,
because
the
idea
is
that
the
sub
projects
sort
of
get
rolled
up
and
often
sub-project
stuff
will
get
discussed
in
the
mean
cig
meeting
or
in
the
main
sig
channel,
and
that's
why
we
have
as
a
concept
of
sort
of
sub
projects.
A
So
the
other
thing
is:
if
you
get
stock
for
the
people,
those
questions,
I
didn't
answer
and
you're
saying
which
CID
covers
this
again:
CID
contra
Becks.
What
we
do
that
right,
so
slack
channel
mailing
list.
If
you
want
to
ask
that
question
of
hey,
this
is
really
the
kind
of
code
documentation,
testing
concept,
implementation,
I
care
about
which
CID
covers
that.
That
is
one
of
the
best
places
to
ask
for
that,
and
we
will
go
and
try
to.
We
don't
know
off
the
bat.
We
will
try
to
figure
that
out
for
you.
A
You
know
like
if
you're
really
nervous
about
this
whole
joining
kubernetes
thing,
you're,
not
really
sure
to
talk
to
you,
don't
want
to
bother
the
sig
leads
and
you
ever
done
anything
before
you
can't
ask
us
to
do
that
and
I
have
done
that
for
other
people
and
gone
out
and
said:
hey
I'm,
gonna
talk
to
the
cig,
lead
and
hey.
Do
you
actually
cover
you
know?
Do
you
actually
cover
robotics?
A
You
know
if
somebody
was
doing
robotics,
do
you
know
anyone
else
is
doing
that
I
can't
actually
do
that
I
mean
if
you're
not
shy.
Go
ahead
and
do
that
yourself.
People
do
actually
respond
to
questions,
not
necessarily
in
a
timely
fashion,
because
everybody
is
super
busy,
but
they're
fine
with
questions
from
from
newcomers,
particularly
on
you
know,
particularly
for
asking
you
know,
is
this
you
or
not
so
now,
there's
a
second
part
of
the
project,
and
here
we
get
into
significantly
more
chaos.
A
But
if
you're,
actually
looking
at
something
and
you're
saying
hey,
it
makes
no
sense
whatsoever
that
this
particular
repo
is
under
here
you're,
probably
right,
it
does
probably
actually
make
no
sense.
It
was
probably
there
because
somebody
put
it
there
a
year
and
a
half
ago,
because
they
didn't
have
another
place
to
put
it
and
then
they
and
then
it
got
stuck
there
and
we'll
be
moving
it
eventually.
A
So
a
big
thing,
core
repository,
kubernetes
kubernetes
right,
github,
kubernetes
kubernetes,
everybody
found
that
on
their
own
right,
that's
the
easy
one.
This
also
gets
referred
to
as
k
/k
a
lot
of
times
in
people
offhand.
You
know
they
say.
Oh
that's
in
k,
/k,
that's
what
they're
referring
to
because
you
type
it
out,
but
that's
kubernetes
kubernetes
yeah,
and
that
is
where
the
core
code
is.
It
is
where
most
of
the
functional
code
for
the
project
is
it's
this
gigantic
repository
with
I.
A
We
under
the
kubernetes
organization,
which
I
am
representing
here
with
K,
slash
because
I
didn't
feel
I,
didn't
feel
like
typing
out
kubernetes
slash
800
times
in
the
slides,
but
that's
what
the
K
slash
is
there
the
and
also
people
will
refer
to
it
this
way
as
well
or
they'll
just
refer
to
it.
We
have
a
number
of
repositories
that
are
devoted
to
running
and
organizing
the
project,
so
this
includes
cake
immunity
which
is
actually
a
critical
repository,
because,
yes,
community
is
things
like
the
contributor
summit
community.
A
Slash
events
contributor
summit
right,
but
it
is
also
things
like
specification
proposals,
proposals
for
major
features
or
architecture
changes.
Let's
actually
go
to
that
so
because
you
notice
here
and
the
master
list
of
SIG's.
So
if
we
actually
go
like
if
you're
going
to
know
a
second
repository
k
community
is
a
really
good
one
to
know.
A
A
I
couldn't
think
it's
like
governance,
information,
the
code
of
conduct
and
a
lot
of
other
stuff,
and
this
is
not
only
information
for
you,
but
you
will
deal
with
in
an
ongoing
basis,
because
if
you
are
proposing
a
major
feature
or
architecture
change,
you
are
almost
inevitably
going
to
end
up
creating
a
document
within
the
cake,
immunity
repo.
In
order
to
back
that
up.
A
Features
the
features
repo
serves
a
special
purpose.
The
way
the
release
cycle
works
right
now,
if
you
are
proposing
a
feature
for
the
next
release
of
kubernetes,
because
you
think
you
get
it
finished
in
the
next
release
of
kubernetes,
then
you
file
an
issue
against
the
features
repo
as
part
of
that,
and
so
the
features
repo
is
just
for
tracking
steering
is
for
the
steering
committee
tests.
Infra
is
where
all
of
the
code
or
most
of
the
code
for
our
automated
testing
lives,
and
you
will
hear
more
about
the
automated
testing
later.
A
But
if
you
are
getting
involved
in
testing,
that's
where
you
go,
except
that
the
performance
tests
have
their
own
repo
because
they
run
somewhat
differently
from
the
tests
for
bugs
and
just
for
failing.
So
these
are
all
the
things
for
project
and
important
these
repositories,
regardless
of
where
you
are
working
to
contribute
to
kubernetes
these
repositories,
probably
things
that
you
are
going
to
end
up
are:
probably
things
are
going
to
end
up.
Doing
as
well
is
those
so
documentation
and
the
website
are
the
ones
that
you
going
to
touch
right.
A
Primary
one
is
actually
called
website.
Despite
the
fact
that
what
it
contains
is
documentation
again,
it's
because
our
website
is
our
documentation,
so
we've
got
the
giant
documentation
website
the
so
the
there's,
a
separate
repository
for
translating
the
documentation
in
Chinese
I'm,
not
quite
sure
why
that's
a
separate
repository,
but
probably
because
of
a
documentation
sprint
also
for
Korean.
A
The
some
of
these
are
special
their
particular
components.
For
example,
I
there's
some
samples
for
controllers,
API
servers,
I
that
sort
of
thing
KS,
dot
IO,
is
actually
a
set
of
sites
that
supply
developer
information.
So
things
like
the
testing
dashboards,
current
issue,
dashboards
and
a
couple
of
other
things,
the
end
we
even
have
a
template
project.
If,
for
some
reason,
what
you
are
doing,
somebody
tells
you
hey,
you're,
going
to
need
to
create
a
new
repo
for
that
we
have
a
github
template
project
for
what
that
new
repo
should
look
like
now.
A
Confusingly,
but
importantly,
for
this
is
remember,
I
said:
we've
got
this
gigantic
monolithic
repository.
That
is
the
main
kaykai
repository,
because
it
is
a
gigantic
monolithic
repository.
We
have
a
bunch
of
mirror
repositories
called
staging
repos
that
mirror
specific
sub
directories
that
are
kind
of
detachable
components,
and
these
exist.
A
The
staging
repos
exist
are
complete
mirrors,
basically,
the
same
PRS
get
applied
to
both
and
they
exist
for
build
and
test
of
those
components,
because,
if
you're
hacking
on
only
those
things,
and
particularly
because
there's
a
number
of
vendors
who
fork
these
things
like,
for
example,
client
go
and
you
know
a
lot
of
people
have
their
own
controller
like
OpenShift,
has
its
own
controller
I.
Think
tecktonik
had
its
own
controller,
that's
based
on
coop
control,
and
so
they
use
this
staging
repo
to
fork
it
out.
A
So
they're
not
forking
the
whole
code
just
to
build
that
controller,
but
this
can
be
really
useful
if,
in
fact,
you
are
say
working
on
the
kubernetes
api
server
for
your
sort
of
build
and
test
workflow
to
use
the
staging
repo
rather
than
the
whole
repo,
so
you're,
not
rebuilding
all
of
the
code.
For
the
one
thing
that
you
want
to
change
now,
a
few
of
the
SIG's
have
their
own
separate
repositories
for
things,
so
the
sig
release,
so
the
release
team
etc.
Has
their
own
repository
for
a
lot
of
release
related
stuff.
A
A
Well,
we'll
get
into
that,
and
then
some
of
the
cloud
providers
have
their
own
repos.
So
we've
got
a
surer.
Gcp
OpenStack
have
their
own
repos
under
kubernetes,
but
where's
Amazon.
Surely
they
have
AWS
specific
code
we'll
get
to
that,
and
then
there
is
a
whole
set
of
tools,
specific
tools
that
are
not
core
kubernetes
components.
While
some
are
core
Caribbeans
components,
some
are
not,
but
things
that
you
build
against
kubernetes
things
that
you
build
with
kubernetes
that
are
sort
of
separate
executables
that
are
available
for
in
repositories.
A
So
we've
got
kuba
admin
and
coop
control
and
the
things
like
cops,
a
whole
bunch
of
different
installers,
an
embarrassment
of
installers
and
the
things
like
helm
and
like
hipster
and
mini
cube
for
testing
and
that
sort
of
thing-
and
these
are
all
their
own
repos.
And,
for
example,
like
say
you
ended
up
working
on
mini
cube
like
trying
to
port
it
to
a
new
platform,
then
that
would
be
against
the
mini
cube
repo
instead
of
the
main
kubernetes
repo.
A
A
There's
a
repo
called
cube
incubator,
a
namespace
called
kuben
committers,
so
everything
we've
done
so
far
has
been
in
the
kubernetes
namespace.
The
second
interface
called
cube,
incubator,
there's
22
projects
on
it,
do
not
assume
that
any
of
these
projects
are
currently
maintained
code
because
most
of
them
aren't.
A
So
right
now,
until
we
do
a
cleanup
in
sort
of
rationalization
do
not
assume
that
the
location
of
a
particular
repo
and
which
namespace
it
in
is
indicative
of
its
current
maintenance
status
because
it's
not
someday.
Hopefully
we
will
get
all
of
this
reorganized
and
that
will
actually
make
some
kind
of
sense.
But
right
now
you
need
to
look
at
the
actual
contents,
the
repo,
the
current
activity
and
maybe
ask
somebody
in
a
cig
before
you
say:
hey
should
I
actually
be
modifying
this.
A
So
the
first
thing
is:
we
started
the
kubernetes
project
and
we
said
hey.
We
need
a
place
for
people
to
put
projects
that
might
not
go
anywhere
and
that
place
was
this
place
called
cube
incubator,
but
the
problem
with
kubinka
Bader
is
there
were
no
written
procedures
for
how
something
got
into
Quba
incubator.
Importantly,
there
were
no
written
procedure
for
anything.
Got
out
of
cooling
queue
better
right.
How
do
we
decide
that
something
is
good
enough
to
be
part
and
central
enough
to
be
part
of
core
kubernetes?
A
If
it's
not
going
to
become
part
of
korra
kubernetes?
Where
should
it
go?
If
people
stopped
working
on
it,
what
should
happen
to
it?
None
of
that
was
written
down
and,
as
a
result,
we
discovered
that
we
didn't
actually
agree
on
what
the
rules,
for
that
should
be
same
thing.
With
a
this
accumulation
thing
called
kubernetes
/
can
fit
contribs
contribs
single
repository
under
kubernetes,
again,
a
random
agglomeration
of
stuff.
A
A
The
important
thing
to
know
about
repositories
is
repositories
can
have
we're
going
to
teach
a
lot
of
rules
about
PRS
and
issues
and
other
things.
These
rules
all
apply
to
kubernetes
kubernetes,
specific
repositories
and
the
cigs
that
maintain
them
can
have
slightly
different
rules
based
on
their
decisions
like,
for
example,
the
helm
team
for
Helmand
charts
and
that
sort
of
thing
has
their
own
rules.
The
docs
team
has
different
rules
for
how
PRS
can
accepted
those.
A
You
will
be
learning
because
you'll
need
them,
but
I'm
not
going
to
teach
you
the
helm
team's
rules
right
now,
because
not
most
of
you
won't
be
working
on
hell.
So
these
can
different
some
things
actually.
First
tools
that
are
completely
separate
from
core
kubernetes:
they
don't
instantly
match
the
main
kubernetes
release
cycle
either
I
need
to
do
owners
files
and
then
we'll
break
yeah
yeah.
A
So
and
then
the
last
thing
is
one
of
the
things
we
are
moving
to,
but
have
not
yet
completed.
Yet
is
the
system
of
owners
files
where
within
directories
there's
a
file
called
owners
and
that
file
defines
who
owns
any
code,
documents
etc,
and
that
were
in
that
directory
or
sub
directories
and
who
gets
approval
on
it
and
that
approval
is
then
controlled
by
github
bots.
A
This
is
not
entirely
complete,
there's
a
bunch
of
stuff
that
still
is
under
certain
github
groups,
but
this
is
the
goal
for
this,
and
certainly
kubernetes
kubernetes,
and
a
lot
of
other
areas
is
controlled
by
these
owners
files.
So
now
we're
going
to
take
a
break
and
there
is
snacks
and
hopefully
coffee
is
there
coffee,
there's,
certainly
snacks.