Skip to content

Add licenses to sub packages #1746

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

Merged
merged 1 commit into from
Feb 22, 2018

Conversation

honzajavorek
Copy link
Contributor

@honzajavorek honzajavorek commented Feb 22, 2018

Fix #1744. Not sure how to trigger patch release, couldn't find any contributing docs. Please advise.

Replaces #1745

Copy link
Collaborator

@ljharb ljharb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't really necessary; the SPDX-compliant "license" field in package.json notes that it's MIT, and that's sufficient due to https://github.com/airbnb/javascript/blob/master/LICENSE.md.

However, this seems fine.

@ljharb ljharb merged commit ea14bda into airbnb:master Feb 22, 2018
@honzajavorek honzajavorek deleted the honzajavorek/add-licenses branch February 23, 2018 09:20
@honzajavorek
Copy link
Contributor Author

@ljharb Thank you! While I'm no lawyer myself, I think although the package is a product of the repository with a license text, it is still necessary to accompany the package with a full license text, as it is distributed separately. And the MIT license requires the full license text to be alongside the code. Will link this as well: babel/babel#7308 (comment)

@honzajavorek
Copy link
Contributor Author

honzajavorek commented Feb 23, 2018

@ljharb btw, are you planning a new release?

@ljharb
Copy link
Collaborator

ljharb commented Feb 23, 2018

The next release will be breaking (due to other merged changes); I’m not going to backport a patch release just for this.

@ljharb
Copy link
Collaborator

ljharb commented Feb 23, 2018

Separately, the point of a SPDX-compliant identifier, as i understand it, is that the license text is no longer relevant or needed because it is uniquely identified by the license identifier (which implies license text). Maybe @kemitchell can confirm, or correct me if I’m wrong?

@honzajavorek
Copy link
Contributor Author

I’m not going to backport a patch release just for this.

I didn't think of it like that. It was more like whether you have an idea when the next release might happen.

@ljharb
Copy link
Collaborator

ljharb commented Feb 23, 2018

No idea, but hopefully soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants