►
From YouTube: K8s SIG Docs meeting for 20220906
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
Alrighty
then,
and
we
started
recording
the
session
of
this
sick
docs
meeting.
This
is
the
stick
docs
meeting
for
Tuesday
the
6th
of
September
2022.
A
I'm,
one
of
the
co-chairs,
Natalie,
watko
and
I-
do
want
to
remind
everyone
that,
as
this
is
kubernetes
community
meeting,
it
does
mean
that
we
follow
the
kubernetes
code
of
conduct,
which
generally
means
that
we
like
to
try
and
be
respectful
and
kind
to
one
another
during
all
kinds
of
interactions,
including
live
on
this
meeting,
but
also
via
slacking
through
issues
and
PRS
as
well.
A
So
thanks
so
much
folks
for
adhering
to
the
code
of
conduct
and
let
me
just
very
quickly
add
for
those
who
can't
see
the
agenda
I'll
just
pop
that
into
the
chat
now
and
I'm,
going
to
very
slowly
share
my
screen
and
see
if
we
can
get
better
gender
on
the
screen
now
too.
One
second.
A
I
seem
to
have
many
tabs
open
and
it's
not
letting
me
do
what
I
want
it
to
do.
So
what
I
might
do
is
not
sure
for
the
time
being,
I'll
figure
it
out
in
a
second,
but
everyone's
got
that
link
there
in
the
chat
that
they
can
open
up.
A
A
Firstly,
what
I'd
love
to
what
I'd
love
to
do
is
welcome
any
new
contributors
that
we
might
have
to
the
session
today,
if
you're
around
as
a
new
contributor
would
love
to
say,
hello
feel
free
to
unmute
yourself
and
say
hi
or
if
you
wish
not
to
do
that
and
want
to
say
hi
in
the
chat
instead
you're
more
than
welcome
to
do
that
instead,
but
we'll
give
folks
a
few
minutes
to
say
hello
if
you're
new
around
here.
A
Hi
there
am
all
welcome
thanks
for
saying
hi,
yes
great,
to
see
that
you're
new.
Hopefully
we
can
help
answer
any
of
the
questions
that
you
might
have
great
to
always
welcome
some
new
folks
around
so
glad
to
hear
that
you
started,
we
are.
We,
hopefully
are
a
friend,
friendly,
Bunch
and
feel
free
to
definitely
come
to
either
the
slack
Channel
stigdox
or
here
to
the
community
meetings.
A
If
you've
got
any
questions
so
great
to
meet
you
all
thanks
so
much
just
going
to
add
your
name
here
and
and
then
we'll
I
think
we
can
get
started
with
the
rest
of
our
agenda.
If
we
haven't
got
anyone
else
who
wants
to
say
hi.
A
Alrighty,
let's,
let's
keep
going
a
quick
reminder
for
our
PR
Wranglers
and
PR
angling
shifts
that
are
happening
this
week.
Our
PR
Wrangler
is
a
is
a
specifically
Jim
co-chair
here
of
the
fake
docs,
and
next
week's
up
PR
angler
is
going
to
be
Zach,
and
this
will
be
shadowed
by
mahek
as
well.
Who
I
can
see
on
the
call
today,
which
is
great
for
anyone
interested
in
shadowing
PR
wrangling.
Please
feel
free
to
reach
out
to
us
and
see
docs.
A
We
are
more
than
happy
to
help
with
this.
For
folks,
who
don't
know,
PR
wrangling
is
what
we
as
reviewers
and
approvers,
do
specifically
a
previous
shot.
Sorry
should
I
say
to
kind
of
push
all
of
our
contributions
that
are
coming
into
sigdocs
pretty
regularly,
so
that
we
can
keep
our
PR
account
at
a
decent
amount
and
we
try
and
do
that
across
all
of
our
localizations
as
well.
A
So
our
localization
leads
are
also
encouraged
to
jump
in
and
help
out
with
wrangling
as
they
can,
but
any
PR
Wranglers
on
the
on
the
call,
please
remember,
to
keep
an
eye
on
the
pr
WR,
England
ships
and
we'll
announce
them
weekly,
either
in
this
meeting
or
in
our
slack
meetings
as
well.
A
So
moving
on
to
the
next
part
of
our
agenda,
you
may
have
seen
an
interesting
update
of
the
new
release.
That's
come
out
now,
and
so
we
are
at
the
1.26
release.
This
is
super
exciting
it's
the
first
week
and
we've
got
some
specific
dates
that
we
want
to
take.
Take
note
of
for
this
for
this
release.
So,
firstly,
the
release
cycle
begins.
As
you
know,
yesterday,
on
the
5th
of
September
and
code
freeze
for
this
cycle
will
be
on
November.
A
The
9th
the
specific
release
day
is
December
6th
as
well,
and
I
forgot
to
I
just
skipped
over,
unfortunately,
the
enhancements
for
you
that
is
specifically
also
on
October
the
7th.
Specifically
you
a
couple
of
names
that
you
will
be
getting
very
used
to
seeing
and
hearing
about
this
release.
A
Carolina
is
our
docs
lead
and
Federico
is
going
to
be
our
Communications
lead
for
this
release,
so
you'll
be
seeing
updates
from
them
throughout
the
assorted
slack
channels,
including
big
dogs,
and
release,
comes
and
release
docs
throughout
this
release,
cycle
and
I
believe
naborong
is
going
to
be.
The
Emeritus
release
lead
as
well
to
be
helping
out
there,
which
is
great
one
important
note
that
I
want
to
kind
of
mention
here
for
all
folks
who
maybe
have
missed
the
announcement
specifically
for
enhancements.
A
Starting
with
this
release,
the
we're
replacing
the
we
as
the
you
know,
General
project
is
replacing
the
enhancement
Google
sheet
that
was
previously
used
and
had
a
lot
of
feedback
shared
about
it,
specifically
with
the
GitHub
project
board,
which
I've
Linked
In
the
which
I've
Linked
In
the
agenda.
A
Now,
unless
you
are
a
Sig
lead,
they
should
actually
affect
anything
with
regards
to
your
workflow
authors
of
caps,
which
is
a
kubernetes.
Enhanced
proposal
will
still
continue
to
do
the
work,
as
they
usually
do
when
they
opt
in
with
the
different
Sig
leads
that
they're
kept
is
associated
with
and
they've
actually
linked.
The
specific
slack
message
that
Grace
very
graciously
put
into
the
Steve
docs
channel
previously
to
give
us
some
more
information
about
that,
but
this
is
going
to
be
a
very
interesting
change.
A
Really,
a
big
welcome
change
has
been
a
lot
of
our
feedback
about
the
Google,
the
enhancement
Google
sheet
for
quite
some
time,
so
we're
excited
to
try
this
specific
new
approach,
which
is
great
I,
wanted
to
double
check.
If
anyone
had
any
questions
or
comments,
specifically
on
some
of
the
release,
the
new
release
information
before
we
move
on
to
our
Linux
part
of
our
agenda.
B
Enhancement
is
opted,
opt
into
release.
This
is
not
any
change,
but
the
defaults
for,
if
they
require
docs,
is
going
to
be
yes,
so
we
need
confirmation
from
enhancements
that
they
do
not
require
documentation,
changes
for
a
release,
something
that
we've
actually
implemented
in
the
past
several
releases,
but
just
want
to
reiterate
that
the
docs
Team
for
release
is
comprised
of
a
docs
lead,
also
foreshadows
it's
still.
It's
still
in
progress
of
picking
selecting
the
team
as
well.
B
So
when
that
team
is
formed,
they
also
since
the
docs
team
they
used
to
rely
on
the
spreadsheets.
Now
they
will
also
rely
on
a
view
on
that
GitHub
project
board,
which
has
not
been
comprised
yet
but
they're,
just
creating
some
filters
for
it,
so
so
the
so.
The
workflow
will
also
change
for
the
release.
Docs
team
as
well
to
use
the
the
same
GitHub
project
board
anyway.
B
So
that's
pretty
much
it
in
terms
of
workflow
changes
for
code
wise
for
for
kubernetes
everything
Remains,
the
Same
it
just.
This
is
just
how
the
only
changes
from
Sig
leads
opting
into
a
release.
Instead
of
going
with
the
spreadsheet
going
with
the
skidup
project
board,
and
so
that's
the
only
thing-
that's
actually
changed
and
there's
later
on,
there's
going
to
be
some
automation
created
for
it.
So
that's
about
it.
A
Perfect
thanks
very
and
I
know:
we've
got
also
actually
one
of
our
release,
Shadows
also
on
the
call
Nate
congrats
lots
of
a
bit
more
shadowing
for
you
to
do
this.
This
cycle,
but
yeah,
really
great
I,
think
the
the
project
Hub
I
mean
the
sorry.
The
GitHub
project
board
idea
is,
is
great.
I
really
hope
it
works
out.
Long
Time
Coming,
great
thanks
Ray.
A
What
we'll
do
is
we'll
move
on
now
to
the
rest
of
our
agenda,
and
we've
got
a
couple
of
issues
in
PR's
to
address
here.
So
I
can
see
in
the
dish.
You've
actually
put
something
here
as
a
an
issue
to
take
a
look
at.
Did
you
want
to
quickly?
Let
us
know
what
it
is
that
you're
you're
you're
chatting
about
here
with
this
up
here.
C
Yep
I'm
already
one.
A
Yes,
we
can
hear
you
we've
just
come
up
to
the
pr
that
you've
added
on
the
agenda
now
just
wanted
to
check
out.
What
did
you
wanted
to
chat
about
here?.
C
Okay,
so
the
basically
the
the
spear
actually
solves
the
issue
to
install
the
strips
for
the
to
modify
the
steps
to
install
the
containerdy.
Basically,
there
were
a
lot
of
changes
suggested
when
this
PR
was
raised,
but
at
the
end
it
feels
like
there
can
be
more
changes
which
can
be
enhanced,
although
the
LG
Team
tag
has
been
added,
but
still
I
would
like
to
take
some
suggestions
from
the
higher
authorities
on
what
are
the
further
changes
that
can
be
put
else.
C
We
can
hold
this
PR
for
now,
or
we
can
look
at
at
it
after
sometimes
that
is
what
the
basically
the
motive
of
freezing
this
issue
was
there.
A
So,
just
to
confirm
you're
wanting
to
get
information
from
folks
in
the
room
here
today
about
what
other
changes
could
possibly
be
added
to
the
condemnity
steps
that
you've
added
here
with
this
PR
is
that
correct.
B
Yeah
there
was
a
common
address
that
was
made
back
in
July
on
this
PR
about
adding
a
third
party
warning
here
and
so
that
I
think
that's
a
good
suggestion
as
well.
So
that
was
made
by
one
of
my
one
of
the
sigdocs
coach
hairs
because
it
is
King,
it
is
container
D.
It's
doll
steps,
it's
a
link
out
to
another,
not
the
coolness.o.d
documentation,
but
it's
actually
linking
to
another
party's
documentation.
A
Right,
yep
completely
agree
there.
For
those
folks
who
aren't
aware,
the
idea
of
a
third
party
warning
is
when
we
have
to
give
warnings
to
folks
who
are
reading
our
documentation
that
we
are
actually
referring
to
outside
products
or
outside
docs
that
aren't
actually
part
of
the
kubernetes
project,
and
that
is
the
kind
of
blanket
rule
that
we
have
throughout
a
lot
of
the
kind
of
third-party
information
that
we
give
out
in
the
kubernetes
docs.
A
So,
given
that
this
is,
as
Ray
mentioned,
linking
to
container
D
documentation,
which
has
no
nothing
to
do
with
the
kubernetes
project,
particularly,
we
would
need
to
put
that
warning
there
for
our
readers,
specifically.
B
And
going
back
to
the
issue,
the
issue
was
requested
to
actually
place
to
actually
add
the
individual
steps
to
container
to
install
the
energy.
But
we,
of
course,
can't
do
that.
We
can
link
out
to
the
to
the
containerdy
side,
which
we
already
do
so
it's
so
so
I,
don't
know
of
this
issue.
B
I
know
this
issue
has
been
triage
accepted,
but
I
don't
know
if
we
could
actually
complete
this
issue
as
the
person
who,
as
the
author
requested
it
to
be
fulfilled,
since
it
is,
goes
beyond
the
scope
of
the
documentation
sites.
B
A
Great
I
was
about
to
say
that
we,
we
can
probably
add
the
feedback
to
the
original
issue,
to
kind
of
indicate
where
that
should
be
now
which
natish
hopefully
should
help
you
with
the
further
information
on
the
pr
that
you'll
need
to
be
able
to
add
things
further.
So
that's
great
thanks.
Thanks
Dad
thanks
Ray
any
other
questions
or
comments
on
this
specific
PR
and
the
containerdy
instructions.
A
All
right,
thanks
Ashish,
for
bringing
that
to
our
attention.
That's
great!
Moving
on
to
the
next
PR,
that's
been
added
in
Abby.
D
Hello
long
time
no
chat
for
all
of
you.
Hello
I
was
wondering
about
the
localization
cap
that
we
had
originally
opened
to
to
formalize
the
the
sub
project.
We
went
a
different
route
and
we
do
we
did
formulas
the
sub-project
internally
within
sigdocs.
D
Do
we
still
need
this
PR
for
the
cap,
I'm,
not
sure
what
else
we
needed
to
do
on
it.
Natalie
I
know
you
had
opened
it,
but
if
there's
anything
you
want
me
to
take
a
look
at
or
whatever
just
wanted
to
open
it
up
and
see.
If
we
still
needed
this
cap
or
not.
A
Yep
great
great
cool,
just
just
a
few
context
of
folks.
There
are
a
couple
of
ways,
different
ways
that
you
can
create
sub
projects
in
the
kubernetes
in
the
kubernetes
project
overall,
and
something
like
the
localization
subproject
was
seen
as
possibly
needing
a
kit,
but
it
turns
out
that
that
wasn't
really
the
way
you're
around
us
formalizing
that
project
specifically.
A
So
what
we've
done
in
seek
docs
is
we
went
about
with
a
lazy
consensus
by
giving
information
to
our
community
linking
information
about
our
desire
to
create
the
localization
subproject
and
having
our
tech
leads.
Generally
be
a
okay
that
that
changed.
So
do
we
need
the
company
more?
A
My
simple
answer
would
be
no,
but
I'm
not
sure
if
there
is
a
way
to
kind
of
I
mean
just
closing,
it
would
still
keep
it
in
posterity
there
as
it
existed
and
that's
a
kind
of
a
relic
there,
but
I.
My
my
general
answer
would
be
like.
No,
we
don't
need
it
any
longer.
E
A
I,
like
that,
a
lot
and
so
I
think
Abby
I
just
saw
earlier,
although
unfortunately
I
haven't
gotten
to
it
yet,
but
we're
doing
a
couple
of
changes
into
our
FC
docs
Community
documentation,
operating
owners
files
Etc.
So
maybe
what
we
can
do
is
once
we
finish
that
work
Abby.
We
can
link
to
those
updated
changes
when
we
close.
D
Okay,
that
sounds
perfect.
Thank
you
for
that.
I've
been
like
you
mentioned,
I've
been
trying
to
get
through
updating
the
the
community
area
also,
so
that
I
think
that
makes
perfect
sense.
So
now
we
have
an
action
plan
and
maybe
I
can
write
a
comment
on
the
issue
or
the
pr
for
the
cap,
so
we
know
kind
of
what
we're
going
to
do
going
forward.
Okay,
perfect.
Thank
you
great.
A
Thank
you
and
any
other
comments
there
before
we
move
on
to
some
of
our
discussion
points.
F
I
I
have
a
question,
so
maybe
I
didn't
catch
up
real
quickly,
but
this
is
a
pull
request
based
on
the
cap.
So
is
this
content
going
to
go
into
the
docs
or
is
this
stuff?
That's
just
gonna
go
away
when
the
kept
goes
away.
A
A
The
kind
of
background
history
of
the
of
the
of
why
we
wanted
the
localization
localization
subproject,
perhaps
not
but
it'll
just
be
the
pr
will
be
closed.
Hence
that
information
will
still
be
there
so
got.
A
No
problem,
thanks
for
asking
all
right,
I'm,
just
going
to
catch
up
on
a
couple
of
notes,
Here
in
our
in
our
in
our
agenda
here
for
for
this
specific
point,
but
with
that
we'll
go
on
to
the
first
parts
of
our
discussion
points
there
and
the
tischware
over
to
you
I
believe
we
already
have
a
comment
here
from
Tim,
but
please
handing
over
the
mic
to
you.
C
Oh,
the
thing
was:
I
was
learning
darker
from
for
the
very
first
time
and
that's
when
I
came
across
the
docker
file,
so
I
had
this
question
for
the
members
like
we
had
this
Huber
server
as
well,
which
we
used
to
run
the
website
locally.
I
wanted
to
mention.
One
thing
is
like:
can
we
use
a
Docker
for
months
in
order
to
build
the
website
as
well.
E
I
thought
that
I'm
just
checking
it's
been
a
while,
since
I've
looked
at
the
docker,
we
had
at
one
point
instructions
on
I,
think
I
think
we
were
sort
of
container
agnostic
there
were.
There
were
instructions
on
how
to
run
the
website
containerized.
If
that's
not
currently
working,
then
we
should
open
an
issue
as
to
they
didn't
say
it's
it's
it's
it's
it's
broken,
but
the
last
last
time
I
checked
it
in
Italy.
This
was
a
few
months
ago.
We
did
have
those
instructions
on
the
in
the
readme.
E
On
on
on
the
getting
started
in
the
getting
started
section
there
and
on
how
to
get
things
up
and
running.
There's
there's.
E
There's
running
it
that.
D
E
Think
there's
also
a
last
I
checked.
It
was
like
a
cloud
version
as
well,
but
if
that's
not
currently
working,
please
do
open
an
issue.
A
Yeah
definitely
I
just
I
added
in
the
chat.
The
link
to
I
believe
what
you
were
speaking
about.
Nate
the,
how
we
kind
of
get
your
preview
working
locally
and
in
our
instructions
on
the
getting
started
guide.
We
do
use
Docker
as
our
default
container
engine
as
like
the
example
there
that's
given,
but
the
idea
is
that
we
do
show
in
those
instructions
how
to
run
Hugo
in
a
container
so
that
you
don't
actually
have
to
install
either
completely
locally
so
natish
just
checking.
A
C
Just
as
right
before
this
meeting,
I
tried
to
run,
the
I
tried
to
run
the
website
locally
using
the
docker,
but
it
actually
showed
me
the
error
in
in
running
the
website
locally.
So
that
is
one
of
the
reason
as
well.
I
put
this
question
in
the
agenda
like
is
there
any
way
by
which
we
can
run
the
website
locally?
If
it
is
not
there,
I
can
I
I
think
like
it
is
a
better
way.
We
can
add
a
in
the
readme
file
on
how
to
run
your
website
locally
using
the
docker.
C
B
Should
not
be
specific
to
Docker,
we
have
to
be
container
and
runtime
agnostic.
We
cannot
have
specific
instruction
just
for
Doc.
We
actually
do
have
it
in
the
documentation,
using
Docker
as
an
example
as
a
default
container
engine,
but
we
should
not
have
very
specific
Docker,
Daemon
or
Docker
commands
in
the
readme.
It
should
be
container
runtime,
I.
E
Agree-
and
we
should
also
make
sure
that
the
instructions
that
not
only
just
linked
are
the
same
as
the
instructions
that
are
in
the
the
readme
repo
because
they're
they
might
have
drifted.
A
Great
thanks,
hey
folks,
I'll
link
to
the
that
specific
how
to
run
your
previous
locally,
also
now
agenda
in
our
agenda
doc
here,
so
that
we've
got
a
reference
to
that
as
well,
but
yeah.
Definitely
if
we
should
definitely
check
those
specifically
the
same
name.
I,
agree
and
I
can
add
that
as
an
action
item
for
for
us
to
take
a
look
at
thanks.
A
Already
and
the
fish
we
are
coming
back
to
you
for
the
last
discussion
points.
So
please
take
it
away.
A
C
So
I
I
saw
this
messaging
listening
docs.
It
was
related
to
the
one
of
the
tools
that
we
use
basically
to
understand
the
file
location
of
a
text
that
is
honed
and
there
were
a
specific
tool
as
well,
which
was
mentioned
so
I
wanted
to
know
if
there
are
further
tools
which
can
be
used
for
the
enhancing
your
productivity
when
contributing
to
gates.
For
example,
we
have
these
two
like
Hoon
right,
which
can
be
used
to
understand.
C
B
There's
a
tool
for
reviewers,
it's
the
governator
or
it's
actually
for
anyone
in
the
kitchen
or
organization.
It's
the
we
call
the
gubernator,
but
it's
also
I
think
it's.
If
you
go
to
there's
a
short
one
to
I,
think
this
Kate
slot
reviews
will
also
send
you
there
as
well.
So
if
we
go
to
it's,
not
review
I'll
put
it
I'm,
putting
this
in
the
chats.
I'm!
Sorry
not
chatting
the
agenda
yeah.
B
So
those
just
kind
of
shows
you
what
PR
stuff
currently
on
your
that
should
be
on
here
that
you
should
be
watching.
C
B
Pay
attention
to
or
that
you
were
assigned
to
or
you've
been
or
that
you
wrote
so
those
are
or
that
you're
currently
reviewing.
A
Yeah
specifically,
the
kubernator
is
something
that
a
lot
of
us,
PR
wrinklers
use
to
keep,
keep
our
eyes
on
a
things
that
we've
been
assigned
tagged
in
that
are
part
of
that
we're
part
of,
but
also
to
be
able
to
kind
of
push
through
reviews
that
are
that,
are
you
know,
obviously
age.
Let's
say
going
through
so
yeah.
The
gubernetes
is
something
that's
super
useful.
A
Any
other
tools
that
people
know
about
that
they
wanted
to
mention
I,
think
the
kubernetes
is
just
the
main
one
that
I
use.
So
thanks
very
for
mentioning
it.
That
would
have
been
my
that
would
have
been
my
Edition.
G
I
just
wanted
to
mention
when
I'm
working
with
Adam
I
usually
have
the
repo
as
a
project.
Adam
is
an
editor
and
what
I'm
seeing
is
not
specific
to
Adam.
Really
it's
most
editors
will
allow
you
to
specify
a
project.
Then
you
can
do
a
search
within
the
project
for
a
specific
string
and
usually
you'll
have
results
immediately,
and
you
won't
have
to
step
out
of
your
workflow
in
the
editor
to
go,
use
a
browser
search.
That's
another
way
of
doing
to
doing
another.
C
G
It
looks
like
we're
at
the
at
the
open
end
of
the
conversation
I
just
wanted
to
throw
in
the
Hindi
localization
launched
this
past
week
and
so
kubernetes
docs
are
now
online
for
over
a
half
billion
of
potential
readers,
very
large
language
groups.
A
Yeah,
that's
great
thanks.
So
thanks
thanks
so
much
for
mentioning
we,
we
are
now
at
the
discussion
section.
So
thanks
so
much
yeah
huge,
huge
congratulations
to
the
to
the
folks
working
on
the
Hindi
localization
massive
effort
over
the
last
year,
I
would
say,
or
even
a
bit
longer,
that
a
lot
of
the
folks
have
been
working
on
that.
A
So
a
huge,
huge
achievement,
huge
achievement
as
well
generally
for
just
our
push
for
a
lot
more
localization
that
also
amongst
kind
of
the
new
official
sub
project,
which
is
great
so
yeah,
big,
big.
Congratulations
to
to
all
the
folks
involved.
All
the
folks,
you
know
tune
from
the
sidelines
and
pushing
a
lot
of
the
work
that
needs
to
happen
there.
It's
I
know
yourself
from
friend
a
lot
of
other
people
on
the
call
were
also
involved.
So
it's
really
great
awesome.
Awesome
work
for
the
team.
A
And
with
that
we've
got
again
as
mentioned,
we
are
at
the
proportion
Airline
meeting
where
we
have
open
space
if
everyone
anyone's
got
any
other
discussion
points
or
things
I'd
like
to
bring
up
as
we've
come
to
the
end
of
our
agenda.
Anyone
else
with
any
other
topics
that
they'd
like
to
share.
G
E
A
C
A
Not
there
to
you
the
people,
but
yes
any
who,
as
long
as
you
join
the
cdox
mailing
list,
you
get
right
access
to.
E
A
I
yeah
I
do
see
I
do
see
an
anonymous
user
in
there,
so
that
could
be.
That
could
be
you,
okay,
great
so
yeah
for
those
folks.
G
A
Are
new?
You
do
need
to
join
the
Sig
docs
mailing
list
to
get
access
to
our
agenda,
then
you'll
be
able
to
freely
add
to
it
every
two
weeks
when
we
have
our
meetings,
we
myself
and
Ray
have
ndbo
for
that
APAC
meeting.
We
always
remind
folks
to
add
things
to
better
gender
too,
so
we'll
we'll
consistently
link
to
it.
It's
also
linked
in
our
seek
docs
channel
in
the
bookmark
section
as
well
for
folks
who
need
a
quick
reference
all
right,
any
last
additions
to
the
meeting
today.
G
Sorry,
yes,
when
you
say
add
yourself
to
the
list,
do
you
mean
the
kubernetes
sigdocs
at
googlegroups.com.
A
A
That's
the
one
and
that's
the
same
list
that
should
then
give
you
the
invites
to
all
the
different
calendar
events
in
the
seek
docs
agenda
as
well.
So
that's
our
new
contributor
meeting,
this
big
docs
meeting
that
happens
bi-weekly
as
well
as
our
APAC
monthly
meetings
as
well.
Throughout
your
pick
votes
and
the
Sig
docs
blog
meeting,
which
I
believe
is
likely
going
to
be
looked
at
in
terms
of
timing,
because
the
timing
isn't
great
for
some
of
those
folks
but
yes,
great.
Thank
you
thanks.
A
Thanks
for
adding
thanks
for
adding
that
there
I
appreciate
it.
I'll.
Add
that
to
the
agenda
as
well.
Alrighty
looks
like
we've
come
to
the
end
of
our
agenda
thanks
so
much
everyone
for
joining
really
really
appreciate
a
lot
of
the
questions,
keep
them
coming
so
that
we
can
help
new
and
season
contribute.
As
a
like
again,
a
big
huge
congratulations
to
the
folks
working
on
the
Hindi
localization,
really
great
achievement
and
really
welcome
to
the
new
release.
A
1.26
we've
got
a
lot
of
fun
over
the
next
four
months
ahead
of
us,
our
three
months,
three-ish
months
ahead
of
us,
because
there'll
be
a
holiday
period
too,
where
it's
a
little
bit
quiet
towards
the
end
of
the
year.
So
I,
just
as
a
note
for
everyone.
A
Alrighty
thanks
folks
shop
at
Sweet.