-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[discussion] Move this repo to nodejs
org
#627
Comments
This is pretty important to me, since it's pretty standard. As a lot of distributions (and users) default to |
yes, that one is a blocker, since it’s the only bug (AFAIK) that still regularly breaks builds on a whole class of systems. |
It makes sense. io.js already bundles and (sort of) maintains a patched node-gyp. |
@TooTallNate If you're keen to push this forward then I'd propose that we make it the joint responsibility of @nodejs/addon-api and @nodejs/build (I'm pretty sure you're still in the former former) after you transfer the repo. I know a few people in both of those teams are keen to get their hands dirty on this. Getting some of the floating patches sorted out prior to Node.js v4.0 would be great, it's been weighing heavily on me for months and I'm sure all of the issues filed here have been annoying for you too. |
That sounds like a great idea @rvagg, I'll plan on transferring the repo and adding ownership for those 2 groups tomorrow. |
Inspired by nodejs/nan#266.
Seems pretty natural at this point, given the org.
I'd also love any additional eyes on top of issues/PRs.
Thoughts? /cc @nodejs @isaacs @nodejs/build @npm
The text was updated successfully, but these errors were encountered: