Creation of LICENSE file to add a license #1
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
By default, any creative work without an explicit license, including Github repositories, have the most restrictive of them all: exclusive "all rights reserved" copyright. I assume that since you have your (awesome) software in a Github repository, it is your intent for people to use it, fork it and improve it. Thus, I'd strongly advise to add an open source license to facilitate this -- otherwise, it would be illegal to use this code in any way. If you want to allow any use of it, I'd recommend a MIT License. Since you may opt to protect its code from any third-party wanting to profit from it, you may prefer to use the AGPL License (which is the one I'm including in this pull-request). I am happy to help clarify doubts or uncertainties around all this, or help choose another license if you don't like these.
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.
By default, any creative work without an explicit license, including Github repositories, have the most restrictive of them all: exclusive "all rights reserved" copyright. I assume that since you have your (awesome) software in a Github repository, it is your intent for people to use it, fork it and improve it. Thus, I'd strongly advise to add an open source license to facilitate this -- otherwise, it would be illegal to use this code in any way. If you want to allow any use of it, I'd recommend a MIT License. Since you may opt to protect its code from any third-party wanting to profit from it, you may prefer to use the AGPL License (which is the one I'm including in this pull-request). I am happy to help clarify doubts or uncertainties around all this, or help choose another license if you don't like these.