search

metal / metal.js

Build UI components in a solid, flexible way
http://metaljs.com
Other
230 stars 59 forks source link

Package.json spdx BSD format #411

Open lneves12 opened 5 years ago

lneves12 commented 5 years ago

I wonder if the package.json license field shouldn't follow the SPDX format.

Checking https://spdx.org/licenses/0BSD.html#licenseText the short format should be 0BSD instead of "BSD".

Am I missing anything here?

mbrukman commented 4 years ago

This project's license is actually the 3-clause BSD license aka BSD-3-Clause in SPDX terms, whereas you linked to the 0-clause BSD license. This project shows a mix of SPDX identifiers, including an MIT license for one of the packages:

$ grep license `find . -name package.json`
./packages/metal-dom/package.json:  "license": "BSD",
./packages/metal/package.json:  "license": "BSD-3-Clause",
./packages/metal-events/package.json:  "license": "BSD",
./packages/metal-incremental-dom/package.json:  "license": "BSD",
./packages/metal-jsx/package.json:  "license": "BSD",
./packages/metal-state/package.json:  "license": "BSD",
./packages/metal-soy-bundle/package.json:  "license": "MIT",
./packages/metal-assertions/package.json:  "license": "BSD-3-Clause",
./packages/metal-isomorphic/package.json:   "license": "BSD",
./packages/metal-web-component/package.json:  "license": "BSD-3-Clause",
./packages/metal-component/package.json:  "license": "BSD",
./packages/metal-soy/package.json:  "license": "BSD",

The project owners should review this and consider: