-
Notifications
You must be signed in to change notification settings - Fork 17
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
Create license.txt file #2
Open
strypey
wants to merge
60
commits into
PixelatedHeart:master
Choose a base branch
from
waako:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
Fixed hash collision bug
Added extra key combination block
Added lazy images loading
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.
Your source code is automatically copyright in most countries just because you published it, so it's good practice to have a license.txt file explaining how people can and can't use your code. I'm suggesting the AGPL, since that's the best way of making sure anyone who runs a service based on your code shares the source of their version with their users, and with you. But you can replace my suggestion with whatever license you like, including a proprietary one that says "don't use our code ever except on unsee.cc!", or one like the WTFPL that tells people they can do whatever they want with your code. See: https://choosealicense.com/
I just took those names from the organization of the repo you forked from. You'll need to change the names to reflect whoever actually wrote the original code, and make sure they all agree on the choice of license. Also, if there are files in the repo that are under another license (I think I saw some mention of "BSD" when I searched for "license" in the original repo?), it would be good to list there here, with the names of the creators, the license they're under, and a link to the original.