►
From YouTube: Kubernetes SIG Docs 20190326
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 26 March 2019.
https://github.com/kubernetes/website
--
19:06:58 From Rajie : Yes!!! please sign me up....
19:09:07 From Rajie : I plan to
19:09:11 From Jim Angel : I wish! I will not be there.. :(
19:13:35 From Kubernetes Sig Docs : https://github.com/kubernetes/community/issues/3505#issuecomment-476407988
19:13:38 From qiming : I hope I can join you but I know I cannot convince the management to support the travel. It is not a problem of a beer or two.
19:34:19 From Rajie : Could you please elobrate on the grade points that are against each of the action items in the Q2 Planning doc?
19:37:23 From Rajie : Thank you!
A
A
A
1.14
docks
are
live.
Many
thanks
to
everyone
who
participated
in
the
1.14
release
Cody.
Thank
you
very
much
for
being
a
release,
shadow
and
many
things
to
do:
Jim
angel
hi,
Juliet,
many
thanks
to
Jim
angel
and
the
other
release
shadows
and
everyone
who
helped
out
with
the
one
about
14
docks.
It's
really.
This
release
went
really
smoothly
and
the
results
are
great,
so
Cody
I
know
that
you
are
working
with
Jim
to
make
the
dock
release
playbook
even
better.
So
thank
you
for
that
follow-up.
Work.
Jim!
A
A
A
There
is
a
link
in
the
agenda
to
the
draft
agenda
that
we
have
for
the
planning
meeting.
Anyone
who
has
this
link
can
leave
a
comment
so
if
there
is
something
that
you
would
like
to
talk
about
that
isn't
already
on
the
agenda,
please
feel
free
to
comment
on
the
document
so
that
we
can
add
that
to
the
agenda
for
discussion.
A
A
A
So
I
want
to.
Let
folks
know
that
we
are
getting
ready
soon
to
introduce
what
we're
calling
a
new
contributor
ambassador,
and
that
is
it's
a
role
that
we
will
be
asking
folks
if
you
are
interested
in
volunteering,
for
it
is
a
good
way
to
what
we
are.
What
we
ask
of
people
who
are
interested
in
being
new
contributor
ambassadors
is
that
you
be
the
first
people
to
greet
new
contributors
to
sync
documentation.
A
Oftentimes,
when
folks
are
new
to
kubernetes
are
new
to
documentation.
It
can
be
hard
to
figure
out
where
to
get
started
and
having
somebody
who
specializes
in
helping
new
people
get
started
is
one
way
that
I
think
we
can
serve
our
community
better
and
finding
folks
who
are
interested
in
greeting
newcomers
and
I
think
will
help
our
community
and
what
we
offer
for
that
role.
A
Is
it's
a
chance
to
receive
mentorship
and
it's
a
chance
to
work
with
the
chairs
to
make
sure
that
that
you
have
all
the
training
that
you
need
to
be
an
effective
ambassador
for
new
contributors?
So
it's
a
chance
to
serve
the
community
and
it's
a
chance
also
to
receive
some
one-on-one
mentorship
with
with
the
the
myself
jennifer
Rondo,
Jerry,
Botti
and
other
approvers.
So
it's
a
it's
also
a
chance
to
get
one-on-one
mentorship.
A
Another
idea
that
we
have
is
having
an
issue
triage,
what
we're
calling
an
issue
triage
captain,
meaning
that
so
right
now
our
issues
are
list
of
issues
in
the
website
repository
we're
not
really
paying
attention
to
it.
We
focus
our
energy
on
PRS
rather
than
issues,
and
it
would
be
nice
to
to
work
through
some
of
our
issue
backlog
and
so
having
someone
dedicated
to
to
triaging
issues
to
identifying
issues
that
would
be
good
for
first-time
contributors.
A
Finding
finding
someone
to
be
in
charge
of
the
issue
log
for
the
website.
Repo
is
something
that
we're
also
thinking
about.
So,
if
you're
interested
in
being
an
issue
triage
captain,
that's
also
an
opportunity.
So
again,
you
can
either
comment
in
chat
or
message
me
on
slack
and
happy
to
talk
more
about
that.
A
So
for
Shanghai,
currently
we
have
an
intro
and
deep
dive
session
scheduled.
Oh
wait,
no
I'm,
sorry
I
think
we
have.
We
have
a
deep
dive
session
scheduled
we
we
signed
up
for
both
for
both
at
an
introductory
session
and
a
deep
dive
session.
The
schedule
was
packed
so
we
had
to
choose
between
them
and
we
chose
to
do
a
deep
dive
session
and
I'm
pleased
to
pleased
to
say
that
Rui
will
be
there
to
help
lead
the
deep
dive.
A
So
thank
you
very
much
in
advance
for
your
help.
What
I'm
curious
about
so
last
last
November
in
Shanghai,
we
had
the
contributor
day
session,
where
we
had
like
three
hours
for
folks
to
come
and
participate
and
ask
questions.
Are
folks
interested
in
doing
that
kind
of
a
contributor
day
session
again
I.
C
Think
they
also
depends
on
the
backlog
of
our
queue
to
plan
the
transmission
schedule.
That
would
be
the
fifth
the
last
last
time
we
did
a
lot
of
configuration,
that's
really
effective
and
helpful
yeah.
My
idea
is
my
mitosis
is
if
we
have
something
that
needs
to
be
solved
in
effectively,
that's
really
half
opportunity.
D
E
F
A
A
E
A
E
A
A
A
E
E
A
Okay,
that's
good
to
know
yeah.
Let
me
let
me
follow
up
with
Dan
just
to
make
sure
that
that
will
to
see
if
there's
like
an
end
date
for
that,
so
that
like
if,
if
there
is
an
end,
whether
you
know
just
to
make
sure
that
people
register
before
that
I,
don't
I,
don't
know.
Let
me
follow
up
with
them
and
find
out
cool.
F
G
C
H
B
B
But
but
things
are
looking
good
so
far,
definitely
and
then
I
saw
teaming
also
put
the
PRS
and
for
the
generated
documentation,
so
I
plan
on
merging
those
probably
ended
day
to
day
just
to
get
those
in,
but
I
want
to
try
myself
first
before
merging
those
in,
but
those
will
be
in
before
midnight
tonight.
Central,
ok,.
A
A
A
G
But
I'm
gonna
leave
that
question
in
light.
You
know
to
those
who
are
currently
working
on
it,
but
that's
my
thought
is
that
it
could
you
know
if
you
had
engineering
resources
on
it,
we
could
get
tools
that
work
a
consistent
and
robust,
and
we
would
serve
us
over
and
over
again,
and
one
of
the
questions
we
might
want
to
ask
is:
do
we
want
to
keep
having
different
formats
for
different
kinds
of
ref
Cox?
A
A
B
A
G
Was
kind
of
the
way
it
was
at
the
very
beginning,
you
know
if
you
went
to
kubernetes
kubernetes
into
the
hack
directory.
There
were
tools
there
for
generating.
You
know
just
about
any
Docs,
any
reference
Docs
that
we
needed,
but
we've
worked
on.
You
know
taking
we've
taken
several
side
trips
off
of
those
tools.
In
some
cases,
we've
completely
looked
away
from
them
and
in
some
cases
we've
we've
added
so
that
the
output
is
prettier.
G
G
A
Do
you
may
know
you
care
about
this
stuff,
but
I
also
care
about
your
your
level
of
burnout
and
meaning
after
you
please
take
some
time
after
like
after
this
week
is
done.
Please
take
some
time
away
from
Docs.
It's
not
because
we
don't
want
you.
We
do,
but
I
want
you
to
be
happy
and
healthy
and
after
like
meeting
a
release,
you've
got
a
charge,
so
I
really.
A
Well,
we
appreciate
everything
that
it
takes
to
leader
release.
So
is
this?
Is
this
a
question
that
we
need
to
resolve
in
the
next
two
weeks,
or
can
we
put
it
down
and
like
pick
it
back
up
into
two
weeks
and
and
like
defer
at
least
long
enough
for
folks
to
get
a
rest
and
then
maybe
come
back
to
the
question.
B
B
It
does
evolve
and
really
we
need
the
momentum
to
continue
to
be
carried
forward.
You
know
more
so
than
this
being
really
answer.
I,
don't
think
it's
you
know,
I
think
there
is
a
clear
answer
here,
but
I
think
as
long
as
we're
asking
the
question
and
moving
in
floor
we'll
be
in
a
good
shape,
any
good
spot.
That's.
A
Fair
yeah
I,
just
don't
want
to
I,
don't
want
it
to
keep
languishing,
even
if
we
don't
need
to
act
on
it
immediately.
It's
good
to
at
least
have
a
sense
of
moving
it
forward.
So
two
weeks
is
April
9th.
So
I've
marked
this
down
to
revisit
this.
Revisit
the
question
of
ref
doc
generation
on
April
9th.
We
can
follow
up
on.
H
H
B
B
A
A
A
C
Sorry
yeah
we
had
a
meeting
challenger
about.
We
have
assumed.
As
you
know,
we
have
separate
the
repo
to
merge
the
tasks
last
week,
a
long
as
some
we
have
actually
two
active
contributors
involved,
but
they
have
some
kind
of
a
difficulty
to
manage
the
tasks
between
the
two
vehicles
and
nasta
weaker.
We
gather
together
and
talk
about
sorting
out
of
the
process
as
well
as
how
to
handle
the
reviews
between
different
team
members.
C
Yeah
I
think
it's
going
pretty
good
and
the
most
important
is
we
actually
like
the
two
with
this
behind,
because
1.14
guy
released
this
Monday
we're
still
working
on
two
1.12.
So
my
biggest
question
on
the
concern
is
to
my
team
is
how
we
can
work
together,
release
one
point
cowboy
as
early
as
possible,
so
the
majority
of
time
was
kind
of
spent
the
manager
task
as
well
as
how
can
we
accelerate
with
the
developer
in
the
process?
C
E
E
You
know,
like
Ray,
said
here
spending
quite
some
time
doing
some
face-to-face
and
virtual
face-to-face
communication
was
the
members
to
clarify
the
process
and
those
kind
of
issues.
I
think
we
were
still
spending
quite
some
time
on
clarifying
those
stuff
and
actually
from
my
side,
I'm
also
thinking
to
use
the
WeChat
platform,
the
one
that
we
had
to
release
some
kind
of
directions
to
face
more
audience
to,
let
them
make
sure
yeah.
They
understand
the
process
and
the
new
process
right
now,
so
we
are
still
working
on
that
yeah
together.
A
E
Think
it's
pretty
clear
to
us
right
now:
the
sameness
that,
since
we've
been
through
this
kind
of
change
in
switch,
the
problem
is
how
to
make
other
people
the
more
audience
in
a
larger
scope,
to
understand
the
change.
Why
we
change
the
history
of
the
change
and
how
they
could
participate
into
this
new
kind
of
process.
You
know
that's
the
scope
of
the
audience
and
the
kind
of
issue
of
the
surprise
thing:
yeah,
okay,.
A
Again,
thank
you
for
your
patience
with
Oliver.
All
of
our
changes,
I
think
our
localization
now
is
quite
stable
and
will
remain
so
since
the
first
of
the
year
we
have
added
three
more
localizations,
French,
Italian
and
German
and
I
think
our
process
right
now
is
stable.
It's
it's
obviously
working
better
now
and
I.
A
Just
I
want
to
express
gratitude
again,
Giulia
to
you
into
all
of
your
team,
for
for
helping
to
make
this
process
become
as
easy
as
it
is
because
it
was
not
always
this
way
as
you
as
you
well
know,
so
anything
that
we
can
do
to
to
ensure
folks
that
the
the
current
process
is
stable,
that
they
don't
have
to
be
afraid
of
any
more
big
changes.
At
least
you
know,
that's
not
in
the
foreseeable
future.
E
A
I
Importantly,
bins
for
localization
team,
it
means
star
to
114
translation,
so
we're
gonna
have
two
different
working
plants
temporarily
for
a
finishing
113
translation
and
starting
114
translation,
and
we
have
a
plan
to
we
put
our
activity
through
our
local
community.
The
deputies
prepare
will
be
prepared
to
buy
us
a
coat
okay.
That's
it.
A
A
So,
if
you
can
see
here,
we
have
grades
that
say
like
0.7
here
is
0.5
here
is
0.3.
This
is
on
a
zero
to
one
scale,
so
these
are
fractions
of
of
one.
So
it's
a
it's
a
percentage
system.
If
you
will
it's
a
an
estimate
of,
if
unfinished,
is
zero
and
completely
finished
as
one
it's
a
fractional
estimate
of
how
far
along
these
these
items
are
so
the
first.
The
first
thing
that
we
will
do
in
the
planning
meeting
is
we'll
review
the
goals
that
we
set
in
December
of
last
year.
A
A
We
have
fractional
estimates
for
how
far
along
we
are
like
the
the
content
plan
that
Steve
made
for
specific
content
in
in
December.
That's
about
70%
of
the
way
done.
So
you
see
point
seven
here,
meaning
about
70%
of
the
way
done,
then
the
the
getting
started
Docs
those
are
still
in
the
very
early
stages
of
getting
done
and
that,
but
then
down
here.