imthenachoman / How-To-Secure-A-Linux-Server

An evolving how-to guide for securing a Linux server.
Creative Commons Attribution Share Alike 4.0 International
17.28k stars 1.1k forks source link

LICENSE #6

Closed ahangarha closed 5 years ago

ahangarha commented 5 years ago

Hi

May you please publish this valuable document Under some copyleft and specially Free Culture license (such as CC0, CC-BY, CC-BY-SA)?

imthenachoman commented 5 years ago

Hello. I do not know a lot about copyrights. I have never heard of copyleft or any of the others you mentioned. I will do some digging. If you have any advice or helpful articles I can read please share.

And would a guide like this need to be copyrighted? It's all information publicly available.

ahangarha commented 5 years ago

I do suggest you to have a look on https://creativecommons.org/ for more information on copyleft movement licenses for cultural works.

If you have no intention to copyright it and you have no issue providing it with zero restriction, you may go for CC0 / public domain. Otherwise, I do suggest CC-BY.

Many people put copyright on what they make as remix of other existing works and close them by saying ALL RIGHTS RESERVED. We, who support free culture movement, believe in SOME RIGHTS RESERVED, with lesser right the better approach since we believe this would be better for having a more diverse and creative world.

imthenachoman commented 5 years ago

I will check into it. Thank you!

rvdmei commented 5 years ago

No legal advice, but be aware that in the current form the work is copyrighted and making any copies is a copyright violation in many countries. By adding a license you can grant others to use (copy / modify) the material. For an example of a license check https://creativecommons.org/licenses/by-sa/4.0/

Edit:

I personally would not contribute to a public work without an open source license, my guess is that not having an open source license will limit the amount of people willing to contribute.

imthenachoman commented 5 years ago

Why/how is it copyrighted in its current form? I didn't add any copyright, did I?

I could use some help with which license to use and how to apply it? I have those links and I will check them out when I have time but with a 2 year old its hard to find the time to read up on copyrighting.

I don't want any copyright. I want folks to be able to do whatever they want with it, as long as I don't get in trouble for anything. It would be nice to get a link back or acknowledgement if thats an option.

Any advice?

imthenachoman commented 5 years ago

So that website makes it pretty easy. I went through the https://creativecommons.org/choose/ wizard and ended up with CC-BY-NC-SA. Is that okay or is it too restrictive?

rvdmei commented 5 years ago

Copyright is (often) a right, you get it because you wrote it (provided you did). At least this is the case in many counties. In some situations you have to claim copyright, you have to figure out for yourself where / when. As for the license, the NC clause adds a restriction. Example: I can’t use the content in slides / docs at work, even if I attribute you as author. Typically you would see the NC clause applied to creative work (art, etc.).

Edit:

Some background on copyright / no license: https://choosealicense.com/no-permission/
https://softwareengineering.stackexchange.com/questions/148146/open-source-code-with-no-license-can-i-fork-it

imthenachoman commented 5 years ago

I added copyright info. Is it okay?

rvdmei commented 5 years ago

You should add the license text as a separate doc to the repo too. You can use the Add License button in GitHub to do this.

imthenachoman commented 5 years ago

Oh boy. They don't have the creative commons ones in their list. I guess I'll go with MIT - it seems to make the most sense...

rvdmei commented 5 years ago

You can always add the file yourself. Creative Commons website should have all the info on what to add.

imthenachoman commented 5 years ago

Added. Thanks!!