►
From YouTube: SIG Docs meeting for 20211102
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).
B
So
I'm
sorry,
I
caught
you
off
there
naren,
so
just
just
wanted
to
start
off
the
call,
because
I
realized
it's
been
over
a
couple
of
minutes
right
now.
So
this
is
the
fortnightly,
kate,
sick,
docs,
meeting
that
we
have.
You
know
over
zoom
and
as
with
every
you
know,
meeting
we
have
in
the
kubernetes
community.
This
is
governed
by
the
kubernetes
code
of
conduct.
So
please
please
be
nice
to
one
another
and
refrain
from
you
know
posting
or
saying
harmful
or
abusive
content.
B
But
that's
that's
just
a
basic
process,
hygiene
that
I
have
to
follow,
but
over
and
about
that.
I
shall
just
start
sharing
my
screen
so
that
I
don't
ramble
too
much.
Let
me
just
bring
up
the
agenda.
B
So
yeah
so
the
very
first
thing
on
our
agenda
narrator.
In
luck,
we
are
going
to
put
all
the
new
contributors
on
the
spotlight
and
by
spotlight.
B
I
don't
mean
to
say
that
you
know
we
we're
going
to
force
you
to
say
hi,
but
it
would
be
good
if
all
the
new
folks
came
up
and
said
hi,
and
you
know
if
you'll
feel
comfortable
telling
us
a
bit
about
your
experience
and
what's
what's
the
stuff
that
you're
looking
to
contribute
to
so
I'll,
go
on
mute
for
a
little
bit,
but
yeah
feel
free
to
go
ahead.
A
So
yeah,
hello,
everyone,
I'm
nareen.
This
is
my
first
time
attending
sick
dogs
meat.
So
I
came
to
know
what
kubernetes
last
year,
I
admitted
almost
four
q
cons
and
yeah
last,
let's
just
last
week
attend
my
first
sake,
event,
which
is
of
say,
contribute
tax.
So
I'm
trying
to
go
start
my
journey
with
either
with
contributex
or
sick
dogs.
I've
actually
picked
up
a
task
in
the
sick
dogs
of
adding
diagrams
to
the
documentation
page,
so
I've
been
going
through
the.
A
What
is
that
mermaid
dogs
and
all
those
kinds
of
things
so
I'll
be
first
contribution
I'll
be
making
the
service
page.
Like
you
know
the
service
kubernetes
service.
Sorry
svc,
so
it
lacks
a
lot
of
diagrams
and
I
have
a
very
fair
idea
of
making.
It
is
more
visually
learnable,
so
that
people
know
which
label
we
are
targeting
and
which
food
we
are
targeting.
A
So
that
will
be
great
for
them,
not
just
a
word,
but
as
a
simple
diagram
and
a
simple
emoji
or
moti,
con
of
which
is
right
and
which
is
wrong
would
be
a
great
thing.
So
I'm
trying
to
do
it
in
a
very
easy
way,
so
yeah,
that
is,
that
is
my
first
goal:
to
make
a
fair,
fairly
a
fair
contribution
that
is
going
to
be
looked
up
by
everyone,
so
that
it
will
be
useful
for
everyone
to
come
on
as
well.
So
yeah
happy
to
be
here.
B
And
we're
happy
to
have
you
naren
and
that's
that's
a
lot
of
stuff
you've
already
taken
on
so
kudos.
To
that.
I
know
for
sure
that
I
was
a
lurker
for
nearly
five
meetings
before
I
actually
had
the
guts
to
speak
up.
So
you
you,
probably
win
on
that
count
as
well,
so
so
anyone
else
would
go
would
want
to
go
next.
Any
other
new
contributor.
C
I
was
here
last
meeting
for
my
very
first
one,
but
I
thought
I'd
say
hello
again,
I'm
whitney
and
I
work
at
vmware,
I'm
a
developer
advocate
over
there
and
I
just
got
a
light
board
to
keep
at
my
house,
so
I'm
hoping
to
be
able
to
contribute
some
video
content
eventually.
But
meanwhile
I
made
my
first
pull
request
this
week
on
docs,
just
cleaning
up
some
stuff
that
high
again
just
cleaning
up
some
stuff,
that
I've
been
learning
from
and
and
seeing
some
opportunities,
but
it
hasn't
been
approved.
B
D
Hello,
hello,
amit
here
this
is
my
first
meeting
so.
B
Yeah,
that's
it
hi
ahmed.
So
would
you
like
to
share
a
bit
about
you
know
your
experience
so
far
in
the
ecosystem?
Have
you
looked
around?
Do
you
need
any
help.
D
B
Right
so
one
so
did
you
did
you
filter
out
with
good
first
issues
and
yeah.
B
B
Okay,
so
I
think
we
have
a
positive
good
first
issues,
then
jim
and
all
the
other
folks.
So
maybe
we
it's
time
we
come
up
with
new
good
first
issues
after
the
come,
you
know
the
current
ones
get
close,
so
yeah
glad
to
have
you
on
board
amit
and
if
there's
anything
that
interests
you
and
if
there's
anything
that
that
we
can
help
with
please
let
us
know
we'll
be
definitely
here
to
help
you
out.
B
Anybody
else
on
the
call
who's
a
new
contributor.
I'm
sorry,
I
can't
see
the
participants,
so
I'm
really
sorry
if
I'm
just
going
on
and
on
with
the
same
record.
E
I'm
new
hello,
my
hi
hi,
my
name
is
adriana
frick
hi
I've
been
kind
of
a
lurker
in
the
community
for
a
few
years.
I
haven't
really
done
any
contributions
or
anything,
but
I've
been
to
a
couple
coupons
right.
This
year
was
awesome
because
it
was
virtual.
E
I
have
a
child,
so
it
makes
it
hard
to
do
stuff
sometimes-
and
I
was
talking
to
somebody
about
doing
a
blog
post
for
people
who
are
just
kind
of
starting
out
and
tim
noticed
me
talking
on
the
slaloc
and
suggested
that
I
check
out
doing
blog
posts.
So
I'm
kind
of
I
just
signed
the
contributor
agreement
about
20
minutes
ago,
so
I
could
be
ready
for
the
meeting
and
I
haven't
really
looked
for
any
pull
requests
or
anything
like
that.
I've
just
been
kind
of
thinking
about
the
blog
draft
that
I'm
working
on.
B
Right
and
if
there's
anything
that
we
can
do
to
help,
you
know
after
you
have
a
quick
glance
and
if
there's
anything
that
we
can
do
to
help
do
give
us
a
shout
out
on
the
sick
dog
slack
we
we're
always
around.
At
least
one
of
us
is
always
around
and
we'll
definitely
get
back
to
you.
B
I'm
not
sure
if
it
was
just
for
me,
but
I
just
got
ashish's
name
and
I
was
not
able
to
hear
the
rest
of
it.
I'm
sorry
if
it
was
just
me
but
yeah.
B
I'm
horrible
now
yeah,
but
you're
breaking
up
your
voice
is
a
little
robotic
at
this
point,
if
I
may
say
so,
without
sounding
offensive,
but
yeah.
B
B
B
G
I
just
want,
I
didn't
want
to
cut
over
anybody
who
is
new.
I
am
I'm
not
necessarily
new,
but
I
am
back
from
leave.
So
I
just
wanted
to
say
hello
to
everyone.
I'm
looking
forward
to
jumping
back
in
and
helping
everyone
participate.
I
didn't
introduce
myself.
My
name
is
abigail.
I
also
work
at
vmware,
so
hi
whitney.
I'm
really
excited
to
be
back
and
saying,
jumping
in
on
the
meetings.
Okay,
thank
you
glad.
B
All
right,
I
think
we
can
move
on
then,
if
there's
no
one
else
so
yeah
so
updates
and
reminders.
So
this
week's
pr
wrangler
is
jim
and
the
next
week's
pr
wrangler
is
I'm
I'm
hoping
I'm
pronouncing
this
name
right.
Is
it
kimming
tank?
So
I
hope
that's
the
right
pronunciation.
If
not,
I'm
really
sorry
so
prove
us.
Please
make
sure
you
know
your
pr
wrangler
shifts
and
yeah.
B
That's
that's
pretty
much
from
the
updates
and
reminder
side
of
things,
and
I
think
we
can
move
on
to
our
main
agenda
and
for
the
release.
1.23.
Please
may
I
know
who's
on
so
that
gel
can
give
the
updates.
H
Do
you
want
me
to
take
this
ray
yeah
go
ahead:
okay,
hello,
everyone
for
the
the
docs
part
of
release,
1.23
we've
downgraded
from
green
to
yellow
in
the
last
week,
primarily
because
we
don't
have
anywhere
near
as
many
placeholder
pr's
as
we
were
hoping
we
might
get.
We
were
hoping
to
get
ahead
of
some
of
this
stuff,
but
unfortunately
that
looks
like
it
hasn't
happened,
so
we're
going
to
have
the
the
same
crunch
that
we've
had
in
in
previous
release
cycles.
H
So
currently
we're
tracking
56
issues.
We've
got
seven
drafts
so
far,
two
are
ready
for
review
and
one
has
been
merged
completely,
which
leaves
us
with
like
49
or
so
or
47,
still
requiring
some
sort
of
placeholder.
H
So
we're
gonna,
be
we've
already
sent
out
sort
of
pings
to
the
the
the
issue
owners
and
we'll
probably
be
doing
another
round
of
reaching
out
this
week
to
try
and
prod
people
into
opening
up
some
of
those
prs
and
just
a
a
process
point
the
the
integration
branch
is
healthy.
So
that's
that's
a
good
sign.
I
All
right,
I
just
want
to
add
on
a
few
notes,
just
on
dates,
so
the
so
syndox
is
aware
of
dates
as
well.
Code
freeze
is
coming
up
in
a
little
bit
over
two
weeks
or
two
weeks
exactly
actually
on
november
16th
and
two
days
after
code
freeze
is
the
docs
placeholder
pr
deadline.
I
So
that's
coming
up
in
about
two
weeks,
but
we
we
know
this
is
kind
of
a
trend,
especially
at
the
the
end
of
the
year,
release
that
with
the
holidays
in
coupon
that
that
that
placeholder
prs
are
kind
of
more
last
minutes.
So
but
we
are
status
yellow.
I
I
I
think
we're
okay,
because
the
enhancement
team
is
actually
going
to
go
through
their
round
of
things
for
enhancement
owners
and
with
with
the
round
of
pings.
We've
asked
them
to
include
a
reminder
that
the
doc's
placeholder
pr
deadlines
is
is
around
the
corner
as
well,
and
also
I
will
send
out
another
email
to
the
community.
I
sent
one
last
week
about
these.
These
milestones
and
deadlines
for
123,
so
I'm
going
to
send
one
out
either
tomorrow
or
on
thursday
for
another
reminder
for
code
freeze
and
the
docs
placeholder
pr
deadline.
I
So
we'll
we'll
see
we
might.
We
might
need
a
little
bit
of
assistance
the
week
before
or
the
doc's
place
of
the
docs,
placeholder
pr
deadline
and
so
yeah
I'll
keep.
You
noted.
F
Right
and
right,
if
you
don't
mind
in
chat,
they're
norman,
asked
a
great
question:
what
is
a
shadow,
if
you
don't
mind
giving
a
little
context
in
the
release
team
in
the
process
there
that'd
be
awesome.
I
Yeah,
so
they
released
so
the
release
team
part
of
the
part
of
the
release
teams
is
the
shadow
role.
So
each
role,
so
it's
like
enhancements,
documentation
and
enhancements
rule.
Is
they
they?
They
gather
all
the
enhancements.
That's
going
to
be
targeted
for
the
123
release,
they
kind
of
handle
a
hand
over
to
docs
and
the
docs
role
it.
They
make
sure
that
any
enhancements
needs
if
they
need
any
updates
for
documentation
or
any
new
documentation
for
the
for
any
new
or
updated
enhancements
that
that
goes
into
the
release
as
well.
I
In
the
shadow
role
on
each
team,
there's
at
least
four
shadows,
where
it's
like.
It's
like
an
apprenticeship
where
they
learn
how
what
what
the
process
for
that
team
is
and
there's
also
a
role
lead
and
that
role
lead
is
the
person,
that's
mentoring,
the
shadows
and
on
on
how
on
what
that?
What
that
what
the
procedures
and
tasks
are
for
each
role
and
the
shadows
also
participate
in
in
those
tasks
as
well.
I
So
there's
a
number
of
roles
or
six
roles
in
the
release
team
and
about
four
shadows
per
team.
Some
teams
have
five
shadows
for
this
cycle.
Enhancements
have
had
five
five
shadows
for
the
past
several
cycles,
because
there's
a
little
bit
more
work
on
the
front
and
meaning
the
first
about
three
weeks
of
the
release
for
the
enhancement.
So
I
hope
that
answered
the
question.
B
And
I
guess
that
would
be
really.
It
would
be
really
great.
If
I,
you
could
actually
paste
the
link
on
the
chat
to
the
shadows
handbook,
I
guess.
H
B
Yeah
that
that
would
provide
further
insight
to
the
person
who's
asking,
I'm
not
sure
who
asked,
because
I
can't
open
up
my
chat,
so
that
would
provide
further
insight.
B
All
right,
so
are
there
any
questions
for
ray
or
or
you
know,
the
release,
1.23
talks,
team.
B
I
shall
take
the
silence
as
a
no
so
yeah.
So
let's
move
on
to
the
issues
in
pr.
So
I
see
there
are
none
listed,
but
are
there
any
specific
pr's
or
issues
that
require
highlighting
on
the
call
and
if
yes,
please
feel
free
to
speak
out
the
floor
is
all
yours
guys.
Folks,
sorry.
J
Hey
everybody,
this
is
chris,
so
I
was
speaking
to
tim,
a
ways
back,
and
he
suggested
that
you
know
some
of
the
material
that
I
had
on
mermaid
could
be
used
as
a
blog
to
contribute
to
the
developers
contr
the
community
contributor
website.
I
think
that's
k-a-s-dev,
so
tim
and
I
went
back
and
forth.
I
have
something
he
said
open
a
pr,
but
I
wasn't
quite
sure
where
to
open
that
pr.
J
Should
I
open
it
here
for
the
website
and
note
that
it's
going
to
end
up,
you
know
under
k-a-s-dev,
or
do
I
go
over
there
and
open
a
pr.
J
Okay,
so
it's
something
separate,
it's
just
sort
of
a
bloggy
write-up
of
some
of
the
mermaid
stuff,
and
it's
just
to
give
the
you
know
the
contributor
community
that
you
know
hey
diagrams
are
good.
We
got
a
tool
that
you
can
use
to
create
diagrams,
so
it
would
be
a
blog
over
in,
like
I
said,
k
a
s
dot.
B
So
that
is
the
contributor
website
right,
if
I'm
not
mistaken,
so
in
that
case,
I
do
think
opening
a
pr
to
you
know.
Kate's
website
should
do
because
we
do
have
the
process
of
mirroring
it
to
the
kth
dev
website.
If
I'm
not
wrong,
please
correct
me,
jim
andre
there
is.
There
is
something
that
I
was
told
that
there
was
a
mirroring
process
between
the
two.
So
if
that's
something
that
we
could
avail
in
this
situation,
then
that
would
be
great.
F
F
For
folks,
in
the
call,
case.io
is
official,
kubernetes.io
kubernetes
website,
there's
also
a
case.dev,
which
is
kind
of
like
a
fork
of
the
website,
with
the
focus
specifically
on
contributions
and
contributors.
It's
a
way
to
abstract
a
contributor
information
from
you
know
upstream
kubernetes
documentation,
so
they're
talking
about
the
two
different
blogs
here.
There
is
a
separate
blog
post
on
ks.dev,
usually
focused
more
on
developer
activities
and
then
there's
also
blog
posts
on
kubernetes.io,
where
this
might
get
a
little
questionable
is.
F
Should
this
land
on
case
that
I
owe
the
upstream
documentation
website
blog
post
area,
as
opposed
to
only
on
kate's
dev,
which
is
more
contributions,
more
developer,
focus,
etc.
I
think
personally
starting
off
opening
my
case
dev
or
case.io.
The
main
website
moving.
Those
pr
is
not
going
to
be
that
big
of
a
deal
I
would
suggest
39k
set
dev
only
with
my
lack
of
under
my
my
lack
of
understanding
on
the
current
process
of
synchronization.
F
If
the
intent
is
to
land
a
case.dev,
it
seems
like
it
might
make
sense
to
open
it
up
on
cage.dev
and
then
also
just
a
little
bit
of
additional
context.
F
When
we
introduced
mermaid
to
the
upstream
kubernetes
documentation,
I
think
it
was
about
two
years
ago,
or
so,
maybe
a
year
and
a
half
ago
I
volunteered
to
create
a
blog
post
to
start
writing
about
how
to
leverage
mermaid,
because
these
features
and
tooling
that
exist
in
the
website
is
not
widely
advertised.
F
I
never
got
around
to
it
so
chris.
I
credit
you
to
picking
this
up
and
driving
it
home.
F
I
think
it's
very
valuable
to
have
this
information
around
mermaid
mermaid
management,
my
only
caveat
or
question
mark
that
I
would
throw
out
there
is-
and
this
is
my
own
ignorance-
that
I
don't
know
what
the
current
status
is
of
our
major
integration
if
we're
using
the
doxy
integration
or
if
we're
using
the
one
that
I
plugged
in
a
year
and
a
half
ago,
I
would
err
on
the
side
of
if
we
can
use
the
native
doxy
mermaid
integration
and
promote
that
around
the
blog
post.
F
If
that
makes
sense,
so
it
shouldn't
change
anything
as
far
as
chris,
your
intent
to
write
that
post,
it's
just
a
matter
of
how
it's
implemented.
So
that's
kind
of
my
two
cents
and
I'll
get
off
my
soapbox
now.
J
Okay,
so
just
to
give
everybody
an
update
on
the
whole
mermaid
situation,
so
a
couple
of
diagrams
have
existed
before
and
there
were
some
added
to
the
contribution
ray
had
suggested
and
I
opened
up
a
pr
to
create
a
diagram
style
guide
as
part
of
the
the
content
style
guide.
So
that's
that's
in
that's
being
processed
or
created.
I
hope
to
have
something
by
the
end
of
the
week.
It's
it's
fairly
robust.
J
If
you
will
and
then
this
blog
is
just
sort
of
a
collapsed
bloggy
format
of
thing,
and
it's
just
for
the
new
con.
You
know
the
developer
contributors
or
what
have
you.
So
in
summary,
we
are
using.
What's
there
in
you
know,
the
native
mermaid
tim
had
suggested
that
I
don't
quite
yet
explain
or
create
a
pr
and
how
to
move
away
from
the
from
the
hugo
short
code
tag.
But
I
guess
that
can
be
something
separate,
but
I'll
make
sure
I
try
and
include
both
on
the.
J
When
I,
when
I
push
the
the
mermaid
diagram
style
or
the
diagram
style
guide,.
F
Cool
yeah,
let's
pair
up
on
that
chris
I'm
happy
to
it,
should
be
a
relatively
quick
change.
There
might
be
a
few
things
we
need
to
edit,
but
to
integrate
in
with
doxy's
mermaid.
Integration
should
be
a
little
bit
more
supportable,
but
more
maintainable
moving
forward.
So
I'm
happy
to
pick
that
up
with
you
work
with
you
on
that
shouldn't
change
the
content,
you're
blogger
and
the
work
you've
done
already.
J
Yeah,
it
already
works.
I
tested
it
earlier,
so
I
think
a
pr
just
to
transition
the
mermaid
docks
away
from
the
short
code
to
just
native
mermaid
would
would
you.
F
Know-
and
I
think
it's
still-
I
think
it's
still
a
short
code-
it's
just
a
different
implementation
mechanism,
but
either
way
we
can.
We
can
take
this
offline
and
I
can
help
you
out
there
and
then
just
because
we
have
a
large
audience
in
the
call
here.
I
wanted
to
explain
what
mermaid
js
was
just
for
contacts
for
folks,
and
so
mermaid.js
is
a
javascript
plugin
that
allows
diagrams
to
be
built
on
the
fly.
F
So
a
lot
of
the
power
and
value
that
comes
from
kubernetes
documentation
is
the
fact
that
we
write
everything
in
markdown,
and
so
we
don't
write
anything
well,
there's
a
there's,
an
abstract
there,
but,
let's
just
say
we
don't
write
any
html,
but
most
of
the
documentation
you
write,
isn't
markdown
and
mermaid
is
a
way
that
we
can
build
diagrams
on
the
fly
using
javascript.
It's
a
plug-in
that
runs
natively
in
the
browser
to
build
these
diagrams
and
a
beautiful
part
of
it
is
that
you
can
then
have
a
structured,
markdown
language
for
your
diagram.
F
So,
as
things
change,
you
want
to
change
the
layout.
Things
are
inaccurate.
You
know
things
change.
You
no
longer
need
to
go
into
an
image
editor
to
make
those
changes
to
the
diagram
they
can
be
reflected
directly
into
markdown.
So
it's
incredibly
powerful
tool.
We
just
don't
do
a
great
job
advertising,
it's
relatively
new
to
kubernetes
documentation
and
chris
is
leading
the
efforts
there
of
boosting
visibility.
So
I
really
credit
you
there.
Chris
sticking
with
it.
B
Right
is
there
anything
else
that
anybody
would
like
to
flag
up
in
terms
of
issues
in
prs,
anything
that
requires
visibility.
B
So
by
non-code,
what
exactly
do
you
mean?
Because
there
are
a
host
of
non-code
opportunities
within
kubernetes?
So
not
necessarily
all
of
them
are
tracked
with
prs.
So
what
what
it
depends
upon?
What
you're
looking
out
for
exactly.
B
Okay,
so
with
respect
to
documentation,
you
can
track
it
on
k
website.
It
should
be
github.com
kubernetes
website.
If
I'm
not
wrong,
then
there
are
a
host
of
other
stuff.
That
is
a
part
of
kubernetes
community
or
the
the
again.
It's
mostly
you
know
stuff,
that's
related
to
editing,
and
you
know
basic
stuff
like
that.
Then
there's
k8
star
dev,
that
jim
mentioned
so
again,
blog
related
stuff
is
there.
So
if
you're
interested
in
that
area,
you
can
pick
up.
B
Yeah
but
that's
subject
to
approval
and
related
to
content.
That's
that
you're
writing
the
blog
about.
So
if
it's
related
to
kubernetes.
K
B
Okay,
okay,
yeah,
so
I
mean
you
can
write
blogs
and
you
can
go
through
the
kubernetes
dot
io.
There
are
several
blogs,
but
it
will
be
going
through
a
formal
review
and
approval
process,
so
it
will
be
submitted
by
our
pull
request
and
will
typically
be
written
in
markdown
and
submitted
by
you
so
yeah
I
mean
it
will
go
through
a
separate
review
and
approval
process
and
yeah.
It
depends
upon
what
the
block
content
actually
is
for
it
to
be
decided
whether
we
can
publish
it
or
not.
Yeah.
B
Hopefully
that
answers
the
question.
Yes,
all
right,
anything
else.
B
I'm
gonna
take
that
silence
as
I
know
and
yeah,
so
I
have
a
couple
of
updates
from
my
side:
more,
not
updates,
really
but
more
of
a
discussion.
B
So
there
are
around
100
plus
prs,
including
aged
ones,
in
the
english
language,
and
if
you
know
you
follow
the
github
query,
you'd
be
able
to
see
them
open
up
I'll,
just
show
you
the
so
we
do
require
you
know
to
have
the
numbers
reduced,
if
I
may
say
so
in
a
very
crude
manner,
but
we
do
need
some
some
of
these
further
down
the
line
in
the
pipe
and
we
need
to
have
a
lot
of
them
closed
or
followed
up
on.
B
So
based
on
the
appetite
of
work
that
you
can
take
up.
There
is
a
lot
of
work
to
be
done
in
this
section
as
well.
So
if
you
are
comfortable
with
reviewing
content-
and
you
know
providing
your
insights
on
the
documentation
or
the
wording
bits,
please
feel
free
to
do
that.
B
The
github
query,
as
I
mentioned,
is
there
on
the
agenda
documentation.
So
you
should
be
able
to
find
the
you
know,
brs
that
are
open,
currently
a
lot
of
them.
I
think
around
at
least
30
of
them
are
older
than
for
five
months
at
this
point.
B
So
if
there
are
any
sort
of
you
know,
insights
that
you
can
chip
in
with
or
if
there
is,
if
y'all
can
follow
up,
that
would
be
great,
any
volunteers
that
you
know
we
have
on
this
call
or
y'all
can
ping
us
on
the
sick
dog
slack.
If
you
all
need,
you
know
direction
on
how
to
proceed,
and
we
will
probably
respond.
B
You
know
in
a
day
or
two
with
what
you
all
can
chip
in
with,
because
there's
a
lot
of
stuff
that
requires
attention
in
this
in
this
area,
so
yeah.
Any
volunteers,
though,
would
like
to
chip
in
on
the
call.
A
I
would
like
to
volunteer,
but
I
wouldn't
I
would
need
a
set
set
of
guidelines
on
what
to
be
done
and
procedure,
because
this
is
my
very
first
time.
So
I
have
no
clue
of
like
how
the
procedure
goes
like
who
to
tag
or
whom
to
get
all
those
things
and
what
is
the
proper
life
proper
pipeline
to
communicate
and
how?
What
are
the
guidelines
of
reviewing
and
what
are
the?
A
What
are
the
no-go
factors
and
what
are
the
go
factors
and
what
sort
of
what
is
a
checklist
we
need
to
check
on
to
making
the
review.
So
these
kinds
of
things,
if,
if
there
is
a
checklist,
it's
very
much
appreciated
and
yeah.
Those
are
things
that
I
wanted
to
say.
B
Right
so
one
thing
that
I
can
you
know,
sort
of
provide
as
a
sec,
not
segue.
Really,
as
you
know,
potential
follow-up
to
this
discussion
is
that
checklist
on
the
slack
segdog
slack
I'll
also
make
it
a
point
to
add
it
in
here
for
folks
who
are
viewing
the
agenda
documentation
after
the
you
know
meeting,
but
I
think
slack
will
be
better
better
in
terms
of
accessibility.
B
To
be
honest,
so
I'll
I'll,
just
put
we'll
just
collate
a
list
of
links,
a
few
of
them
are
already
on
the
bookmarked
bookmark
pins
on
the
sig
dog
slack.
So
you
can
go
through
those,
but
we
will
be
collating
and
putting
a
few
more
for
you
to,
or
you
know,
chip
in
with,
but
that
makes
sense.
A
Yeah
that
makes
complete
sense
right
now,
I'm
looking
at
the
sick
dogs
channel,
but
I
can't
see
much
of
the
bookmarks.
B
B
Yeah,
that's
the
one
I
might
have
you
know
got
in
my
language
confused
here,
but
the
pin
topics
is
what
I
was
referring
to.
Contributor
guide
is
one
of
the
things
that
is
pinned
on
there
and
over
and
above
that
there
are,
you
know,
other
couple
of
links
that
I
will
collate
and
put
it
as
a
slack
link
for
towards
this.
You
know
effort.
Would
that
make
sense
for
you
and
for
everybody.
A
Else
in
the
call
as
well
yeah-
and
I
would
like
to
voice
out
a
point
here
so
when
I
lister
when
I
go
to
the
sick
community
stress,
there
is
a
overall
list
which
kind
of
tablets
how
many
six
are
there
and
those
links
and.
K
A
Click
on
the
sick,
docs
thing
it
gives
it
takes
me
to
a
page
where
I
can
see
all
the
sig
meetings
and
regarding
who
are
all
the
contributors
and
for
the
chess.
So.
H
A
I
want
what
I
would
like
to
suggest
just
how
do
I
get
started
or
what
are
the
things
to
get
started
like
if
I
go
to
any
government
discount
or
something
like?
How
do
I
get
started,
or
a
quick
start
guide
to
something
like
that
so
step
lines
for
everybody
to
get
started
so
attend
a
meeting
and
the
meeting
startup
er,
and
these
are
the
links
that
you
can
go
and
look
or
something
like
that.
A
document,
a
documentation
or
a
gist
of
it.
A
Added
on
the
page
would
be
a
very
good
thing
because
to
get
this
calendar
event
and
to
get
this
thing,
I
was
a
bit
of
a
confused
way
like
last
week.
I
couldn't
get
those
things
in
our
to
say
in
a
very
perfect
manner,
so
I
have
to
ask
people
and
ask
them
in
the
slack
and
those
things.
So
if
it
is
like
what
to
say
checklist-
or
these
are
things,
how
they
get
started
page
or
get
started
kind
of
section
would
be
a
very
nice
thing.
I
I
just
posted
that
on
the
chat
we
do
have
a
how
to
contribute
page
on
the
kubernetes
website.
Right.
I
It
does
have
the
the
links
to
the
to
the
slack
and
to
the
google
group
to
the
sigdoc's
mailing
list
and
also
has
a
link
to
the
sig
docs
channel
on
the
slack.
There's
also
links
to
some
videos
as
well
and
also
shows
you
some
like
the
like
the
how
to
contributes
and
see
so
post
it
on
on
the
slack
once
around
the
chat,
the
zoom
chat.
I'll
put
it
on
the
meeting
notes
as
well.
B
Right,
thank
you
for
that.
Right
really
really
appreciate
that
anything
else
that
you'd
like
to
suggest
or
anybody
else
likes
to
chip
in
with
this
effort.
You
all
don't
need
to
come
out
right
and
say
or
raise
your
hands
or
anything.
That's
that's
completely
fair.
I
don't
expect
y'all
to
do
that,
but
if
there's
any
interest
around
this,
please
reach
out
to
us
on
sick
dog
slack
I'll,
be
starting
a
thread
for
this,
so
y'all
can
reach
out
there.
Probably
so.
A
B
A
One
more
thing
ray
you:
I
know
the
existence
of
the
contribute
guide
on
the
contribute
thing
on
the
kubernetes
dev,
also
in
the
dev
website.
Also,
but
what
I'm
suggesting
is
like,
like
many
of
many
films,
they
say
that
sick
dogs
list
and
eventually
finding
out
that
and
looking
at
the
page
of
the
let's
say
I
eventually
found
this
page.
A
Let
me
post
that
link
here.
Give
me
a
moment.
This
is
this
data
page.
So
it's
just
the
sig
docs
read
me
page.
Okay,
then
here,
if
I
go
here
and
it's
it's
completely
blank,
so
it
doesn't
have
like
how
to
get
started
or
how
do
I
so
I'm
saying
as
a
as
a
as
a
segway
or
a
as
a
a
way
to
cover
this,
if
we
can
add
it
as
an
extra
column
here
that
would
be
nice.
A
B
Right,
we
will
consider
that
and
we'll
try
to
make
it
a
little
more
user
friendly
for
folks
who
are
incoming
and
who
are
relatively
new.
Thank
you
for
that
feedback.
B
B
I'll
take
the
silence
as
a
no,
so
the
next
discussion
item
was
more
around
the
apac
friendly
meetings.
B
We've
I've
sort
of
narrowed
down
the
slots
and
days
for
the
apac
friendly
meeting
and
the
poll
will
be
sent
out
by
the
end
of
this
week,
so
request
all
those
folks
for
joining
him
from
apac
time
zones
wherever
y'all
are
to
vote
on
this
because
we
really
want
for
you
all
to
be.
You
know
comfortable
with
the
new
timings
that
we
are
setting
out
with
for
the
apac
friendly
meetings.
B
I
understand
that
this
meeting
is
something
that's
not
really
feasible
for
apac
folks
to
attend,
and
the
current
apac
friendly
meetings
are
again
not
covering
a
lot
of
ground
in
terms
of
the
various
regions
so
trying
to
we've
I've
narrowed
down
a
couple
of
slots
and
days,
so
apologies
that
I
could
not
send
it
out
earlier,
but
it
will
be
sent
out
by
the
end
of
this
week
on
the
different
localization
groups,
as
well
as
the
mean
sig
docs
so
channel
on
the
slack
so
yeah.
That's
that's
regarding
that.
B
I'll
take
the
silence
that
says
no
and
I'll.
Actually
let
ray
take
the
center
stage
for
the
next
one,
because
this
has
been
your
baby
and
you
know,
you've
led
the
efforts
for
this
so
over
to
you
ray
for
talking
about
the
label
command
being
used
with
refactor
now,
and
thank
you
so.
C
I
For
that,
yes,
so
there's
some
there's
been
some
pull,
requests
that
have
large
refactoring
changes.
Either
content
has
been
moved
around
or
pages
have
been
deleted,
and
this
has
an
effect
to
localization
efforts
as
well,
where
they're
not
aware
of
these
of
these
large
changes,
and
they
too
also
have
to
align
the
localization
pages
to
match
the
english
or
any
large
refactoring
changes,
particularly
done
on
the
english
site.
I
First,
so
we've
created
a
new
label
called
refactor,
so
you
could
so
you
could
apply
this
label
to
to
a
pull
request
with
any
large
refactoring
changes
with
just
the
slash
label
space
refactor
and
then
it
will
add
a
label
to
to
to
that
pull
request.
So
then,
next
step
is
trying
to
see
if
how
to
on
on
how
we
can
send
communications
to
the
localization
owners
and
when
there
is
a
pull
request
with
this
label.
So
you
can
see
here
on
the
slack
there.
I
There
is
a
link
to
the
slack
channel,
sorry
slack
thread
and
within
that
sac
thread,
there's
there's
a
github
pull
request
and
I've
applied
that
label
the
refactor
label
to
that
pull
request.
So
so
the
label
is
available
to
be
to
be
used
now
so
now
trying
to
figure
out
how
to
how
do
we
notify
localization
elders
and
also
sigdoc
reviewers
of
that
any
pull
requests
with
that
label
as
well.
So.
B
K
I
was
wondering
if
that
would
apply
to
new
pages
as
well
as
just
change
pages,
or
is
it
really
just
to
show
them
hey?
This
page
has
changed
so
you
have
to
redo
it
initially,
it's
it's.
I
It
is
for
this
page
has
changed.
You
have
to
redirect
this
page
has
been
deleted,
but
I
know
for
release
efforts.
We,
the
the
new
page,
is
particularly
done
after
a
release,
but
I
I
believe
that
that
would
work
well
as
well
for
any
new
pages
for
like
any
new
enhancements
that
that
goes
into
release.
So
I
believe,
that's
also
a
good
use
case
for
it.
B
Right
any
other
questions
for
ray.
A
So
I
have
a
question
so
there
are
like
multiple
versions
of
documentation
so
for
version
1.21.18,
1.19
1.20.
A
So
if
I
make
a
diagramming
contribution,
which
version
do
I,
which
version
do
I
target,
do
I
target?
Do
I
target
for
a
commonality,
or
do
I
toggle
for
a
single
version
or
which
is
the
latest
so.
I
So
if
you're,
if
you're
targeting
a
change
that
is
specific
to
the
current
version
of
kubernetes,
let's
say
it's
122,
then
you
would
do
two
to
the
main
branch
of
k
website
and
then
when,
when,
when
the
next
release
is
cut,
the
docs
really
will
will
create
that
will
create
that
branch
of
release
122
so
that'll,
be
so
that
will
go
into
release
1282
and
also
stay
with
the
current
one.
I
The
the
cur
main
k
website,
the
only
the
only
changes
I
would
see
to
cherry
pick
back
into
an
older
version
like
release,
120
or
121,
is
if,
if
there
is
a
change
that
needs
to
be
reverted
or
that's
changed
on
main
and
that's
also
a
valid
change
for
the
previous
versions.
I've
seen
that
before
as
well.
So
that's
when
we
would
cherry
pick
or
or
back
into
the
to
the
older
branches.