►
From YouTube: K8s SIG Docs Monthly APAC Meeting for 20230124
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
So
again,
hello,
everyone,
as
I
mentioned
before
this-
is
the
APAC
friendly
version
of
the
sick
talks
eating
it
happens
on
a
monthly
basis,
and
today
is
the
25th
of
January,
which
means
this
is
our
first
meeting
for
2023,
and
we
have
a
pretty
light
agenda
for
today.
So
I'll
paste
the
agenda
link
here
in
a
bit.
So
if
anybody
wants
to
go
ahead-
and
you
know
enter
their
names
on
in
there,
that
would
be
great
not
for
the
purpose
of
you
know
showing
off
or
anything.
A
But
just
you
know,
it'd
be
great
to
have
you
all
this
thing
and
also
it
helps
us
check.
If
you
know
you
all
have
got
the
relevant
taxes
and
stuff
like
that,
so
yeah,
so
I've
entered
the
docs
Link
in
the
chat,
and
this
is
the
agenda
for
today
and
we'll
be
walking
through
it.
A
As
you
know,
we
go
through
the
meeting,
so
I
will
also
start
sharing
my
screen,
but
if
you
all
notice
the
first
section
or
there
is
our
new
contributors
so
just
wanted
to
understand,
if
there's
anyone
new
here
or
if
everyone's
new
here
and
if
anybody
wants
to
introduce
themselves,
please
feel
free
and
I
can
go
first
because
I
I
pretty
much
have
done
this
too
many
times
so
I
don't
feel
as
scared.
So
I
am
one
of
the
sick
dogs,
coaches
and
lucky
for
me.
A
I
didn't
have
to
get
up
early
to
do
this
meeting
because
you
know
I
based
out
of
India
and
the
other
coaches
are
based
out
of
Europe
and
America
respectively,
which
is
why
you
can't
see
them
on
here.
A
So
if
you
all
attend
the
meeting
at
11,
30,
PM,
IST
or
12
a.m,
ISD
I'm,
not
sure
the
time
there's
one
that
that
occurs
on
a
bi-weekly
basis.
You
will
probably
get
to
see
more
of
them
as
well,
and
you
can
obviously
chat
with
us
on
slack
but
yeah.
That's.
A
I
have
been
working
in
the
kubernetes
ecosystem
for
around
three
years
now
so
mostly
talks
and
release
stuff.
So
yeah,
that's
me:
does
anybody
else
want
to
go
next.
B
Foreign
I'm
Rita,
so
I
work
as
a
software
engineer
at
Twitter
and
now
I'm
like
wanting
to
contribute
to
open
source
and
like
I,
am
a
like
a
receiver
or
user
of
kubernetes.
I
would
say
so,
but
yeah
definitely
want
to
contribute
to
open
source
so
looking
into
like,
which
is
the
right
stick
to
join
and
like
picking
tickets,
Open
tickets
out
there.
So
hello.
A
Great
to
have
you
here
and
I
hope
you,
you
know
find
you
know
good
issue
or
a
good
set
of
first
issues
to
you
know,
join
us.
I
think
you've
already
assigned
yourself
one
issue
in.
A
Don't
mistake:
yeah
yeah,
so
if
you
have
any,
you
know
questions
concerned,
please
you
know
make
sure
you
ask
them
on
the
issue
or
or
on
our
Channel
like
because
you
know
people
on
the
issue
might
necessarily
not
be
looking
at
the
issue
every
day.
So
if
you
know
you
want
attention
from
one
of
the
leads
or
approvers
reviewers,
please
make
sure
to
post
that
in
the
channel
as
well,
but
yeah
welcome.
Nevertheless,
and
I
hope
you
find
your
fitting.
C
Okay,
anybody
else
wants
to
go
next,
yeah
sure.
A
Oh,
you
don't
mute
that
happens
to
me
very
frequently,
you're
on
mute.
D
Sorry,
okay,
so
myself,
Rajesh
I'm
working
with
the
cloud
and
devops
engineer,
foreign.
A
Like
most,
the
community
is
very
welcoming
and
as
far
as
I've
experienced
the
past
three
years,
they're
extremely
warm.
So
again,
that's
my
biased
opinion,
but
I
have
been
a
part
of
the
community
for
three
years,
so
that's
obviously
very
biased
of
me
to
say,
they're,
warm
and
welcoming
that
I'm
in
a
part
of
it
already.
So
when
I
started
out,
they
were
very
warm
and
welcoming.
We
still
are
I
hope.
So,
if
you
have
any
questions,
you
know
I'll
I'll.
Also,
probably
you
know
when
we're
discussing
the
issues.
A
I'll
also
probably
show
you
all
some
good
first
issues
and
how
y'all
can
probably
sort
for
that,
at
least
in
K
website
and
y'all
can
follow
a
similar
process
in
the
other.
You
know
areas
of
the
project
that
you
want
to
contribute
to,
and
maybe
you
know
you
you
find
better
stuff
to
work
there.
I
don't
know
so.
I
can
just
show
you
the
process,
and
hopefully
you
know
you
can
take
it
from
there.
Yeah
absolutely.
E
A
It's
nice,
so
have
you
worked
on
any
issues
or
are
you
like
looking
for
first
issues
like
the
other
people,
other
people
are.
C
A
Can
find
stuff
in
other
areas
of
the
project
as
well?
If
you
are
interested
Basha,
do
you
want
to
introduce
yourself
because
I
feel
like
I
know
you,
but
do
you
want
to
introduce
yourself
can't
hear
you
can't
hear
you.
A
A
Okay,
oh
we
get
paid
for
all
in
the
meantime,
I'll
also
start
my
screen
share.
So
just
a
second
okay,
hi
Basha.
Any
luck
with
your
mic.
I,
don't
know
she's
still
connecting
for
you.
A
F
You're
not
Audible
yeah
yeah,
so
I'm,
very
sorry
for
taking
you
know
so
much
of
your
time
so
yeah,
my
name
is
bosta.
Even
I
am
in
college
as
well,
but
I
kind
of
work
as
a
junior
developer.
Advocate
at
this
company
called
Evie
marks.
I
work
remotely
and
to
be
I
mean
to
my
surprise.
I
haven't
literally
contributed
to
kubernetes.
Yet,
but
I
am
organizing
a
kubernetes
conference
internationally.
That.
F
F
Yes,
so
my
trajectory
is,
you
know
a
little.
You
know,
unlike
a
lot
of
different
people
who
start
from
grassroot
and
then
probably
go
to
that
particular
stage.
So
I'm,
just
trying
to
you
know,
play
the
roller
coaster
and
jump
from
this
to
this
place
to
that
place.
So,
hopefully,
after
having
you
know,
organized
this
stuff,
I
will
probably
want
to
get
back
to
the
grassroot
level
and
contribute
to
communities.
That's
the
kind
of
plan
right
now.
A
A
No
two
people
have
the
same
Journey
here
so
like
whatever
works,
for
you
works
for
you
and
that's
like
really
great,
because
you
know
for
a
lot
of
people,
traditional
contributing
works,
you
know
contributing
to
code
or
contributing
to
maybe
the
you
know,
Automation
and
stuff
like
that
and
even
dogs,
maybe,
but
it's
nice
to
hear
you
know
somebody
going
the
other
way
and
coming
back
and
that's
really
really
nice
to
hear
and
it's
wonderful
to
see.
A
You
know
more
Indians
and
more
people
from
the
Asian
diaspora
of
trickle
in,
as
you
know,
we
expand
our
contributor
base,
so
yeah,
so
I
was
just
gonna
share.
My
screen
before
you
came
in
so
I'm
gonna.
Do
that?
Because
I
will
forget
so
hopefully
everyone's
able
to
see
my
screen
right
now.
A
Righty
so
yeah
so
I,
if
you
all
want
to
and
if
y'all
wish
you
all
have
to-
or
you
all
can
enter
your
names
here.
A
If
you
don't
feel
like
it,
it's
okay,
not
a
huge
problem
and
just
to
go
through
the
you
know,
Basics
or
you
know
the
hygiene
checks
for
this
meeting.
The
first
thing
is
that,
since
this
is
a
meeting
for
the
kubernetes
project,
we
are
governed
by
the
kubernetes
code
of
conduct.
I
should
have
said
this
earlier
on
in
the
meeting,
but
this
is
something
we
explicitly
require
or
our
contributors
to
abide.
A
By
that
you
know
you
should
be
nice
to
one
another,
because
you
know
we
are,
you
know
part
of
a
larger
community.
So
that's
that's
one
thing
and
I
should
have
set
out
with
that,
but
I
kind
of
forgot,
because
I
saw
a
lot
of
new
faces
so
yeah.
So
that's
the
first
thing
and
as
some
of
you
all
would
have
already
experienced,
we
have
certain
people
reviewing
PR's
for
sick
dogs
on
a
weekly
basis.
I,
don't
know
if
any
of
you
all
have
experienced
that.
A
But
there
are
people
a
certain
set
of
people
known
as
PR
ranglers,
who
review
docs,
who
review
the
changes
that
have
been
submitted
to
the
website
or
to
the
docs
on
a
weekly
basis.
So
the
calendar
is
here
and
I
hope
it
opens
right
now.
A
Yes,
so
I,
hopefully,
are
able
to
see
a
GitHub
page
of
sorts,
so
approvals
within
sick
dogs
actually
take
this
responsibility
of
reviewing
and
approving
PRS
that
are
submitted
to
the
K
website
repository,
which
is
the
repository
that
we
manage
and
the
person
who's
responsible
for
reviewing
and
approving
PRS
this
week
is
Nate.
A
We
all
have
a
provision
for
Shadows
in
the
sense
that
you
can.
Actually
you
know,
tag
alongside
the
approver
and
reviewer
for
the
week
and
learn
more
about
the
process.
I'll
come
to
that
in
the
later
section,
but
that
is
a
provision
that
we
have.
So
this
week's
approver
is
neat
and
the
next
week's
approver
is
Anna
Jung,
and
these
are
you
know
their
GitHub
handles.
A
You
can
I
think
Nate's.
A
slack
handle
is
also
pretty
similar
and
he's
pretty
active
on
slack
as
well.
So
you
can,
you
know
you
feel
free
to
actually
reach
out
to
him,
but
I
would
highly
recommend
that
if
there
are
doubts
around
a
particular
PR
or
if
there's
a
PR,
that
requires
attention
instead
of
pinging
Nate
I
would
recommend
that
you
put
it
on
the
stick.
Talk
slack
Channel
so
that
you
know
everybody
has.
A
You
know
Clarity
that
this
requires
some
sort
of
attention.
So
that's
the
basic
thing
and
we'll
come
to
the
shadowing
bit
in
the
later
sections.
Like
I
said
before
another
thing,
like
I
said,
we
have
a
code
of
conduct
which
can
basically
be
summarized
as
being
nice
to
one
another
refrain
from
using
any
sort
of
harmful
language
or
abusive
language.
But
if
you
notice
that
or
there's
a
violation
of
this,
please
feel
free
to
actually
reach
out
to
the
kubernetes
code
of
conduct
committee.
A
The
links
here
you
can
reach
out
by
email
and
your
anonymity
is
definitely
protected,
and
this
is
you
know
at
an
event
like
you
call
or
a
meeting
like
a
sick,
docs
meeting
or
even
like
a
snack
meeting.
If
you
find
instances
where
this
thing
is
being
violated,
so
you
can
reach
out
to
them.
Okay,
so
that's
the
basic
updates
reminder
section.
A
Next,
we
come
to
the
agenda
for
today,
so
the
first
step
here
is
release
1.27.
So
as
most
of
y'all
are
aware,
or
if
you're
not
aware,
that's
also,
okay,
release
1.27
is
underway
as
of
January
first
week,
so
so
I
think
the
you
know,
team
building
process
is
actually
right
now
going
on
as
we
speak
and
the
Shadows
have
been
selected.
So
there's
not
much
work.
A
That's
actually
going
on
currently
with
respected
dogs,
but
there's
a
lot
of
you
know
the
admin
work
that's
going
on,
so
current
status
was
not
reported
because,
obviously
you
know
the
teams
are
being
formed
and
shadows
are
being
this
thing.
So
there
will
be
an
a
sync
report
on
this
particular
agenda
after
the
meeting
gets
over.
There's
something
we
respect
when
it
comes
to.
A
You
know
kubernetes
meetings
in
general
that
not
everybody
can
probably
enter
their
updates
at
the
time
when
you
know
we
put
out
this
agenda,
so
we
ensure
that
we
allow
for
an
async
mode
and
a
single
mode
of
contact
and
a
single
mode
of
update
if
need
next
up.
We
have
issues
in
PRS,
okay,
so
this
is
what
I
was
saying
when
I
was
saying
that
you
know,
we
have
a
couple
of
issues
and
I'll
probably
show
you
how
we
can
sort
out
for
good
first
issues.
A
So
the
first
issue
here
is
it's
already
actually
given
by
Shannon
as
an
update,
Shannon's
one
of
the
approvers
and
hopefully
I'm
able
to
open
this
open
it
all
right.
So
this
is
an
issue.
That's
there
in
K
website
was
reported
back
in
October
with
respect
to
you
know
not
just
one
area
of
the
website,
but
across
a
lot
of
the
content
that
we
have
on
there.
So
it
was
reported
by
Chris,
negus
and
he's
reported
that
there
is
a
problem
with
the
way
the
titles
and
headings
are
K.
A
You
know,
are
cased
on
K
website
and
there's
an
inconsistency.
Basically
now
we
recommend
using
title
case
as
per
our
documentation
style
guide.
A
Unfortunately,
that's
not
followed
because,
like
I
said
you
know
we
are
like
we
accept,
you
know
contributions
or
contributors
and
not
every
time
are
we
able
to
actually
check
or
is
the
approval
or
have
you
able
to
check
consistently
whether
that
style
guide
has
been
applied
or
not,
so
there
are
inconsistencies
and
the
recommendation
is
to
move
to
sentence
casing
now.
Why
sentence
casing?
A
Because
title
casing
is
hard:
it's
really
hard
to
figure
out
which
you
know
which
letter
needs
to
be
titled,
which
letter
needs
to
be
capitalized
in
a
particular
sentence,
and
it's
it's
difficult.
A
So
a
sentence
casing
is
much
simpler
and
it
will
help
us
get
closer
to
other
technical
documentation.
That's
out
there
for
Google
AWS
Etc.
So
this
is
one
thing
that
he
wanted
to
bring
up
as
part
of
this
meeting
and
he
had
like
put
it
as
a
comment
there,
so
I
made
sure
to
actually
add
it
in.
So
if
there
are
any
suggestions,
if
there
are
any
you
know,
you
know
concerns
or
any
thoughts
that
you
have
about
this.
Please
make
sure
to
go
and
check
the
GitHub
issue.
A
It's
linked
in
the
agenda,
documentation
and
one
more
thing
about
you
know
picking
up
an
issue
and
working
on
it.
A
This
I
think
Rita
is
aware,
because
I
wrote
it
in
a
comment
that
we
have
a
no
cookie
looking
policy,
which
basically
means
that,
even
if
a
particular
person
is
assigned
to
the
you
know,
issue-
and
you
know
another
person
wants
to
take
a
stab
at
it-
you
are
allowed
to
do
so.
We
will
be
reviewing
and
approving
dogs
chronologically,
which
means
that
whatever
is
easiest
to
merge,
will
be
given
preference.
A
Whatever
is
easiest
to
approve
and
merge
and
requires
the
least
amount
of
changes
from
a
reviewer's
perspective
will
be
given
preference,
but
we
will
be
reviewing
dogs
and
PR's.
Sorry,
we
need
reviewing
PRS
chronologically
any
questions.
I'll
stop
there,
because
I've
been
talking
for
quite
some
time.
Any
questions
there
yeah.
D
Hear
you
yeah
yeah
I,
understand
that
you
mentioned.
Maybe
there
is
no
cookie
licking
policy.
Maybe
multiple
contributors
can
work
on
PR
or
issue.
So
there's
the
other
way
around.
Multiple
approvers
or
reviews
can
also
approve
or
review
or
how
is
that
work
or
Only
One
reviewer
approved,
can
approve
issue.
A
Okay
yeah,
so
that's
a
very
good
question.
Thank
you
for
asking
that,
so
it's
so
for
K
website.
Just
to
let
you
understand
the
structure,
just
a
second.
C
A
So,
okay
website
I'll
just
go.
Let
you
understand
how
the
approving
reviewing
thing
works.
So
we
have
an
owner's
file
here
right
and
we
have
an
owner's
underscore
aliasis
file
here.
A
So
in
the
owners
you
specify,
who
are
the
owners?
Who
are
the
reviewers
for
each
particular
localization?
Now
localization
is
translation
of
the
talks,
but
there
are
overarching.
You
know.
Administrative
privileges
that
are
given
to
poachers
and
tech
leads
so
under
owners.
Whoever
is
there
at
least
we
are
able
to
approve
and
review
changes
across
localizations.
That's
not
limited
to
just
English
alone,
but
for
reviews
you
are
restricted
to
reviewing.
Only
for
your
particular
localization.
A
Now
contrast
is
with
the
your
owners
underscore
aliases.
You
can
see
that
there
are
blogs
reviewers,
blog
owners,
then
bunch
of
localization
reviews
and
owners.
Now,
localization
reviews,
reviewers
and
owners
will
only
be
able
to
approve
and
review
content
for
their
specific
language.
You
cannot
approve
and
review
content
for
other
languages,
but
anyone
who
has
a
review
and
approve
access
for
English
the
web.
The
main
website
can
actually
approve
a
review.
So,
for
example,
I'll
just
show
you
a
PR
here.
A
Let's
take
an
English
one
actually
so
that
it's
easier
to
understand
what
I'm
talking
about
so,
for
example,
this
is
a
sign
like
here,
it's
assigned
to
Tim
Natalie
and
someone
called
smart
Clayton.
Okay,
now
in
docs
what
happens
is
there
is
a
technical
review
that
goes
in
and
you
know
my
qualitative
review
and
if
it's
just
you
know
a
minor
change
in
the
quality
of
the
docs,
then
it's
just
quality
qualitative
review.
A
You
don't
have
to
go
through
a
technical
review
for
rephrasing
a
particular
sentence,
or
something
like
that.
So
obviously
that
is
not
required,
but
if
it's
a
technical
whole
new
technical
dock,
you
have
to
go
through
a
technical
and
or
non-technical
Revenue.
A
But
in
this
case,
if
I
am
supposed,
if
I'm,
if
Nate
is
the
you
know
reviewer
for
this
week,
PR
Wrangler
for
this
week,
he
can
actually
go
ahead
and
suggest
changes
this.
This
is
how
we
ensure
that
the
load
stays
distributed,
because
otherwise
these
three
people
I
mean
only
the
reviewers
who
are
mentioned
in
sick
docs
and
reviews
will
be
reviewing
everything.
A
So
we
give
the
option
of
actually
reviewing
the
content
to
literally
anyone,
but
the
actual
lgtm
and
approved
commands
that
are
required
that
we
only
allow
these
reviews
reviewers
to
give
and
other
reviewers
who
are
part
of
the
pr
Wrangler
skin,
actually
also
give
the
lgtm
and
approved
command
based
on
their
schedule
or
based
on
whether
or
not
they
have
bandwidth
that
week
to
help
out
I
know
that
was
a
lot,
but
did
that
answer
your
question?
A
Tldr
you
can
there
will
be
other
people
who
come
in
and
say:
okay,
you
need
to
change
that
stuff.
Okay,
you
need
to
change
that
stuff
in
a
particular
file.
Other
people
can
come
and
do
that,
but
that
depends
on
their
bandwidth.
It's
allowed
but
dependent
on
their
bandwidth
did
I
clarify
yeah.
D
Absolutely
so,
basically
the
maybe
many
reviewers
can
comment
like
looks
good
to
me
or
something
like
that,
but
mainly
who
is
the
BR
Wrangler
for
that
particular
week?
A
Not
necessarily
so
suppose,
suppose
you
know
Tim
actually
signs
off
on
this.
This
cannot
be
signed
off
because
it's
in
draft.
So
let
me
be
clear
on
that.
So
it's
in
draft,
so
you
can't
sign
off
and
say:
okay,
I
can
merge
this
PR,
but
suppose
this
were
okay
and
it
was
like
a
minor
change
of
a
link
and
Tim
was
tagged
on
it
and
he
got
to
it
first.
He
can
say
that
you
know
lgtm
approved.
A
We
can
merge
this,
but
typically
we
shift
the
owners
onto
the
pr
Wrangler
so
that
it's
not
just
you
know
the
reviewers
were
tagged
on
this
reviewing
it
continuously,
because
the
number
of
reviewers,
if
you
saw,
are
like
maybe
10
people
right.
So
it's
difficult.
So
that's
why
we
have
like
something
I'll
talk
about
and
as
the
shadow
program
wherein
you
can
get
involved
and
provide
informal
reviews
and
you
know,
help
actually
lessen
the
loaders
so
yeah
did
it
make
sense
or.
A
No
okay,
so
I
will
just
show
you
all
how
to
check
for
good
first
issues,
there's
something
called
as
a
yellow,
clo
I,
don't
know,
monitor
something
like
that.
That
also
helps
it,
but
typically
anything
labeled
as
a
good
first
issue.
Here,
like
the
one
on
this
thing,
you
can
just
sort
by
labels.
That's
how
I
normally
do
all
right.
So
this
is
not
exactly
coming.
Okay,
it's
just
good.
First
issue:
I'm,
sorry,.
A
So
this
is
a
good
first
issue:
there's
a
label
that
you
have
you
can
just
sort
by
it
and
you
can
see
the
available
good
first
issues
in
a
particular
repository
now.
I
understand
that
there
are
like
600,
odd
issues
here
and
some
of
them
I
worked
on
triaging
them
last
week,
but
again
not
fully
completed
so
we're
working
on
actively
tagging
these
with
with
you
know,
good
first
issues
or
help
wanted
labels
so
that
you
know
people
can
appropriately
pick
up
but
yeah.
A
This
is
the
way
you
can
actually
check
out
across
any
repository
to
be
honest
in
kubernetes
or
whether
there
are
any
good
first
issues
or
not.
Does
that
make
sense.
B
So
I
just
had
a
question.
I
was
reviewing
this
like
looking
through
this,
but
there
are
like
some
issues
which
are
very
old
so
like,
and
it's
not
sometimes
it's
like
you
know.
This
is
December
2013
2021,
yeah.
B
Like
sometimes
like,
you're,
not
sure
whether
it's
still
relevant
now
or
like
what?
What
needs
to
be
done
about
it,
yeah.
A
Good
question
because
I
went
through
the
same
thing
last
week:
I
was
the
pr
Wrangler
last
week,
so
there
were
a
bunch
of
issues.
In
fact,
the
one
that
you
picked
up
I
think
you
took
the
glossary
entry
for
quantity,
or
did
you
take
something
else,
but
I
don't
remember.
So
if
you
there
were
other
issues
as
well.
Those
ranging
back
from
2017
I
I
was
not
part
of
the
project
and
not
know
kubernetes
existed
back
then
so.
A
A
Actually,
you
know
ping
the
person
on
GitHub
like
ask
for
the
issue
basically,
but
also
tag
the
person
on
GitHub
and
ask
if
you
know
those
people
on
in
person,
you
can
actually
ping
them
on
slack,
but
I
don't
know
if
you
all
know
a
lot
of
people
here.
So
what
I
normally
do
is
talk
to
them
on
GitHub
and
get
a
consensus
on
the
issue
itself.
A
So
I
was
able
to
close
that
I
think
four
to
five
issues
just
like
that,
because
they
were
back
fixes
that
were
required
and
not
documented
properly.
In
some
earlier
kubernetes
version
folks
had
brought
it
up
on
the
docs
website,
but
now
they
are
no
longer
bugs
because
they
have
been
fixed
in
the
later
version.
So
you
need
to
ask
on
the
GitHub
issue
itself:
there's
no,
you
know
improper
way
or
proper
way
of
doing
it.
A
We're
also
you
know,
thinking
of
introducing
a
person
just
like
the
pr
Wrangler
for
issue
or
wrangling
as
well,
because,
as
you
can
see,
there
are
around
600
plus
issues
here
and
they
just
keep
on
getting
you
know
moving
it
just
keeps
on
getting
more
and
more
every
day,
so
we're
trying
to
do
that.
But
there's
it's
not.
It's
not
completely
shaped
up
correctly
right
now.
A
So
when
there's
more
on
that,
I
can
let
you
know
later,
but
right
now,
the
best
way
to
go
about
it
is
to
actually
reach
out
to
the
person
on
the
issue,
tag
the
issue
Creator
and
see.
If
that's
something
that
is
still
a
problem
or
still
an
issue
and
go
about
doing
it,
does
that
answer
your
question?
Yeah.
C
E
In
in
issue,
there's
a
label
called
needs
triage
accepted.
So
what
does
it
means.
A
Triage
is
basically
so
when
okay
I'll
get
I'll,
give
you
the
basic
def
difference
between
the
two.
When
we
accept
when
we
have
the
label
triage
accepted
right,
it
means
that
sigdox
is
ready
to
move
forward
with.
You
know,
accepting
contributions
to
that
particular
issue.
A
Okay,
if
you,
if
you
see
the
needs
triage
one
which
are
like
the
first
three
here,
we
we
have
not
reviewed
it
yet
or
the
pr
Wrangler
or
who
have
probably
it's
the
pr
Wrangler
who's,
also
supposed
to
review
it.
So
Aztec
docs
we
haven't
decided
whether
or
not
we
want
to
actually
support
the
you
know
further
enhancement
of
this
particular
issue
on
our
website,
so
it
could
be
a
support
case,
for
example
like
this
one
encrypting
and
NFS
volumes
data
address.
A
A
Whether
or
you
know
particular
thing
in
the
documentation
is
missing
or
if
a
link
is
inappropriate,
or
you
know
this,
so
if
V
that's,
why
Tim
has
actually
mentioned
that
it's
not
the
right
place
for
support
requests,
and
if
that
is
the
case,
you
need
to
actually
just
you
know,
ask
on
server
fault
or
post
your
question
on
this
slack
or
on
the
discuss
kubernetes
Forum.
A
So
we
have
explicitly
said
in
this
case
that
it's
a
support
issue,
but
and
that's
why
we
cannot
add
the
triage
accepted
label,
because
we
can't
do
anything
in
this
case.
It's
actually
somebody
else
who,
as
a
community,
need
to
needs
to
come
together
and
answer
that
person's
question,
because
Doc's
website
is
only
catering
to
the
content
of
the
website.
We
cannot
be
the
support
personnel
as
well,
but
when
you
say
triage
accepted,
what
happens
is
this?
This
thing
goes
ahead
and
we
are
inviting
contributions
for
this.
A
So
if
you
will
see
the
discussion
here,
Tim
has
actually
said
that
we
we
are
willing
to
actually
do
this.
How
about
you
know
we
do
it
in
this
particular
way
and
if
there
are
any
suggestions
or
if
anyone's?
Actually
you
know
if
the
requester
actually
says
that
we
need
to
do
it
in
this
particular
way
and
any
other
further
input
is
given.
You
actually
put
it
up
open
for
contributions,
so
that's
the
basic
difference.
Did
that
make
sense,
or
do
you
need
further
clarity.
A
Okay,
so
we
have
our
last
agenda
item
to
get
to
which
is
like
I,
said,
the
pr
Wrangler
Shadow
rule,
so
y'all
already
saw
the
pr
Wranglers
right,
so
they
are
the
people
who
are
responsible
for
reviewing
and
approving
PR's
for
a
week
and
we
have
a
calendar,
that's
prepared
at
the
start
or
actually
not
at
the
start
of
every
year.
A
Let
me
be
honest:
we
prepare
it
at
the
end
of
the
previous
year
so
that
we
have
like
a
calendar
ready
for
the
next
year
to
actually
follow
when
it
comes
to
approvals
and
reviewers
reviews.
Sorry,
not
reviews
so
pure
is
the
2023
schedule
and
you'll
notice
that
there's
a
shadow
column.
Now
what
does
a
shadow?
Do
it's
an
apprenticeship,
but
it's
not
a
paid
one,
just
just
letting
you
all
know
out
there,
but
it's
not
a
paid
one.
A
What
you
basically
do
is
you
work
alongside
the
pr
approver
for
the
week
figure
out?
What
is
the
process
behind
a
PR
approval
and
what
what
are
the
things
that
you
might
need
to
look
out
for?
And
you
know
what
are
the
things
you
are?
You
know
supposed
to
suggest
what
are
the
actual
things
you
can
review
like
right
now.
I
said
right
that
when
you're
an
approver,
if
you're
not
a
co-chair
or
really
technically
you
don't.
A
Actually
probably
you
won't
look
at
the
localization
PR's
unless
you
are
also
actively
working
with
the
localization.
So
if
so,
Shadows
often
like
people
who
join
in
our
shadows
often
don't
know
that,
and
that
is
what
you
know.
This
program
gives
you
it's
just
a
one
week
thing,
but
you
can
obviously
sign
up
for
more
than
one
week
and
Shadow
different
people
understand
the
process
from
different
people.
A
If
you
want,
and
the
only
thing
is
we
don't
function
during
kubecon
EU,
because
very
obviously
we're
all
at
kubecon
or
at
least
participating
virtually
so
the
week
of
kubecon
we
are
not
there
and
Christmas
holidays
is
something
again.
Christmas
and
Thanksgiving
are
again
other
two
holidays
that
we
don't
actually
work
during.
So
that's
like
a
free-for-all.
Buffet,
you
can
you
you
can,
if
you're
a
reviewer
and
if
you
have
spare
time
you
can
go
and
actually
work
on
it.
A
But
again
we
try
and
you
know
not
overload
any
specific
person
with
a
lot
of
work.
So
if
the
shadowing
program
interests
you
you'll
want
to
learn
more
about
how
to
actually
review
and
approve
PRS
and
go
beyond,
like
you
know,
just
contributing,
please
feel
free
to
reach
out
to
me
or
Natalie
and
Ray
are
the
other
two
coaches,
please
feel
free
to
reach
out
to
them
as
well
or
Abby.
Is
the
localization
lead,
so
we
before
actually
any
of
the
leadership,
can
actually
help
you
with
editing.
A
This
talk
so
feel
free
to
reach
out
to
us.
If
you
have
a
particular
week
in
mind
and
we'd
be
happy
to
enter
you
all
in,
we
are
looking
at
in
increasing
the
number
of
Wranglers
and
approvers
that
we
have
in
our
list
so
as
to
cater
to
the
number
of
issues
that
come
in,
as
you
already
saw
so
yeah.
B
So
one
question
is
like:
is
it
like,
for
someone
is
not
contributed
yet?
Can
they
become
they
participate
in
this
program?
Oh.
A
Sure
it's
not
like
a
so
again.
Let
me
be
very
clear:
anybody
can
contribute.
There's
no
problem
at
all.
You
will
have
to
get
in
touch
with
your
to
the
assigned
person,
like
suppose,
you're
checking
for
the
next
say
next
week.
You'll
have
to
get
in
touch
with
Anna
and
figure
out
her
process
and
understand
what
how
she's
going
to
go
about
her
PR
reviewing
thing.
A
So
everybody
has
a
different
process.
I
have
a
different
process.
Somebody
else
has
a
different
process,
so
you
go.
Are
you
can
you
can
definitely
do
that
and
you
don't
need
to
be
an
organizational
contributor
by
organizational
contributor.
I
mean
that
you
don't
need
to
be
a
part
of
the
kubernetes
organization
on
GitHub.
A
You
can
informally
give
your
reviews
you
only
can't
you
know
your
LG
TMS
will
actually
not
be
accepted
by
the
bot.
That
is
the
only
thing,
but
your
reviews
will
still
very
much
be
valid.
You
can
do
it,
so
there
is
no.
You
know
I
have
to
complete
10
reviews
to
get
this.
That
is
not
the
case.
D
Yeah
yeah,
please
go
ahead,
yeah!
Okay!
Is
it
something
like
only
one
Shadow
can
be
with
a
Wrangler
or
okay.
Maybe
multiple.
A
A
So
we
recommend
one
Shadow,
but
you
know
again
if
the
Wrangler
is
ready
to
take
on
more
that's
another
thing
or
typically,
we
recommend
one
Shadow
only
so
that
you
know
it's
it's
not
it's
not
overloading
them
as
well,
because
you,
you
have
to
work
with
somebody
right
and
your
LG
TMS
and
approves
are
not
actually
going
to.
A
You
know
trigger
the
bot
to
actually
get
the
pr
merge.
So
somebody
has
to
actually
do
that
and
Coach
you
to
how
as
to
how
this
process
works.
So
recommendation
is
one
to
one,
but
if
the
Wrangler
is
willing
to
take
on
more
that
works
for
us
as
well,
like
it's
great
for
us
like
the
more
the
merrier
for
us,
but
yeah.
D
Understood
so
maybe
can
you
give
some
insight
about
how
we
were
shadowing
with
I
mean
I
saw
that
you
are
sharing
with
nitish
right,
I
mean
so
how.
A
Yeah
so
nadish
was
shadowing
me.
Yes,
sorry
yeah,
so
yeah
I
mean
it's
just
the
same,
so
we
connected
over
slack
and
he
asked
me
certain
questions
he's
already
contributing
quite
a
bit
to
the
K
website
repository,
so
he
had
context
about
whatever
I
was
speaking.
A
So
if
you
don't
have
context,
it
becomes
only
slightly
more
difficult,
not
to
scare
anyone,
but
it
becomes
slightly
more
difficult
to
explain
so
then
so
when
it's
easier
to
explain
to
people
who
already
have
the
context
around
contributing
and
what
is
acceptable
and
what
is
not
acceptable.
You
all
know
the
bot
commands.
You
all
know
what
actually
is
lgdm
and
approve
and
stuff
like
that.
So
you
all
know
that
it's
easier.
A
So
he
connected
with
me.
He
asked
me
what
were
the
things
that
were
required
and
then
we
we
went
through
the
issues
and
the
pull
requests,
because
last
week
again
there
were
600
issues.
You
all
won't
believe
it
it's
still
at
600,
but
new
issues
have
come
since
then,
but
yeah,
the
pull
requests
were
down
to
250s
and
I
was
very
happy
and
over
the
weekend
it
just
again
went
up
so
yeah.
A
That's
that's
how
it
works,
so
you
connect
over
slack
or
you
connect
to
a
resume
or,
however,
it
works
for
you
and
you
work
a
sync
as
far
as
possible
because
it's
obviously
not
possible
for
everyone
to
jump
on
Zoom.
At
the
same
time,
people
could
be
working
in
different
time
zones
as
well
so
yeah.
So
in
fact
the
shadow
for
this
current
week
is
in
India
and
the
other
person
is
in
Mountain
Standard
Time.
So
it's
I
think
he's
in
market
Standard
Time
date,
but
yeah.
A
They
are
in
two
different
time
zones.
It's
obviously
not
always
possible,
but
since
I
think
priyanshu
is
not
as
well
versed.
They
were,
you
know,
going
to
jump
on
a
call
and
catch
up
and
figure
out
how
to
do
it.
So
approaches
are
different,
like
I
said
so,
with
more
context,
it's
easier
to
connect
with
lesser
context.
A
It's
you
know,
you
have
to
explain
it
in
a
particular
way,
so
that
the
other
person
also
understands,
because
we
want,
for
you,
know
you
all
to
understand
and
gain
something
out
of
the
experience.
D
C
Not
a
problem
anything
else.
A
Can
sign
up
for
multiple
weeks?
That's
not
a
problem.
You
can
sign
up
against,
because
again,
subsequent
weeks
are
also
by
different
people
right
like
we
don't
give
the
same,
we
don't
give
the
same
person
two
weeks.
Consequently,
it's
because
you
know
it,
we
are
having
us
a
lot
of
work
and
it's
it's
a
lot
of
owners,
because
you
have
to
go
constantly
back
and
forth
with
a
lot
of
people
now,
310
PRS
are
there
out,
of
which
I
think
around
110
will
be
English.
A
I
could
be
like
more
or
less
out
of
just
a
second
I
can
just
show
you
it's
around
110
PRS,
which
will
be
around
you
know,
English
related,
so
you
have
to
review
all
of
those
and
some
are
like
age-old
PR's
again
because
they
are
so
see
112
PRS
here
which
are
open.
So
you
have
to
go
back
and
forth
which,
with
each
of
these,
sometimes
you
need
to
on.
A
There
will
be
released
PRS
that
come
in,
so
it's
not
going
to
be
the
same
from
one
week
to
the
next
week.
It's
going
to
be
different
people
different
set
of
PR's
coming
in
it's
going
to
be
a
different
experience
every
week
and
it's
going
to
be
an
overload
if
the
same
person
Works
two
weeks
because
imagine
the
amount
of
the
same
conversations
they
have
to
have
with
a
different
set
of
people.
A
So
that's
why
it's
normally
recommended
that
you
know
the
same
person
doesn't
do
it
twice,
but
if
there's
an
emergency
again
unavoidable
emergency,
personal
emergency,
somebody
or
the
other
takes
over
for
like
and
may
do
subsequent
weeks
as
well.
So
there
have
been
cases
like
that
last
year
because
of
the
pandemic,
but
in
general
we
don't
recommend
that
you
know
the
same
person.
Does
it
twice,
so
you
can
definitely
Shadow
against
two
different
people
in
subsequent
weeks
and
see
how
it
works.
Artsy.
D
A
If
there
are
I
mean
it's
not
like,
you
know,
I
I'm,
gonna,
stop.
The
conversation
here
well
can
definitely
reach
out.
On
slack
on
the
sick
dog
slack
everybody's
nobody's
going
to
bite,
you
all
I
promise
and
we
try
and
answer
as
many
questions
as
we
can
time
zone
and
work
permitting
and
yeah
I
mean
the
conversation
doesn't
have
to
stop.
Is
the
tldr
for
everything.
C
A
Any
other
questions
like
going
once
going
twice
because
I
don't
want
to
keep
you
all
from
the
rest
of
your
day
and
I
know
that
giving
your
12
minutes
back.
Might
not
really.
You
know
help
you
all
start
a
new
side.
Hobby
I
can
understand
that.
A
But
oh
yeah,
you
had
a
you,
can
type
it
out
if
you
need
the
answer
to
it.
A
So
borsha
had
a
question
and
the
mic
start
working
so
she's
gonna
ask
question
and
chat.
A
Also,
like
I
said
before
this
is
going
to
be
available
on
the
kubernetes
YouTube
channel,
so
y'all
can
watch
the
recording
or,
if
you
all,
don't
want
to
ask
questions
so
I
mean
if
y'all,
don't
wanna,
ask
the
same
questions
again.
Rather,
I
was
taking
off
okay
of
adding
yeah,
so
I
think
there's
already
a
Bengali
localization
for
the
docs.
By
the
way
I
mean
it's
not
like
in
in
production,
like
normally
people
say
it's
not
live
it's
not
life.
A
That's
the
reason
why
you're
not
able
to
find
it
you
can
join
just
a
second
I
will
give
you
the
contact,
I.
Think
it's.
A
That's
the
person
who
started
it.
I
will
give
you
the
slack
Channel
and
you
can
just
join
here.
They
have
been
working
on
getting
stuff
in
in
terms
of
content,
so
we
are
not
yet
ready
with
the
minimum
amount
of
content,
that's
required
for
the
localization
to
go,
live
like
you
can't
just
randomly
say:
I
want
to
create
a
localization
and
not
have
content
right
like
just
the
front
page
will
not
make
it
worth
it.
A
You
have
to
have
some
content
along
with
the
translated
you
know
stuff,
so
that
is
the
channel
you
get
to
join.
You
have
to
join
if
you
need
to
contribute
to
Bengali
localization,
just
say
that
you
know
you
came
to
know
about
this
from
this
meeting
and
you
all
are
interested
in
contributing
I'm
sure
you
know
the
lead
is
more
than
happy
to
actually
appoint
you
all.
A
So
the
I
I'll
actually
also
paste
the
minimum
localization
requirements.
Localization
sorry
yeah
I
can
definitely
go
for
whichever
language,
but
it's
recommended
that
when
you
actually
start
with
a
new
localization,
you
need
to
have
at
least
two
people
along
with
a
bunch
of
contributors,
so
that
you
know
you
can
approve.
A
So
if
there's
just
one
person
that
person
will
have
to
contribute
and
review,
which
is
not
like
a
proper
procedure
right,
so
you
need
to
have
two
people,
so
one
person
will
at
least
write
the
content
and
the
other
person
will
review
it
and
the
other
person
is
writing
the
content.
The
first
person
reviews
it
that
that
needs
to
be
a
balance.
And
of
course,
then
you
grow
your
community
by
attracting
like
like-minded
folks.
A
So
this
is
the
localization
documentation
that
we
have
but
I
think
I've
shared
the
channel
just
up
here,
so
I'll,
just
re-share
it
it's
hash.
Kubernetes
docsdn,
on
the
kubernetes
slack
so
should
be.
The
slack
channel
is
the
same.
There's
no
different
slab
channel,
it's
kubernetes,
Slack,
okay,
so
yeah.
A
B
Yeah,
please
so
to
pick
any
items
in
the
existing
localization.
It
should
basically
come
across
as
like
a
issue
on
on
the
kubernetes
website.
A
I
didn't
get
you
I'm.
Sorry,
basically,.
B
Like
if,
if
I'm
interested
in
like
contributing
to
your
localization,
where
do
I
look
for
open
institutes
in
the
same
kubernetes
website,.
A
Rights
so
localization
Works
slightly
differently.
We
obviously
also
put
out
issues
there,
but
localizations
are
supposed
to
mirror
your
documentation
right,
but
they
don't
start
out
as
that.
That
is
why
we
have
the
concept
of
minimum
content
that
is
required
for
a
localization
to
go
live
so
typically,
localizations
that
have
just
started
like
I
can
give
you
the
example
of
Hindi
localization
that
started
last
year,
also
an
approver
on
that.
A
But
the
thing
is
that
we're
expanding
the
content,
but
for
more
form,
localizations
or
more
older
localizations
I,
would
call
them
old,
but
localizations
that
have
been
there
for
quite
some
time
like
Korean
or
Chinese.
They
have
their
content
almost
in
place,
so
they
tend
to
have
issues
with
their
content.
A
You
can
obviously
check
out
that,
but
if
you
are,
but
typically
when
Hindi
puts
out
issues
it's
more
around,
actually
you
know
contributing
new
content
like
translating
existing
content,
English
content
to
Hindi
content
and
putting
it
on
it's
not
going
to
be
like
bug,
fixes
or
stuff
like
that,
and
if
you
don't
notice
a
page
in
Hindi
and
you
want
it
in
Hindi,
you
can
yourself
also
file
an
issue
against
the
K
website.
So
anybody
is
welcome
to
file
an
issue.
A
If
you
know
you
don't
find
a
page
in
a
particular
localization
and
ask
people
to
work
on
it
if
the
localization
exists,
but
typically
that's
how
localizations
work
and
in
the
in
the
issues
section
right
now,
you
can
see
a
lot
of
localization
related
issues
as
well.
There's
a
Brazilian,
Portuguese
Brazilian,
Portuguese
issue.
There
is
a
mandarin
issue.
There
are
a
lot
of
issues
related
to
French,
Italian
stuff,
like
that.
A
So
if
the
existing
content
hasn't
has
a
problem,
you
can
submit
an
issue
yourself
and
work
on
it.
Adam
localizations
typically
focus
on
keeping
the
content
updated
and
expand
their
current.
You
know
repertoire
of
content,
because
we
very
much
struggle
as
an
approval
and
as
a
lead.
I
know
that
we
very
much
struggle
getting
content
translated
to
the
language
itself.
It's
very
difficult
because
you
need
to
be
very
fluent
with
the
language.
So
that's
that's
the
thing
does
that
answer
your
question,
though
yeah.
A
Right,
that's
a
good
question,
so
Hindi
localization
content
like,
but
what
I
would
do
is
if
I
were
to
start
out
firstly
check.
If,
under
the
issues
section,
you
can
find
out
anything
with
a
label
language,
so
we
tag
our
localization
related
efforts
at
least
the
live,
localization
related
efforts
with
the
language
code
and
the
language
slash
the
language
code
So.
Currently
there
are
27
open
issues
for
Hindi,
and
you
know
there
are
there
I
think
all
of
them
are
triage
accepted
ones.
A
So
you
all
can
take
a
stab
at
that.
If
you
all
want
and
see,
if
you
know
there
are
and
check
if
there
is
another
issue
and
if
you
all,
you
know
with
the
website
in
general
and
file,
an
issue
yourself
like
if
you
see
a
spelling
error
or
a
grammatical
error,
or
something
like
that,
you
can
do
that
as
well,
and
otherwise
you
can
just
reach
out.
A
You
can
just
check
a
particular
page
on
kubernetes
English
website
and
see
if
it's
there
in
Hindi
and
if
not,
you
can
directly
offer
to
translate
it
like
that's
the
two
ways
of
going
about
it.
I
know
the
second
way
is
comparatively
longer,
but
there's
only
so
much
you
can
do
like
the
person
who's
running
like
apart
from
me,
the
person
who's
running
the
localization
for
Hindi
he's
the
one
who
started
it.
Honestly,
speaking
I'm
just
like
tagging.
The
item
he's
a
student
himself,
so
he's
really
not
like.
A
He
also
doesn't
have
like
the
bandwidth.
So
it's
so
it's
a
lot
of
pressure
to
keep
up,
and
so,
if
you
are,
you
know
if
you
want
to
actually
translate
you're
very
much
welcome
and
you
can
just
file
an
issue
and
get
started
with
the
translation.
You
don't
even
need
to
ask.
You
just
need
to
check,
though,
if
the
work
is
already
being
done.
You
don't
want
to
do
duplicate
stuff.
A
We
have
a
no
cookie
licking
policy,
but
I.
Don't
think
any
one
of
us
here
likes
doing
duplicate
work
so.
B
A
All
righty
so
I
think
we're
just
about
closing
time
here.
If
there
are
any
other
questions,
please
feel
free
to
reach
out
to
me
on
slack
or
you
know
you
can
also
reach
out
to
the
sick
dogs
channel
on
slack
happy
to
help
wherever
and
see
you
at
our
next
meeting.
Hopefully.
D
A
Yes,
yes,
you
can
actually
voice
that
concern
here
for
the
Tamil
localization
I'll
give
you
the
we
have
a
localization
specific
Channel,
also
stick
docs
localization.
So
that's
the
sub
project.
The
main
website
is
like
one
entity
within
the
kubernetes
project.
This
is
a
sub
project
within
the
main
website,
so
you
can
reach
out
here.
A
We
have
our
lead
Abby,
who
is
also
working
out
of
EST
if
I'm
not
wrong,
but
she
will
respond
or
I
can
respond
or
anyone
else
will.
That's
not
a
problem.
You
can
reach
out
definitely
and
we'll
try
getting
it
off
the
ground
if
everything's
far
suitable.