New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roadmap #18

Closed
mhdawson opened this Issue Nov 11, 2016 · 20 comments

Comments

Projects
None yet
9 participants
@mhdawson
Member

mhdawson commented Nov 11, 2016

Roadmap

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

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

This comment has been minimized.

Member

Fishrock123 commented Nov 21, 2016

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

@aruneshchandra

This comment has been minimized.

Member

aruneshchandra commented Dec 10, 2016

Updated the roadmap for better progress visibility and current status.

@MylesBorins

This comment has been minimized.

Member

MylesBorins commented Dec 14, 2016

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

This comment has been minimized.

Member

aruneshchandra commented Dec 18, 2016

@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

This comment has been minimized.

Member

RReverser commented Jun 5, 2017

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

This comment has been minimized.

Member

aruneshchandra commented Jun 5, 2017

@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

This comment has been minimized.

Member

RReverser commented Jun 5, 2017

@aruneshchandra

the link is not dead

Well it returns 404 to me :/
screen shot 2017-06-05 at 16 35 29

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

This comment has been minimized.

@RReverser

This comment has been minimized.

Member

RReverser commented Jun 5, 2017

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

@RReverser

This comment has been minimized.

Member

RReverser commented Jun 5, 2017

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

@aruneshchandra

This comment has been minimized.

Member

aruneshchandra commented Jun 5, 2017

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

This comment has been minimized.

Member

RReverser commented Jun 5, 2017

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 me@rreverser.com? Thanks!

@mhdawson

This comment has been minimized.

Member

mhdawson commented Jun 5, 2017

@sampsongao can you send @RReverser a direct invitation.

@RReverser

This comment has been minimized.

Member

RReverser commented Jun 7, 2017

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

@sampsongao

This comment has been minimized.

Collaborator

sampsongao commented Jun 7, 2017

@RReverser Invitation sent. Have you receive it?

@RReverser

This comment has been minimized.

Member

RReverser commented Jun 7, 2017

@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

This comment has been minimized.

Silur commented Jul 28, 2017

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

@addaleax

This comment has been minimized.

Member

addaleax commented Jul 28, 2017

@Silur actually, yes: nodejs/node#14532

@gabrielschulhof

This comment has been minimized.

Collaborator

gabrielschulhof commented Oct 1, 2018

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

@mhdawson

This comment has been minimized.

Member

mhdawson commented Oct 1, 2018

I think so, closing.

@mhdawson mhdawson closed this Oct 1, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment