►
From YouTube: Kubernetes Sig Docs 20180828
Description
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 28 August 2018.
https://github.com/kubernetes/website
A
B
A
Well,
welcome
everyone,
so,
with
this
meeting
time
usually
I
find
that
normally
we
have
the
agenda
and
we
talk
about
things
as
we
go
along,
but
with
this
meeting
time,
my
experience
so
far
has
been
that
there
tend
to
be
more
questions
at
the
end
rather
than
filling
in
the
agenda
upfront.
So
I
would
say:
let's
go
with
the
agenda
that
we
have
but
leave
more
room
to
add
agenda
items
at
the
end.
A
So
I
wanted
to
follow
up.
First,
with
an
update
from
the
last
monthly
meeting
at
the
APEC
Tom.
There
was
a
question
about
whether
or
not
the
localization
guidelines
were
up
to
date
and,
yes,
they
are
look
very
kindly
Luke
Perkins
very
kindly
submitted
a
PR
91-92
to
make
the
updates
to
the
localization
guide.
So
as
far
as
I
know,
our
localization
guides
are
our
guidelines.
Are
current
and
up-to-date
any
follow-up
questions
there.
Any
anything,
that's
outstanding
about
localization,
guys
that
we
need
to
cover.
A
A
E
Not
necessarily
a
proposal
at
this
point
I
just
kind
of
wanted
to
raise
the
idea
with
the
group
I
think
it
came
up
in
the
meeting
last
week,
but
because
of
the
write,
the
docs
conference,
we
weren't
quite
at
decision
making
quorum
or
so
to
speak.
So
yeah
I
think
that
the
basic
idea
that
I'm
that
I'm
sort
of
that
I'd
like
to
throw
out
to
the
group,
is
you
know
in
a
lot
of
our
meetings.
We
we
spend
a
lot
of
time
and
talk
about
documentation
strategy
and
we
talk
about
content.
We
talked
about.
E
You
know
on
Docs
on
writing
Docs,
as
opposed
to
as
opposed
to
to
netwo
Phi,
and
you
know
weird
Hugo
glitches
and
things
of
that
sort.
So
I
just
wanted
to
see
if
I'm
you
know,
I
would
be
happy
to
to
spearhead
an
effort
like
that,
but
you
know
I
I'm
perfectly
open
to
two
other
stepping
in
as
well
like
Andrew,
for
example,
who
I
know
who's
who's
done
a
ton
of
great
work
in
this
area.
A
D
I
think
it's
a
great
idea,
because
we
just
usually
have
too
many
things
going
on
so
it'd
be
great.
If
there's
like
a
work
group
that
was
focused
on
this
because
there's
definitely
some
things
that
need
to
be,
you
know
kept
up
and
addressed
and
I
think
it'd
be
good
if
it
was
just.
You
know,
a
small
group
of
people
that
were
interested
in
that
could
work
on
it.
Yeah.
E
And
I'm
thinking
a
little
more
concretely
that
you
know,
maybe
one
person
from
that
working
group
could
could
you
know,
provide
a
brief
status
update
during
the
cig
Docs
meeting
every
week
and
then
also
act
as
a
as
a
vessel.
You
know
if
people
have
tooling
and
infrastructure
related
concerns
that
they
could
raise
them
in
the
meeting
and
then
we
could
all
you
know
we
could
take
those
concerns
and
discuss
them,
discuss
them
elsewhere.
E
A
That
sounds
awesome
to
me.
It's
also
I
think
that
there's
enough
concerns
I,
like
Andrew
points
out
there's
our
tooling
chain
is
always
God.
It
always
has
ongoing
concerns
and,
like
once
a
week
may
not
be
often
enough
to
talk
about
them.
We
Frank
them.
The
the
needs
are
sometimes
more
immediate
and
having
a
more
direct
channel
for
communication
about
tooling
and
infrastructure
seems
like
it
would
be
a
good
idea,
so
so
Raji
I,
see
in
in
chat
that
you
would
love
to
join
the
working
group
for
tooling
and
infrastructure.
A
What's
what's
the
best
way
to
publicize
to
get
interest
Duke?
Would
you
be
willing
to
like
send
email
to
or
something
to
email
out
to
the
to
the
email
list,
and
maybe
like
post
on
slack
and
and
like
put
together
I,
don't
know
like
a
slack
channel?
That
seems
like
it's
going
to
be
the
best
way
to
do
that.
But
if
you
want
to
do
mines
like
grabbing
that.
A
Okay,
let's
move
on
to
talk
about
internationalization
repos
and,
let's
start
out
by
specifically
talking
about
updates
to
the
owners
and
owners
sub
aliases
files.
I
want
to
offer
my
thanks
and
my
congratulations
to
both
the
Korean
and
Japanese
localization
teams
for
updating
their
owners
files
and
their
owners
aliases
and
bringing
in
new
contributors
and
new
members,
so
the
communities
or
in
order
to
have
functional,
approver
and
reviewer
teams.
That
is
wonderful
news.
It's
awesome.
Some
congratulations.
A
A
A
But
Junie
would
you
is
there
anything
that
that
your
team
needs
in
terms
of
input
or
feedback
from
us
about
your
workflow
having
your
owners
and
owners?
Aliases
files,
updated
is
a
great
step,
but
is
there
anything
that
you're
encountering
any
problems
that
you're
running
into
any
challenges
that
we
could
help
with?
How
are
you.
C
Yeah,
we
didn't
use
the
sub-tree
Reggie,
you
recommended
people
because
it
is
too
complex
for
us,
so
we
are
currently
working
on
the
a
debut
112
branch
that
we
made,
which
is
based
on
the
website
release
one
12-inch
I
know
the
Frenchie
is
in
a
stable
now,
but
I
think
it
will
be
soon
stable.
So
currently
we
are
in
discussion
on
how
to
stay
up
with
the
of
team.
A
Awesome,
that's
I,
think
you
made
the
right
choice
about
subtree
like
subtree
is
way
too
complex
for
us
to
so
I.
Think
that's
I
think
that's
the
the
right
choice
to
make
there
I
think
so
how
you
is
the
stability
of
112,
a
challenge
at
all,
but
if
that
pose,
are
you
finding
the
instability
of
112
right
now
to
be
too
much
of
challenge
or
it
sounds
like
things
are
going?
A
C
A
C
F
A
C
A
A
A
A
A
C
How
can
I
sit
up
need
to
fight
to
full
leave
you
up?
Oh
great.
C
C
D
So
it's
it's
not
a
script,
but
there
we
do.
Thank
you
for
bringing
this
up
because
we
need
to
set
it
up
so
that
when
you
submit
PRS
to
your
repo,
it
will
show
the
previews
and
then
we
can
also
set
up
a
preview
site
like
URL.
So
you
can
always
go
there
and
see
what
the
preview
for
the
whichever
branch
yeah
Luke,
can
you?
You
have
access
to
the
of
our
net
left
eye
stuff
right,
I'm,.
E
Not
sure
but
but
I
can
check
with
you
after
the
meeting
yeah
it's
it's
super
easy
to
do.
I
can
do
that
in
just
a
couple
minutes:
okay,.
A
A
A
E
A
C
G
A
A
A
B
B
When
you
go
look
at
that
page
and
you
look
at
the
left
map
navigation
panel,
it's
very
misleading,
because
the
left
navigation
panel
only
shows
a
few
of
the
vendors
offerings
that
have
inline
instructions.
Basically
inline
instructions
for
for
how
to
you
know,
use
their
product,
and-
and
so
you
have
a
huge
list
and
pick
the
right
solution
that
essentially
are
not
showing
up
on
the
left
nav
bar.
B
And
what
have
you
that
are
there,
because
a
pivotal
person
was
trying
to
update
the
list
because
the
pivotal
product
was
incorrect
and
and
when
the
review
was
done,
it
was
oh,
we
shouldn't
let
this
go
in,
because
we
think
there's
a
whole
bunch
of
work
being
done,
and
my
concern
was
well.
If
there's
a
whole
bunch
of
work
being
done,
that's
great.
But
where
is
the
canonical
list
of
up
to
date
of
what
the
products
are?
B
Turnkey
hosted
cloud
what
you,
because
we
need
to
have
that
list
somewhere,
even
if
you're
redoing
the
navigation
or
what
have
you?
And
so
you
know.
If
you
go
look
at
the
poll
request
100
to
8
from
someone
from
pivotal,
my
inclinations
would
be
to
go
ahead
and
hit
merge
to
at
least
keep
the
pick,
the
right
solution
date
and
then,
if
there
is
more
work
going
on
to
fix
the
navigation,
that's
great,
but
at
least
we
have
a
canonical
page.
B
That
is
up
to
date
with
what
the
vendors
are
offering,
because
I
could
see
vendors
coming
to
us
and
getting
very
angry,
because
that's
where
all
the
money
comes
from
right.
These
people
have
distributions,
they
have
offerings,
and
you
know
it's
one
thing
for
the
documentation
that
need
to
be
updated,
because
you
know
things
change
or
what
happened
you,
but
my
guess
is,
you
know
the
marketing
crowd
and
the
people
that
that
kind
of
that
that
are
trying
to
to
monetize
kubernetes
would
really
really
like
us
to
keep
that
page
up-to-date.
If
that
makes
sense.
A
It
does
so
Cody
I
know
that
you
can
talk
specifically
about
updates
to
pick
the
right
solution.
I'm
gonna
dive
in
though,
and
can
it
give
the
the
intro
in
the
context
for
the
work
that
Cody
is
doing
so
this
is
it's
a
timely
discussion
because
the
the
pick
the
right
solution,
page
right
now
I
mean
need
the
entire
so
that
entire
section,
what
is
currently
labeled
getting
started
is
a
bed.
It's
not
just
a
bit
of
a
mess.
It
is
a
giant
mess.
A
The
entire
section
is
not
very
well
organized
content.
There's
willfully
out-of-date,
it's
it's
very
stale,
so
I
am
willing
to
entertain.
Brad
I
think
you
I,
think
you've
got
the
good
idea
and
that
we
should
have
some
sort
of
a
resource
page
that
lists
distributions,
so
I'm
getting
I'm
getting
a
sort
of
a
push
initiative
from
the
CNC
f2
highlights
kubernetes
certified
service,
all
right,
Casey,
SP,
kubernetes,
certified
platforms
and
to
prioritize
those,
but
I
do
think
that
you're
right
that
there
needs
to
be
a
kind
of
an
up-to-date
list
of.
D
C
A
H
D
H
D
B
Easier
for
me
to
say:
hey,
it's,
okay,
we're
gonna,
merge
it
in
and
understand
that
it's
a
big
ugly
list
today,
but
we've
got
your
most
recent
version
of
what
changed
with
your
pivotal
product.
For
example,
it's
on
the
page
and
understand
that,
and
so
we're
gonna
work
on
that
page
and
reorganize
that,
but
they
can
feel
comfortable
like
they
got
four
latest
updates
in
for
one
month
or
what-have-you
and
and
and
then
they
can
trust
that
we're
gonna
do
the
right
thing
organizationally.
However,
you
want
to
restructure
it.
B
They,
like
you,
know,
cuz
I've,
seen
product
name
changes,
everybody
a
lot
of
things
are
changing
from
so-and-so
container,
offering
to
kubernetes,
offering
just
fabulous
for
us,
so
I
want
to
get
those
changes
in,
and
so
so
my
thought
process
was.
Is
it
okay?
If
we
just
merge
locations
in
that
one
big
page,
and
then
you
have
them
up
to
date?
B
B
D
D
B
A
D
So
since
since
its
gonna
be
in
Shanghai
I'm
guessing
that
several
of
you
may
be
attending,
so
I
just
wanted
to
see
if
anyone
was
planning
to
attend
I.
Believe
it's
what
November
like
10th
through
the
13th
yep
or
something
like
that
yeah
and
then
I
Brad
I,
know
you're
going,
but
are
any
of
the
other
folks
who
are
on
now
planning
to
go.
G
D
Okay:
okay,
because
if
anyone
was
planned
to
go,
then
my
follow-up
question
would
have
been.
What
would
you
like
to
work
on
for
the
docs
print?
Because
our
our
original
idea
was
to
help
make
sure
that,
like
these
translation,
workflows
we're
working
correctly?
Because
you
know
a
lot
of
the
issues
that
you
brought
up
today
like
we
could
make
sure
we
get
them
fixed.
B
A
A
A
C
Korean
localization
team
had
a
presentation
at
the
local
kubernetes
YouTube
room
beat
up
last
week.
I
introduced
the
Korean,
realization,
team
and
I
expect
the
community
processes
of
neatly
within
the
scope
of
that
I
understand
and
Adelle
I
call
the
photo
contributors
and
I
think
they
walked
that
team.
That's.