Roadmap

[mhdawson]

Roadmap

✅ Milestone 1 - Initial API Implementation (DONE except landing EP)

• Initial concept defined in EP
• Initial API
• All NaN examples running
• Implementation of initial modules (leveldown and nanomsg)

✅ Milestone 2 - Ports across versions and runtimes

• Ports to ChakraCore (7.x)
• Ports across versions (0.10.x, 0.12.x, 6.2.x, 7.x)
• Performance Eval of initial implementation

✅ Milestone 3 - Demo for Node Interactive

✅ Milestone 4 - Full error handling

• Land EP as a draft after CTC Review
• Addition of full error handling
• Broad analysis of V8 API usage in top 30 most downloaded native modules
• Investigate canvas
• Evaluate Performance

✅ Milestone 5 - API feature complete (VM summit Readiness)

• Full API checked in to abi-stable-node and up to date with current Node.js master
• Update ports to head of v6, v8, ChakraCore-master
• Enable build flag for experimental support for NAPI
• Complete porting IoTivity
• Convert most depended on native module node-sass
• Convert native module from CITGM List canvas
• Community review checkpoint and update EPS
• Demo

✅ Milestone 6 - Land in master as Experimental - Targeting Node version 8.0

• Submit PR to Node master
• Land N-API in Node 8.0

Milestone 7 - Community Outreach

• Documentation for migrating existing Native modules to NAPI
• Automation for Migration assistance
• Blog: call to action for community / early adopters

[Fishrock123]

@mhdawson could you convert this to a checklist for better visibility of the status?

[aruneshchandra]

Updated the roadmap for better progress visibility and current status.

[MylesBorins]

Are we on target for this to land in 8 as mentioned in milestone 5?

edit: can we expand on what "experimental" means in the roadmap

[aruneshchandra]

@thealphanerd - IIRC from VM Summit 2, experimental means this will be available behind a config flag for version 8 and previous 1 or 2 LTSes.

As per being on target - its unclear at the moment, how much can be achieved by the time we cut a build for version 8. But Milestone 5 is what we are shooting for with the number of people who are working on it today. By VM Summit 3 (March 2017) we will have a better idea.

[RReverser]

Sorry for commenting on a probably inappropriate issue, but the Hangout link in the README seems dead. Are you still doing meetings? I'm trying to implement N-API on a somewhat unusual target and got quite a few questions/suggestions that would love to discuss. cc @nodejs/n-api

[aruneshchandra]

@RReverser - the link is not dead. The meetings are on Thursdays 10.30 Pacific / 1:30 Eastern US time. We would love to hear about your project and your feedback. Please join us this Thursday on June 8th.

[RReverser]

@aruneshchandra

the link is not dead

Well it returns 404 to me :/

The meetings are on Thursdays 10.30 Pacific / 1:30 Eastern US time. We would love to hear about your project and your feedback. Please join us this Thursday on June 8th.

Thanks!

[aruneshchandra]

How about this URL ?
https://plus.google.com/events/c0eevtrlajniu7h8cjrdk0f56c8?authkey=COH04YCalJS8Ug

[RReverser]

Same. Perhaps one needs to be invited to be able to access it?

[RReverser]

Ha, it opens when I open in incognito mode. So certainly something to do with permissions. Let me try from another Google account.

[aruneshchandra]

I don't think this is an invite only link - coz we had someone join without invitation last week. @sampsongao - can you please check ?

[RReverser]

Apparently, it has something to do with Google Apps (I have Google account on custom domain) + Google Plus Events links. https://www.reddit.com/r/google/comments/5b11gw/google_events_gone_for_good/

Direct hangout link should work. Could someone please send me an invite for hangout itself to [email protected]? Thanks!

[mhdawson]

@sampsongao can you send @RReverser a direct invitation.

[RReverser]

@sampsongao Friendly ping (and sorry for the hassle).

[sampsongao]

@RReverser Invitation sent. Have you receive it?

[RReverser]

@sampsongao Received it, but it contains the same link to the event itself and not to hangout, so still 404. This becomes weirdly complicated...

Sorry for bothering again, but is there a way to extract https://hangouts.google.com/hangouts/_/{id} link from the event page? I wonder if that id is same as the event id and I will be able to just substitute or I should register a separate gmail.com address just to join...

Got direct link to a hangout, all good now, thanks!

[Silur]

any plans about when this will grow out the experimental status?
how can we help to accelerate it?

[addaleax]

@Silur actually, yes: nodejs/node#14532

[gabrielschulhof]

@nodejs/n-api can we close this issue?

[mhdawson]

I think so, closing.