►
From YouTube: Kubernetes SIG Docs APAC meeting for 20210623
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
A
A
This
week's
pr
wrangler
is
sabitha
right
nathan.
This
week's
next
week's
pr
angler
is
me.
I
do
know
my
scheduled
pr.
English
shifts.
Let's
talk
about
the
upcoming
release.
Do
we
have
any
update
from
the
release
team.
B
I'm
guessing
is
it
on
chris
yeah,
I'm
on
the
release
team.
I
don't
have
a
new
status
for
us.
I
knew
they
had
some
problems.
The
spreadsheet
had
had
difficulties
and
I
believe
victor
has
gotten
those
straightened
out.
Other
than
that,
I
don't
have
an
update.
A
Okay,
good
to
know:
let's
move
on,
there
is
a
pull
request.
I'm
going
to
open
this,
have
a
look.
A
Cleaning
up
the
owner
owner's
aliases
file;
okay,
so
this
is,
I
think,
mostly
a
public
sort
of
information
announcement.
A
This
is
gonna
clean
up
and
remove
some
folk
castro,
joe
from
various
groups,
steve
perry,
53
and
zp.
Arnold,
adding
a
sig
lead
from
c
release,
which
is
just
a
copying
over
and
also
updating
some
release
engineering
people.
A
Any
questions
on
that.
I
believe
I
think
this
is
mainly
on
the
agenda
as
an
fyi.
A
Okay,
we
could
definitely
do
with
increasing
the
pull
of
reviewers
in
sig
darks.
So
what
would
folks
like
to
do
about
that?.
C
How
do
we
go
about
that?
Is
there
like
a
would
they
have
to
review
an
amount
of
docs
or
they
kind
of
I
don't
know
what
is
what's
the
criteria
to
be
a
reviewer.
A
I
would
say:
I'm
open
to
there
being
a
a
bunch
of
different
pathways
to
being
a
sig
docs
reviewer,
for
example,
someone
who's
a
reviewer
for
another
sig
or
who
has
done
plenty
of
reviewing
for
another
league
and
hasn't
contributed
much
to
dogs.
A
I
think
the
the
there's
not
a
big
barrier
of
evidence
to
say
if
you're
reviewing
for
another
sig
and
you
want
to
review
the
sick
docs,
I
think
we'd
be
like
open
to
doing
that.
We
would
assume
good
intent.
A
These
reviewing
is
kind
of
a
privilege
and
there
are
grounds
for
not
giving
it
to
just
the
whole
internet.
We
wouldn't
just
give
it
to
everyone
who's
on
get
github.
Otherwise
we
would
have
a
defaced
website
pretty
quickly,
but
the
aim
is
more
about
including
people
than
it
is
about
excluding
people.
A
If
you
are
new
to
contributing
in
kubernetes.
We
want
you
to
be
an
old
member,
but
actually
you
can
be
someone
who
is
reviewing
without
being
an
org
member.
You
can
be.
You
know
we
want
to
in
increase
the
pool
of
people
who
are
doing
reviews,
whether
they
are
doing
that
as
people
who,
whose
lgtms
count
or
they're
just
people
who
are
doing
that
as
people
who
contribute
by
by
providing
good
feedback
to
other
contributors.
C
A
What
how
should
we
do
this?
How
should
we
go
about
getting
more
people,
doing
reviews
and
then
relatedly?
How
should
we
go
about
giving
more
reviewer
rights
out
to
people
who
who
will
benefit
from
having
them.
B
One
one
of
the
hard
things
seems
to
be
getting
the
experts
to
come
in
and
do
a
review
when
it's
something
say
beyond
what
you
know.
You
know
some
of
the
docs
team
like
myself
might
be
able
to
do
so.
Maybe
I've
been
trying
to
figure
out
how
to
get
in
in
the
prs
I'm
working
on
how
to
get
people
to
review
them
and
maybe
showing
up
to
some
of
their
meetings
and
saying
hey.
We
have
three
or
four
prs
that
are
you
know,
particularly
in
your
guy's
wheelhouse.
B
C
Yeah
well
for
technical
reviews,
I
believe,
that's,
I
think,
that's
a
little
bit
different,
because
you
have
to
have
some
sort
of
expertise
in
that
in
that,
in
that
context
of
that
part
of
the
documentation
to
do
a
more
technical
review.
Yes,
I
agree.
Sometimes
you
do
have
to
to
privately
pinch
people
on
slack
to
get
a
technical
review
that
that
is
that's
not
in
common,
so
or
also
reaching
out
on
these
various
different
slack
channels.
C
For
for
the
various
different
sigs
of
that
contacts
is
another
avenue,
after
of
course,
making
the
comments
and
and
pinging
people
on
github
on
the
github
pr
yeah.
So
yeah
it
it's
it's
been
a
known.
I
guess
it's
I've
experienced
that
and
yeah
it's.
C
It
is
a
little
a
little
more
work
to
get
a
technical
review,
but
a
technical
review
is
is
needed
in
order
for
a
document
that
needs
a
technical
review
to
make
it
into
release.
So
if
they
want,
if
that
sig
does
want
that
documentation
updated,
it
has
to
have
a
technical
review,
and
so
there's
no
way
about
around
that.
A
So
let's
say
I
mean
imag
what
I'd
say
in
the
case
of
things,
whether
they're
going
into
a
release
and
documenting
a
feature
for
an
upcoming
release
or
it's
something
on
the
main
branch.
A
I
think
that
we
are
more
looking
for
the
person
who
who
does
the
the
nagging
who
engages
with
the
other
sig
rather
than
with
you
know,
with
the
person
that
makes
so
we're
looking
for
the
person
who
who
says
hey
sig,
whatever?
Could
you
could
you
find
someone?
That's
a
piece
of
work
that
we
do
and
and
yeah
that
mean
that
might
be
going
to
a
weekly
meeting
of
that
sig.
A
It
might
mean
posting
in
the
pr
reviews
channel
of
kubernetes,
which
you
can
do
if
things
are
not
going
well,
but
we
need
someone
doing
that
role.
B
A
Did
I
see
you,
I
mean
giving
time.
D
Yes,
so
so
so
the
fact
is,
actually
we
maybe
do
mention
some
sick
groups
when
reviewing
some
some
articles,
some
changes,
but
those
mentions,
do
not
work
well,
so
I'm
wondering
whether
we
can
have
some
kind
of
a
list
nominating
some
focal
points
from
each
and
every
relevant
seeks.
Just
as
we
have
a
list
of
pr
wranglers,
we
can
ask
help
from
other
things.
C
There
there
is
a
place
for
this,
for
the
there
are.
You
could
find
the
technical
reviewers
within
the
cap.yaml
file
for
a
for
for
a
cap.
It's
it's
a
lot
of
of
hunting
down,
because
with
the
documentation
you
have
to
find
what
that
documentation.
What
kept
is
aligned
with
the
documentation
then,
through
that
cap?
Now
you
could
find
the
technical
technical
review,
but
that
is.
It
is
difficult
to
find,
because
you
would
have
to
have
some
kind
of
knowledge
of
that
of
that
doc.
Pr
and
what?
A
So,
let's,
let's
come
back
to
that,
that
sounds
like
a
useful
thing
to
this
to
talk
about
in
its
own
right.
I
think
so.
We
also
want
to
regrow
the
reviewable
for
for
the
blog,
which
is
really
sparse
right
now
I
would
say
we
have
two
and
a
bit
active
approvers,
one
of
whom
is
me.
A
Actually,
I'm
not
I'm
not
officially
an
approver,
so
I
think
I'm
gonna
put
myself
forward,
but
really
you
know
the
thing
I
would
love
to
achieve
is
that
someone
else
steps
forward
and
I
can
endorse
you-
know
more
people
and
rather
than
doing
all
this
or
the
approving
myself,
I
would
I'd
love
to
help
other
people
step
up
to
that
role.
A
Any
thoughts
on
how
we
can
encourage
folk
from
I
guess
from
from
any
background
as
well,
like
there's,
no
background
that
we're
looking
for
in
terms
of
reviewers
and
approvers,
whether
you're
volunteering,
whether
you're
doing
it
in
your
fully
professional
capacity,
something
else.
B
There
was
a
question
a
few
weeks
ago
about
having
them
having
meetings
to
discuss
the
blogs,
and
I
don't
know
if
that
ever
came
about
if
there
have
been
any
meetings
for
people
who
are
interested,
because
I
think
there
are
several
people
who
said
they
were
interested
working
on
blogs.
I
don't
know
if
that
happened.
B
Yeah
I'll
do
that,
because
this
we
have
a
channel,
so
I
can
just
I
can
post
on
the
channel
and
just
what
just
pick
a
date
and
try
to
hold
a
meeting.
Is
that.
A
Yeah,
okay-
and
you
know,
if
you
need
resources
like
you,
want
to
find
out
as
a
zoom
link
that
you
can
use
that
kind
of
thing.
That's
the
sort
of
thing
that
you
know
there
are
folks
in
sig
doc
who
can
docs?
Who
can
help
you
get
hold
of
that
if
you're
not
sure.
B
Okay,
now
that
sounds
great.
Actually,
someone
did
also
ask
me
about
the
blogs,
in
particular
the
release
team.
How
in
the
past
have
they
worked
with
sig
docs
to
to
put
out
blogs
for
the
releases?
Have
you
been
through
that
or
or
ray
have
you
been
through
that
in
a
release.
A
C
Yes,
yeah,
yes,
so
with
blogs
there-
and
I
might-
I
remember
there-
used
to
be
a
separate
meeting
for
blogs
that
met
less
frequently.
I
believe
it
might
have
been
every
two
weeks
or
so,
but
someone
with
the
block
from
the
box
team
would
generally
introduce
themselves
on
this
meeting
as
well,
usually
midway
through
the
release
or
even
earlier
through,
through
the
release
just
to
introduce
themselves
as
part
of
the
of
the
blog
team
for
the
122
release.
C
Then
usually
I
would
refer
them
to
the
the
to
the
slack
channel
for
sig
doc
blogs.
They
do
have
a
separate
slack
channel
where
they
could
paying
for
reviews.
Also
thank
for
request
any
help
as
well
and
also
get
more
info
on
that
on
the
blog
on
the
blog
meeting
and
and
the
cadence
for
that
meeting.
A
My
my
recollection,
is
you
know
if
you
rewind
a
good
number
of
months.
I
I've
heard
people
saying
we
could
really
do
with
more
people
joining
the
blog,
the
blog
group,
and
that
that
that
was
that
call
went
out.
I
don't
think
it
was
particularly
well
answered,
and
I
think
that
that
that
what
was
left
has.
A
B
I
I
could
try
to
step
up
and
and
and
get
or
at
least
get
maybe
get
a
meeting
and
get
us
to
discuss
it.
So
it
would
be
nice
to
maybe
offline
talk
to
someone
who
has,
you
know,
gone
through
the
process
and
know
what
it
entails.
B
I
mean,
is
it
diff?
Maybe
it's
just
like
doing
anything
you
just
have
to
do.
You
know,
do
pr's
and
get
them
reviewed,
and
you
know,
or
if
there's
more
to
it
than
that,
you
know,
need
to
know
that.
B
A
We
record
all
these
things
and
I'm
not
sure
how
how
popular
the
videos
are,
but
I
mean
my
first
suggestion:
chris
is
have
a
look
on
youtube.
A
If
you're
willing
to
do
that
and
see
if
you
can
find
it
recording
and
that
will
you
know
through
the
application
of
watching,
probably
on
double
speed,
a
bunch
of
meeting
recordings,
you
can
work
out
how
the
things
used
to
go
and
if
you
don't
find
them,
I
guess
we
don't
have
the
recordings.
A
B
A
I
mean
in
terms
of
what
I
will
also
say
that
in
terms
of
what
is
actually
published,
we
have
our
we
have
the
blog
like
we
have
the
r
every
blog
article
started
life
as
a
pull
request
for
at
least
for
the
past
few
years,
and
so
you
can
have
a
look
at
the
pull
request
and
I
realize
that's,
you
know
reconstructing
history,
but
you
know
we
have
a
bit
of
forensic
approach
to
to
process
inferring
it
from
what
we
saw
happened.
B
Okay,
well,
I
will
try
to
get
something
started
before
next
week's
meeting
then,
and
try
to
report
on
something
that'll
that
will
lay
the
fire
under
me
to
you
know,
get
started
on
it
then.
A
I
do
think
it's
it's
okay
to
to
to
suppose,
and
you
know
maybe
put
a
message
in
say:
sigdoc's
blog
or
on
a
pull
request
saying.
I
believe
this
is
the
case.
I
believe
this
is
the
approach
we
would
take.
I
have
certainly
both
before
becoming
a
reviewer
and
afterwards
becoming
a
docs
reviewer.
Put
in
a
review
saying
hello,
I'm
trying
to
help
here
is
how
you
know
my
feedback.
A
A
E
I
have
another
idea,
you
know
initial
tentative
liberals,
I
mean
poor
issue,
we
can
provide
labor
for
help
wanted,
but
I'm
not
sure
we
can
help.
We
can
get
help
wanted
labor.
We
can
put
headphones
variable
to
pr
so
that
tentative
reviewers
check,
which
one
they
can
be
volunteered
as
a
tentative
reviewer.
E
B
E
E
A
So
I
I
have
a
view
on
this,
which
is
that
any
pr
which
doesn't
have
lgtm
and
is
open
is
reviewable,
and
you
know
if
it
does
have
lgtm.
You
can
still
review
it,
but
you're
adding
less
value.
Sure.
E
But
they
are
not
sure
we
know
we
can
review
any
repair
we
can
initiate,
but
some
new
contributors
may
not
know
they
can
review
that
one,
because
our
github
system
assigned
the
tentative
reviewers
already
in
the
pr,
and
sometimes
we
peer
regulars
assign
or
favor.
So
in
the
case
they
may
not
touch.
A
I
think
I
think
that
first
case
is
one
we
should
handle
through
communication.
A
I
my
take
is:
let's
make
it
super
clear
to
people
that
when
you
see
a
bot
assigning
a
review
and
recording
a
reviewer,
that's
saying:
well,
my
understanding
is
that's
saying
the
bot
thinks
these
people
should
review
and
to
be
honest
with
the
website,
repo
that
that
process
doesn't
work
so
well,
I
it
might
work
better
for
some
of
the
other
power
managed
repos,
I
don't
know
but
yeah
it
doesn't
work
super
great
for
the
website.
A
A
I
don't
know
how
that
affects
localizations,
so
typically
localized
pages,
don't
keep
the
the
front
matter
localizers.
How
do
localizations
phase
you
know
face
and
address
the
you
know
reviewers.
Is
that
something
that
is
generally
similar
to
what
the
english
upstream
docs
are
having
or
is
it
better?
Is
it
worse.
E
You
know
in
localization
team
there
are
pure
reviewers
than
the
english
leaders
and
we
try
to
make
more
pro
in
contributing
localization
itself.
Then,
if
there
are
many
people
are
working
on
localization,
then
among
them
we
can
bring
up
them
as
reviewers
and
then
approve
us,
but
we
also
facing
pure
pure
reviewers
and
approvers.
A
So
I
want
to
capture
maybe
a
couple
of
comments.
I'm
not
really
sure
I
can
echo
that
back
and
and
and
summarize
what
you
said
there,
but
are
there
a
couple
of
steps
that
you
would
say
that
the
korean
localization
takes,
for
example,
two
specific
specific
actions
you
take
to
to
make
sure
that
there
are
review.
The
pool
of
reviews
is
big
enough.
E
Sure
in
localization
we
also
have
a
pair
wrangling
system,
so
in
our
korean
localization
we
could
try
weekly
meeting.
We
select
a
peer
wrangler
for
a
current
development,
localization
branch
so
that
he
she
or
he
can
assign
a
proverbs
assigned
vprs
and
then,
if
there
are
edge
teams,
then
assign
a
proverbs
so
that
the
pr
can
be
completed.
E
We
tell
regular
rate
response
from
assigned
reviewer
whether
the
reviewer
can
take
review
for
the
pr.
Sometimes
people
are
not
responding,
so
we
check
and
then,
if
they,
if
the
reviewer
is
not
respond,
does
not
respond,
then
we
change
to
another
vpr
and
we
have
agreements
on
that.
A
A
I
thought
I
heard
someone
sorry
if
there's
anything
negative,
that
we're
doing
what.
What
can
we
do
to
not
do
that.
D
D
A
That
is
a
really
good
point
jimmy
if
you
open
an
issue
about
that
now,
if
you're
willing
to
open
an
issue
about
that
now,
please
feel
very
free
to
copy
me
in
on
that,
and
I
will
take
work
on
that.
If
not,
I
will
put
an
action
on
myself
to
open
that
issue.
Which
way
do
you
want
to
do
it?
A
Okay,
cool
thanks,
I
think
that's
gonna,
be.
I
think
that
action
is
gonna
help,
because
the
feedback
I'm
hearing
here
is
that
we
are
putting
reviewers
off
by
making
it
hard
for
them
to
work
out
what
their
job
would
be,
and
if
we
do
that
at
the
moment
we're
not
going
to
be
effective
at
growing
up
all
of
reviewers,
because
people
look
at
that
and
say:
oh
I'm
clearly,
you
know
there's
some
people
who
look
at
that
and
say
I'm
clearly
not
up
to
the
job
of
reviewing.
I
don't
understand
these
guidelines.
A
A
So
I
think
that's
I
feel
like
that's
one
of
the
more
useful
steps
we
can
take
immediately.
What
other
people
think.
B
Yeah,
maybe
something
like
a
cheat
sheet
that
just
says
you
know
you
know
too
long
too
long,
don't
read
and
that
that
there's
like
a
immediately
something
you
could
click
on
to
get
to
there.
B
Yeah,
I
did
I
mean
I
really
only
started
working
in
in
in
the
with
the
kubernetes
docs
really
just
a
few
months
ago,
so
some
of
it's
still
pretty
fresh
in
my
mind.
You
know
you
know
I
did
some
work
a
few
years
ago
so
and
one
of
it
was
yeah
when
I
see
reviewers
assign
when
I
first
saw
that
I
didn't
know
that,
then
anyone
could
jump
in
and
and
review
since
it
did
have
reviewers
on
it
already.
So
that
would
be
a
nice
thing.
B
A
Cool
branch
rename
the
if
you're,
calling
it
the
master
branch
you
need
to
to
update,
because
it's
called
the
main
branch
now
well
done
jim
for
coordinating
that
well
done.
W
g
naming
for
coordinating
coordinating
that
we're
moving
forward
a
bit
of
a
challenge.
A
I
don't
envy
k,
slash
kubernetes
having
to
do
the
same
thing,
but
it's
gonna
be
gonna,
get
done
one
day
also,
thanks
to
all
the
people
who
made
the
infrastructure
to
give
us
buttons
to
to
do
the
hard
work
and
so
on,
it's
a
lot
easier
when
you've
got
a
button
that
does
it
does
the
hard
work
for
you
any
more
thoughts.
A
Okay,
slack
meetings:
this
is
ties
in
with
the
disc
question
about
blog
meetings,
quite
heavily
chris
sick
contributor
experience
holds
some
of
their
meetings
in
slack
via
threads
in
a
dedicated
channel.
We
have
four
daily
four
week,
four
weekly
meetings
in
a
month,
one
at
this
time.
Three
at
another
time,
do
we
want
to
try
maybe
having
a
different
pattern
where
some
of
those
meetings
in
a
month
are
replaced
with
a
slack
chat,
I
saw
a
nod
there,
maybe
from
cool
sorry.
I
can't
pronounce
your
name
so
well.
D
So
for
apec
meeting
a
monthly
meeting
is
still
good.
I
don't
think
we
need
some
change
for
that.
C
A
I
guess
you
know
we
could
have
a
a
pacific
caden
meeting
on
a
monthly
cadence
as
well.
A
C
Thoughts
personally,
when
I
can
make
the
meeting
I
do
enjoy
it
depending.
What's
what
I
guess
my
role,
I
guess
for
that
time,
if
I'm
working
on
it
on
the
release
or
if
or
from
or
if
I'm
not,
but
I
I
do
tend
to
enjoy,
but
I
know
with
my
schedule
personally
that
I'm
getting
busier
and
busier
every
week,
it
seems
like
so.
A
One
thing
I'll
I'll
add:
I
don't
know
if
this
is
worth
minuting,
but
it
would
increase
the
gap
between
you
know
what
well
I
don't
know,
I'm
thinking
out
loud
here.
Would
it
increase
the
gap
around
between
actually
saying
hello
to
a
new
contributor
as
a
hello
in
a
meeting,
because,
like
saying
hello
on
slack,
is
not
the
same
as
being
able
to
wave
at
someone
and
say:
hey
it's
great
to
see
you
because
you
don't
see
them.
C
And
personally,
from
just
being
part
of
releases-
and
this
might
change
since
we're
going
to
three
release
cadence
per
year
instead
of
four-
that's
you
know
it's
a
meeting
is
also
a
place
to
signal
for
for
for
help
for
reviews
or
to
signal
what
is
coming
up
just
dates
in
terms
of
important
dates,
for
the
release,
and
just
so
just
another
place
to
signal.
Yes,
we
could
always
have
signal
and
slack
as
well
when
needed,
but.
A
I
mentioned
the
and
on
chord
that
is
a
thing
that
toyota
used
to
use
in
their
factories
to
be
able
to
call
a
supervisor
over
if
you're,
having
difficulty
assembling
things
and
so
on,
but
yeah
calling
for
help.
A
E
Thank
you,
I
just
hope
to
update
korean
localization
team
and
I
hope
to
share
the
korean
localization
milestone
and
as
we
as
you
know,
we
are
using
a
prince
changing
and
we
have
our
own
development
localization
branch
for
two
weeks
and
then
we
keep
changing
and
current
localization
branch
next
ko5
and
we
have
announced
we
make
announcements
with
people
after
we
may
generate
that
branch.
E
E
We
have
a
pair
please
and
we
have
world
target
after
we
merge
this
branch
to
main
branch,
and
then
we
initiate
another
upcoming
branch
again
also,
we
can
go
to
the
meeting
note
and
we
also
make
a
issue
to
update
outdated
korean
document.
E
E
Okay,
I
just
shared
korean
localization
milestone.
Do
you
have
any
question
regarding
korean
localization
milestone,
or
can
I
keep
going?
It
is
to
just
sharing
korean
team
update.
E
Decided
to
change
it
to
tri-weekly
meetings,
because
we
are
losing
participants
to
our
weekly
bi-week,
limiting
so
to
make
more
people
in
one
meeting
we
changed
the
schedule,
I
hope
to
to
share,
not
thing
to
discuss
and
then
the
last
one
is
election
for
new
korean
localization
team
leader.
Currently
it's
me
circo,
but
my
duty,
the
team
leader,
will
be
finished
on
july.
I
did
it
one
year
of
around
one
year
and
we
have
some
tentative
schedule
to
get
to
proceed
with
the
election,
so
that's
all
for
the
career,
localization
team.
E
A
Something's
just
popped
into
my
mind,
which
I'm
gonna
share,
which
is
twitter.
We
have,
as
in
kubernetes,
has
a
twitter
feed
and
some
of
the
things
that
were
coming
up
here.
We
might
be
able
to
share
as
tweets
there's
a
mechanism
being
added
in
draft
to
make
it
easier
to
tweet
out
as
this
as
this
tweet
has
this
twitter
handle.
A
So
I'm
not
sure
what
level
of
detail
would
be.
You
know
appropriate
to
share,
we
can
find
out,
but
this
is
stuff
that
is
aimed
at
contributors,
and
you
know
a
call
to
action
to
say
hey
if
you're
a
contributor
who
speaks
korean,
here's
some
ways
to
get
involved,
one
of
which
might
be
dogs,
could
be
useful.
Maybe
you
know
the
same
for
other
languages.
If
you
speak,
chinese
there'll
be
similar
mechanisms
to
getting
involved
in
things.
Not
just
docs
they'll
be
different
bits
of
of
ways
to
get
involved.
A
There
might
be
a
meeting,
there
might
be
some
projects
which
have
a
an
aipac,
friendly,
weekly
meeting.
That
kind
of
thing.
A
Generally,
my
advice
is,
you
know,
be
general
if
you're
tweeting
at
a
whole
community,
try
and
include
people
and
try
and
and
reach
that
community
in
in
lots
of
ways
of
interest
rather
than
narrowly
I've
released.
My
new
thing
or
here
is
this
particular
team
that
you
want
to
know
about,
but
the
mechanism
is
there
and
I
think
we
can
I'll
try
and
revisit
it
when
the
new
mechanism
is
out
and
promote
this
to
people
in
sick
docs
to
say
we
can
do
this
tweeting.
A
I
mean
I'm
saying
that
to
someone
who's
not
on
twitter
myself,
but
it
might
be
relevant
to
folks
who
are.
A
Well,
yeah,
not
everyone
who
speaks
chinese
is
in
china,
but
I
appreciate
the
vast
majority
are
and
there's
plenty
of
localizations.
So
this
is
this
is
of
general
interest.
I
I
appreciate
china
is
a
special
case
and
there
are
websites
you
can't
reach
into
china
and
and
that
aren't
used
in
china
still
relevant
to
create
right.
Okay,.
E
A
Sure
and
that's
not
to
say
that
if
you
know
if,
for
example,
for
for
china,
though
there
are,
you
know
other
websites
that
I'm
not
going
to
be
particularly
familiar
with,
that
are
going
to
have
a
better
reach.
If
you
want
to
reach
people
using
a
different
channel,
you
can
nothing
stops
you
doing
that.
A
A
Sure
cool
cheating
back
to
you-
you
mentioned
this
just
earlier
reviewing
and
people
in
other
cigs.
D
Yeah,
so
so
that
that
was
my,
that
was
my
experience
from
the
openstack
community
and
in
in
that
community
we
have
focal
point
for
each
and
every
sub-communities.
For
example.
If
we
want
some
api
to
be
confirmed
to
be
from
in
a
good
way,
you
will
have
a
focal
point
for
that.
So
so
in
kubernetes
I'm
wondering
if
we
can,
we
can
have
a
list
of
focal
points
for
each
sig,
for
example,
for
a
signal.
Maybe
he
has
one
for
the
coupe
admin,
maybe
nearly
so
on
and
so
forth.
A
A
Okay,
so
what
I
can
do
is
I
can
ask
on
that
slack
workspace.
I
I'm
happy
to
ask
that,
but
you
know
anyone
who's
a
contributor
and
if
you're
in
this
meeting,
you're
contributing
to
kubernetes,
is
welcome
to
join
in
that
discussion
as
well.
A
Okay
and
then
blog
release
liaison,
I
think,
let's
try
and
spend
not
so
much
time
on
this.
I
think
we've
gone
a
little
bit
over
the
official
time,
but
I'm
happy
to
talk
about
blog
and
release
for
a
bit.
A
Chris
and
ray
I'm
going
to
call
on
you
to
chris,
you
had
to
think
you
had
a
question
and
ray.
I
think
you
might
have
felt
you
had
an
answer.
C
Yes,
okay,
so
for
the
kubernetes
block
for
the
blogs
for
the
release
there
is,
there
was
an
opt-in
process
that
was
started
last
release
cycle
where,
where
six
would
opt-in,
if
they
would
want
their
enhancements
for
release
to
have
a
blog
post
and
that
that
that
kind
of
starts
off
that's
the
first
step
in
a
blog
for
release,
the
blog
scene
will
follow
up
with
with
those
six
as
well
and
then,
and
also
the
blog.
C
The
the
release
blog
team
would
also
would
would
usually
touch
with
usually
come
to
this
docs
meeting
midway
to
the
release
and
just
introduce
themselves
and
then
and
then
reach
out
to
the
sig
docs
blog
team,
either
usually
on
slack
first-
and
I
don't
know
what
that
what
the
meeting
cadence
is,
but
I've
seen
on
most
of
the
communications
is
via
slack
most
of
the
doc.
Most
of
the
blogs
are
released
after
the
release,
but
of
course,
they
have
to
be
reviewed
that
be
reviewed
before
the
release
date.
C
This
is
always
a
time
crunch.
The
the
first
blog
on
the
release
is
the
actual
release
blog
and
that
has
always
been
a
time
crunch.
To
get
to
get
written
and
to
get
reviewed
as
well,
it's
always
been
it's
not
always
been,
but
it's
the
past
few
cycles.
C
It
seems
like
it's
been
the
very
last
minutes,
then
the
other
blogs
tend
to
be,
no,
I
don't
say
most,
but
some
of
them
tend
to
be
in
a
better
position
in
order
ready
and
to
be
ready
for
their
release,
yeah
and
as
far
as
a
release
liaison
that's
pretty
much
the
role
of
of
the
release,
blog
team.
So
there's
I
I
know,
there's
been
some
sad
news
with
with
the
cycle
on
on
the
on
the
blog
lead,
so
divya
and
other
release.
C
Members
like
sabita
and
davia
have
stepped
up
and
to
help
leading
with
the
with
the
blog
with
with
the
blog
team,
so
yeah.
So
davey
has
devia's
a
good
resource.
If
you
have
more
questions
on
the
release,
vlog
process.
A
B
Yep
and
it's
accurate,
so
you
said
that
so
the
first
one
to
go
out
is
the
main
release
blog.
So
what
was
sort
of
the
cadence
of
the
others
like
how
soon
after
did
they
come
out.
A
A
little
bit
what
I've
seen
is
that
the
post
release
blogs
are
scheduled
and
they
are
go
out
on
weekdays
with
at
least
a
get
a
one-day
gap
between
them.
So,
typically,
you
might
go
around
on
monday,
wednesday
and
friday
leaving
gaps
for
any
other
announcements
that
need
to
come
out.
So
if
kubernetes
needs
to
say,
oh,
my
gosh
we've
just
found
a
security
hole,
you
know
don't
use
such
and
such
a
thing.
A
They've
got
a
day
where
there's
a
slot
for
it
or
any
other
blogs
that
come
in
at
the
same
time
can
sort
of
fit
in.
So
let
me
put
I'll
put
this
point.
B
A
So
I
I
don't
know
how
I
the
the
big
one
we
wanted
to
get
for
as
a
pre-release
article.
I
don't
know
how
well
we
did
with
that
was
around
post
security
policy,
application
and
plan
a
was
to
have
an
article
go
out
before
release
followed
by
a
post
release
article.
I
don't
think
we
actually
got
that,
but
that
was
the
aim
and
and
we
would
be
aiming
on
a
similar
thing.
If
we
had
a
you
know,
we
have
a
deprecation
coming
up.
A
I
should
probably
talk
to
jesse
butler
about
this.
In
fact,
I
think
that
would
be
a
good
idea.
A
So
what
I'm
saying
with
this
is
that
what
we
might
do
is
have
an
article
before
the
release
saying
you
know
what
in
the
next
release,
you
won't
be
able
to
use
beta
apis
for
ingress
because
they
disappeared,
they're,
already
deprecated
and
they're
going
in
the
real
way
to
release.
They
just
won't,
be
there
anymore
and
then
post
release.
A
We
could
have
an
article
saying,
they're
gone
like
you
know,
going
back
and
look
at
their
other
article
kind
of
thing,
like
I'm,
not
saying
what
the
article
should
be,
but
that's
the
cadence
you'd
have
you'd.
Have
some
articles
saying
well,
the
release
is
coming
out
soon.
This
is
what
you
need
to
know
another
article
a
day
after
release
saying
we
did
tell
you
roughly,
but
not
not
that
that
not
that
public
nuance.
A
Let
me
change
that
to
removal
to
be
a
bit
more
clear.
I
want
to
wrap
things
up
so
any
more
on
blog
and
release
liaison
I'd
be
very
happy
to
see
this.
Some
of
these
conversations
move
to
slack,
because
I
think
there
is
some
stuff
to
talk
about.
I've
learned
some
stuff
to
talk
about.