Skip to content
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

Closed
TooTallNate opened this issue May 19, 2015 · 5 comments
Closed

[discussion] Move this repo to nodejs org #627

TooTallNate opened this issue May 19, 2015 · 5 comments

Comments

@TooTallNate
Copy link
Contributor

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

@rgbkrk
Copy link

rgbkrk commented May 21, 2015

This is pretty important to me, since it's pretty standard. As a lot of distributions (and users) default to python being python3, updates are needed. #502 is one fix that I'd like to see go in.

@flying-sheep
Copy link

yes, that one is a blocker, since it’s the only bug (AFAIK) that still regularly breaks builds on a whole class of systems.

@kkoopa
Copy link

kkoopa commented May 25, 2015

It makes sense. io.js already bundles and (sort of) maintains a patched node-gyp.

@rvagg
Copy link
Member

rvagg commented Aug 17, 2015

@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.

@TooTallNate
Copy link
Contributor Author

That sounds like a great idea @rvagg, I'll plan on transferring the repo and adding ownership for those 2 groups tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants