nodejs / nodejs/nan

Time for a proper meeting (?)

Open
#373 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
3.4k
Forks
531
Avg merge
21m
Merged PRs (30d)
1

Description

When we decided to move into the io.js org we collectively agreed that we didn't really want to add the overhead of a regular meeting or anything above GitHub chatter because it had been working so well. I'm certainly not keen to add more meetings to my calendar, however, there are a number of outsiders that are looking to get involved that would be of great value to both NAN and the broader ecosystem in general and they can't see an obvious way to get up to speed. So I'd like to propose we have a meeting within the next couple of weeks to talk about the current state of the project, the future (tentative) plans for the project and see what others would like to be able to contribute.

In particular, the IBM V8 team would like to get involved in contributing and they have some excellent expertise around V8 due to the porting work they've had to do for their architectures. Also, the Microsoft Node/Chakra team would like to explore ways to bridge their work in their Chakra fork with the native addon ecosystem. The work they have done so far in bridging the Chakra API to appear as the V8 API to Node is very impressive and I see this as a great wedge for any work we may want to do for a more generalised compatibility layer.

I'll put up a doodle soon so we can find a good time unless I get shouted down by people who don't want to meet. At a minimum it would be good to have @kkoopa and @bnoordhuis on board.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or implementation entry points are named. Start by reading the issue and its 12-comment discussion, then determine whether a meeting is still wanted and what participation or contribution guidance is needed; done would require an agreed meeting plan and follow-up, but the issue does not define either.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, nodejs
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.