►
From YouTube: Kubernetes SIG Docs 20170815
Description
Meeting notes: https://docs.google.com/document/d/1Ds87eRiNZeXwRBEbFr6Z7ukjbTow5RQcNZLaSvWWQsE/edit#heading=h.jd5qvxb36ts4
The Kubernetes special interest group for documentation (SIG Docs) meets weekly to discuss improving Kubernetes documentation. This video is the meeting for 15 August 2017.
https://github.com/kubernetes/kubernetes.github.io
A
We
can
get
started
I,
so
hi
I
am
Zach
cor,
listen,
I'm!
The
editor
for
kubernetes
Jared,
who
has
run
this
meeting
in
the
past,
has
asked
me
to
start
running
this
meeting
so
I
apologize.
This
is
my
first
time
running
this
meeting.
So
it's
this
recording
somehow
goes
into
the
void,
I
apologize
and
we'll
do
better
next
week.
A
Happy
news
we
have
two
new
Sig
ducks.
Maintainer
is
Jennifer
Rondo
and
myself
that
if
the
process
of
becoming
a
maintainer
is
something
that
you're
curious
about,
please
ask
either
Jennifer
or
myself.
We
can
both
speak
pretty
knowledgeably
about
it
so
functionally.
What
this
means
is
that
we
have
a
little
more
power
in
the
repo
to
move
things
around
in
potentially
dangerous
ways,
but
we
have
promised
to
use
our
powers
for
good
all
right.
Moving
on
to
our
agenda,
Steve
there's
an
item
for
giving
people
analytics
access.
B
Sorry
we
we
have
six
people
now
from
the
this
thing
you
have
analytics
access
and
I
submitted
those
in
a
batch
to
Nate
Karcher
at
the
Linux
Foundation
he's
the
one
who
can
Congrats
s
so
going
forward.
Any
individuals
who'd
like
to
have
access
can
contact
Nate
carton
of
direction.
I
think
his
email
address
he's
a
little
lower
down
end
up
getting
notes
back
about
it.
For
that.
A
C
A
So,
thank
you.
Steve
again
for
google
analytics
access
contact
need
koechner,
address
available
further
down
in
the
big
box
meeting
notes.
Alright.
Moving
on
to
luke
for
doctor
review
for
comment,
diagram
assets,
click
with
us,
you
I
do
not
see
him.
A
Moving
on
reprolabels,
so
Jared
and
I
took
a
look
at
the
the
the
label
with
the
labels
for
issues
and
PRS
that
we
have
in
the
repository
I.
There
are
a
hundred
and
forty
four
of
them.
It's
too
many
it's
a
cumbersome
process.
They
don't
outside
of
a
very
small
handful
that
see
regular
use.
It's
just
it's
a
clutter,
so
what
I
will
be
doing
over
the
next
week
or
two?
Well,
it's
yeah
what
I'm?
A
A
So
I
have
learned
the
hard
way
from
past
experience
that
removing
removing
a
label
when
the
repo
means
it
has
gone
forever,
so
I
would
rather
get
consensus
and
make
sure
that
that's
something
that's
transparent
to
everyone
before
fully
taking
action
on
it.
So
if
you
are
interested
in
that,
send
me
a
message
on
slack
or
just
watch
rush,
the
watch,
the
Pierre
log
in
the
repo-
and
you
see
the
shoe
for
label
removal
coming
up
soon.
A
Issue
so
after
Friday
of
next
week,
I
will
be
out
on
vacation
for
two
weeks.
I
have
already
made
arrangements.
A
radical
new
community
member
who
attended
last
week
has
already
volunteered
to
handle
issue
triage
while
I'm
out,
and
we
did.
We
did
a
practice
run
of
a
shoe
triage
this
week
and
she
did
great
so
with
Veronica
will
be
doing
issue
triage
for
the
next
two
weeks.
They'll
be
back
on
September,
5th,
Tuesday,
September
5th,
so
through
then
radical.
We
handle
an
issue
triage.
A
A
Get
and
while
Radhika
might
not
be
the
best
choice
for
PR
review.
That
said,
it
would
be
awesome
to
have
another
person
doing
reviewing
PRS
that
have
been
submitted.
The
work
itself
is
fairly
straightforward.
Pr
review,
there's
just
a
lot
of
it.
A
F
I
realized
that
I'm
new
to
actually
working
you
know
steadily
at
this
level
in
the
repo
but
I.
This
is
something
I'd
been
meaning
to
ask
Andrew
about
anyway,
especially
now
that
I
mean
I'm
a
maintainer,
so
I
would
be
willing
to
take
on
that
work.
If
you
think
that
my
level
of
experience
is
appropriate,
I've
dealt
with
this
kind
of
triage
before,
although
not
in
this
particular.
D
F
F
D
F
D
A
E
A
D
D
D
D
A
Absolutely
so
I
think,
then
what
I'm
hearing
is
that
Andrew
and
I
will
remain
just
just
the
two
of
us
on
the
auto-assignment
list.
For
now,
am
I
hearing
that
correctly
and
then
others
can
come
in
and.
E
D
So
maybe
I
should
explain
the
auto
assignment.
Actually
it's
not
that
hard
to
change
like
in
the
root
directory,
there's
an
owner's
file,
and
that
is
where
it
looks.
So
it's
actually
not
that
hard
to
make
these
changes
right
now,
you'll
see,
there's
just
Zach
and
myself
under
reviewers,
so
we
could,
you
know,
add
people
even
temporarily
or
remove
them
so
like
I
could
remove
Zach
from
that
file
like
while
he's
gone
and
then
add
them
back
and
then,
if
anyone
wants
to
sort
of
help,
fill
in
I
could
put
them
in
temporarily
something
that.
F
E
D
A
A
C
A
Feel
like
even
just
having
a
review
like
when
we,
when
sort
of
when
a
maintainer
or
a
collaborator,
comes
to
an
issue
and
seeing
that
it's
already
been
reviewed
by
somebody
on
our
list
is
helpful.
It
means
it
cuts
down
the
amount
of
the
amount
of
review
up.
I
think
it
goes
into
that
so
I
if
it
works,
I'm,
certainly
glad
to
do
it.
Oh
yeah.
C
A
A
C
F
F
F
A
A
B
Yeah
sure
so
I
think
too
waited
to
do
this
to
keep
it
simple
is
just
if
some,
if
you're,
not
a
maintainer-
and
you
want
to
take
an
issue-
just
put
a
comment
in
the
issue
that
says
Steve,
Perry,
Andrew
I
will
work
on
this
issue
and
then
we
will
spot
that
and
we
can.
Then
we
can
make
you
a
outside
collaborator
with
read
access
that
will
allow
us
to
assign
issue
to
you
and
then
we
can
go
in
and
move
the
in
Liam
in
the
project
page.
B
A
G
So
so
Stephen
against
this
I'm
SQL
engineer
at
core
OS
so
just
want
to
get
more.