Discussion: Handing off GYP from Chromium to nodejs.org

Skip to first unread message

Refael Ackermann

Apr 26, 2017, 5:00:33 PM4/26/17
to gyp-developer
Hello All,

We at the nodejs org are deeply invested in the ".gyp" syntax, as it is used as our format for building native modules.

Also it's our framework for scaffolding the build for the entire project.

We think we would like to take over the tool formally, instead of just forking it, so all stakeholders can benefit.
We would devote dev resources to clear the bug backlog, and be more proactive with adapting to new tools (i.e. the VS2017 story).

Would the gyp-developer be in favor of such a move?

Dirk Pranke

Apr 26, 2017, 7:18:50 PM4/26/17
to Refael Ackermann, gyp-developer
Hi Refael,

I think the other GYP maintainers and I would generally be okay with some sort of transition, but up until recently there's been very little activity in GYP itself from the Node folks. Normally the way I'd want to transition the ownership of an open-source project would be to get people up to speed by making them contributors to the project, and then generally work out some sort of transfer once the current maintainers are comfortable with the new people.

It's entirely possible that various Node devs are very familiar with GYP, but have been reluctant to upstream changes or even ask for changes, because perhaps it was perceived that we were only focused on Chromium. And, it's certainly true that GYP has been in "maintenance mode" and not even really maintained for quite some time.

Does it make sense to try and proceed by having yourself and the other Node folks start by being much more active in terms of submitting bug fixes (like you've been doing of late) and proposing changes, and for myself and the other existing committers to try and be much more responsive about reviewing changes? And then we can go from there ...

-- Dirk


You received this message because you are subscribed to the Google Groups "gyp-developer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gyp-developer+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Refael Ackermann

Apr 26, 2017, 9:06:11 PM4/26/17
to Dirk Pranke, gyp-developer
Sounds like a great idea!
We already have a bunch of "floating" patches that people have been reluctant to push upstream.

Mark Callow

May 1, 2017, 6:02:55 AM5/1/17
to gyp-developer

On Thursday, April 27, 2017 at 6:00:33 AM UTC+9, Refael Ackermann wrote:
Would the gyp-developer be in favor of such a move?

I would certainly like to see GYP find a new home. I'd be in favor of this and doing the transfer in the manner suggested by Dirk.

Refael Ackermann

May 1, 2017, 6:43:18 AM5/1/17
to Mark Callow, gyp-developer
For now it's been a challenge to get the people in nodejs excited about GYP (other than me ;) )
This week we have the collaborators summit, hopefully some good news will come from it.

Reply all
Reply to author
0 new messages