►
From YouTube: Kubernetes Sig Docs 20180313
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 13 March 2018.
https://github.com/kubernetes/kubernetes.github.io
A
B
I,
don't
know
if
you
can
hear
me
or
not.
This
is
my
first
time
using
this
wonderful
device.
My
name
is
Tom
I'm,
just
joining
the
kubernetes
flex
team
here
with
Jared
and
Ryan
and
Steve,
and
the
others
just
nice
to
meet
you
all
I'm,
going
to
be
a
fly
on
the
wall
and
eventually
ask
a
lot
of
questions
that
will
demonstrate
a
legit.
Yet
I
really
am
now
a
good
man.
Welcome.
Thank
you.
Oh.
A
A
C
D
A
E
Just
briefly,
and
then
let's
also
come
back
to
that
when
Jennifer's
here,
but
what
what
I
hadn't
realized
about
that
the
spell
checker
is
that
it's
not
a
general-purpose
spell
checker.
It
just
uses
a
word
list
of
known
typos
and
so
I
I.
Don't
really
think
it's
the
appropriate
tool
for
English
text
and
Jennifer
chimed
in
in
the
PR
would
end
with
the
same
same
view.
So
let's
just
call
that
good
for
now
and
then,
let's
hear
from
Jennifer
when
she's
when
she
arrives.
E
A
Apparently
Ben
has
been
out
with
a
really
bad
case
of
the
flu,
but
I
spoke
with
him
and
he
says
that
the
plan
is
to
to
update
bootcamp
via
HTML
or
JavaScript
tag
instead
of
any
github
based
approached
he's
ready
to
start,
but
he
says
that
he
should
have
it
tested
and
a
PR
ready
for
next
week.
There's
a
related
issue
linked
in
the
agenda.
A
If
you
are
interested,
look
at
that
and
talked
about
home
moving
on
I
would
like
to
nominate
Brad
tocall
for
sig
Dux
maintainer.
Basically,
he
has
already
been
doing
the
job.
It
would
be
nice
to
give
him
actual
maintainer
power
and
not
just
the
cobbled
together
right
access
that
we
have
given
them
right
now.
A
So,
let's
big
thumbs
up
for
Brad
to
Paul
I
will
open
a
PR
and
give
him
maintainer
access
and
like
that
for
review,
right,
Oh
new
team,
so
I
put
together
a
new
github
team
for
kubernetes
blog
maintainer
x'.
If
folks
should
see
some
activity
around
new
folks,
getting
added
to
that
team
that
is
going
to
be
Sara,
Conway
Caitlyn
Barnard
make
our
trainer
Bob
radensky.
A
Basically
the
folks
who
have
always
been
maintaining
the
kubernetes
blog,
we're
just
bringing
them
into
the
into
the
kubernetes
website
to
github
workflow
and
getting
them
off
of
blogger
as
a
platform
that
migration
process
is
getting
near
the
end.
So
if
you
notice
a
new
team,
that's
what's
going
on
those
are
the
people
already
involved
in
it,
and
I
mentioned
it,
because
it's
from
mark
remarkable,
but
otherwise
unremarkable,
yes,
Joe.
C
I
just
want
to
ask
if
there
was
anything
that
to
her,
nor
anybody
else
you
did
were
pr's.
Most
of
them
are
still
marked
work
in
progress
and
I'm
happy
to
get
help,
but
I
didn't
know
what
to
do
or
how
to
support.
In
that
case,
thank.
A
You
that's
very
kind,
the
for
two
hoots
blog
migration,
I,
think
that
is
the
only
thing
like
the
little
tiny
piece.
That's
left
on
that
one
is
stripping
special
characters
out
of
file
titles
just
for
good
hygiene
purposes.
The
other
pieces,
the
other
to
open
PRS
that
we
have
for
blog
migration
related
stuff
are
the
owners
and
the
blog
guidelines.
A
A
Let's
see
all
right
migrating
by
creating
the
website
from
Jekyll
to
Hugo.
So
after
a
whole
lot
of
discussion,
we
are
going
to
proceed
in
terms
of
timing
for
that
migration
from
Jekyll
to
Hugo.
We're
looking
at
starting
migration
with
a
contractor.
The
first
week
of
April
that
is
Wanda
ten
is
scheduled
for
release
on
March
23rd,
starting
the
first
week
of
April
gives
us
buffer
for
any
slippage,
any
last-minute
fixes
that
need
to
happen
so
we're
looking
at
getting
started.
A
A
F
G
A
D
H
D
Then
communicating
that
to
the
rest
of
the
community
and
he
or
seems
on
board
with
what
we
do
so
I
think
you
to
come
up
with
schedule.
You
know,
and
that
was
just
everybody
if
you'd
be
prolific
budget
we
tell
and
then
just
get
started.
So
also
of
choice
is
to
meet
English
follow-up
meeting
with
Bjorn
and
Elvis.
All
that
thank.
A
A
A
F
What
attend
is
looking
good
ducks
pr's
wise
anyway,
and
I've
asked
for
some
help
with
a
straggler
that
came
in
overnight.
That's
currently
looking
to
merge
with
master,
but
it
looks
like
it
actually
belongs
in
one
to
ten,
it's
small.
You
know
it's
like
I.
Look
at
things
like
that
and
if
I,
if
I
can,
if
I
know
I
can
handle
a
manual
fix,
you
know
we're
good
to
go.
F
The
other
two
are
waiting
because
I'm
being
punked
Ilyas
about
tech
review,
but
I
would
be
willing
to
merge
them
now,
if
need
be
so
I
mean
it
has
already
gone
through
rounds
of
tech
review
and
the
last
bits
of
things
look
like
by
shooting
so
and
I
went
Steve
know
already,
because
of
course,
right
now
is
when
all
of
the
projects
and
hefty
out
are
landing
in
my
lap.
F
A
F
Things
are
okay,
I'm
trying
to
schedule
next
week
pretty
carefully,
because
we've
got
to
have
teal
on-site,
of
course,
but
I
will
be.
I
should
be
completely
clear
on
Monday
and
I've.
Let
folks
know
I'm
not
available
for
socializing
Tuesday
night.
Maybe
I
should
circle
around
with
you
Zack
just
because
you
did
1.9
on
to
make
sure
that
I
had
the
list
of
what
needs
to
happen
day
of
really
clear,
so
that
I
can
make
sure
I've
got
time
set
aside
for
that.
Otherwise,
I
might
need
to
ask
for
help
JLS
I'm,
afraid,
okay,.
A
F
F
What
I
wanted
I
wanted
to
I
mean
people
can
go
see.
I
wrote
an
extensive
comment
in
the
pull
request,
so
you
can
see
what
I'm
recommending
on
but
I'll
just
say
here
to
this
group,
who
may
not
all
have
looked
at
the
PR
yet
or
be
aware
of
the
issues.
There
are
already
excellent
spell
checkers
out
there
you
can
integrate
into
your
code
editor
locally.
They
work
beautifully
far
better
than
you
know.
F
There
may
be
some
confusion
about
how
to
use
these
spell.
Checkers
I
think
we
could
certainly
use
some
documentation
in
how
to
contribute
to
Doc's,
encouraging
people
to
use
spell
checkers,
but
I
think
that
misspell
is
really
a
tool
meant
to
solve
a
different
kind
of
problem
in
a
different
kind
of
environment.
F
That
said,
I
did
also
had
a
separate
comment
about
a
related,
but
not
identical
issue,
which
is
that,
in
addition
to
spell
checking
there
are,
you
know,
pros
linters
out
there
that
we
might
want
to
think
about
integrating
into
workflow
down
the
road.
This
is
the
kind
of
thing
we
need
a
working
group
in
a
proper
proposal
and
some
more
investigation
into
and
and
I
also
made
the
point
that
I
think
we
have.
You
know
the
kind
of
culture
shifts
that
we're
already
working
on
us
on
putting
in
place.
We
need
those
things
in
place.
F
First,
before
we
go
and
looking
about
ruling
at
all,
we
need
to
encourage
people
to
understand
the
style
guide,
better,
to
understand
what
spell
checking
means
and
how
they
can
do
it
easily
locally.
We
need
a
whole
lot
of
know,
sort
of
broader
based
community
awareness,
I
think
that
looking
at
this
tooling,
you
know
starting
to
think
about
doing
it
now.
F
E
So
Jennifer
it
am,
I
right
in
thinking.
I
think
this
is
what
you
said,
that
this
was
designed
for
going
through
code
files
that
have
comments,
and
them
is
that
right,
that's
what
it
looks
like
yeah
and
so
that
that's
why
they
use
a
fixed
list
of
knowing
typos,
because
you
can't
go
through
a
code
file
and
have
your
spell
checker
pick
up
every
variable
name:
that's
that's
in
code,
so
it
might
make
sense
to
restrict
your
spell.
F
It
looks
to
me
from
the
discussion
about
ven
during
the
misspelled
checker
in
the
original
it
looks
like
it
was
to
be
integrated
into
local
building.
Right
you've
got
your
spelling
errors.
You
know,
you
know
either
breaking
your
builder
at
least
spitting
out
warnings.
I
didn't
hang
that
far
right,
it's
true.
They
don't
have
to
build
locally
to
check
code
in,
but
you
are
encouraged
to
do
so.
F
So
you
know
it's
also
a
tool
that
looks
as
though
it's
meant
more
for
that
kind
of
iteration
and
again
do
you
know
the
reason
as
Steve
says
you
want
to
get
rid
of
false
positives.
It's
also
small
and
like
wait,
you
don't
want
it
slow
your
build
process,
so
it
addresses
a
whole
set
of
important
use
cases.
They
just
happen
not
to
be
ours.
Fair.
C
F
Agreed
and
that's
one
of
the
reasons
I've
tried
to
be
careful
about
saying,
look.
Misspelled,
looks
like
a
fine
tool
for
the
right
context,
but
you
know,
and
and
I
think
that
this
is
also
another
sign
of
just
where
we're
still
in
this
sort
of
cultural
shift.
Communication,
improving
communication
mode,
we're
in
all
kinds
of
ways.
The
docs
repository
does
not
work
like
the
code
repository
and
people
are
keep
tripping
over
that
and
the
more
we
understand
where
the
disconnects
are
the
better.
F
We
can
try
to
explain
why
they
happen
and
and
sort
of
sympathize
with
them.
You
know
I'm
not
when
I'm
complaining
about
I'm
trying
not
to
complain
about
people
submitting
PRS
against
the
wrong
Doc's
branch,
it's
confusing
if
you're
used
to
just
always
working
from
master.
You
know
in
the
code
repo.
So
it's
not
it's
not
a
problem.
Exactly
it's
a
communication
opportunity.
There's.
A
Create
a
solution
that,
if
approved,
would
have
required
very
little
actual
work
to
implement
from
the
community
at
large,
and
that
was
a
very
thoughtful
display
of
empathy
on
the
on
the
contributors.
Behalf
so
I
agree
Jennifer
that
we
should
be
a
few
sieve
and
praise,
even
as
we're
clear
in
our
rejection.
Well.
F
F
E
A
A
F
Think
that
I'd
like
to
defer
this
one,
because
Nick
isn't
on
the
call,
because
he's
still
in
the
release,
meeting
and
I
haven't
had
a
chance
to
talk
to
him
about
it.
How
valuable
this
suggestion
even
is,
is
based
in
part
on
some
assumptions.
I
need
to
confirm
with
him
and
I
also
feel
like
I.
Don't
want
him
to
people
like
a
rugs
getting
pulled
out
from
under
him
because
he's
been
doing
a
magnificent
job
trying
to
improve
their
release.
F
Note
process
for
1.10
under
very
constrained
circumstances,
so
my
thoughts
really
I
mean
it
came
out
of
conversation
with
Andrew
and
Steve
last
week
about
release,
notes
generally
and
so
I
think
they
need.
You
know,
sort
of
Nick
and
then
1.10
work
for
a
similar
context.
Okay,
though,
I'm
like
in
deferring
for
two
weeks,
depends
on
the
state
of
the
release
next
week,
but
I
will
take
an
action
item
to
talk
about
it
with
Nick
when
many
surfaces.
A
F
Not
necessarily
from
what
I
see
Nick
and
his
shadow
Noah
I,
keep
wanting
to
call
him.
Nick
and
Nora
Oh
Nick
I
know
on
have
gotten
more
release.
Note
labels
added
to
the
case
repository
so
that
really
so
that
pull
requests
and
issues
that
actually
require
a
release.
No
one's
a
user
facing
you
know:
here's
a
user
facing
feature
or
bug
fix
thing.
You
really
need
to
know
about,
so
that
those
are
better
flagged
and
can
be
better
sorted
so
that
we
can
use
that
as
a
start
for
automating
a
bit
better.
F
F
Steve
and
Andrew
and
I
were
brainstorming,
and
the
thought
that
we
had
was
that
if
we
could
start
training
developers
and
writing
better
release
notes,
that
would
be
a
piece
of
help
here
and
that
another
thing
we
might
do
is
be
part
of
the
pull
request
process
for
in
upstream
code
so
that
we
catch
in
felicitous,
PRS
or
improperly
tagged
PRS
early
in
the
cycle.
This
is
clearly
not
something
any
anybody
in
C
docks
can
take
on
much
there's
a
lot
of
work.
Hence
the
proposal
to
rotate.
F
A
F
I
F
Trained
in
you
know,
sort
of
translating
geek
into
English.
You
know
formally
on
there
I
mean
not
that
I
mean
like
Jase
is
you
know?
Jase
is
an
amazing
writer,
but
you
know
that
that
that
just
well
there's
still
this
perception
that
the
release
notes
are
unduly
burdensome.
Honestly
I
didn't
experience
it
that
way
for
either
1.8
or
1.9
crazy-making,
but
the
end
of
the
release
cycle
is
always
crazy-making.
F
A
J
A
You
are
our
PR
Wrangler
for
this
week.
Thank
you
very
much
in
advance
I.
If
you
are
looking
at
this
list
of
PR
Wranglers
and
you
are
interested
in
rain
PRS
for
the
good
of
the
cig,
consider
checking
your
name
to
the
list
and
if
you
are
new,
we
can
talk
about
what
PR
wrangling
involves.
But
Joe
heck
has
already
written
up
an
excellent
guide
to
PR
wrangling
and
the
honours
and
duties
incumbent
thereupon,
so
give
a
give
some
consideration
to
taking
a
rotation
for
PR
wrangling.
D
A
K
In
joining
them,
that
to
me
sounds
like
the
trickiest
part
is
okay
now,
whose
email
and
we
found
like
a
group,
email
or
something,
because
you
don't
want
it
to
be
your
email
on
to
my
email
and
then
you
know
I've
seen
how
this
works,
where
basically
we
will
share
the
counts
and,
and
whoever
has
it
you
know,
can-
can
feel
free
to
post,
which
is
nice.
You
know
any
of
those
say
the
maintainer
sir,
what
happened
so
yeah?
We
take
it
offline
and
figure
it
out.
Okay,
if.
A
A
Okay,
so
let's
talk
about
moving
documentation
away
from
or
moving
our
duct
set
away
from
hosting
OS
and
platform
specific
documentation
and
providing
links
to
provider
specific
or
platform
specific
documentation.
Instead,
I
talked
about
this
with
with
my
boss,
Chris
Anna
stick
at
the
CN
CF
and
he
was
very
much
in
favor,
so
I
think
we
have
the
blessing
of
CN
CF
in
moving
away
from
a
hosting
provider,
specific
content
in
our
doc
set,
and
this
is
something
that
we
talked
about
last
week
in
the
week
before
and
as
folks
were
encountering
provider
specific
documentation.
A
I
know
that
folks
were
chiming
in
and
saying,
like
Brad
I'm
thinking,
specifically
about
your
comment
that
it
feels
really
good
to
to
let
go
of
this.
So
is
there
anybody
who
is
there?
Anybody
who
thinks
that
we
are
taking
the
wrong
tack
by
moving
away
from
hosting
provider
and
and/or
platform,
specific
documentation
and
providing
links
instead,.
E
He
would
be
the
one
to
you
know
to
advocate,
for
maybe
keeping
some
sort
of
presence
in
our
table
of
contents.
I
talked
to
him
about
this
the
other
day
and
his
feeling
was
he
just
you
know
he
places
a
pretty
high
value
on
not
asking
people
to
jump
around
from
one
box
it
to
the
other,
and
he
just
wishes
that
in
a
perfect
world
there
could
be
some
sort
of
automation.
That
would
let
these
things
be.
E
J
A
A
On
the
CN
CF
side,
the
request
has
been
to
give
some
priority
to
kubernetes
certified
service
partners
and
kubernetes
certified
platforms
and
distributions,
and
so
I
think
we
can
keep
the
or
address
andrew's
presence
concern
just
by
providing
links
to
service
partners
or
certified
service
partners,
but
in
terms
of
automatically
populating
documentation
that
I
mean
that
comes
down
to
a
importing
and
mirroring
content
hosted
elsewhere.
I
feel
like
that
touches
our
stack
in
a
way
that
doesn't
necessarily
provide
a
whole
lot
of
benefit
for
the
return
of
labour
I.
A
D
H
D
H
D
A
Agree
so
I
noticed
that
andrew
has
joined
us
Andrea.
Is
there
so
we're
talking
about
removing
a
provider
specific
and
platform,
specific
content,
Steve
head
sort
of
shadow
shadow
puppet
into
you
to
say,
but
hosting
major
content?
Possibly,
is
there
anything
more
that
you
want
to
say
about
that
I
mean.
H
A
C
Since
you've
joined
us,
one
thing
I
wanted
to
put
into
some
thinking
and
background
key
for
you
at
some
point.
I
know
you
were
doing
a
bunch
of
analysis
on
metrics
of
the
contributor
experience
and
how
the
flow
of
people
utilizing
those
Doc's
kind
of
a
fall
from
an
analytics
point
of
view.
I
would
love
to
see
kind
of
a
results
of
that
in
some
fashion.
You
have
to
be
you
know
next
week
or
tomorrow
or
anything,
but
just
don't
want
to
miss
out
the
news
on
yeah.
H
Actually,
we're
I'm
just
starting
that,
and
it's
not
done
yet
so
I'll
keep
you
in
the
loop
because
we're
we're
first,
you
know
kind
of
make
an
assessment
of
what
our
analytics
are
now
and
you
know
what
can
tell
us
and
then
next
step
will
be
to
add
some
things
like,
for
example,
we're
thinking
about
adding
like
a
time-based
and
focus
based
beacon.
So
because
you
know,
oftentimes
people
will
leave
a
page
open
for
many
hours
or
days
and
in
traditional
analytics.
H
That
just
is
considered
bounce
like
because
the
session
will
time
out
and
that's
it,
but
it
so.
It
won't
tell
us
how
they're
actually
using,
but
if
we
have
like
a
beacon
that
will
refresh
you
know
different
time
periods
and
then,
when
the
page
is
you
know,
on
the
the
focus
is
on
us
on
the
page.
It's
on
the
forefront,
then
we
can
better
measure
like
if
they're,
using
our
Docs
like
long
term
and
leaving
it
open
in
a
tab
so
like.
H
If
we
can
add
things
like
that,
that
might
help
us
track
some
of
these
behaviors,
and
then
we
can
figure
out
based
on
that
like
we,
then
after
that
I
think
we
want
to
find
a
set
of
metrics
that
will
infer
the
kind
of
behavior
that
we're
looking
for
like
so
it's
like
multi-step
but
I'm
in
the
process
of
writing
up
the
plan.
The
proposal
and
I'll
share
with
you
guys.
C
Very
awesome:
it's
a
side
note
he
doesn't
make
to
this
meeting,
but
Matt
Farina
from
helm
has
been
doing
a
bunch
of
related
to
documentation,
hotel
and
it's
you
know,
kind
of
its
own
separate
thing,
but
he's
also
been
at
least
during
the
home,
something
so
we're
discussing.
How
do
we
track
this?
How
do
we
get
metrics
on
things
like
that,
so
anything
that
we
have
that
we
could
share
in
that
direction?
I
think
yeah.