forked fromamcewen/HttpClient
- Notifications
You must be signed in to change notification settings - Fork171
Add dedicated license file#185
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or 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
Standardization in license documentation is important because, in addition to making it easy for humans to find thisvital information, it allows machines to automate the process of license type determination, which is useful both fordiscovering suitable open source projects as well as checking open source license compliance.Previously, the open source license of this project was not documented in a dedicated license file. Due to this, eventhough the project is licensed under a standardized open source license, the open license type could not be identifiedwith 100% confidence by machines (e.g., the Licensee Gem used by the GitHub website), which meant identification couldonly be made by a human carefully evaluating the license text.The project's license is hereby documented in a standardized license file. The result is that the project's open sourcelicense type can now be automatically identified. This does not result in any change to the project licensing.
566b6e1 intoarduino-libraries:master 3 checks passed
Uh oh!
There was an error while loading.Please reload this page.
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
topic: documentationRelated to documentation for the project topic: infrastructureRelated to project infrastructure type: enhancementProposed improvement
1 participant
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.
Standardization in license documentation is important because, in addition to making it easy for humans to find this vital information, it allows machines to automate the process of license type determination, which is useful both for discovering suitable open source projects as well as checking open source license compliance.
Previously, the open source license of this project was not documented in a dedicated license file. Due to this, even though the project is licensed under a standardized open source license, the open license type could not be identified with 100% confidence by machines (e.g., theLicensee Gem which isused by the GitHub website), which meant identification could only be made by a human carefully evaluating the license text.
Astandardized license file is hereby added to the project. The result is that the project's open source license type can now be automatically identified. This does not result in any change to the project licensing.