►
From YouTube: K8s SIG Docs Meeting for 20210316
Description
The Kubernetes special interest group for documentation (SIG Docs) meets weekly to discuss improving Kubernetes documentation.
For more information, please see: https://github.com/kubernetes/website
A
All
right
here
we
go
welcome
everyone
to
another
rendition
of
our
sig
docs
weekly
meeting.
My
name
is
taylor
dolezal
and
I'm
filming
for
jim,
who
has
a
very
crazy
schedule
so
very
happy
to
see
all
of
your
happy
faces.
The
this
is
a
kubernetes
meeting,
and
so
we
abide
by
the
kubernetes
code
of
conduct
which
simplifies
down
to
please
be
excellent
to
one
another.
I
make
that
same
request
of
all
of
you
and
we
shouldn't
have
too
much
of
an
issue
on
that
front.
A
A
A
A
A
They
need
to
be
published
on
april
8th
the
target
date
for
121
release
logo
and
the
associated
blurb
will
be
added
by
neverend
towards
the
end
of
the
cycle,
that
being
kind
of
like
what
the
release
the
release
mascot
is
going
to
be
so
awesome.
Great
update
on
that
front.
Divia
also
mentioned
that
eight
feature
blogs
are
tracked
so
far.
The
tracker
sheet
is
in
the
sig
is
in
our
weekly
meeting
schedule
and
in
the
agenda
that
will
be
ready
for
review
on
march
31st.
A
A
B
B
They
have
to
make
a
placeholder
pull
request,
at
least
a
placeholder
pull
request
to
the
dev
121
branch
and
k
website,
and
that
deadline
is
today.
The
good
news
is
that
every
enhancement
owner
has
either
has
notified
or
made
their
pull
requests
into
the
into
the
dev
121
branch.
We're
just
missing
three
prs
where
the
owner
said
that
they
will
create
a
pull
request
by
today
and
that's
pretty
much
it.
The
rest
is
pretty
standard.
The
integration
branch
is
healthy
and
yeah,
so
we're
in
a
good
place
so
stay.
B
As
for
docs,
I
think
there
have
been
times
where
they
we've
had
to
do
an
exception
for
one
or
two.
I
don't
think
so.
There's
not
like
a
formal
process
like
there
are
with
the
enhancements
where
you
file
for
an
exception
for
docs.
It's
it's
mostly
just
there's,
always
one
or
two.
That's
always
a
little
bit
late,
and
sometimes
one
or
two
might
will.
D
B
B
So
yes,
it's
not
it's
not
as
formal
as
the
enhancements
exception,
but
yeah
we
can
grant
exceptions
or
we
there's
also
the
ability
as
well
in
case
there
is
also
the
ability
to
be
removed
from
the
milestone
as
well
for
the
enhancements.
That's
a
a
technicality,
but
luckily
we
haven't
done
that
since
the
few
and
the
result
in
the
release
cycles,
I've
been
on
but
yeah.
E
Hand
up
tim
so
because
we're
not
part
of
the
release
in
terms
of
you
know,
none
of
the
documentation
is,
is
made
into
the
release,
artifacts
and
so
on.
We
can
slide
the
docs
in
a
little
bit
after
release,
and
so
the
sort
of
thing
that
I'd
be
willing
reluctantly
to
do
would
be
to
accept
some
incomplete
docs.
The
diagrams
are
wrong.
There's
a
factual
error,
they're,
just
not
good
enough
to
to
publish
except
we
go.
E
A
F
B
Day
before
april,
8th
and
should
thaw
the
day
of
I'll
have
to
go
back
to
the
timeline
just
to
verify.
But
I
believe
let
me
go
check
the
uproll
handbook.
I
believe
it's
the
day
before
we
freeze
and
then
the
day
of
I'll
talk
to
the
sig
to
the
sigdoc's
chairs,
about
thawing
and
there's
some
process
involved,
as
well
with
the
merge
of
the
dev
120
branch
and
the
master
branch
on
the
day
of.
A
D
A
G
No
it's
a
week
after
codes
for
you,
sorry
so
before
in
the
last
release,
it
was
week
before
code
freeze.
So
there
is
a
difference
between
the
deadline
between
last
release
and
this
release,
and
I
think
I
don't
know
if
you
remember,
but
last
release
the
day
of
the
placeholder
deadline.
There
was
we
started
off
with
like
a
huge
number
of
like
prs
that
wasn't
open
and
we
track
them
like
throughout
the
night
throughout
the
day,
and
we
have
to
ping
so
many
people
to
get
those
placeholder.
G
B
I
think
there
was
less
pressure
this
release,
because
the
deadline
was
after
code
freeze
and
like
in
the
in
the
in
the
morning.
We
had
four
that
had
not
replied
and
so
versus
last
release
was
quite
a
bit
more
than
four.
So
within
with
you
know,
before
10
a.m.
Pacific
time
all
four
already
replied:
if
they
do
or
do
not
need
docs,
so
it
wasn't
so
it
was
it
was
it
wasn't.
B
I
guess
it
was
just
easier
with
it
with
the
dog
placeholder
deadline
after
code
freeze,
because
enhancement
owners
do
do
get
busy
with
trying
to
get
make
sure
their
enhancements
is
being
tracked
for
121,
whether
it's
code
related
issues
or
kept
related
things
that
they
have
to
do
yeah.
So
it
was
a
little
bit
easier.
D
B
I
do
want
to
make
a
note
on
the
on
the
docs
role
handbook.
I
believe
it
actually
does
say
that
the
doc's
placeholder
pr
deadline
is
after
code
freeze,
usually,
but
I
think
in
120
we
had
like
thanksgiving
holiday
and
we
had
keep
con
and
we
had
a
so.
We
had
those
hurdles
that
might
have
played
into
with
the
schedule.
F
A
A
A
All
right,
wonderful,
and
with
that,
I
guess
we
can
give
you
some
time
back.
If
you
have
any
questions
this
week
or
in
the
upcoming
weeks,
feel
free
to
raise
them
up
in
the
sig
doc's
slack
channel,
I'm
going
to
go
ahead
and
handle
this.
This
recording
of
this
meeting
we'll
get
that
up
on
youtube
and
make
sure
everything's
good
on
that
front
and
as
always
such
a
pleasure
to
work
with
all
of
you
and
hope
you
have
a
wonderful
rest,
your
tuesday
have
a
going
everybody
so
good
to
see
everyone
bye.
Thank
you.