►
From YouTube: Kubernetes Sig Docs 20181204
Description
Meeting notes: https://docs.google.com/document/d/1Ds87eRiNZeXwRBEbFr6Z7ukjbTow5RQcNZLaSvWWQsE/
The Kubernetes special interest group for documentation (SIG Docs) meets weekly to discuss improving Kubernetes documentation. This video is the meeting for 04 December 2018.
https://github.com/kubernetes/website
-----
10:41:00 From Brad Topol : when/where are meeting during KubeCon
10:45:34 From Brad Topol : http://bit.ly/kubernetes-summit
10:47:32 From Tom van Waardhuizen : Sorry, my mike was on
10:48:19 From Jared Bhatti : Thanks :)
11:02:18 From Jennifer Rondeau : Gotta drop — I’ll stop by sig-cli sometime, too
11:09:09 From Tom van Waardhuizen : kubecudgel
11:10:25 From Tim Fogarty : cuttlefish
11:11:45 From Jared Bhatti : I’ve got to step away early :( Apologies for missing the modeling concepts discussion.
A
C
A
A
A
Let's
see
there
was
originally,
there
was
a
note
about
misty
being
scheduled
for
next
weekend:
I
bumped
that
discussion
a
little
bit
further
down
in
the
agenda,
because
I
think
there's
more
to
talk
about
there.
So
we'll
come
back
to
that.
Don't
worry
see.
Let's
talk
about
coop
con
Seattle,
okay,
I'm
also
going
to
bump
this
further
down
the
schedule
because
it
is
more
to
the
agenda.
But
as
a
reminder.
Next
week
on
Monday,
we
are
part
of
the
contributor
day
at
KU.
Con
in
Seattle.
A
C
C
A
E
A
F
A
G
I
I'll
be
at
Q,
Khan,
I,
suppose
I'll
be
able
to
I,
probably
won't
crank
through
as
many
issues
as
very
typically
doing
in
the
PR
angler
I
in
general,
I'm
happy
to
continue
taking
on
that
responsibility.
I
had
to
skip
a
couple
of
times
because
I
was
actually
on
leaves
so
I
wasn't
even
working
for
Google,
so
gonna
back.
That's
a
welcome.
G
A
A
A
A
C
A
Let's
see
next
week's
meeting
so
Q
Con
is
next
week,
I
think
most
end
or
all
of
us
will
be
there.
What
do
we
want
to
do
a
better
weekly
meeting?
Do
we
want
to
defer
it
with
that
in
mind?
I'm
also
like
blf,
though
sorry,
the
Linux
Foundation
is
shutting
down
from
the
17th
through
the
end
of
the
year,
so
like
I
won't
be
around
for
the
last
half
of
the
year
and
I'm,
also
taking
like
the
first
half
of
January
off.
A
D
C
E
A
A
A
E
E
Organizing
at
the
contributor
summit,
because
I've
been
getting
in
through
the
code
of
conduct
committee
also
looked
like
specific
locations,
we're
not
all
together
defined,
that
is
to
say,
we
know
generally
where
we
are
and
where
we're
not,
but
specifically
where
we
are
where
we
is
anything
on
anybody.
Contributor
summit
at
least
yesterday
wasn't
finalized
I
guess.
H
D
H
D
H
I
A
The
contributor,
the
contributor
or
contributor
day
organizers,
have
for
us
perfect
as
far
as
our
actual
agenda
I
have
not
completed
that
yet,
and
that
is
totally
on
me.
My
plan
had
been
to
do
that
yesterday,
but
I
mean
my
initial
plan
had
been
to
do
that
last
week
was
waylaid
by
the
need
to
create
a
state
charter,
and
then
I
said:
oh
I'll
just
do
it
on
Monday
and
then
I'll
do
it
after
I'll.
Do
it
after
we
release
the
docs
and
that
never
works.
A
A
D
You
creates
the
placeholder
issue,
but
the
new
link
a
Google
Doc
to
it.
So
that
way
we
can
collaborate,
a
collaboratively,
edit
and
add
more
information
and
then
take
notes
in
that
Google
Doc
going
on,
but
it's
linked
to
from
that
issue,
because
that
way
we're
not
just
piling
onto
the
issue
suggestions.
J
Sorry
also
I
was
gonna,
say
FYI
like
in
the
community
calendar.
They
have
some
of
the
schedule
for
the
contributing,
because
there's
like
on
conference
sessions
and
other
things.
Okay,
so
you
can
check
out
activity
calendar
for
the
contributor
day
schedules,
but
it
doesn't
have
the
sig
Docs
login.
Yet
yeah.
H
A
A
E
H
A
E
A
E
D
D
A
I
I
could
see
that
going
at
the
top.
We
have
start
contributing
intermediate
contributing
advanced
contributing.
Next
topic
could
be
something
like
you
know.
What
we
don't
do,
I
prefer
not
to
use
the
anti
thing
I.
Think
of
that,
as
jargon
and
I'm,
you
know
my
personal
preference
is
not
to
use
that,
but
I
think
it
would
fit
nicely
right
there
after
advanced
contributing
what.
E
C
E
Which
I'm
not
gonna,
do
right
now,
because
I'm
trying
to
finish
lunch
and
get
ready
to
leave
in
a
few
minutes,
but
I
will
take
an
action
item
to
look
up.
We
have
contributing
to
the
right
the
docs
website
topic
as
part
of
the
website
in
part
of
the
repo,
and
we
drew
it
from
some
of
it
from
a
fairly
standard
set
of
contributing
guidelines.
That
includes
some
of
this
negative
stuff
in
more
positive
language.
So
I
will
look
that
up
and
see
whether
that
can
provide
a
helpful
model.
Also.
A
A
A
H
K
Topics
I
think
it
was
initially
driven
by
us
introducing
customized
into
who
control,
apply
and
customized
actually
having
a
lot
of
documentation
needs
and
so
how
to
lay
those
out.
And
so
this
is
what
I
put
together
and
I
intentionally
kind
of
just
said.
Okay,
how
would
I
read
and
vision?
This
I
was
maybe
had
no
preconceptions
and
was
pointed
at
the
rust
documentation
which
is
done
in
a
similar
format.
K
They
use
to
control,
but
have
a
project
set
up
with
the
directory
structure
or
repo
structure
and
and
they
need
to
know
how
to
set
it
up
well
or
they
use
it
with
its
build
tools
that
build
containers
and
then
kick
off
rollouts
and
these
sorts
of
things
and
how
to
provide
that
Indian
solution.
It
tries
to
be.
This
is
a
pretty
large
topic.
K
It
tries
to
be
comprehensive
and
what
it
does,
and
so,
instead
of
breaking
it
up
and
to
maybe
task
concepts
and
tutorials,
where
we
assume
that
maybe
a
variety
of
different
users
are
coming
in
with
different
goals
and
different
needs
and
having
different
formats
of
the
documentation
tailored
to
all
those
different
users,
instead
is
mirrors
a
book
format
where
we
cater
to
one
type
of
user,
which
is
a
user.
Who
wants
to
be
able
to
have
a
comprehensive
resource
on
how
to
how
to
use
this
tool
or
set
of
tools?
K
If
you
will
and
so
I
think,
one
thing
we're
going
to
talk
about
or
like
to
get
feedback
in
on
is
how
does
this,
how
this
integrate
with
the
main
Doc's
site,
some
some
goals?
I'd
like
to
have
are
to
keep
it
together
as
a
whole
unit.
I
would
like
to
be
able
to
facilitate
users
walking
through
linearly
and
saying
yes,
I've
read
the
book
on
this
topic
and
now
I
understand
what
there
is
to
understand
about
using
the
tooling
around
kubernetes
and.
K
K
K
Think
the
the
book
was
written
with
the
intent
that,
because
we
expect,
like
a
user
to
be
able
to
go
through
it
and
to
end
I,
try
to
make
each
chapter
flow
into
the
other
and
have
kind
of
a
logical
progression.
I
know
the
concepts
documentation.
Does
that
as
well?
But
I,
don't
think,
has
taken
quite
as
strong
a
focus
on
that
and
in
this
little
more
indexable
to
go,
find
the
concept
and
read
about
that
specific
thing.
I
Well,
I'm
gonna,
I'm
gonna
go
completely
backwards
on
what
I
said
before
before
I
thought
that
you
know
I
made
the
statement
that
I
think
all
documentation
should
live
in
one
place,
it
should
live.
It
kubernetes
died
out
now
I'm
having
a
second
thought,
which
is
we
should
treat
this
like.
We
should
treat
a
book,
that's
printed
physically,
so
you
know
if
someone
writes
a
book
on
kubernetes,
like
you
know,
Joe
heck
wrote
a
book.
Chelsie
Hightower
has
a
book,
others
have
a
book
I
I'm,
starting
to
think.
I
We
should
view
this
in
that
same
light,
that
this
should
just
live
somewhere
as
a
book,
and
we
should
all
get
really
familiar
with
it
and
link
to
it
or
link
to
portions
of
it.
As
as
we
can
enhance
our
dog's.
You
know
we
might
be
able
to
remove
some
of
some
of
our
Doc's.
That
would
duplicate
this,
but
so
that's
my
current
thought.
I'd
I'd,
rather
not
try
to
blend
it
into
our
Doc's.
Unless
we
do
two
things
that
would
sort
of
ruin
what's
done
here.
I
Those
two
things
are:
you
know,
return
to
the
to
the
organization
of
task
concept.
Tutorial
return
to
the
idea
that
it's
all
structured
around
asking:
what
does
the
user
want
to
do?
Not
not
what
tool
or
what
you
know
overall
situation,
the
user
is
in.
So
what
the
rest
of
you
think
about
that
that
this
could
just
be
something
that
has
its
own
life,
and
here
in
cigars,
we
don't
maintain
it.
We
don't
bring
it
in
into
our
website.
E
To
go
so
I,
but
I
do
have
some
thoughts.
I
mean
some
thoughts
about
Phillips,
separate
ears
and
thoughts
about
your
comments.
Just
now,
Steve
so
I'm,
just
gonna
toss
these
out
here
and
look
at
the
notes
when
I
get
back
and
what's
the
video,
because
I'm
real
interested
in
this
stuff
on
I
think
I'm
inclined
to
agree
with
you
Steve
about
having
it
live
on
its
own,
be
linked,
but
as
a
resource
that
we
link
to
and
as
a
resource
for
or
as
broad
an
audience
as
possible.
E
K
K
Do
I
do
try
to
think
that's
great
feedback.
I.
Do
try
to
do
that.
I'd
love
to
have
your
perspective
on
whether
or
not
successful
there.
Some
of
the
things
I've
done
here
is
good,
like
the
TLDR
of
just
like
here's,
what
you're
going
to
learn
about
so
you
can
skip
away
if
this
isn't
the
problem
you're
trying
to
solve
and
then
to
put
a
motivation
for
like
why
we're
why
we
have
this
page,
so
every
page
has
kind
of
those
pieces
and
then
I.
E
E
I
I
K
I
my
plan
is
not
this
just
to
be
in
my
book.
It's
really
60
I,
pitched
this
to
and
is
pretty
excited
about
it
and
I.
Think
the
likely
scenario
is
that
there's
two
or
three
maintained
errs
from
sig
CLI
and
that
the
that
the
sake
leadership
is
the
escalation
point
right
normal
with
the
normal
stress,
but.
K
K
A
great
question
I
mean,
I
think,
the
to
be
determined,
I
think
the
contribution
process
would
be
if
it
lives
in
60,
Li,
ku
control,
repo
go
file
a
PR
there
and
have
the
60
Li
folks
review
it.
If,
if
we
wanted
folks
to
be
able
to
contribute
to
this,
we've
want
the
process
to
be
the
same,
we
could
put
the
bits
in
the
docks
repo
and
then
we
can
even
have
it
hosted
on
the
game
same
data
pages,
similar
to
how
we
do
for
the
API
reference
Docs,
which
is
also
a
static
HTML
page.
C
I
K
Was
gonna
say
I
mean
maybe
has
a
if
we
don't
come
up
with
a
better
plan.
The
default
would
be
for
one
not
for
all
make
sure
this
is
hosted
someplace
on
some
website
somewhere
and
that
60
Li
has
the
appropriate
permissions
and
documentation
for
updating
it,
pushing
it
and
that
will
go
and
find
the
parts
of
documentation
that
are
either
insufficient
or
out-of-date
on
the
main
web
site
and
link
them
to
the
new
thing
and
then
going
forward
figure
out
what
the
best
long-term
plan
is.
If
it's
that
or
something
else,
okay.
C
H
So
so
from
your
book
point
of
view,
I
see
that
kind
of
flow
right,
they'll,
be
things
and
you'll
cover
and
then
maybe
they're
things
I
don't
know,
depending
on
the
style
of
the
book.
Maybe
they'll
leave
things
that
you
just
feel
like.
Well,
I'll
just
give
you
a
pointer
because
I
didn't
want
to
write
about
all
that
stuff
and
it's
so
well
covered
in
the
docs.
It
would
be
redundant
I
think.
The
more
interesting
thing
is
after
we
read
the
book.
H
Is
there
stuff
to
harvest
and
I
haven't
even
done
this
with
my
own
book,
but
is
there
stuff
to
harvest
that
we
figure
like
well?
This
is
really
good
to
add
to
the
docs,
because
the
book
did
such
a
great
job
of
covering
this
topic.
Do
you
mind
contributing
it
a
certain
portion
here
there
to
beef
up
the
docs
on
that
particular
topic
that
was
kind
of
how
I
argued
it
I,
don't
know
if
that's
all
for
naught,
but
that
was
kind
of
process.
I
went
through
I.
Think.
K
K
Some
of
this
stuff,
the
the
customized
documentation,
for
instance-
I-
don't
think,
there's
a
great
place
right
now.
It
definitely
doesn't
exist
on
the
cadance
website,
and
so
maybe
we
want
to
yeah
I.
Think
a
big
question
is:
do
we
want
to
put
that
put
sections
for
that
there,
like
if
there's
content
in
here
that
simply
does
not
exist
on
the
website?
Should
it
yeah.
D
D
I
The
cube
cube
control
content
looks
limited
on
our
site
because
it's
not
in
there
as
cube
control
content.
It's
it's
in
almost
every
task.
In
our
tasks
section
you
do
the
task
and
at
some
at
some
point
you
use
to
keep
control.
So
that's
been.
The
approach
we've
taken
is
to
you
know,
ask
what
do
you
want
to
do
and
now
here's
how
you
do
it
and
Cube
control
is
going
to
be
involved.
H
Mean
I
mean
I
think
what's
differentiating
about
the
Phils
work
here
is
as
I
look
at
it
is.
There
is
a
need
to
want
to
be
able
to
go
through
just
Kubb,
cuddles
soup
to
nuts
and
and
see
all
the
features
you
know.
I
saw
the
nice
thing,
Rizzo
Oh
wide,
here's
what
this
means
and
it's
sort
of
like
a
different
view
into
how
you
want
to
proceed
through
and
that's
where
I
think
it
provides
value.
H
And
then
there
may
be
some
topics
in
here
where
he
does
end
up
wanting
to
link
for
more
detail
into
our
dogs,
I'm
guessing
but
but
he's
providing
a
differentiated
view
for
somebody
who
has
sort
of
a
different
purpose,
which
is
I
really
want
to
learn
everything
about
coop
Cuddalore
coop
control.
Maybe
the
first
thing
is
how
Brad
should
properly
pronounce
it.
Even
though
he
doesn't
that's
right,
I
keep
getting
every
time
I
do
it.
H
B
H
I
mean
so
to
me:
it's
you
know,
you
write
a
book
because
you
think
you've
got
something
that
that
differentiates
and
provides
some
value
and
how
you
want
to
present
it
and
and
I.
Just
by
looking
at
it,
I
see
that
and
I
just
think.
It's
just
a
matter
of
getting
the
procreating
SPAC
and
forth
you
do
everybody,
a
good
service.
Does
that
make
sense,
yeah.
K
Like
that
one,
maybe
one
question
which
is:
let's
say
a
year
from
now.
We
say
you
know
what,
like
the
the
experience,
is
disruptive
having
it
as
a
book
like
because
it
does
belong
on
the
caves
website
having
it
had
as
a
separate
thing.
Is
that,
like
we're
not
really
committing
to
that
right,
like
it's
not
really,
gonna
be
disruptive
experience
to
just
read
aside
how
we
want
to
have
structured
things,
I
think.
I
H
A
K
H
H
J
J
Planning,
that's
fine
I
will
we're
planning
to
give
an
update
so
I'll
when
we
have
that
Google
Doc
up
and
stuff
I'll
I'll
submit
proposals
so
that
we
can
give
a
little
a
project
update
while
we're
there
and
then
like
we're
working
on?
Oh
so
we
just
put
out
another
blog
post
called
the
mechanics
of
kubernetes.
So
please,
if
you
have
any
feedback,
that's
welcome.
B
J
Then
we're
working
on
another
one:
that's
the
scheduler
and
I'll
set
the
contributor
summer.
We
will
try
to
propose
for
one
of
the
unconference
sessions
sort
of
an
in
depth
thing
about.
You
know
the
scheduler.
It
served
as
this
case
good
as
a
case
study
for
doing
systems
modeling.
So
hopefully
we
will
be
able
to
do
that
as
well,
so
that
I
just
want
to
give
those
quick
updates.
A
Yeah,
thank
you.
I
think
we'll
have
plenty
of
time
at
@qu
con
to
to
do
as
much
review
as
you
would
like
to
do
so.
Yeah
I'll
get
there
the
Google
Docs
set
up
and
we
can
start
wrangling
the
specifics
for
for
the
agenda
in
there
cool
all
right.
That
is
the
end
of
our
agenda.
So
far,
is
there
anything
else
that
folks
would
like
to
discuss
in
the
time
we
have
left
you.
A
I
suspect
we're
all
kind
of
worn
out.
It's
been
a
heck
of
a
year,
it's
the
holidays,
so
this
is
my
last
meeting
of
the
year,
so
I'm
simply
going
to
say
thank
you
to
everyone.
It's
been
just
a
joy
to
work
with
you
over
this
past
year,
looking
forwards
next
year
and
I
hope
the
season
brings
you
and
yours
all
the
very
best.