search

platramos / tokenTrust

Python based blockchain that is more datastore than currency
0 stars 0 forks source link

Pick a OS licence (or choose not to have one) #8

Open m3dwards opened 7 years ago

pduldig-at-tw commented 7 years ago

There are a few ways we can go:

GPL BSD *MIT

In the words of satoshi:

If the only library is closed source, then there's a project to make an open source one. If the only library is GPL, then there's a project to make a non-GPL one. If the best library is MIT, Boost, new-BSD or public domain, then we can stop re-writing it. I don't question that GPL is a good license for operating systems, especially since non-GPL code is allowed to interface with the OS. For smaller projects, I think the fear of a closed-source takeover is overdone.

I would like us to consider the same license as bitcoin, which is MIT. This does not limit commercial exploitation or derivatives, which may increase adoption.

platramos commented 7 years ago

Apparently Ethereum hasn't even picked which license they are going to go with. Is this something that needs to be decided now?

pduldig-at-tw commented 7 years ago

We dont have to pick something now, however if we publish code to Github it will fall under the default github license. This is an implicit Open Source license, however it does not contain the same user freedoms (ie: Free) as GPL, nor the same developer freedoms as BSD/MIT.

What happens if I don't choose a license?

You're under no obligation to choose a license. It's your right not to include one with your code or project, but please be aware of the implications. Generally speaking, the absence of a license means that the default copyright laws apply. This means that you retain all rights to your source code and that nobody else may reproduce, distribute, or create derivative works from your work. This might not be what you intend.

Even if this is what you intend, if you publish your source code in a public repository on GitHub, you have accepted the Terms of Service which do allow other GitHub users some rights. Specifically, you allow others to view and fork your repository within the GitHub site.

If you want others to use, copy, modify, or contribute back to your project, we strongly encourage you to include an open source license.