Adding licenses to splits #1695
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If sub-splits are meant to be used on projects directly, like this one https://github.com/thephpleague/flysystem-aws-s3-v3, then they should be signed with their own license.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello everyone,
If flysystem split packages are meant to be used outside of the monorepo,
they should also be signed with clear licenses, otherwise, it narrows down the applicability scope and therefore adoption.
Eg
https://github.com/thephpleague/flysystem-ftp
https://github.com/thephpleague/flysystem-aws-s3-v3
Cheers,