►
From YouTube: Node.js Internationalization (i18n) Working Group
Description
A
B
A
Good
turnout
and
hey,
oh
gosh,
it
cut
some
of
my
awkward
things
that
I
thought
weren't
gonna
be
like
okay.
Here
we
go
so
welcome
to
the
first,
no
js'
internationalization
working
group
meeting
of
the
year
super
excited
to
have
everybody
here
and
excited
to
talk
through
some
really
relevant
issues
and
pick
up
steam.
Everybody
who's
here
has
done
so
much
in
the
last
couple
years,
since
we
even
started
talking
about
this
and
I.
Think
it's
a
really
amazing
opportunity
to
get
the
ball
rolling
and
see
how
we
can
support
both
internationalization.
A
A
Let
me
grab
our
agenda,
so
I'm
gonna
go
over
to
the
agenda.
If,
if
there's
nobody
here,
who
would
win
mine
taking
notes
that
would
be
awesome
since
there's
only
four
of
us
I
know,
taking
notes
is
hard
and
participating
at
the
same
time
to
do
both.
So
you
know
no
pressure
to
take
extremely
thorough
notes
if
you
want
to
participate,
but
can
anybody
take
notes
while
we
go
through
this
I
can.
C
A
If,
as
we're
going
through
this,
it
would
be
extremely
helpful,
I
put
in
action
items
section
above
the
minutes
if
we
could
bubble
up
action
items
just
you
know,
ad
hoc.
That
would
be
super
awesome
if
possible,
no
pressure,
but
you
know,
if
we
don't,
then
you
know
I'll,
probably
traverse
through
the
minutes
and
myself
in
post.
So,
okay,
let's
get
started
and.
A
B
A
Essentially,
this
is
still
in
an
initiative
of
calm.
Calm
internationalization
is
one
of
like
ten
as
far
as
like
governance
is
concerned,
so
we're
still
under
that
purview
within
with
an
odious
know.
It's
interesting
you
know
about.
This
is
right
now
we're
talking
both
about
you
know
more
community
outreach,
oriented
stuff
and
translating
text
you
know
for
people
to
read
as
well
as
what's
going
on
in
the
actual
and
in
the
core
with
int
L,
and
so
that's
really
interesting.
A
Let's
get
into
that
and
in
the
issue
down
below
that,
so
they'll
be
interested
conversation,
but
right
now
we're
essentially
just
kind
of
where
we
left
off
last
time
and
a
you
know:
full
full
support
from
calm,
calm
to
push
board
so
I
see
internationalisation
repository,
it's
still,
I
mean
not
much
has
happened
as
far
as
code
is
concerned
in
the
last
like
a
year
or
so,
and
so
I
think
it's
basically
at
that
it.
You
know,
after
that
initial
you
know
opening
the
floodgates
moment
with
not
a
lot
of
maintenance
afterward.
A
So
you
know,
like
we
kind
of
opened
the
floodgates
we
set
up.
We
set
up
all
the
configuration
between
crowding
in
the
repository,
so
in
fact
translations
can
come
in.
We
just
don't
have
active
maintenance
of
people
who
are
fielding.
All
of
the
I
mean
there
are
my
I
mean
my
god
there's
so
many
requests
for
joining
and
translation
help
and
crowd
in,
and
you
know
part
of
this
a
lot.
You
know
I
I,
take
the
blame
for
a
lot
of
you
know
not
not.
A
Continually
refreshing
the
support
pool
for
this,
but,
like
you
know,
there's
no
time
like
the
present
tip
to
push
on
and
do
that
so
anyways.
There
is
a
a
lot
of
interest
in
that
in
the
crowd
and
repository
people,
translators,
reaching
out
to
get
involved,
and
so
I
think
you
know.
One
aspect
of
this
is
to
set
clear
maintenance.
You
know
are
clear
contribution,
guidelines
and
I'll
get
you
know
we
have
that
on
the
agenda
as
well,
but
there's
there's
a
lot
that
can
be
done
there.
So
international
internationalization
repository
is
essentially
like
we're.
A
You
know
it's
it's
a
it's
ready
to
get
the
the
targets
fleshed
out
as
far
as
how
we
want
to
set
that
up
and
enhance
that,
and
we
started
to
do
some
of
that,
but
we
need
maintain,
errs
and
then
yeah
Crowden
I
mean
as
far
as
crowded
as
concerned
as
an
isolated
thing.
It
looks
great
I
mean
you
know:
I,
it's
I
mean
Spanish.
Is
that
like
a
really
high
percentage
of
translation?
A
Let
me
let
me
like
it's
like
Spanish
was
at
there's
something
like
in
there's
like
90
percentile
or
something?
Oh,
no,
not
I
need
76,
so
like
70
percent
76
after
like
not
do
it
not
having
really
any
maintainer
's.
You
know
like
having
some
translation
percent.
Translation
is
like
kind
of
cool
for
like
API,
Doc's
and
stuff
we
need
to.
A
C
A
B
Having
a
meeting
we'll
get
this
we'll
get
something
done
well,
one
thing
that
might
be
good
is
to
is,
to
you
know,
get
the
the
metrics
I
mean,
maybe
I
wonder
if
even
you
know,
if
there's
a
badge
or
something
I
mean
I'm,
not
trying
to
add
you
know,
I
could
easily
add
more
work
rather
than
less
work.
But
you
know
if
there
was
like
a
badge
or
something
we
could
put.
B
A
B
C
Of
the
things
in
my
people,
which
I've
seen
on
other
websites
like
open
collective
as
this
is
to
have
a
list
of
percentages
somewhere
on
the
website
itself,
so
that
you
can
actually
see
like
on
node.js
comm
what
the
percentage
is
of
translations.
That's
actually
a
really
good
way
to
getting
people
on
board,
because
I
can
see
that
actually,
oh
so
Spanish
that
76%
I
can
help
with
that.
C
A
C
It's
super
awesome,
like
you,
can
see
right
there,
Portuguese
and
France
are
at
100%
I
thought
that
might
be
something
that
we're
really
cool
because
having
a
dashboard
is
great
for
us
as
a
maintainer,
but
as
a
way
of
like
rallying
support,
maybe
good
to
have
really
clear
badges,
say
yo.
When
you
help
here,
yep.
A
B
B
So
but
there
was
there
are
the
language
specific
subgroups
and
are
those
yes
I
think
they're
still
around.
So
that
would
be
something
where
you
could
go
to.
You
know.
Nodejs.
Okay,
yes,
is
great,
but
you
know
kind
of
recruit
from
there
absolutely.
A
I
think
that's
a
it's
a
good
resource
to
go
back
and
and
see
what
interest
people
have
been
jumping
into
this
we
did
when
we
did
kick
us
off.
We
we
did
run
I
ran
through
all
those
steps
of
contacting
each
localization
working
group
and
saying
this
is
the
way
things
are
shifting
and
there,
as
far
as
like
you
know,
great
mister
boson.
That
kind
of
so
people
are
aware,
or
have
been
aware
for
some
time
that
it's
shifted
into.
You
know
a
different
pattern
for
internationalization,
but
we
need
to
yeah.
A
A
Yeah,
no,
no
and
and
I
think
I.
Think
that
thing
to
take
from
that
right
now
as
we're
rolling
through
this.
The
broad
agenda
here
is
that
we
need
we
need
input
and
we
need
maintainer
to
help
with
that.
It's
been
stagnant
for
a
while,
and
it's
basically
like
who
can
help
to
help
set
that
up
as
we
identify
targets
and
I
think
that's
kind
of
where
we're
at
so
I
know.
Zeke
has
put
in
a
lot
of
work
in
the
past
on
that
and
a
few
other
people
and
Nick.
D
D
A
D
D
A
I
think
Zeke
handled
a
bit
of
that
before
okay
in
the
past,
so
he
would
be
a
good
person
to
reach
out
to
about,
but
I'm,
also
interested
in
that
I
just
haven't
looked
into
it.
So,
let's
just
keep
in
touch
and
I
like
everything
about
to
listen
reach
out
to
the
localization
I'm
chatting
action
item
serialization.
A
Okay,
the
next
thing
on
the
agenda
is,
oh
sorry,
well
are
we
all
done
discussing
you
know
aspects
of
reviving
this
project.
Is
there
anything
else
that
anybody
would
like
to
talk
about
for
that
cool?
Okay,
the.
A
Thing
is
updating
our
guides.
I
just
put
in
this
issue
right
before
the
meeting.
I.
Think
part
of
the
reason
why
we
don't
have
much
involvement
is
because
we
essentially
have
like
you
know,
like
a
small
MVP,
getting
started
guide
and
like
know
contributing
guide,
so
it
would
just
have
like
I,
don't
know
we
we
have.
We
have
no
nothing
actually
describing
how
to
get
involved
in
the
project
in
the
community,
so
that
needs
to
change.
And
if
we
add,
let
me
look
at
that.
A
So
you
know
the
four
points
essentially
are
that
we
need
to
help
people
understand
or
how
to
get
involved
in
this
initiative.
You
know
like
what
we
do
and
then
how
to
work
on
the
internationalisation.
Repo
to
localize
content
like
Nick,
was
talking
about
how
to
join
crowd
in
and
localized
resources
as
a
translator
and
point
people
to
crowd
and
who
want
to
just
translate,
and
then
you
know
how
to
get
involved
in
contributing
to
incl
and
ojs
and
how
to
gather
volunteers
to
help
out
with
this.
A
B
D
C
B
A
A
B
A
B
B
A
A
B
One
might
be,
it
might
be
good
even
to
get
we
could
even
get
the
an
initial
PR.
Even
if
it's
a
more
more
modest
change,
just
kind
of
get
getting
these
points
out
on
the
table
and
send
the
PR
around
and
say
you
know,
hey
we're
trying
to
help
people
on
board
to
this,
and
you
know
a
specialist
that
you
send
it
to
calm.
Calm,
send
it
to
some
of
the
language
groups,
I.
A
C
A
A
A
A
B
C
A
On
alright,
so
this
is
a
big
one.
I
think
we
need
to
think
through
and
we're
gonna
need
a
lot
of
your
ear
guidance
and
help
here,
Steven,
so
I,
there's
gonna,
be.
Let
me
let
me
like
back
up
and
say
from
what
I've
noticed
like
internationalization
is
sort
of
like
a
niche
thing
inside
the
you
know
the
ecosystem
of
nodejs.
Now
you
know
that
because
you're
like
one
of
the
only
people
who
works
on
impl-
and
there
are
people
who
care
about
internationalization
of
documentation,
there
are.
A
About
internationalization
of
runtime,
you
know
I'm,
like
those
are
both
extremely
valuable
things
in
the
ecosystem
and
are
two
different.
You
know
can
become
be
two
different
dis
plans
as
far
as
like
what
you
are
doing
and
get
involved
in
and
I
want
to
figure
out
like
what
the
best
role
is.
You
know
what
the
best
way
is
to
or
I
guess
what
the
best
foot
forward
is.
A
You
know
how
do
you
feel
about
int,
l
and
being
a
part
of
like
one
internationalization
thing
that
has
like
you
know,
kind
of
two
directives
in
it
or
you
know
like
what?
How
how
should
we
move
forward
with
this,
like
what
I
mix
I
mean
I,
I,
just
love
being
hanging
out
and
talking
about
these
things
and
getting
involved
and
I
want
to
help
out
with
int
L
more
because
I
love
it.
B
B
I
mean
I
think
there
are
two
things
and
in
fact
you
know
I
I've
I've
spent
a
lot
of
time
only
doing
globalization
and
not
translation
and,
interestingly
enough,
you
know
kind
of
my
my
main
day.
Job
work
is,
is
actually
more
translation
and
a
smaller
part
of
the
globalization,
but
so
so
I
kind
of
see
both
pieces
to
it.
I
think
one
of
the
things
that's
part
of
it
is,
as
you
said,
it
can
be
hard
to
get
people
engaged
and
get.
B
You
know
to
find
the
right
people
that
can
answer
the
questions
and
all
that
so
I
think
you
know,
having
kind
of
more
collectiveness
of
back
like
a
better
word,
then,
rather
than
less
is
probably
a
good
thing.
I
also
think
one
of
the
things
that's
that's
great
about
node,
you
know
I've
I've
done
like
the
IC
project
has
been
open
source
since
1999
or
something
like
that.
But
you
know
one
of
the
things
I
think
is
great
about
nodejs
and
is
that
as
a
community
there's
all
cuz
it's
from
people
working
on
stuff?
B
So
it's
not
just
you
know
someone
sitting
in
a
corner.
You
know
hacking
out
optimized,
you
know
some
optimized
parser
for
something
it's
it's.
You
know
people
doing
all
kinds
of
stuff,
including
Communications
and
translation.
Oh
yes,
anyway,
all
that
long
story
short
is
I.
Think
that,
as
as
a
group
I
think
I
teen
n
group
can
should
really
cover
both,
because
a
lot
of
things
are
really
related
and
one
of
the
things
I
see
in
translation
is
that
a
lot
of
times
difficulties
with
translation
can
go
back
to
architectural
decisions.
B
You
know
just
kind
of
a
basic
one,
I
look
at
is
you
know
every
website
that
has
a
every
website
that
wants
to
have
multiple
languages
has
a
list
of
languages
and
it's
often
translated.
So
you
know
one
of
the
things
that
gets
translated.
A
lot
is
okay.
Translate
English
in
English
translate
French
into
French.
You
know
all
this
translation
stuff.
Well,
the
thing
is:
there's
there's
already
a
project
cldr
that
does
that
and
has
all
those
translations.
So
if
you
leverage
the
right
architecture,
you
can
improve
your.
B
You
know:
try
your
translate
ability
a
lot
so
anyway,
so
I
think
that's
that's
just
that's
kind
of
why
those
are
related.
The
other
thing
is
that
when
you
find
people
that
are
interested
in
some
language,
let's
say
Spanish
they
they
also
will
have
the
knowledge
needed
to
deal
with
the
you
know
the
globalization
question,
so
you
get
in
contact
with
the
right
people
that
know
about
that.
If
you
have
those
completely
separate,
you
know
if
some
people
doing
translating
over
here,
as
if
that's
kind
of
I,
don't
know
non
programming,
it's
non
development.
B
You
know
that's
just
text,
but
you
know
that's,
that's
writing
stuff.
You
know,
and
then
you
have
people
over
here
that
are
doing
code.
If
you
keep
those
separate,
then
you
don't
get
the
you
don't
get
the
you
don't
get.
The
pain
points
come
back
from
the
language
community.
Where
someone
says
well
I'm,
you
know
I'm
writing
this
code.
I'm
yeah,
I'm,
I'm,
a
coder,
I
use
this
language
and
my
language
has
never
really
been
well
supported,
I,
just
kind
of
live
with
that
because
that's
it's
been
that
way.
My
whole
life.
B
You
know
people
people
will
get
used
to
lack
of
support.
You
know
I'm
used
to
not
finding
my
language
written
on
the
system,
because
it's
I
don't
know
it's
it's
historian,
or
something
and
and
I
just
don't
see
it
as
one
of
the
major
languages.
So
people
don't
push
for
stuff,
but
if
we
can
keep
those
communities
together,
then
if
we
keep
global
the
globalization
side,
like
the
89
code,
the
the
int
l
coding
stuff
with
people
doing
translation
that
we
can,
we
can
bring
out
some
of
those
I
call
pain,
points
and
called
opportunity.
B
A
B
B
But,
but
there
was
a
you
know:
there's
a
feature
in
in
Celia
on
ICU
for
several
years
list
format
and
it
finally
is
being
proposed
to
go
into
Ekman
script
and
VA
came
with
the
early
proposal,
somebody
tweeted
in
Spanish,
hey.
This,
doesn't
work
in
Spanish
and
a
bunch
of
people
kind
of
collectively
scratched
her
heads
over
the
past
several
months
and
said:
you're
right.
It
doesn't
work
in
Spanish,
but
it
wasn't
that
wasn't
noted
until
somebody
you
know
on
Twitter
saw
that
v8
had
this
new
feature
tried
it
out
in
their
language.
B
Spanish,
not
not
a
super
obscure
language.
I'm
I
do
a
lot
with
Spanish
myself
so,
and
they
said
this
doesn't
work,
so
that's
completely
brought
a
new
requirement
from
a
technical
side
from
from
the
user
community
via
v8.
So
anyway,
that's
the
kind
of
interaction
that
would
be
great
to
get.
You
know
what
are
the
things
you
run
into?
What
would
it
what
are
the
things
where
you
see
your
language
as
what,
where
your
language
can
seem
like
a
second-class
citizen?
How
can
we
fix
that?
A
Awesome,
you
know
what
that
makes
me
think
of
is
kind
of
operationally
or
you
know,
being
pragmatic
moving
forward.
If
we
do,
you
know,
as
we
do
internationalization
working
group
meetings
here,
mm-hmm,
it
might
be
good
to
you
know
section
over
to
partition
like
two
parts
of
the
of
the
time
to
talk
more
about,
like
you
know
the
translation
process
and
then
yep.
A
You
know
the
globalization
process,
and
so
it
might
be
interesting
to
like
to
kind
of
feel
that
out
over
time
and
how
much
time,
because
you
know
how
much
time
we
can
spend
right.
You
know
like
getting
the
trans
in
the
translation
process,
supporting
the
globalization
and
the
globalization's
for
the
translation.
You
know
other
concepts,
yep
yep
sounds
good.
That's
great!
Thank
you.
Thank
you
for
that
summary,
and
it
really
helps
you
know.
We
I
don't
know
if,
like
in
that
issue,
that
I
shared
someone
chimed
in
they're
like
wait.
What
why
is
there?
A
A
A
C
A
B
C
A
A
C
A
B
One
thing
is
I
think
you
know
I
think
in
sense.
Sam
Sam's
have
been
part
of
been
part
of
some
of
this
for
a
while,
but
I.
You
know
I'm
rereading
this.
Now
today
this
kind
of
looks
like
he.
You
know
there
may
be
a
point
here.
Maybe
maybe
we
just
need
to
be
consistent
with
our
naming.
You
pick
one
and
and
sorta
I
mean
our
ITN.
Is
our
repository
going
forward,
and
maybe
what
we
need
to
do
is
clean
up
the
labels
and.
A
B
Maybe
we
want
like
an
IT
nen
translation,
i18n
api.
I
don't
know
something
like
that.
You
know
some
kind
of
team,
labor
I,
think
you
know
if
sub
teams
even
to
just
sort
things
out,
because
actually
I
I
think
I'm
rereading
this
I,
don't
think
that
it's
necessarily
I,
don't
think
Sam
is
mixed
up
about
the
I.
B
A
B
C
B
A
B
A
A
D
A
Yeah
I
think
essentially
yeah,
like
you,
said
2906,
and
we
just
I
mean
it's
essentially
just
waiting
for
progress
and
unblocking
people
with
like
that
are
the
crowd
in
bond
and
credentials
and
stuff
so
I
mean.
Is
there
anything
really
besides
that
that
we
need
to
talk
about
in
this,
so
that
you'd
like
to
discuss.
D
A
Absolutely
so
I
think
the
yeah
the
what
we're
getting
into
I
can't
I,
don't
have
that
issue.
Handy
I
think
it
was
linked
somewhere
through
this,
like
Miles
chimed
in
talking
about
CMS
and
stuff,
and
people
wanting
to
have
access
to
be
able
to
update,
update
websites
and
whatnot,
if
even
if
they're
you
know
like,
if
they
I
can't
write
code
or
whatever
for
it.
So
it's
gonna
be
an
interesting
problem
that
we're
going
to
have
to
tackle
as
far
as
how
to
configure
internet.
A
You
know
configure
that
pipeline
and
like
kind
of
advocate
for
making
it
work,
for
you
know
and
I
guess
best
practices.
Zeke
like
has
a
lot
of
experience
with
doing
this,
for
electron
and
for
github
and
I
would
love
to
get
a
conversation
with
another
conversation
soon
with
the
website,
redesign
team,
who's
responsible
for
no
js',
no
dev
or
whatever,
and
and
and
you
Nick
and
and
figure
out
how
to
do.
A
You
know
like
what
the
primary
goal
is
and
how
to
you
know
like
what
do
we
need
to
do
since
it
is
gatsby
driven
and
that
sort
of
thing?
How
can
we
make
parity?
You
know
like
how
can
we
make
that
work
so
I
think
that's
kind
of
next
steps
is
to
have
a
more
in-depth
working
group
conversation
cross
working
your
conversation
with
website
redesign
team
because
it
doesn't
really
Harry
when
you
have.
You
know
like
CMS
stuff,
and
you
know
like
frameworks
and
whatnot.
A
You
can't
just
like
you
know,
I
don't
know,
but
especially
with
CMS.
It's
hard.
You
know
like
the
original.
The
original
thing
we
were
you
know
doing
was
creating
this
NPM
module.
You
know
that
you
can
import
them,
sort
of
lazy
load,
your
JSON,
you
know
just
on
if
I'd
mark
down
from
translations
or
whatnot
and
then
import
them
into
the
right
place.
You
know
like
per
page
or
whatnot
and
I.
A
Just
we
just
have
to
see
like
how
far
down
the
road
we
can
go
with
that
you
know,
as
in
how
it's
going
to
work
like
with
GATS
being
with
other
configurations
but
yeah,
let's,
let's
definitely
I,
think.
The
action
item
here
is
to
set
up
a
working
group
meeting
as
soon
as
possible
with
the
website
redesign
team.
A
So
any
any
more
thoughts
on
that
before
we
live
long,
no,
okay!
Well!
The
next
agenda
item
is
number
four
working
you're
admitting
time
in
frequencies.
Some
housekeeping
I
am
planning
on,
as,
like,
probably
for
the
next
three
three
months.
I'll
probably
have
to
reassess
so,
like
you
know,
currently
I'm
unemployed,
so
I'm
looking
for
a
job
right
now,
but
my
time
is
relatively
open
for
the
neck.
I
usually
takes
about
three
months
to
learn
your
next
thing,
so
I'm
within
that
time
period,
I'm
planning
on
being
here
at
this
time
every
week.
A
So
if,
if
that
works
for
y'all,
that's
great
as
far
as
having
like
you
know
in
a
core
team,
you
know
doing
this
for
a
while,
we
can
reassess
this.
We
need
to
I'd
like
to
meet
weekly
for
now,
so
that
we
can,
you
know
just
like
make
good
progress,
doesn't
have
to
be
an
hour.
It
could,
if
it's
weekly
or
we
could
do
a
bimonthly
at
you,
know
an
hour
or
whatever.
But
what
do
y'all
think
about
timing
and
frequency
and
what
works
I.
B
A
A
B
A
So
next
one
is
published:
module
to
NPM
I
I
feel
like.
We
don't
really
need
to
go
in
depth
about
that
right
now,
because
it
would
be
better
to
have
people
who've
worked
on
it
before
here
with
us,
so
I'm
gonna
punt,
that
until
we
can
get
Zeke
and
other
folks,
input
will
be
highly
valuable
to
that
discussion
and
then,
unless
the
nobody
had
something
burning,
burning
questions
about
it.
B
A
He
posted
yeah.
He
posted
like
his
findings
from
yeah
from
those
groups,
so
I
think
that
was
the
most
exhaustive
list
of
source
of
truth
that
we
had
for
that
and
then
I
also
in
tandem
posted
an
issue
on
each
in
every
localization
group.
Just
saying
you
know
like
this
is
what
we've
been
doing.
Is
you
know?
What's
your
interest
in
it
all
that
kind
of
stuff?
So,
and
there
was
you
know,
some
people
responded
or
some
groups
responded
some
some
didn't.
A
B
Yeah
I
think
we
could
close
it.
We
probably
want
to
make
sure
we
have
a.
We
have
a-
and
maybe
this
is
separate,
but
we
we
should
make
sure
that
we
have
a
you
if
there's
any
I
know
they're
they're,
all
kind
they're,
all
somewhat
independent
in
some
sense,
but
it
would
be
good
to
have
some
kind
of
general
coordination.
B
I
I
talked
to
the
collaborator
summit
years
back
about
trying
to
do
some
kind
of
you
know
worldwide
call
with
everyone,
but
that
that's
was
too
difficult
logistically,
but
it
would
be
good
to
have
some
way.
I
know,
yeah.
Thanks
for
doing
the
late
work
on,
you
know
sending
something
out
to
each.
Each
group
and
I
found
a
lot
of
those
yeah
this
link
there,
but
it
would
be
good
to
figure
out
some
way
to
to.
You
know,
have
some
sort
of
central
way
to
at
least
contact
everyone
or
yeah.
A
A
B
And
and
maybe
there's
some
way
to
do
at
least
a
I
mean-
maybe
maybe
a
meeting
is
not
not
practical,
but
maybe
there's
a
way
to
do
a
you
know
like
a
poll
or
an
open
document
or
something
to
to
kind
of
take
the
pulse
of
everyone
and
and
and
have
it
be
regular
thing.
So
anyway,
I
have
some
old
issues
from
the
old
group
that
started
trying
to
do
that
anyway,
I'll
file,
it
I'll
file,
probably
two
issues
perfect.
B
A
D
D
A
B
B
Being
a
contributor
I
mean
there's
a
there's,
a
defined
process
for
being
a
contributor
right,
and
so
maybe
that
would
be.
Maybe
that
would
be
a
good
kind
of
point
of
contact
for,
for
the,
for
the
groups
is
to
say
hey.
This
is
a
call
for
contributors
and
maybe
maybe
I
mean.
Probably
there
are
some
members
of
the
groups
that
are
already
contributors
and
say:
ok,
we
need
some
people
to
be
to
be.
B
B
B
D
B
A
No,
an
accident,
yeah
I
mean
I
think
like
yeah,
that's
the
like.
With
the
policies
right
like
Stephen
was
mentioning.
You
know,
I
think
it's
gonna
take
a
minute
to
sort
out
what
that
might
look
like
and
how
that
might
be
feasible
for
making
you
know
for
adding
contributors.
I,
don't
know
if
there's
like
specific
policies
around
at
the
moment
around
making
contributors
for
like
specific
repos
in
that
way,
yeah
it
would
just
yeah
I,
don't
know.
Maybe
we
just
have
said
yeah.
D
A
A
A
A
A
A
A
C
B
D
A
B
A
A
A
A
A
A
A
D
A
A
A
D
A
B
A
B
A
B
A
B
A
A
B
In
fact,
I
was
gonna
gonna
mention
about
that.
You
know
I'm
discussing
a
couple
features
and
I
keep
hearing.
Well,
we
want
the
web
to
work
this
way
and
the
web
to
work
this
way
and
it's
like
well.
Okay,
my
scope
is
not
just
the
web,
but
anyway
anyway,
yeah
but
yeah
that'd
be
great.
I
would
I
would
love
to
get
there's
a
lot
of
stuff
happening
there.
We
don't
need
to
go
through.
We
can't
go
through
here,
but
it
would
be
great
to
get
more
input.
I
love
to.