►
From YouTube: Kubernetes SIG Docs 20181023
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 23 October 2018.
https://github.com/kubernetes/website
A
Hello,
everyone:
this
is
Tuesday
October
23rd,
and
this
is
the
weekly
meeting
for
kubernetes
sig
Docs.
This
is
a
fourth
Tuesday,
so
we
are
hosting
this
at
7:00
p.m.
Pacific.
In
order
to
accommodate
more
contributors
from
the
asia-pacific
region,
asia-pacific
regions,
there's
been
a
slight
mix-up
with
zoom,
so
I
think
our
attendance
is
artificially
low.
So
if
you
are
watching
this
after
the
fact,
I
deeply
apologize
all
right,
let
us
go
to
our
agenda.
I,
see
no
new
contributors
but
happy
to
see
you
all.
A
Okay,
then,
let's
move
on
to
our
agenda,
if
you
have
not
had
the
chance
yet
to
look
at
any
of
the
kubernetes
modeling
project
that
Andrew
Chen
and
Dominic
Tourneau
are
putting
together.
This
link
to
a
model
with
showing
the
modeling
project
for
high
availability
is
a
good
update,
good
place
to
start
so
that
is
available.
That's
something
that's
going
on!
That's
one
of
the
content
projects
right
now
for
cig
docks
is
increasing,
having
a
better
onboarding
experience
through
adding
modeling
to
documentation.
A
B
Sure
it's
pretty
straightforward,
I
went
to
our
project
at
kubernetes
website
and
I
am
I,
I
thinned
it
out
and
I
reduced
the
number
of
columns
and,
what's
there
is
you
know
what
I
think
of
as
the
top
six
or
seven
things?
And
you
know
people
can
add
things
if
they
feel
strongly
about
them,
but
I
thought
the
the
best.
B
The
best
approach
would
be
to
have
a
you
know,
six
or
seven
things
that
we
think
of,
as
are
our
priorities
for
this
quarter,
and
my
a
my
only
thought
was:
let's
get
rid
of
the
columns
for
in
progress
and
completed
because
we
don't
tend
to
keep
those
up
to
date
with
the
issues
themselves,
so
my
thought
is,
or
was,
let's
just
track,
whether
something's
been
taken
in
the
issue
itself
and
the
PR
and
let's
track
whether
something
is
complete
in
the
issue
within
the
PR.
B
But
Andrew
pointed
out
today
that
we
can
actually
set
up
in
progress
and
completed
columns
that
will
automatically
update
themselves
according
to
the
the
issue
and
the
and
the
PR.
So
I
think
that
if
we
can
get
that
set
up
that,
that
would
be
fine
but
I.
Just
you
know,
my
main
thought
was
I.
Don't
want
to
try
to
manually
keep
track
of
that
information
to
places.
I
just
would
like
to
keep
it
simple.
I
think
we
ought
to
have
two
projects.
Only
one
called
one
called
dock
writing
and
editing
right
now.
B
B
B
Everybody
see
that
yep,
okay,
so
here's
here's
a
project
called
duck,
writing
and
editing.
It
has
five
issues
listed.
I'd
say:
let's
keep
small
lists
until
we're
seeing
progress
on
those
unless
somebody
you
know
that
is
feels
strongly
about
something
they
would
like
to
do.
They
could
add
it
to
this
list
and
then
get
started
on
it,
and
then
the
other
project
is
to
express
where
I
think
we
ought
to
keep
track
of
upcoming
and
current
Docs
prints
and
then
at
the
end
of
a
given
Docs
print
could
clean
this
out.
A
So
I
am
on
board,
with
everything
that
you're
proposing
yeah
for
github
does
have
some
really
cool
project,
automation
tools
that
will
automate
things
like
in
in
progress
and
complete.
So
if
we
can
implement
those
I
think
that's
a
good
idea,
but
otherwise
I
agree.
Let's,
let's
let
the
the
issues,
let's
let
issues
npr's
be
self
tracking
in
terms
of
completion
and
openness.
I
do
have
a
question,
though,
about
number
of
projects:
Claudia
and
Junyi.
A
A
D
Yeah,
so
basically
what
we
were
hoping
to
do
in
the
last
meeting,
but
I
think
that
we
didn't
quite
have
quorum
for
that
kind
of
discussion
was
to
begin
to
potentially
or
maybe
not
kind
of
concretize.
What
exactly
the
the
sigdoc
stooling
working
group
does.
Thus
far
it's
been
a
very
kind
of
AG.
You
know
ad
hoc,
ragtag
effort
where
we
have
a
channel
of
people
who
are,
you
know,
enthusiastic
about
these
things
and
want
to
improve
the
lives
of
others.
D
D
What
I
wanted
to
sort
of
discuss
a
bit
with
the
group
is
what
you
all
would
like
for
us
to
do
if
you'd
like
for
it
to
be
a
more
a
more
settled
structure
with
its
own,
a
weekly
meeting
or
if
you
have
thoughts
on
what
the
appropriate
venue
for
for
our
discussions
and
for
our
our
proceedings
would
be
and
so
on
and
so
forth.
You
know
if
everybody
is
is
content
with
with
things
the
way
they
are
I'm
perfectly
happy
to
leave
them
that
way,
but
I
just
wanted
to
check
in.
A
A
B
A
D
B
Right
right
now,
I
know
that
I'm
one
of
the
owners,
maybe
the
only
owner,
I'm,
not
sure
of
the
kubernetes
incubator
reference,
Docs
repository
and
I-
think
I'm
fairly
soon.
We
need
to
have
someone
else
own
that,
or
at
least
someone
else
be
an
owner
of
that.
So
in
your
in
the
tool.
If
you
could
just
kind
of
keep
that
in
mind,
if
anybody
would
like
to
take
that
on.
D
Yeah
for
sure,
could
you
jump
into
the
the
sigdoc
stools
channel
and
maybe
provide
some
more
info
and
we'll
see
if
there's
an
enthusiastic
party
that
wants
to
jump
at
that
sure
yep
all
right
sounds
crazy.
A
A
All
right:
can
everyone
see
this
okay,
yep,
okay,
so
you'll
notice
here
that
there
is
a
poll
request
open,
107,
one
nine,
as
for
the
first
Korean
localization
work
on
the
dev
1.13
branch
and
you'll
see
that
it
has
this
label
here,
language,
/ko
and
that
was
opened
by
Jimmy
and
Jimmy.
Did
you
was
this
automatically
applied?
Did
you
manually
apply
the
label.
A
And
you
can
see
that
there
are
other
labels.
Probably
the
most
common
label
will
be
a
language,
/en
and
Steve.
If
you
remember
a
year
ago,
the
our
initial
rationale
for
farming
out
localizations
to
other
repositories
was
because
we
didn't
want
to
be
inundated
by
the
flow
of
PRS
that
we
couldn't
meaningfully
review.
So
the
nice
thing
now
is
that.
B
A
A
A
So
the
polar
the
issue
is
1
0,
682
and
juni,
and
Claudia
I
suspect
that
this
is
correct
for
the
Korean
team.
If
there
are
other
people
that
you
would
like
to
add
to
that
particular
management
team,
let
me
know,
but
for
for
folks
who
are
watching
this
on
the
Japanese
and
Chinese
teams,
if
these,
if
these
are
not
the
people
that
well,
if
this
works
for
you
great,
if
there
are
other
people
that
you
would
like
to
be
in
charge
of
long-running
branches,
please
let
me
know.
Issue
comment
is
great,
so.