►
From YouTube: K8S SIG Docs Monthly APAC Meeting for 20220727
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
Up
all
right
so
good
day,
everyone
hope
you
are
all
doing
fine.
This
is
the
APAC
friendly
meeting
for
sick
talks
and
it's
held
every.
You
know
fourth
Wednesday
of
the
month
and
today
is
the
27th
of
July.
So
obviously
this
is
the
APAC
friendly
meeting
for
July,
and
that
being
said,
let's
just
you
know,
get
some
ground
rules
in
order.
The
first
thing
is
that
you
know
your.
A
This
is
governed
by
the
kubernetes
code
of
conduct,
which
basically
means
that
you
know
abusive
or
harmful
or
any
sort
of
language
that
is
targeted
at
coming.
Another
person
is
not
tolerated
and
will
be,
you
know,
dealt
with
per
the
code
of
conduct
and
also
that
you
know
we
request
each
of
our
members
to
be
nice
to
one
another.
A
So
that's
that's
the
basic
gist
of
it.
So
this
follows
the
code
of
conduct
and
we'd
request
that
you
abide
by
it.
So
what
so?
Because
that
is
out
of
the
way
I
am
now
going
to
you
know
open
up
the
meeting
to
our
agenda
items
and.
A
A
Yeah
so
hopefully
everyone's
able
to
see
my
screen
right
now,
cool,
so
I
think
a
lot
I
see
a
lot
of
familiar
faces
here,
but
I
think
Luigi
or
the
new
contributor,
and
if
you
feel
comfortable
enough,
please
go
ahead
and
introduce
yourself-
and
you
know
tell
us,
you
know
what
your
aims
are
with
respect
to
contributing
to
sick
talks
and
stuff,
like
that.
Yes,.
C
I'm
is
the
first
time
for
me
that
I'm
I'm
trying
to
join
this
community.
Yes,
I,
have
experience
with
kubernetes,
but
I
would
like
to
improve
this.
Yes,
improve
the
knowledge
that
I
have
about
it
and
maybe
I
I
will
able
to
contribute
more.
So
is
it
my
I'm
a
Java
developer,
but
I
am
very
good
at
Bosch
as
well.
So
yes,
I
I'm
learning
golang,
and
this
is
my
journey
right
now.
A
B
A
You
need
help
please
voice
out.
We
have
a
new
contributor
Ambassador
who
can
help
you
out
he's
not
there
on
the
call
today,
but
we
can.
You
know
point
you
to
him
and
he
can
help
you
out
on
your
journey
so
and
we
have
a
contributor
guide
as
well.
If
you
need
the
link
to
that,
I'll
paste
it
shortly
after
I
stop
sharing
my
screen,
but
okay
there's
a
contribution
guide
as
well.
You
can
read
through
that.
A
So
right
any
other
new
contributors
on
the
call.
I
don't
see
any
so
please,
you
know,
feel
free
to
take
the
mic
and
introduce
yourself.
B
D
D
I
mean
I
didn't
participate
in
this
this
18
meeting
for
a
long
time.
So
it
is
very,
very
recent
to
joining
of
this
meeting
so
I
hope
to
say
hello
to
every
folks,
and
if
you
have
any
question
related
with
localization,
you
can
feel
free
to
ask
to
me.
Thank
you.
A
Thank
you
Circle,
and
it's
it's
a
pleasure
that
you
can.
You
can
drop
by
so
hi.
A
Since
nobody's
taking
that
opportunity,
I
am
going
to
our
next
agenda
item
for
today,
which
is
the
updates
and
reminder
section
so
because
there
was
sort
of
blip
in
the
way
we
got
the
Rota
formed
this
time
around.
We
do
not
have
a
PR
Wrangler
for
this
week,
so
the
leads
coaches
and
the
folks
on
the
approvers
list
are
going
to
be
wrangling
PRS
for
their
convenience
and
are
going
to
provide
feedback.
A
But
good
news
is
that
next
week
we
have
Zach
as
rpr
rankler
and
we're
back
on
schedule,
so
you
should
expect
more
streamlined
feedback
coming
in
starting
next
week,
but
this
week
it's
going
to
be,
you
know,
basis,
convenience
and
basis
a
lot
of
our
you
know
Comfort
level.
So
please
expect
you
know,
infrequent
replies,
but
we're
trying
to
get
to
as
many
PRS
as
possible
and
one
PSA,
since
there
are
a
few
folks
who
might
not
be
aware
of
this.
A
If
you
aren't
aware
of
what
is
the
pr
Wrangler
for
this
week
and
you
are
actively
working
on
PRS,
please
make
sure
you
check
the
pr
or
Wrangler
shift
by
navigating
to
the
link
on
the
agenda.
Documentation,
fun
fact
is
also
that
you
can
sign
up
to
actually
shadow
the
pr
Wrangler
for
the
week
now.
What
do
we
mean
by
shadowing?
A
You
basically
get
to
go
through
PR's
and
you
know
check
for
any
technical
or
qualitative
inconsistencies,
and
you
know
help
the
pr
Wrangler
for
that
week,
who
you
will
be
shadowing,
assess
and
provide
feedback
over
a
set
group
of
PRS,
or
maybe
you
know,
some
pias
they
will
assign
to
you
and
some
peers
you'll
be
working
on.
The
process
remains
ambiguous,
but
the
thing
is
you'll
be
more
familiarized
with
how
we
go
about
traveling
PRS,
when
you,
when
you
know
we
become
PR
ranklers.
A
So
if
that's
something
you're
interested
in,
please
make
sure
you
reach
out
to
Brad
Topol.
He
is
the
POC
for
you
know,
making
the
Rota
currently.
So
we
can
get
you
on
for
a
particular
schedule
date,
and
you
know
you
can
sort
of
assess
the
pr
Wrangler
for
that
particular
week
to
actually
Wrangle
the
PRS
so
yeah,
that's
that's
pretty
much
as
far
as
updates
and
reminders
go
sorry
about
that
yeah.
So
any
questions
on
that
before
we
move
ahead.
A
All
right
I'll
take
the
silences
and
no
and
move
ahead.
This
third
item
on
our
agenda
is
the
ongoing
release
1.25.
A
So
in
so
in
this
section,
what
typically
happens
is
that
we
have
the
dogs,
the
comms
leads
report
pack
their
status
for
the
current
ongoing
cycle
and
if
they
require
any
help,
this
is
where
you
know
they
ask
for
help,
and
as
far
as
you
know,
the
status
goes
we
currently
are
like
they
currently
are
following
up
with
enhancement
leads
to
not
leads
enhancement.
No
one
has
to
remind
them
of
the
pr
placeholder
deadlines.
A
A
few
of
them
are
already
in
place,
but
we
expect
to
see
the
number
and
the
velocity
of
PRS
coming
in
towards
the
end
to
increase.
So
the
pr
deadline
is
next
week.
So,
like
I
said,
the
numbers
will
slowly
increase
on
the
K
website
repository
and
once
this
is
done,
we
then
have
the
whole
cycle
of
approving
or
reviewing
and
approving
those
PRS
that
are
placed
there,
so
they
are
continuing
to
follow
up
and
the
dev
branch
that
is
in
place
for
this
PR.
A
Sorry
in
place
for
this
release
is
in
sync.
As
of
last
week,
all
right,
so
the
next
subsection
in
our
agenda
would
be
issues
and
PRS,
so
I
think
Soco.
You
were
the
one
who
added
the
three
five
four
zero
five
Hugo
build
log
file.
I
actually
just
commented
on
that,
because
I
saw
a
small
Spelling
net,
but
yeah
do
you
want
to
add
on
to
that
or
provide
context
to
the
entire
audience.
D
D
So
it
is
actually
opened
by
Chinese
Park,
who
is
a
active
contributor
in
Korean
localization.
D
A
A
All
right
so
I
think
that
was
a
very
good
PR.
Thank
you
for
bringing
it
to
my
attention.
I
have
left
a
comment
there
because
there's
a
small
spelling
knit
in
the
you
know
this.
The
phrase
that
has
been
put
in
so
once
Jenny
addresses
that
I
will
also
have
one
of
the
tech
leads.
Look
at
that
and
then
provide
sign
off.
If
that's,
okay
with
you.
D
Sure,
thank
you.
Yeah.
A
All
right,
so
the
next
PR
has
also
been
added
by
you.
I.
Think.
Okay,
that's
I!
Think
this
okay,
sorry
I'm!
So
sorry,
but
other
should
we
want
to
provide
further
insight
into
what
this
is.
E
So
I
thought
they
should
record
this
session,
so
I
put
it
over
here.
I
was
actually
motivated
by
seeing
a
slap
message
about
the
dev
environments,
so
I
thought
it
a
very
nice
solution
to
this
would
be
to
add
a
DOT
Dev
container
to
their
kubernetes
website,
reposit
group,
and
it
might
be
some
work
to
test
it
out
and
do
all
of
that
so
I
thought
it
might
require
some
discussions.
A
Yeah
it
will
require,
but
what
I
think
would
be
a
better
way
is
because,
since
the
in-person
meetings
are
infrequent
right,
why
don't
you
reference
this
issue
and
open
up
a
slack
thread
so
that
people
can
actually
provide
feedback
on
slack
as
well?
A
I
know
that
you've
mentioned
it
somewhere,
but
opening
up
a
slack
thread
and
asked
for
folks
inputs
would
make
most
sense,
of
course,
bringing
it
thank
you
for
bringing
up
at
the
meeting
not
saying
that
that's
completely
invalid,
but
because
a
lot
of
folks
don't
attend
the
in-person
meetings
as
well
right,
especially
in
the
APAC
time
zone,
it
would
be
worthwhile
to
actually
open
up
a
thread
and
seek
feedback
from
folks
as
well.
In
my
opinion,.
A
Yeah
but
I
think
this
is
a
worthwhile
effort
to
undertake,
because
I
realized
that
a
lot
of
folks
go
through
this
whole
process
of
setting
up
locally
and
they
run
into
multiple
issues.
So
a
Dev
container
or
the
dev
container
suggestion
really
does
help
and
I
think
it
would
be
worthwhile.
But
since
you're
Community,
Driven
I
think
I'd
like
to
hear
other
people's
opinions
as
well.
So
hopefully,
in
the
next
couple
of
days
you
can
open
a
slack
thread
and
we'll
discuss
further
on
that
all
right.
A
Okay,
so
the
next
thing
before
we
go
ahead
to
the
next
one.
Are
there
any
other
issues
in
PRS
that
you
all
want
to
discuss
any
specific
ones
that
you
all
want
to
highlight?
Because
we
don't
have
a
PR
Wrangler
for
this
week,
which
is
why
I
am
explicitly
putting
this
out
there.
F
Hi
I
had
a
small,
it's
a
very
small
yeah,
just
a
link
change
for
the
cubecon
2020,
three
Europe
Edition.
So
it's
a
very
small
change,
so
I'll
just
put
it
and
whenever
you
are
free
you
can
please
take
a.
A
Look
yeah,
absolutely
absolutely
just
put
it
on
your
I
I
intend
to
go.
We
are
growing
going
chronologically,
so
there
are
a
lot
of
PRS
to
sift
through,
but
we'll
definitely
get
the
stonewise.
F
Yeah,
since
since
it
was
just
opened
only
not
even
a
day
ago,
so
I
thought
it
would
not
be
good
to
it
will
not
be
appropriate
to
put
it
here,
you
can.
A
Put
it
you
but
we'll
eventually
get
to
it.
That's.
G
A
A
A
Okay,
so
now
we
move
on
to
the
next
agenda
item,
which
would
be
open
discussion.
A
So
I
don't
know
if
natish
has
joined,
but
if
I
don't
see
him
you're
on
the
members
list,
so
I'm
gonna
read
it
out,
so
he
has
basically
suggested
a
page
talking
about
the
best
community
practices
that
need
to
be
followed.
For
example,
don't
spam
don't
work
on
the
issue
which
has
already
been
assigned,
be
patient.
Try
before
asking
so
my
two
cents
in
this
is
that
we
already
have
a
code
of
conduct
in
place.
A
We
also
have
a
contribution
guide
which
talks
about
you
know
checking
whether
somebody
is
already
working
on
the
issue
before
being
you
know
before
actually
participating
in
it,
and
even
the
trying
before
asking
bit
is
covered
in
that
contribution
guide,
so
the
rest
of
it
is
I,
just
think
human
decency,
so
I.
Don't
really
think
that
we
should
be
enforcing
things
that
are
basic
human
and
decency.
A
Tenants
hunt
people
but
yeah
I
would
be
taking
this
back
to
the
chairs
and
the
other
coaches
and
the
team
tech
leads
to
see
if
this
is
something
that
would
benefit
but
as
far
as
I
know,
I,
don't
think
this
would
fall
under
docks
per
se,
the
very
being
the
very
first
thing,
because
this
is
going
to
be
like
something
that
needs
to
be
followed
across
the
community.
A
So
contribution
guide
notwithstanding
this
probably
might
not
be
the
best
Avenue
to
discuss
it,
given
that
this
is
a
more
of
a
community
best
practice
rather
than
a
dog's
best
practice,
but
I'd
be
curious
to
hear
if
anyone
else
has
any
alternative
opinions
on
the
call
foreign.
D
I
actually
agree
with
you
and
era
vertical
documents
related
with
this
topic:
yeah,
maybe
you'd
better,
to
keep
some
information
regarding
related
documents
to
and
then.
D
S
came
to
if
you
find
any
enhancement
point
for
those
documents,
maybe
making
you
want
new
page.
If
not,
we
have
to
cover
the
whole
Community
things
different
things
regarding
the
stand
and
those
things
that's
my
opinion.
Thank.
A
You
yeah
and
we've
already
also
pinned
a
message
regarding
this
on
the
docs
Channel
as
well,
so
I
I
really
don't
know
if
it
would
be
worthwhile,
but
just
just
to
understand
like
if
this
is
a
requirement,
because
I
don't
know
if
others
feel,
alternatively,
have
been
here
for
around
two
years.
So
I
don't
know
if
others
feel
alternate
or
have
alternate
opinions
about
this.
So
yeah.
F
I
also
feel
like
a
separate
page,
should
it
shouldn't
be
necessary
for
this,
but
if
like,
if
some,
if,
if
it's
like
newcomers
are
like
confused
I
think
we
can
just
you
know,
create
some
like
bullet
points
in
the
Community
conduct,
page
or
COC
page.
That
would
be.
That
could
be
another
alternative
instead
of
making
a
separate
page
in
my
opinion,
but
I
feel
like
Percy.
It's
not
that
necessary.
B
A
Discussion
point
I
was
waiting
for
someone
to
feedback,
but
apparently
nobody
has
any
other
points
in
this.
So
yeah
I'll
just
enter
in
the
last
bit
here.
A
Oh
right
so
Circle
do
you
want
to
speak
to
the
next
set
of
agenda
items,
which
is
the
Korean
localization
info.
D
From
why
not
actually
I'm,
since
I'm
audit
of
Korean
localized
or
something
I
hope
to
share
how
Korean
Team
Works
in
this
meeting
since
I
have
been
in
long
time,
Stephen
Pakistan
this
meeting,
so
it
is
just
information
to
all
over
you.
Yeah
crossover,
Korean
localization
team
has
a
milestone
strategy
and
we
have
our
own
development
Branch.
We
don't
directly
push
commit
to
main
branch
and
we
we
do
a
localization
job
in
the
development
branch
and
then
we
both
try
to
board
the
development
Branch
into
main
branch.
D
D
Yeah
we
when
we
initiate
new
Milestone,
we
open
a
marathon
in
GitHub
UI,
and
here
is
the
our
my
current
Milestone
level,
one
to
24
ko2,
and
this
button
usually
includes
two
issues
and
first
one
is
announcing
the
localization
job.
D
We
give
information
to
contributors.
What
is
the
current
development
branch
so,
and
this
branch
has
a
deadline
and
please
debate
and
then
the
second
one
is
checking
out
date,
the
Korean
content,
since
we
use
development
branch
and
we
don't
use
just
one
development
Branch.
We
create
development,
branch
and
embroidery
to
main
branch
and
we
created
another
development
branch
and
we
checked
the
difference
between
development
friendships.
That's
how
I
how
we
trace
the
change
the
English
documents
during
our
job
yeah.
D
So
could
you
go
to
the
agenda
yeah?
So
the
Milestone
is
like
this
ko1
to
ko2,
ko3
and
so
on,
and
we
follow
the
follow.
The
figure
docs
release,
phase,
yeah,
yeah
and
currently
the
development
branch
is
ko2
for
124
and
it
will
be
validity
to
into
Main.
D
So
thanks
to
our
Korean
contributors
yeah-
and
we
have
some
issues
regarding
this
Korean
localization-
actually
actually
queer
localization
team
have
contributed
to
a
website
for
for
our
five
years.
So
we
have
many
localized
the
files
I
checked,
it
is
more
than
400
and
they
are
keep
changing
so
yeah.
Could
you
open
the
next.
D
D
H
D
You
can
just
scroll
down,
it
is
to
trace
and
Report
outdated
content.
As
you
can
see,
there
are
125
prices
to
be
modified
for
our
Milestone
during
our
Milestone
yeah.
B
D
It
is
really
really
overload
for
Korean
localization
team
right.
B
D
So
we
are
looking
for
a
way
to
reduce
load.
So
folks,
if
you
have
any
nice
idea
and
or
nice
experience,
then
please
share
it
to
Korean
localization
team.
It
will
be
very
helpful.
A
I,
don't
purposely
have
any
you
know,
tips
or
tricks
regarding
this,
but
so
could
you
feel
that
bringing
this
up
in
the
main
channel
would
help,
because
our
tech
leads
like
gaming
and
Tim
and
Taylor
might
have
insights
on
how
to
do
this
better
partially,
because
Tim
has
been
involved
in
a
lot
of
localizations
and
he
might
have
something
to
you
know
speak
from
his
experience.
Have
you
you
know
tried
that
approach.
D
Sure
actually,
Tim
already
know
this
situation
and
okay
other
localization
teams,
such
as
Chinese
localization
team,
has
different
approach
with
us.
Okay,
some
teams
are
following
a
similar
way
with
Korean
localization,
okay,.
B
D
Actually,
the
our
localization
guide
document
interface-
this
I
mean
recommendative
approach
so
yeah.
D
Maybe
we
will
find
some
tentative
ideas
and
we
will
test
and
then
I
hopefully
share
several
ideas
with
six
dogs
and
other
perks
and
then
see
how
it
works.
A
Yeah,
the
reason
is
I
think
God
has
also
localization
meeting
that's
coming
up
on
Monday
the
coming
Monday,
because
it's
the
first
of
August,
if
I'm
not
mistaken
and
my
math
is
not
bad.
So
maybe
this
is
something
that
you
can
put
on
the
agenda
item
for
today
and
even
if
you're
not
present,
those
meetings
are
recorded.
So
maybe
this
is
something
that
you
can
bring
up
there
as
well.
So
I
can
pass
you
the
link
for
the
sick,
docs
localization
meeting.
A
It
occurs
on
the
first
Monday
of
every
month,
so
I
can
pass
you
the
link
for
that,
and
maybe
you
know
you
can
actually
add
it
there
as
well,
since
this
is
a
very
localization
specific
issue
and
it
would
benefit
you
know
all
other
localizations
as
well,
because
this
is
a
recommended
approach
that
you're
taking.
So
if
this
is
something
that
is
a
problem
for
you,
which
it
will
be
a
problem
for
everybody
else
as
well
so
benefits
from
wider
discussion
is
what
I
think,
and
maybe
you
know
in
that
localization
meeting.
D
Sure,
actually
I'm
main
participant
in
that
meeting,
yep
I
I
usually
participate
in
meeting
and
I
shared
this
situation
already
too
proud
and
other
perks.
So
they
are
aware
of
this.
A
A
Yes,
thank
you
so
much
and
if
there's
anything
that
I
can
find
out-
and
no
you
know
let
you
let
you
know
about
I'll-
do
that
as
well.
Oh.
A
Just
a
second:
maybe
you
want
to
go
ahead
with
the
next
one
as
well.
I
think
that's
that's
put
in
by
you
the
contributor
Management
mentorship
program.
You
want
to
share.
D
Sure
it
is
information,
and
actually
we
applied
for
a
contributor
contribution,
mentorship
program
posted
in
Korean
agency,
and
it
is
effort
to
invite
new
contributors
for
six
dots
and
result.
Is
we
accepted?
D
A
Yep
we're
always
looking
for
new
contributors,
of
course,
so
I
think
this
is
like
you
know
perfect,
and
thank
you
for
doing
this.
A
I
think
it'll
only
help
you
know
reduce
the
overall
workload,
not
just
for
the
current
localization
or
the
Korean
team,
but
for
docs
and
the
project
in
general.
So
thank
you
so
much
for
taking
on
this
effort
of
applying
to
the
contribution
mentorship
program.
Sure.
D
Thank
you,
tester
from
my
site,
and
if
you
have
any
question
yeah,
then
let
me
let
me
know
thank
you
right.
A
All
right,
so
are
there
any
other
discussion
items
that
anybody
wants
to
bring
up
before
we
close
for
the
day.
A
Has
anything
I
think
we
can
call
it
a
day
and
I'll
see
you
folks
soon,
a
hangout
in
slack
and
hopefully
bye
next
meeting?
We
have
more,
you
know
PR's,
that
are
you
know
that
have
their
resolution.
So
thank
you
so
much
to
everyone
who
attended
today
and
have
a
great
day
all.
A
I
Yeah
hi
actually
I
want
to
understand.
Like
can
you
guide
a
little
bit
about
PR
Wrangler
ship
because
I
reserved
to
Ray
for
the
pr
Wrangler
chip
and
eat?
Like
sorry,
he
mentioned
me
under
some
person
and
I
reached
out
to
that
person
and
that
person
didn't
reply
over
that
particular.
A
Yeah,
that's
that's
probably
because
that
person
was
actually
also
unavailable
and
he
was
on
a
holiday
for
like
two
weeks.
So
could
you
just
reiterate
your
request
to
him?
I
know
that
you
spoke
to
Brad
Topol,
but
he
he
was
on
a
holiday
for
two
weeks.
So
this
is
the
PR
Wrangler
program
link.
Brad
Topo
is
the
person
you
need
to
reach
out
to
and
he
was
on
a
holiday
up
till
last
week,
so
yeah.
So
that's
that
I
think
you
have
been
added
as
a
shadow.
A
Yeah
you
have
been
as
far
as
I.
Remember,
I,
remember
seeing
it,
but
thank
you
vital
for
remembering
that
in
just
a
second
I'll
just
open
that
up
here.
A
B
A
Can
you
check
that
link
yeah,
just
a
second
I
opened
it
up
right
now,
yeah
you
are
added
as
a
Wrangler
against
my
name,
so
I
think.
I
Yeah
I
reached
out
I
reached
out
to
Ray
for
like
assigning
me
into
your
role
because
yeah
to
the
community.
So
that's
the
reason
I.
A
I
Okay,
so
like
can
you
guide
me
a
little
bit
about
what
particular
sets
I
have
to
go
through.
A
So
basically,
like
I,
said
it's
a
case-by-case
basis
for
me,
specifically,
what
I
tend
to
do
is
I.
Allow
the
shadow
who
works
with
me,
or
rather
not
allow
or
I,
actually
asked
the
Shahi
to.
You
know
review
a
set
set
of
Piers.
We
basically
bifurcate
the
PRS
amongst
them
ourselves,
and
then
we
actually
go
through
the
process
of
reviewing
so
I.
A
Let
the
shadow
review
PRS
and
come
back
to
me
if
they
have
doubts
on
what
basis
or
what
specific
stuff
that
the
piano
needs
to
be
reviewed
on.
So
some
are
just
links
then
some
are,
maybe
you
know
more
qualitative
and
Technical,
then
some
could
possibly
be.
You
know
wrongly
raised
PRS,
for
example,
a
lot
of
PRS
get
raised
to
amend
reference
talks
directly
and
those
are
the
kind
of
PRS
that
you
should
not
be
allowing
to
you
know,
amend
manually.
A
You
need
to
sort
of
tell
them
that
kubernetes
kubernetes
is
the
area
where
they
should
be
amending
that
and
then
generating
the
reference
documentation.
So
those
are
just
three
broad
categories
that
I
can
think
of,
but
what
we
basically
do
is
bifurcate
the
English
language
PRS
between
ourselves
and
review
it
because
the
localization
PRS
are
handled
by
the
respective
localization
teams.
A
So
the
English
language
PRS,
are
what
we
bifurcate
among
ourselves
and
work
on
them
and
if
they
have
any
doubts,
is
when
I
step
in
so
basically
it's
a
half
half
job
and
after
that,
if
there
are
any
questions
around
reviewing,
mostly
they
end
up
being
around
styling
and
stuff,
like
that,
so
there's
a
style
guide
around
and
a
reviewing
guide
on
how
to
do
the
reviewing
process.
So
I
recommend
that
everybody
who
Shadows
under
me
goes
through
that
as
well.
A
G
I'm
I'm
new
here
and
I
have
been
contributing
to
Hindi,
localization
and
yeah
of
age,
guarding
me
with
that.
So
as
as
far
as
know
that
how
can
I
join
this
Shadow
thing
and
what
all
the
pr
Wrangler
stuff
is
there
that
I'm
looking
yeah.
A
So
I
just
mentioned
at
the
start
of
the
meeting
that
for
the
pr
Wranglers,
what
you
essentially
need
to
do
is
reach
out
to
Brad
Topol
I've
pasted
his
name
on
the
chat.
You
need
to
reach
out
to
him
on
slack
and
tell
them
or
tell
him
which
PR
Wrangler
you
need
to
share.
You
want
a
shadow
again,
so
there
are
a
bunch
of
people
here
on
this
page
and
the
link
is
also
out
in
the
chat
itself.
A
So
you
just
need
to
go
and,
as
us
pick
one
and
assign
your
and
ask
him
to
assign
that
person,
not
ask
him
to
assign
that
person.
Basically
ask
him
to
add
you
as
a
shadow
against
that
person.
G
Oh
okay,
so
what's
the
gender
role
of
a
shadow
yeah.
A
So
that's
exactly
what
I
was
explaining
to
Abhishek
it's
a
case
by
case
thing.
So
for
me
it
that's
how
it
works,
but
I'm
sure
it's
the
same
with
every
it's
similar,
if
not
same
with
everyone
else.
We
majorly
work
on
English
language
PRS
because,
like
you
already
know,
the
localization
team
works
on
the
actual
localization
PRS.
Unless
you
know
like
yourself,
if
you're
already
a
part
of
the
localization
you'll,
probably
also
be
working
on
the
Hindi
language
PRS,
but
primarily
it's
English
language,
PRS
you'll
be
reviewing
them
on.
A
You
know,
quality
or
the
technical
content,
or
you
know,
checking
if
they
are
really
valid,
PRS
or
not,
and
basically
assisting
the
pr
Wrangler
for
that
week,
with
an
lgtm
on
that
PR,
you
will
not
obviously
be
able
to
give
a
sign
off,
because
you
are
not
an
approver
on
that
you're,
not
on
the
approvals
list,
but
you
will
basically
be
just
writing
an
LG
TM
and
what
I
tend
to
do
is
I.
Have
like
a
set
I.
A
Have
the
shadow
tell
me
if
there
are
any
specific
PRS
that
they
have
problems
with
or
they
find
challenging?
So
then
we
go
to
it,
we
go
through
it
together.
So
that's
that's,
basically
the
gist
of
it.
You're
going
to
review
English
language
PRS
how
you
do
it
is
obviously
based
on
the
person
who
you
are
you
know,
working
with
it
could
be
on
a
Case
package.
It
could
be,
you
know
about
half
off,
it
could
be.
You
know
them
guiding
you
through
each
PR.
However,
it
works.
G
Yeah,
okay,
thank
you.
Thank
you,
David
yeah.
How
can
how
can
we
access
the
recordings
for
the
meetings
that
we
are
having.
A
Yeah,
that's
a
good
question,
so,
unfortunately,
what
has
happened
is
over
the
last
one
year
there
has
been
a
huge
backload
and
I
am
still
trying
to
you
know
upload
all
of
them,
so
all
of
this
gets
uploaded
onto
Google
Cloud,
so
I
have
to
manually,
download
them
and
put
them
up
on
YouTube.
The
YouTube
link
is
also
there
on
the
agenda,
documentation
so
I
think.
Currently
so
far
we
have
all
recordings
up
to
Jan.
A
I
am
in
the
process
of
uploading,
all
of
them
update
on
on
YouTube,
but
it's
a
bit
difficult
because
you
have
to
first
download
them
off
of
the
cloud
and
then
upload
them
back.
That's
because
this
claim
is
broken
the
connecting
software.
So
that's
sort
of
the
reason
why
we
have
to
do
it
individually.
A
Cool
any
other
questions,
please.
A
Okay,
that's
I,
actually
not
only
the
remit
of
tick
tock.
So
why
don't
we
speak
on
DM's
Abhishek
I?
Don't
have
any
problems
guiding
you,
but
it's
not
in
the
remit
of
sick
dogs.
The
shadow
program
is
in
sick
release
and
that's
a
separate
topic
all
together.
So
it's
basically
this
very
similar
to
how
you
would
you
know,
Apprentice
against
a
lead,
but
there
are
various
facets
to
it.
A
So
I
don't
want,
for
you
know
a
meeting
first
of
sick
dogs
to
be
covering
that
program
as
well.
So
could
you
reach
out
to
me
on
DM
so
that
we
can
talk
about
this
further?
Please.
A
Thank
you
anything
else,
please,
before
we
wrap
up
because
I
think
we're
running
over
time,
which
is
why
I'm
asking.
B
All
right,
okay!
So
if
there
are.
A
No
questions,
please,
you
know
please
continue
to
contribute
to
the
PRS,
and
if
there
are
any
doubts,
please
have
you
know,
voice
out
on
the
kubernetes
tech.
Talk,
slack
Channel
and
we'll
be
more
than
happy
to
help
out,
but
for
today
I
think,
that's
pretty
much.
It
and
I
hope
to
see
all
soon.
Thank
you
and
have
a
great
day.