►
From YouTube: K8s SIG Docs Meeting 20191008
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
A
A
A
If
you
have
any
question
about,
you
need
to
reschedule
it's
better
to
do
that
really,
rather
than
try
to
do
it
after
after
the
wrangling
week
has
already
started,
speaking
of
which,
if
we
look
at
the
schedule
and
see
for
October
20th
grad,
Topol,
yay,
Brad,
Spring,
Wrangler,
October,
27th,
Shema,
post
Andrew,
Chen
is
scheduled
and,
as
folks
may
know,
andrew
has
stepped
down
as
a
chair
and
has
completely
scaled
back.
His
involvement
with
sigdoc.
So
he's
not
going
to
be
available
to
wrangle
PRS
that
week,
so
we
need
a
replacement
for
October
27th.
A
C
A
Right
so,
oh
thanks
for
posting
the
agenda
into
the
chat
window,
much
obliged
I
apologize
that
the
agenda
is
a
little
thing.
Like
I
said
it's
been
sort
of
a
week
of
kashyap,
so
on
the
agenda
we
have
to
sort
of
main
areas,
one
starting
with
content
for
the
actual
Docs
and
then
two
pieces
to
talk
about
so
far
in
terms
of
process.
A
Pr
Wranglers
we
already
covered
so
I'm
gonna,
move
that.
So,
let's
talk
about
sorry
before
we
dive
into
it.
If
there
is
something
that
you'd
like
to
talk
about
in
today's
agenda,
feel
free
to
add
that
item
to
the
discussion,
yeah
feel
free
to
go
on
in
and
add
the
topics
that
you'd
like
to
talk
about
all
right.
So,
let's
dive
into
third
party
content.
A
We
need
to
get
reviewers
on
that
before
we
start
implementing
it
wide
scale.
So
the
first
step
is
to
put
together
an
actual
proposal.
Jim
has
linked
a
Google
Doc
into
the
agenda.
This
is
the
shell
of
a
cat.
This
is
the
the
kept
form
and
what
we
need
is
we
need
folks
who
can
fill
this
out,
and
some
of
that
will
be
it's.
It's
not
a
really
complex
job,
basically
you're
taking
feedback
from
the
third-party
content
issue,
which,
let's
see
1574
eight,
is
the
issue
we
post
a
link.
A
A
D
A
A
E
E
People
have
memed
about
them
hard
because
stephen
augustus
pushes
caps
hard,
but
they
kind
of
give
structure
to
the
project.
Really.
What
it
is
is
a
big
long
document
where
you
describe
what
big
change
you
want.
If
you
were
just
doing
an
internal
cig,
you
don't
need
to
worry
about
writing
a
cap,
but
any
user
facing
change
or
cross
cig
change
is
when
you
need
to
write
a
cap.
It
is
very
simply
a
proposal,
your
steps
to
fulfill
your
proposal,
how
you
are
going
to
test
your
proposal
and
then
what
you
would
deem
graduated.
E
So
a
lot
of
caps
tend
to
have
API
changes
where
you
go
from
alpha
to
beta
to
stable
and
you
have
to
define
what
that
criteria
is.
When
it
comes
to
the
release
cycle,
we
typically
look
at
what
caps
are
slated
to
land
in
a
release
and
then
we'll
reach
out
to
people
and
be
like
hey.
Is
this
actually
gonna
happen
or
not?
E
Now,
whether
that's
like
I
I,
came
in
halfway
the
conversation
so
I
don't
know
what
you're
talking
about,
but
if
that's
like
a
big
website
change
that
might
be
like
okay,
the
alpha
stage
is
the
like
website
can
be
viewed
by
certain
people
and
then
the
graduated
stage,
as
everyone
can
see
it.
You
know
something
like
that
again
there.
There
are
so
many
different
caps
that
span
such
a
broad
range
of
the
project.
You'll
probably
find
a
few
that
you
can
kind
of
model
yourself
after.
A
E
F
E
Release
started
September
23rd.
This
is
going
to
be
a
much
shorter
release
cycle
than
previous
releases,
the
main
reason
being
we
they're
holidays
and
there's
also
cube
con
in
the
middle.
So,
instead
of
like
14
weeks,
it's
more
like
12,
so
keep
that
in
mind.
Enhancements
freeze
is
next
Tuesday
October
15th
end
of
day
Pacific
time.
The
code
freeze
will
be
November
14th
end
of
day
Pacific
time,
and
that's
also
right
before
cube.
Con
Doc's
must
be
completed
and
reviewed
by
November
19th,
which
is
I
believe
right
in
the
middle
of
cube
town.
E
E
If
you
want
to
shift
that
around
please,
let
me
know
and
I
can
talk
with
Glynn
and
the
other
leads
and
maybe
shift
it
ahead
of
time
or
shift
it
later.
I
would
defer
to
all
of
your
wonderful
opinions
and
I
would
honestly
back
that,
because
docks
docks,
freeze,
kind
of
being
in
the
middle
of
cube
con
isn't
really
good
good.
E
A
E
D
F
F
Well,
they
turn
up
when
the
deadline
for
for
that
PR
is
which
is
like
a
week
before
the
docks
release,
freeze
and
I
feel
like
that
should
be
much
earlier.
But
here
is
my
placeholder
PR
get
contributors
who
are
writing
code
to
think
about
the
docks
and
it
lets
the
docks
people
think
about
what
the
docks
for
that
new
feature
looks
like
now.
It
might
be
far
too
late
to
change
that
for
this
cycle,
but
chasing
up
those
PRS
and
saying:
where
is
your
placeholder
PR?
Can
I
help
with
your
placeholder
PR?
E
Like
that,
so
what
I'm
gonna
do
first
I'm
gonna
talk
with
the
enhancements
lead,
see
if
there's
something
from
their
side
that
they
might
be
able
to
address
up
front
because
they're,
typically
the
ones
that
are
chasing
down
the
caps
and
seeing
who
who's
getting
into
the
release,
because
typically
it
goes
cap
docks
and
oro
cap
PRS
and
docks.
So
if
they
can
potentially
just
hey,
get
this
in
sooner,
and
maybe
we
set
a
date
for
that
sooner.
That
might
be
nice.
E
F
E
A
E
E
B
C
D
So
if
one
of
those
doesn't
make
sense
to
you,
what
they're,
looking
for
what
they're
more
or
less
expecting
out
of
us
I
think
we're
gonna
have
to
change
how
we
propose
the
cap
due
to
the
nature
of
what
the
caps
are
normally
used
for
kind
of
like
what
Zach
was
talking
about,
where
we're
talking
about
website
changes
versus
code
changes,
but
I
think
that
those
highlighted
areas
encompass
kind
of
what
they
were
looking
for.
Along
with
that
issue,
we
can.
We
can
come
up
with
a
unified
direction.
There
ya.
C
C
C
C
A
Okay,
cool,
thank
you
both
so
I
have.
Let's
move
on
to
process.
I
need
to
forward
this
on
Bob
Kalin
aka.
Mr.
Bobby
tables
sent
a
notification
to
the
chairs
and
tech
leads
list
for
cubing
ADIZ,
basically
asking
SIG's
to
clean
up
their
owners
files,
and
they
have
a
particular
tool
that
shows
you
which
owners
files
you
currently
belong
to.
So
I.
We
need
to
go
through.
We
have
enough
owners
files,
some
which
were
good
ideas,
some
of
which
were
half-baked
ideas,
some
of
which
I
look
at
and
like
what
was
I
thinking.
A
A
A
D
A
C
We
so
we'll
go
over
what
it
takes
to
be
able
to
contribute,
and
then
we
typically
will
help
them
through
certain
processes.
You'll
get
different
people
that
come
in
at
different
levels.
We
typically
want
them
to
have
already
come
in
and
signed
the
license
agreement,
because
that's
kind
of
annoying
if
they
don't
have
the
the
approval
to
actually
contribute,
but
if
we
get
them
to
that
spot,
we
can
typically
get
them.
C
I
guess
we'd
give
them
some
instructions
on
get
or
what-have-you,
but
ideally
we
show
them
how
they
could
contribute
to
Doc's
the
overall
structure,
and
we
typically
do
easy
things.
We
look
for
little
fruit.
A
lot
of
glossary
entries
are
typically
a
good
way
start
for
a
person
to
get
their
first.
Pull
request
is
to
go
add
a
glossary.
Entry
is
a
really
nice
trick
and
sort
of
the
overall
theme
is
to
talk
about.
You
know
getting
getting
folks
to
get
the
way
I
look
at
it.
C
Is
you
get
you
get
a
couple
things
you
you
of
course
get
the
folks
that
want
to
learn
how
to
contribute
to
Doc's,
but
then
there's
also
folks
that
we
can
try
and
funnel
get
into
the
top
of
the
funnel
are
folks
who
want
to
eventually
contribute
to
the
code,
but
they're
not
ready
for
that.
Yet
you
know:
I've
worked
in
open
source
past
seven
years.
C
It's
a
great
way
to
learn
how
to
contribute
to
the
code
is
to
start
with
the
docs
learn
the
docs
contribute
to
the
docs,
and
so
we
try
and
get
both
groups
to
to
show
up
at
the
sprints
and
be
able
to
contribute
the
other
place.
We've
used
the
doc
sprints
a
lot,
so
we've
either
done.
You
know
the
easy
glossary
type
things
when
we
were
in
Shanghai
or
Barcelona.
C
C
For
example,
in
Shanghai
we
had
we
had
the
Indonesian
folks
and
some
other
folks
there
that
needed
help
on
how
to
get
translation
done,
and
so
we
were
able
to
sit
down
with
them
and
talk
about
how
the
structure
is
for
the
different
languages
and
and
answer
their
questions,
because
we
we
had
the
experience
folks
theirs
as
well.
So
you
know
the
China
team.
C
The
Korea
team
are
very,
very
good
at
at
what
they
do
and
how
they
their
processes
for
how
they
translate
the
docs
and
helping
to
disseminate
that
knowledge
from
the
Korean
team
and
the
Chinese
team
to
other
teams
that
aren't
as
up
to
speed,
is
kind
of
something
that
we
can
sometimes
cover
as
well.
So
so.
C
C
F
C
Typically
will
have
a
theme
of
some
form
and
prep
of
what
we
want
to
cover
I've
seen
us.
Do
them,
hey
everybody
come
in
and
we'll
just
start
teaching
everybody
how
to
do
it
and
will
do
glossary
entries.
We've
done
that
before
and
then
lately,
we've
typically
started
out
with
a
nice
presentation
overview
of
of
how
to
contribute
to
docs
overview
of
the
area.
I
know
I
put
together,
I
can
I
can
go
dig
out,
I
did
a
nice
presentation,
I
think
I
stepped
in
for
Zach.
C
He
wasn't
able
to
make
one
of
the
trips
and
so
I
stepped
in
and
covered.
Oh
here's,
what
we're
gonna
cover
and
then
we
do
to
the
new
contributors
and
that
we
also
did
it
as
part
of
the
beginning
part
of
the
docs
sprint.
And
then
that
was
a
nice
way
to
set
the
thing
and
then
set
the
table
of
what
we
were
gonna
do
and
then
we
would
typically
have
groups
where
we
just
go
around
and
help
folks.
We
have
typically
enough
approvers
around
so
that
somebody
gets
real-time
gratification
right.
C
H
C
The
theme
was
typically
needs
driven,
so
the
so
we've
done
themes,
we've
done
a
couple,
different
themes.
We
did.
Obviously
we
can
do
glossary
and
nice
easy.
Just
you
Oh
easy
things
to
go.
Fix,
we've
done
translation
where
that's
made
sense.
The
other
theme
was
a
much
much
more
again.
Self-Motivated
theme
was
when
we
were
switching
from
Jekyll
to
Hugo
right
and
they
were
all
kinds
of
bugs.
So
that
was
a
everybody.
Here's
a
patient
go
find
what
schmuck
with
some
key
ours.
You
know
or
issues
I
mean
what
we
had
one
Doc's
print.
C
That
was
mostly
go
open
up
issues
because
of
you
know
we
were
halfway
through
that
process
of
converting
over
and
the
pages
were
just
not
in
good
shape.
So
the
idea
of
the
theme
is
generally
something
that's.
Here's
where
we're
gonna
be
careful.
It's
gotta
be
easy
enough
for
new
time,
new
new
folks
to
be
able
to
do,
but
if
we
can
line
it
up
with
one
of
our
critical
needs,
that's
what
we've
done
in
the
past
and
those
that's
the
magic
formula
you
want
and
I'm,
usually
a
good
weather
belt.
C
For
this
you
want
somebody
that
should
I
put
it.
You
want
things
that
would
be
very
easy
for
a
beginner
to
come.
Do
and
I
have
a
nice
gift
of
always
seeming
to
act
and
look
like
a
beginner
on
things.
We're
gonna
bring
those
away.
So
so,
if
I
feel
like
hey,
if
I
could
go,
do
this
out
of
Austria
entry
or
go
debug
the
page
and
go
you
know
open
issue.
C
If
it's
something
really
easy,
that
that
seems
to
be
the
thing
trying
to
shoot
for
too
much
and
say:
oh
we're,
gonna
go
revamp
some
huge,
complex
organizational
structure.
We
have
in
our
Docs
my
opinion,
and
that
has
not
been
as
successful
because
you
just
you
never
know.
Who's
gonna
show
up
and
really
the
odds
of
them,
ramping
up,
quick
enough
to
understand
all
that
structure
and
then
to
be
able
to
make
good
decisions
on
how
we
do
something
big
like
that
again.
C
If
the
purpose
is
to
try
and
at
the
conferences
we're
trying
to
get
new
people
in,
we
typically
avoid
those,
whereas,
as
our
group
of
experienced
folks,
we
couldn't,
we
have
jams
or
whatever
we've
done
in
the
past,
where
we
have
focused
on
things
like
that,
but
but
typically
not
the
conference's
were
we're
more
focused
on
gathering
new
people
to
get
excited.
But
a
theme
just
I'm
rambling
a
little
bit
there.
But
getting
a
theme
early
is
good
because
we
really
want
to
tweet
about
it
and
try
and
get
people
interested
again.
C
Yet
we
can
teach
you
that,
as
we
teach
you
how
to
contribute
to
the
docs
and
that's
how
I
always
sell
it,
because
I
don't
think
anybody.
We
typically
don't
get
as
many
people,
and
so
since
we
get
less
people
and
there's
many
of
us
there,
we
typically
can
give
them
very
one-on-one
or
one
two,
three
type
ratio
of
helping
people
who
otherwise
would
be
intimidated
or
like
well,
I
really
want
to
learn.
H
C
C
C
Perhaps
right
yeah
so
that
that's
an
interesting
idea
as
well
focus
on
a
concept
theme,
yeah
and
again.
The
other
thing
is,
you
know,
sometimes
it's
hard
to
get
people
to
stand
there
the
whole
day
I'm
just
thinking
out
loud,
but
sometimes
you
might
think,
okay.
C
Does
that
make
sense,
because
I
I
think
my
experience
has
been
it's
real
hard
to
get
that
newcomer
to
stay
there
all
day,
I
think
usually
by
right
after
lunch,
around
2
o'clock
or
1
o'clock,
they're
pretty
tapped
out,
it's
been
overwhelming
for
them
and
we're
kind
of
out
of
easy
things.
But
you
know
sometimes
we
might
think
hey.
You
could
have
enough
time
to
do.
First,
half
of
the
day
new
contributor,
easy
stuff.
C
D
C
D
Is
it
normal
that
we
would
have
a
dock
sprint
pretty
much
the
entire
day,
I
know
cubic
on
last
year
we
kind
of
had
some
smaller,
like
lightening
talk
sessions,
and
then
that
is
a
whole
nother,
I
added
it
to
the
bottom
of
the
agenda
here,
best
kind
of
where
I
want
to
go
with
this
discussion.
As
far
as
that
contributor
day
in
cig
docks.
What
do
we
want
that
to
look
like.
A
So
we've
tried
a
couple
different
models
for
timing
and
duration
over
the
past
couple
of
years,
and
the
Sprint's
were
I.
Think
we've
had
the
the
the
best
success
and
the
best
traction
have
been
where
we
started
the
dock
stay
with
the
contributor
day.
So
when
the
contributor
day
gets
started
the
in
the
morning,
starting
with
them
has
people
come
in
with
the
energy
in
the
morning,
they're
fresh
they're
ready
to
go
and
then
to
run
basically
into
lunch
and
maybe
a
little
after,
but
not
much
more
doing
a
sprint
for
a
whole
day.
A
I
think
people
like
pretty
much
have
have
done
their
best
work
by
lunch
and
providing
enough
providing
structure
for
the
morning
and
then
providing
like
more
opportunities
to
socialize
and
just
be
present
for
whatever
happens,
or
whatever
people
want
to
do
or
show
interest
in.
For
the
like.
The
last
two
hours
seems
to
be
the
magic
recipe,
and
one
thing
that
I
would
I
would
concur
with
Brad
I.
Don't
know
that
we're
in
competition
with
new
contributor
days.
So
much
as
we
are
one
venue
there
for
for
people
to
express
interest.
A
A
So
we
will
be
present
in
there
in
the
contributor
day,
space,
okay,
so
as
far
as
the
new
contributor
workshops
themselves,
so
typically,
the
way
that's
gone
in
the
past
is
there's
like
a
giant
slide
deck
that
goes
for
the
whole
day
and
the
people
from
different
SIG's
come
in
and
do
introductions
both
and
Brad
and
I
have
stepped
in
to
do
that
at
points
in
the
past,
I
think
we
usually
end
up
getting
allocated
like
10
to
15
minutes,
but
it's
usually
just
the
show
up.
This
is
who
we
are.
A
This
is
this
is
how
to
find
out
more
so
like
I
can
show
you
the
slide
deck
from
previous
coop
cons.
Basically,
what
I
do
is
I
go
in
I,
say:
hey
or
sick
docks.
This
is
our
repo.
Please
know
that
we
use
prowl
all
of
the
commands
that
you've
learned
to
interact
with
repoed
with
other
projects,
still
work
here,
but
we're
we're
the
Ginger
Rogers
of
of
kubernetes
repos.
In
that
we
we
commit
and
publish
from
master,
and
then
we
release
historically
to
branches.
A
D
D
C
So
we
typically
what
I
the
last
time
was
show
some
visuals
of
the
docks
and
show
people
are
Nestle
aware
how
much
we've
done
with
translation
so
showing
that
hey,
you
can
click
here
and
you
get
the
different
languages
and
what-have-you
I
think
just
showing
off
the
different
features
of
the
docks.
In
addition
to
all
the
stuff
that
Ben
Zack
mentioned,
that
we
always
do
in
our
10
to
15
minutes
seems
to
go
pretty
well
right,
so
we
want
to
leave
them
with
a
wonderful
impression
of
there's
a
really
great
set
of
docks.