►
From YouTube: K8S SIG Docs Meeting for 20220215
Description
For more info see https://git.k8s.io/community/sig-docs
A
Out,
okay,
folks,
this
is
the
sigdox
blog
meeting.
We
are
following
the
kubernetes
code
of
conduct
and
the
general
Community
theme,
so
please
be
nice
to
everyone
and
we're
recording
this
meeting
hello.
Let's
talk
about
the
blog
hello.
A
The
agenda
is
in
is
in
the
the
meeting
chat.
A
Are
you
sharing
it
Nate
yeah
I
will
referee.
B
B
Dr
Shim
related
discussions.
I
think
that
we've
got
krakowthrove
is
suggesting
March
18th
deadline
for
PR
30917.
B
B
I
think
that's
a
fine
date,
but
I
wanted
to
bring
it
up
here
just
in
case
there
is
something
along
something
around
if
there's
something
else
scheduled
for
that
time,
slot
that
I
didn't
want
to
I
didn't
want
to
get
I
didn't
want
to
push
that
out
of
the
way
and
she's
also
suggesting
a
31st
deadline
for
309
1
8.
B
to
be
ready,
and
that's
the
that's
the
history.
That's
the.
B
The
docker
sham
removal
story,
blog
entry
and
I
thought
that
that
one
was
going
to
be
released
a
day
of
I
thought
that
was
going
to
be
on
April
19th
release,
but
I'm
not
again
I
don't
have
a
problem
with
it
being
pushed
up.
If
that's
what
the
community
wants
to
to
do,.
C
C
Two
weeks
or
so
we
have
release
release
related
blogs.
A
These
two
that
we've
got
up
here-
these
are
both
going
to
come
out
before
the
release
right.
B
Well,
that's
the
question
here:
the
history,
the
Dr
Sherman
released
I
thought
that
one
was
going
to
be
a
release
day.
B
Blog
post
I
think
that
in
in
this
case,
while
traditionally,
we
only
have
the
one
I'm
wondering
if,
if
this
release
would
if
it
would
serve
us
well
to
have
the
traditional
release
day,
blog
entry
and
the
Docker
shim
removal
entry
come
out
the
same
day.
On
the
same.
A
What
we've
done
before
I
like
the
idea
of
keeping
the
release
day
for
what
like
there's
one
blog?
You
know
you
you're
expecting
one
article
on
that
day
and
that's
the
one
because
there's
a
bunch
of
people
who
will
watch
our
blog
that
day
and
don't
care
about
anything
else
and
let's
serve
that
audience.
However,
we
have
done
articles
that
come
out
a
day
or
two
before
the
release.
A
A
Did
you
see
the
new
thing
and
we
have
those
come
out
and
that's
great,
but
we
can
have
one
that
comes
out
like
a
day
before
or
two
days
before,
saying,
there's
a
release
coming
it's
coming
tomorrow
and
here's
the
thing
and
I
think
that
the
history
with
kubernetes
one
would
be
day
before
the
release.
C
C
With
this
having
it
way
before
the
release,
even
to
me
the
the
more
how
we
front
end
the
more
we
prepare
a
folks
with
additional
blog
entries
for
me
and
that's
better
but
I
know
people
tend
to
watch
the
cuminess
of
that
I
O
blog
when
we
post
the
release
so
might
get
more
eyes,
but
I'm
thinking
way
before,
just
because
we
could
have
a
whole
campaign
around
it,
we
could
tweet
about
it
and
it
could
be
other
people
other
folks.
We
were
retweeting
about
it.
C
Now,
it's
not
a
I
mean
it's
not.
It
should
not
be
a
surprise
by
now,
the
more
the
more
things
we
publish,
the
the
less
of
a
surprise
will
be
for
folks
I'm
sure
there
will
be
folks
that
will
be
surprised
by
this,
though.
C
A
To
make
people's
lives
easier,
we
might
want
to
put
some
attributable
quotes.
So,
for
example,
if
Maha
and
Nate
are
the
authors,
you'd
have
a
particular
quote.
Saying
mate
says
this
and
and
Meha
says
that
because
people
will
want
to
do
that
and
they
won't
want
to
get
attributions
or
whatever
they'll
just
want
to
have
a
copy
and
paste.
But
you
know,
if
you're
a
journalist,
you
don't
want
to
spend
a
long
time.
A
Putting
this
you
just
I'm
going
to
quote
Nate
and
the
quicker
the
less
effort
you
can
do
and
the
more
mechanical
you
can
make
that
kind
of
article.
The
better
and,
of
course
there
are
other
art
journalists
who
will
be
like
reaching
out
and
trying
to
get
people
to
do
an
actual
call
or
an
interview
or
whatever,
and
that's
that's
fine
too.
We
need
to
serve
both
those
constituencies,
I
think
so.
I
think
I
mean
if
we've
got
one
by
I.
A
Think
you
know
if
cat's
going
to
be
an
author
on
on
that,
we
can't
I
think
can
be
fine.
Like
one
author,
you
can
quote
one
author.
It's
great
this
this
one
with
Dr,
Sherman
Docker
engine
history,
I
think
we
should
aim
to
put
quotes
in
there,
bearing
in
mind
what
you've
just
said,
it
makes
me
think
it's
important.
B
A
B
B
Can
even
draft
the
copy
link.
A
B
Pictures
are
always
great.
Is
there.
B
B
A
Actually
think
a
diagram
is
probably
worth
having,
for
example,
showing
that
Docker
engine
run
has
containerdy
inside.
It
is
going
to
be
massively
reassuring
people.
What's
this
contentity,
oh
okay,
it's
the
thing
that
Docker
engine
uses.
A
Yeah,
so
if
the
story
is
that
essentially
there's
two
middle
layers
and
we're
removing
them-
and
now
you
know,
instead
of
there
being
a
Docker
shim
and
Docker
and
Humanity
we're
talking
directly
to
the
organ
grinder.
Well,
that's,
that's.
A
diagram
can
show
that
and
I
hope
yeah
I
mean,
but.
B
Do
we
have
do
we
have
go-to
folks
that
can
do
those
types
of
diagrams
or
people
we
need
to
bring
the
cncf
in
for
some
design
capacity.
A
Well,
do
we
want
this
to
be
no
like
we
can
use
mermaid?
Do
we
want
this
to
be
a
technical
diet,
looking
diagram
or
or.
A
Because
if
it's
a,
if
it's
a
technical
diagram,
I
can
do
it
in
mermaid
and
we
can
find
Sig
dogs
folk
to
do
it
in
mermaid.
If
it's,
if
we
want
something
looking
designed,
we
might
want
to
call
on
different
resources.
B
A
Okay
and
to
move
on
to
the
next
one,
do
we
want
a
diagram
for
the
the
history
one,
and
do
we
want?
Oh
sorry,
do
we
want
an
illustration
for
that
one,
and
maybe
do
we
want
to
design
the
illustration
there.
B
I
would
love
a
designed
illustration
for
that.
One,
like
I,
think
that
one's
I
think
that
one
lends
itself
more
to
to
that,
but
I'm
not
sure
again
what
it
would
be.
A
A
Be
blue
if
it's
not
blue,
it's
wrong!
No
I
would
like
I
would
hope
that
we
do
not
do
that,
because
it's
shouldn't
have
said
that
I'm
sorry.
B
Design
a
design
illustration
there
I
think
would
again,
because
this
is
probably
going
to
be
one
of
our
most
viewed
blog
articles
for
a
while.
It's
probably
it
will
help
to
to
give
an
appearance,
a
professionalism.
A
Yeah,
okay,
I'm
gonna
close
off
the
resolved
thing
about
whether
the
project
board
is
automated
because
it
isn't
do
we
want
to
move
on
and
talk
about
the
signal
test,
improvements.
C
Not
much
I'll
just
we're
just
on
the
project
board.
I
just
put
the
two
blog
PR's
that
are
on
the
project
board
up
there,
just
just
for
yeah.
This
is
just
one
two:
okay,
Dev
and
like
likely
to
be
married
to
kimes.io.
A
Okay,
so
that
yeah,
that
that
issues
I'm
not
sure
what
the
issues
are
I'd
kind
of
prefer
this
to
be
piano
guys,
but
we
don't
have
draft
PRS.
Maybe
we
should
ask
for
draft
pianos
a
bit
like
we
do
for
releases.
A
B
We
had
some
PRS
in
progress.
Let
me
do
we
know
it.
B
Pr
in
flight,
for
that
hits
the
blog
right
now
and
that's
the
highly
discussion
issue
for
Docker
shift
deprecation,
and
that
looks
like
it's
more
of
a
fix
than
just
a
Blog.
So
this
is
not
a
blog
entry,
so
yeah
I
think
opening
opening
yeah
getting
a
a
request
for
a
placeholder
PR
is
probably
worthwhile
at
this
point.
B
A
A
Can
I
make?
Are
you
happy
Nate
to
take
that
as
an
action
to
to
to
I
would
say
chiffy
up
authors
and
and
get
them
to
commit?
As
far
as
opening
a
draft
PR
yep
I
can
do
that
cracking.
A
And
this
is
one
where
you
know
if
we
could
get
a
quote
from
someone
who
had
an
early
involvement
in
in
in
Docker
and
and
in
adapting
Docker
for
kubernetes,
there's
a
bunch
of
names
that
I
can
think
of
I'm
happy
to
do
some
reaching
out
there.
B
B
Yeah
and
that
that
would
be
good,
I
completely
agree.
I
was
also
thinking
that
there
was
a
little
bit
of
confusion
about
the
historical
blog
post
and
because
this
is
recorded
and
not
public
information,
I'm
going
to
say
the
thing
but
I'm
not
going
to
say
the
name.
B
So
we
were
going
to
invite
somebody
from
the
the
the
the
history
of
of
the
project
to
write
a
blog
post
for
us
on
this
documentary,
and
removal
and
I'd
still
like
to
do
that.
But
there
was
some
confusion
on
I
think
it
was
30918
about
what
that
blog
entry
was
going
to
be
and
whether
or
not
somebody
from
the
cncf
was
going
to
sort
of
reach
out.
So
I
would
like
to
clarify
with
those
folks,
because
I
think
that
speaks
to
what
you
were
just
talking
about
is
there.
B
There
are
some
some
people
that
I
think
are
interested
potentially
in
writing
a
even
an
individual
blog
post
for
us
for
this,
so
I
will
see
what
I
can
do
about
clarifying
that
and
seeing,
if
there's
any
way
to
anyway,
to
move
that
forward
and
I
hope.
I
wasn't
too
vague
in.
In
my
description
so.
A
A
We
need
authors
for
the
history
of
dokashem
to
write
the
spiel.
We
would
like
people
to
provide
poll
quotes
or
quotable
material
as
an
aside.
A
Whatever
people
who,
for
whom
you
know
most
of
their
experience,
was
explaining
what
these
c
groups
and
namespaces
were
anything
like
that.
Any
companion
articles
like
we
can
line
up
any
number
of
those
on
the
contributor,
blog
and
I'm
I'm
sure
it
wouldn't
be
at
all
challenging
to
get
those
like
through
the
necessary
things
and
to
go
out
on
the
right
day.
A
And
I
you
know
and
I
would
personally
think
that
would
be
better.
That
would
add
some
add
to
it
to
say
you
know
this
is
someone's
perspective.
This
is
someone
else's
perspective
right
it
get.
It
helps
get
our
our
story
in
the
media
in
a
I
guess
a
neutral
way,
but
you
know
I'm
good
with
neutral,
because
I
don't
want
I,
don't
want
negative.
B
A
Yeah
kubernetes
dot,
Dev,
slash
blog,
that
is
the
contributor
blog
yeah,
and
we've
got
a
bunch
of
options
there.
We've
never
had.
You
know
like
two
blog
articles
go
live
there,
the
same
day
as
a
companion,
but
we've
also
never
removed
dockershim
from
kubernetes
right.
B
B
I'm
not
going
to
I
think
that's
a
great
idea
and
I've
noted
it
here,
but
I'm
not
going
to
I'm.
Not
and
I
may
well
be
happy
to
to
to
take
that
at
a
later
point.
But
at
this
point
I'm
not
going
to
take
that
as
an
action
item.
Absolutely.
A
Are
we
happy
to
move
on
a
bit
and
talk
about
the
the
contributor
site
article
that
is
up.
B
A
So
I
will
I
will
bring
up
a
screen
share
on
that.
Actually
I'll
screen
share
the
preview,
because
why
not
there
you
go
I,
don't
know
it's
not
previewing.
Oh.
C
A
A
B
This
has
to
go
out
tomorrow.
Then
I'll
do
that
this
afternoon,
just
to
make
sure
that
we've
got
all
our
commas
in
place.
I.
A
Wouldn't
say
it
has
to
go
out,
but
it's
much
easier
to
avoid
fiddling
around
with
the
dates.
If
we
can
do
that,
yeah
you'll
also
need
to
nudge.
The
sync
contributor
experience
folks
to
approve
this
because
doesn't
run
this
blog.
B
B
A
B
A
To
be
honest,
if
that
was
all
that
was
missing,
I
would
use
my
commit
approver
technical,
lead
access
and
go
and
add
it
and
merge
it
because
it's
already
been
reviewed,
so
the
important
Key
Stage
I
think
is
getting
it
past
the
contributor
and
say
contracts,
people
get
that
lgtm
and
approval,
and
then
once
that's
done
everything
else,
it's
kind
of
mechanical.
We
don't
need
to
reapprove
this
just
for
mirroring
it's
like
it's
fine,
yeah.
A
So
I
mean
this
really,
you
know
like
officially
lives
with
sick
contracts,
but
I'm
I'm
sure
we're
very
happy
to
help,
because
it's
all
kubernetes.
B
B
Is
there
an
automated
way
of,
or
is
a
Sergey
just
like
copying
and
pasting
all
the
edits
from
one
to
the
other
end?
If
that's
the
Verge,
that
could
be
an
ugly
marriage.
A
I
mean
it's
two
different
git
repositories,
I
think
copy
and
paste,
or
you
know,
CP
or
something
are
about
as
clever
as
it
gets.
But.
A
Foreign
I
said
also
that
I
would
have
a
look
at
the
calendar
and
I
haven't
done
that
yet.
But
it's
on
my
list.
A
Because
I
said
I'd,
do
it
I,
don't
I,
think
I
mean
Ray.
You
could
do
it
as
well,
but
I
said
I'd
have
a
look
into
it.
Foreign.
C
B
I
think
then
I
think
that
probably
is
it
for
for
things.
I
want
to
bring
up
for
this
particular
meeting.
B
I
think
that
was
everything
from
my
end
to
what
I
wanted
to
bring
up.