►
From YouTube: Kubernetes Sig Docs 20180710
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 10 July 2018.
https://github.com/kubernetes/website
A
A
Let's
see,
let's
go
on
to
updates
and
reminders.
So
some
updates
happy
news.
We
have
two
more
maintainer,
so
we
have
two
new
approvers
I
should
say.
Let
me
change
that
for
cig
docks.
We
have
Caitlyn
Barnard
from
CN
CF
Caitlyn
is
our
kubernetes
blog
guru
and
also
a
Hugo
devotee
and
enthusiast.
So
Caitlyn
has
been
working
on
kubernetes
for
quite
some
time
and
has
recently
stepped
up
her
involvement
in
the
docs
in
general
and
not
just
blog
posts
and
it's
great
to
have
her
joining
us.
Also.
A
We
have
Zack
Arnold
from
Y
Greene,
who
is
going
to
be
the
release
Meister
for
the
1.12
cycle
from
the
docs,
so
Zack
shadowed,
misty
during
1.11,
and
glad
to
have
him
as
an
approver
I
just
wanted
to
say
again:
congratulations
to
misty
Zach,
Arnold
Anton
dick
chase
on
the
1.11
Doc's.
You
folks
really
knocked
it
out
of
the
park,
so
good
job.
A
Let's
see
okay,
PR
Wranglers
I
put
together
a
draft
of
the
schedule
for
approvers
for
the
PR
Wrangler
shifts
through
the
rest
of
2018.
The
link
is
there
in
the
agenda:
I
also
roughed
in
a
little
bit
of
the
actual,
what
the
actual
Wrangler
Duty's
look
like,
there's,
definitely
more
room
for
that
to
become
there's,
definitely
room
for
that
to
be
more
complete.
If
you
look,
if
you
are
an
approver
and
you
look
at
that
schedule
and
you're
just
like
I
cannot
do
this
feel
free
to
talk
with
other
approvers
change.
A
A
A
Moving
on
another
update
on
translation
repositories,
so
there
is
an
agenda
item
within
the
cig
architecture
meeting
this
week.
Apparently,
all
new
repositories
for
kubernetes
have
to
be
approved
by
sega
architecture,
which
makes
sense.
So
there
is
a
meeting
are
there's
an
agenda
item
at
this
week,
cig
architecture
meeting
to
discuss
adding
translation
repos
for
Japanese
and
Korean
I
will
be
at
that
meeting,
and
hopefully
we
can
figure
out.
Hopefully
we
can
get
to
these
repositories
added
and
also
talk
about
how
to
streamline
the
process
of
adding
new
translation
repositories
more
smoothly.
B
I
just
did
thank
you
Jemaine
for
doing
as
a
big
job,
15
pr's,
and
he
just
cranked
him
out
one
after
the
other.
So
there's
a
little
bit
of
follow-up
work
to
do,
but
for
the
most
part,
that's
done.
The
EML
files
no
longer
sit
in
the
same
directory
with
the
topic
that
they
all
sit
together
in
a
common
directory.
A
Awesome
yeah
I
was
looking
at
the
PR
that
you
linked
in
the
agenda
and
that
is
really
handy
work,
but
there
was
a
really
cool
implementation.
So
yes,
a
big
THANK
YOU
to
teaming
for
for
doing
that,
Paris.
How
nice
to
see
you
do
you
have
anything
that
you
would
like
to
add
to
the
agenda
before
we
get
rolling
through
it.
C
I
wanted
to
let
everybody
know
here
that
obviously
I
know
that
you
are
the
owners
of
the
the
websites
we're
going
to
be
doing
updates
here.
So
when
the
MOC
comes
through,
we
will
gladly
present
to
this
group
will
also
presented
to
contributor
experience.
So
we'll
just
do
some
double
work,
but
if
anybody
has
any
comments,
questions
or
suggestions
we're
going
to
direct
that
direct
all
of
those
to
the
github
issues.
We
have
one
place,
one
source
of
truth,
so
that's
pretty
much
it
for
me
unless
anybody
has
any
other
questions,
concerns
or
comments.
A
C
Mean
I
and
I
know
sansamp
has
said
several
times
in
the
past.
If
we
wanted
the
entire
site
to
me,
either
redesigned
or
repurposed
or
what-have-you
that
they
would
be
very
open
to
hearing
on
listening
and
or
hiring
others
or
outside
sources
for
that
work.
So,
yes,
that's
just
something
to
keep
in
your
back
pocket
for
the
rest
of
the
pages.
C
D
So
this
was
an
interesting
exercise.
Yesterday
we
had
a
lot
of
deploy
keys
in
the
repo
that
were
not
being
used
anymore,
and
it
was
just
actually
unclear
what
all
that
stuff
was
about
at
one
point.
Last
week
or
the
week
before,
we
had
two
web
hooks
configured
for
Nephi
and
our
github
repo,
like
there
were
just
a
lot
of
unknowns
and
I.
D
Think
in
the
past,
Andrew
Chen
took
on
the
net
lip
I
sort
of
relationship
and
configuration,
but
that
also
makes
him
a
single
point
of
failure
and
I
wanted
to
understand
what
was
going
on.
Make
sure
that
our
repo
was
secure
and
fix
a
problem
that
we've
been
having
to
where
we
were
getting
that
Y
notifications
in
the
comments,
but
we
weren't
getting
the
signal
that
the
tests
passed
in
the
pull
request.
D
So
all
that
stuff
was
down
to
some
configuration
problems,
I
think
it's
all
sorted
out
now,
I
added
all
of
the
deploy
keys
that
we
still
needed
back
again
and
renamed
them.
The
wrinkle
here
is
that
you
can't
do
that
from
notify
side.
When
you
first
create
the
deploy
case,
you
can
only
kind
of
do
it
later.
If
you
get
the
information
you
need
from
the
FI
support
and
then
put
them
back
again,
so
there's
no
way
to
rename
those.
D
So
anyway,
the
long
and
short
of
it
is
there
needs
to
be
a
deploy
key
for
every
branch
that
we
deploy.
That's
what
those
are
for,
and
every
branch
that
we
deploy
is
like
an
elephant.
That's
kind
of
the
one-to-one
relationship,
there's
also
a
different
kind
of
token,
so
I
think
that
maybe
even
Jennifer
and
Andrew
have
either
forgotten
about
this
or
we're
confused
by
it.
Some
of
the
things
that
nullify
needs
don't
use
a
deploy
key.
They
use
a
personal
access.
D
Token,
that's
on
somebody's
github
account
settings
and
gives
them
the
right
permission
for
the
repo.
So
any
of
us
can
do
it
effectively,
like
anybody
that
has
any
access
at
all
to
our
repoed
that
doesn't
need
push
access
or
anything
can
create
that
personal
access
token
and
that
gets
used
by
the
web
hook
directly,
and
it
also
gets
used
on
net
wise
side
for
the
comments
and
other
kinds
of
notifications
that
we
get
out
of
net
y.
D
So
I
am
going
to
share
that
document
and
make
Zach
the
owner
of
it.
You
doc
and
then,
because
there's
some
secret
information
in
there
like
there
are
the
mappings
between
the
deploy
keys
and
the
sites
that
we
currently
have.
So
that's
something
that
it's
only
moderately
sensitive
information,
because
Matloff
I
only
has
read
access
to
our
repo.
It
doesn't
write
anything
to
the
repo
but
anyway.
So
that's
what
I,
then
that's
what
I
did
part
of
yesterday.
A
D
Is
that
I
would
assume
that
if
you
delete
a
site
from
net,
why
it
would
delete
the
deployed
keys
from
github?
But
it's
possible
that
that's
not
the
case,
so
I
think
that
I
actually
need
to
go
and
delete
the
one
point
six
site,
because
I
don't
think
we
need
to
build
one
point
anymore.
So
that'll
be
a
good
test
because
there's
a
deploy
key
for
the
one
point,
six
site
so
like.
D
If
I
have
the
OK
to
go
and
delete
that
now
that
111
is
out,
then
we
will
see,
because
if
that's
the
case,
then
that
means
that
that's
going
to
be
tricky
to
manage,
because
when
you
make
a
new
site
in
that
liffe,
I
it
makes
a
new
deploy
key.
That's
just
called
like
net
liffe
I
deploy
key
and
so
with
the
ones
that
I
haven't
like
riad
it
and
renamed.
D
A
D
Something
else
that,
like
maybe
we
can
like
play
around
with
this
on
a
test
net
with
eyesight,
but
nullify,
has
a
feature
well.
They
have
two
different
ways
that
you
can
make
multiple
sites,
because
our
sites
are
kind
of
based
on
the
branches
and
it
looks
like
you
can
have
one
site
that
builds
multiple
branches
or
you
can
have
it
the
way
we
have
it
where
every
site
we
have
set
up,
builds
only
one
branch
and
maybe
some
of
that's
new
since
we
set
up
and
Elif
I.
D
So
it
would
be
interesting
to
see
if
that
streamlines
management
a
little
bit,
because
then
we
might
only
need
one
deploy
key
for
the
whole
site
and
we
can.
We
would
be
able
to
like,
remove
and
add
branches
to
build
pretty
easily
like
it
would
just
be
taking
one
point,
six
out
of
the
list
or
whatever.
So
that
may
be
something
we
want
to
play
around
with,
but
definitely
not
like
on
the
live
site.
D
A
D
E
A
A
A
So,
let's
talk
a
little
bit
about
zoo
maintenance.
This
is
not
really
so
much
a
discussion
thing.
It's
the
more
properly
an
update
recently
I
guess.
The
kubernetes
community
has
experienced
some
bad
actor
problems
with
with
attendees
in
kubernetes
zoom
channels.
So
we
have
to
do
some
maintenance
for
the
sigdoc
zoom
I'm
gonna,
take
that
on
this
week
and
what
I
think
the
most
visible
piece.
A
If
that
will
be
a
regenerated
link,
so
the
we
will
need
to
update
the
meeting
invitation
for
this
meeting
with
a
new
zoom
Lake
if
I
understand
that
correctly
Parris,
yes,
okay,
so
you
should
see
a
meeting
update,
go
out
this
week
with
a
different
zoom
link
and
that's
why
we're
basically
tightening
up
web
moderation
controls
that
we
can
zhuzh
moderation,
sweet
isn't
the
best,
but
there
are
things
that
we
can
do
more
actively
than
we're
doing
right
now.
So
that's.
That
is
the
change
that
you
will
see.
A
C
Zach,
if
I'm
a
button,
I'm
actually
gonna
send
another
email
to
the
leaves
to
let
you
know
that
I
will
do
sort
of
like
an
AMA
recording,
slash
demo,
slash
stuffs
where
you
can
pretend
to
be
a
bad
actor
and
I'll
show
you
exactly
the
the
protocol
and
the
procedure
for
that
I
mean
as
far
as
the
users
are
concerned.
Like
everybody
on
this
call,
you
won't
necessarily
see
any
major
changes,
except
for
like
what
Zach
mentioned
with
a
French
link.
F
A
A
If
it's
accurate
and
totally
helpful,
never
need
to
apologize,
so
thank
you.
All
right,
I
have
a
note
to
revisit
the
discuss
the
discussion
from
two
weeks
ago
about
how
to
make
sure
that
featured
documentation
is
updated
accurately.
But
a
lot
of
the
a
lot
of
that
discussion
requires
Andrew
to
be
here
and
to
use
not
today
so
I'm
going
to
suggest
that
we
postpone
this
for
another
week
until
you
can
join
us.
A
G
Do
I,
certainly
yeah
so
I
was
I,
was
over
the
holiday
break.
I
was
contributing
to
a
different
open-source
product
and
I
was
talking
to
I
was
talking
to
that
group
and
I
was
like
oh
look
at
how
we
do
contribution
on
kubernetes,
it's
so
great
and
then
I
clicked
through
the
documentation
button
and
then
clicked
documentation
contributors,
and
then
we
have
the
three
options:
I
am
a
co
contributor,
I'm,
a
community
contributor
and
I'm
a
doc
contributor,
and
this
sort
of
journey
is
pretty
broken
when
I
click
through
it.
G
The
co
contributor
is
probably
the
best
at
least
say
links
to
a
specific
Co
contributor
guide.
The
community
guide
looks
like
it's
a
you
know
idle
link.
Here,
the
community
guide
is
a
like.
It's
like
an
older
doc.
That's
been
imported,
but
still
needs
quite
a
bit
of
cleanup
and
I.
Don't
know
if
that
folks,
on
our
team
or
parish,
temples
and
in
your
team,
but
the
thing
that
really
caught
me
by
surprise
was
the
the
poor
experience
of
the
documentation.
G
If
you
click
on,
you
know,
I
want
to
contribute
documentation,
you're
immediately
taken
to
a
page
on
content
organization
and
basically
saying
this
I
use.
This
you
go
content
organization
is
the
core
concept,
which
is
true,
but
it's
probably
not
the
first
thing
that
a
brand
new
contributor
needs
to
know
about
our
Docs,
so
I'm
sure
how
this
ended
up
being
the
top
page
for
contribute.
So
I'd
like
to
see
a
landing
page
of
some
kind
get
written
for
contributing
to
content.
Just
because
this
experience
is
very
poor.
That's.
G
D
D
Somebody
has
bit
like
I,
think
everybody's
been
holding
off
on
making
future
improvements
because
they
knew
that
I
was
working
on
something.
Oh,
my
thing
does
address
that.
The
other
thing
that
I
want
to
do
is
sort
of,
like
maybe
a
follow
on
to
my
contributor
guy
stuff,
so
that
I
can
actually
keep
them
so
and
I
want
to
see
us
have
edit
and
feedback
links
like
we
have
now,
but
I
want
them
to
go
directly
to
the
thing.
D
G
I
I
originally
thought
there
was
just
like
I
think
we
used
to
point
people
to
the
like,
create
a
PR
page
and
that's
not
really
the
most
I
mean
I.
Guess
it's
like
me:
it's
the
most
common
thing
that
people
are
trying
to
do
and
I
think
that's
what
caught
me
by
surprise
and
then
to
be
to
hit
with
this
page
I
assumed
it
was
a
Hugo
migration
issue,
but
I
didn't
see
an
issue
for
it.
D
What
are
you
much
supposed
to
be
only
working
on
that
for
like
the
next
two
weeks,
so
hopefully
totally
like
a
lot
of
the
contents
are
written.
It
was
before
Hugo,
and
so
what
the
end
of
last
week,
I
like
made
it
work
with
Hugo,
but
I've
also
done
a
release
since
then,
so
I
learned
a
lot
more
stuff
than
I
knew
when
I
first
started.
Writing
it.
Okay
I
want
to
you,
get
it
there
in.
G
The
world
cool,
yeah
I
didn't
mean
those
I
I,
don't
know
right
on
your
parade
or
poopoo.
Your
work,
I
just
didn't
know
what
the
progress
was
and
I
haven't
decided
on
one
of
these
meetings
for
a
while.
So
so
thank
you.
I'll
just
look
forward
to
that
misty.
Is
there
an
issue
that
you're
tracking
that
in
I.
G
B
G
But
this
seems
a
lot
bigger
because
if
it
was
just
a
TOC,
it
like
I
thought
there
might
be
a
page
that
I
could
just
point
to
instead,
but
you
know
and
misty
I
know
you
were
working
on
like
a
much
larger
rewrite.
I
didn't
know
if
there
was
sort
of
like
an
interstitial,
fixity,
Hugo
breaking
thing
and
then
the
imported
community
guide,
4.4
code
and
community
contributor
I
don't
know.
Are
you
working
out
as
well
misty?
Are
you
folding
like
thin
I?
Don't.
G
D
D
Awesome
so
that's
also
just
an
interim
because
there's
gonna
be
I,
guess
there's
a
code
of
conduct
committee.
That's
forming
so
I
guess
some
CN
CF
is
gonna,
have
it
or
maybe
kubernetes
is
gonna,
have
its
own
conduct,
in
which
case.
B
Back
to
the
user
journeys
for
a
minute,
so
Jared,
some
of
the
things
you
were
mentioning
we're
about
the
poor
experience
on
the
documentation
homepage
and
navigating
through
the
user
journeys,
and
so
our
intern
Neha
has
been
doing
user
research
on
that
page
and
she
has
a
whole
body
of
of
you
know,
results
from
from
doing
that.
Research
and
I
know
that
and
Andrews
viewpoint.
After
looking
at
what
she
came
up
with
is
we
need
to
just
tear
that
whole
thing
down
and
start
fresh
with
something
simpler.
So
that's
in
the
works
right
now.
G
Okay,
that's
not
the
answer,
I
hope
to
hear,
but
I'm
really
curious
to
see
her
result
and
to
fix
that
maze.
I
think
there's
Isis
the
people
who
I
showed
is
doing
like.
Oh,
this
is
really
great,
but
I
definitely
think
there
are
some
nice
improvements
and
maybe
we
take
the
concepts
from
it
and
fly
it
elsewhere,
yeah
totally
for
not
glad.
B
G
People
when
I
was
showing
it
to
I,
was
working
with
some
folks
over
on
Google
org
we're
doing
another
open
source
project
called
open
data
kit
and
I
was
showing
it
to
them
and
doing
a
demo
of
our
Docs,
because
they
need
a
lot
of
guidance
on
their
content
and
and
they
they
saw
the
landing
page
and
we're
very
impressed
by
it
at
first
glance
and
then
I
was
as
I
was
walking
through
it.
I
was
like,
oh
that
behavior
is
unexpected.
Oh
that's,
behavior
something
expected
and
does.
G
Mean
I've,
given
a
few
demos
in
the
past
and
so
I
I
know
how
to
do
this
with
a
hand
wavey
and
moved
quickly
toward
something
else.
That
looks
better.
But
for
me
it
was
just
a
surprise
at
that
point
and
I
knew
it
was
a
Hugo
migrate
issue,
but
I
didn't
know
what
the
fix
was.
I
didn't
know
there
was
an
issue
filed
for
it
today
answer
your
question:
Steve
it
was
a.
G
A
Thank
you
for
raising
this
Jared.
It's
because
I
totally
missed
this
yeah
I
haven't
looked
at
the
at
the
I,
didn't
even
think
to
look
at
the
contribute
pages
after
the
human
migration
and
yeah.
This
is
not
a
good
experience
and
yeah
I
agree
about
the
creating
issue
and
an
edit
this
page.
Those
new
UI
elements
at
the
bottom
of
the
page
are
that's
really
confusing
experience.
A
D
I
have
a
branch
up,
but
I
don't
yet
have
a
PR
I'll.
Also
look
at
this
specific
issue
and
see
if
there's
a
quick
fix
for
it,
that
I
can
just
put
in
the
PR
okay.
I
I
was
working
on
a
dock
for
myself,
calling
it
something
like
newbie,
getting
started,
contributing
to
kubernetes,
open
source
dock
kind
of,
like
for
my
own
information
for
somebody,
who's
not
very
familiar
with
github
or
kubernetes,
and
if
it
can
help
you
any
misty
ike,
it's
just
a
word
doc
on
on
google
docs.
I
can
send
it
to
you
right
now.
It's
it's.
You
know
it's
half-baked,
but
just
for
another
perspective,.
D
You
know
that
would
be
great.
My
email
address
is
just
misty
hacks
at
google.com.
Okay,
do
you
want
to
share
that
along
great.
I
A
F
So
interestingly,
this
came
up
because
I
was
working
on
a
healthier
project
that
was
documenting
some
additional
cute
on
cubelet
flags.
We
thought
okay.
Well,
we
should
refer
to
the
upstream
documentation,
I
go
and
I
look
at
the
cumulative
ever
installed
it
alone.
Behold,
none
of
the
flags
that
I'm
documenting
are
even
there
on
the
page,
which
is
when
I
found
the
poll
remembered,
seeing
the
whole
request
that
I
refer
to
in
the
in
the
agenda
and
in
fact
a
pull
request
refers
back
to
an
issue
that
goes
into
substantially
more
detail.
F
Anyway,
I'd
like
I,
would
like
to
merge
the
pull
requests
and
because
well,
okay,
partly
because
hep
tio
needs
a
partly
because
that's
a
big
chunk
of
reference
content.
That's
missing
and
it
does
not
look
as
though
it's
a
quick
fix
to
get
it
fixed
in
kubernetes
kubernetes.
But
we
have
the
issue
and
we
have
people
who
want
to
get
it
fixed.
So
it
feels
like
the
interim
manual
fix
would
not
be
with
us
for
too
Oh
big
PR
yeah.
A
Right,
no
I
hear
you
yeah,
it
is
a,
it
doesn't
solve
the
underlying
issue,
but
it
does
like
you
point
out,
solve
the
solve
the
more
immediate
need.
So
Zach
it
looks
like
you
went
through
and
reviewed
both
you
and
she
being
reviewed
this
exact.
You
gave
an
approve
there.
Anything!
Oh,
yes,
you
did
it's
in
the
timeline.
Oh.
F
F
We
can
document
it
elsewhere,
I'm
willing
to
take
point
on
making
sure
that
there's
an
issue
in
the
KKK
repository
against
this
I,
don't
think
that
there
is
yet
and
that's
where
the
solution
needs
to
be
devised,
but,
like
I
said
thought
I
should
come
before
the
group
and
not
just
get
decided
arbitrarily
I'd
be
hitting
approved.
Oh.
B
E
J
E
F
For
helping
catch
the
underlying
problem,
too
I
looked
at
that
and
I
thought
I
mean
I,
looked
at
the
what's
actually
on
the
dark
side,
I
thought
wait,
a
minute
total
I,
don't
swear
in
Kansas
anymore,
but
I
was
also
pretty
sure.
I
could
all
I
could
remember
was
that
there
was
the
word
cubelet
in
commit
message,
good,
but
sure
enough.
There
it
was
Jennifer.
F
Is
not
it's
not
guaranteed,
but
oh.
A
E
G
A
A
Oh
yes,
so
Jared
and
I
submitted
a
proposal
to
write
the
Ducks
Cincinnati
in
August,
talking
about
the
the
migration
process
from
Jekyll
to
Hugo
and
less
about
the
less
about
the
technical
merits
of
Jekyll
and
Hugo.
Although
those
will
get
a
mention
and
more
about
the
actual
process
of
what
it
was
like
to
do
that
as
a
sake
that
proposal
was
accepted
and
heard
and
I
will
be
presenting
on
that
in
in
August.
And
if
you
are
interested
in
I'm
sure
we
will
have
an
early
draft.