►
From YouTube: K8S SIG Docs meeting for 20220614
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
Alrighty
and
we're
recording
so
hi,
everyone
again
welcome
to
the
bi-weekly
meeting
for
Sig
docs
access
joining
and
hello
everyone.
My
name
is
Natalie
I'm,
one
of
the
coaches,
my
pronouns,
are
she
her
I'm
trying
to
do
pronouns
so
that
we
can
normalize
this
in
our
communities
to
support
our
marginalized
folks
and
welcome
from
my
workplace
my
office
joining
you
from
the
office
today?
A
Yes
sing,
docs
mix
bye
week.
Please
thanks
to
everyone
for
for
joining
us
today
and
we're
a
community
that
looks
after
the
documentation
of
kubernetes
and
what
I
want
to
remind
everyone.
Is
that
we're
also
a
community
that
follows
a
code
of
conduct
for
kubernetes?
We
want
to
be
excellent
to
one
another.
A
I
want
to
treat
each
other
with
respect
and
kindness
to
kindness
is
nice
and
for
anyone
on
the
call
that
has
any
kind
of
issues
around
that
we
do
have
a
code
or
conduct
Community
for
the
kubernetes
project
that
you
could
also
reach
out
to
with
any
issues.
There
is
around
this
as
well
on
the
slack.
That
would
be
the
the
best
way
to
ask
questions
and
then
be
able
to
also
reach
them
via
the
mailing
list,
but
they'll
specifically
advertise
and
that's
like
so
thanks.
A
So
much
for
joining
and
we'll
we'll
get
started.
A
big
big
attendance
today,
which
is
really
really
great.
A
What
I
first
wanted
to
do
is
on
the
agenda
I'm,
going
to
quickly
link
it
in
the
in
the
chat,
funnily
enough,
operating
on
a
single
monitor,
which
is
not
my
not
my
favorite
thing,
but
the
agenda
varies
in
the
chat
for
those
who
who
want
to
follow
along,
and
the
first
thing
I
would
love
to
ask
is
to
for
the
new
contributors
to
say
hello:
do
we
have
any
new
folks
who
are
either
new
to
kubernetes
new
to
this
meeting
and
haven't
introduced
themselves?
B
A
Well,
good
I
am
horrible
with
names,
so
I
never
love
to
assume
that
I
know
everyone
joining,
unfortunately,
but
but
what
we'll
do
we'll
leave
another
minute
or
so
for
those
who
don't
want
to
speak
up?
Oh
here
we
go
Abhishek
hi
great
to
meet
you.
Thank
you.
So
much
for
for
saying,
hi
and
taking
part
I
did
want
to
also
state
that
for
those
who
didn't
want
to
unmute,
you
can
definitely
just
type
in
the
chat.
That's
also
super
okay
as
well
hi,
japanka,
hello.
A
Thank
you
so
much
for
saying,
hi
Welcome
to
our
little
docs
Community.
We're
super
we're
super
stoked
to
have
you
for
the
recording,
I
realize
I
forgot
to
mention
the
date.
It
is
the
14th
of
June
2022
for
those
watching
in
the
future.
Abhishek
is
simple
guidance
to
get
started.
I
can
see
that
your
high
Tanya,
a
big
hello
there
I
can
see
and
also
Carol.
Thank
you
so
much
for
saying,
hi,
you're
saying
that
you
need
some
guidance
getting
started.
This
is
definitely
great.
A
We've
got
some
really
great
pinned
messages
in
our
slack
Channel
I've
gotta.
If
I
can
ask
a
couple
folks
who
are
on
the
call
to
maybe
link
some
of
those
in
the
chat
now,
they're
contributing
the
contributing
setting,
docs
would
be
really
great,
but
our
slack
channel
is
the
best
place
to
get
a
few
of
those
links
that
are
going
to
be
pinned
there.
A
I'm
gonna
see
if
I
can
quickly
get
a
couple
of
those
now
linked.
Give
me
one
sec.
A
I
love,
I,
love.
Thank
you
so
much
Vitale.
Yes,
that's
the
one
I
want
a
single
monitor.
A
single
monitor
problems
myself
is
is
real
great
Abhishek.
A
The
the
link
that
Vitale
just
sent
in
the
in
the
in
the
code
in
the
chat
there
is
a
best
thing
to
get
started,
definitely
understand
that
code
could
look
overwhelming
to
you,
which
is
why
docs
is
a
great
place
to
actually
start
some
of
the
contributions
that
you're
having
kubernetes
is
a
huge
project
with
a
lot
of
different
ownership
areas,
different
special
interest
groups
that
look
after
those
ownership
areas,
people
the
great
thing
about
that
is
that
people
are
usually
pretty
family
in
a
lot
of
the
different
slack
channels,
so
I
definitely
recommend
having
a
look
at
some
of
the
different
areas
that
you're
interested
in
going
to
that
specific
owned.
A
Channel
docs
is
a
great
place
to
get
started
for
documentation.
Boss
is
a
great
place
to
get
started
with.
Maybe
the
Pod
security
policy,
for
example,
or
or
authentication
authorization,
depending
on
what
you
want
to
kind
of
get
into
your
island
is
huge,
but
there
are
ways
to
to
help
and
get
started,
and
starting
in
some
of
those
like
Channels
with
their
specific
resources,
is
a
great
way.
A
So,
thanks
for
asking
the
question
and
welcome
it's
great
to
have
you
on
board
thanks
nitish,
also
for
linking
the
place
to
get
started
on
slack
2.,
very
appreciated.
A
It
takes
a
village
folks
to
help
help
contributors
even
on
meetings.
So
that's
great
again
a
big
welcome
to
everyone
who's
joining
again.
Thanks
again,
so
much
for
saying
hello,
I
will
be
adding
I've
got.
We've
got
some
names
already
added
there.
Thank
you,
so
much
I
believe
I've
got
some
note
takers
in
the
in
the
chat
doing
so
already.
So
that's
great!
Thank
you
so
much
alrighty
with
that
being
the
case.
Let's
move
on
to
a
couple
of
quick
announcements.
A
As
for
folks
who
are
new
in
sync
docs,
we
have
a
bit
of
a
a
program
that
we
call
PR
wrangling
and
that's
something
where
we
have
reviewers
and
approvers
who
have
a
weekly
shift
of
being
the
the
person
that's
going
to
push
contributions
through,
so
that
we
can
get
our
contributions
upstream
and
into
production
as
soon
as
possible,
and
so
we
have
different
different
folks
doing
that
week
to
week,
and
so
our
regular
Wrangler
this
week
is
actually
on
the
call
Zachary
hi
thanks
so
much
for
being
the
Wrangler
this
week.
A
Thanks
also
for
calling
that
out
on
the
slack,
that's
awesome
and
and
that'll
definitely
be
something
that
will
be
helpful
for
folks
who
are
looking
for
some
of
their
PRS
to
kind
of
be
looked
at
and
commented
on,
and
so
on
for
the
week
for
next
week,
the
pr
Wrangler
is
Ray,
the
genre
who's,
one
of
our
coaches
and
for
all
folks
who
are
on
the
call
who
are
possible.
Pr
Wranglers.
Please
take
a
look
at
your
shifts.
A
My
own
is
coming
up
very
soon
so
that
you
know
when
you're,
when
you're
on
the
hook
to
answer
some
questions
on
top
of
a
lot
of
our
other
contributors,
contributing
as
they
usually
do
throughout
throughout
the
different
months.
A
A
Our
agenda
at
the
moment
is
pre-sparce,
which
is
fine,
and
if
anyone
has
extra
things
that
they'd
like
to
add
to
the
agenda,
extra
speaking
points
feel
free
to
jump
into
the
agenda
now
and
add
those
As
You
Wish,
and
then
we
can
get
to
them
as
we're
as
we're
going
through.
But
my
first
call
out
is
looking
at
the
next
release,
which
is
1.25.
Do
we
have
anyone
on
the
docs
on
the
docs
team,
as
part
of
as
part
of
the
release
team
for
docs?
A
Great
thanks
so
much
thanks,
so
much
Carol,
that's
great
I,
yeah
I,
don't
believe
we
have
a
huge
update
on
our
end.
Definitely
keep
a
keep
listening
to
the
meeting
generally
and
like,
and
what
we're
generally
working
on,
but
I
believe
we're
in
week.
Four
of
the
release
of
the
race
cycle
as
we
as
we're
going
through.
So
so
we're
going
to
keep
a
trucking
on
and
and
I
do
I
do
believe.
The
enhancements
deadline
has
been
extended
too
as
well.
A
So
that's
actually
something
of
note
for
for
folks
to
to
keep
in
mind
as
well
alrighty
with
that
being
the
case
thanks
so
much
Carol
for
saying,
hi
and
and
for
being
on
the
on
the
on
the
call
as
the
shadow
that's
really
great,
and
if
we
go
on
to
the
next
parts
of
our
agenda,
we're
now
going
to
go
into
the
issues
and
PR
section
of
the
agenda
there
and
we
do
have
vittel
who's
added
a
specific
issue
around
adding
tips
for
abbreviations
vittel.
B
D
Ahead,
so
it's
basically
I
created
this
issue,
basically
on
team
suggestion
on
another
issue
and
he
adds-
and
he
had
suggested.
I
have
also
linked.
That
comment
also
on
the
agenda,
and
he
suggested
that
we
could
add
a
tips
tips
section
for
Pages,
where
we
can
use
shortcuts
or
like
abbreviations
for
cube
cuddle
commands,
because
in
the
deployment
page,
as
as
you
rightly
mentioned,
that
cubecut
tell
got
RS,
it
took
me
a
while
to
register
yeah.
D
It
is
also
replica
set,
so
I
believe
that
these
certain
tip
sections
could
help
anybody
who's,
viewing
the
doc
so
to
just
speed
up
their
time
and
if
they
are,
if
and
if
in
this
case,
if
they
are
newbies
or
just
starting
to
roll,
they
can
just
register
more
quickly
with
the
command
means
to
say:
I
mean
this.
This
is
all
I
have
from
my
side
and
if
Tim
wants
to
go
ahead,
I
would
be
more
than
happy
because
it
was
it's
his
own.
His
idea
originally
thank
you.
E
So
my
idea
is
that
you
know
I
when
I'm
writing,
Tech
docs
I
tend
to
use
the
long
command,
so
I
could
cut
or
get
replica
set
could
all
create
whatever,
because
I
want
people
to
know
what
these
things
I'm
talking
about
are,
but
I
also
know
that
people
want
to
learn
the
short
commands
for
things
like
exams
or
just
having
less
worn
out
fingers
and
I'm,
suggesting
that
we
standardize
on
a
a
tip
section.
The
same
way.
The
pages
have
a
standard.
E
A
Great,
that's
awesome
and,
and
vital
I
saw
that
you
would
put
the
issue
specifically
there.
Is
that
something
that
you'll
be
working
on,
or
is
this
something
that
we
want
a
lot
more
contributions
from
the
community
on
specifically.
D
A
Perfect
I
definitely
think
the
the
more
contributions
to
something
like
this
could
be
could
be
really
valuable,
at
least
on
the
on
a
let's
say,
review
process
specifically
have
we
missed
certain
commands
that
could
actually
be
added
and
so
on?
I
think
that
could
be
really
valuable.
So
that's
great.
This
is
awesome.
F
F
Sorry
I
said
as
if
I
was
going
to
say
some
more
and
then
that
was
actually
it.
E
I
guess
what
I'm
thinking
of
is
that
if
we
use
a
short
code
for
the
tips
heading,
one
that
helps
localize
it
and
helps
with
consistency.
And
it
means
that
future
work
to
use
something
that
looks
like
a
pull
quote
or
a
call
out
whatever
becomes
easier.
Because
you
can
make
that
almost
mechanical.
A
We've
got
a
question
there
from
our
author.
Would
it
make
sense
to
give
the
long
and
short
versions
of
the
command
side
by
side
very
likely.
E
Watch
out,
if
you
are,
you
know,
if
you're,
giving
people
a
script
version
and
you're
expecting
people
to
type
that
script
in
some
of
these
commands
have
side
effects.
So
if
you
run
them
twice
and
we
give
the
long
and
the
short
version
we
have
to
think
about
how
that
works.
People
will
some
people
just
read
our
docs
and
paste
things
in
without
reading
them,
whether
we
want
them
to
or
not.
A
Great
thanks
so
much
for
tell
for
putting
that
on
the
agenda
and
you've
got
the
issue
there.
As
well.
I've
noted
the.
G
A
Specifically
Tim
that
you
mentioned,
of
having
the
umbrella
issued
a
track,
a
traffic
track,
adopting
this
for
key
Pages,
and
that
was
going
to
require,
like
you
said
several
PR's,
so
that
could
mean
you
tell
us
an
example.
Folks
can
have
contributions
for
specific
Pages
as
opposed
to
need
to
kind
of
explain
the
whole
issue,
so
that
could
be
a
great
way
to
elicit
help
from
larger
areas
of
the
community.
A
For
sure,
thanks
for
the
bringing
that
up,
I
think
that's
a
really
really
great
addition
and
change,
and
also
wanted
to
call
out
super
appreciate,
Tim
that
hoping
to
get
folks
to
understand
what
the
entire
command
is,
but
we
love
shortcuts
too
so
good,
it's
a
good,
it's
a
good,
medium
process
for
sure
all
right,
any
further
or
last
last
remarks
on
that
specific
issue.
Before
we
move
on.
A
Going
once
twice:
okay,
moving
on
thanks
everyone,
that's
the
last
issue
of
PR
that
we've
got
on
the
agenda.
We're
moving
over
to
the
questions
and
discussion
area
points
now,
and
the
first
item
on
the
agenda
is
is
byray,
who
is
unfortunately
not
here
today,
but
a
few
of
us
can
can
speak
to
this
specific
issue
regarding
the
catacota
scenarios
and
specifically
O'reilly
reaching
out
and
stating
that
the
katakura
scenarios
for
kubernetes
Io
they've
been
moved
to
a
separate
server
and
they're
going
to
be
available
after
June,
the
15th.
A
So
after
tomorrow.
That
being
the
case,
this
was
also
actually
mentioned
in
our
in
our
specific
slack,
a
meeting
updates
for
last
week
in
this
in
the
slack
threads
and
those
as
I
mentioned,
those
will
be
available
after
after
June
15th
and
the
scenario
specifically
for
kubernetes.
I
o
won't
be
affected
by
the
public
shutdown
of
katakuda
as
well.
So
that's
just
a
general
notice
for
folks.
A
There
happy
to
hear
other
comments
or
anything
there,
but
generally
we've
understood
that
we
are
thankfully
not
affected
by
that
specific,
that
specific
change.
A
And
then
next
comment,
our
next
question
or
discussion
point
that
I've
got
here
is
actually
from
my
own
as
just
a
bit
of
a
heads
up.
A
We
are
just
about
to
we
meaning
myself
when
I
click
the
button
send
out
the
notice
to
the
sigdocs
tick
tocks
mailing
list
group
that
will
be
confirming
the
localization
subproject
via
lazy
consensus,
just
sending
that
out
to
folks
for
folks
to
understand
that
the
sub
project
will
be
created
so
that
the
localization
General
workload
is
going
to
be
formalized
under
a
sub
project,
and
we've
got
here
specifically
one
of
our
leads
of
that's
a
project.
A
That's
going
to
be
undertaking
some
really
really
great
work,
Abigail
on
the
call
so
that
we
can
formalize
localization
itself
as
an
ownership
area,
get
a
lot
more.
Really.
Amazing
initiatives
through
some
really
great
centralized
kind
of
stuff
has
already
kind
of
come
through
from
Abby
and
Brad.
Who
are
our
two
leads
for
localization,
but
something
that's
very,
very,
very
exciting,
as
I
mentioned,
I
just
literally
need
to
click
the
button
to
click
Send,
and
that
lazy
that
this
would
be
three
business
days
specifically.
A
So
by
the
end
of
the
week,
we
hope
to
get
the
owners
and
yaml
files.
That's
needed
updating,
so
that
that
work
can
really
really
get
get
started.
A
I'm
really
excited
too
Abby
thanks,
it's
something
that
Steve
docs
as
a
cohort
has
been
working
on
for
quite
some
time,
and
it's
really
awesome
to
be
able
to
finally
recognize
that
localizations
are
an
area
that
there
were
decision
making
and
Leadership
and
guidance,
and
they
can
be
able
to
get
those
short
feedback
loops
in
a
really
more
effective
way
by
having
their
own
sub
project,
which
is
great.
A
Did
you
want
to
say
anything
else?
Abby
to
that
before
we
move
on.
H
Just
to
say,
I'm
really
excited
I
know.
Some
folks
here
are
also
participating
in
the
the
localization
group.
So
it's
great
to
see
everyone
here
and
if
you
didn't
know,
we
do
have
these
meetings.
We
have
our
own
channel
too,
if
you're
you're
interested
in
localization
and
learning
more
that's
I
will
post
the
slack
Mass
slack
channel
in
the
the
chat
I,
because
I
can't
think
of
it
off
the
top
of
my
head,
so
I'll
place
the
link.
H
There
are
people
interested
to
see
what
we're
all
about
and
I'm
really
excited.
Thank
you,
Natalie
for
for
helping
drive
this
forward.
It's
been
a
road
that
we've
been
traveling
down
for
a
while.
So
I'm
really
excited
that
we
have
this
formalizing.
H
A
Okay,
that's
it!
Thank
you
awesome!
Thank
you.
No
worries,
typing
and
talking
at
the
same
time,
for
me
is
not
a
strong
point,
Abhishek
just
to
answer
your
question
there.
A
We
do
have
different
localizations
of
different
of
different
languages
for
kubernetes
documentation
in
the
again
in
yes,
thank
you
so
much
for
adding
adding
that
that
a
link,
thereofly,
specifically
specifically
Abhishek
you'll,
be
able
to
actually
find
the
different
channels
of
the
localizations,
our
link
to
by
using
kubernetes
Dash,
Docs
Dash,
and
then
the
the
language
code,
specifically
so
you'll,
be
able
to
see
a
lot
of
the
different
language
language
localizations
on
offer
for
sure
as
well.
A
But,
yes,
that's
the
channel
link
there
a
lot
of
other
really
useful,
pinned
resources
in
that
specific
localizations
Channel
that
you
can
definitely
have
there
and
I
just
saw
Ray
thanks.
Abhishek
I
just
saw
Ray
jumped
on
hi
Ray
another
one
of
our
co-chairs
of
speedbox.
A
G
Yeah
I'm,
Pastor
I,
know
I,
like
the
paste
the
link
to
the
comment
about
it
so
catechota
for
for
some
background
and
they
are
removing
our
public
access
to
create
kind
of
coded
scenarios.
But
so
we
did
have
a
short
movement
to
try
to
migrate
off
katakota.
G
We
listed
we
just
quickly
for
looked
at
some
different
options
here,
but
O'reilly
which
owns
catacota
reached
out
and
they
stated
that
the
catacolic
scenario
is
only
on
kubernetes.io.
Are
we're
already
moved
to
separate
server
and
that
they
will
be
available
after
June?
15Th
is
when
the
public
access
to
cataclyna
will
be
removed.
I
know,
there's
a
pull
request
to
remove
the
warning
label.
G
We
have
warning
label
on
on
pages
to
have
catechota
scenarios,
so
we
have
a
warning
label
so
there's
a
pull
request
to
remove
that
warning
label
but
put
on
hold,
because
I
want
to
test
to
make
sure
that
we
do
have
access
to
catechota
after
June
15th,
also,
and
also
think
in
the
back
of
my
head
that
we
should
I
would
when
I
do
have
some
Cycles
too,
that
we
should
look
into
possibly
migrating
or
pocing
some
some
options.
G
As
well
in
case,
we
do
run
into
the
same
issue
down
the
road.
A
But
you
know
something
like
this
happens
again.
Making
sure
some
of
the
keeping
of
that
knowledge
is
is
in
some
of
our
some
of
our
control.
I
think
that's!
That's
a
really
really
great
approach,
so
B,
plus
one
to
that
for
sure
alrighty
thanks
so
far
for
input
on
a
lot
of
the
different
agenda
items
we're
going
to
be
moving
on
to
the
next
one
and
that's
specifically
with
with
Zachary
specifically
around
signal
review
times
over
to
you.
G
B
I
Okay,
excellent,
so
yeah
I
just
wanted
to
boost
visibility
as
I'm
wrangling
this
week
that
there
are
many
open,
PR's
requesting
signode
reviews,
some
of
which
have
been
open
for
six
plus
months
and
Natalie.
I
saw
that
you
had
responded
that
maybe
the
best
thing
to
do
is
to
attend
a
sick
note,
meeting
I
agree
that
sounds
wonderful,
I,
don't
think
I
should
be
the
person
to
do
it.
I
I
really
hate
to
push
co-chairs
in
front
of
the
bus
so
to
speak,
but
in
this
case
it's
going
to
be
with
both
hands
and
an
enthusiastic
shove
to
suggest
that
a
co-chair
be
the
person
to
go
and
say:
hey,
we
noticed
this.
How
can
we
support
you?
What's
the
best
way?
How
should
we
set
expectations
accordingly?
I
A
Thanks
so
much
I,
firstly,
as
as
one
of
the
people
would
be
in
front
of
the
bus,
absolutely
agree
with
you
that
probably
should
be
a
co-chair
or
a
tech
lead
that
jumps
in
and
I
think
being
able
to
go
to
cigno
to
actually
give
also
our
own
expectations
of
our
own
reviewers
and
our
proofers
that
we're
happy
to
also
close
PRS
after
a
certain
number
of
weeks.
A
If
there's
no
movement
and-
and
you
know
kind
of
contributions
coming
further
on,
especially
when
it
comes
to
revisions
or
clas
not
being
signed,
et
cetera
and
so
being
able
to
kind
of
nudge
them
in
a
in
a
direction
of,
let's
make
a
decision
around
when
we
can
act
when
there's
lack
of
reviewers,
lack
of
kind
of
lack
of
resources
and
kind
of
coming
to
a
happy
medium,
there
I
think,
would
be
a
really
great
idea.
Yeah.
I
So
closure
is
one
tool
and
I
notice,
as
I'm
wrangling
this
week,
that
there
are
also
a
lot
of
PRS
that
have
been
open
for
I.
Think
too
long
and
I
think
we
should
be
less
shy
about
closing
PRS
of
the
PRS
that
have
been
open
for
a
long
time
that
I
closed
just
last
night.
Two
or
three
of
them
have
reopened
I.
Think
like
getting
a
closure
notice
is
oftentimes
the
kick
that
contributors
need
to
be
like.
I
Oh
no,
that
actually
matters
and
reopen
their
PR
and
finish
the
work
that
said
I
don't
want
the
lack
of
a
Sig,
node
approval
or
technical
review
to
equal
automatic
closure.
Maybe
maybe
we
approve
they
get
the
chance
to
approve,
and
if
they
don't
review,
then
the
content
goes
out.
I
This
is
I
I
like
similar
to
closing
a
PR
and
like
getting
that
kick
sometimes
sending
out
the
wrong
information
can
be
the
thing
that
pushes
people
to
say:
that's
not
right
and
contribute
the
the
right
information
I'm,
not
saying
I'm,
not
saying
that
we
should
intentionally
obfuscate
and
send
out
terrible
information
just
that
there
are
I
want
a
broader
palette
than
simply
closing
PR's.
In
the
absence
of
a
review,
Tim
very
strong
feelings,
I
see
you
are
so
muted,
Tim.
A
B
E
Computers
so
for
seek
security
and
Security
reviews.
I
would
make
an
exception
from
what
Zachary
Sarah
has
just
said
for
what
I
hope
are
obvious
reasons.
A
Can
you
just
you
specifically
said
for
stick
security
Tim?
Is
that
correct.
A
I'm
gonna
fix
because
I'm
going
to
fix
some
of
these
notes
up
after
the
meeting,
because
I
can't
type
and
talk
at
the
same
time
it
seems
but
great,
yes,
completely,
agree.
I
I,
like
your
I,
like
that
I,
do
the
approach
Zachary
this
idea
of
sometimes
putting
out
not
so
great
information
can
actually
trigger
better
information
to
be
published,
but
obviously,
with
the
exception
of
security
in
some
areas
of
Seagulls,
where
that
could
actually
be
super
detrimental
to
what
we're
actually
trying
to
achieve.
A
A
You
know,
as
opposed
to
only
closing,
and
this
idea
of
a
larger
breadth
of
possible
solutions
to
maybe
not
having
a
lot
of
review
resources
and
a
lot
of
time
or
not
seeing
certain
Kings
and
and
so
on,
and
what
we
can,
what
steps
we
can
take
being
very
transparent
about
the
possible
steps
we
would
take
so
that
they
know
what's
kind
of
what's
to
be
expected.
I
think
is
the
is
the
best
approach
here
for
sure
yeah
great.
A
So
what
that
sounds
like
is
that
there's
a
to-do
for
putting
the
head
up
for
myself
to
attend
the
next
signode
community
meeting
to
actually
discuss
some
of
these?
What
I
might
do
is
Zachary.
If
you
don't
mind,
I
can
also
look
a
bit
later,
but
there's
a
couple
of
PR's
in
particular,
you
wanted
me
to
kind
of
push
as
like.
Here's.
I
A
No,
no,
that's!
That's
awesome!
If
it's
already
I
I
definitely
haven't
I
jumped
into
the
channel
yet
so,
if
it's
already
there,
that's
perfect.
That's
really
great
and
I'll
put
myself
on
the
agenda
for
the
next
meeting.
A
Let's
hope
it's
not
at
6
p.m,
Pacific
time,
because
that
would
be
horrible
in
Europe,
but
we'll
see
we'll
figure
it
out
for
sure
great.
Any
any
other
comments
on
this
specific
issue.
Around
reviews
for
stick
notes.
A
All
right
thanks
thanks
Zachary,
see
you
later.
Thank
you
so
much,
and
with
that
too
bye
Tim
as
well.
You
also
need
to
drop
well.
We've
actually
come
to
the
end
of
our
agenda,
so
we've
got
a
few
folks
saying
goodbye,
but
I
did
want
to
quickly
open
it
up
to
double
check.
Does
anyone
have
any
last
topics
that
they
wanted
to
suggest
discuss
as
we
have
some
of
the
time
we
do
have
a
few
minutes
left,
but
just
wanted
to
check.
H
I
just
wanted
to
raise
a
point
from
the
chat
which
is
about
our
localization
teams.
Of
course,
we
are
open
to
anyone
helping
out
on
our
localization
teams.
They
have
things
always
in
need
of
people
to
help
fix.
H
So
if
you
are
thinking
of
helping
in
that
area,
you
know
if,
hopefully
you
are
some
someone
who
is
fluent
in
the
language
you're
hoping
to
contribute
to,
but
otherwise
there
are
other
areas
that
you
can
fix
like
if
there's
a
broken
link
or
whatever
any
type
of
contribution
is
always
open,
but
specifically
for
translating
be,
hopefully
something
you
feel
fluent
in
and
comfortable
in
communicating
in
that
language,
but
I
do
believe
that
each
process
also
has
a
review
team.
H
So
if
there's
something
you
want
to
contribute,
you
can
also
work
within
those
stock
channels
in
that
review
process
to
to
kind
of
make
sure
it's
accurate.
If
it's
something
you
do
want
to
contribute,
so
just
wanted
to
raise
that,
because
I
thought
that
was
a
really
great
question
that
got
brought
up
and
hopefully
inspire
people
to
come
help
our
localization
teams.
A
Perfect,
yes,
that's
that's
a
really
really
great
Point
as
someone
who
has
fixed
a
bunch
of
broken
links
in
different
localizations
as
well,
myself
or
or
approve
them,
yeah,
total,
plus
one
and
and
thanks
for
that
really
great
discussion
as
well.
A
Alrighty
folks,
we've
had
a
great
crisp
official
meeting
today
with
a
few
with
a
few
different
points
to
raise
really
great
attendance.
Really.
Thank
you
so
much
for
everyone
taking
part
in
for
saying
hello
for
those
new
contributors.
Who've
said
hi
we'll
definitely
see
you
over
in
the
Sig
docs
Channel,
where
we're
always
open
to
questions
and
like
different
issues
and
PRS
you're
working
on
feel
free
to
link
them
in
the
in
the
in
the
channel
there.
A
If
you're,
looking
for
kind
of
direction
or
or
need
some
help,
I
would
ask
we
want
to
try
and
make
sure
that
we're,
not
tagging
or
adding
specific
people
in
the
in
in
the
channel.
However,
if
you've
had
someone
that
already
is
engaging
on
your
PR
great,
but
specifically,
we
try
and
make
sure
that
our
PR
Wranglers
are
the
ones
who
are
leading
a
lot
of
the
push
for
a
lot
of
our
peers
throughout
the
different
weeks.
So
we
can
share
the
workload
across
our
cross,
our
reviewers
accordingly.
A
So
again,
thanks
so
much
for
wherever
you
are
in
the
world.
I
hope
you
have
a
great
afternoon
evening
morning,
sleep
and
hopefully
we'll
see
you
online
for
our
slack
meeting
next
week
and
for
our
next
bi-weekly
waiting
in
two
weeks
time
stay
safe
and
healthy.
Everyone.
Thank
you.
So
much
for
joining.