►
From YouTube: Kubernetes SIG Docs APAC meeting for 20210825
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,
hey
everybody!
Welcome
to
the
sig
doc's
apec
friendly
meeting.
I
am
jim
angel.
One
of
your
co-chairs
and
today
is
august
24th
2021,
depending.
A
Nice
cool-
I
see
that
we
have
returning
folks,
so
it's
great
to
see
everybody
back
and
moving
on
to
this
week's
updates
reminders.
This
week's
pr
wrangler
is
tim
bannister.
I
know
tim
is
leaving
on
holiday
this
week,
so
we
need
someone
to
step
in.
I
don't
know
if
anyone
on
the
call
would
like
to
volunteer.
Otherwise
it
can
be
just
a
group
effort.
C
Yeah
I
volunteered,
I
told
him,
I
would
hop
out
a
little
bit
awesome.
Thank
you
ray.
A
C
Yeah
so
the
first
week
release
123
started
on
monday,
so
we're
actually
day
two
I'm
the
123
123
release
lead
jesse
butler
is
the
123
123
release
stocks
lead
so
next
week
will
be
the
shadow
on
boarding
and
we'll
start
with
the
statuses
starting
next
week.
C
There
will
be
one
change,
though,
which
was
something
that
happened
in
122.
we,
the
some
folks
it
was
tim
and
also
someone
from
the
coms
release
team,
released
a
blog
post
post
code
phrase
about
some
about
deprecations,
and
so
this
is
something
that
we're
going
to
add
in
the
comm
circuit.
Communications
handbook
is
to
add
a
blog
post,
postcode
phrase
of
the
upcoming
deprecations.
So
that's
something
to
watch
out
for.
C
It's
it's
finalizing
final
date
is
friday.
Actually,
then,
we'll
notify
everyone
by
friday
and
start
onboarding.
Next
week,
perfect.
A
D
Hello
can
hear
you
so
my
name
is
luis,
I'm
based
in
singapore,
and
this
is
my
first
ever
so
sorry
open
source
six
meeting.
So
I
was
just
wanted
to
see
how
how
it
looks
like
because
I'm
interested
to
to
contribute
to
kubernetes-
and
I
was
interested
especially
in
the
sick
documentation.
A
Welcome
welcome
yeah
great
to
have
you
lewis.
If
there's
anything,
we
can
do
to
help
out
with
that
we're
going
to
have
some
time
at
the
end
of
this
meeting
for
open
questions
so
happy
to
help
out
otherwise
glad
to
have
you.
E
Yeah,
thank
you
so
you're
french
in
singapore,
you
said
yes,
I
am
french
and
I'm
working
in
singapore.
Okay,
that's
why
you
came
on
the
apac
meeting,
yeah,
okay,
yeah
cool!
Thank
you
for
visiting
yeah.
Thank.
A
F
Know
yeah
hi.
One
thing
I
didn't
notice
is
that
we
are
facing
an
issue
when
translating
the
upstream
english
documentation,
we
we
saw
some
prs
moving
pages
around.
F
So
it
is
a
big
headache
for
us.
A
Do
you
happen
to
have
one
of
the
pr's
or
examples
to
link?
I
think
this
is
one
of
those
things
where
we're
not
necessarily
you
know,
shaming
or
or
punishing
people
for
doing
this.
I
think
this
is
an
educational
opportunity
to
say
like
this
is
the
best
way
to
do
localization,
here's,
how
other
teams
have
done
it,
and
so
I
want
to
be
very
clear:
we're
not
we're
not
punishing
the
team
doing
it,
but
we
want
to
raise
visibility
to
the
folks
that
are
doing
it.
F
Yeah
one
thing
maybe
we
can
do
is
to
label
such
kind
of
prs
with
build
labels
such
as
a
big
change.
F
A
And
are
you
talking
about
localization
teams
moving
content?
Are
you
talking
about
the
english?
The
current
main.
A
A
Yeah
still,
if
you
have
an
example
of
some
of
the
major
moves,
it'd
be
great
to
call
it
out
or
add
it
to
the
pr
or
add
it
to
the
agenda.
If
you
have
a
second.
C
A
A
Cool
yeah,
if
you
could
throw
that
and
chat
there
or
in
the
agenda,
that'd,
be
awesome
and
then
I'm
thinking
as
we
and
this
kind
of
leads
us
into
the
next
couple
of
topics
here
discussion.
So
let
me
just
pause
there.
Any
other
issues
or
prs
folks
would
like
to
talk
about.
A
Cool,
so
so
this
is
the
first
meeting
that
we
are
hosting
since
I
sent
out
the
email
where,
basically,
we
lost
two
other
traditions,
so
we
lost,
they
stepped
down,
did
other
outside
responsibilities,
and
I
sent
out
the
email
saying
that
sigdocs
is
in
need
of
help.
A
And
I
think
this
is
an
area
that
has
been
commonly
kind
of
not
well
maintained
and
I'm
partially
to
blame
for
that.
And
what
we're
doing
now
is
saying
you
know
if
we
had
a
wish
list
of
what
could
be
done
or
a
better
way
to
organize
docs.
Here's
the
approach
that
we
can
take
and
then
just
to
be
very
clear.
None
of
these
decisions
are
happening
behind
closed
doors,
they'll
be
happening
outside
and
open
in
front
of
the
community
at
slack
stand-ups
and
things
of
that
nature.
A
When
we
see
big
content
with
this-
and
I
I
feel
like
we're
starting
to
correct
the
ship,
but
without
using
too
many
ship
analogies
for
for
a
kubernetes
meeting,
we're
starting
this
correct
course
here
and
we're
making
progress.
But
it's
going
to
be
a
longer
journey.
It's
not
going
to
happen
overnight.
It's
not
like
this
problem
is
going
to
be
fixed.
A
We've
moved
it
to
bi-weekly,
which
means
that
is
two
times
a
month
or
once
every
other
week,
and
one
of
the
challenges
that
we
face
is
prior
to
that.
When
we
had
weekly
meetings.
When
we
had
this
scheduled
apec
meeting,
we
would
cancel
the
normal
normal,
scheduled,
sig,
docs
meeting,
and
so
now
the
problem
we
run
into
is
now
that
we're
bi-weekly
when
this
meeting
occurs
when
we
cancel
the
main
one.
A
That
means
that
the
regular
scheduled
meeting
won't
meet
for
a
four
week
period,
because,
basically,
you
think
about
how
it
skips
we're
basically
losing
those
four
weeks
there,
and
so
I
don't
have
a
solution.
Just
yet,
I
just
want
to
raise
awareness
about
how
we
got
here,
but
as
a
result
of
this,
we
have
this
really
funky
schedule
where
even
the
apec
meeting
is
a
little
bit
challenging
to
schedule.
It's
not
quite
the
fourth
tuesday.
A
I
want
to
get
us
to
the
point
where
you
know
when
apec
meets.
You
know
when
the
regular
sig
docks
meet.
You
know
when
the
localization
meets.
You
know
when
the
various
times
are
it's
accountable?
It's
reliable,
you
can
add
it
to
your
calendar
and
you're
not
constantly
having
to
figure
out.
Oh,
is
it
the
standard
time
meeting?
Is
it
the
apac
time
meeting
and
having
to
juggle
that
so
more
to
come?
A
There
I
feel,
like
there's,
going
to
be
a
lot
of
changes
in
sig
ducks
for
the
better,
and
I
really
look
for
folks,
like
y'all
in
the
community,
to
voice
your
voice.
Your
input
give
feedback.
Let
us
know
if
there's
any
areas,
we
can
help
improve
as
we
start
to
to
build
out
the
team
a
little
bit
more
and
improve
the
overall
capacity
of
sig
ducks
leadership.
A
So
I'm
going
to
stop
there
any
questions.
Comments.
Feedback,
like
I
said,
sound
kind
of
a
very
large
email,
and
I
want
to
make
sure
I
can
address
any
comments
or
concerns.
Considering
this
is
the
first
time
we've
met.
F
So
jim,
it
sounds
to
me
that
we
have
already
had
the
decision
that
the
the
community
meeting
will
go
bi-weekly
right.
A
Correct
yeah,
so
that
was
just
basically
where
the
decision
to
go.
Bi-Weekly
was
due
to
the
fact
that
I
was
a
single
co-chair
president
for
sick
docs,
and
it
was
just
unmaintainable
and
unmanageable
to
meet
weekly
at
the
current
capacity.
So
we
just
made
the
somewhat
of
an
emergency
decision
just
to
say
we're
going
to
go
bi-weekly
for
right
now
we're
going
to
alleviate
that
workload
from
myself
and
some
of
the
other
tech
leads.
A
Now
that
isn't
to
say
that
once
we
get
grow,
the
contributor
capacity
that
we
couldn't
go
back
to
a
weekly
model,
it's
just
unsustainable
today.
So
that
is
something
that
the
community
could
help
decide.
A
I
I
really
think
we
could
potentially
do
something
like
the
last
thursday
of
the
month,
or
maybe
the
first
thursday
of
the
month,
or
I'm
thinking
of
a
way
that
we
could
potentially
have
it
not
relying
on
utc
time,
because
we
find
that
well,
it
will
be
pinned
to
utc
time
because
that's
very
important,
but
it's
not
relying
on
the
day
of
the
week
based
on
utc,
if
we
did
the
first
friday
or
the
last
friday,
for
example,
that's
gonna
make
it
a
lot
easier
to
schedule.
A
It's
gonna
make
it
a
lot
more
consistent
every
single
month.
So
I
think
we
can
keep
it
monthly,
but
we
might
move
it
to.
Let's
say
a
thursday
and
the
last
you
know
the
last
thursday
of
a
month,
for
example,
as
opposed
to
to
let
the
last
the
instead
of
the
fourth
thursday.
That's
the
problem
right
now.
A
A
Cool
any
other
preference
as
far
as
one
thing
that
did
come
up
too
is,
I
know,
folks,
are
in
various
time
zones
so
depending
this
could
be
extremely
early,
extremely
late.
It's
hard
to
find
a
time
that
meets
for
everybody,
but
in
general,
for
the
folks
that
are
attending
here.
I'd
imagine
they
say
this
time
works,
but
is
there
a
preference
between
it
being
earlier
or
later.
A
A
Yeah
absolutely
yeah.
I
think
this.
This
should
be
definitely
raised
up
in
slack
and,
like
I
said
to
that,
email
I
sent
out
is
we're
going
to
be
evolving
and
growing
here
and
we're
going
to
it's
going
to
be
iterative
process.
You
know
we're
going
to
help
expand
the
contributor
capacity,
we're
going
to
start
defining
roles
a
little
bit
more
clearly,
and
I
feel
like
we're
going
to
you
know,
get
things
back
into
a
shape
that
is
maintainable
and
was
not.
You
know,
burning
out
folks.
A
A
Cool
those
were
the
comments
that
I
wanted
to
share
any
other
things
that
folks
would
like
to
discuss.
E
Even
has
the
french
translation
channel,
I
believe,
which
is
kubernetes
dash
docs
dash,
fr.
D
D
When
I
was
saying
I
can
speak
french,
I
think
my
value
is
is
more
than
that,
I'm
open
to
contribute
in
a
new
way.
I
think,
depending
on
the
priority,
I
have
one
question
for
the
apac
group.
So
what
would
be
typically
the
scope
for
apac
it?
Will
it
be
sick
dogs
for
for
each
region,
sweet
junk
meetings,
or
is
it
only
for
apac.
A
So
I
can
answer
that
so
sig
docs
is
such
a
large
community
that
the
time
zones
that
we
meet
in
don't
always
align
with
everybody
in
the
wider
community.
So
this
meeting
in
particular,
is
for
the
entire
documentation
website.
It
covers
all
localizations.
It
covers
all
languages.
All
news
that
pertains
to
sig
docs.
There
is
a
specific
localization
meeting.
That
happens.
A
I
want
to
say
it's
the
first
monday
of
the
month
and
it's
once
it's
monthly
and
they
actually
focus
on
the
localization
issues,
the
issues
that
folks
are
having
doing
the
localization
efforts
and
that's
really
the
purpose
for
that
specific
meeting,
and
so
the
meeting
you're
attending
here
for
the
apac
time
zone
is
really
spanning
just
the
entire
org,
the
entire
community,
the
entire
kubernetes
website,
and
what
you
hear
here
is
the
exact
same
thing
that
you'll
hear
in
the
slack
stand-ups.
A
D
Yeah
just
wondering
what
would
be
typically,
the
discussion
points
for
this
type
of
meetings.
A
A
A
The
second
area
about
issues
in
prs.
We
have
pr
wranglers,
which
go
and
actually
review
and
approve
and
manage
pull
requests
that
are
open.
So
that's
an
area
where
usually
a
pr
wrangler
or
somebody
who's
having
issues
in
the
community
could
surface
an
issue.
So,
for
example,
if
I
come
across
a
poll
request
or
a
pr
that
I
didn't
know
how
to
deal
with
whether
it
was
a
personal
opinion,
whether
it
was
a
challenge,
I've
never
seen
before
it's
a
great
opportunity
to
bring
up
what
the
docs
community
is.
A
Here's
an
issue
I'm
having
and
then
the
last
section
you
see
is
an
open
discussion.
Anybody
can
add
topics
or
questions
or
anything
they
want
to
bring
up
there.
A
It's
ranged
from
anything
from
what
we're
going
to
talk
about
at
cubecon
to,
for
example,
here
I'm
talking
about
co-chair
transitions,
and
so
folks,
like
yourself,
that
are
new
contributors,
we're
here
to
help
you
we're
here
to
make
sure
that
you
have
a
smooth
journey
to
get
on
board,
and
so
it
would
be
a
great
opportunity
if
you
had
any
specific
questions
about
contributing
to
docs
and
people
here
are
very
friendly
and
be
happy
to
help.
You.
A
Okay,
thank
you.
That's
no
problem
and
hey
ram.
I
don't
believe
we've
met
before
just
saying
hi.
If
you
want
to
introduce
yourself,
go
ahead
but
feel
free,
there's
no
obligation.
G
Hey
everyone,
my
name
is
ram.
I
work
as
the
developer
advocate
for
the
cloud
foundry
foundation
just
here
to
learn
a
lot
about
the
you
know,
different
things
that
are
going
on
with
the
kubernetes
community.
G
The
cf
community
is
having
a
lot
of
overlap
in
terms
of
technical
competence
with
kubernetes,
and
I
thought
it
will
be
a
great
way
to
for
me
to
learn
about
kubernetes
by
you
know,
helping
contribute
where
I
feel
I
have
the
most
strength,
which
is
technical
documentation,
so
here
to
learn
as
much
as
possible
and
contribute
as
best
as
I
can
as
I
go
along.
The
way
awesome
well
welcome.
Ron.
A
Cool,
so
that
brings
us
to
the
end
of
the
the
discussion
as
well.
We
have
some
time
rom
l
k,
l
e
lewis,
if
you
have
anything
else
you
want
to
discuss
the
floor,
is
yours
otherwise,
and
not
to
exclude
anyone
else,
and
everyone
can
break
up
a
topic,
but
I
feel,
like
newcomers,
definitely
might
have
more
questions
than
y'all,
but
the
floor
is
open.
A
Cool
hearing
a
whole
lot
of
nothing
we'll
give
everybody
some
time
back
in
their
day.
I
appreciate
you
all
spending
this
evening
with
me
or
that
morning
and
we'll
see
you
on
slack,
have
a
good
one.