►
From YouTube: Kubernetes SIG Docs 20171107
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 07 November 2017.
https://github.com/kubernetes/kubernetes.github.io
A
A
Listen,
we
have
a
guest
Fabrizio
andini,
but
this
is
not
his
first.
It's
not
his
first
sig
Docs
meeting.
So
simply
hello
and
saying
glad
you're
here,
all
right,
let's
see
Steve
Perry
is
not
here.
I
he's
got
another
meeting
going
on,
but
there
was
an
issue
in
the
in
this
sig
Docs
email
group
that
came
up
about
about
search
engine
results
for
kubernetes
deployment
and
Ahmet
noted
that
the
top
result
is
paid
advertising
and
that
this
represents
a
possible
problem
for
kubernetes
documentation
and
that
paid
results
for
search
engine
page
is
related
to
kubernetes.
A
A
B
A
B
Reference
page
one
for
each
main
could
mean
a
common
and
in
this,
what
I'm
doing
I'm
mixing
the
generated,
the
dr.,
which
are
included
with
the
part,
which
is
my
main
element
in
it.
That
gives
some
additional
extra
content.
This
was
the
read
the
goal
so
to
have
something
generated
there,
but
also
something
which
is
a
bad
way.
I
did
and
additionally,
that
we
can.
That
is
difficult
to
to
add
in
the
Cobra
documentation.
A
A
Excellent
I
think
we'd
like
to
take
a
look
at
it
and
just
become
more
familiar
about
what
it
is,
what
the
what
the
scope
of
the
PR
entails.
I
can't
think
of
any
reason
why
we
wouldn't
be
absolutely
delighted
to
have
improvements
to
to
the
reference
stock,
but
I
think
we'd
like
to
be
able
to
I
think
we'd
like
to
be
more
conversant
in
the
specifics
of
the
PR
and
take
a
look
at
it
more
in
depth.
B
C
As
a
work
in
progress
right
now
and
then
for
the
automated
side
for
the
auto-generated
axe
touch
base
with
a
steep
carry
because
he's
he's
sort
of
spearheading
like
the
auto-generated
Docs
for
the
the
whole
site.
So
we
want
to
make
sure
they
all
they're
supposed
to
go
into
the
docs
reference
generated
directory.
So
that's
what
we're
working
towards
right
now
and
then
I'll.
Take
a
look
at
the
the
rest
of
the
the
Cuba
admin
stuff
and
comment
on
the
on
the
PR.
A
C
D
Okay,
I
will
try
to
just
briefly
recapitulate
our
conversation
at
the
highest
level.
You
know,
for
the
other
folks
have
been
working
on
the
user
journeys.
I.
Don't
think
that
I
think
that
user
journeys
at
the
level
of
user
journeys
aren't
suitable
I
do
think
that
there
is
work
to
support
individual
user
journeys.
D
D
D
A
A
When
it
comes
to
what
that
work
will
look
like
at
the
docs
sprint,
how
will
we
know
which
which
issues
or
which
PRS
are
our
I
guess,
which
which
issues
are
good
to
work
on?
Is
there
is,
if
have
you
thought
about
a
specific
label
to
apply
to
issues
to
designate
them
as
being
suitable
for
well
you're?
Making
the
face
that
says?
No,
so
I
will
make
a
suggestion
that
there's
I've
added
a
Help
Wanted
label
to
the
repo
and
that
applying
Help
Wanted
would
be
a
good
way
to
to
parse
out
that
content.
Yep.
D
F
F
A
A
For
this
event,
with
the
understanding
that
people
will
not
attend
for
whatever
reason
and
the
way
that
we're
thinking
about
structuring
the
ducks
sprint
is
to
have
one
one
room,
that's
dedicated
to
to
a
structure
that
we
provide,
so
in
this
case
the
working
on
the
user
journeys
and
had
that
to
be
sort
of
the
collective
work
of
the
room
and
then
in
the
other
room
too,
and
that's
what
we're.
What
we're
calling
sort
of
cigs
structured,
a
sig,
structured
sprint
where
the
sig
is
providing
the
structure
and,
in
the
other
room
we're
thinking
about.
A
Having
that
be
more
of
a
participant,
structured,
participant,
structured
flow
of
work.
It's
a
by
participant,
structured.
We
mean
that
people
that
people
may
come
to
this
to
the
stock
sprint
with
a
particular
dock
ax
to
grind
and
that
they
may
have
their
own
their
own
goals,
either
as
individuals
or
maybe
in
small
teams,
for
improving
specific
aspects
of
the
documentation
that
are
important
to
either
like
that
user
or
to
this
small
team
and
so
providing
providing
support
for
users
to
consult
with
each
other
on
on
their
own
sort
of
initiatives
for
ducks
prints.
A
Jared.
You
and
I
talked
about
this
yesterday
a
little
bit,
and
you
pointed
out
rightly
that
there's
it's
possible
for
that
to
be
very
problematic
that
users
could
go.
Our
participants
could
go
sort
of
wildly
out
of
bounds.
We
could
end
up
with
it
like
a
torch,
torch
and
pitchforks
situation,
where
you
know
folks
come
in
and
say,
hey
your
dock
sucks
and
unless
we
have
very
specific
notions
of
boundaries
about
how
to
how
to
confine
or
how
to
respond
and
how
to
confine.
A
You
know,
potential
biggest
potential
attempts
to
go
out
of
bounds.
Of
like
we're
going
to
I
guess
the
it's
possible.
The
participants
could
come
in,
like
a
block
of
ten,
could
come
in
and
say,
hey
we're
going
to
add
automation
to
this
thing.
That
has
never
been
taught
to
make
it
before
and
we
just
to
be
clear.
F
I,
just
like,
like
that's
a
fair
assessment,
I
think
you
think
when
I
think
about
how
you're
going
like,
if
a
group
self-selects
into
these
two
categories
of
user
journeys
or
participant
structured
projects,
ideally
like
the
goals
that
we
want,
are
the
people
who
know
kubernetes
really
really
well
to
pick
user
journeys.
We
should
probably
tell
people
because
people
won't
know
what
to
pick
and
as
good
tech
writers.
F
We
should
actually
give
them
as
much
guidance
as
possible
to
prevent
too
much
cognitive
overhead,
so
I
think
when
it
comes
to
things
like
user
journeys,
we
want
people
who
are
most
familiar
with
the
product
to
choose
it,
because
they're
gonna,
once
you're
gonna,
be
able
to
provide
us
with
a
lot
of
guidance
in
how
they
use
it,
and
also
people
who
can
sort
of
test
out
that
theory
I.
Think
with
you
know
he,
if
I
take
that
group
aside
and
then
examine
who's
left.
F
We
have
a
lot
of
people
who
probably
don't
know
the
product
very
well
and
just
want
to
get
started
and
contribute
to
something
and
help.
So
I
would
be
very
careful
about
putting
the
onus
on
them
to
design
their
own
project
because
they're
not
going
to
know
what
they
want
to
do,
and
so
they
might
suggest
things
that
are
either
not
productive
or
not
very
useful
to
us
or
not
within
our
own
boundaries
and
goals
for
the
doc
sprint.
F
D
There
is
publicly
available
information,
and
some
of
you
know
my
background,
so
you
won't
be
surprised
to
hear
that
I
just
checked
on
LinkedIn
three
names
just
drawn
at
random.
Two
of
them
are
execs
right,
and
one
of
them
is
a
Content
designer.
So
more
of
a
tech
writer
person,
but
I
looked
at
that
list
of
names,
I
thought,
I'd,
begley,
recognized
one
or
two
is
I,
was
surprised
to
see
them
on
the
list
and
and
that's
why
I'm
thinking
that
we
might
I'm
not
prepared
to
do
this
right
now.
A
If,
if
folks
think
that's
a
good
idea,
I
would
ask
for
you
know
a
little
bit
of
help,
whether
that's
15
minutes
a
half
hour
an
hour
somewhere
between
now
and
and
coupe
con
to
go
through
that
list
of
actionable.
That
list
of
actionable
issues
and
just
try
to
assess
and
apply
the
label
for
good.
First
issue
to
things
that
you
think
would
be
easily
accomplished,
lived
in
within
a
duct
spread
to.
F
D
Think
I
got
there.
It
was
after
I
raised
my
point
that
I
thought
no
item
in
a
week.
You
know
we
do
have
a
way
of
getting
in
touch
with
them
ahead
of
time
provide
them.
You
know
suggest
that
if
they're
not
sure
what
you
know,
what
their
expectations
are,
that
they
go
take,
a
look
at
you
know
like
maybe
send
out
the
email
after
we
get.
D
F
D
F
C
H
F
Yeah,
I
think
that's
a
really
well
scoped
out
project
and
maybe,
if
there's
additional
work
that
we
want
folks
to
do
it,
and
maybe
when
we
reach
out
to
people
we
can
say
like
here
are
some
projects
that
we're
considering
what
would
you
like
to
get
out
of
it
I?
If
we
want
that
sort
of
feedback
we
can,
we
can
solicit
it,
but
hey
I
like
it.
You
like
the
glossary
and
user
journey.
Singling
really
well
scoped
out
projects,
your
folks,
it.
A
D
F
Other
thing
that
I
and
I
I
want
to
make
sure
that,
like
this
is
also
fun
for
folks
to
do
like
people
are
gifting
us
their
time.
I
also
want
to
get
their
feedback
on
things
and
like
how
we're
doing
is
it
like?
Does
the
process
work?
Does
it
make
sense
like
what
are
your
first
impressions?
That
sort
of
thing
I
also
want
to
keep
it
fun,
so
there's
ideas
of
like
ways
to
like
make
this
fun
and
interesting
for
the
folks
who
are
attending
I'm
all
ears.
So,
let's
port.
G
If,
if
people,
if
you
want
them
to
be
able
to
contribute
like
immediately
if
you're
gonna,
send
them
out
an
email,
one
nice
thing
to
do
might
be
to
say:
hey
make
sure
you
have
a
github
account,
make
sure
you've
signed
a
disclosure
whatever
it
is.
That
thing
you
have
to
sign
because
I'm
just
getting
into
it
myself,
I'm
trying
to
actually
I,
was
going
to
try
to
do
a
glossary
term
just
to
see
if
I
could
do
your
process,
so
maybe
she
could
define
the
process.
People
would
come
in.
A
Have
that
is,
in
fact
exactly
what
we
have
talked
about,
so
we
listed
having
a
github
account
as
a
prerequisite
that
went
out
in
the
program
blurb,
but
that
is
signing
the
License.
Agreement
is
something
that
we
had
already
hit
on
as
as
part
of
the
message
that
we
send
out
to
the
participants
they're
saying
hey.
If
you
can
sign
this
in
advance,
that
would
be
a
that
would
be
awesome
because
otherwise
it
could
be
the
friction
boy
first
hour
of
a
sprint,
just
walking
people
through
the
licensing
process.
A
So
ya,
don't
know,
that's
a
great
idea
Chris.
So
you
know
user
journeys
and
glossary
sound
like
a
really
great,
well
scoped
a
really
great,
well
scoped
place,
and
if
users
want
to
come
with
their
own,
you
know
with
their
with
their
own
particular
Doc's,
to
improve.
That's
great
I
think
we
can
support
that,
but
let
the
the
initiative
for
that
rests
with
the
users
rather
than
making
things
more
complicated
than
necessary.
A
Does
that
sound
reasonable
to
folks?
It's
the
only
thing
that
I
want
to
be
that
I
would
like
to
nail
down
sooner
rather
than
later.
Is
how
how
we
will
present
the
glossary
so
like
we
talked
about
user
journeys,
we
talked
about
going
through
and
identifying
pieces
of
the
project
that
Steve
has
already
laid
out
and
adding
the
Help
Wanted
label
to
those
issues.
Do
we
want
to
do
something
similar
with
the
glossary?
Do
we
want
to
open
glossary
issues
for
specific
terms?
A
C
Was
the
list
of
terms
that
need
to
be
added,
or
so
we
can
stick
that
and
then
also
if
people
are
like?
Oh,
you
know
fairly
new
to
ku
Bernays
and
they're
like
oh.
What's
that
term,
like
I,
hear
thrown
around
a
lot
but
I,
don't
know
what
it
is
exactly
they
can
kind
of
do
some
research
and
you
know,
get
the
definition
and
then
do
that
because
I
think
that
would
be
interesting,
seeing
them
and
also
help
them
learn
as
a
new
user.
You
know
absolutely.
A
A
Reviewers,
if
you
are
not
going
to
be
attending
coop
con,
but
you
still
want
to
be
involved,
as
it
turns
out
we're
going
to
be
reviewers
for
all
of
the
PRS
that
people
at
this
docs
print
open
up.
So
if
you
are
going
to
be,
if
you're
going
to
be
available
during
the
window,
the
time
window
of
the
docs
prints
Jared,
do
you
do
you
know
what
time
on
on
the
days
of
or
like
what
time
in
which
days
we're
scheduled
for
at
coupon
for
the
Ducks
prints?
Let.
A
F
E
A
A
F
I,
don't
think
so
that
we
can
gladly
give
so
in
the
past.
I've
just
like
the
CNCs
has
a
mountain
of
swag,
and
what
makes
it
great
is
that
you
just
give
people
a
code
and
they
punched
into
the
CN
CF
website,
and
then
they
get
swag
so
and
I
can
I
can
send
people
a
link
to
the
CN
CF
store,
but
it's
what's
that
and
they
can
choose
their
own
size.
So
you
don't
have
to
like
I
choose
gender.
F
A
F
A
A
A
I,
don't
know
what
radhika's
goal
is
in
particular.
Is
it's
not
to
fill
fill
attendant
slots
I?
Think
it's
to
boost
visibility
that
hello?
Yes,
we
are
sick,
Docs.
We
will
be
doing
this
thing
and
you,
even
if
you
can't
attend
you,
should
at
least
come
glad-hand
us
or
you
know,
come
by
and
say
hello
and
we
can
at
least
they
can
meet
and
talk.
So
it's
I,
don't
know
what
you
call
that
in
marketing,
speak,
visibility,
branding,
I,
think.
D
There's
some
benefit
to
to
letting
people
know
that
there's
organized
systematic
work
going
on
on
the
docks,
I
swear
to
God.
If
I
hear
one
more
person
just
saying:
oh,
my
god,
the
docks
suck
with
absolutely
no
awareness
of
the
work.
That's
been
done.
Large
amounts
of
work
right
to
re
architect
and
to
redo
the
site
and
to
work
it
continues,
and
the
number
of
people
who
are
coming
in
all
of
that
I
think
just
letting
people
know
that
systemic
sustained
attention
is
being
given
to
the
docks
is
a
very
good
thing.
Then.
C
I
think
we
should
cream
it.
As
you
know,
sort
of
a
PR
thing-
words
I'd
come
by
and
talk
to
us
about
the
docks.
You
know
we're
working
on
it
like
if
you
have
any
questions
or
feedback
or
whatever,
because
then
we
can,
then
it's
not
specifically
about
the
Sprint
it's
up,
but
just
like
you
know
a
point
of
contact.
Yes,.
I
E
A
A
Radhika
also
suggested
doing
a
usability
study.
I
would
love
to
do
a
usability
study,
but
I
don't
want
to
do
one
in
the
context
of
coop
kahn
and
I
think
that's
a
lot
of
work.
I
think
that
a
usability
study
well,
okay,
so
here's
the
thing
I
think
I
think
it's
a
great
I
think
it's
like
coupe
Khan
is
going
to
be
a
great
opportunity
to
like
to
pull
folks
to
visit
with
folks
and
just
to
get
really
good
qualitative
data
like
well.
What
is
your
experience
and
like
with
sigdoc
or
with
with
kubernetes
stocks?
A
You
know,
yeah
qualitative
data
I.
Think
that's
going
to
be
a
great
opportunity,
but
in
terms
of
like
an
actual
usability
study,
I,
don't
I
just
won't
see
that
being
feasible
within
the
window.
That
we
have
and
I
would
like
to
do.
I
would
love
to
do
a
usability
study
but
I'd
like
to
like
do
it
justice,
so
I
don't
know
if
that's
that's
about
usability
studies
and
sort
of
maximizing
the
benefit
of
like
being
present
as
I.
C
C
Personally
think
we
should
wait
till
after
user
journeys
gets
out
the
door,
because
we're
already
addressing
some
things
we
know
are
issues
so
I.
Think
it'll
be
more
helpful
like
once.
It's
done
to
see
how
we
can
improve
on
that
and
then
we
should
also
team
up
with
our
UX
people.
So
we
can
get
maybe
better
guidance
over,
like
you
know,
doing
more
comprehensive
one
yeah
I.
F
F
We
should
definitely
solicit
from
the
community
like
when
we
talked
about
user
journeys.
Just
do
this
informally,
so
we
talk
about
user
journeys,
get
feedback
like.
Are
there
additional
user
journeys
that
were
not
that?
We
should
include
here
that
you're
thinking
of
and
like
you
know,
frame,
questions
said
to
help
us
in
these
projects.
A
Create
I
think
that's
that
would
be
really
awesome
if
we
want
to
I,
don't
know
if
we
want
to
like
pool
our
resources
close
to
the
coop
con
and
just
have
like
a
like
a
small
set,
maybe
like
three
or
four
primers
for
conversation
about
to
elicit
that
kind
of
feedback.
You
can
talk
about
that,
but
I
don't
know
that
we
need
to
devote
a
whole
lot
of
effort
to
it.
A
A
A
I
have
noticed
that,
even
though
we
sew
about
what
a
month
or
two
ago,
we
put
together
a
list
of
tech
reviewers
who
are
available
for
particular
domains
of
expertise
in
kubernetes
stocks,
and
that
has
proven
to
be
less
helpful
than
I
ate
and
I
hoped
so
I
would
like.
I
would
like
for
us
to
get
to
the
place
where
we
have
a
decent
and
well-maintained
list
of
people
who
are
capable
of
providing
tech
reviews
for
documentation
and
I.
Don't
know
the
best
way
to
go
about
that.
A
C
I
can
think
of
two
things:
one.
We
can
work
with
Parris
Pittman
to
contact
different
cichlids
to
get
the
list
of
tech
reviewers
for
their
particular
cig.
The
other
thing
to
do,
instead
of
having
us
look
through
each
list
and
like
pick
out
a
reviewer,
we
could
try
using
that
mentions
for
cigs
to
be
like
specifically
to
ask
for
a
reviewer
from
that
cig,
and
then
they
may
be
concealed
from
select.
J
The
sick
and
trip
exer
or
the
working
group
for
contributes
variances,
trying
to
start
out
a
program
around
mentoring
and
mentorship.
Specifically,
it
was
a
couple
of
areas,
one
new
contributor
to
member,
but
also
getting
members
up
into
reviewing
and
approving
and
I
think.
This
is
an
area
where,
maybe,
if
some
of
those
people
as
part
of
the
mentorship
process,
took
on
some
so-called
janitorial
type
work,
but
had
some
visibility
on
what's
going
on
and
documentation,
they
could
act
as
liaison
and
that
bridges
them.
A
A
E
K
K
A
K
A
C
Wait
you
mentioned
automatically
assigned
like
how
would
that
work
good,
so
what
you're
saying
is,
if
there's
a
PR
in
in
our
Doc's
repository
right
and
it's
related
to
a
package
in
kubernetes
kubernetes
like
we
should
have
like
a
mechanism
that
will
like
Auto,
assign
a
reviewer.
That's
like
an
owner
of
that
package.