►
From YouTube: K8s SIG Docs Meeting for 20230613
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
folks,
I've
just
linked
the
agenda
in
the
chat
I
want
to
welcome
everyone
to
this
meeting,
Edition
13th
of
June
2023
to
seek
docs.
This
is
a
community
meeting
for
the
special
interest
group
that
owns
the
documentation
and
the
website
of
kubernetes,
and
we
have
these
meetings
every
two
weeks,
barring
certain
events
such
as
kubecon
Europe
and
kubecon,
North,
America,
and
also
over
certain
major
holidays
as
well
big
welcome
to
everyone.
My
name
is
Natalie,
my
pronouns.
Are
she
her
and
I'm
one
of
the
coaches
of
cdocs?
A
We
also
have
Ray
lahano
on
the
call
as
well
who's,
our
other
co-chair,
who
will
be
taking
notes
today.
Thank
you
so
much
Ray
and
Divya.
Our
final
co-chair
is
it's
a
little
bit
late
for
Divya
to
join
these
meetings
regularly,
however,
divio
usually
hosts
our
APAC
meetings,
which
are
held
every
month
on
the
fourth
Wednesday
of
the
month,
all
righty.
If
we
are
going
to
jump
into
the
agenda,
the
first
thing
I
want
to
mention
is
a
couple
of
things:
I'm
just
going
to
actually
quickly
share
my
screen.
A
There
we
go
so
that
everyone
can
see
the
agenda
there
Fab
so
a
couple
of
things
to
mention
for
Sig
docs.
Firstly,
this
is
a
as
it
is
a
kubernetes
meeting.
We
abide
by
the
kubernetes
covert
of
conduct,
so
these
kinds
of
meetings
here,
and
also
virtually
in
a
lot
of
our
slack
rooms
and
slack
channels,
which
generally
means
we
want
you
to
be
respectful
to
one
another.
A
But
if
you
have
any
issues
that
you
think
could
be
a
code
of
conduct,
issue
or
violation,
you
are
absolutely
at
your.
It
is
at
your
disposal
to
contact
the
code
of
conduct
committee.
You
can
email
them
at
conduct,
kubernetes.io,
it
is
anonymous.
A
They
will
reach
out
to
you
and
keep
your
anonymity
and
non-annuity
if
you
wish-
or
if
you
don't
wish
to
that's,
okay,
but
anything
that
you
say
to
them
is
all
in
confidence
and
reaching
out
to
them
doesn't
mean
that
you're
filing
a
report
just
to
talk
about
things
is
also
completely
okay,
so
I
just
want
to
put
that
out
there
for
anyone
encountering
anything
either
happening
in
this
meeting
or
others
that
you
attend
as
part
of
the
kubernetes.
B
A
All
right,
sorry,
I've
been
collaborating
a
lot,
so
I
want
to
start
off
today's
meeting
by
first,
hopefully
welcoming
anyone
who's
new
to
either
sigdocs
or
kubernetes,
or
this
meeting
particular.
If
you
wanted
to
call
out
your
name
and
say
hi
and
tell
us
a
bit
about
yourself,
Now's
the
Time.
C
See
if
I
can
unmute
is
the
first
challenge:
hi
I'm
Matt,
moore'sma
I'm,
just
joining
because
I'd
like
to
help
out.
However,
I
can
and
I
haven't,
come
to
see.
Docs
before
I
have
been
contributing
to
kubernetes
for
several
years.
C
I
work
in
cluster
API,
specifically
on
Azure
stuff,
but
I
took
a
step
back
recently
and
thought
about
kubernetes
as
a
whole
and
where
I'd
like
to
contribute
and
I,
think
we
do
a
great
job
with
the
docs
and
I'd
like
to
help
out
that's
as
far
as
I've
gotten
with
my
planning.
A
That's
that's
awesome,
really
really
great
to
have
you
here.
We
also,
we
always
always
up
for
people
wanting
to
help
us
with
docs.
As
you
know,
it
takes
a
village.
So
it's
really
really
awesome
that
you're
willing
to
help
out
thanks
so
much
for
welcoming
or
for
coming
in
and
introducing
yourself
and
yeah
welcome,
welcome
to
docs
and
then
we've
got
Michael.
D
Hey
everybody,
my
name
is
Michael
Levan
and
I
am
actually
on
the
1.28
release
team
for
Doc,
so
I
figured
I
should
probably
join
these
meetings
for
the
obvious.
So
thanks
so
much
for
having
me
appreciate
it
great.
A
Awesome
thanks
so
much
Michael
for
joining.
We
do
love
if
the
docs
either
lead
or
Shadows
join
our
meetings.
So
that's
so!
Thank
you
so
much.
We
are
for
folks
who
are
not
aware
every
three
times
a
year
with
kubernetes,
with
the
releases
that
we
have
docs
is
a
big
integral
part
of
those
releases
in
terms
of
the
new
features
being
put
out,
features
graduating
from
one
stage
to
another
or
a
very
big,
important
things
that
we
need
to
announce
via
docs.
A
The
docker
shim
removal
is
one
example
Registries
another
example.
Catacota
removal
and
other
examples
so
Michael
great
to
have
you
we
are.
We
always
try
and
do
a
small
release,
update
and
so
I
may
actually
give
that
part
over
to
you,
given
that
you're
one
of
the
1.28
Team
but
Ray
is
also
here
and
and
will
here
also
to
support
on
the
on
the
on
the
release
team
update
side.
So
thanks
so
much
anybody
else.
That
wants
to
say
hello.
B
Hi
I
think
I
should
so
I'm
Maureen
I
have
been
to
these
meetings
a
while
back,
but
I
haven't
shown
up
in
a
while.
My
pronouns
is
she
her
and
I'm,
currently
an
approver
for
the
Portuguese
documentation,
so
I
just
joined
today,
because
I
have
a
couple
of
questions
on
the
brothers.
A
Great
awesome
welcome
back
Maureen
great
to
have
you
as
always,
and
if,
if
for
some
reason,
you
can't
attend
some
of
these
meetings,
that's
totally.
Okay,
we're
also
always
cool
to
have
questions
in
the
big
chat
and
this
like
channels
as
well.
A
Although
I
know
as
of
late,
we
haven't
been
very
good
at
answering
a
lot
of
those
questions,
because
a
lot
of
us
have
been
in
and
out
with
the
different
different
different
tasks
but
great
to
have
you
back
again
just
checking
if
we've
got
any
last
people
that
wanted
to
say
hi
and
introduce
themselves.
A
Great
so
young,
thank
you
so
much
for
saying,
hi!
Yes,
we've
got
you
down
there
with
them
for
shadowing
there.
So
thank
you
again.
Pr
wrangling
is
an
important
but
sometimes
thankless
job.
So
it's
definitely
something
that
us
as
approvers
and
reviewers,
try
to
do
to
make
sure
that
a
lot
of
our
contributions
for
docs
and
PR's
that
are
that
are
put
in
are
kind
of
moving
through
the
pipelines
that
we
can
get
as
much
done
as
possible,
so
great
to
see
that
you're
shadowing.
A
Hopefully,
hopefully,
you
learn
a
lot.
So
thanks
thanks
for
saying
hi,
it's
a
great
segue
to
go
into
our
next
part
of
our
agenda,
which
is
the
pr
Wrangler
updates
and
reminders
for
those
who
don't
know
and
who
are
new.
We,
the
role
of
PR
Wrangler
here
in
the
cdocs
group,
is
something
that
we
have
where
we
weekly
have
a
an
agenda
which
is
linked
under
PR
Wrangler
shifts
there
on
the
agenda
for
this
meeting,
where
they
were
an
approver
or
a
reviewer.
A
Will
each
week
kind
of
be
tasked
to
move
through
the
PRS
to
try
and
get
as
many
either
approved,
reviewed
or
possibly
closed
if
that's
required
each
week,
so
that
we
can
actually
get
those
contributions
under
a
decent,
manageable
number?
We
do
try
lately
with
the
amount
of
localizations
that
we
have.
We
do
try
and
get
that
number
to
around
150.
A
We're
kind
of
failing
in
that
lately,
I
will
say:
there's
a
lot,
there's
a
lot
to
do,
and
so
trying
for
folks
who
are
interested
in
learning.
We
do
have
a
shadow
program
that
sriram
has
just
mentioned,
where
you
can
just
contact
any
of
us
leads
or
any
of
the
approvers
and
reviewers
that
are
on
that
schedule
and
just
ask
to
Shadow
and
learn
what
they
do.
A
I
want
to
note
really
quickly
here
that
the
gubernator
has
been
kind
of
shut
down
which
I
know
for
our
PR
Wranglers
was
a
tool
that
we
used
very
regularly
to
help
us
out
with
that.
So
I'm
sure
there's
going
to
be
an
interesting
time
for
us
to
figuring
out
how
we're
going
to
keep
up
with,
what's
assigned
to
not
only
ourselves
but
to
other
approvers
in
Docs,
but
I
wanted
to
quickly
go
through
for
the
approvers
for
the
next
couple
weeks.
A
This
week's
current
Wrangler
is
Divya
and
she's
being
shuttered
by
Rita
Singh
and
then
next
week's
Wrangler
is
Nate
Waddington
and
srivam,
as
already
mentioned,
will
be
shadowing
Nate
and
then
the
following
week
we're
adding
an
extra
week's
Wrangler
kind
of
list.
A
There
is
Anna,
young
who's
have
been
a
previous
docs
lead
for
release
before
and
so
for
all
any
Wranglers
or
any
approvers
and
reviewers
on
the
call
just
make
sure
you're
checking
your
shifts
so
that
you
can
jump
in
and
do
that
work
and
if
you
can't
jump
in
if
you've
got
different
things
that
come
up,
we
are
humans
with
lives.
After
all,
you
can
always
let
us
know
in
the
in
the
seed
docs
maintainers
Channel,
and
we
can
try
and
get
your
shift
covered
as
well.
A
D
Sure
yeah,
let
me
just
actually
open
up
slack,
really
quick,
because
something
just
went
out
today
that
I
was
trying
to
approve,
but
I
did
not
have
approver
ability
to
be
able
to
approve
it.
So
let
me
see
here
there
was
one
for
okay.
Actually,
this
was
actually
just
something
to
sink
the
the
dev
hyphen
1.28
Branch
with
main
so
that
went
out
and
was
synced
up
today.
D
Oh
no,
wait!
I'm!
Sorry!
Actually,
I
am
apologies.
Give
me
one
sec,
oh
no
yeah!
This
was
this
one.
Oh
no
yeah,
never
mind!
It
was
just
another
sync
to
from
the
dev
Branch
to
main.
That
was
about
it
other
than
that
I
think
we
just
got
our
kaps
assigned
so
we're
you
know
ultimately
just
looking
at
those
and
checking
the
documentation
and
doing
the
feedback
and
all
that
fun
stuff.
A
Okay,
great
I've
just
had
that
so
the
Kip's
now
being
assigned,
but
as
we
speak
great
okay,
thank
you
so
much
for
that
update
feel
free
in
future.
If
you're
attending
these
meetings,
Mike
or
any
of
the
other
doc
Shadows,
you
can
add
your
updates
directly
to
the
agenda.
If
you
like
to
with
the
different
points,
we
would
really
love
that
if
you
wish
to
add
that
as
well.
So
thank
you
thank.
D
A
F
Oh
yeah
I'm
typed,
thank
you.
I
was
trying
to
find
the
raised
hand
button.
So
I
did
it.
So.
Regarding
the
previous
topic,
I've.
D
F
A
Okay,
so
a
couple
of
things
there.
Firstly,
we
are
in
docs
super
open
to
unofficial
reviews
that
is
completely
okay
and
definitely
fine
to
do
so
in
terms
of
reviewing
feel
free
to
jump
in
and
give
your
review
perspective
on
certain
Piers.
It
doesn't
actually
matter
that
you
don't
have
the
let's
say
ability
to
add
certain
tags
like
lgtm
or
approve
having
an
unofficial
review
is
also
really
really
super
helpful.
A
So
the
answer
is
yes,
you
can
jump
in
and
review
in
terms
of
becoming
a
member
of
the
kubernetes
organization
to
have
that
possible
approval
power
or
should
I,
say
reviewer
power.
There
is
a
way
to
become
a
org
member,
which
is
having
submitted
five
PR's
and
doing
so
in
ensuring
that
you've
got
a
possible
sponsorship
from
folks,
let's
say
in
docs
that
would
approve
your
membership.
You
can
absolutely
Marcelo
do
that
where
you
put
the
call
out
in
the
seek
docs
Channel
asking
for
a
couple
of
sponsors.
A
I
know
there
will
be
a
couple
of
us
folks
here
in
the
meeting
that
would
be
willing
to
sponsor
you,
but
becoming
an
org
member
requires
around
five
PR's
that
have
been
emerged
into
the
submitted,
at
least,
but
definitely
mainly
merged
into
the
into
the
kubernetes
repository
and
then
and
then
get
you
started
on
org
membership.
A
Definitely
enough
yeah
I
would
definitely
I
can't
find
it
right.
A
Yeah
I
think
I
think
the
interpretation
of
significant
or
the
interpretation
of
small
differs
amongst
people
and
folks
being
able
to
look
for
sponsorship
is
also
something
that
kind
of
shows
that,
on
top
of
the
peers,
that
you've
submitted
you're
coming
to
meetings,
you're,
showing
consistency
in
terms
of
showing
up
and
that's
what
also
finding
sponsors
and
people
who
are
willing
to
sponsor
you
kind
of
advocates
for
as
well,
so
this
that
sponsorship,
plus
the
PRS
you
submit
and
will
surely
be
enough.
A
Okay,
thank
you
great,
no
problem
for
anyone,
I'm
I'm,
fortunately
unable
to
find
it
right
now,
all
your
yes
great,
we've
got
a
already.
You've
got
a
couple
of
folks
in
the
chat
Marcelo
who
are
already
willing
to
sponsor,
which
is
awesome
and
they'll
and
I
can
find
the
information
later
on
for
you
to
read
up
if
you,
if
you
needed
it
on
on
the
sponsorship
issue,
that
you
would
create
as
well
as
a
note.
Yes,
no
problem
as
a
note
on
that
two
months
ago.
A
That
process
isn't
immediate
our
GitHub
folks,
as
in
the
GitHub
Management
Group
and
the
kubernetes
community
group.
They
go
through
organ
memberships,
I
believe
once
a
week.
So
if
you
submit
it
maybe
a
few
days
but
just
know
that
people
would
be
working
on
it.
A
Right,
great
yeah,
sorry
that
I
didn't
see
you
raised
hand
before
because
of
my
sharing
screen
mode.
I
only
have
certain
enough.
A
number
of
pictures
on
my
screen
so
raised
hands
always
go
to
the
top
as
FYI
to
everyone.
For
me,
all
right
I
want
to
jump
over
to
now
the
issues
in
PR
section
and
unfortunately,
Diva
wasn't
able
to
be
here,
but
I
do
want
to
mention
something
that
she'd
like
to
bring
up,
which
is
our
new
contributor
Ambassador
role,
I've
linked
the
issue
there
31946..
A
This
is
a
role
that
we've
had
and
ask.
Sharma
has
been
fulfilling
that
really
great
and
we've
actually
asked
him
to
document
this
role
in
in
a
more
succinct
and
specific
format,
so
that
we
can
actually
bring
on
a
couple
more
new
contributor
ambassadors.
You
might
be
asking
what
this
is.
A
This
is
a
role
where,
every
month,
we
host
a
meeting
that
is
generally
geared
towards
mainly
towards
APAC
timing,
but
it
also
works
in
Europe,
because
the
meetings
at
around
11AM
for
most
European
time
zones
and-
and
this
is
geared
towards
welcoming
folks
who
are
new,
who
might
have
questions
who
just
need
help
and
guidance
and
who
are
interested
in
just
finding
out
from
a
seasoned
contributor
what
they
would
like
what
they
would
need
to
kind
of
get
their
contribution.
Journey
started.
A
We
are
looking
for
an
another
person
to
help
us
with
this.
We
don't
want
to
put
all
the
work
on
one
person
and
we
think
sharing
that
contributor
kind
of
Journey
and
and
mentoring
in
that
way
is
also
another
really
good
way
for
folks
who
are
becoming
regular
contributors
as
a
way
for
them
to
get
involved
in
another
impactful
way,
on
top
of,
let's
say,
reviewing
or
PRS
or
so
on,
and
so
in
the
issue
that's
linked.
A
There
feel
free
to
take
a
look
to
see
if
either
a
you're
interested
in
attending
any
of
those
contributor,
your
contributor
Ambassador
meetings
or,
if
you're
interested
in
possibly
taking
on
that
role,
you
can
either
speak
to
Ash
or
myself
Divya
already
to
find
out
more
about
it
and
what
that
would
fail.
A
But
at
the
moment
it
is
a
monthly
meeting
that
goes
for
30
minutes,
and
it
is
just
generally
looking
at
slack
to
possibly
monitor
for
questions
that
might
be
for
some
of
them
from
some
new
contributors
that
you'd
like
to
answer
any
questions
or
feedback
on
that.
E
We
can
ask
our
questions
in
the
linked
issue
right
regarding,
yes,.
A
No
worries
at
all
we're
currently
in
the
process
of
having
us
document
that
role
better,
so
that
for
folks,
who
are
definitely
interested
in
possibly
taking
up
in
a
co-lead,
Ambassador
role
and
they'll
have
the
information
there
of
what
the
expectations
are.
So
that's
the
step
that
we're
up
to
now.
A
All
right,
okay,
we'll
move
on
to
the
next
issue
in
PR
agenda
item
then,
and
Maureen
I'd
like
to
hand
it
over
to
you.
B
Sure
so
I
created
this
issue
just
this
morning.
This
is
about
the
adapted
tutorials.
We
had
some
tutorials
that
were
linking
to
color
Coda,
but
then
karakoda
was
discontinued,
so
what's
happening
right
now
is
that
the
code
blocks
in
those
pages
they
don't
look
quite
the
same
as
the
other
pages
that
we
have
in
markdown
and
I
was
just
wondering
what
would
be
the
right
place
to
start
a
discussion
about
how
we
can
make
those
pages
be
more
consistent
with
the
remainder
of
the
website.
A
Great
question
I
want
to
open
it
up,
I'll
be
talking
a
lot.
I
want
to
open
it
up
to
anyone
else
on
the
call
that
has
a
possible
answer.
There.
F
You
can
see
it
links
to
a
question
I
made
in
a
previous
meeting
about
if
we
have
templates
to
start
documentations
from
scratch,.
A
For
folks
who
aren't
aware,
catacota
was
a
free,
tutorial
site
offered
by
O'reilly
media
that
we
used
to
have
on
many
of
the
tutorial
pages
on
the
kubernetes
site
and
last
year
they
or
this
year
properly
actually,
but
they
basically
took
them
offline,
and
so
we've
had
to
remove
some
of
the
links
to
those
cataclyn
tutorials
that
they're
no
longer
online
and
available,
and
there
is
a
discussion
on
the
GitHub
discussions
area.
A
I'll
need
to
find
it
and
add
it
to
our
agenda
of
what
we
can
replace
catacota
with,
given
that
it
didn't
require
a
login.
It
didn't
require
your
email,
it
required
no
payment
and
we're
trying
to
possibly
find
a
solution
that
mirrors
that
old
experience
as
much
as
possible
for
for
new
users,
but
Lauren.
That's
a
great
question
of
how
we
can
start
that
discussion.
We
can
start
it
here
as
you
as
you've
clearly
attempted
to
do,
but
I
think
also
another
great
place
to
since
I.
A
I
think
is,
is
a
great
place
as
well
to
document
that
conversation
I,
think
it's
great
that
you
want
to
do
a
lot
more
in
terms
of
consistency,
because
that's
something
that,
with
reviewers
of
all
shapes
and
sizes,
that
we
have
it's
something
that
we
kind
of
like
a
bit
so
yeah,
that's
a
great
way
to
start
the
convo.
G
I
was
going
to
say
that
the
proposal
you
you
have
on
the
issue
with
the
with
the
pre-element
around
the
code
blocks.
It
looks
pretty
straightforward
and-
and
you
know
well,
I-
think
once
we
once
there's
a
PR
created
and
we
could
compare
visually
with
if
it's,
if
it's
consistent
with
the
other
pages
with
code
blocks,
that
should
be
pretty
straightforward
and
it's
also
a
good
thing
to
have
in
terms
of
good
first
issues,
if
it's.
G
If,
if,
if
that,
if
the
fix
turns
out
to
be
adding
that
pre
elements
around
the
code
box,
so
something
we
can
also
create
a
new
good
person.
Issues
for
as
well.
B
A
F
In
in
that
specific
case
of
karakora
tutorial,
it
seems
the
as
you
mentioned,
the
Technologies
has
been
retired,
you
know
the
obsolete,
is
it
worth
putting
effort
in
something
and
it's
not
no
longer
relevant.
F
A
A
So,
what's
being
retired
is
the
actual
access
to
those
tutorials
itself.
A
So
we
have
links
that
now
no
longer
work
on
our
that
that
take
it
that
take
our
users
to
a
page
that
they
can
no
longer
access
and
taking
that
content
away
and
then
reformatting
the
code
block
so
that
they
look
similar
to
other
pages
of
the
site.
That
don't
include
a
tutorial
basically
is
is
the
what
we're
doing
there.
So
it
still
is
relevant
to
definitely
do
because
we
need
to
take
away
something
that
no
longer
works.
B
The
tutorial
remains,
they
have
been
just
repurposed,
so.
C
F
Yeah,
as
for
consistency,
I
asked
in
a
previous
meeting
if
we
have,
if
there
are
template
a
library
of
templates
where
you
can,
if
you
are
a
contributor,
you
can
use
them,
but
I
think.
The
reply
at
that
moment
was
that
that
you
don't
have
a
library
of
templates,
so
I
wonder
how
people
start
documentation
from
scratch,
which
is
just
copy
paste
and
existing
one
or
the
Acer.
As
skeleton
like
from
a
library
of
templates,
you
can
be
used
to
when
you
had
to
write
from
scratch.
A
Yeah
I
believe
from
the
last
meeting.
The
answer
is
there?
Isn't
any
templates
necessarily,
we
do
often
kind
of
use
a
pre-existing
page,
let's
say
to
Let's
to
generally
start
from
scratch.
There
is
Ray.
You
may
want
to
correct
me,
but
there
is
a
general
template
for
how
we
want
specific
features
when
they
are
graduating,
for
example,
to
be
documented
and
how
that
happens.
A
G
Yeah
we
do
have
a
style
guide
that
also
is,
should
be
adhered
and
in
content
guide
as
well
to
help
guide
the
Page
information.
A
Great
any
more
comments
on
that
or
the
tutorial
Pages
issue
that
Maureen
put
together
today.
H
H
A
C
A
We're
a
bit
Kinder
there
in
terms
of
pushing
certain
work
like
that
yeah,
but
any
I
will
say
that
if
you
find
in
a
localization
page
any
of
those
links
that
are
no
longer
working
and
it
may
not
be
a
localization
that
you're
necessarily
familiar
with.
But
it's
a
link
removal.
Let's
say
that
doesn't
necessarily
need
to
be
done
by
someone.
D
A
E
A
A
B
So
on
that
note,
I
have
been
wondering
if
we
could
I
don't
know.
If
standardizing
is
the
correct
word
here,
but
if
we
could,
when
major
changes
happen,
just
opening
like
an
umbrella
kind
of
issue
like
the
patch
did
recently,
because
that
helps
at
least
for
me
as
an
approver
for
the
Portuguese
localization
that
helps
catch
my
attention
when
something
is
required
to
be
done
and
I
I
did
not
notice
that
the
catacono
tutorials
have
had
been
removed
from
the
main
website
until
the
umbrella
issue
came
about.
B
So
I
think
I
mean
this
is
most
perplexive
just
as
a
localization
person,
but
perhaps
if
we
could
like
Define
a
process
where
we
create
an
issue
or
another
mechanism
just
to
call
attention
from
the
localization
teams,
it
could
be
useful
for
us.
A
Yeah,
definitely
what
I
would
what
I
would
say
is
that
we
shouldn't
make
a
decision
for
localization
folks
in
this
meeting.
They've
got
their
own
localization
meeting
that
that
kind
of
that
happens
in
two
but
I
think
what
could
be
really
great
is
actually
putting
that
on
the
agenda
for
next
time
and
I'm
happy
to
jump
in
and
help
do
that
so
that
we
can
discuss
hey.
Is
this
going
to
be
a
a
useful
process
thing
because
introducing
a
new
process?
A
I
think
is
always
good,
but
someone
needs
to
own
that
in
order
for
that
tool
to
to
to
be
successful
and
I'd
want,
the
localization
leads
involved
so
that
they
know
that
that,
if
that's
wanted,
that's
going
to
be
an
expectation
of
something
that
would
be
required,
but
yeah
great
I
think
that's
a
great
suggestion
for
sure.
G
There's
also
a
current
label.
That's
used
called
refactor.
It's
helped
in
filter
out
their
label,
a
PR
with
any
like
refactoring
changes
on
a
on
a
current
page,
so
that
localization
is
my
I
need
to
update
that
they
might
need
to
update
that
page
in
the
future.
So
that's
also
a
label.
That's
also
helpful.
A
Great
thanks,
Ray
thanks
Maureen
I'll,
letting
you
catch
up
with
notes
there,
but
I'm
going
to
move
on
to
our
next
topic.
So
thanks
so
much
Ray
and
Maureen
there
and
Marcelo
going
on
to
the
questions
and
discussion
points
area.
Now
that
we've
moved
on
from
that
part
of
the
agenda
and
localization
is
another
great
segue.
A
I
wanted
to
notify
folks
here
that
a
couple
weeks
ago
we
put
out
information
via
the
sick
talks,
mailing
list
that
we
have
a
new
co-lead
nomination,
Seiko
son
who's,
our
the
Korean
localization
lead,
and
he
is
stepping
up
to
help
co-lead
the
whole
localizations
of
project.
Alongside
Abby
and
McCarthy,
the
current
leader
of
the
sub
project
with
Brad
Topol
stepping
down.
A
We
wanted
to
make
sure
that
we
were
sharing
the
load
of
that
work
across
a
couple
of
folks,
I've
been
stepping
in
as
I
can,
but
Circo
has
been
doing
a
really
great
job
and
so
he's
been
nominated
to
take
on
the
co-lead
role.
Today
is
actually
the
last
day
of
the
lazy
consensus
time
period
that
we
set,
which
was
two
weeks,
and
so
what
I
will
do
after
today.
A
Sometime
this
week,
I
will
put
in
the
pr
to
merge
the
changes
of
Circo
being
the
new
co-lead,
which
also
means
not
much
else.
Will
change,
because
he's
already
been
leading
a
lot
of
the
localization
meetings.
He's
been
doing
a
lot
of
helpful
things
recently
for
the
Russian
localization,
but
across
a
lot
of
the
different
teams,
and
what
I
would
love
to
do?
Sioko
can't
be
here
today
for
this
meeting
as
the
time
zone
is
not
exactly
it's
not
exactly
perfect
for
him
being
in
Korea.
A
But
what
I'd
love
to
do
is
have
him
say,
hi
across
the
localization
groups
and
know
that
they
can
have
another
contact
in
terms
of
localization
issues
and
questions
as
well.
So
you
know
here's
Yoko,
but
if
you're
watching
the
recording,
congratulations
just
want
to
extend
that,
but
if
anyone
does
have
any
plus
ones
or
questions
on
that,
you
do
have
until
the
end
of
today
in
the
West
Coast
time
zone,
to
add
in
any
possible
comments
or
questions
on
that
nomination.
A
All
right,
gonna,
move
on
to
the
next
agenda
item
here
that
I've
put
up
the
contributor
Summit,
the
kubernetes
contributor
Summit
in
the
North
America
kubecon
conference,
has
become,
has
gone
underway
in
terms
of
organizing
for
those
folks
who
don't
know
every
kubecon
conference,
we
have
a
contributor
Summit,
which
means
everyone
who's.
A
kubernetes
org
member
is
able
to
if
they're
at
the
conference
come
and
attend.
A
Usually
it's
a
day
or
two
before
the
official
conference
starts
but
come
and
attend
to
meet.
Fellow
contributors,
listen
to
talks
from
them,
possibly
do
work
alongside
one
another
and
to
generally
have
a
summit
where
we
celebrate
the
work
that
we've
been
doing
and
the
North
American
version
of
the
contributor
Summit
always
always
features
Awards
as
well.
A
So
our
contributor
awards
are
also
a
part
of
the
North
American
celebrations
there
and
one
to
post
this
info
that
with
the
preparation
we're
currently
looking
for,
leads
and
Shadows
of
the
different
parts
of
what
makes
the
contributor
Summit
great
and
how
we
organize.
This
Ray
has
organized
the
awards
previous
times
and
we'll
be
stepping
in
as
an
Emeritus
advisor
for
the
awards
section
for
the
summit
and
I'll
be
leading
the
day
of
operations
for
this
year's
Summit
in
North
America.
A
The
requirement
is
that
the
only
requirements
is
that
you
read
the
different
linked
handbooks
that
we
have
attending
a
lot
of
the
meetings
that
are
going
to
be
virtual
in
terms
of
organization
and
that
you
want
to
do
it.
You
don't
have
to
have
done
any
of
this
before
we're
just
looking
for
folks
who
want
to
jump
in
and
help
out
and
for
majority
of
the
work
there
are
linked
there
as
you
can
see
handbooks
so
that
you
will
understand
exactly
how
that
work
gets
done
and
what
those
rules
require.
A
All
right,
then,
we've
got
a
couple
more
agenda
topics
here.
Depeche
would
love
to
hand
it
over
to
you.
H
D
H
A
When
you
said
you
rejoined
how
how
long
ago.
A
Okay
yeah,
if
it's
a
week,
then
they
should
have
already
been
coming
to
your
inbox.
It's
not
immediate!
That's
why
I
ask
it
takes
a
bit
of
time,
but
a
week
you
should
have
received
them
already.
A
You
may
just
have
to
check
if
they
are
possibly
there
somehow,
but
need
to
be
deleted
to
be
re-added,
I'm,
not
actually
sure
I'm,
not
a
Google
group
expert,
unfortunately,
which
is
those
invites
get
sent
out.
If
anyone
has
a
suggestion
for
Depeche.
B
E
A
Great
thanks,
everyone-
and
you
said
that
the
second
question
has
been
answered.
There.
You've
got
Ray,
giving
a
bunch
of
the
difference.
Yeah
yep
great
different
answers
on
the
links
there,
but
also
Depeche
feel
free
to
reach
out
to
us
any
of
our
us
as
leads
OR
tech
leads
in
terms
of
becoming
a
reviewer
as
an
FYI
for
everyone
on
the
call.
A
What
we're
basically
looking
for
is,
is
consistency
and
and
jumping
in
to
do
the
work,
and
so
reviewing
means
that
you
get
the
opportunity
to
be
able
to
add
the
lgtm
labels
on
on
PRS
approvers
are
the
ones
who
can
add,
approve
and
thus
be
able
to
actually
push
a
PR
properly
to
merge.
A
So
we're
always
looking
for
more
reviewers
so
great
to
hear
that
you're
interested
to
push-
and
let
us
know
if
you
have
any
more
questions
once
you've
gone
through
the
the
the
links
that
Ray
has
provided.
A
Great
last
topic
here,
Maureen's
got
a
question
of
how
to
apply
to
be
a
shadow
of
the
current
PR
angle,
very
easy
to
answer.
You
can
just
reach
out
to
the
pr
Wrangler
that
you
wish
to
Shadow
and
they
can
pop
you
onto
the
list
as
a
shadow
themselves.
A
What
I
would
recommend,
however,
is
that
if
there's
already
a
shadow
assigned
to
someone
to
pick
someone
that
doesn't
have
one
so
that
there
isn't
an
abundance
of
Shadows
for
one
person,
so
that
would
be
all
you
need
to
do
if,
for
some
reason,
you
can't
get
hold
of
the
pr
Wrangler
themselves,
any
of
us
leads.
We
can
reach
out
to
us
and
say
I
wish
to
Shadow
on
this
week,
and
we
can
add
you
no
problem
at
all.
A
No
worries
yeah
feel
free
to
also
for
those
who
are
interested
in
shadowing
it
doesn't
have
to
only
be
once
you
can
do
it
several
times.
That's
okay,
shadowing
I
would
do
want
to
say
it
doesn't
mean
that
you
will
automatically
become
a
Wrangler.
Wranglers
are
approvals.
A
Sometimes
we
have
reviewers
helping,
but
they're
generally
approvers,
so
that
they
can
actually
push
PRS
through
to
possibly
be
merged,
but
becoming
a
Reviewer
is
a
great
step
towards
eventually
becoming
an
approver
and
that's
a
Wrangler
as
well,
but
we
always
are
willing
to
share
how
we
do
wrangling
so
that,
even
as
reviewers,
you
get
a
lot
more
information
and
guidance
on
how
you
can
do
reviews
in
zidocs
as
well.
A
All
right,
we
have
come
to
the
end
of
our
written
agenda.
I
want
to
put
a
quick
call
out
for
anyone
who
has
any
further
questions
or
topics
that
they'd
like
to
address
today.
H
A
It
is
around
English,
however,
we
do
try,
there's
a
couple
of
us
that
are
involved
in
localization
generally,
where
we
do
try
and
jump
in
if
needed.
A
great
example
might
be
a
link.
Change
really
only
connect
in
a
certain
localization
that
a
localization
reviewer
has
already
approved,
and
we
need
an
lgtm,
maybe
from
an
ordinary
reviewer.
So
little
things
like
that
can
also
happen,
but
we
generally
leave
localization
PRS
to
the
localization
groups,
what
I
would
suggest
and
for
folks
who
are
involved
in
those
localizations.
A
You
can
always
tag
in
if
you
need
extra
approval
approval
beyond
the
localization
group
tagging.
One
of
us
leads
if
you
need
it
on
your
PR
and
we
can
absolutely
look
into
it.
An
example
of
that
is
the
Korean
localization
often
uses
me
to
help
merge
up
changes
to
their
specific
Dev
branch
that
they
use
and
that's
something
that
we're
happy
to
kind
of
jump
into,
because
we
don't
need
Korean
localization
experience
to
be
able
to
help
out
with
that.
A
All
right,
I'm,
taking
silence
as
a
no
I,
want
a
big
thank
you
to
everyone
for
coming
to
today's
meeting.
Also,
thank
you
to
Ray
for
being
my
notetaker
I,
find
it
very
hard
to
do
both.
So
thank
you.
So
much
I
want
to
wish
everyone
a
really
great
week
if
it's
warm,
where
you
are
enjoy
the
warmth,
if
not
enjoy
that
weather
too,
and
we'll
see
you
in
a
couple
of
weeks
for
our
next
meeting
bye,
everyone.