►
From YouTube: K8s SIG Docs meeting for 20220824
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).
B
Yeah
so
hi
I'm,
Italian
I
think
it's
just
gonna
be
the
three
we
you
know
get
started
with
the
meeting.
Nevertheless,
so
this
is
the
APAC
friendly
meeting
for
sick
talks
as
you're
already
aware
and.
B
With
respect
to
you
know,
dog's
reviews,
because
the
dogs
for
I
mean
not
just
the
dogs,
but
entire
1.25
has
just
gone
out
so
a
little
bit
less
I,
wouldn't
say
less,
but
yeah
less
reviewing
work
but
as
like.
You
know,
as
with
every
meeting
I
just
wanted
to
put
this
on
as
a
PSA
that
this
is
governed
by
the
kubernetes
code
of
conduct,
and
you
know
we
should
not
be
using
harsh
or
abusive
language
on
the
chat.
So
yeah
I
mean.
B
Are
there
any
discussion,
points
or
anything
else
that
you're,
you
know,
need
attention
from
a
perspective
or
for
reviewer
or
a
broker?
I
know
that
the
Hindi
localization
is
a
focus
Point,
but
other
than
that.
Are
there
any
specific
concerns
or
problem
areas
that
you
all
would
like
to
bring
up
in
this
circle?.
D
B
Okay,
so
I
I
will
give
it
another
couple
of
minutes
to
see
if
anybody
else
is
joining
or
else
I
think
it's
best
to
park.
The
call-
and
you
know
give
you
back
your
R
rather
than
sitting
on
a
call-
and
you
know
looking
at
each
other's
faces,
so
we'll
give
this
another
couple
of
minutes,
but
in
the
mean
pile,
if
there
are
any
questions,
I'd
be
happy
to
take
them
and
y'all
can
always
ask.
D
So
actually
I
was
working
on
the
localization
style
guide.
Right,
so
I
wanted
to
add
some
couple
of
Point
dedicated
to
the
grocery
items.
You
know
like
go
in
glossary.
There
are
people
using
some
time
to
use
English
word
over
there,
so
we
can
have
a
dedicated
column
or
dedicated
section
in
the
style
guide
for
the
grocery
one.
So
I
was
just
hoping
for
some
comments
and
suggestions
so
that
I
can
add.
B
So
if
I
understand
correctly
you're
saying
that
when
we
are
talking
about
glossary
items
in
our
documentation
right,
people
for
the
Hindi
localization
can
translate
into
the
Hindi
localization.
They
are
using
English
words,
and
what
essentially
is
the
cause
of
concern
is
that
we
need
to
have
like
a
sort
of
directive
that
everything
should
not
be
like
anglicized
for
the
sake
of
it.
C
B
Of
share
in
terms
of
the
angularization
of
you
know
terms
because
some
terms
are
meant
to
be
anglicized,
to
be
honest
because
cons
so
for
things
like
kubernetes
concepts,
for
example,
Core
Concepts,
you
wouldn't
want
them
to
be.
You
know,
translate
it
to
Hindi
in
the
sense
that
you
cannot
translate,
for
example,
who
believes
itself
cannot
be
translated
to
Hindi.
You
cannot
have
like
a
word
for
kubernetes,
but
then
same
with
other
stuff
as
well.
B
You
can't
really
there
are
certain
certain
terms
which
need
to
not
be
translated,
but
then
having
a
directive
Works.
Is
there
a
draft
that
you
are?
You
know
you
have,
and
you
want
to
sort
of
come
up
with
yeah.
D
I
have
been
working
on
the
style
guide
for
Hindi,
localization
and
recently
I
saw
some
comments
on
you
know
like
the
Hindi
grocery
terms
that
somewhere
peoples
were
confused,
that
which
term
should
I
translate
in
Hindi
and
which
not?
So
that's
why
I
wanted
to
add
something
in
the
block
start
guide,
yeah.
B
So
what
I'd
suggest
is
this
is
not
going
to
be
a
case
that
is
specific
to
just
Hindi
as
far
as
I
know,
because
even
when
your
localizations
come
in
right
when
they
start
doing
this
localization
effort
right
from
scratch,
like
we've
been
doing,
what
will
happen
is
that
you
know
people
are
going
to
run
into
the
same
thing.
So
continue
work
not
going
to
say
no
to
that.
B
But
what
I'd
also
request
is
that
you
bring
this
up
at
a
meeting
in
one
of
the
localization
meetings.
I
think
the
next
one
is
on
of
September
12th.
Sorry,
so
I
would
suggest
that
you
bring
this
up.
September,
12th
or
11th
I'm,
not
sure
so.
I'd
suggest
that
you
bring
this
up
at
the
meeting
as
well,
so
that
when
so
that
there
can
be
some
sort
of
formal
procedure
across
all
localizations
and
you
are
not
the
only
person
you
know
struggling
with
this.
B
It's
a
very
valid
point
and
I
think
we
should
sort
of
introduce
this
in
the
localization
side
of
things
as
well:
yeah,
September
12th.
Thank
you.
A
I
have
one
thing
on
this,
like
some
words
like
like
scheduler
some
words
like
schedulers,
these
like
when
you
there.
If
you
see
their
words,
are
like
anusu
check
and
I'm
of
the
opinion,
like
some
words
when
we
translate
in
Hindi.
A
We
know
that
this
means
this,
but
some
words
are
very
hard
to
click
like
in
my
daily
life,
I
mean
I
studied
Hindi
till
almost
10
9.,
so
I
I
never
knew
that
scheduler
is
called
anusu
check,
so
it
will
not
click
to
me
in
the
first
time
like
what
is
what
they
are
seeing.
So
I'm
of
the
opinion,
if
we
have
certain
words
like
these
and
people,
are
familiar
with
the
word
scheduler
more
than
Anu
suture,
so
I
feel
like
in
this
case.
A
If
we
feel
like
these
words
are
not
in
the
daily
user,
keep
clicking
as
much
so
I
think
it's
better
that
we
can
translate,
translate
those
words
instead
of
translating
it.
But
yes,
it
is
have
to
be
a
case
by
case
basis
and
we
have
to
develop
a
consent
service
amongst
all
the
contributors
and
other
localizations
yeah.
B
And
having
that
you
know,
guideline
really
helps
in
my
opinion,
like,
for
example,
like
you
said,
scheduler
right,
that's
one
of
the
examples,
but
when
you
go
across
localizations,
we
don't
know
like
I
I'm,
not
very
proficient
in
any
other
languages,
at
least
for
the
localization
with.
But
if
you
go
across
localizations.
B
This
is
something
that
you
know
will
Striker
court,
because
there
is
this
confusion
as
to
what
needs
to
be
translated
and
what
doesn't
so
having
a
set
guideline
on
what
can
and
what
should
fall.
Whether
the
remit
is
something
that
at
least
we
should
have
a
basic
idea
of
rather
than
you
know,
just
attempting
to
put
it
on
the
reviewers
or
put
it
on
the
people
who
are
writing
it.
B
So
if
they
say
that
these
things
do
not
be
to
be
translated
at
all
at
least
the
people
are
translating
it
does,
don't
need
to
actually
look
at
it,
as
you
know,
words
like,
for
example,
schedule
or
maybe
nodes
or
something
like
that.
But
when
it
comes
to
other
components,
we
can
go
on
a
Case
by
case
basis.
B
B
So
yeah
I
will
just
add
that
as
the
so
Aman
will
you
be
attending.
The
meeting
can
I
assign
that
action
item
to
you.
If
that's
possible.
B
Okay,
so
What,
if,
if
a
man's
not
able
to
do
it,
can
anyone
take
a
responsibility
of
at
least
putting
this
on
the
agenda
for
the
next
meeting?
If
not
isn't
about
it,
so
that
this
can
be
discussed.
B
Not
a
problem,
so
I
was
saying
that
is
it
possible
for
you
to
bring
this
up
in
the
next
localization
meeting.
Can
I
put
it
as
an
action
item
on
you
to
have
like
a
general
consensus,
driven
amongst
the
different
localizations
about
what
and
have
it
documented
somewhere.
D
B
So
so
yeah
so
right
anything
else
right.
B
All
right
added
the
agenda
agenda.
Sorry,
the
action
item
number
on
your
name
whenever
just
let
us
know
if,
if
there's
any
support,
that's
required
from
our
site,
if
you
can't
make
it
to
the
localization
meeting,
please
let
us
know
then
as
well,
so
that
we
can
at
least
add
this
as
a
conversation
topic
and
then
go
ahead
with
the
actual.
You
know
discussion
during
the
meeting.
If
none
of
us
are
present
so
yeah
I
think
that's
pretty
much
the
end
of
it.
B
All
right,
then,
so
I'll
hit
stop
on
the
recording
and
yeah.
Thank
you.
Everyone
and
have
a
great
day,
see
you
all
soon
bye.
Thank.