►
From YouTube: Kubernetes Sig Docs 20180925
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 25 September 2018.
https://github.com/kubernetes/website
A
A
A
Have
a
note
here,
I
think
we're
going
to
I,
don't
see
Raji
here
she
might
join
us
in
a
little
bit
or
she
might
not,
but
I
think
unless
she
joins
us.
I
would
say:
let's
hold
off
on
discussing
accessibility
until
Raji
can
talk
more
about
the
tools,
but
I
would
encourage
folks
if
you
haven't
looked
at
the
links
yet
for
the
accessibility
tools.
That
Raji
is
proposing
that
we
use
to
take
some
time
this
week
and
check
those
out.
A
Let's
see,
let's
move
on
to
reap
reap
Oh
branching
strategy.
So
in
last
week's
weekly
meeting
we
had
talked
about
the
possibility
of
using
sub
trees.
There
have
been
sort
of
two
discussions
that,
whether
whether
we
should
use
internationalization
repos
encourage
internationalization,
repos
to
use
commits
back-and-forth
or
whether
we
could
use
sub
trees
and
after
investigating
sub
trees.
A
They're
really
good.
If
you
have
a
very
simple
strategy
with
one
branch
to
be
concerned
about,
but
if
you
need
to
do
more
than
that,
like
we
do
with
kubernetes
with
the
kubernetes
website,
they're
really
really
difficult
to
a
scale
and
complexity
very,
very
quickly
and
they're,
pretty
fragile
as
well.
There's
not
what
you
add
a
sub
tree,
there's
no
way
to
remove
it,
and
you
can't
even
poll
to
see
whether
you
have
a
sub
tree
set
up.
A
The
we
have
a
working
group
for
branching
strategy.
We
have
a
meeting
set
up
for
Thursday,
but
it's
looking
like
what
we're
going
to
do
is
confirm.
We
in
order
to
get
content
back
and
forth
between
kubernetes
website
and
internationalization
repos,
that
we're
going
to
ask
that
contributors
simply
pass
commits
back
and
forth
between
repositories.
A
A
B
B
B
B
We
need
to
get
periodic
update,
I
think
it
should
be
done
in
two
weeks,
every
two
weeks
when
we
are
ready
to
push
in
perspective
of
downstream
maintenance
when
he
read
it
through
push,
we
need
to
push
to
upstream
and
pull
from
upstream,
and
we
are
when
we
are
not
ready
to
push.
We
need
to
pull
from
upstream
to
update
the
changes.
B
B
B
First,
we
need
to
poke
from
oncoming
number
one
from
upstream
to
downstream
and
we
add
common
number
two.
We
need
to
add
coming
number
two,
so
there
we
can
maintenance,
our
own
maintenance
can
manage
our
friends
coming.
Number
two:
is
olive
oil
changing
so
account
number
two
most
that
push
to
obtain.
B
A
C
Yeah,
just
looking
briefly
at
this,
are
we
missing
an
easy
win
to,
instead
of
making
the
branching
strategy
in
line
with
the
Cooper
nays?
That
IO
have
like
a
sub-domain
like
a
coyote
Cooper
nays
that
IO
and
CN
that
Cooper
nays?
That
IO
is
that?
Did
we
explore
that
or
at
all
I
know,
I'm
coming
can't
come
becoming
any
kind
of
late
here,
so
the.
A
D
A
Hugo
constructs
links
based
on
when,
when
there's
a
language
translation
available
in
so
in
config
that
tamil,
you
specify
whether
there's
a
language
available
and
if
there
is
then
any
content
available
and
that
will
follow
the
path.
So
right
now,
like
docs
in
English,
are
kubernetes
audio
/.
En
so
I
mean
we
could
add,
we
could
register
the
subdomains
and
do
it,
but
it
seems
like
a
little.
B
On
the
downstream,
when
we
make
a
change
on
to
the
downstream
on,
there
will
be
changes
also
on
to
the
upstream.
So
we
need
to
budget
of
both
streams
changes
into
a
single
French,
so
we
need
to
make
another
working
branch
name.
Our
thetac
scale
that
one
through
K
through
and
we
will
are
going
to
be
based
on
through
the
upstream,
because
the
Austrian
branch
is
not
protected,
so
sometimes
it
is
force
operated.
B
B
B
This
is
the
most
complex
part
of
this
right
when
he
led
it
to
push.
We
need
to
make
a
single
compound
single
squash
to
commit
on
our
own,
the
user
website
repository
that
is
not
kubernetes
organization
depository,
because
current
Kedar
scale
repository
is
not
guitar
poped
report,
so
we
can
make
a
pretty
cast
from
the
kadar
scale,
historic.
D
B
So
Korean
translation
team
has
our
shared.
B
B
B
B
B
B
B
A
A
So
both
yeah
okay
and
using
that
to
meaningfully
like
take
all
the
work
for
this
I
guess
it
would
be
comparable
to
a
milestone,
squashing
everything
into
that
milestone
and
then
passing
that
I
think
as
a
commit
so
Jin
yi
are.
You
is
the
plan
to
use
those
squash
commits
to
commit
to
make
those
commits
to
K
website
to
push
up
stream
to
K
website.
B
E
I
was
gonna,
say,
I
think
that
the
one
thing
that
would
help
me
would
be
if
they
had
a
documentation.
That
said,
here's
all
the
steps
we
do
when
we
do
this
when
we
switch
a
branch
just
so
you
can
actually
just
call
me.
The
pictures
are
very
helpful,
but
just
to
see
the
concrete
steps,
I
think
I
know
it
would
help
me
just
to
understand
I,
don't
like
that's
how
they
teach
teach
the
new
people
how
to
do
it,
but
somewhere
I'd
like
to
sell
document
and
the
guests.
B
No,
it's
a
it's
really
too
many
just
playbook.
Some
kind
of
play
go
yeah.
D
So
let
me
ask
one
question
that
might
be
related
to
Brad's
question.
So
is
the
reason
for
the
additional
branch
that
you
use
for
squashing
is
the
reason
that
you
don't
want
to
lose
the
history
on
the
working
branch?
So
you
don't
want
to
squash.
The
working
branch
is
that
why
you
create
the
additional
branch.
A
I
think
we're
we're
curious
Junie,
but
we
our
goal,
is
to
help
and
to
be
as
helpful
to
you
as
possible.
So
our
questions
are
for
the
purpose
of
understanding,
not
certainly
not
because
we
think
you're
doing
anything
wrong.
I
think
your
your
work
is
fantastic
and
your
ability
to
explain
it
effectively
is
is
superb
I
think
we
just
want
to
be
as
helpful
to
you
as
we
possibly
can.
A
B
A
Thank
you
very
much
and
thank
you
to
you
to
you
and
your
team,
both
you
and
Claudia.
Thank
you
very
much
for
the
work
that
you're
continuing
to
do.
We
are
learning
a
lot
from
you,
I
think
in
the
future.
We
will
be
careful.
The
next
translation
project
that
comes
along
will
fork
off
of
key
website
just
to
make
everybody's
life
easier.
We
didn't
even
think
about
doing
that
back
when
we
set
this
up
and
I
think
now
how
how
much
more
helpful
that
would
have
been
so.
A
We're
very
very
grateful
and
I
am
very
inspired.
So
many
thanks
to
you
alright
Jim
I
know.
Last
week
you
had
expressed
interest
in
being
invited
to
the
working
group
for
branching
branching
discussion.
So
if
you
had
lost
your
email,
will
you
send
it
to
me
outside
so
that
I
can
get
you
an
invite
to
the
working
group
Robert.
C
A
You
Ginny
and
Claudia
I
know
that
the
time
is
deeply
inconvenient
for
you.
The
meeting
I
think
is
on
Thursday.
A
B
D
A
A
Think
that's
a
great
idea,
even
more
than
that,
I
think
it
would
be
helpful
to
do
that
more
frequently,
I
think
six
months
between
between
those
kinds
of
goal-setting
sessions
is
just
too
long.
I
mean
when
I,
when
I
think
about
May,
which
was
only
what
like
four
months
ago,
that's
a
license.
Yet
only
four
months
ago.
A
My
goal
and
the
things
that
I
would
like
to
work
on
are
making
sure
that
our
our
intro
material
to
kubernetes
is
as
good
as
possible.
I
still
think
that
we're
lacking
in
some
areas,
so
I
can't
talk
about
it
yet,
but
I
mean
in
the
Avena
I'm
talking
right
now
with
a
potential
contractor
who
I
would
bring
on
board
to
focus
exclusively
on
that
on
that
content.
A
A
A
C
Speak
a
little
to
that
I
heard
that
Zak
generated
other
Zak
generated
the
docks
yesterday,
I
believe
and
pretty
much
the
PR
that
I
opened
up
for
the
112
branch
is
ready
to
merge
and
nothing
is
really
changing.
This
anything
major,
just
kind
of
waiting
to
get
our
steps
in
mind
with
the
one
actual
branches
being
released.
For
you
know
the
latest.
You
know
coup
Bernays,
112,
stable,
so
I
think
that's
tentative
for
originally
heard
Thursday,
but
I
think
that's
already
moved
since
I've
last
heard.
C
Yeah
and
I
talked
to
Andrew
a
little
bit
about
that
and
we
ended
up
just
merging
the
change
that
we
were
talking
about
to
the
PR
and
we're
just
kind
of
trudging
forward
through
that
figuring.
If
we
do
end
up
breaking
some
eggs,
making
an
omelet
we're
gonna
fix
them
with
be
ours
and
yeah
move
forward
that
way.
Yeah
cool,
okay.
A
D
F
C
D
I'm
I'm,
in
some
sense
the
owner
of
kubernetes
incubator,
reference,
Docs
and
I,
haven't
looked
carefully
it.
You
know
it
what
that
means
as
far
as
what
I
can
do
compared
to
what
other
people
can
do.
But
I
can
imagine
that
at
some
point
during
this
next
three
months,
we'll
want
to
you
know,
name
somebody
else
to
take
on
that
role.
A
E
F
All
right,
so
we
kind
of
had
to
pivot
on
what
we
were
able
to
do
for
thinking
the
right
solution
and
there's
gonna
be
changes
like
Andrew
and
I
are
going
to
the
st.
cloud
provider
and
there's
kept
there
that
we're
gonna
have
to
work
on
refactoring
and
that's
going
to
do
some
information
architecture
changes
and
that
can
better
inform
the
navigation
on
the
setup
page
currently.
But
all
that
to
say
is
it's
gonna
be
a
work
in
progress.
That's
gonna
be
a
little
bit
longer.
E
And
then
we
talked
about
trying
to
get
resources
from
you
know
the
different
different
companies
or
whatever,
to
help
with
the
cloud
provider
stuff.
If
I
recall,
Zack
I
do
have
a
person
that
was
interested,
so
I
just
need
to
know
the
right
place
and
where
to
connect
and
I've
been
really
busy
and
some
other
special
projects.
E
E
E
F
E
Right
yeah,
because
I
I
guess
I
haven't
call
seeing
it
so
it'll
be
interesting
to
see
what
the
vision
is
of
how
that's
gonna
work.
I
know
how
it
works
today,
right
with
the
NAB's,
and
there
are
certain
things.
Entry
but
yeah
that'll
be
curious
to
see
that
the
division
I
know
it's.
You
know
it's
a
very
long
process,
of
course,
but
it'd
be
first
to
see
what
the
vision
is.
Have
you.
A
That
would
be
the
kept
that
Cody
mentioned
is
from
our
from
in
for
CID
cloud
provider.
So
if
you
want
to
see
like
what's
what
is
cooking
in
terms
of
specifics,
I
think
am
I
right
that
Cody
is
that
the
kept
that's
in
process?
Okay,
yeah!
There's
a
there's
a
kept
in
process
to
discuss
exactly
that
architecture
that
cloud
providers
are
agreeing
sort
of
among
themselves
about
what
that
could.
What
that
can
look
like.
F
A
E
F
A
A
A
A
Good,
so
part
of
the
reason
why
Cody
step
back
is
because
it
would
have
been
a
cloud
provider,
editing
descriptions
about
cloud
providers
by
other
cloud
providers
and
that
gets
into
some
very
tricky
business
very
quickly
and
it
just
it
puts
Cody
and
it
puts
Google
in
a
very
awkward
situation.
So
I
think
that
was
very
astute.