►
From YouTube: SIG Docs meeting for 20210907
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
right
just
kicked
off
the
recording,
hey
everybody
welcome
to
the
bi-weekly
sigdocs
in-person
meeting
and
we're
kind
of
getting
our
meetings
in
order
here.
So
I
appreciate
everyone
bearing
with
us
I'm
jim
angel.
One
of
your
co-chairs
for
sig
docs
today
is
september
7th.
It
is
10,
30,
pacific
and
let's
get
rolling
first
of
all,
are
there
any
new
contributors
or
anyone
who
wants
to
introduce
themselves
in
person
feel
free
to
introduce
yourself.
B
Hi
everyone
I'll
go
ahead.
My
name
is
natalie
vosko,
I'm
someone
new
contributor
on
the
on
the
stickbox
scene,
but
I've
been
working
with
sega
for
a
little
while
in
terms
of
kind
of
pr
and
she
triage
with
them
and
and
and
general
reading
stuff,
and
I
am
really
looking
forward
to
doing
a
lot
more
contributing
contributing.
So
hello.
C
A
C
D
Cracking
yeah
there's
loads
of
reviewing
that
that
you
can,
you
can
do
to
help
and
you
can
ask
for
advice
on
slack
if
you're
not
sure
how
that's
going
sure
I'll
reach
out
to
you.
Thank
you.
A
Awesome,
thank
you
very
much,
and
next
week's
pr
wrangler
is
myself
and
I
believe
ray
is
gonna.
A
Shadow
me
as
well
there,
and
just
for
some
context
for
folks
that
might
not
have
been
keeping
up
with
slack
is
there's
actively
a
co-chair
mentoring
group
that
has
been
established
where
folks
are
basically
being
on
ramped
into
what
is
co-chair
involved,
some
of
the
other
leadership
roles
in
sig
docs,
and
so
we
have
folks
that
are
popping
in
and
out
trying
to
shadow
pr
wranglers
getting
to
know
more
about
the
you
know:
administrative
work
for
sig
ducts,
as
well
as
some
of
the
more
advanced
contributing.
A
So,
as
you
see,
new
fen
new
friends
and
faces
around
feel
free
to
not
be
a
stranger
say
hello
to
these
folks
reach
out,
and
if
you
are
one
of
the
folks
that
is
going
through,
the
mentoring
program
feel
free
to
reach
out
and
engage
with
the
other
folks
as
well.
So
it's
a
two-way
street,
a
lot
of
friendly
folks
and
really
excited
to
see
this
happening.
A
A
A
E
Where,
where
did
it
go?
I
have
so
many
things
open,
so
yeah,
the
enhancement
spree
starts
as
you
have
in
the
agenda.
We're
tracking
67
now
enhancements
I'm
going
through
the
tracking
sheet
and
trying
to
update
the
scripting.
So
it's
a
little
more
accurate,
but
it
looks
like
right
now:
51,
herniating,
docs
and
yeah.
We
have
the
first
stock
related
milestone,
as
you
indicate
here
is
the
placeholder
for
the
docs
prs,
which
is
november
18th.
E
It's
it's
a
little,
I
wouldn't
say
it's
tighter
than
usual,
but
it
felt
tight
to
me
this
being
my
first
rodeo,
where
we
have
the
docs
placeholder
pr,
which
is
the
18th
and
then
ready
to
review,
is
the
23rd.
So
hopefully
we're
going
to
be
able
to
shepherd
a
lot
of
those
in
well
ahead
of
the
deadline
and
I'll
be
very
communicative
on
sick
docs
and
the
slack
and
with
the
folks
that
are
typically
doing
this
work
so
yep
any
any
questions
or.
F
I'll
just
add
more
a
few
more
comments
that
the
release
towards
the
end
of
the
year
is
always
very
hard
with
kubecon
and
holidays.
So
we
always
we're
always
going
to
have
this
issue
with
with
milestones,
so
I'm
going
to
place
also
additional
milestones
as
well
in
the
in
the
agenda,
not
just
docs
ready,
one
or
doc's
related
muscles,
but
like
enhancements
raises
this
thursday
code
freezes
november
16th,
the
docs
placeholder
pr
deadline
is
november.
F
18Th
we'd
like
to
we
found
that
having
this
docs
placeholder
pr
after
code
freeze,
we've
gotten
much
better
traction
in
creating
for
enhancement
owners
to
create
placeholder
pr's,
but
then
that
also
leaves
that
we
don't
have
much
time
for
docs
ready
for
review
and
docs,
which
is
november
23,
which
is
the
week
of
u.s
holiday
for
us,
thanksgiving
or
then
doc's
ready
is
the
week
after
november
30th,
because
the
week
after
that
is
the
release
date.
So
it
becomes
very,
very
tight
at
the
end.
F
A
Is
there
anything
that
we
can
do
as
far
as
a
kubecon
contributor
summit
presentation
to
help
out
the
release?
You
know?
Historically,
we
haven't
done
much
to
help
shepherd
the
release,
and
I
just
kind
of
was
thinking
of
that
idea.
Now
as
we're
cramming.
Everything
in
and
folks
are
visiting
for
kubecon.
F
That's
a
good
question.
I'm
sure
there
is,
if
I
could
think
of
something
that
you
know
I'll,
let
you
know
yeah.
I
think
that's
great.
I
think
what
we
should
do
is
definitely
do
a
push
to.
I
know
we
have
the
docs
placeholder
pr
after
kubecon,
but
we
should
start
to
to
start
communicating
to
get
those
open
the
week
after
coupon
or
after
coupon.
B
Just
just
also
wanted
to
let
folks
know
that
it's
unlikely
that
folks
from
europe
are
going
to
be
there
at
kubecon,
given
that
they're
not
letting
us
in
the
country
yet
so
you
there
may
be
some
help
on
the
ground.
A
That's
that's
good
to
know
and
unfortunate
circumstances,
but
it
makes
sense
and
happy
to
have
the
help.
A
D
Will
I
will
say
some
stuff
that
just
for
the
sort
of
the
record
and
people
who
are
catching
up
late,
I
know
chi
ming
tang
had
some
some
feedback
about
the
amount
of
refactoring
that
happens
to
english
pages
and
then
every
time
we
improve
an
english
page
in
sort
of
this
way
it
triggers
you
know,
n
lots
of
work
for
localization
teams,
so
I
I
suspect
it
was.
You
know
the
feedback
was
along
that
that
lines.
D
That
is,
the
value
of
this
kind
of
refactoring,
something
that
outweighs
the
effort
that
it
causes
for
teams
that
have
already
localized
the
page
updating
their
version.
D
A
Got
you
and
I
appreciate
the
context
there
and
that
does
bring
a
refresher
from
when
we
had
the
apec
meeting.
Cheating
did
bring
this
up,
basically
just
to
what
you
said:
tim
having
a
large
refactor
in
english
content,
trickles
downstream
into
the
localization
efforts,
causing
a
whole
ton
of
work
that
was
necessarily
unplanned
and
figured
out
how
we
can
raise
the
communication
visibility
up
a
little
bit
more.
A
A
4Th
it
looks
like,
but
I
do
feel
like
this
is
something
that
we
should
decide
with
or
in
tandem
with
the
localization
teams,
to
figure
out.
A
What's
going
to
be
the
best
way
forward,
at
the
very
least
it
seems
like
over
communication
would
be
the
answer
here
as
far
as
messaging,
multiple
localization,
six
or
the
different
groups,
not
necessarily
sigs,
but
the
different
groups
on
slack,
especially
when
we're
talking
about
refactoring
these,
you
know
major
contents
or
major
chunks
of
the
page,
but
beyond
that,
I'm
not
sure
how
we
can
coordinate
other
than
increasing
and
encouraging
conversation.
C
A
Yeah,
so
currently
there
is
is
somewhat
of
a
poor
mechanism
to
be
totally
transparent
with
with
y'all
and
as
far
as
localization
goes.
Each
localization
teams
has
their
own
various
sets
of
scripts
and
tooling
to
actually
validate
what
is
the
difference
between
what's
currently
in
main
versus,
what's
in
their
branch,
and
then
they
tackle
the
localization
work
based
on
the
differential
between
the
two
previous
branches
and
try
to
bring
them
up
to
future
parity.
A
And
so
this
is
where
a
pr
like
this
would
be
a
challenge,
because
it's
such
a
major
change
that
could
potentially
impact
future
minor
changes
or
even
previous
minor
changes
that
have
already
been
done
on
said
pages,
because
not
only
are
you
then
making
the
actual
layout
changes
you're,
also
making
the
content
changes
localizing
that
translating
that
and
it
can
get
a
little
messy
in
the
terms
of
the
steps
that
are
taken
to
actually
localize
there.
A
C
A
A
A
D
So
I
probably
won't
make
the
meeting
when
this
comes
up.
So
I
hope,
if
anyone's
here
is
there,
that
they
could,
they
could
bring
up
a
suggestion
on
that.
I'm
gonna
make
now
sort
of
theory
of
constraints.
We
could
place
a
limit
on
the
number
of
these
that
we
make
in
you
know
in
a
week
or
in
in
a
in
a
cycle,
so
we
might
say:
okay
during
one
kubernetes
release,
we
will
have
at
most
n.
D
I
don't
have
a
number
but
n
big
page
refactors,
and
that
if
we,
if
we
plan
to
go
over,
that,
we
recognize
that
actually
downstream
doesn't
have
capacity
for
this.
So
there
isn't
a
point
and
people
who
do
sort
of
factory,
optimizations
and
various
different
kinds
of
overall
value
chain
analysis
might
recognize
that
it
is
the
theory
of
constraints
or
it
is
taken
from
the
theory
of
constraints
as
to
why
you
might
do
that.
A
Yeah,
so
let
me
just
reiterate
to
make
sure
I
understand
correctly
you're
just
saying
announced
the
x
number
of
changes
prior
to
the
release
actually
occurring,
so
it's
kind
of
like
an
impending
major
change
for
let's
say
we're
in
123.
Right
now
you
could
say
in
one
two:
four
we're
going
to
have
a
major
release.
D
What
we
might
say
is
that
for
the
the
the
cycle
to
1.24
well,
we're
not
we're
on
the
next
cycle
is
1.23.
Yes,
so
we
released
1.23
and
then
between
then
and
1.24
being
released.
We
might
say
that
we
will
have
only
200
big
page
refactors,
and
so
we
might
do
that
by
pr
size.
We
might
do
that
by
some
other
identification
and
that
once
we
have
reached
that
quota,
we
will
stop.
D
We
will
pull
the
cord
and
stop
the
production
line,
because
we
know
that
the
localization
teams
couldn't
pick
things
up
when
we
pushed
them
to
the
next
bit
of
factory.
A
I
can,
I
think
it
would
help.
I
do
like
the
idea
of
some
sort
of
compromise
or
hybrid
solution
here
where
big
changes
that
are
at
least
tracked.
You
know.
So
if
somebody
does
open
up
an
extra
large
pr
and
has
major
changes,
we
could
potentially
put
a
hold
on
it
until
a
future
release
and
say,
hey,
look.
This
is
great
stuff,
but
given
the
impact
it's
going
to
have
to
downstream
localizations,
let's
track
it
where
you
know
it
won't,
go
actually
won't
become
actually
merged
until
the
following
release
or
something
similar.
A
All
right
moving
on
to
the
last
bit
here
for
discussion,
so
I'm
going
to
send
out
an
email
to
sig
docs
a
little
bit
later
on
today,
announcing
that
I'm
going
to
nominate
divya
mohan
as
a
co-chair
adivia
has
been
around
sick
docs
for
quite
some
time
now
has
also
participated
in
a
mentorship
cohort,
similar
to
what
we're
doing
for
sick
docs.
A
A
The
process
will
be
that
it
goes
up
to
six
docs
for
review.
Folks
can
plus
one
and
talk
about
how
awesome
divya
is,
if
they'd
like
and
then
after
a
certain
period
of
nomination.
I
believe
it's
one
week
this
then
emails
will
go
out
to
kubernetes
dev,
the
major
or
the
wider
developer
release,
email
and
with
a
week.
I
believe
after
that,
then
we'll
open
up
the
pr's.
Where
did
you
open
up
the
prs
to
become
a
co-chair
and
we'll
move
forward
with
that?
A
Much
appreciated,
yeah,
really
just
being
transparent,
with
y'all
we're
looking
to
write
the
the
ship
on
sig
docs
here
get
a
lot
of
folks
into
the
co-chair
area
as
well
as
more
approvers
and
really
just
beef
up
around
contributor.
You
know,
I
guess
quality
of
life
if
you
will
so
so
we're
on
track
right
now
and
we're
we
have
a
great
team
that
we're
working
with
and
if
I
can
help
anyone
else.
If
they're
wondering
how
do
you
become
a
reviewer
approver
co-chair
reach
out
to
me,
I'm
happy
to
help
out.
A
I
don't
think
it's
always
been
that
clear
in
sig
docs
as
far
as
like
a
path
to
become
anything,
and
so
can
very,
I
can
understand
how
it'd
be
very,
not
so
clear
to
to
certain
folks
so
happy
to
help
happy
to
reach
out
and,
like
I
said,
we're
definitely
around
and
in
progress
of
correcting
the
the
ship.
If
I
can
use
a
ship
pun
cool,
that's
all
I
got
anything
else.
Folks
want
to
bring
up
for
discussion.