►
From YouTube: SIG Docs meeting for 20211019
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
righty
and
we
should
be
going
recording
so
again
thanks
everyone
and
welcome
to
the
seed
docs
bi-weekly,
the
edition
after
kubecon,
where
a
lot
of
folks
are
probably
feeling
really
great
and
really
inspired
after
a
really
awesome
event
that
was
attended
by
some
folks
here
in
person
on
the
call
and
a
bunch
of
us
virtually
as
well
so
really
great
to
welcome
autistic
docs.
I
do
want
to
just
start
off
by
saying
thanks
for
joining
us.
A
I'm
natalie,
as
I
mentioned,
and
I'm
hosting
today,
taking
over
some
of
the
duties
of
divya
and
jim
who've,
been
graciously
helping
out
with
a
lot
of
new
contributors
and
a
lot
of
new
folks
like
myself,
getting
involved
in
sick
docs,
which
is
which
is
really
great.
A
I
do
want
to
just
quickly
post
the
agenda
here
in
the
chat,
just
in
case
folks
haven't
got
it
at
their
fingertips
and
if
anyone
wants
to
add
anything
as
we
go
into
that
it's
there
in
the
chat
for
everyone
to
access,
but
we're
going
to
quickly
get
started
now
with
what's
on
the
agenda
here,
and
the
first
thing
I
would
love
to
shout
out
is
to
see
if
there
is
a
any
new
contributors
that
want
to
say
hello
and
introduce
themselves
on
the
call
today.
A
C
B
A
D
Introduce
themselves,
I'm
I'm
whitney
nice
to
meet
you
when
he
said
new
contributors.
I
was
wait.
I
didn't
introduce
myself
because
I'm
not
a
contributor
yet
so,
but
I
look
to
be
soon.
I
met
chris
at
kubecon,
I
went
to
the
sick,
ducks
meet
and
greet,
and
I'm
looking
forward
to
helping
out
around
here.
A
That's
really
awesome.
Whitney
welcome,
definitely
would
be.
Contributors
also
welcome.
I
think
anyone
that
wants
to
be
part
of
the
community
can
definitely
shout
out
and
say
hi,
so
it's
really
really
great
to
to
have
you
here
on
board.
That's
really
great,
and
then
we've
got
atharva
here
in
the
chat
too.
Your
first
meeting
in
seek
docs
great
to
great
to
have
you
here,
thanks
for
thanks
for
saying,
hi
and
then
calling
that
out
really
awesome
to
have
so
many
new
folks
saying
hi
on
the
call
really
really
awesome.
Hi.
E
E
And
as
a
student,
I
feel
it's
good
to
contribute
to
the
community,
so
I'm
very
excited
to
join
sigdocs
and
hopefully
I'll
start
contributing
so.
A
Awesome
just
going
to
give
for
anyone
new
who
else
wants
to
introduce
themselves
another
minute
or
two
to
say:
hi.
G
Hello,
hello,
can
you
hear
me?
Yes,
hello,
okay,
I'm
part
of
I
was
part
of
the
spanish
subgroup
and
I'm
just
here
as
a
listener,
and
if
we
are
lucky
I
will
be
contributing
again
in
spanish,
but
I'm
not
sure
I
just
want
to
know
what
you're
doing
and
that's
all.
A
G
A
Awesome
nice
to
meet
you
too
welcome
and
thanks
so
much
yeah,
we're
great
to
have
great
to
have
anyone
from
the
localizations
on
awesome
that
you
want
to
take
part
and
see
what's
taking
place,
awesome
really
to
have
you
with
us
and
really
great
work
on
the
localization
front.
It's
so
it's
it's
great
efforts
that
you
that
you're
putting
in
so
that's
awesome,
yeah.
G
Ryan,
garcia
was
part
of
the
spanish
localization,
I'm
not
sure
if
he
still
as
a
leader
of
the
spanish,
that
I'm
gonna
talk
with
them
and
and
participate
in
that
group.
That's
okay,.
A
Awesome
that
would
be,
I
think,
that
would
be
really
great
and
yeah.
You
can
definitely
feel
free
to
reach
out
to
them
in
the
in
the
in
the
localization
chat
there
or
just
over
on
channel
two
totally
fine
to
reach
out
there
as
well.
A
Thank
you
awesome
and
then
also
with
the
chat.
We've
got
a
couple
of
hellos
there,
hello,
ko,
hey,
ota,
hi,
welcome
really
great
to
have
so
many
new
contributors
on
wow.
This
is
awesome.
I
would
turn
this
into
just
a
new
contributor
meeting
the
whole
time.
This
is
great
hello.
Everyone
welcome
welcome.
Firstly,
I
also
just
want
a
quick
shout
out
to
ray
thanks
for
taking
notes.
A
I
was
going
to
start,
but
I
saw
you
typing
there,
so
thanks
ray
for
being
our
scribe
today,
I
really
appreciate
it
and
I
haven't
seen
him
jump
on
the
call
yet,
but
one
of
the
other
things
I
wanted
to
do
as
a
kind
of
the
opening
of
the
of
the
meeting
here
after
kubecon.
A
I
want
to
give
a
big
shout
out
to
our
tech
lead
tim
tim
bannister,
who
was
noted
as
a
top
documentarian
for
2021
for
over
at
kubecon
big,
congratulations
to
him
really
hope
he
was
here
to
say
to
say
hi
and
it
would
be
really
really
great
to
for.
Anyone
who
wants
to
you
know,
say:
congratulations
jump
into
stick
docs
and
tell
him
that
he's
so
great.
A
I
think
that's
an
awesome
achievement
and
a
really
awesome
recognition
for
our
little
sig
over
at
kubecon
as
well
all
right,
and
so
with
that,
with
that
with
the
contribution
welcomes,
there
done,
wanted
to
kind
of
jump
in
and
just
quickly
remind
folks
about
pr
wrangling.
Interestingly,
this
week
and
next
week
we
don't
seem
to
have
anyone
on
the
agenda
or
on
the
list
for
doing
pi
wrangling
for
those
who
are
new
here.
A
In
terms
of
signing
clas
and
understanding,
you
know
some
of
the
feedback
they're
receiving,
and
so
if
I've
got
any
approvers
on
the
call
that
want
to
put
their
hand
up
to
do
any
pr
wrangling
this
week
or
next
week
feel
free
to
jump
into
the
agenda
and
add
your
name,
but
we
will
be
collectively
as
a
as
a
as
a
community
helping
out
with
their
prs
in
terms
of
them
getting
them
moving
through
through
the
kind
of
through
the
workflow
over
the
next
couple
of
weeks.
A
Anyhow,
so
approve
is
out
there
if
you're
on
the
call
remember
to
check
your
shifts,
there
will
be
information
listed
there,
also
in
the
agenda
and
going
moving
on
to
some
of
the
next
topics.
We've
got
some
information.
I
know
ray
you've
put
this
in
on
release.
One
two:
three:
would
you
mind
giving
a
quick
update
here.
H
Yeah
I'm
actually
going
to
defer
if
any
of
the
release
docs
team
members
would
like
to
give
an
update.
If
not,
I
can.
C
Sure
we
have
only
a
couple
or
some
draft
put
requests
open.
We
have
seven
out
of
forty,
so
maybe
we
think-
or
we
are
a
little
bit
worried-
that
there
are
a
few
pull
requests
opened
due
to
the
deadline
on
november
18th.
But
as
jesse
told
us,
you
may
be
send
an
email
to
the
email
list
in
order
to
speed
up
these
pull
requests,
or
this
draft
pull
request.
H
Yeah,
I
will
send
out
an
email
on
thursday
to
the
kubernetes
community
to
remind
folks
a
number
of
milestones
coming
up,
because
all
the
milestones
around
major
u.s
holidays,
major
december
holidays
as
well
123,
is
scheduled
to
be
released
on
december
7th.
So
we
have
some
major
milestones
around
a
mid
mid
november.
H
I
did
see
some
additional
prs
open
draft
pr
is
open
over
the
past
day
or
two,
so
I
think
we
do
have
more
than
seven
draft
pr's
open,
yes,
so,
but
about
so
that
leaves
about
over
on
that
30ish
enhancement
still
need
placeholder
pr,
so
which
is
quite
a
bit,
and
we
have
about
three
weeks
until
the
docs
placeholder
pr
deadline
and
for
those
who
are
new
part
of
the
release
cycle
when
the
first
milestones
for
for
docs
is
after
they
opt
in
to
have
their
enhancements
part
of
a
release.
H
If
they
need
documentation
for
their
release,
they
we
do
have
a
milestone
for
enhancements
to
open
a
placeholder
pr.
This
is
just
a
draft
pr
it
just
it
doesn't
have
to
be
complete
at
all.
It's
just
to
give
us
what
sense
of
velocity
and
the
number
of
prs
we
need
to
review
for
sig
docs
for
the
for
the
release
so
because
the
milestones
are
pretty
close
together
towards
the
another
release
and
feel
free
to
ask
any
questions
or
have
any
comments
for
me
or
for
the
release
stocks
team
as
well.
D
H
So
milestones
are
pretty
much
deadlines,
so
we
have
like
code
freeze
coming
up
november
16th,
two
days
after
code
freeze,
we
have
the
docs
placeholder
pr
deadline,
so
that's
for
more
sig
docs
for
for
for
sig
docs
to
see,
and
after
that
is
once
documentation
is
complete.
The
docs
should
be
ready
to
be
reviewed,
which
is
reviewed
by
the
release,
docs
team
and
also
sig
docs
reviewers,
as
well
that
I
forgot
what
date
that
is.
I.
D
H
The
code
okay,
so
the
goal
is
that
is
to
have
what
the
the
code
goes
into
into
the
kubernetes
kubernetes
repository
and
that's
just
all.
Code
related
changes
for
that's
targeted
to
123.,
along
with
those
code,
related
changes,
and,
let's
say
like
dual
stack:
ipv4
ipv6
is
is
an
is
a
feature:
that's
going
to
be
stable.
H
There
should
be
documentation
to
to
reflect
that.
It
could
be
either
updating
the
feature
gates,
page
or
just
documentation,
stating
that
oh,
it's
going.
It
is
stable
in
123
or
any
other
new
features
that
go
into
alpha
beta
as
well
or
any
changes
so
there's
the
documentation,
changes
that
need
to
be
part
of
the
release.
A
Yeah,
thanks
for
your
question,
whitney
as
well
and
any
I
want
to
just
save
some
space
for
anyone
else
with
any
other
questions
around
the
123
update
on
docs.
A
Alrighty
so
we'll
move
on
to
the
next
agenda
item-
and
I
do
note
that
this
was
popped
in
by
tim,
who
doesn't
look
like
he's
on
the
call
at
the
moment,
but
perhaps
there
is
someone
on
the
call
that
will
be
able
to
speak
to
this.
This
is
a
pr
that
he
brought
up,
or
should
I
say,
an
issue
that
was
reported
by
a
contributor
as
a
possible
bug
reporter,
not
necessarily
a
design
behavior.
A
Then
he
put
he's
popped
this
on
here
for
the
next
meeting
of
sea
dogs,
but
he's
not
here
to
speak
to
it.
Does
anyone
else
have
any
background
or
info
on
said
pr
in
the
agenda
that
they'd
like
to
speak
to
right.
H
Yes,
so
I
just
took
a
look
at
this
issue.
This
is
a
an
issue.
It
looks
like
he
has
a
pr
to
fix
this
issue.
I
haven't
checked
yet,
but
this
is
in
the
comment:
when
you
go
to
the
documentation
page
and
on
the
left
side,
you
get
the
navigation
menu
and
if
it's
three
levels
deep,
the
second
level
items
below
the
active
parent
doesn't
show
their
children.
A
Yeah,
I
believe
tim's
original
question
was
around
whether
this
was
intended
behavior
or
not,
and
it's
you
know
seen
likely
as
not
and
something
to
be
discussed.
But
I
guess
that's
the
discussion
to
take
place
if
we
think
that's
intended
or
if
it
is
something
that
is
a
is
a
bug
that
should
be
fixed.
C
A
All
right,
sorry,
just
taking
some
notes,
I'm
on
a
single
monitor
here
from
my
couch
but
great
yes,
I
so
you
sort
of
just
make
sure
you
were
experiencing
this
also
specifically
on
the
english
side
or
other
localizations.
C
A
Great
I'll
note
that
here
as
well,
anyone
else
with
comments
here.
G
Sorry,
I'm
not
sure
if
you're
talking
about
the
same
thing,
but
I
remember
that
there
is
a
subcategories.
I
mean
you,
you
open
that
second
index
or
second
level
nested
level
and
there
is
there,
are
like
heaters
and
then
you
go
to
the
location.
Maybe
we
are
not
talking
about
that.
That's
what
came
to
my
mind.
A
Yeah,
I
think
this
is
definitely
in
the
main,
like
the
top
top
level
navigation
on
the
left,
specifically
here
that
that
this
that
this
seeming
bug
is
is
is
coming
up
into.
But
it
looks
like
it's
regardless
of
intent.
It
looks
like
it's
not
actually
coming
across
the
same
way
for
all
different
users.
So
definitely
something
I
think,
needs
to
kind
of
come
in
in
terms
of
maybe
a
pr
to
to
bring
in
a
fix
here.
A
All
right
we're
going
to
jump
to
the
next
topic
then,
and
we're
moving
into
the
discussion
area
here
and
ray.
I've
noted
that
you've
got
the
new
reflect
refactor
label
listed
here.
I'll
defer
to
you.
H
All
right,
sorry
about
that,
just
getting
off
meets
so
on
a
github.
I
think
issuer
discussion
when
we
talked
about
adding
a
new,
so
there's
been
pull.
Requests
that
have
come
in.
That's
just
give
some
background.
That's
change,
that's
removed
and
deleted
files
and
move
content
from
one
page
to
another
page,
but
localization
teams
have
issues
following
those
pull
requests
because
they're
not
notified.
H
So
on
a
github
discussion
or
an
issue
I
forgot,
which
one
it
was
we
decided
and
also
on
this
sig
docs
meeting
as
well.
We
decided
to
have
to
add
a
new
label,
a
label
on
get
on
our
local
github
to
kubernetes
website
repo.
So
again,
so
there's
a
new
label.
That's
almost
ready!
It's
it's!
A
it's
labeled
title
as
refactor,
and
this
refactor
label
indicates
any
large
refactoring
changes,
so
files
being
removed,
content
moving
from
one
site
to
another
site.
H
So
that's
almost
finished.
I
have
one
more
pull
request
to
make
to
the
label
is
there,
but
I
have
to
make
one
more
update
so
that
we
can
use
the
label.
So
that's
I'm
about
to
finish
it
up
in
the
next
half
an
hour
after
this
call
is,
is
done.
There's
also
a
contributor
named
avinesh
named
evanesh
tripathi
avinash
is
looking
into
how
to
automate
notifying
localization,
reviewers
and
or
other
sig
docs
reviewers
on
when
there
is
a
pull
request
with
the
refactor
label
as
well.
H
So
we
know
that
that
if
there
are
some
big
changes
that
all
the
localization
reviewers
are
or
owners
are
notified
as
well,
so
they
can
make
those
subsequent
changes
in
their
localizations
as
well.
A
A
small
question
on
mayan
ray:
do
you
need
any
new
contributors
to
help
out,
or
is
there
a
great
place
that
folks
can
get
started
to
help
out
here.
H
Yeah
just
doing
some
just
probably
just
some
testing,
I
have
a
work
in
progress,
draft
pull
request
just
to
make
sure
it
works.
But
after
I
make
this
one
pull
request,
which
I
will
post
on
the
sigdoc
slack
channel
when
it
is
up
and
merge,
then
we
can
test
it
out.
I
know
we,
I
know
we're
looking
at
into
adding
the
refactor
label
to
us
to
a
few
previous
pull
requests
that
have
merged
already,
so
we
can
add
that
label
and
and
make
and
see.
A
Awesome
thanks
so
much
for
the
update
any
last
requests
for
questions
on
that.
A
All
right,
then,
we'll
move
on
to
the
next
item,
and
I
know
chris
chris
metz
on
the
call
you
I
wanted
to
give
a
brief
update
around
diagrams
in
mermaid
love
to
hand
over
the
virtual
mic
to
you.
I
Okay,
good
terrific,
thank
you
natalie.
So
a
couple
of
things.
First
of
all,
I
attended
coupon
last
week,
first
one
and
I
think
two
or
three
years,
but
it
was
great
meeting
everybody,
jim
and
brad
nate.
I
know
we
chatted
a
bit
ray,
so
it's
just
a
great
community
and
I'm
very
grateful
to
be
part
of
it
and
I
feel
more
empowered
than
ever
as
a
contributor
for
sig
docs,
okay.
I
Secondly,
I'm
gonna
jump
on
my
diagram
soapbox
for
a
moment,
so
I
think
one
of
our
jobs
really
is
to
make
this
documentation
as
interesting,
accessible
and
friendly,
in
particular
to
new
contributors
or
folks
who
haven't
really
worked
or
even
understand
what
kubernetes
is.
So.
I
I
think
the
notion
or
the
use
of
diagrams
can
be
a
a
great
addition
to
what
we're
trying
to
accomplish
I'll,
be
honest
right,
there's
a
dearth
of
diagrams
within
the
documentation.
I
So
I
think
either
you
know
existing
contributors
or
new
contributors
think
about
even
just
a
simple
block
diagram
and
some
arrows
and
labels
would
go
a
long
way
towards
simplifying
things
for
for
new
contributors
or
new
users
or
folks
looking
at
kubernetes
for
the
first
time.
Some
of
these
concepts
can
be
pretty
difficult.
So,
like
I
say,
just
a
simple
diagram
would
be
would
be
great.
I
Fortunately,
within
docs
the
dots
we
do
have
a
package
mermaid,
it's
a
simple
way
to
craft
up
very
simple
diagrams,
using
markdown
like
syntax
syntax.
Within
the
document
itself
right,
you
don't
have
to
go
somewhere
and
hack
up
an
svg
and
then
bring
it
back
in
copy
it
to
images,
link
it
into
the
docs.
You
can
put
it
right
then,
and
there
others
can
collaborate
on
these
diagrams.
They
can
make
changes.
There's
an
offline
live
editor
where
you
can
see
how
it
works.
I
You
can
generate
a
rest
api
for
the
document
and
fling
it
around
the
contributors.
So
so
again,
it's
it's
really
easy.
It's
all
working,
some
of
the
new
diagrams
are,
in
the
you
know
the
new
contributor
or
the
contributor
documentation,
but
existing
or
any
new
contributors.
Please
please,
please
just
think
about
a
little
diagram.
You
may
think
it's
like
you
know
this
is
you
know
everybody
gets
this.
Why
not,
but
some
people
may
not
get
it,
and
some
people
may
need
just
that
way
of
okay.
Now
I
get
a
little
bit
of
this.
I
Let
me
delve
into
the
into
the
documentation.
I
Last
item
is,
I
saw
a
talk
by
kim
sleschenzer
schlesinger
from
digital
ocean
last
week
called
beyond
block
diagrams
different
ways
of
visualizing
kubernetes
architecture,
and
one
of
the
interesting
ones
that
she
brought
up
was
the
idea
of
a
sequence
diagram,
and
so
I
I
took
what
she
had
in
her
presentation.
By
the
way,
I
would
encourage
everybody
to
take
a
look
at
that
presentation.
I
I
took
what
she
had
and
and
used
mermaid
to
craft
up
a
simple
block
diagram
and
to
me
it
sort
of
made
sense,
and
you
know
I'd
look
to
folks,
like
even
you
know,
whitney
who's
done.
Some
outstanding
work
on
you
know
explaining
and
visualizing
kubernetes
and
and
how
we
may
be
able
to
incorporate
that
into
the
documentation.
So
again,
it's
not
a
lot
of
effort.
You
don't
have
to
be,
like
you
know,
a
powerpoint
or
diagrams
or
sketch
whiz.
I
Just
you
know
little
simple
diagrams
start
from
there
open
an
issue
say:
hey
folks.
I
was
looking
at
this.
What
do
you
think
we
can
all
collaborate
on
it,
but
you
know
as
new
contributors
even
existing
contributors.
You
know
you
have
in
your
mind
how
this
thing
looks.
You
know
sure
you
can
come
convert
it
to
text,
but
again
a
diagram
would
would
be
helpful.
So
I'm
going
to
step
off
my
diagram
soap
box
and
back
to
you,
natalie.
D
Great
whitney,
actually,
it
looks
like
you've
got
a
question
yeah
well,
I
was
gonna
say
it
feels
a
little
bit
like
the
stars
in
lining
or
serendipity.
Actually,
let
me
share
my.
Let
me
figure
out
how
to
share
this
to
the
chat
anyway.
I'll
share
my
bio
in
chat,
but
my
day
job
is
to
I
I
used
to
work
for
ibm
and
make
ib
videos
for
the
ibm
cloud,
and
now
I
work
for
vmware
and
I
have
a
light
board
studio
in
my
home.
D
Where
I
can
make
videos,
I
can
only
see
figure
out
how
to
send
a
direct
message
to
okay.
Here
we
go
yeah,
so
here's
the
box
at
the
bottom
yeah
there
you
go
so
there's
an
example
of
a
video
I
made
for
ibm
and
I'm
gonna,
I'm
just
starting
to
do
this
for
vmware.
I
Your
your
videos,
up
on
the
up
on
the
slack
channel
again,
I
think
I
think
we
need
to
have
more
of
a
you
know
start
to
you
know,
hone
in
on
that
mindset
of
we
need
to
visualize
what
we're
doing,
not
in
every
instance,
but
in
those
cases
where
you
know
sort
of
makes
sense.
K
A
K
Up
yeah-
I
just
want
to
this
discussion,
reminded
me
of
a
chat
that
I
had
with
chris
last
week,
especially
if
we're
talking
about
bringing
videos
and
such-
and
I
know
that
mermaid
is
done
in
sort
of
in
the
pages.
So
it
doesn't
need
its
own
sort
of
space.
But
I
wanted
to
bring
up
the
idea
of
potentially
creating
a
repo,
a
separate
repo
for
art
assets
for
the
site,
things
like
photoshop
files
or
video
files,
or
the
things
that
we
use
to
generate
svgs.
K
That
way.
If
these
things
need
to
get
edited,
I
know
you
can
edit
svg
in
in
inline
as
well,
but
we
potentially
lose
the
all
the
layering
information
and
that
sort
of
thing,
so
it
might
be
valuable
to
look
into
opening
a
separate
repo
that
can
store
the
the
working
files
for
these
types
of
assets
so
that
we
can
easily
go
back
and
edit
them
later.
I
Yeah,
that's
a
good
point.
Nate!
You
brought
that
up
last
week
and
even
for
example,
svg's
that
come
from
maybe
some
other
package
you
can
edit
it
to
point.
You
can
all
crack
it
open
and
put
a
url
url
in
there
as
to
where
this
diagram
can
be
found,
and
it
could
point
to
that
repo
as
well.
I
So
I
have
an
issue
open
about
adding
and
per
raise
suggestion,
adding
a
section
in
the
diagrams
in
the
in
the
the
style
guide.
So
I'll
work
with
you
guys
on
to
see.
You
know
where
that
might
be
appropriate.
A
Yeah
definitely-
and
I
just
just
also
wanted
to
kind
of
highlight
what
you
mentioned
earlier-
chris-
around
a
possibility
for
new
contributors
to
to
kind
of
get
involved
in
this
way,
definitely
opening
up
an
issue
and
having
a
dialogue
and
conversation
with
the
rest
of
the
community
about
areas
that
you
you
find
on
the
side
that
you
think
could
make
could
be
improved
with
a
diagram
and
getting
a
bit
of
consensus
so
that
you
know
this
is
something
that
folks
will
actually
appreciate
and
be
able
to
get
a
lot
of
value
out
of
before
jumping
in
on
the
work.
A
That's
definitely
the.
I
think
the
path
forward
there
in
terms
of
opening
up
issues
and
chatting
to
folks
and
seeing
what
they
think
is
is
valuable
to
you
so
definitely
jump
in
there.
I
think
that's
a
great
resource
for
sure,
and
I
do
want
to
call
out
I've
got
atharva
who
has
asked
a
question
specifically
for
you,
chris,
being
selected
for
this
kcna
exam
and
preparing
for
that
any
docs
and
resources
for
a
higher
understanding
of
kubernetes
in
general
atharva.
I
do
want
to
definitely
get
you
to
go.
A
Have
a
look
specifically
at
some
of
the
pinned
messages
in
the
sig
docs
channel
and
some
of
the
kubernetes
contributors
channels
as
well,
and
there's
a
lot
of
really
great
useful
resources
there
around
high
level
understanding
of
kubernetes
overall.
A
But
if
anyone
else
has
suggestions
there
of
what
atharva
could
look
at
in
terms
of
documentation
feel
free
to
pop
them
in
the
chat.
So
she
can
get
that
link
and
be
able
to
study
for
her
exam
really
well.
A
Definitely
all
right
any
other.
Any
other
comments
on
mermaid
and
the
diagram
work
that
anyone
wants
to
chime
in
with.
A
All
righty
we're
going
to
move
on
to
the
next
agenda
item
thanks
so
much
chris
for
bringing
that
to
the
attention.
We've
got
some
notes
there
in
there
in
the
agenda
of
some
really
interesting
suggestions,
specifically
also
from
you
whitney
with
the
video.
That's
really
great.
I've
just
listed
actually
that
that
link
that
you
shared
in
the
agenda
docs
for
folks
to
be
able
to
have
a
look
at
later
on
all
right.
A
Moving
on
to
our
next
agenda
item
for
discussion,
this
is
from
ash
actually,
who,
I
believe,
is
on
the
call
any
docs
related
changes.
We
need
to
be
aware
of
for
the
cube
cuddle
out
of
tree
cap.
Please
ash
up
after.
F
You
hey
folks,
so
some
context
for
this
is
that
so
cube.
F
It
did
not
pass
through,
but
in
the
cap
there
were,
if
you
open
the
github
link
I
have
mentioned
and
go
to
line
five
one
one
you'll
see
that
there
are
discussions
about
how
docs
would
be
handled
once
this
component
moves
out
of
the
kubernetes
repository.
So
I
wanted
to
know
from
folks
if
there's
something
we
need
to
be
aware
of,
because
we
are
writing
the
gap
right
now.
F
H
I
think
we're
not
there
yet
so
we're
still
planning
the
road
map
for
keep
control
going
out
of
the
tree,
with
both
six
cli
and
sig
release
and
release
engineering
sub
projects
of
secret
release.
So
it's
not
definitely
not
targeting
for
123.
This
is
in
the
in
the
future,
so
yeah
so
yeah.
So
we're.
I
think,
once
we
get
more
discussion
between
the
folks
at
six
cli
and
sig
release,
we
could
help
identify
which
there's
any
documentation
changes
for
for
control.
F
H
Yeah
I
mean
ideally
for
now
we
could,
I
don't
know
if
it's
correct
to
target
any
all
the
controlled
docs
is,
and
I'm
sure
that
there
will
be
some,
but
I
think
I
ideally
there
would
be
the
whole.
The
keep
control
section
or
maybe
the
overview
at
least
will
be
targeted
for
an
update.
L
L
F
A
A
This
all
right,
great
thanks
ash
for
bringing
that
to
fix
his
attention,
and
that
looks
like
some
more
conversations
between
six
cli
and
secret
release
so
that
we
can
get
kind
of
moving
on
the
next
steps.
There
awesome
we
have
come
to
the
end
of
our
listed
agenda
items,
so
I
do
want
to
kind
of
open
it
up
in
case.
Anyone
else
has
anything
that
they'd
like
to
add.
Last
minute
before
we
were
to
close
off
the
meeting
early.
A
G
Yes,
me
uh-huh.
I
would
like
to
to
add
a
note
about
the
videos.
Just
look
for
the
for
the
meetings
to
to
to
I
mean
search
for
this
topic.
I
mean
about
creative
content,
media
content
about
the
topics,
because
I'm
pretty
sure
that
that
was
talking
in
in
a
meeting
at
least
once
and
the
problem
is:
how
do
you
update
the
video
content
when
the
concepts
change?
It's
not
that's
not
happening
all
the
time,
but
that
can
be
from
two
versions
or
the.
G
So
I'm
pretty
sure
that
if
you
find,
if
you're
searching
the
dogs
meetings
index,
you
can
find
some
video
calls.
So
some
dates
to
to
get
the
video
and
get
that
point
of
view.
A
Thanks
for
sharing
federico
actually
with
me,
given
that
you're
the
video
expert
on
the
call,
I
just
want
to
check
if,
in
terms
of
a
updating
content,
when
things
let's
say,
go
stale
or
out
of
date,
how
have
you
generally
handled
that.
D
The
thing
the
videos
that
I
make
are
only
five
to
ten
minutes
long
and
are
easy
if
something
gets
updated,
they're
pretty
easy
to
reshoot
since
they're,
just
in
my
house
and
they're
all
in
one
take.
So
they
don't
take
a
lot
of
editing.
So
so
I
would
just
say
make
it
again
from
scratch,
but
but
it
would
be
a
pretty
quick
thing.
A
Okay,
that
also
sounds
like
it
could
be
an
interesting
way
to
kind
of
write
up
a
kind
of
a
best
practices
how
to
guide
if
there
are
folks
who
other
folks
would
get
interested
in
doing
videos,
if
that
was
something
that
was
to
kind
of
come
up,
that
could
be
also
an
interesting
contribution
kind
of
dock
as
well
yeah.
Excellent
yeah
awesome
thanks
for
the
record
for
bringing
that
up.
That's
a
really
valid
point.
A
H
Just
one
more
thing
for
all
those
who
are
new
just
to
if
you
want
to
contribute
just
feel
free
to
reach
out
on
the
sigdoc
slack
channel.
There's
several
of
us
here,
they're
more
than
happy
to
help
out
I'm
about
to
send
a
message
on
that
so
feel
free
to
reach
out.
If
you
want
any
help.
A
Definitely
great
message
to
indones
and
I
think
firstly,
big
thanks
to
everyone
for
coming
to
sig
docs
after
the
q,
con
interesting
kind
of
event
taking
place
and
everyone
getting
back
on
their
feet
again
after
a
great
virtual
or
in-person
event,
and
also
thanks
everyone
for
your
agenda
items
and
for
the
discussion
today.
As
ray
said,
new
contributors
or
would-be
contributors,
please
come
into
sigdoc,
say
hi.
Make
yourself
known!
A
Ask
questions,
get
curious,
it's
really
something
that
we're
super
super
interested
in
helping
out
folks
and
getting
to
know
you
all.
So
thank
you
whitney
also
for
coming.
Hopefully
we
haven't,
haven't,
hasn't
felt
too
intimidating,
for
you
always
welcome
anytime
at
this
or
many
other
sig
meetings
as
well.
A
I
think
this
is
another
shout
out
to
anything
that
you're
interested
in
the
kubernetes
community,
naturally
we're
a
bit
biased
in
docs,
but
if
there's
other
areas
of
the
kubernetes
project
that
you
think
are
going
to
be
interesting
to
you
attending
the
different
sigs
they're
also
open
to
be
able
to
go
and
see
what's
going
on,
what's
happening
and
how
you
can
contribute.
A
There
also
a
really
good
way
to
get
to
know
other
community
members
and
and
and
to
stay
curious,
and
so
on
that
thanks
everyone
so
much
everyone's
getting
a
bit
of
a
early
mark,
and
I
will
see
you
again
in
another
couple
of
weeks
for
the
next
sig
dogs
meeting.
Take
care.