►
From YouTube: Node.js Internationalization (i18n) Working Group
Description
A
A
A
Yeah
but
really
happy
to
have
you
all
and
thankful
that
you
know
we're
here.
We
have
a
lot
to
discuss
localization
not
today
and
how
we
can
support
each
other
immediately
and
there's
other
things
on
the
agenda.
I
would
like
to
discuss
those
in
earnest
the
people
who
primarily
represent
more
of
the
globalization
side
of
things.
A
Oh
thanks
thanks
so
I'm
gonna
appreciate
it
so
Steven
Loomis
is
usually
here
he's
not
here
with
us
today,
so
we
might
be
light
touching
light
on
globalization
and
we
do
have
Nick
with
us
who
is
definitely
interested
in
the
internationalization
side
of
things
so
setting
that
up
for
our
setting
up
our
localized
information
to
our
you
know,
deployed
targets
and
stuff
like
that.
So
we're
definitely
interested
in
that.
We
can
talk
a
little
bit
about
that.
A
However,
seek
is
not
here
today,
but
will
we
with
this
next
week,
as
he
said,
so
we
might
be
able
to
get
more
of
a
perspective
on
how
we
got
here
from
him
and
other
folks
to
discuss
interest
then,
but
let's
get
into
localization.
We
have
both
Alejandro
and
Thiago
here
today,
which
is
great
and
I
am
going
to
jump
into
the
minus--
I
will
post
the
minutes
link
here
and
the
chat
for
y'all?
A
B
A
Anyone
would
love
to
would
like
to
take
notes
today.
That
would
be
super
great,
no
pressure,
though
so,
let's
roll
through
agenda
topic
number
one,
which
is
localization
best
practices,
and
this
this
touches
into
some
things
that
Alejandro
and
myself
have
been
briefly
chatting
over
after
a
Twitter
push
a
couple
days
ago
for
internationalization
and
getting
excitement
in
that,
and
he
had
a
big
response
with
with
people
wanting
to
help
out
with
Spanish,
but.
A
Back
up,
you
know,
there's
kind
of
three
tiers
to
the
internationalization
working
group,
and
you
know
one
is
translation
and
that's
what
we're
doing
over
and
Crowden
and
the
crowd
and
service
and
another
is
taking
those
translations
and
deploying
them
into
our
tart
into
our
targets.
Like
our
document,
our
documentation,
our
website
things
like
that,
and
then
the
other
is
internationalization
within
node
itself.
Globalization.
The
int
object
that
kind
of
thing,
but
Alejandro
and
myself
we're
talking
to
the
day,
and
we
thought
that
it
might.
A
This
might
be
a
great
opportunity
to
discuss
how
we
can
create
a
better
collaboration
from
between
internationalization
and
localization
working
groups.
So
part
of
that
is
the
this
issue
that
I
just
spun
up
the
internationalization
of
localization
team
collaboration,
best
practices
guide,
I'm
sort
of
my
first
thought
was:
maybe
we
can
start
creating
a
guide
around
this
to
be
able
to
give
people
a
landing
spot
to
funnel
in
to
where
they
need
to
be
in
which
team
and
that
sort
of
thing?
A
C
A
B
A
A
Yeah,
absolutely
and
I
guess
that
that's
something
that
our
group
is
definitely
in
the
purview
of
our
group
and
something
that
we
should
do
is
I
think
just
taking
a
step
back.
We
need
to
create
a
proper
funnel.
That's
documented,
for
you
know
how
to
get
people
into
using
crowdin,
and
you
know
what
they
can
do
and
all
that
and
all
that
kind
of
stuff.
So
maybe
maybe
next
steps
next
steps
before
you
reach
out
to
the
people
who
are
interested
in
Spanish
or
I
mean,
like
obviously
other
people.
A
We
can
try
to
help
get
them
through
this,
but
maybe
you're
blocked,
really
because
there's
not
like
a
process
around
that
yeah,
which
is
what
I'm
gathering
so
like
the
next
steps
are
to
create
like
a.
How
do
you?
How
do
you
use
crowd
and
how
do
you
you
know
just
like
a
getting
started
guide
for
how
to
use
crowd
and
translating
for
node?
Would
that
be?
Is
that
would
that
be
the
most
helpful
thing?
C
A
Okay
and
then,
how
do
you
feel
like
over
time
like
how?
What
is
the
best
way
to
maintain
like
a
good
relationship
between
the
Spanish
working
group
and
oh
shoot
it's
read-only
like
I'd
like
to
maybe
you
can
chime
in
on
the
issue
that
I've
posted
here
in
a
little
bit,
but
you
know
I'd
like
to
identify
some
of
the
areas
that
you
know
we
can.
We
can
support.
You
know
working
as
translation
working
groups
better
over
time.
So
how
do
we?
A
What
what
kind
of
questions
do
we
need
to
ask
periodically
to
check-in
to
make
sure
things
are
okay
and
you
know
like
how
do
we?
What
kind
of
touch
points
do
we
need
to
have
to
make
sure
that
someone,
like
yourself,
is
kind
of
a
chant?
You
know
there's
like
a
champion
in
the
Spanish.
You
know
localization
team
and
that's
what
I
think.
C
B
C
C
A
Right
and
so
there's
kind
of
this
unclear
just
make
sorry
just
episode
of
message.
It
just
may
I
can
just
say
it
alone.
You
know
how
you
know
have
editing
priveleges
on
the
document.
Sorry
about
that,
thanks
for
coming
out
naked
pathologies.
So
yes,
there's
no
clear
directive,
but
there's
no
clear,
like
you
know
how
does
this
go
from
being
translated
to
being
on
the
website
right
and
I?
A
Feel
and
I
know
that
that's
that
sort
of
representative
of
the
fragmentation
of
the
current
state
of
this
working
group,
since
we
kind
of
spun
it
up
and
then
there
was
a
lot
of
activity
for
you
know
a
year
and
a
half
or
so
or
a
year,
maybe
something
like
that
and
so
we're
kind
of
we're
at
the
point
to
where
we
are
regrouping
and
picking
up
the
pieces
of
how
we
deploy
you
know
deploy
to
those
those
targets,
like
you
know,
no,
no
js'
dev
and
the.
A
Api,
Docs
and
stuff,
like
that,
you
know
no
js',
org,
okay,
no
problem,
but
so
I
feel,
like
you
know,
that's
that
sort
of
the
that's
just
in
the
nature
of
the
of
the
team
right
now
and
as
we
get
more
involvement,
you
know
with
people
like
Zeke
and
Nick,
and
you
know
other
folks,
I
know
I
think
it's
Alexander
has
really
been
trying
to
push
that
as
well
and
he's
blocked.
A
We
need
to
help
him
with
that
as
soon
as
possible,
but
there's
just
sort
of
the
nature
of
the
team
right
now,
so
I
think
thinking
on
that
and
a
broad
spectrum
of
like
what
is
useful.
You
know
what's
useful
for
translators
at
that
point,
maybe
maybe,
as
we
spin
up
something
like
a
user
guide
or
that
sort
of
thing
you
know
we
can
take
it
at
the
bottom
of
my
case.
You
know,
as
as
the
innovations
are
actually
oh
he's
gone.
A
A
A
A
You
know
like
the
internationalisation
pipeline,
so
they're
not
like
I'm,
not
sure
if
they're
gonna,
you
know
like
if
individual
contributors,
unless
yeah
I'd
love
to
think
that's
just
another
problem
to
get
in
a
get
to
get
the
localization
contributors
names
on
those
PRS
that
are
coming
through.
You
know,
I
think
that
would
be
an
interesting
one
that
we
should
figure
out,
because
we
want
people
to
you
know
if
you
recognized
for
their
work
as
well,
but
Alejandro.
A
All
we
were
talking
about
was
that
we'd
like
to
get
you
know
to
things
like,
maybe
at
the
footer
of
the
contributing
guide,
we
can
have
a
place
where
people
can
see.
You
know
have
links
to
see
where
there
localization
is
going
live
and
then
on
the
deployment
side
you
know
having
getting
there.
You
know
info
readily.
A
It's
awesome
any
general
thoughts
on
this
topic
of
relationship
between
localization
groups
and
our
teams,
and
in
this
group
and
I,
think
we've
kind
of
we've
talked
about
some
of
the
basic
stuff
that
we
need
to
do.
Obviously.
But
what
what
are
your
thoughts
and
is
there
any
other
points
of
discussion
within
that
scope?
That
you'd
like
to
you'd
like
to
bring
up
for
discuss.
A
A
What's
this
in
the
chest,
so
forget
that
whatever
I
said
just
made
that
doesn't
make
any
sense
that
was
remote
earlier
comment.
So
here
is
a
list
of
our
localization
teams
at
the
moment
and
I.
Think
in
addition
to
having
you
know,
documented
support
for
localization
teams.
Internationalization
working
group
needs
documented
support
for
like
just
like
exactly
what
you're
asking
Nick
like
how
how
do
you
know
like
how
do
we
identify
who
you
know
who's
that
who's
the
champion
for
which
group?
And
how
do
we
funnel
these
people?
A
You
know
to
the
right
people,
the
right
team,
that
sort
of
stuff
so
I
think
having
both
of
those
you
know
both
of
those
concerns
addressed,
would
be
extremely
helpful
because
you
know,
for
example,
all
the
Hunter
and
I
just
did
this
blast.
You
know
on
Twitter,
and
now
we
have
a
bunch
of
interest
and
now
it's
up
to
us
to
be
able
to
help
them.
A
A
Of
that
that
thing,
but
here
with
you
know
with
this
list
of
localization
groups,
I
think
like
next
steps
within
the
action
items
that
we
discussed
last
week,
part
of
that
is
going
to
be
touching
base.
You
know,
with
with
each
of
these
groups
and
seeing
like
kind
of
like
we
did
or
I
did
a
couple
years
ago.
You
know
when
we
were
switching
over
to
sort
of
a
new
model.
You
know
just
saying:
okay,
this
is
what
we're
kind
of
direction.
A
You
know
for
a
group
or
who's
interested
in
helping
be
the
the
point
person
if
you
will
so
that
when
we
do
these
blasts,
we
can
give
them
to,
or
you
know,
get
them
in
touch
with
those
individuals.
But
this
this
is
the
general
topology
of
of
our
localization
teams,
as
they
currently
stand,
I
think
I.
B
Because
something
like
Norwegian
there's
just
one
but
for
localization,
I,
think
of
more
the
English
Canadian
type
thing
versus
English,
like
the
English
or
Spanish,
would
be
the
internationalization
group.
But
there
might
be
locale
specific
teams.
I
didn't
realize
they
were
all
considered.
The
localization
teams
yeah.
A
Sorry
I
mean
I
may
be
throwing
verbage
around
here
that
crosses
over
definition,
but
I
think
what
you
know
like
what
I'm
talking
about
here
is
just
translation
in
there.
You
know
we're
calling
the
translation
of
localization
within
these
within
these
various
teams.
So
these
are
the
the
people
who
would
be
interested
in
translating
textual
assets
of
nodejs.
A
You
know
within
crowding
and
that
sort
of
thing,
but
as
far
as
like
there's
a
lot
I
think
there's
a
lot
of
legwork
that
we
need
to
sort
we
could.
We
could
almost
have
another
working
group
meeting
here
soon
between
Nick
between
you
and
me
and
Steven,
and
them
and
Zeke
probably
discuss
more
in
depth
like
you
know,
globalization
and
how
we
can
you
know
funnel
and
help
for
that
sort
of
thing
as
well,
but
I
think
primarily
these.
C
Yeah
I
was
going
to
mention
a
couple
of
things.
Hearing
from
other
teams,
which'll
actually
be
helpful
for
us
as
a
simple
example
to
say,
for
example,
communicating
with
within
all
the
team
members
for
the
Spanish
translation,
working
with
or
team
I'm,
so
not
sure
what
would
be
the
best
channel
say.
For
example,
the
open
is
slack
if
they
are
using
something
else
if
they
are
using
so
Peter
or
any
other
tool.
C
C
Forgot
the
question
that
I
was
going
to
ask
to
you
yeah
and
if
there
are
other
teams
that
are
I
know,
there
are
a
lot
of
of
them
that
are
really
active
if
they
are
doing
things
in
some
way.
That
would
be
very
helpful
from
from
hearing
on
what
they
are
doing
currently
how
they
are
finishing
these
things.
Yes,.
A
Yeah,
exactly
so
I
think
something
that
there's
no
yeah,
there's
no
groundwork
for
collaborator,
Urbina,
maintainer
guidelines,
I.
Suppose,
hey
Alexander
nice
to
see
you
welcome.
Oh,
so
all
the
hundred
yeah
there's
no
I,
don't
think.
There's
any
maintainer
guidelines
like
we
don't
we
don't
have
enough
definition
or
established
definition.
Yet
for
the
internationalization
working
group
or
for
localization
teams.
A
You
know
to
know
like
I,
don't
think
we've
arrived
at
the
we
have
a
level
of
abstraction
for
like
the
pipeline
and
how
things
should
work
and
those
are
still
you
know
not
fully
implemented,
but
we
also,
you
know,
need
to
really
define
you
know
how
best
practices
for
how
we
can
stay
in
touch-
and
you
know
how
maintain
errs
of
localization
working
groups
can,
you
know,
can
support
each
other
in
that
I
mean.
That
brings
brings
up
a
great
point
with
the
slack
channel
and
things
like
that.
I
mean
I.
A
Definitely
I'll
have
to
through,
through
my
position
within
conquer
the
community
committee.
I'll
be
able
to
you
know,
bring
bring
that
conversation
through
the
community
community.
Saying
like
hey,
you
know
within
the
open,
Jas
slack.
Maybe
we
can
have
a
you
know:
can
we
have
channels
for
each
localization
working
group,
because
that
would
be
super
helpful
and
a
great
way
to
get
people
collaborating
and
closer
proximity?
A
You
know,
rather
than
sort
of
just
one-off
issues,
and
things
like
that,
so
slack
channel
definitely
sounds
good
or
figuring
out,
like
a
central
place
for
communication
and
I've
been
thinking
about
spending
up
one
for
this
group
there
as
well.
So
let's,
let's
get
our
communications
in
order
and
then
we
can.
You
know
we
might
see
a
higher
frequency
of
communication
that
way,
but
I
think
that,
along
with
like,
as
you
said,
that
having
and
having
some
kind
of
guide,
you
know
for
localization
teams,
you
know
especially
for
maintainer
z'
would
be
would
be
good.
A
C
There
were
people
interested
in
helping
out
I,
know,
there's
a
fee
contributors
like
adrienne
and
alex
ramirez,
who
volunteered
as
well.
So
that
would
be
really
helpful.
They
couldn't
make
it
today,
but
they
were
interested
helping
facilitate
these
things
as
well.
From
my
point
of
view,
it
would
be
great
if
I
could
laid
down
the
groundwork
and
facilitate
all
the
people
that
have
reached
out
I
mean
yeah,
I
wrote
some
some
guidelines
and
help
them
stay
in
touch
and
have
a
tool
say,
for
example,
to
not
have
the
same
people
translating
the
same
document.
C
A
Supporting
folks
like
yourself,
who
are
gathering
with
other
maintainer
x'
for
local
localization
groups,
is
helping
them
yeah,
like
helping
them
know
how
to
like,
where
to
look
for
those
things
in
cronin
because,
like
you
can
see,
I
mean
like
if
you're
using
it.
You
know
you
can
see
like
Oh.
Nineteen
percent
of
this
document
has
been
translated
or
whatnot,
and
you
know
there's,
like
other,
really
handy,
there's
another
really
handy
yeah.
It
is
there
that
you
can.
You
can
reference
while
you're
working,
but
you
know
yeah,
I,
think
okay,
yeah.
C
I
I,
missed
I,
think
most
of
the
discussion,
but
most
part
of
discussion,
but
yeah
I
think.
Firstly,
we
need
to
think
and
configure
our
process
and
just
then
start
thinking
about
how
we
write
our
guides
and
other
things,
because
for
now
I
am
not
100%
sure
how
it
should
be
and
how
it
will
be
and
I'm
sure
that
someone
else
know
how
it
will
be,
and
in
that
case
I
I
think
nobody
can
write
some
guide
or
some
documentation
about
that.
C
A
If
there's
no
place
for
this
to
get
for
the
stuff
to
get
deployment,
then
there's
nobody.
You
know
like
we
gotta
get
that
set
up
right
away
and
so
Zeke
I
know
Zeke.
Who
was
leading
a
lot
of
that?
You
know
when
we,
as
we
first
found
out
this
working
group
a
couple
years
ago,
is
still
very
interested
in
working
with
us
on
that,
and
so
he
was
not
able
to
make
it
today,
but
will
be
here
at
the
same
time
next
week.
A
So
I
think
we're
gonna
spend
a
lot
of
time
discussing
how
we
can
we
can
get
more
of
that
set
up
and
unblock
folks,
like
yourself,
I
know
that
there's
some
pretty
simple
made
like
you
just
right
now,
I
mean
to
unblock
translation
processes
for
the
nodejs
website,
user
and
crowd,
and
you
just
need
for
that
user
just
needs
permissions,
I
think
global
permissions
from
node.
So
I,
you
know
that's
something!
A
That's
on
my
agenda
to
do
as
soon
as
possible,
hopefully
today
but
yeah
we'd
like
to
get
you
unblocked
and
and
get
that
set
up,
but
as
far
as
deployed
targets
and
that
sort
of
thing
you
know
where
we
need
to
maybe
someone
like
Nick
and
you
Alexander
and
Zeke,
and
myself
and
other
folks
can
set
up
a
working
group
meeting
with
the
owners
of
those
deployed
targets.
The
API
Docs
and
the
the
website
working
group
I
think,
would
be
a
great
one.
A
So
I
think
that's
our
that's
our
next
steps
for
getting
that
unblocked
is
setting
up
that
user,
and
then
you
know
making
sure
that
we're
on
this
on
the
same
page
with
that
with
those
groups
who
own
those
projects
but
yeah,
but
thank
man,
I'm
so
I'm
so
excited
that
we're
all
here
were
finally
discussing
this
and
yeah
it's
good
to
it's
good
to
get
together
and
make
this
happen.
Oh
cool.
So
let's
see
the
next
item
on
the
agenda
was
update.
A
Our
guides,
which
was
number
two
ten
I,
think
that
was
in
tandem
with
the
last
one
I
think
we
kind
of
discussed
this
in
a
you
know
for
mostly
through
the
last
discussion
it
was
sort
of
all
tied
in
you
know.
We
needed
to
update
our
contributing
and
getting
started
guides
to.
You
know
facilitate
a
good
place
for
people
who
are
either
interested
in
globalization.
A
You
know,
select
the
int,
L
object
or
localization,
you
know,
or
setting
up
so
they're
working.
You
know
like,
within
this
specific
repository
you
know
so
there's
there's
a
few
different
places
where
people
can
get
involved,
but
we
need
to
make
those
guidelines
clear
as
to
how
they
can
contribute
in
what
they
can,
what
they
can
do.
So
updating
that
I
think
is
also
pretty
important.
A
A
A
We
sort
of
picked
this
time
out
of
a
hat
between
four
people
who
were
at
the
first
working
group
meeting
so
that
this
seemed
to
be
a
good
time
for
to
me.
However,
the
other
four
people
aren't
here
today,
so
this
little
but
have
you
know
said
this
was
a
generally
good
time
if
you
are
sincerely
interested
in
joining
us
on
these
on,
like
a
weekly
call.
A
Well,
you
know
like
please
chime
in
on
this
issue
and
tell
us
you
know
like
either
like
this
doesn't
work
for
you
and
if
we
get
a
couple
of
people
saying
hey,
this
doesn't
work
for
us.
Then
we'll
you
know
spin
up
a
doodle
and
then
try
to
get
a
new
meeting
time,
but
what
I
think
might
we
might
actually
have
to
do
based
on
the
nature
of
time?
A
Global
time
is
have
two
different
meetings,
so
one
that's
more
a
you
know
a
workable
time
for
people
who
are
saying
like
Central,
European,
Time
or
whatnot,
and
then
or
you
know,
like
Asia
or
whatever,
and
then
you
know
one
that's
over
here
as
well,
so
we
might
have
to
maintain
two
different
working
group
meeting
times
in
order
to
maintain
parity
through
all
the
people
who
are
interested
in
working.
But
as
far
as
the
folks
who
are
here
is
this
like
for
the
next,
you
know
a
few
weeks.
A
B
A
C
No
yeah,
no
no
I
have
something
I
started
looking
on
that
I
think
improve
it
in
previous
year
and
there's
slow
progress.
But
finally,
we
started
making
a
call
starting
discussing
this
and
I
hope.
We
will
fix
this
soon,
so
yeah.
Firstly,
I
need
I
investigated,
maybe
three
or
four
hours
in
research
about
how
we
can
connect
trevean
with
no
GS
org
and
no
GS
documentation
repositories
easily
for
us
and
safely
from
security
points
like
to
share
permissions
and
other
stuff
and
the
options
that
I
posted
in
the
issue
is
I
know
the
most.
C
Is
a
good
fit
for
us
because
it's
not
require
any
access
to
repository
for
someone,
some
specific
person,
for
example
for
me,
and
it's
just
creating
a
token
that
has
limited
permissions
and
it's
okay
and
we
also
can
start
managing
everything
from
crowd
to
crowdinside.
Also,
I
I
just
want
to
explain
how
it
looks
now
so
I
I
am
like
and
sorry
I,
don't
remember.
Who
else
has
manager
permissions
in
crowdin
in
current
crowd
in
project
you
yo
area?
C
Okay,
so
if
you
managers,
we
already
have
and
yeah
that's
great,
but
0.1
Crowden
has
updated
version
of
croydon
like
crowd
in
2.0.
It's
like
herding,
foreign
organizations
and
I.
Think
if
we
us
have
have
some
progress
on
current
in
current
project
on
old
platform
and
also
I
connected
lease
crowd
and
team,
there
explained
me
how
we
can
migrate
current
progress
from
old
platform
to
new
platform,
it's
possible,
so
I
think
we
need
to
start
thinking
about
using
a
new
platform
instead
of
old.
It's
the
first
point.
C
Second
point:
we
need
to
think
in
some
way
how
we
manage
all
this
stuff,
because
we
have
I
am
not
sure
how
it
works
in
crowd
in,
but
we
can
make
a
few
managers
or
from
our
side
and
then
we
need
to
assign
in
some
way
proof
leaders
or
each
language
that
we
want
to
support
and
I'm,
not
sure
in
what
way.
We
will
do
this
because
I
also
contributing
to
get
bgs.
They
also
start
with
their
translation
process
and
they
doing
like
in
a
way
if
someone
wants
to
handle
their
language.
C
Please
write
something
in
comments
of
this
video
I
wrote
a
comment
and
now
I
am
a
manager
of
Russian
language,
but
I
think
it's
not
very
good
way
because
it's
open
source,
but
we
need
to
manage
good
people
in
some
way
because
we
can
assign
to
someone
rights
of
proof
reader.
But
then
it
this
guy
meet
somewhere
and
it's
not
a
good
idea,
because
without
proofread
we
can't
publish
any
translation
to
to
life.
So
we
need
to
start
thinking
and
about
all
processes
and
I.
C
I
have
I'm
trying
to
keep
in
mind
all
this
stuff,
but
it's
really
hard
so
that
I
am
trying
to
organize
the
first
question.
If
it's
is
about,
do
we
want
to
migrate
to
a
new
platform
of
crowding
or
we
want
to
still
use
a
first
version.
It's
a
first
question
and
second
question
is
about
permissions,
but
it's
related
to
the
first
question.
C
If
we
decided
to
go
to
the
next
version
of
platform,
we
need
to
use
another
token,
it's
a
important
point
to
know
so
yeah
first,
we
need
to
and
I
know,
discuss
with
everyone,
maybe
with
most
active
guys,
that's
already
on
call.
Maybe
we
can
create
an
issue
where
I
provide
the
links
and
each
of
us
can
test
the
new
platform
beside
benefits
and
other
things,
and
if
we
decided
to
go
with
you,
okay,
let's
go.
Isn't
you
if,
if
now,
let's
a
little
bit,
let's
stay
on
the
old
I?
C
A
So
great
that
was
so
great.
It
was
very
concise
and
in
the
very
poignant
and
exactly
what
we
need
to
discuss
right
now
and
I
was
trying
to
take
some
good
notes
so
that
we
can
create
some
action
items
and
issues
around
that
I
think
one
thing
that
did
spawns
spin
out
of
that
that
would
be
great
is,
if
you
wouldn't
mind,
Alexander,
making
an
issue
about
testing
out
the
new
platform.
A
That
would
be
super
good
just
to
get
people
who
are
interested
and
knowledgeable
about
that
within
the
team
to
be
able
to
discuss
that
and
test
it
out
together.
Just
to
you
know
as
a
springboard
for
us
to
talk
more
about
that.
That
would
be
awesome.
Okay.
So
if
you
don't
mind
like
opening
an
issue
about
that,
that
would
be
really
great
yeah
and
as
far
as
the
other,
you
know
the
other
things
here.
A
Yeah
we
do
need
there
has
been
slow
progress.
This
is
really
great
as
far
as
like
a
sort
of
roadmap
for
how
we're
gonna
get
that
set
up.
I
do
know
that.
So,
on
the
other
side
you
were
saying
like
we
don't
know
how
the
API
documentation
gets
compiled,
there's
definitely
folks
that
I
can
reach
out
to
what
I
what
I'd
like
to
do
is
get.
The
members
of
this
group
would
like
to
discuss
this
at
length
on
the
call
for
next
week,
and
then
maybe
we
can.
You
can
open
that
issue.
A
We
can
talk
about
it
and
then
like
reconvene
within
a
week
with
the
with,
like
Zeke,
who
said
he
was
going
to
be
able
to
join
next
week.
So
you
know
it'd
be
great
to
have
you
and
Zeke
and
other
folks
on
the
call
who
we
can.
You
know
we
can
work
through
this
with
as
well
spending
out
these
issues,
so
I
think
that
would
be
super
great
and
then
yeah
and
then
just
taking
down
these
notes.
Here,
though,
the
other
big
point.
A
Yes,
so
here's
the
thing
I,
we
don't
just
as
in
in
line
with
what
Alejandro
is
saying,
you
know
we
we
don't
have.
We
don't
have
like
crowd
and
best
practices
guides
yet
for
translators,
and
that's
also
going
to
have
to
take
in
mind
how
track
how
crowd
in,
like
Miska,
obviously
gonna,
have
to
take
in
how
crowd
and
works
and
how
you
work
as
a
proofreader,
or
you
know,
a
manager
or
whatever.
A
So
there's
some
there's
some
organizational
problems
that
are
inherent
between
how
crowded
works
and
then
how
localization
groups
will
have
to
work
accordingly
to
to
create,
like
you
know,
as
streamlined
process
for
translation
as
possible
as
easy,
a
process
for
translation
as
possible
and
as
solid
as
you
were
saying
so
like.
If
you
know
we
don't
want
to
just
have
people
like
leave
a
comment
and
then
their
manager
or
whatever
you
know.
A
We
need
to
be
able
to
figure
that
out
and
have
those
roles
be
defined
so
in
or
the
process
to
becoming
those
roles
be
defined
so
that
within
a
contributing
guys,
so
that
you
know
there's
a
step
to
a
step
to
be
able
to
become
that.
You
know,
probably
after
discussing
it
with
localization
groups
or
with
you
know,
with
the
champions
of
the
localization
teams,
all
owner,
you
have
your
hand
open
or
hand
opened
up.
Yes,.
C
I
do
have
the
question
very
specific
one
that
you
might
have
addressed
before
I'm,
not
sure.
As
of
the
documentation
website,
the
API
is
now
our
version
correct
and
what
I
could
find
on
crowding
is
not
versioned
at
all.
My
question
would
be
if
that's
by
design
and
we
are
not
planning
on
translating
every.
A
Yeah
I
think
I
think
it's
more
about
pragmatics
right
now,
so
I
do
know
that
there
is
definitely
interested
in
translating
like
every
version.
However,
I
also
know
that
within
the
interests
or
the
current
within
the
current,
you
know
participation
within
this
group
I
think
what
might
be
pragmatic
is
to
you
know,
get
all
of
our
all
of
our
team
structure
and
infrastructures
set
up
to
a
basic
MPP
because
I
we're
not
even
really
out
the
door
yet
there
right.
So
we
need
to
I
think
we
need
to
just
choose.
A
You
know
whatever
the
LTS
version
is
or
whatnot.
You
know
that
we've
been
translating
and
just
roll
with
that.
Until
all
of
this
is,
you
know,
set
up
and
then
and
then
you
know
slowly
open
the
the
firehose
I
guess
more
and
more
slowly
like
introduced.
You
know
more
things
to
translate
over
time.
So
from
a
pragmatic
perspective,
I
think
it's
most
important
to
like
translate.
You
know
LTS,
but
then
you
know
beyond
that.
Yeah
would
be.
It
would
be
ideal
to
target.
A
A
C
A
C
Yeah
and
though,
and
also
sorry,
I
I,
just
want
to
I,
give
you
some
information
about
how
codeine
works
in
Croydon.
You
can
set
up
a
first
point
when
we
are
synced
with
our
repository.
We
sync
all
we
can
configure
in
any
different
ways.
We
can
think
you
know
in
one
project,
different
branches
and
set
up
some
specific
versions
for
each
branch,
and
we
can
configure
all
of
that.
A
That's
great,
that's
great
I
think
this
is
something
that
yeah
we
did.
We
talked.
We
obviously
don't
want
people
to
waste
time,
and
so
this,
that's
that's
all
the
internationalization
work
and
maintainer
ship
here
to
keep
up
to
date.
So
yeah,
there's
I'm,
just
glad
it's
like
it's
a
it's
almost
painful
to
recognize
that,
but
then
also
know
that
yeah.
We
need
to
keep
this
updated
so
that
people
are
updated
and
prioritized.
As
you
said,
so
people
are
updating
the
right
thing
at
the
right
time.
A
Absolutely
I
think
that
that
is
just
that's
going
to
be
messaging
best
practices
so
like
if
we
as
we
discussed
before,
if
we
set
up
slack
or
slack
and
Twitter
I
would
suppose
might
be
a
good
place
to
say:
hey,
we
pulled
the
lid,
you
know
like
I
mean,
or
you
know,
we're
like
obviously
get
up
as
well.
If
people
are
following
along.
A
For
translators
and
getting
that
messaging
out
to
translators,
it's
a
little
there's
a
little
bit
more
abstraction,
because
you
know
translators
are
checking
crowd
and
maybe
there's
ways
to
message
that,
obviously
across
the
group
within
crowded
as
well,
it's
probably
more
central
than
this
too
so
like
I,
think
if
we
make
sure
that
we
have
a
communication
blast
to
the
translators
every
time
you
know
we
pull
latest
Docs
and
that
kind
of
stuff
that
would
be.
That
would
be
ideal.
A
A
Okay,
so
we
had
a
couple
other
things
here:
one
was
publishing
an
NPM
module,
I,
don't
think
we're
quite
and
with
like
four
minutes
left.
We
don't
really
need
to
talk
about
that
in
earnest
today,
as
we
will
probably
do
it
next
week
when
we
have,
you
know
we're
talking
about
unblocking
the
translation
process
and
getting
that
set
up
with
you
know
the
the
API
documentation
and
things
like
that.
A
Let
me
not
only
under
Alexandra
starting
to
in
two
ways:
I,
don't
thought
Xavier
had
any
thoughts
on
that
before
we
move
on
or
anything
no
great,
okay
cool,
then
the
other
thing
is
creating
a
crowd
and
glossary
with
the
couple
minutes
that
we
have
here,
I
think
we'll
just
punt
that
to
the
next
that
will
go
to
the
next
thing.
That
is
not
an
issue
but
needs
to
be
an
issue
that
I
just
wanted
to
throw
out
there
so
crowding
a
glossary.
A
We
need
to
create
a
glossary
of
sort
of
reserved
words
and
things
that
you
know
may
get
lost
as
we're
translating
that's
a
general
idea.
If
anybody
needed
to
know
about
that.
So
it
translators
have
a
reference
sheet
so
that
they
can
say
like.
Oh
you
know,
oh
don't
translate
that
or
you
know
then
there's
all
there's
also
the
fuzzy
line
between
sometimes
you
know
sometimes
certain
idioms
though
they
are
common
in
English.
Maybe
don't
translate
well
at
all.
A
A
A
C
B
A
A
A
So
a
lot
of
what
we
talked
about
you
know
so
far
has
been.
Regarding
localization
and
trained.
You
know,
translation
translating
you
know
our
text
into
into
various
languages.
The
other
is
setting
up
the
infrastructure
and
that's
obviously
number
one
like
what
we
have
with
without
an
infrastructure
setting
up
the
infrastructure
to
be
able
to
deploy
our
localized.
A
You
know
documentation
and
things
like
that,
and
then
the
other
point
that
we
need
to
you
know
we'll
probably
discuss
more
next
time
Steve
in
this
year.
Stephan
Loomis
is
how
do
we
onboard
folks
who
are
more
interested
on
the
side
of
maintaining
the
int
L
object
and
how
we
internationalize
things
within
node
itself?
So
that's
definitely
something
that
you
know
various
people
are
interested
in
and
is
under
the
purview
of
the
internationalization
working
group
in
nodejs.
A
These
these
two
things,
these
two
disciplines,
you
know,
seem
relatively
different,
but
they
are
mutually
supportive
kind
of
like
how
languages
evolved.
So
you
know
how
how
there
might
be
a
delegate
and
a
invited
expert
relationship
within
you
know,
like
a
language
standards
organization,
is
kind
of
how
to
think
about
that.
The
work
we
do
supports
the
internationalization
of
node
and
JavaScript,
and
then
you
know
that
helps
us
understand
how
to
create
a
symbiotic
relationship
between
how
we're
translating
and
how
it's
used.
A
You
know
how
we're
using
the
int
objects
and
things
like
that,
so
we're
definitely
interested
in
evolving
that
conversation
and
how
we
can
get
people
more
interested
and
yeah.
You
know
helping
out
the
evolution
of
that
and
note
as
well,
and
Steven
can
probably
help
us
more
with
that
next
week,
where
we
are
at
time.
Did
anybody
have
any
last
thoughts
on
that
particular
issue
or
or
anything
that
they'd
like
to
discuss
today?.