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

Missing LICENSE #38

Open
jwflory opened this issue Jul 7, 2016 · 0 comments
Open

Missing LICENSE #38

jwflory opened this issue Jul 7, 2016 · 0 comments

Comments

@jwflory
Copy link

jwflory commented Jul 7, 2016

First, the standard disclaimer: I am not a lawyer, and this does not constitute legal or financial advice.

Generally, it is a good idea to use FSF or OSI-approved licenses (which can be found here and here). Once you have chosen a license, you should place it in the root directory of your repository in a file named LICENSE.

The Free Software Foundation has a useful guide for choosing a license. I often reference the Software Freedom Law Center's Legal Primer for both practical and academic purposes (highly recommended). tldrlegal.com is a useful resource for comparing the various FOSS licenses out there once you have some context and background to what they mean.

To get a hold of actual lawyers and advisors who help FOSS projects, you could reach out to the FSF, SFLC, and OSI at:

Hope this helps, and happy hacking!

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

No branches or pull requests

1 participant