►
Description
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/summit/issues/164
A breakout session for members of the i18n WG to cover how we can continue to push forward efforts like:
* l10n: CommComm Initiatives for internationalizing the API docs, and the website redesign project.
* Intl in Node.js: How the i18n WG can focus on supporting current Intl development in node core, and get more folks to help out with the core WG.
* The i18n WG's role in ECMA 402: How we can scale the i18n WG's involvement and support for tc39 in ECMA 402, and what the current needs are that Node.js representatives can fulfill for pushing JavaScript's Intl specification forward.
B
C
D
E
B
A
For
work,
consulting
for
Vincent
finished
consulting
company
here,
because
I
found
it
interesting
and
fun
to
work
on
JavaScript
localization
projects.
Message
format
is
projects
I
maintain,
which
is
now
no
bjs
project
also
make
plural
and
they're
the
intramural
rules.
Polyfill
is
his
mine
and
I
recently
have
started
messing
around
with
the
fluent
project
that
Mozilla
has
grown
a
compiler.
G
A
F
F
G
B
E
E
E
E
H
I
work
on
tc39
on
different
specifications,
including
I,
can
afford
to,
and
so
yeah
would
be.
If,
if
folks
are
interested,
one
thing
we
could
we
could
talk
about
is
like
what
proposals
are
being
discussed
and
what
things
we
should
discuss.
But
Emily
mentioned
message,
format
and
well:
I,
guess
that
was
sort
of
a
different
context,
but
to
make
internationalization
work
for
node.js.
I
C
So
I'm
Stephen
Lewis,
coming
to
you
from
sunny
California,
you
can
see
the
Sun
in
the
background
there.
It's
the
Sun
Sun
is
scheduled
so
and
I
work
for
IBM's,
global
foundation,
esteem
and
I.
Work
on
I,
see
you
in
cldr
libraries,
for
with
the
Unicode
project
and
with
JavaScript.
One
thing
I've
I've
been
involved
in
is
getting
no
I
C
to
be
on
by
default
in
node
version
12.
J
E
Sounds
great
welcome,
well,
what's
your
story.
E
E
So
if
you
go
to
the
no
J
summit
issues
I,
can
everybody
find
that
if
they
like
and
then
go
to
should
be
at
the
top
of
the
list
and
so
I
just
updated
it?
What
it's
164
scroll
down
to
the
bottom
there?
At
the
last
comment,
I
published
the
agenda,
as
someone
said,
I
think
it
was
Dan.
This
can
be
a
dynamic
agenda,
so
please
feel
free
to.
A
E
E
The
service,
the
crowd
in
service
to
perform
as
a
landing
for
translators,
to
be
able
to
translate
those
and
we've
set
up
the
automated
with
the
automation
of
putting
translations
in
as
PRS
and
to
our
documentation
repository
right
now,
so
there's
that
translating
our
stuff
and
the
next
would
be
int
Oh,
implementation
and
OGS,
which
is
where
Stephen
and
other
folks
are
involved
and
we'll
get
into
talking
more
about
Oh
Stephen.
Did
you
were
you
able
to
get
the
agenda.
C
E
Okay,
cool
awesome,
so
I'll
give
some
room
to
Stephen
to
update
us
on
that
and
just
a
little
bit
that
we're
excited
to
figure
out
how
to
support
that
team
more
and
create
ways
to
contribute
to
that
initiative,
and
then
we
also
concern
ourselves
with
support
for
tc39
and
402.
We're
excited
to
hear
from
Dan
today
on
current
status,
on
all
the
things
and
figure
out
ways
that
we
can
and
what
the
needs
are
and
how
we
can
support
support
them.
E
E
E
Publish
it
as
an
NPM
module
so
that
you
can,
you
know,
consume
it.
So
I
think
like
we're
just
this
kind
of
just
like
a
quick
update
and
then
like
you,
leave
on
to
other
things,
but
we
yeah
I,
guess
the
the
next
steps
are
to
set
up
an
NPM
account
published.
You
know,
publish
the
the
module
and
update
in
version
from
there,
and
all
this
to
say
you
know,
like
I,
think
as
we
create
a
project
board
for
that
and
I
would
love
it.
E
F
We
have
a
lot
of
feature
edition,
static,
node
morrow
morning
first
event,
tomorrow
morning,
website
redesign
and
what
next
steps
are
I
but
yeah,
so
we're
we're
not
immediately
blocked
by
it.
It
will
be
a
locker
for
switching
it
over
to
the
main
domain
when
that
choice
was
made.
So
I
did
from
what
it
sounds
like
that,
we're
mostly
going
to
be
working
in
markdown
files,
we're
gonna
be
pulling
from
a
number
of
sources,
I
believe
we
don't
want
to
break
up
documentation
from
the
court
ridox
all
of
them
on
site.
F
We
don't
want
to
we're
not
at
the
moment
all
the
kind
of
like
learning
documentation
like
getting
started.
Documentation
does
live
in
the
node-red
repo
right
now,
but
we
may
also
start
pulling
in
files
from
other
repos
like
it
would
be
nice
if
community
page
stuff
could
live
in
the
Hong
Kong
repo.
You
know,
try
and
keep
documentation,
we're
living.
F
F
We
then
have
the
flip
side
of
this
problem.
We're
actually
after
stuff
is
scooped
in
translated
through
and
the
mando
is
published.
I
need
to
make
sure
that
we're
updated
so
like
we
need
something
like
greenkeeper
or
something
up
there
just
to
keep
keep
this
thing,
auto
updating
on
the
regular.
If
we
do
go
the
module
route
for
disseminating
translations.
F
Currently,
it
will
be
yeah
right
now,
the
page
as
it
is
just
comes
from
up
there.
You
design,
it's
literally
just
like
a
little
digest
that
Deb
is
a
microsite
that
just
has
getting
started.
Documentation
like
starting
to
learn
note,
but
we're
gonna
expand
it
to
have
API
Docs,
homepage
downloads,
page
community
pages,
so
we'll
be
pulling
from
a
number
different.
I
I
G
E
F
We
may
want
to
consider
when
publishing
that
module
for
like
publish
a
different
one
for
repo,
so
that
we're
not
like
it's
something
bumps
in
the
API
Doc's.
We
need
to
bump
the
text.
Translations
or
you
know,
learn
documentation.
Just
keep
that
separation
concerns
there.
G
I
F
A
E
F
E
E
I
think
even
I
should
stay
in
touch
about
how
we're
going
to
utilize
that
you
know
if
that's
I'm,
just
trying
to
cite
like
should
internationalization
consume
one
thing
from
you
or
should
we
target
all
those
things
to
since
they
might
all
be
the
source
of
truth,
because,
like
getting
down
to
one
source,
the
truth
would
be
nice,
but
okay,
yeah,
great
I,
think
in
the
interest
of
time
and
other
stuff
we
can
push
along.
Do
you
have
any
questions
for
me.
E
I
also
have
other
yeah
I've
been
doing
some
documentation.
Automation,
I
work
for
this
sort
of
thing.
So
when
would
you
think
when
you
do
get
to
the
point
to
where
you
need
to
set
up
like
a
green
keeper,
or
something
like
that?
Let
me
know
because
there's
definitely
ways
that
we
should
hook
it
into
releases.
I
think
is
the
most
important
thing.
So
you
know
cool
okay,.
E
E
E
My
my
only
question
here:
free
Steven
as
far
as
facilitating
a
18m
repo
is
something
I've
noticed
is
there's
a
few
people
in
the
int
L
github
team
or
like
in
the
nodejs
team,
and
it
just
seems,
like
you
know,
there's
not
a
great
window
for
contributors
to
line
or
to
help
with
getting
into
you
know
supporting
int
L
like
in
ojs
core
and
like
it's
like
there's
a
few
like
a
handful
of
active
people
working
on
those
issues.
We
have
a
tag.
E
C
C
It
should
be
a
lot
easier
to
come
access,
the
what's
happening
with
those
projects
and
even
open
a
PR
into
upstream.
So
I
know
if
that
answers
your
question,
but
in
the
so,
for
example,
from
my
my
history
getting
nodejs
into
sorry,
getting
international
turned
on
by
default
in
nodejs.
12
was
a
major
milestone
because
the
until
support
was
there
before,
but
it
was
optional
and
had
this
build
process
and
the
big
the
big
issue
with
that
was
data.
Loading
and
data
loading
remains
a
major
issue.
C
E
C
Yeah
I'm
typing
directly
into
that,
if
I,
don't
click
close
one,
okay,
so
I
put
a
link
to
a
open
question
on
full
ICU
NPM
and
it's
kind
of
a
question
of
whether
the
data
loading
for
fall
ICU
should
should
move
out
of
NPM
into
Adobe
get
because
we
get
a
lot
of
concerns.
There
was
one
just
went
open
just
a
few
two
days
ago
about
the
way
the
FO
ICU
project.
Actually
works
and
fall.
I
see
is
just
a
loader.
It's
not!
C
E
E
Like
I
think
that's
something
that
we
can
evolve
and
figure
out
how
to
so.
The
thing
that
I
perceive
is
there's
going
to
like
looking
from
looking
from
sort
of
like
a
high
level,
people
who
are
getting
involved
in
this
repository
library
and
the
work
at
the
internationalisation
working
group.
We're
just
gonna
need
a
verbose,
contributing
guide
that
basically
brings
to
light
everything
that
you
think
you
just
said.
You
know
like
from
sort
of
the
ground
up
and
yeah.
C
E
You
know
the
int
L
object
and
that
sort
of
thing
so
I
think
like
creating
a
contribution
guide
there
that
is
sort
of
like
a
knowledge
dump
and
then
how
to
support
Unicode
would
be
a
great
place
to
start
as
well
as
yeah
I
guess.
I
just
want
to
figure
out
how
we
can
bleed
more
help
into
what
you're
doing
so,
the
more
that
we
evolve.
That
conversation
through
the
ITN
repo
of
the
better
I
think
right.
C
E
C
Yeah
that
that's
a
that
there
isn't
there's
an
issue
open,
that's
for
exactly
that
and
I
can
I
can
try
to
link
that
one
in
here
I
mean
I
thought
that
would
be
my
preference
I
mean
the
the
terms.
English
only
are
kind
of
grading
shall
we
say:
I
mean
that's
kind
of
what
I
spend
my
career.
Trying
to
avoid
is
English
only,
but
the
the
the
issue
with
that
is
is
is
just
download
slice,
but
I'll
put
a
link
to
the
issue.
C
I
would
I
would
certainly
support
that,
but
the
other
thing
that
we
could
do
is
have
downloads
provide
both
so
basically
just
how
a
prebuilt
binary
there's
a
small
one.
If
you
really
want
to
download
a
small
one,
but
basically
you
know
encourage
people
to
just
download
just
download
the
full
full
content.
F
C
G
C
C
That's
constrained
in
terms
of
no
runtime
footprint
like
if
you're
right,
if
you're
running
on
a
server
and
you're
paying
for
the
disk
space,
you
know,
but
so
it's
a
it's
a
valid
concern,
but
I
think
I
think
there's
some
value
to
having
the
default
be
be
full
just
so
that
it
reduces
the
pain
point,
because
it's
always
the
issue
right.
We
get
these
issues
once
in
a
while
and
node.
Basically,
my
date
format
doesn't
work
and
the
reason
is
because
you're
not
using
English
and
it
it
what's
the
phrase
the
objects.
The
objects
aren't.
J
It's
like
it's
like
how
many
people
are
in
this
situation,
where
they
need
to
run
node
on,
like
a
Raspberry
Pi,
a
very
constrained
versus
how
many
people
are
there
that
are
just
running
node
in
development
environments
to
run
backpack
or
run
in
a
container
or
on
the
server.
But
they
don't
really
care.
They
probably
dump
like
tens
and
thousands
of
megabytes
and
node
modules.
Yeah.
J
It
so
like
could
like
the
default
distribution,
have
it
included
and
then
there's
a
another
binary
distribution
like
a
separate
package
like
no
no
ICU
or
something
like
that.
That
is
like
the
raspberry
pi
users
can
download,
and
they
would
probably
be
aware
that
they
they
want
to
go
for
the
minimum
one
more
so
than
the
people
not
know.
A
Did
is
no
I,
don't
think
that
personally,
I
don't
believe
that
an
argument
that,
oh
because
of
our
thing,
we'd
like
to
increase
the
size
of
node
by
50%
or
100%.
Oh
sorry,
that's
not
gonna
fly,
but
would
it
be
conceivable
or
considerable
to
think
about
D
specializing
English
and
rather
make
it
explicit
that
this
distribution
that
you're
downloading
has
just
English
in
it
and
possibly
in
parallel
with.
C
A
E
F
F
C
So
basically,
there's
a
package
called
fall
ICU
and
if
you
do
npm
install
full
ICU,
it
turns
around
and
duck
and
installs
installs
the
data
for
you
as
a
package.
But
the
thing
is
that
the
the
data
needs
to
be
configured
at
startup
time
of
noted
v8.
So
you
can't
you
can't
just
include
it.
It's
not
really!
It's
not
really
a
module.
C
It's
kind
of
just
a
post
installed
loader
hack,
but
it's
a
way
that
you
can.
You
can
get
the
data
on
your
disk
by
adding
it
to
package
JSON,
and
this
is
documented
in
the
in
the
in
the
readme
yeah
on
the
agenda.
We
have
a
link
to
fall.
I
see
NPM
number
36
is
my
question
about
pulling
from
ICU
github
release.
Instead
of
doing
a
and
a
post
install
sorry
having
a
post
install
script,
just
do
it
download,
basically
like
a
just
to
fetch
from
github
rather
than
turning
around
and
reinstalling
a
sub
package.
D
C
D
C
F
C
You
know
npm
install
and
require
this
module,
doesn't
do
what
npm
install
and
require
a
module
usually
does
which
is
pulling
functionality.
So
that's
hack,
number
one.
This
is
hack.
Number
two
is
that
it's
you
know
any
package
manager
is
trying
to
manage
the
transitive
dependencies
and
this
in
this
it
breaks
that
by
what
when
in
post
install
it
goes
and
installs
another
package
and
which
package
installs
depends
on
the
Indian
Asst
and
the
version
of
node
that
you're
running,
so
you
can't
predict
it
at
you
know
original
install
time.
C
J
G
J
C
I
E
H
A
H
The
Intel
API
provides
things
like
date-time
format,
where
you
put
in
a
date
and
you
you
can
put
in
formatting
options
like
including
the
locale,
but
also
including
different,
like
which
components
of
the
date
you
care
about,
and
it
gives
you
a
string
which
is
locale
dependent.
So
there's
there's
a
bunch
of
ongoing
ongoing
feature,
work
to
add
more
functionality
to
this
like
there's
one
PR
that
would
add
sort
of
Chinese
calendar
functionality,
certain
kinds
of
like
informal,
related
lunar
calendar.
H
H
H
That's
the
hope.
The
web
compat
issue
is
is
for
the
older
features,
they're
very
broadly
supported
and
I.
Think
you
can.
You
can
count
on
the
basics
of
date-time
format,
number
format
and
collator
being
there,
and
then
the
other
ones
are
more
mixed
and
so
I'm
wondering
like
do
you
face
these
needs
in
node
and
what
what
functionality
might
be
useful
for
you
yeah
one.
D
Also,
just
to
say,
one
thing
about
the
compatibility
on
browsers
is
that
really
Firefox
and
Chrome
and
Safari
are
like
up-to-date
and
have
been
really
implementing
Intel,
as
we've
been
developing
it
and
Ekrem
afford
to.
But
Microsoft
is
far
behind
but,
as
we
know,
they're
they're
also
switching
out
their
JavaScript
engine
to
the
eight
so
going
forward
like
soon
enough,
we'll
have
Intel
and
all
the
and
all
the
browsers.
Well.
H
A
J
H
A
A
A
H
B
H
Until
display
names
is
like
a
way
for
you
to
get
certain
big
things
like
the
names
of
all
the
countries
in
the
world
in
all
the
different
languages,
which
is
useful.
If
you
build
a
like
a
region,
picker
well
yeah,
they
you,
you
might
have
heard
like.
Oh
the
Unicode
people
want
you
to
say
words
like
code
white.
It
turns
out
there's
all
sorts
of
different
words
that
in
a
nationalization
world,
you're
supposed
to
use
like
region,
rappin
I
wasn't.
H
H
Yeah,
it
also
includes,
like
names
includes
name,
is
for
a
bunch
of
these
different
things,
and
so
that
should
help
well
on
the
way.
But
you
help
reduce
the
binary
size
that
has
to
be
shipped
over
on
the
server
I
think
it
has
the
same
function,
but
it
doesn't
reduce
the
size
of
things
to
get
shipped
over,
but
it
reduces
the
amount
of
stuff
that
you
have
to
did.
C
This
happened,
thing
is
they're
they're,
always
they're.
Always
things
like
this.
You
know,
Swaziland
is
now
Isla,
teeny
and
and
such
and
but
even
besides,
changes
just
the
the
the
load
in
in
translation.
You
know,
there's
there's
a
lot
of
translated
content.
You
know
my
I
work
with
our
internal
translation
across
the
seas
and
tools
and
a
lot
of
times
people
will
have
submit
for
translation.
A
E
A
C
C
H
Think
so
I
think
this
is
something
that
we've
been
looking
into
in
this
group
in
it,
for
both
today
I
come
up
four
or
two
things:
there's
data,
that's
already
in
the
browser
stuff,
like
units
use
not
in
Chrome,
but
that
it's
there
in
iOS.
So
then
it's
kind
of
okay
or
moderately
okay.
They
ended
up
reducing
the
list
of
units
that
are
supported.
So
then
the
increment
in
binary
size
was
less
and
that's
you
know
working
through
the
ization.
H
A
H
C
H
E
D
G
H
B
G
H
E
H
F
I
C
I
C
F
E
C
E
A
wrap-up
because
it's
a
three
past
the
hour
but
I
definitely
have
some
action
items
here
that
I'd
like
to
take
for
kind
of
I,
think
it's
more
about
making
the
contribution
process
for
proposals
and
how
to
get
involved
less
abstract
to
people
who
may
want
to
contribute
for
the
first
time.
That
sort
of
thing
that's
really
important,
and
we
can
do
that
through
internationalisation,
but
just
having
this
conversation
has
been
really
really
good
to
get
visibility
into
it
and
I'm
definitely
learning
a
lot
too.