Skip to content
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
wants to merge 60 commits into
base: master
Choose a base branch
from
Open

Conversation

strypey
Copy link

@strypey strypey commented Jun 8, 2018

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.

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.

3 participants