►
From YouTube: Kubernetes SIG Docs 20190219
Description
Meeting notes: https://docs.google.com/document/d/1zg6By77SGg90EVUrhDIhopjZlSDg2jCebU-Ks9cYx0w/edit#
The Kubernetes special interest group for documentation (SIG Docs) meets weekly to discuss improving Kubernetes documentation. This video is the meeting for 19 February 2019.
https://github.com/kubernetes/website
--
10:43:28 From Chris Hoge : chris@openstack.org
10:43:31 From Chris Hoge : hogepodge on slack
10:56:51 From rchen : I have a quick question about how to collaborate with the external efforts
10:59:45 From Kubernetes Sig Docs : Rui: Sure, which external efforts in particular?
11:01:51 From Zach Arnold : I have to run to an 11 o clock, but thanks everybody!!!! YOU GUYS ROCK!!!
11:01:58 From Kubernetes Sig Docs : Thanks Zach!
11:04:17 From Chris Hoge : possibly
11:04:51 From stevepe : Hacking and Hardening Kubernetes Clusters by Example https://www.youtube.com/watch?v=vTgQLzeBfRU&t=17s
A
A
B
C
A
A
C
A
A
A
So
let's
talk
about
setting
our
sigdoc
summit
for
the
end
of
march,
let's,
let's
take
a
look
at
some
dates.
Really
quick
I
know
that
when
we
met
in
Seattle
in
December
we
talked
about
doing
an
online
summit
and
I
think
that
makes
the
most
sense
it's
going
to
be
the
the
way
to
get
the
maximum
contributors
involved.
So
let's
take
a
look
at
dates
for
the
end
of
March.
C
C
A
C
A
D
D
C
C
A
E
A
A
C
A
Let's
see
we
can.
We
can
get
more
visibility
on
that
date
through,
like
through
slapping
through
email,
we're
still
speaking,
speak
of
the
man
and
he
appears
Brad,
so
cool.
Do
you
have
arrived
in
a
very
timely
fashion,
so
for
our
second
quarter
planning
meeting,
we
are
looking
at
Thursday,
March
28th
from
3
to
6
p.m.
Pacific
and
we're
wondering
if
that
time
works
for
you.
We
know
it's
late
in
the
evening
for
for
East,
Coast
folks,.
D
A
A
Excellent
and
if
there
is
a
conflict,
please
let
us
know
sure
all
right.
Let's
move
on
with
the
agenda,
so
I
want
to
plug
for
Syd
cloud
provider
and
Gaye
that
Chris
Hodge
is
here
so
I.
Think
after
talking
with
Syd
cloud
provider
in
the
kubernetes
community
meeting
last
week,
I
think
it
would
just
be
really
helpful
for
Syd
cloud
provider
if
they
had
someone
to
do
kind
of
the
big,
deep
language
and
mechanics
wrestling
on
their
proposed
cap.
A
Template
for
cloud
providers,
and
specifically
this
is
in
the
context
of
information
for
like
the
pick,
the
right
solution
page
and
revising
that
entire
section,
so
Chris
feel
free
to
jump
in
but
as
I
understand
it
you've
got
a
template.
I
kept
template
or
sorry
I
kept
open
for
a
template
that
cloud
providers
would
use
to
provide
information
about
themselves
and
getting
some
review
on
that
and
getting
getting
some
like
just
dedicated
help
in
structuring
what
that
information
looks
like
for
sig
cloud
provider,
but
that
would
be
really
helpful
for
you
is
that
correcting?
E
A
E
A
D
A
D
Yeah
go
for
it,
okay,
so
he
actually
think
about
the
this
weekend.
If
actually,
the
issue
flow
board
that
has
a
local
Asian
team
member
developer
commanding
an
issue
attackers,
we
actually
have
kind
of
a
location
management
tool.
They
use
a
demeanor
which
I
work
for
so
the
I
just
for
share
appeal
from
my
soul
may
be.
The
truly
yourself
is
not
fully
good
enough
for
our
I
just
want
to
share
an
idea.
So
the
motivation
party
is
right.
Now
we
work
really
there,
which
was
making
work
outside
the
actual
segmentation
right.
D
A
life
cycle,
because
the
translation
has
to
be
after
the
actual
documentation
is
weakened.
I
would
actually
outside
the
writing
life
cycle.
So
the
translation
Komodo
is
the
dealer
on
the
issue
tracker:
either:
training
or
Japanese
team
Jewish
record
1001
we're
trying
to
sort
of
generate
record
Amina
who
actually
in
Europe
for
the
issue
tracker
to
manage
the
content,
mobilization,
college
yeah,
actually,
cognitive
problem,
so
first,
the
one
you
actually
require
you
to
have
to
have
tea
there,
water
flow
panting.
D
You
used
to
be
media
with
peak
kiss
in
the
pool
request
and
you
need
to
do.
Coa
actually
area
is
multiple.
The
PPR
review
is
either
very
heavy,
so,
like
we
can,
team
has
a
community
two
packages
and
what
I
find
their
problem
then
usually
for
the
for
the
easier
one,
the
easy
to
pick
it
up.
Like
example,
I,
say:
oh
I,
see
I
come
online
translation
like
which
flag
means
work.
Things
like
that.
D
It's
very
easy
if
you
got
a
full
along
identical
like
a
broad
like
actual
top
a
setup
path
toward
the
carpet
and
a
very
hard
to
work
out.
So
we
actually
know
easy
to
managing
issue
can
have
an
issue
so
I
leave
you
the
screenshot
content
we
have
for
the
challenge
came
to
have
issues.
We
have
a
separator
issue,
tracker
repo.
We
talked
about
it
in
cube
town
shanghai,
but
if
you
happen
to
have
chocolate,
we
have
a
little
for
women
in
many
many
men
Alameda.
D
So
right
now
come
in
to
my
attention
that
I
recently
learned
at
our
company
that
we
used
to
transfer
experiments
in
the
local
edition.
So
we
have
react
along
with
the
reactor
after
the
level
cognac
as
international
dishes,
actually
cool
in
the
transition,
so
sort
of,
like
a
variable
most
of
your
I
believe
we
are
actually
using
only
for
UI
label
or
description,
so
we
have
divided
into
three
people,
one
in
the
engineer's
like
me,
so
we
put
in
the
translation
work
the
other
ones.
D
Localization
manager
could
be
anyone
who
is
more
from
here
with
the
localization
economist
seconds
them
and
the
first
things
will
translate
cervezas
only
down
the
translations.
It
could
be
anything
work
piece
of
legislation
and
when
the
position
gallery,
it
could
be
any
any
time.
So
we
just
automatically
pure
ethically
putting
transitioned
into
our
our
reborn
and
just
a
shield
disappear.
D
So
here's
what
I
have
right
now,
I'm
happy
to
share
more
information.
I
was
I,
get
more
fantasizing
of
this
approach,
because
reasons
are
more
like
here:
three
casual
people,
while
between
right
document,
more
animation
announcement
like
a
low-grade
Asian
manager,
because
it's
already
sweet
to
was
too
coordinated.
D
Effort
like
a
priority
like
the
same,
are
the
thirteen
is
more
important
in
like
how
to
reduce
the
overhead
to
help
the
translator
to
translate
what
what
sort
of
but
chiefly
W
Commission,
is
actually
the
most
difficult
unintended
translation
community
as
well
the
international
community,
because
they're
like
for
Italian
translation
community.
They
we
have
one
a
person
who
can
help
with
this
I'm
kind
of
a
thinking
that
we
should
a
doctor
like
a
machine
tradition,
although
with
the
humor
with
you
to
a
fellow
reader,
the
transition.
G
So
I'm
actually
having
a
flashback.
I
do
remember
many
many
means,
and
years
ago
we
were
using
transifex
transifex
for
OpenStack
translation.
We
had
a
crowd
sourcing
model
and
from
what
I
recall,
the
process
was
pretty
slick
to
trigger
off
the
different
crowd
source
based
translations.
We
moved
to
the
nada,
though.
G
E
D
D
A
So
again
it
sounds
like
this
is
a
really
good
discussion
for
sig
Docs
tools,
because
the
I
mean
this
is
awesome
and
it's
also
out
of
scope
for
a
weekly
meeting.
So
now
it's
all
good
I'm,
really
glad
that
you've
got
this
information
together
and
I
really
want
to
dive
into
it.
But
I'm
gonna
ask
that
you
wrap
it
up
and
continue
the
conversation
in
sig
ducks
tools.
A
A
H
Myself,
yep
all
right,
I
am
gonna.
Keep
this
a
short
winded
as
possible.
I
remember
as
part
of
the
quarter.
One
ideals
and
goals
is
to
be
able
to
bolster
and
beef
up
our
security
documentation
and
aggregate
it
in
a
way
that
it's
easy
to
follow
as
both
a
set
of
concepts
and
a
set
of
tasks
and
I
have
an
idea
of
how
to
do
this
and
I'm
happy
to
carry
the
flag.
But
after
speaking
with
a
few
contributors,
it
seems
like
there
is
interest
from
the
broader
community
to
participate.
H
H
Think
extraordinary
precedent
has
been
placed
in
lots
of
other
tools
where
we've
documented
features
that
we
have
that
are
security
related
and
we've
done
a
terrific
job
of
adding
glossary
items
on
the
various
definitions
of
our
keywords,
but
this
would
be
sort
of
a
way
of
addressing
security
concepts,
one
at
a
time
from
the
cloud
level
all
the
way
in
the
cluster
than
the
container
and
then
at
the
code.
Level
of
this
is
what
security
looks
like,
and
so
the
specific
goal
is
to
add
documentation
to
the
website
to
achieve
that.
F
J
F
J
Would
say
there
is
there's
a
fair
amount
of
documentation
there.
Maybe
the
trouble
is
finding
it,
and
but
some
of
those
topics
have
been
worked
on
fairly
recently,
like
the
pod
security
policy
topic
and
the
network
policy
topic,
so
they
might
be
moved
or
linked
to
better
and
but
in
a
recent,
a
new
material
I
was
doing
good.
C
Yes,
so
so
yeah,
you
know
both
discoverability,
then
maybe
possibly
I
might
be
adding
to
your
mandates.
Accidents
so
I
send
this,
but
possibly
some
best
practices
guidelines
while
we're
at
it.
Since
you
know,
one
of
the
things
that
kubernetes
does
is
offer
you
six
ways
till
Sunday
to
do
just
about
anything.
C
So
you
know
we
might
don't
want
to
get
too
far
into
that
territory,
because
best
practices
are
so
very
often
context
dependent
in
a
way
that
we
can't
document
right.
So
definitely
that's
probably
off
the
table
for
a
certainly
for
first,
if
I
checked
act
but
I
like
just
a
vision
of
the
architecture
that
you
just
gave
us
I
liked
a
lot.
C
J
A
H
Let
us
know
because
we'd
like
to
include
more
people
but
otherwise
I
think
the
first
few
members,
the
charter
members,
would
most
likely
define
the
meeting
dates
and
times
and
and
we
would
have
our
own
sub
set
of
tasks
and
possibly
a
github
project
again.
I
have
not
even
thought
about
how
I
want
to
organize
the
group.
Just
the
content
at
this
point
sure.
A
H
A
D
D
D
D
A
And
unfortunately,
Zach
Arnold
had
to
drop
off
so
I.
Would
that's
a
really
valid
perspective?
I
would
encourage
you
like
I
would
say,
bring
that
up
with
Zach,
like
the
the
first
time
that
the
security
working
group
meets
I
would
raise
that
right.
Okay,
that's
that's
awesome
to
be
aware
of
overlapping
layers
of
concern
like
that
yeah,
okay,
cool
Brad
Cooper
on
Shanghai
yeah.
G
A
A
So
I
see
three
folks
going
I
know:
Roy
I
am
guessing
that,
like
the
localization
folks,
there
want
to
attend.
I,
know
Roy,
you
and
I
had
spoken,
maybe
about
a
month
ago
about
making
time
to
they
do
a
pitch
for
to
do
like
recruitment
for
more
localizers,
more
people
to
work
on
the
project.
So
right
now,
I
have
signed
us
up
for
a
cig,
deep
dive
or
I
guess
a
cig
intro,
and
that
is
a
half
hour
slot
in
the
main
track.
A
A
That's
not
to
say
that
we
can't
also
do
like
a
community
day
to
do
like
a
I
guess.
We
could
do
like
a
localization
sprint
as
part
of
the
community
day,
but
I
wanted
specifically
to
get
into
the
main
track
so
that
we
could
be
so
that
we
could
give
Roy
specifically
some
time
to
talk
about
localization
and
do
do
some
recruitment
for
localization
for
for
Chinese
Docs,
so
honestly,
I
plan.
My
plan
is
to
get
up
front
sort
of
provide
the
the
nice
candy
shell
on
the
on
the
talk.
G
A
Willing
to
sign
up
for
Community
Day
I
would
just
like
to
go
in
with
a
sense
of
what
specifically
we'd
like
to
do
in
the
past.
We've
had
I
know
that
we've
had
Doc's
prints
that
have
but
they've
been
kind
of
loosely
clustered
around
an
idea.
I
guess
that's
a
great
question
for
Roy
Roy.
Would
you
like
to
do
a
community
a
where,
like
we
did
last
year,
where
we
have
people
gathered
to
talk
about
the
like
mean
so
last
year
we
really
kind
of
ironed
out
the
workflow.
D
We
can
go
with
the
tween,
so
you
greased
and
aligned
to
the
20s
right
now.
It's
almost
pretty
much
annoying
depends
on
the
the
work
progress
of
networks.
We
have
this
idea
of
how
we
can
express
the
knowledge
alone.
Andy
request
a
team-
yes,
probably
if
next
time
I
can
actually
read
a
more
formal
water
flow
document
share
with
the
the
tool
pick
signal
food
team
and
review
by
the
team
that
kind
of
generalized-
and
there
can
be
more
useful,
okay,
more
feedback
today.
G
Well,
we
kind
of
worked
this
all
out
the
last
time,
so
only
if
there
was
a
in
fact,
I
was
even
thinking
the
the
30
minutes
slot,
where
we
just
talked
to
folks
on
Community
Day,
it
was
was
I
was
but
I
thinkin's
act,
but
I
just
wanted
to
kind
of
throw
that
out
there
and
see
what
you're
all
we're
thinking.
If,
if
we're
like
well,
we
kind
of
really
solved
this
afresh
time,
I'm,
totally
cool
with
that
sure
I.
A
A
D
A
D
I
I
Those
who
aren't
aware
were
I
should
say
words
at
cig
release,
they're
requiring
every
single
feature
and
I'm
coming
in
to
have
a
cup,
and
it
has
to
be
an
implementable
status.
So
that
really
helps
narrow
down
was
coming
into
release
and
it
really
gives
at
least
like
Doc's
a
good
impression
of
what
what
to
be
on
the
outlook
for
so
you're,
not
gonna
get
caught
with
a
curveball.
Hopefully
there's
a
PR
deadline
for
March.
First,
this
is
the
just
a
placeholder
PR.
I
So
a
lot
of
the
interactions
with
the
different
caps
and
the
different
enhancements
are
going
in
is
more
of
a
hey.
What's
the
current
status
you
know,
are
we
ready
to
at
least
open
up
a
placeholder
PR,
or
is
it
even
need,
Docs
in
general,
and
so
far
we've
seen
we
have
about
a
third
of
the
enhancements,
don't
need
Docs,
and
some
of
the
other
ones
are
starting
to
get
the
process
moving
forward
there
and
I'm,
hoping
by
pinging
them
early.
We
can
get
a
head
start
on
that
outstanding
items.
I
I
still
need
a
merge
master,
not
still
I
need
a
continually
a
merge
master
in
the
developer
branch.
So
it's
all
up
to
date
with
the
current
current
branch
and
that's
about
it
there.
There
is
also
the
draft
for
the
docs
handbook.
I
was
working
with
Stephan
Augustus
and
he
wanted
to
see
that
at
least
in
a
completion
form
of
a
draft
this
week,
so
I'll
have
that
submitted
and
I've
also
shared
out
the
kind
of
running
the
the
running
document,
with
the
shadows
as
well.
I
I
Yeah,
so
the
anything
in
general
will
probably
be
something
I
start
paying
folks
and
bothering
everybody
about
down
the
release
cycle.
But
the
handbook
will
be
very
soon
I
think
here,
where
we
have
at
least
a
working
draft.
I
have
a
lot
of
dues
in
there,
and
so,
let's
once
we
get
that
draft
published
basically
Stephen
wanted
a
mirja
basore,
a
merger
already
PR
for
that.
So
I'd
like
to
get
some
feedback
on
that
as
we
merge
it
in
there
in
his
future
release
team's
starting
looking
at
that
stuff.