Skip to content
This repository has been archived by the owner on Oct 7, 2020. It is now read-only.

VM Summit #3 #4

Closed
aruneshchandra opened this issue Jan 5, 2017 · 15 comments
Closed

VM Summit #3 #4

aruneshchandra opened this issue Jan 5, 2017 · 15 comments

Comments

@aruneshchandra
Copy link

aruneshchandra commented Jan 5, 2017

At VM Summit 2 during Node Interactive Austin, we decided to meet again (end of feb / early march 2017) to evaluate the progress of ABI stable prototypes namely NAPI and FFI and discuss including them in Node v8.0 as experimental.

This onsite meeting is being planned to be held at the Microsoft campus in Redmond, WA. People will be able to participate online as well.

Proposed Agenda:

  • NAPI Demo by @mhdawson
  • FFI Demo by @ofrobots
  • Evaluate above stable ABI solutions to be included as experimental in Node v8.0 and older LTS versions
  • Next steps (Documentation, support, bug fixes etc.)

Please respond to this poll to indicate your availability for VM Summit 3
http://doodle.com/poll/qk4krgicifty24kk

The poll is to figure out the exact date for this meeting and also the headcount for onsite attendance.

@mikeal
Copy link

mikeal commented Jan 5, 2017

Is there a date associated with this?

In the future we may want to try and line these up with TC39 meetings since a few people will overlap.

@digitalinfinity
Copy link

@mikeal the doodle poll that @aruneshchandra linked to is to help figure out the date. The options are Feb 28 to Mar 3- these dates were picked with the idea that if we need a go/no go decision on ABI stable node as an experimental feature in Node v8.0, end of Feb/early march lines up with around when that branch will be created, and we should have a good idea around the state of the project (both NAPI and FFI) by then.

@mikeal
Copy link

mikeal commented Jan 5, 2017

Ah, solid reasoning, thanks @digitalinfinity :)

@aruneshchandra
Copy link
Author

Updated the original comment for clarity around dates. Also to @mikeal's point going forward we should better align these meetings to avoid date conflicts and overlaps. This time its more tactical due to v8.0 release schedule.

@mcollina
Copy link
Member

I would really like to join, the discussion at Node.js Interactive NA was really good and productive.

@aruneshchandra
Copy link
Author

aruneshchandra commented Jan 11, 2017

@mcollina please take this poll to indicate your participation preference http://doodle.com/poll/qk4krgicifty24kk

For now its looking like its going to be held at the Microsoft Redmond campus on Friday, March 3rd.

@mcollina
Copy link
Member

@aruneshchandra when the final date will be announced?

@aruneshchandra
Copy link
Author

I'm expecting a few more to respond to the poll - hopefully we will lock on the date by Friday Jan 20th and allow people to make travel arrangements in advance.

@aruneshchandra
Copy link
Author

aruneshchandra commented Jan 23, 2017

Based on the doodle poll - here's what the consensus was for the event:

Date: Friday 3rd of March 2017
Time: 9 AM to 4 PM
Location: Building 18 Microsoft Campus, Redmond WA
15701 NE 39th Street, Redmond, WA 98052

@dshaw dshaw closed this as completed Mar 3, 2017
@dshaw dshaw reopened this Mar 3, 2017
@joshgav
Copy link
Contributor

joshgav commented Mar 3, 2017

@ofrobots
Copy link

ofrobots commented Mar 3, 2017

@aruneshchandra
Copy link
Author

@joshgav
Copy link
Contributor

joshgav commented Mar 6, 2017

Notes: nodejs/abi-stable-node#128

@joshgav
Copy link
Contributor

joshgav commented Mar 6, 2017

also posted the notes to this repo in #5

@aruneshchandra
Copy link
Author

This event is done. I wrote a blog capturing the high level discussion and next steps.
https://blogs.windows.com/msedgedev/2017/03/13/notes-from-nodejs-vm-summit/

@dshaw dshaw mentioned this issue Mar 13, 2017
jasnell added a commit that referenced this issue Jul 31, 2017
jasnell added a commit that referenced this issue Nov 3, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants