-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
Do we need to include any new licenses when we ship the new v8 inspector? #7123
Comments
v8_inspector is extracted from Blink (license). We can add a LICENSE file to it (/cc @pavelfeldman). jinja2 and markup_safe are build time dependencies. |
If you look in license-builder you'll see a section at the bottom for build tools, jinja2 and markup_safe can go there. Being able to pull LICENSE files in some form for both of these as well as v8_inspector in-tree would be ideal. Currently we only have to go out of tree for punycode and we can't properly match version for that when we do so it's not ideal. |
@ofrobots ... can you verify that neither jinja2 or markup_safe insert any of their own licensed boilerplate or template code into the generated output during build time? If they do, then we may still need to include mention of those bits in the license file. |
@jasnell jinja2 (website) is a simple python template engine (similar to handlebars or mustache). It is used to generate protocol files for v8_inspector. markup_safe is a dependency of jinja2. Here's an example template file |
Awesome. Thank you!
|
This issue hasn't been resolved but the inspector shipped in Node.js v6.3.0. Given that Blink's license is not the same as Node.js' primary license the v8_inspector really should have its own LICENSE since some of the source files say
and at present there is no LICENSE in deps/v8_inspector. |
With regards to dependencies
|
A utility library also used by other projects (WebKit uses it, as does Mozilla.) I'm a bit surprised to see LGPL code in there. @ofrobots? |
It should not be LGPL, I'll fix it. But more importantly, v8_inspector/deps/wtf is not a part of upstream, so this whole folder should not be there. [EDIT:ofrobots: fix link] |
The deps/v8_inspector directory is a gathering of external dependencies, and no original content other than the README.md file (which documents this).
|
Ouch. It should have been inlined in |
This is my bad. #7302 should have deleted |
So from what I understand wtf will be removed so the remaining concern would be deps/v8_inspector/deps/jinja2/ext/jinja.el. From earlier comments it sounds like it is only used to generate files from templates, which don't include the licence, and only these new files are used to create what is part of the delivered node packages. The result being that none of the files with the GPL license are "shipped" as part of the Node.js deliveries. @ofrobots is this correct ? |
jinja.el is an emacs syntax highlighting script. It's not used and can be removed without harm. |
Yes, deps/wtf will be removed in the next roll (I'm working on this). The jinja.el script is neither used in the build nor shipped as part of a node distribution. |
@ofrobots when do you expect the next roll to come in? Is it safe to assume that it should resolve all licensing concerns? |
Remove wtf files as v8_inspector no longer needs them. Ref: nodejs#7123
These are the concerns that I am aware of:
|
To add a LICENSE file along with the v8_inspector code, we need to pick up v8_inspector from an intermediate repository: https://github.com/pavelfeldman/v8_inspector. This repo still tracks upstream code in Blink. This roll also picks up the latest v8_inspector from upstream fixing a few issues. * Pickup commit id bc60957 from pavelfeldman/v8_inspector * Update node.gyp to adapt to the new file paths * Update the DevTools hash for the devtools frontend. Fixes: nodejs#7123 Fixes: nodejs#7736 Fixes: nodejs#7734
To add a LICENSE file along with the v8_inspector code, we need to pick up v8_inspector from an intermediate repository: https://github.com/pavelfeldman/v8_inspector. This repo still tracks upstream code in Blink. This roll also picks up the latest v8_inspector from upstream fixing a few issues. * Pickup commit id bc60957 from pavelfeldman/v8_inspector * Update node.gyp to adapt to the new file paths * Update the DevTools hash for the devtools frontend. Fixes: nodejs#7123 Fixes: nodejs#7736 Fixes: nodejs#7734 PR-URL: nodejs#7796 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: jasnell - James M Snell <jasnell@gmail.com>
To add a LICENSE file along with the v8_inspector code, we need to pick up v8_inspector from an intermediate repository: https://github.com/pavelfeldman/v8_inspector. This repo still tracks upstream code in Blink. This roll also picks up the latest v8_inspector from upstream fixing a few issues. * Pickup commit id bc60957 from pavelfeldman/v8_inspector * Update node.gyp to adapt to the new file paths * Update the DevTools hash for the devtools frontend. Fixes: #7123 Fixes: #7736 Fixes: #7734 PR-URL: #7796 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: jasnell - James M Snell <jasnell@gmail.com>
It does not appear that v8_inspector has a LICENSE but some of the vendored deps do including:
I do not believe we will have to as both of these appear to be build tools, but I'm not entirely sure and wanted to play it safe.
@ofrobots is there anything we should know license wise before shipping?
@mikeal thoughts?
/cc @nodejs/tsc
The text was updated successfully, but these errors were encountered: