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? #17

Closed
jwflory opened this issue Aug 2, 2017 · 6 comments
Closed

Missing LICENSE? #17

jwflory opened this issue Aug 2, 2017 · 6 comments

Comments

@jwflory
Copy link

jwflory commented Aug 2, 2017

I was looking into the repository and noticed that there was no license file in the root directory. I did see in the README that it's copyrighted to @kushaldas, but I'm not sure if this was a temporary or permanent plan (since it seems like there's also other people who have contributed to this repo already).

Since most of it is Markdown content, I would suggest adding a Creative Commons license so the content here can remain free and open, and others can contribute knowing that their additions to the book will be added to a larger project dedicated to open knowledge.

This would also likely invite other people to contribute to the efforts of helping write the book as well. :) Plus, when you use a CC license and add it into the LICENSE file in the root directory, GitHub will also show the license type in the header bar and provide a brief explanation of what the license means.

@jasonbraganza
Copy link
Collaborator

jasonbraganza commented Aug 2, 2017 via email

@jwflory
Copy link
Author

jwflory commented Aug 3, 2017

It would still be nice to license it under a Creative Commons license now, if that is the future intent. :) This is more motivating for a potential contributor to know if my contributions would be licensed under a free and open license.

Additionally, it also makes it easy for others to cross-promote the book too. For example, if I wrote an article for Opensource.com based on one of the book's sections, I would link back and cite to the book per the requirements of the CC license, and also invite others to contribute to the book as well. Under normal copyright restrictions, I'd be more inclined to write something of my own.

@jasonbraganza
Copy link
Collaborator

jasonbraganza commented Aug 3, 2017 via email

@ghost
Copy link

ghost commented Jan 9, 2018

Free Software licenses are good for your health :-P

@kushaldas
Copy link
Owner

I am keeping the current license as it is.

@etanot
Copy link
Contributor

etanot commented Jul 21, 2021

Hi! @kushaldas, could you please reconsider adding a license?

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

4 participants