Closed jaredsmith closed 6 years ago
I agree. In my environment we cannot use this package without a license file in the repository.
FWIW, monorepo's root package.json
says the license is ISC:
Some packages are under the ISC license, while others are under the MIT license.
The root package.json
is under the ISC, though that was setup automatically when this repository was converted to a mono-repo, and that particular license from that particular package.json
file doesn't apply to any published package because the root package.json
isn't published.
My understanding is that ISC and MIT are functionally equivalent, so it may be worth looking into whether we can consolidate around a single license.
it may be worth looking into whether we can consolidate around a single license.
That would be great!
Some packages are under the ISC license, while others are under the MIT license.
As far as I am concerned, having different licenses in different packages is fine. The issue I see is that some packages don't contain any LICENSE
file, see e.g. packages/conventional-commits-parser.
IMO, the first (and easy) step is to ensure every package has a LICENSE files matching the license entry in its package.json
file.
IMO, the first (and easy) step is to ensure every package has a LICENSE files matching the license entry in its package.json file.
Agreed, along with the fact that it's just the right thing to do.
I think right now we're waiting on an update to #287
I have not seen any progress on #287.
Would someone be available to submit another pull request containing a LICENSE
file in each package within the conventional-changelog
mono-repository?
I'll try to get to this today or tomorrow. It fell off my radar.
I'll try to get to this today or tomorrow.
Thank you @jaredsmith! I've re-assigned the issue to you.
Pull request #287 has been updated.
Thanks to the work from @jaredsmith we have successfully published the following packages with new LICENSE
files:
@bajtos and @blaineadams License issues should now be addressed. Please let us know if there are any other License related issues following these releases.
Please add a LICENSE file -- The MIT license specifically states that the text of the license must accompany the source code.