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
Please add a license to this repo #32
Comments
@vahidk — you closed the bug without comment, but I also didn't see a |
It seemed like a mass copy pasted message that's why I didn't comment. This repo is a tutorial. What percentage of tutorials/ebooks come with an open source license? |
The question is not whether it's a tutorial or a production system; the question is what can users do with this content (e.g., can they redistribute it? can they extend it? can they modify or update it? etc.). From a copyright perspective, a lack of a license prohibits these activities and others. Please see the docs I quoted from GitHub regarding what a lack of a license does for this repo; they have an entire site on this: https://choosealicense.com, specifically, please take a look at https://choosealicense.com/no-permission/ which describes this situation in detail. My comment above got a 👍 vote from another user, so clearly it's relevant and important for other users of your repos. Please consider adding an open-source license to your repositories. |
My point is, it's a tutorial. It could be on Medium and you wouldn't comment on having a license file for it. I'm using Github as a publishing platform. The way it currently works is that people who want to use this material just send me an email and I usually tell them it's okey to use to this material. So it's on a case by case basis. If you really are interested to use this material personally we can discuss privately. I might add a license later. I just am not sure what's a suitable license at this point. |
Thanks for the clarification. FWIW, https://choosealicense.com has options both for code (applicable to https://github.com/vahidk/TensorflowFramework) as well as this repo (which isn't code). E.g., Creative Commons licenses are widely used for text/documentation. Of course, the choice of license (or to have no license, defaulting to "all rights reserved" copyright) is up to you, and it sounds like you've chosen to do that and handle exceptions on a case-by-case basis. |
Could you please add an explicit
LICENSE
file to the repo so that it's clear under what terms the content is provided, and under what terms user contributions are licensed?Per GitHub docs on licensing:
Thanks!
The text was updated successfully, but these errors were encountered: