►
From YouTube: Kubernetes SIG Docs APAC meeting for 20210324
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,
hello,
everybody
and
welcome
to
the
sig
docs
weekly,
apec
friendly
meeting.
This
is
the
fourth
tuesday
or
wednesday,
depending
on
where
you're
at
in
the
world
of
march
march,
23rd
or
march
24th,
and
I'm
jim
angel
a
co-chair
of
sig
docs
and
let's
get
this
thing
started.
A
So
I
see
all
returning
all
two
returning
contributors.
So
it's
good
to
see
everybody
welcome
back
and
thanks
for.
B
A
A
Okay,
so
one
issue
with
that
chi
ming-
is
that
you
are
the
pr
wrangler
for
next
week
as
well
I'd
hate
to
give
you
double
duties.
I
can
definitely
help
out
with
the
pr
wrangling
schedule
if
you'd,
like
maybe
chiming
you
and
I
could
split
it-
yeah
sure
cool.
Let
me
make
that
change.
A
Thank
you
and
thank
you
for
the
double
duty,
so
chi
ming
is
also
the
pr
wrangler
for
next
week.
So,
as
always,
approvers
make
sure
you
know
your
pr
wrangling
schedule,
there's
a
link
in
the
chat
there
or
link
in
the
agenda
so
moving
on
to
the
release.
121
ray,
unfortunately,
couldn't
make
it,
but
did
sync
with
me
before
this
meeting,
and
let
me
know
that
there
was
a
status
of
yellow
for
the
release
cycle.
A
Currently
waiting
on
the
docks
to
be
ready
for
review
tomorrow
is
the
deadline
they
had
two
outstanding
when
we
chatted,
I
just
saw
that
one
actually
merged
so
now
we're
down
to
one
that
should
be
worked
on
later
on
this
evening.
So
it's
yellow,
but
I
I
feel
like
it's
a
little
bit
of
a
cautious
yellow,
so
things
are
going
well,
but
just
to
be
aware
that
the
deadline
of
docs
ready
for
review
is
tomorrow
and
we
have
one
outstanding
pr.
A
A
Discussion
all
right
here
or
nothing
said
this
would
be
a
quick
one.
So
moving
on
to
the
discussion
area
or
open
discussion,
abigail
has
been
investigating
how
we
can
build
out
reports
for
localizations
a
while
back.
I
want
to
say
about
six
months
ago,
or
so
I
was
working
with
some
of
the
localization
teams
about
how
we
could
generate
a
report.
The
conversation
went
back
and
forth
on
how
to
use
google
analytics
most
effectively.
A
As
far
as
sending
out
those
pdf
reports,
we
haven't
found
a
great
solution
to
give
the
folks
who
need
the
data,
the
access
that
they
need,
while
at
the
same
time
not
sending
out
a
bunch
of
spam
emails
to
folks
who
don't
need
that
type
of
data
around
localization.
A
A
So
the
the
idea
that
abigail
proposed
and
we'll
discuss
this
further
as
well
in
future
meetings
as
well
as
on
the
email
list,
was
using
google
data
studio.
And
personally,
I
don't
have
a
ton
of
experience
with
google
data
studio,
but
it
sounds
like
a
free
data,
visualization
platform
that
integrates
directly
with
google
analytics.
A
So
there's
still
some
more
discussion
to
happen
around
this,
but
I
feel
like
it's
a
pretty
big
development
as
far
as
how
we
can
portray
and
visualize
some
of
the
localization
analytics
with
this
approach,
as
opposed
to
going
with
the
method
that
would
send
an
email
to
everybody,
it
would
just
be
a
website
that
folks
could
then
go
and
look
at
and
see
the
current
data
sets
that
are
present
through
the
website.
A
A
Yes,
so
that's
the
plan
is
the
google
data
studio.
You
want
to
try
out
the
unknown
questions
right
now.
We
haven't
gotten
too
far
into
investigating.
What
does
the
final
solution
look
like,
but
some
of
the
barriers
to
trying
this
out
is
who
what
account
will
we
use
to
own
it?
Can
we
automate
some
of
the
onboarding
off-boarding?
A
Cool,
thank
you.
Thank
you.
Yeah
definitely,
and
I
think
that
we'll
need
to
do
is
figure
out
some
of
the
operational
pieces
as
well
as
some
of
the
testing
and
making
sure
the
dashboard
can
be
appropriate.
But
from
the
initial
test
that
I've
seen
everything
looks
like
it
has
all
the
data
we
need
popular
pages,
most
visits,
click,
throughs
ability
to
filter,
etc.
A
A
All
right
more
to
come
there
and
one
thing
that
I
didn't
have
slated
on
the
agenda,
but
I'm
going
to
add
it
here,
so
we
have
this
apec
friendly
time
zone
meeting
that
happens.
You
know
once
a
month,
the
fourth
tuesday
or
wednesday,
depending
on
how
you
look
at
it
every
single
calendar
month,
but
we
also
have
the
localization
working
group
and
brad
I'm
glad
you're
on
this
call.
A
I
haven't
talked
to
anybody
about
this,
I'm
completely
just
talking
off
the
the
cusp.
I
guess
you
know,
but
I'm
curious
what
folks
thoughts
are
on
merging
the
two
of
them
and
I
don't
really
have
a
preference
over
one
or
the
other,
but
I
feel
like
in
previous
apac
meetings.
I've
always
said
this
would
be
a
great
topic
for
the
localization
meeting
and
what
I'm
thinking
is,
it
seems
like
there's
two
meetings
serving
the
same
purpose.
C
So
you
know
I
try
and
attend
both.
I
really
get
the
feeling
the
localization
meeting.
What's
nice
about
it
is
we
just
focus
solely
on
localization
and
we
get
to
go
really
really
deep.
C
This
meeting
is
more,
you
know
just
sort
of
like
your
typical
weekly
meeting,
but
in
a
different
time
zone,
and
you
have
perhaps
different
participants,
I
mean
and
the
other
meetings
only
once
a
month,
so
I
I
found
it
really
beneficial
because
we
get
to
sit
and
just
talk
about.
You
know
what
we
can
agree
on
and
what
have
you
best
practices?
So
I
mean
I
I've
found
it.
I
mean
just
attending
both
meetings.
I
find
them
dramatically
different,
but
it'd
be
good
to
know
what
you
know
cohen.
B
So
I
actually
have
the
same
type
of
opinion
as
broads,
because
here
I
can
talk
about
like
general
purpose
like
anything
about
localization
and
I
mean
documentation
and
then
at
the
localization
meeting
we
can
you
know
deep
dive
about
localizing
and
what's
the
best
practices,
and
how
do
we
proceed?
What
do?
How
do
we
manage
content
which
tends
to
be
out
of
date
compared
to
the
english
one?
So
it's
like,
if
I
talk
about
that
those
things
at
this
meeting,
they'll
be
a
bit
out
of
context.
B
For
you
know
english
stock
fox,
so
yeah
I
prefer,
I
think,
attending
on
both
for
different
purposes,
cool.
A
I
I'm
interested
if
anyone
has
any
other
opinions,
but
this
is
exactly
why
I
brought
it
up.
It
sounds
like
there
is
distinct
need
to
have
both
of
them
and
as
long
as
other
folks
enjoy
having
the
the
split
there,
I
think
it
makes
complete
sense
to
leave
them
together
or
leave
them
separate,
but
under
the
same
problem.
B
Yeah
I
mean
I
don't
mind
either
actually
yeah
just
if
this
time
time
being
it's
not
really
good
for
a
majority
of
the
attendees.
Maybe
we
can
change
it,
but
personally
I
don't
mind.
C
C
That
was
what
they
picked.
Does
that
make
any
sense
so.
A
Yeah
yeah,
so
maybe
it
might
be
worth
considering
if
attendance
is
kind
of
drooping
a
little
bit
on
the
apec
friendly
meeting.
Maybe
it's
a
better
time
zone
for
all
the
the
folks
interested
in
attending,
but
at
the
very
least,
it
makes
sense
to
keep
them
in
two
separate
areas.
And
ultimately
the
other
point
here
which,
which
makes
more
sense,
is
that
the
working
group
at
some
point
should
resolve
itself.
Once
the
working
group
and
the
work
is
completed.
A
So
it
would
be
a
little
challenging,
I
feel
like
to
combine
and
then
split
out
or
manage
somewhere.
So,
as
I
talk
more
about-
and
I
appreciate
y'all's
opinions
definitely
seems
to
make
sense
to
leave
them
separate,
but
potentially
proposing
a
a
new
time.
If
we
see
participation,
dropping
that
sounds
fair.
A
Awesome
yeah.
That
sounds
good
to
me.
Well,
what
I
think
what
it
will
do
is
leave
this.
As
is
you
know,
I
feel
like
I've
already
rattled
the
the
calendar
invites
for
quite
a
bit
this
year
already
we'll
leave
everything
as
is,
and
then,
if
we
find
the
attendance
to
be
relatively
poor
for
the
apec
friendly
time
zone
meetings,
consider
throwing
out
a
doodle
or
something
like
that
to
schedule.
A
Cool
any
topics
folks
want
to
bring
up
for
discussion,
pretty
much
open
discussion
now.
B
Oh,
it's
not
about
discussion,
but
I
I
have.
I
think
I
already
passed
it
on
slack
as
well,
but
so
I'm
I'm,
I
will
be
talking
at
kubecon
yeah.
C
B
And
so
one
is
about
kubernetes
like
internal
like
how
do
does
it
handle
resources
limiting
and
requesting
so,
which
is
technical
side
and
the
other
one
is
about
the
community,
and
the
topic
is
about
like
a
non-code
contributing,
so
you
know,
sig
docs
is
definitely
one
of
those,
so
yeah
I'll
be
talking
about
it,
especially
you
know,
considering
of
the
minority
so
localization
and
also
like
sig
docs
and
project
management.
B
There
are
a
lot
of
like
perspectives
that
you
can
involve,
get
get
get
involved
with
without
coding
right,
so
I've
been
talking
about
it.
Cool
awesome.
Is
there
anything
that
we
can
do
to
help
you
out
with
that
presentation?
B
I
think
that's
fine,
because
we
will
be
having
a
panel
discussion
with
like
a
lot
of
like
big
people.
Basically
so
yeah.
C
B
Would
just
provide
some
opinions
based
on
localization
and
documentations.