►
From YouTube: Node.js N-API Team meeting - July 19 2018
Description
B
C
B
B
Probably
most
of
the
people
who
are
in
the
call
know
that
the
blog
post,
which
I
just
pasted
the
link
into
the
chat
that
blog
post,
went
out
yesterday,
I'm
closing
out
one
of
the
issues
talking
about
you
know
an
update
on
the
status
in
terms
of
availability
on
6,
8
and
10,
as
well
as
some
examples
of
modules,
they're
being
used
and
so
forth.
Does
anybody
else
have
any
other
announcements
before
we
get
started.
B
E
Alright
get
me
out
of
my
office
and
see
what
happens.
Ok,
so
the
most
current
news
is
I
got
a
tutorial
up
for
a
sink
worker
and
Gabriel
I
really
appreciate
your
feedback.
I
will
I
will
incorporate
those
changes
into
that
tutorial
before
Monday
I'm
continuing
to
work
on
an
ode,
pre
jib
tutorial
I
cannot
commit
right
now
that
I'll
have
that
done
in
time,
but
if
I
do
I'll
post
it
here
also,
if,
if
I
do
it'll
be
tomorrow,
if
it's
not
there
tomorrow
that
it
won't
be
there
in
time
for
Monday
sure.
B
Well,
thank
thanks
for
all
the
efforts
in
putting
those
together
either
way-
that's
really
good
sure,
I
I've.
Unfortunately,
my
plan
is
this
afternoon
to
go
through
them
myself.
So
I
might
have
a
Lopez
feedback,
but
hopefully
I
suspect,
they're
gonna
be
they're,
gonna,
be
all
good,
so
okay,
I
will
have
time
tomorrow
to
incorporate
changes.
Excellent,
ok,
cuz,
yeah
I
was
planning
to
sort
of
just
run
through
them
myself.
Okay,
very
good,
Michael,
I
think
otherwise
we're
pretty
much
set
for
the
workshop
right.
I
guess.
One
thing
that
attached
was
mentioning
a
brownish.
B
A
F
B
A
B
I
think
they
zero
like
his
was
booked
like
weeks
ago,
so
he
probably
just
couldn't
register
for
that.
Even
if
he's
register
for
the
conference,
so
I
really
I
really
do
not
think
it's
an
issue
anyway,
like
even
if
you
just
showed
up,
but
it
just
doesn't
hurt
to
send
the
email
saying:
hey
we've
got.
Some
else
is
gonna
help
out
too
yeah.
Okay,
okay,
I
think
Kitaj
put
together
the
list
of
module
owners.
He
sent
it
out
to
them,
I
guess
there.
B
There
was
some
interaction
on
one
of
them,
but
I
haven't
heard
anything
like
people
saying:
no
don't
do
it.
So
that's
good
and
I
think
the
let
you
know
we
haven't
no,
no
updates
to
the
deck
I.
Don't
think
since
we
last
spoke,
but
I
don't
think
any
are
necessary
either
right,
right,
okay,
so
anything
else.
We
should
talk
about
on
on
this
front.
I.
E
E
B
A
E
B
G
B
Looks
like
a
test
joint
in
the
attendees
okay,
so
I
need
to
promote
them,
probably
hold
on
yep.
Do
that
before
we
participants?
How
do
I
get
the
right
view
to
see
him?
Oh
there
he
is
hold
on
these
promote.
Okay,
thanks,
if
no
problem,
so
basically
we
have
the
you
know
the
the
intro
we're
gonna
each
introduce
ourselves.
B
C
B
Slides
for
that
we
have
the
you
know,
welcome
to
every
thank
you
to
everybody,
who's
contributed
and
then
basically,
it's
you
know,
introduction
a
little
bit
of
short
introductions
to
the
nappy
note
on
API
going
through
the
tutorials
and
then,
if
people
get
through
those,
we
have
a
list
of
it's
more
than
24
modules,
that
people
can
start
to
port
mm-hmm
and
we'll
hand
that
out,
and
then
we
have
a
little
bit
of
a
wrap-up
and
assessment.
Sorry,
so
you
know
in
the
end
the
bottom
picture
shows
who's
talking
to
it.
B
B
This
is
Gabriel
is
going
to
talk
here
at
this
instance
about
you
know,
know
that
on
and
no
doubt
on
an
API
sort
of
what
the
difference
is
between
the
two
of
them
a
little
bit
about
node
versus
nan,
then
we're
gonna
get
into
the
tutorial.
So
I
don't
think
we
think
those
first
number
of
slides
are
going
to
take
huge
amount
of
time.
Most
of
it
will
be
then
people
going
through
each
of
these
tutorials
okay
and
then,
if
people
get
through
the
tutorials,
it's
like.
Okay,
we'll
have
the
list
of
modules
support
people.
B
D
B
B
Me
is,
we
should
have
20,
you
know
they.
Basically
an
earlier
emails
were
saying,
you
know,
can
you
handle
the
room,
holds
24,
but
it's
capped
at
15
or
something
so
we
said
fine
to
24.
So
that
tells
me
we
should
have
20
or
people
they're,
nice,
nice,
so
I'm
I'm,
hoping
that's
reflective
of
interest
in
it
as
well,
and
you
know
so.
The
other
talks
you
know
mine
in
the
afternoon
and
yours
in
the
Maine
State
should
also
be
well
attended
and.
B
To
one
as
they
work
through,
then
they
can
move
on
to
the
next
one.
Oh
yeah,
they
get
to
the
end.
We'll
have
this
list
of
modules.
We
can
say
here's
the
list
attached
just
put
some
work
in
to
classify
whether
they're
like
hard
or
easy
or
whatever
right-
and
you
know
so-
yeah
it's
after
after
the
short
intro,
it's
basically
self-directed
with
us
being
there
to
help
people
out
when
they
run
into
problems.
Okay,
yes,
that's
good.
A
D
C
D
B
B
B
Okay,
before
I
forget,
maybe
we
could
mention
one
of
the
maintainer
for
note
sauce
reached
out
to
us
and
Gabriel
I
met
with
him
yesterday.
Just
he
was
had
some
questions
about
an
API
talks
a
little
bit
about
what
they're
doing
you
know
he
mentioned
they
gonna
have
ten
million
downloads
and
you
know
they're
looking
at
an
API
for
sure,
possibly
the
you
know.
In
the
end
it
sounds
like.
Maybe
they
might
start
with
like
enabling
it
for
ten,
as
opposed
to
all
releases,
but
I
think
that's
a
really
good,
really
good
story.
There
too.
A
B
They
seemed
quite
active
now
because,
basically,
they
reached
out
on
Twitter
saying
you
know
we'd
like
to
talk
to
somebody.
We
had
like
an
hour
chat
with
them,
so
it
sounds
like
you
know,
they're
actively
working
on
it.
They
were
running
into
problems
by
the
time
we
talked
to
them.
They'd
work
through
those
problems
they
had
things
running
compiling.
B
He
had
some
questions
that
were
not
necessarily
related
to
an
API
that
we
sort
of
talked
through
in
terms
of
doing
things,
but
my
impression
and
Gabriel
can
add
to
it
as
well
was
that
you
know
they're
actively
working
on
it
and
figuring
out
which
release
is
gonna,
have
any
P
I
support
to
it?
Yeah
awesome.
They
also
mentioned
they're
quite
interesting
cuz.
They
got
a
ton
of
binaries
to
manage
so
yeah.
F
B
F
C
E
F
B
F
A
D
Yeah
and
when
I,
when
I,
recently
back
ported,
some
changes
from
from
master
I
actually
made
changes
in
the
back
board,
so
like
I,
didn't
just
cherry-pick
to
commit
I
actually
made
changes,
because
there
were
some
API
is
that
we
couldn't
use
in
in
for
and
and
I
actually
tested
it
against
for.
Even
though,
for
is
it's
like
out
of
our
scope?
Well,.
C
B
Really
I
think
that's
the
if
you
really
you
know
I
wouldn't
be
publicizing
for
too
much,
but
it's
good
to
have
that
in
the
back
pocket
that
well
like.
Currently,
it
still
probably
works.
Okay.
D
C
D
But
the
fact
that
we
are
I
think
and
I
mean
I.
Obviously
it
no
longer
benefits
from
the
from
from
the
wide
and
and
varied
testing
that
we
have
on
the
CI,
but
but
I
certainly
tested
it
locally,
would
note
for
and
it
works
so
I
mean
that
speaks
to
Linux
I
I.
Don't
have
that
kind
of
infrastructure
at
my
disposal
and
I
know
that
the
the
CI
short-circuits,
when
you
try
with
for
because
it's
not
supported
that
the
job
just
finish
it
successfully
immediately
without
running
anything
there.
D
B
B
On
that
front,
I
don't
know
if
I
mentioned
it
or
not,
but
there
is
a
job
in
the
CI
now
which
tests
every
LTS
like
six,
eight
and
ten
every
night.
So
we
did
have
a
breakage
on
six
a
little
while
we
never
shipped
a
release
with
it,
but
that
will
catch
that
earlier.
At
this
point,
just
soso
Nicola,
that's
one
thing:
you
probably
want
to
run
that
as
part
of
the
testing.
It
makes
one
of
the
steps
a
little
bit
easier.
B
C
B
B
B
No
okay,
so
the
next
issue
is
this
document
guidance
on
having
api's
to
any
pie.
I
saw
attach
opened
the
P
R
yesterday,
I
think
yep
and
so
far
I
think
only
really
positive
inputs.
I
did
I,
did
I
tagged
it
for
TSU,
review
and
sort
of
say
at
TSE.
It
needs
input
because
it
does
add
some
sort
of
policy
changes
in
terms
of
who
needs
to
sign
off,
but
hopefully
that
will
go
through
I,
don't
know
anything,
nothing
else
to
talk
about
on
that.
One.
B
D
No
I
just
didn't
it
just
an
idea
that
that
popped
into
my
mind.
This
is
this,
is
informal
and
but
usually
usually
when,
when
a
PR
comes
in
no
matter,
the
subsystem
people
who
are
familiar
with
the
subsystem
tend
to
end
up
being
the
approvers.
So
we
already
kind
of
de
facto
have
what?
What
that
right?
D
B
B
It's
going
to
be
a
foreign
idea
here,
right,
there's
even
another
discussion
where
you
know
a
crypto
API
went
in,
and
people
wish
it
had
more
review,
so
I'm
going
to
be
opening
something
that
proposes
the
security
working
group
gets
signed
and
sign
off
on
some
of
those
things.
So
I
I'm,
fairly
optimistic
on
that
front
makes
sense
so
SQLite
adding
resolving
that
I
couldn't
make
it
today.
I
actually
asked
her
to
focus
more
on
the
documentation.
B
First
cuz
we
wanted
that
for
the
summit
next
week.
So
that's
what
she
worked
on
this
week
get
in
the
reference
and
property
descriptors.
So
we'll
talk
about
that
later
on.
So,
but
there's
no
progress
on
this
particular
one
investigate
use
of
pre,
build
as
NEP
I,
don't
know
if
Jimmy.
If
you
probably
know.
E
This
or
yeah
you
have
been
giving
priority
to
issue
the
issue
backlog
on
node
pre
chip
and
getting
ready
for
node
summit.
But
here
this
is
actually
two
separate
modules.
What
one
for
building
and
publishing
and
then
a
separate
one
for
installing
so
I
do
have
the
the
build
and
publish
module,
creating
an
API,
builds
and
uploading
them
successfully
and
now
I'll
turn
my
attention
to
the
install
side
and
I'll
do
that.
After
note
summit
sounds.
B
B
B
A
C
B
C
D
D
C
B
Okay,
any
other
comments,
or
things
like
that
I
know
just
just
knees.
Okay,
so
that's
good,
but
yeah
I
think
will
be.
You
know
will
be
in
good
good
enough
shape
to
say
to
the
you
know:
people
there
we're
still
refining
the
documentation,
because
I
think
we
still
will
be.
Even
if
we
finish
this
off.
You
know
people
using
it
for
the
first
time
will
give
us
comments
and
stuff,
but
we're
pretty
close
to
having
a
you
know,
good
coverage,
which
is
good
okay,
so
that
was
what's
on
our
list.