►
From YouTube: Kubernetes SIG Docs APAC meeting for 20210428
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,
welcome
everybody
to
the
weekly
sig
docs
meeting.
This
is
the
apec
meeting,
which
is
at
one
o'clock
utc
time,
I'm
jim
angel,
one
of
sigdoc's
co-chairs
and
yeah.
Let's
kick
it
off.
Today's
date
is
april
27th
2021
and
very
quickly.
No
new
contributors.
I
see
a
lot
of
returning
welcoming
faces
so
good
to
see
everybody
and
moving
on
to
this
week's
updates
and
reminders.
A
So
this
week's
pr
wrangler
is
brad
topple
and
next
week's
pr
wrangler
is
nobody
because
of
kubecon
eu,
which
is
next
week
and
as
always
proverbs
make
sure
you
know
your
scheduled
pr.
Wrangler
shifts
the
link
is
in
the
agenda
and
I
will
put
the
link
into
the
chat
here.
A
A
As
far
as
I
know,
the
dates
have
been
published,
but
not
much
more
than
that.
So
I'll
look
for
the
release
lead
to
fill
us
in
in
the
future,
as
things
start
picking
up
and
moving
on
to
the
issues
in
pr's.
This
is
a
pretty
light
agenda
today.
So,
if
you
have
anything,
you'd
like
to
add,
feel
free
to
add
it
in
for
the
issues
or
pr's
and
or
discussion
area,
the
first
pr
for
discussion
was
brought
up
by
tim
bannister
and
this
pr
and
I'll
open
it
up.
A
A
So
I
looked
at
this
open
issue
and
it
seems
like
it
has
to
do
with
the
fact
that
there's
no
word
wrap
and
they
get
diff
when
they're
running
the
comparisons
and
it
becomes
challenging
to
read
and
the
proposal
is
essentially
adding
in
line
breaks.
So
it's
easier
to
understand
the
difference
there
and
I'm
not
sure
if
I
capture
that
correctly
at
jimmy.
I
know
that
you
have
more
context
on
this
than
I
do.
Do
you
have
any
other
comments
on
the?
I
guess
the
benefits
of
what
is
being
proposed.
B
B
We
want
to
synchronize
those
changes
to
localization
versions,
but
because
the
comparison
is
on
a
line
by
line
basis.
So
if
you
have
long
lines
that
has
200
300
words,
it's
very
difficult
to
capture
where,
where
exactly
it
are
the
changes
so
for
future
change
tracking.
This
is
very
inconvenient.
Sometimes
it's
very
time
consuming
to
to
find
out
the
difference.
So
I
I
think
that
is
the
same
finding
by
other
localization
team
as
well.
B
A
Yeah
that's
helpful
context,
and
I
would
imagine
this
applies
to
any
of
the
localization
teams
dealing
with
this.
I'm
curious,
so
my
thoughts
on
this
are
really
twofold
and
I
guess
it
makes
complete
sense
from
a
localization
standpoint,
especially
a
get
diff
standpoint,
to
compare
the
two
changes
and
since
you're
doing
a
line
by
line
comparison.
If
there's
only
a
single
word
change
now
that
entire
you
know,
line
or
multiple
paragraphs
have
been
updated
if
they're
not
broken.
A
B
No
yeah
yeah,
then
that
is
a
a
hub
for
concern,
so
the
I
think
there
is
some
kind
of
misunderstanding
of
the
markdown
syntax.
B
So
even
if
you
break
lines
for
long
paragraphs,
the
paragraphs
still
remain
the
same.
If
you
want
two
paragraphs,
you
will
insert
an
actual
empty
line
between
the
paragraphs.
That's
the
syntax,
so
maybe
some
contributors
are
not
well
aware
of
these
syntax.
So
that's
the
reason
they
they
they're,
not
breaking
long
lines.
A
Good
job
yeah
yeah,
I
think,
if
there's
no
impact
to
the
overall
readability
and
responsiveness
of
the
website,
I
wouldn't
mind
either
testing
it
myself
or
seeing
the
the
test
done.
I
think
it
makes
sense
why
we
would
want
to
do
something
like
this,
but
I
think
at
the
same
time
it's
one
of
those
things
to
make
sure
that
there's
no
impact
to
the
overall.
A
I
guess
readability
of
the
website
or
formatting
of
the
website
and
jihoon
welcome.
I
see
you
join
and
actually
we're
discussing
the
current
issue
that
was
opened
by
yourself
around
the
line
wraps
for
for
the
markdown.
B
So
I'm
understanding
this
correctly
because
we
are
using
the
hugo
engine
for
for
the
conversion
of
the
whole
website.
B
A
Yeah
and
I
guess
what
I'm
wondering
is
if
it's
on
a
new
line,
if
that
new
line
is
represented
in
hugo
or
if
this
is
going
to
just
mash
it
all
together.
So
let's
say
I
had
a
giant
ultra
wide
monitor
and
I
had
multiple
lines
in
the
markdown
file.
If
I
open
up
that
page
in
the
website,
does
it
make
that
single
paragraph?
So
I
still
see
the
long
line
and
it's
just
broken
in
the
code
base
or
in
the
markdown
and
that's
what
I'm
not
sure
about.
B
I'm
not
I'm
not
sure
either.
Maybe
we
can
do
a
double
check.
A
Gotcha
so
I'll
leave
a
comment
there.
I
I
personally
don't
have
an
opinion
or
really
a
comment
on
one
way
or
the
other.
It
sounds
like
this
would
be
very
helpful
for
localizations
and
I
think
that
any
way
we
can
support
localization
is
helpful
to
the
wider
goals
of
sig
docs.
So
I
think
that
that
makes
sense.
If
we
do
make
this
change,
I
have
a
feeling
that
we
should
definitely
widely
advertise
it
through
the
mailing
lists
and
other
means
of
communication,
potentially
having
a
future
discussion
at
the
weekly
meeting
next
week
as
well.
A
But
I
would
propose,
let's
do
a
test
on
this
and
the
impacts
of
what
this
would
look
like
and
really
the
example
being.
If
we
have
two
short
lines
that
are
touching
each
other
on
markdown.
A
B
A
A
A
Cool
yeah,
so
I
said
we
probably
test
it
out
just
to
double
check,
and
then
we
maybe
bring
this
up
next
week
at
the
weekly
meeting,
just
to
make
sure
everyone
is
on
the
same
page,
see
if
there's
any
differing
opinions.
I
know
we
have
a
smaller
team
on
the
call
right
now
and
I
think,
if
there's
no
objections,
this
makes
a
lot
of
sense
for
for
future
documents.
A
Okay,
before
moving
on
any
questions
or
concerns
around
the
the
line
breaks.
C
A
Awesome,
I
will
note
that
here
yeah,
I
think
it
makes
sense.
I
think
we
should
just
make
sure
that
that
it
is
as
we
intend
it
to
be,
and
then
I
think
the
other
challenge
is
going
to
be
potentially
fixing
future
documents,
but
I
wonder
how
you
know
retroactively.
I
don't
think
there's
an
easy
way
to
break
all
of
the
lines
that
are
currently
existing
today.
There
are
lines
over,
let's
say,
180,
characters
that
might
be
something
worth
scripting
or
looking
at
in
the
future.
If
we
do
go
down
this,
this
route.
B
So
so
jim,
I
just
take
the
south
coast
of
the
generated
html.
B
All
the
lines
are
joined
together
properly,
so
this
this
genuine
operation
was
done
by
hugo.
So
so
it
won't
impact
any
browsing
experience.
I
think.
A
Cool
awesome,
I
think
that
sounds
good,
so
it
sounds
like
really
the
only
action
item
here
then,
since
you've
tested
it
out
is
just
bring
it
up
next
week
to
make
sure
there's
no
differing
or
alternative
opinions
and
then
potentially
move
forward,
and
once
again
I
I
think
we
can
do
this
for
future
documents,
but
I
I
don't
know
how
we
can
really
retroactively
apply
this
to
older
ones
without
doing
some
sort
of
scripting
or
some
sort
of
tooling
to
to
adjust
older
ones,
which
might
be
something
to
look
into.
A
All
right
cool,
so
moving
on
to
tim
bannister
had
a
second
pull
request
here,
and
this
is
mentioning
that
court
lesson
stepping
down
and
becoming
an
emeritus
status,
which
we'll
talk
more
about
a
little
bit
later,
really
just
asking
to
fill
in
the
wrangler
schedule,
which
I
volunteer
to
do
so
I
don't
see
any
impact
or
necessary
action
to
be
done
there.
I
will
take
the
action
item
to
replace
the
pr
wrangler
schedule
and
we
should
be
should
be
okay
there
and
moving
on
to
reference
generation,
including
cube
components
and
config
apis.
B
B
I'm
curious
about
the
actual
problems
people
make.
Maybe
I
can
fix
them
so
yeah.
To
be
honest,
this
this
reference
generate
generation
is
not
so
straightforward.
B
Kubernetes
repo
cannot
be
imported,
but
we
need
to
import
it
to
pass
the
the
the
source
comments,
but
things
are
becoming
better
and
better
now,
because
most
of
the
packages
we
are
using
are
being
rendered
be
able
are
being
staged,
so
we
don't
need
to
import
the
whole
kubernetes
level.
That's
a
good
thing.
Another
improvement,
I've
done
in
the
generator
is
we
are
switching
to
use,
go
mod
for
for
depends
for
dependency
managing,
so
so
in
the
future.
A
B
Videos
I'll
be
on
the
agenda
two
weeks
ago,.
A
Gotcha
yeah
and
what
I'm
thinking
is
I'm
taking
a
look
here.
A
Gotcha,
so
I
want
to
say
that-
and
this
is
from
memory
so
don't
hold
me
too,
but
I
want
to
say
it
had
to
do
with
the
way
that
the
actual
releases
were
triggered
and
I
think
it
had
to
do.
B
A
A
Yeah,
so
I
I
don't,
I
really
would
like
to
revisit
this
definitely
and
talk
a
little
more
about
it.
I
want
to
make
sure
I
capture
this
correctly,
because
I
don't
know
if
that
was
the
entire
issue,
but
that
definitely
was
something
that
was
brought
up
and
I
don't
know,
maybe
we
could
potentially
build
the
reference
docs
off
of
one
of
the
alphas
or
one
of
the
you
know,
release
candidates
prior
to
the
release
happening,
but
I
know
a
lot.
B
B
A
Cool-
and
I
think
the
other
thing
too,
that
came
up
was
just
the
multiple
efforts
for
around
the
reference
generation.
I
think
there
was
just
some
general
confusion
there,
but
yeah.
Let
me
let
me
double
check.
Let
me
make
sure
that
video
is
published
and
if
there's
something
more
we
want
to
talk
about.
I
said
we
just
bring
it
up
again,
either
next
week
or
at
the
next
apec
meeting
to
to
deep
dive
into,
but
I
don't
think
it's
necessarily
concerns
with
the
effect
that
we're
doing
the
reference
generation.
A
So,
moving
on
to
the
localization
update
looks
like
yoko
here,
you're
editing
on
the
fly
there.
Do
you
want
to
give
us
a
quick
update
on
the
korean
team.
C
A
Awesome,
thank
you
and
thank
you
jihoon.
I
understand
if
you
can't
talk
right
now,
but
look
forward
to
to
seeing
more
of
you
around
here
and
welcome.
If
there's
anything
we
can
do
to
help.
Let
us
know.
A
Awesome
cool
so
moving
on
to
the
discussion
really
here,
I
just
wanted
to
call
out
and
acknowledge
all
of
the
work
that
zach
corlessen
has
done
for
sig
docs
reference
to
the
pull
request
that
was
opened
to
move
zach
to
emeritus.
A
A
Localization
there's
there
is
so
much
work
that
has
been
done
in
the
sig
docs
community,
much
of
credit
to
zach,
and
I
know
that
if
zach
were
to
be
on
this
call,
he
would
give
the
credit
back
to
the
community,
and
I
I
think,
that's
a
very
characteristic
of
zach
and
many
thanks
for
for
the
years
of
time
spent
and
effort
in
docs,
and
many
thanks
and
many
applause
for
for
future
journeys
and
endeavors.