►
From YouTube: Kubernetes Sig Docs 20180911
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 11 September 2018.
https://github.com/kubernetes/website
A
Hello
all
and
welcome
to
the
weekly
sig
Docs
meeting
for
kubernetes
today
is
Tuesday
September
11th
2018
I'm
Zack
cor,
listen,
co-lead
of
sig
ducts
and
yuri
lr.
Why
don't
we
start
by
asking
about
new
contributors?
Folks
who
are
here
for
the
first
time
I
see
we
have
one
new
contributor,
Silvie
TSM,
so
they
do.
You
want
to
introduce
yourself
just
briefly.
A
A
A
So
I
want
to
say
thank
you
to
Andrew
for
being
the
PR
Wrangler.
Last
week
this
week
the
original
PR
Wrangler
had
I
had
scheduled
zack
arnold
to
be
PR
wrangler
he's
still
in
the
middle
of
1.12
madness.
Brad
tuple
stepped
up
and
said
that
he
would
be
happy
to
take
that
shift,
and
now
brad
tuple
is
in
the
middle
of
the
path
of
hurricane
Florence
and
no.
B
A
C
A
C
What
it's
worth
I
am
under
a
certain
amount
of
pressure
on
the
FDA
side,
to
really
get
those
Canadian
Doc's
knocked
out.
So
that
really
does
need
to
be
a
priority
for
me.
So
that'll
help
because
that's
a
bunch
of
them
at
this
point,
there's
a
lot
of
QbD
and
related
bits
and
pieces
from
112
and
I've
been
seeing
stuff
in
master.
Also,
okay,.
A
D
I,
don't
know
how
it
feels
about
itself.
It's
I,
don't
have
that
capability
of
discernment
yet,
but
I
feel
I
invented
a
new
status
color
in
the
release,
burndown
meetings,
so
we
are
at
status
chartreuse
for
docs.
It
is
somewhere
in
between
yellow
and
green.
It's
the
Sierra
Mist
of
statuses,
and
it
we
are
basically
in
a
place
where
there's
four
people
that
have
been
just
decided
that
they're
kind
of
done
talking
to
me
so
I,
don't
know
that
those
features
are
going
to
make
it
because
there's
simply
no
documentation
whatsoever.
D
However,
60%
of
Doc's
are
in
progress
and
I'm
expecting
a
lot
of
them
to
hopefully
emerge
this
week.
30%
are
done
so
that's
good
to
go,
which
is
nice
and
keeping
the
112
branch
up-to-date
with
Master
as
I
can
and
that's
been.
Actually,
we
haven't
really
had
any
merge
issues
which
has
been
nice
people
who
have
been
wrangling
pr's.
Thank
you
because
you've
flown
it
out
where
it
needs
to
be
rebased
on
to
release
112
as
opposed
to
master.
So
that's
the
nice
Gibbs
nice
little
feature
of
letting
me
just
simply
change
the
base.
D
It's
also
really
nice.
So
that's
that's
been
cool
other
than
that
I
I
was
trying
to
put
stuff
in
the
113,
milestone
and
I.
Don't
know
if
I
have
the
ability
to
create
milestones
inside
of
the
repo
I,
don't
need
it,
but
basically,
if
a
113
milestone
could
be
created,
I
would
love
for
that
to
be
in
existence.
So
then
I
can
push
some
of
the
docs
that
are
saying
113.
Instead
of
just
clearing
the
milestone
and
saying
okay,
well,
I'm,
not
gonna
pay
attention
to
this
anymore,
I
could
simply
set
it
up.
D
C
C
A
Sweet
Thank,
You,
Jennifer,
so
misty
also
had
a
suggestion,
which
is
rather
than
granting
repo
admin
permissions
to
release
Meister's
that
we
can
just
open
for
things
like
opening
new
milestones
that
we
can
also
just
have
released.
Meister's
open
up
a
PR
requesting
that
from
the
what
I
can't
remember
the
team,
but
the
repo
team
saying
hey,
we
need
to
open
a
new
milestone
or
create
a
new
milestone.
Is.
D
A
A
A
D
Would
love
to
be
able
to
automate
as
much
of
this
as
humanly
possible?
You
know
I
mean
not
that
it's
you
know
like
there's
there's
no
way
that
a
release
Meister's,
never
gonna,
get
away
from
manually.
Reviewing
poll
requests
which
is
I
would
argue
the
most
valuable
work
and
we
release
my
sister
does.
But
a
lot
of
the
other
sort
of
play
go
here.
Talk
to
this
person
tell
them
that
remind
them
of
this.
D
This
that
and
the
other,
like
all
of
that
is
on
a
time
schedule
and
a
robot
can
do
stuff
really
really
well
and
not
forget
things
and
drop
stuff
on
the
floor.
So
like
automated
creation
of
milestone,
automated
keeping
branches,
up-to-date
automatic
bugging
people
and
slack
and
and
and
github,
and
all
that
good
stuff.
So
that's
actually
something
I
was
thinking
about
trying
to
flesh
out
a
bit
more
so
I'm
in
a
shadow
for
docs,
again
next
release
and
then,
but
basically
kind
of
like
not
really
shadow
but
more
mentor.
Slash.
D
A
Ice
I
am
thoroughly
in
favor
of
it.
The
work
that
you've
been
doing
and
documenting
in
your
own
repo
for
for
automation,
for
review
automation,
specifically
the
the
piece
that
you
use,
the
github
graph
QL
to
create
I
think
is
awesome
as
a
review
tool
for
releases.
So
any
work
that
you
can
do
or
are
interested
in
doing
I
mean
it
sounds
like.
A
D
A
D
A
B
A
D
C
I,
don't
with
this
towards
the
end
of
1-10
I.
Think
probably
you
all
have,
but
what
happened
in
110
was.
There
were
some
related
issues
and
some
of
the
cigs
and
Josh
burkas
and
I
wound
up
attending
sig
meetings
and
basically
letting
folks
know
as
part
of
the
agenda.
You
are
not
going
in
unless
you
step
up
and
pay
attention
to
tests
and
Docs,
because
at
that
point
Josh
was
leading
tests,
and
so,
if
you
can
find
an
ally
or
go
at
yourself,
I
mean
I
was
prepared
to
do
it.
C
A
D
And
and
Tim
and
and
Steven
have
both
because
I've
just
presented
me
like
hey
here,
are
the
facts:
I
think
we've
done
our
work
and
they're
like
okay.
Well,
then
they
didn't
make
it
and
I
was
like
geez
it's
it's!
It's
rough
like
it's
gonna,
be
so
much
effort
to
pull
it
out
of
the
codebase,
but
okay
and.
A
E
A
Excellent
good
work
on
1.12
the
light.
The
light
at
the
end
of
the
tunnel
draws
near
hang
in
there
all
right.
Let's
move
on
I,
don't
see
Vlad
here
to
talk
about
the
focal
chatbot.
But
let's
give
a
brief
summary
then,
in
in
lieu
of
having
a
larger
conversation
with
dad,
so
the
the
working
group
that
we
put
together
to
talk
about
the
the
chatbot
that's
been
active
in
kubernetes
slack
since
June.
A
We
met
with
glad
the
vocals
designer
yesterday
and
he
pointed
out
that
this
bot
is
drawing
its
information
from
three
different
sources:
they're
drawing
from
kubernetes
Doc's,
Stack
Overflow
and
some
AI
and
natural
learning.
That's
drawing
answers
from
conversations
in
the
in
the
slack
channels
themselves.
A
A
Glad
gave
us
the
option,
I
guess,
to
enable
a
vocal
bots
for
sig
Docs,
and
it
seems
like
an
interesting
idea.
Jennifer
do
you
wanna?
Do
you
want
to
talk
more
to
the
particulars
I
know
you
that
you
were
enthusiastic
about
it
yesterday?
Is
there
do
you
is
that
do
you
want
to
pick
it
up
now
and
talk
about
it?
A
little
bit
I
can.
C
Say
just
a
little
bit
we
didn't
get
into
this
yesterday
on,
but
I
see,
the
value
would
have
bought
more
in
the
channels
where
it's
currently
working,
then
in
cig
Knox
itself,
people
don't
tend
to
come
to
sig
Docs
with
technical
questions
about
kubernetes.
C
They
tend
to
show
up
to
kubernetes
users
or
kubernetes
novice,
where
the
bots
already
running,
and
so
what
I
think
would
be
most
interesting
for
this
group
is
to
take
a
look
at
the
data
from
those
that,
from
from
the
bottom,
there
there's
and
there's
a
kind
of
rough
you
eye
for
aggregate
reporting
and
then
Vlad's
willing
to
give
us
access
to
the
raw
data
as
well.
There's
not
a
lot
right
now.
C
People
are
saying
well,
I,
looked
at
that
topic
and
it's
confusing
or
I
couldn't
make
this
thing
work,
or
it
glad
showed
us.
There's
there's,
like
you,
know,
one
or
two
questions
where
people
have
come
across
commands
in
the
docs
that
they
can't
get
to
work.
That
seems
like
gold
and
information
for
us
to
figure
out
where
to
focus
our
attention
at
a
very
high
level,
just
knowing
where
people
are
tending
to
look.
The
most
line
already
has
a
sense
of
that.
C
A
C
E
C
F
F
C
That's
kind
of
in
the
back
of
my
head
and
whatever
we're
going
to
get
information,
I'm
wondering
right,
trying
to
sort
of
hold
my
my
mind
open
about
it,
but
wondering
whether
we're
gonna
get
information
about
key
areas
where
we
might
want
to
think
about
restructuring
it
ox2
or,
as
you
suggest,
you
know,
providing
some
some
more
ways
of
presenting
the
same
content.
I'm
god
forbids
moving
into
something
like
thank
yous.
C
Well,
maybe
here
we
would
really
have
some
frequently
asked
questions
that
are
that
way,
right,
I,
don't
know,
I,
don't
know
yeah,
but
yeah
I.
Think
thanks
for
the
reminder
and
I
will
try
to
you
know
come
up
with
both.
You
know
some
stories.
You
bet
the
data
I
don't
see
if
we're
ready
for
anything
is
full-blown
as
analysis
yet
and
I'm
thoughts
about
what
we
might
deal
with
it.
Yeah.
F
C
C
You
know
we're
coming
up
on
that's
more
than
a
year
and
a
half
I've
been
saying:
what's
my
audience,
what's
my
audience,
what
do
they
need?
What's
my
audience,
people
say
cluster
admin.
People
say
cluster
operator.
They
offer
up
all
these
elaborate
personas
which
do
not
answer
the
question
at
all.
This
is
the
first
time
I
feel
like
I've
got
a
chance
to
understand
not
just
who
people
are
with
their
job.
Descriptions
are
like
what
they're
actually
trying
to
do
when
having
trouble
with
so
I'm
pretty
excited
I.
D
C
A
B
Working
group
yeah,
so
let
me
grab
the
link
really
quick,
I
shared
the
sort
of
proposal
for
what
the
group
would
be
up
to
you.
Last
week,
I'm
gonna
put
that
in
the
chat
here
myself
and
a
couple.
Others
have
modified
it
a
bit
expanded
the
scope,
a
tiny
bit
to
include
some
things,
I'm
pretty
excited
about
so
I'm,
not
sure
if
this
is
shareable
with
all
of
you,
but
his
Android
Chen
in
the
meeting
I,
don't
see
him
he's
not
he
reached
out
to
somebody
you'll
see
the
second
Google
Doc.
B
The
presentation
he
reached
out
to
somebody
I
think
he
knows
who
did
some
some
SEO
and
site
latency
analysis
and
put
together
a
little
presentation,
so
this
I
think
will
be
so.
One
of
the
the
imperatives
of
the
group
is
to
make
sure
that
site
latency
is
kept
within.
You
know
reasonably
acceptable
bounds
and
and
I
think
that
this
that
this
assessment
will
sort
of
paint
will
sort
of
show
us
a
path
to
how
to
get
there.
I
think
the
scores
are
pretty
good
overall,
but
there
are
some.
B
B
It's
just
like
a
Google
Docs
presentation,
thingy
that
second
link
all
right:
okay,
yeah
I'm,
not
quite
sure
yeah
I'll
talk
to
Andrew
about
that
I'm,
not
sure
what
the
what
the
story
on
permissions
is
there.
But
so
that's!
So
that's
one
little
development
I
think
I'm
gonna.
Let
Andrew
kind
of
spearhead
that
that
particular
effort,
because
he
seems
know
his
way
around,
and
so
you
have
a
good
handle
in
the
situation.
Another
initiative
underway
is
Raj.
B
He
pointed
something
out
to
me,
which
I
I,
don't
believe
that
she's
in
the
meeting
pointed
out
that
we
haven't
really
thought
much
about
site
accessibility,
and
so
she
wants
to
spearhead
an
effort
to
to
improve
our
story
there
and
I
think
is
the
first
step.
She's
gonna
get
back
to
get
back
to
the
working
group
within
a
couple
days
with
some
rep,
with
kind
of
an
assessment
of
like
what
kind
of
tooling
we
could
potentially
have
in
place.
You
know
I've
put
together
some
kind
of
plan
of
action.
B
B
Think
that's
why
I
had
report
on
the
the
actual
like
concrete
process
side
I
got
in
touch
with
the
appropriate
people
about
getting
another
slack
channel
and
I
think
that
that
that
efforts
kind
of
stalled,
so
I
need
to
send
out
some
friendly
pings
right,
maybe
after
this
meeting
but
but
yeah.
That's
where
things
are
at
at
the
moment.
A
Excellent,
thank
you.
Yeah
I'm
super
excited
to
hear
about
about
Rajee,
taking
on
accessibility
improvements
in
particular,
yeah
we're
not
really
doing
anything
actively
on
the
site
at
this
point,
even
just
some
best
practice,
tooling.
Just
some
best
practices
for
for
accessibility
and
having
having
moving
forward
in
that
area,
meaningfully
I
think
will
be
huge,
so
I
think
you
look
for
tearing
that
group
and
moving
that
work
forward.
A
A
It
looks
like
the
manual
path
for
just
passing,
commits
back
and
forth
between
the
repo
like
manually,
created,
mitts
back
and
forth,
between
misery
posts
is
more
or
less
equivalent
to
any
advantage
gained
by
trying
to
follow
either
a
sub
tree
or
a
sub
module
path.
So
we'll
talk
again,
but
that's
sort
of,
though
that's
the
way
it's
leaning
right
now
is
just
make
commits
back
and
forth
between
the
repos,
but
we'll
meet
again
this
right
after
this
meeting
and
confirm.
A
C
Vote
for
deferring
to,
but
I'm
I
just
want
to
say,
I'm
really
glad
that
somebody's
taking
us
up,
because
it's
definitely
broken
the
way
it's
being
used.
Now
there
I
did
come
across
a
polar
quest,
not
looked
at
its
current
state.
That
seemed
pretty
designed
to
address
the
problem,
but
it
addressed
it
at
the
level
of
fixing
the
short
code,
not
at
the
level
of
best
practices
and
we're
up
against
not
just
a
short
code
use
issue,
we're
up
against
how
features
are
developed
and
documented
issue
multiple
weight
as
a
big
can
of
worms.
G
Talk
about
it
if
you
need
misty
for
anything
specific,
it
probably
would
be
good
to
reach
out
to
her
specifically
before
the
meeting
as
she's
kind
of
turning
her
attention
to
some
other
things.
Right
now
and
probably
won't
be
attending
de-facto.
But
if
you
meet
her
for
anything,
maybe
Zach
just
email,
her
and
let
her
know
is
like
we
want
to
talk
about
X
topic
in
X
meeting.
Can
you
please
come
and
she'll
be
there?
Okay,
it's
a
good
reminder.
Tom.
A
A
E
A
E
Well,
you
know,
and
then
you
know,
if
I
start
going
back,
stir-crazy
I'll
do
a
future.
Well,
I
got
power
cuz,
you
know,
III
have
nobody
here,
my
family's
in
Florida,
my
daughter's
at
college.
So
but
I
did
run
into
a
few
things.
It
turns
out.
I
got
to
run
some
supplies
to
my
daughter
in
Chapel
Hill,
because.