►
From YouTube: Kubernetes Sig Docs 20190129
Description
Meeting notes: https://docs.google.com/document/d/1zg6By77SGg90EVUrhDIhopjZlSDg2jCebU-Ks9cYx0w/edit#
The Kubernetes special interest group for documentation (SIG Docs) meets weekly to discuss improving Kubernetes documentation. This video is the meeting for 29 January 2019.
https://github.com/kubernetes/website
B
A
C
No
I,
don't
know
you
I,
don't
think
I
know
many
of
the
rest
of
the
folks
on
this
call.
I
am
doing
kind
of
I
want
to
contribute.
I
also
tried
to
land
a
very
significant
project
in
kubernetes
overall,
which
is
support
for
Windows
containers
in
kubernetes
and,
as
you
can
imagine,
requires
a
new
node
type
to
run
Windows
containers
and
has
significant
sort
of
UX
implications.
So
I'm
in
the
process
of
trying
to
understand
how
Steve
doctor
works,
how
to
best
make
sure
we
do
the
right
things
and.
A
A
See
familiar
faces,
Dominic
welcome,
back
focus
on
welcome
back
all
right.
Let's
move
on
to
updates
reminders
and
housekeeping
so
sick,
docs
approver.
Excuse
me:
sig
Doc's,
approvers
I
put
up
the
PR
Wrangler
scheduled
for
q1
q2.
If
you
look
at
that
schedule
and
are
less
like
no,
no
that's
wrong.
You
have
the
power
to
switch
out
your
schedule
with
someone
else.
A
A
Let's
see
so
for
the
agenda.
Steve
I
haven't
it
from
Steve,
saying
he'll
be
late
to
the
meeting,
but
I
imagine
this
is
Steve's
reminder
to
at
least
partially.
So,
let's
just
a
reminder
to
take
a
look
at
the
project.
The
repo
project
that
Steve
has
set
up
for
content
that
needs
review
that
we
agreed
for
that.
We
agreed
met
the
priorities
for
q1.
A
Some
folks
have
been
grabbing
PRS
in
that
project
and
assigning
themselves
to
it.
That
is
awesome.
Thank
you
very
much,
but
there
looks
like
there
are
still
a
couple
of
issues
in
that
project
that
haven't
been
cleaned
yet
so,
if
you're,
a
new
contributor
Craig,
this
might
be
a
great
place
to
at
least
take
a
look
at
those
issues
and
decide
if
that's
a
place,
if
any
of
those
are
places
where
you
want
to
dive
in
and
take
a
look
at
the
particular
requirements
and
the
particular
technical
knowledge
required
for
any
of
those
PRS.
A
If
you
see
something
you
like
feel
free
to
assign
yourself
to
it
or
just
to
leave
a
comment
on
the
issue
cool
and
if
you
have
any
questions
about
that,
you
can,
if
you
have
u-joints
like
yet
Craig
I'm
on
this
back
to
awesome
and
you
can
feel
free
to
reach
out
and
grab
one
grab.
One
of
us
for
health
inside
questions
about
that.
A
Take
a
look
at
that
all
just
really
quick
yeah.
It
looks
like
we've
got
about
three
three
issues:
top
level
controllers
concept,
guide
deployment,
documentation.
We
need
better,
more
accurate
documentation
for
replica
sets
and
specifically
naming
naming
and
replica
sets
and
an
update
to
the
replica
set
concept
topic
so.
A
F
F
But
but
I
I
mean
wait,
I'm
glad
you
you
jumped
in
I
happen
to
have
seen
that
one
and
I
was
gonna
point
out.
It
looks
like
maybe
the
issue
needs
to
get
assigned
cuz.
It
is
actually
in
flight.
It's
not
like
waiting
for
somebody
to
claim
it.
Okay,
but
that's
that's
housekeeping,
but
we
should
maybe
get
that
clear
that
yeah.
A
A
F
Sorry,
you
were,
you
were
talking
about
some
of
them
and
I
was
just
thinking
wondering
whether
if
and
Reno
and
Steve
are
meeting
with
JD
to
talk
about
replica
sets,
whether
it
would
make
sense
to
do
a
little
bit
more
brainstorming
around
deployments
at
the
same
time
since
they're
so
tight.
Well,
since
replica
sites
are
so
tightly
coupled
to
deployments.
F
F
This
just
happens
to
be
an
area
that
I
banged
my
head
against
for
a
long
time,
because
there's
the
whole
replication
controller
replica
set
model
that
JD
is
already
addressing,
and
so
it
seems
like
there's
some
tight
coupling,
so
it
might
be
worth
at
least
discussing
and
I
agree
with
Zach
absolutely
about
the
figuring
out
ways
to
surface
these
and
get
them
assigned.
But
I
just
seemed
like
a
start,
given
the
tight
coupling,
possibly
and
if
it
doesn't
work.
F
E
Think
we
also
need
to
figure
out
kind
of
what
are
the
impediments
to
people
wanting
to
contribute
like
like
I
know,
for
myself,
like
bandwidth,
is
a
key
one,
because
I
have
a
lot
of
stuff
going
on
right
now.
So
I
can't
like
take
on
additional,
like
writing
tasks
and
I,
wonder
if
it's
the
same
for
everyone
or
if
there
are
also
other
issues.
I
know.
G
A
A
A
It's
still
a
rough
start
in
some
ways
to
figure
out
how
we've
got
Doc's
organized.
What's
the
what's
the
best
possible
way
to
contribute
who
to
chase
down
for
specific
tech
information
like
I,
think
about
you,
know,
I
I
still
don't
know
like
if,
when
I
look
at
a
particular
piece
of
functionality,
it's
not
always
immediate.
The
obvious
to
me
like
which
cig
is
responsible
for
that
feature.
A
Development,
so
maybe
like
providing
helpful
pieces
like
that,
but
also,
maybe
maybe
taking
time
to
not
just
have
a
PR
Wrangler
schedule,
but
like
a
like
a
mentor
schedule
and
I,
don't
want
to
sign
us
up
preemptively
for
what's
going
to
be,
what's
going
to
require
some
really
thoughtful
and
intentional
work
around
mentorship.
But
I'm
saying:
let's:
let's
look
down
that
road,
because
I
think
I
think
the
lack
of
mentorship,
I,
think
the
lack
of
sort
of
active
presence
and
active
help
is
a
barrier
to
contributors.
It's
not
because
we
don't
want
to
help
contributors.
A
It's
because
we're
just
not
set
up
to
do
it
well,
and
so
that's
what
I
see
do
other
folks
agree.
Do
you
see
like
completely
different
things,
how
to
folks?
What,
if
folks
think
about
that?
What
do
folks
feel
about
that
about
the
idea
of
providing
active
mentorship
to
increase
this,
to
make
it
easier
for
you
like
new
and
first-time
contributors.
H
G
B
You
know
right
at
the
very
top
of
contribution
guidelines
or
in
in
slack
or
something
you
know
as
soon
as
you
introduce
yourself
in
slack,
for
example,
as
soon
as
you
introduce
yourself,
you
know,
whoever
is
you
know,
whoever
are
the
the
mentors
on
call
that
week
immediately
just
send
someone
a
message
and
say:
hey
welcome.
Thank
thanks
for
joining
us.
You
know,
can
I
have
it
can
I
help
you
get
started.
B
I
A
A
The
speak,
just
speaking
anecdotally
I
know:
we've
had
like
so
I
have
messaged
a
couple
of
the
new
folks
who
have
joined
this
week
and
what
I
noticed
is
that,
basically,
all
of
their
questions
are
answerable
yeah.
They
have
been
answered
in
the
contribution
guide,
but
having
a
human
to
say,
hey.
This
is
the
contribution
guide,
and
this
is
for
you,
the
particular
question
you
ask.
This
is
where
you
visit
the
specific
section
that
you
look
at
just
having
that
human
interaction
seems
to
be
really
valuable.
A
A
A
So
what
that
looks
like
exactly
yet
is
still
in
process,
but
I
want
to
put
it
out
there
that
if
you
are
interested
in
being
a
chair,
this
is
a
great
time
than
maybe
like
think
about
your
interest
and
like
if
you,
if
that's
something
that
you're
interested
in,
come
and
talk
to
one
of
us.
It's
not
an
automatic
commitment
like.
If
you
talk
to
us,
you
know
like
tagged
by
the
National
Wildlife
Society
and
you
won't
be
like
radio
tracks
or
anything
like
that.
A
Just
you
know
like
raise
raise
your
own
visibility
so
that
we
can
include
you
in
the
conversation
so
obviously
to
be
a
chair.
You
have
to
be
an
approver,
but
you
know
if
you're,
not
an
approver
yet
and
you're
interested
in
what
that
path
would
look
like.
That's
also
a
good,
a
good
chance
to
think
about.
Well,
what
would
the
path
from
like
new
contributor
to
chair
look
like?
A
A
A
I
could
do
it
like
right
now
in
less
than
five
minutes,
the
the
challenging
piece
is
figuring
out
admin
permissions
because
I
know
with
with
the
Korean
branch
that
you're
always
updating
your
development
branch
and
so
finding
figuring
out
admin
permissions
to
let
you
continuously
update
that
branch
name
is
the
hard
piece,
I
mean
I,
don't
know
what
that
answer
is.
I
was
poking
around
on
it
a
little
bit
earlier.
There
may
not
be
a
good
answer,
but
I
will
look
at
that
more
this
afternoon
and
I
I
will
I'll.
J
A
A
Like
push,
maybe
figure
out
a
way
to
push
PRS
to
that
preview
branch
so
that
that
the
preview
branch
stays
stable
like
that
branch
names
stay
stable,
I,
don't
know
we'll
look
at
it,
some
more
I'm
just
trying
to
think.
If
we,
if
we
can't
figure
out
admin
permissions,
then
it
may
be
worthwhile
to
try
and
figure
out
how
to
how
to
get
like
a
stable,
a
stable
branch
name
for
for
localization
previews.
J
C
H
There
certain
grouping,
where
some
of
them
all
hang
together
and
they're
all
kind
of
related
and
those
group
could
be
in
one
PR,
because,
what's
really
hard
is
when
you're
like
well
I
did
two
PRS
and
you
really
need
to
either
merge.
Both
of
them
are
not
both
of
them.
That's
always
crazy.
I've
we've
had
people
do
that,
and
that's
that
drives
me
nuts.
H
H
C
F
And
I
can't
help
just
even
noticing
this
the
subject
line
before
I
delete
it
unread
right
so
I've
been
trying
not
to
think
about
it,
but
it's
been
there
anyway,
and
one
of
the
things
I
wonder
whether
it
might
not
be
useful
to
think
about
before
you
worry
about,
like
touching
umpteen
gajillion
topics
for
files-
or
you
know,
however,
you
want
to
think
about
them.
Is
how
much
do
you
really
need
to
do
that
for
the
audience
that
you
want
to
reach?
F
How
much
would
that
audience
be?
Perhaps
it
better
served
by
a
new
set
of
related
topics?
Did
you
see
them
if
that
Windows
user
experience
is,
is
distinct
from
other
kubernetes
users?
They're,
probably
gonna
have
any
they're
like
the
folks.
You
really
want
to
reach.
You're
gonna
have
an
easier
time
getting
the
information
they
need,
if
they're
not
having
to
look
for
little
bits
and
pieces
in
other
topics.
I'm
dealing
in
my
in
my
day,
job
I'm
dealing
with
exactly
this
issue
right
now,
where
there's
pieces
of
on-prem
install
content
and
sprinkled
throughout.
F
F
F
But
at
the
same
time
we
want
to
figure
out
the
right
relationship
between
these
things.
Yeah,
it's
not
it's
not
an
easy
problem,
and
what's
really
what's,
since
we've
got
a
little
bit
of
time.
I'll
share
this
with
you.
My
first
look
at
your
outline
for
a
Windows
node
user
guide
was
oh
wait.
He's
got
to
look
at
the
current
docs
and
figure
out
how
to
fit
all
this
content
into
that
right
and
then
now
I'm
saying
well.
F
C
Think
kind
of
the
first
thing
that
we
do
is
probably
write
an
outline.
You
know
you're,
you
know,
there's
an
outline
in
the
cab
for
sure,
but
it's
kind
of
like
we
need
to
hit
all
these
topics.
It's
not
really
an
outline
of
how
the
different
users
would
come
to
the
docs
and
what
they
would
expect
to
see.
That's
my
next
task
is
to
think
about
who
are
who
are
the
different
stakeholders?
What
user
persona
are
they?
How
would
they
be
consuming.
C
A
This
is
a
super
productive
and
I
would
like
for
us
to
maintain
it
a
synchronously
as
well
and
like
let
folks
from
other
SIG's
who
also
have
like
we're
stakeholders
in
all
of
this,
give
them
the
opportunity
to
participate
as
well
so
open
an
issue,
use
comments,
and
that
would
be
my
strongest
recommendation.
Okay,.
C
G
Just
gonna
say
my
selfish
two
cents
on
being
the
release
lead.
Is
that
having
the
one
document
prevents
multiple
merge
conflicts,
not
I,
say
conflicts,
but
the
more
pieces
we're
all
touching
and
the
dev
branch
as
we
merge
master
there,
there's
you're
introducing
more
potential
problems.
I
guess
you
know,
you're
spanning
a
broader
net,
I
guess
and
then
also
I
think
this
was
originally
slated
for
113
and
missed
it
and
they
got
pushed
to
114
for
the
windows.
G
Node
release,
so
I
think
having
that
one
centralized
dock
to
drop
with
the
114
release
would
be
a
great
initial
goal
and
then,
if
you
did
have
to
do
the
small
you
know
minor
knits
here
and
there
working
off
a
master
after
114
after
strapped
might
be
a
better
better
way
forward.
But
I
can
put
that
all
in
the
issue,
though,
sounds.