Move gyp-next to the nodejs org

[ryzokuken]

Request to move gyp-next (https://github.com/ryzokuken/gyp-next) to the nodejs organization. More context at nodejs/node#32090.

[ryzokuken]

/cc @targos @cclauss @rvagg @MylesBorins

[targos]

+1

[mhdawson]

+1

[MylesBorins]

+1 with the name gyp-next

…

On Mon, Mar 9, 2020, 12:57 PM Michael Dawson ***@***.***> wrote: +1 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#475?email_source=notifications&email_token=AADZYV3U2AKPLYCZAMNXIGTRGUUYDA5CNFSM4LEHFP62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOICYOY#issuecomment-596651067>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADZYV6RBEVZQOBMJMYGH2TRGUUYDANCNFSM4LEHFP6Q> .

[joyeecheung]

+1

[rvagg]

Full context:

GYP is a Google tool, now deprecated by them, we've taken over maintenance of it and it's used in nodejs/node and node-gyp (libuv too, but they're using a pruned-down version and are about to rip it out entirely). We're in the middle of a synchronization effort between the two projects and the repo on question here should be a synthesis of all that so ought to end up as the source of truth for both nodejs/node and nodejs/node-gyp.

We can't just take over the name "GYP" due to copyright concerns. Refael put in a bunch of work to make GYP3 but that stalled in a previous attempt to bring it into the org. The name "GYP3" is also too similar to "GYP". In private discussions (Myles also involved in these on behalf of Google), "gyp-next" was arrived at as the best attempt at a name that was distinct enough from "GYP" that it indicated it was a separate project. Nobody's particularly enamored with the name, it's a pragmatic choice.

If someone has a better name, now would be the time to speak up, otherwise I suspect "gyp-next" is going to be baked in for good.

[Qard]

PYG: (Here's the) Project You Generated 😆

[MylesBorins]

I very much like pyg. Can't get the Beatles song "Little Pygies" out of my head now.

…

On Mon, Mar 9, 2020, 11:23 PM Stephen Belanger ***@***.***> wrote: PYG: (Here's the) Project You Generated 😆 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#475?email_source=notifications&email_token=AADZYV6CMIGEMY5FEECBVYDRGWXBJA5CNFSM4LEHFP62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOJ3FDA#issuecomment-596882060>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADZYVZSTOL5WOQFTPVTNP3RGWXBJANCNFSM4LEHFP6Q> .

[cclauss]

pip install pyg does have a ring to it. But it is already taken by @rubik‘s long defunct https://pypi.org/project/pyg/

[Qard]

Hasn't been updated in seven years. Maybe we could ask to reclaim the name? 🤔

Alternatively:

JUNA - Just Use Ninja Already 😉
JHEF: Javacript Has Enough Frameworks (so we made one for Python instead)
NACL: Node.js Abstract Compiler Launcher (That'll get us away from Google copyright concerns for sure )

More seriously:

NUB - Node.js Universal Builder
JUBE - JSON-based Universal Build Environment

[richardlau]

I kind of feel that, boring as it may be, anything that doesn't have "gyp" as part of its name is just going to be confusing.

[Trott]

I very much like pyg. Can't get the Beatles song "Little Pygies" out of my head now.

That'll do: pyg. That'll do.

Er, uh, more seriously, I kinda agree with @richardlau that including gyp as part of the name is the user-friendly thing to do.

[sam-github]

I agree, to, should have gyp. I'm fine with gyp-next, the README should be clear that the goal is not to resuscitate gyp or encourage its use for new projects, but to maintain it sufficiently for Node.js addons and libuv.

[cclauss]

I would advocate that this module can be pip install-ed from PyPI. My sense is that there has been a lot of unnecessary questions and delay in working with the current gyp because we have resisted the use of pip install.

[sam-github]

Can we pip install and vendor it? Node.js build doesn't depend on pip ATM for building, but if pip's a better way to get it into our deps or tools than cp -r, I'm OK with using it.

[cclauss]

Yes. pip and vendor can co-exist.

[targos]

/cc @nodejs/tsc @nodejs/community-committee per https://github.com/nodejs/admin/blob/master/transfer-repo-into-the-org.md#step-2-open-an-issue-in-the-admin-repository

[bnb]

SGTM

[ryzokuken]

Can we pip install and vendor it?

Yes. pip and vendor can co-exist.

That's the plan anyway.

Re: the name, @Qard suggested that the "gyp" in the name can stand for "Google Yeets Projects" which is an amazing name IMO as long as it's okay with Google folks (mean no offense, it's just a fact about the past of the project...) @MylesBorins thoughts?

[ryzokuken]

@targos the document doesn't exactly say how many approvals are required or how long we should wait until we can proceed with the transfer.

[targos]

There's a reference to another document which says we must wait 72 hours.

[richardlau]

The link to the other document is broken (I've raised #476 to fix it).

[richardlau]

https://github.com/nodejs/admin/blob/master/GITHUB_ORG_MANAGEMENT_POLICY.md#repositories (the corrected link) says (as @targos points out) to wait for 72 hours.

No approvals are required, just no objections in that 72 hour period.

[nschonni]

Just curious if this is still a stopgap to keep it alive while a non-Python alternate is proposed?

[nschonni]

The GYP license also only only seems to restrict the use of the Google trademark, rather than GYP name

https://chromium.googlesource.com/external/gyp/+/refs/heads/master/LICENSE

• Neither the name of Google Inc. nor the names of its
  contributors may be used to endorse or promote products derived from
  this software without specific prior written permission.

[Qard]

Wouldn’t making it pip installable increase the likelihood people use it for other things, which we specifically don’t want? 🤔

[cclauss]

I doubt that anyone is going to find gyp just by search among the +222k packages on PyPI.

[ryzokuken]

Done.