The license OpenClonk uses grants free access to our source code for any purpose you wish. To avoid license compatibility issues, we ask you to put your contributions to this project under the same license as we do with ours.
If you contribute to OpenClonk, you license your code to the public under the ISC license. You must therefore be able to grant this license. This means that you either
a) hold the copyright to the contributed code, which is the case if you produced it yourself, or
b) you have acquired the code from a source that is ISC compatible, for example code in the public domain or code that itself underlies the ISC license.
In the first case, you retain your copyright. You never need to transfer your copyright to the OpenClonk project. You can relicense your code to other parties any way you like. However, you cannot withdraw your license under the terms of the ISC license.
The ISC license
Permission to use, copy, modify, and/or distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
If you contribute to OpenClonk, you license your code to the public under the ISC license. You must therefore be able to grant this license. This means that you either
a) hold the copyright to the contributed code, which is the case if you produced it yourself, or
b) you have acquired the code from a source that is ISC compatible, for example code in the public domain or code that itself underlies the ISC license.
In the first case, you retain your copyright. You never need to transfer your copyright to the OpenClonk project. You can relicense your code to other parties any way you like. However, you cannot withdraw your license under the terms of the ISC license.
The ISC license
Permission to use, copy, modify, and/or distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Clarifications
The ISC license is compatible to the GPL. This means that you can use code from OpenClonk and use it in any application that is licensed under the ISC license or the GPL. However you cannot take GPL code and contribute it to OpenClonk unless you are the copyright owner and are willing to relicense the code under ISC license terms.
The ISC license is compatible to the GPL. This means that you can use code from OpenClonk and use it in any application that is licensed under the ISC license or the GPL. However you cannot take GPL code and contribute it to OpenClonk unless you are the copyright owner and are willing to relicense the code under ISC license terms.
![[es]](/mwf/flags/es.png "Spain")
>However, you cannot withdraw your license under the terms of the ISC license.
I don't fully get that sentence. Do you mean...:
However, you cannot withdraw your license from the OpenClonk project under the terms of the ISC license.
The OpenClonk project does not have a special license from the copyright holder. Instead, he grants a world-wide, non-exclusive, royalty-free license under the terms of the ISC license. As such, he cannot withdraw his license from one particular licensee. The sentence is supposed to mean that there is no way to revoke the license to the public, once it is granted.
![[de]](/mwf/flags/de.png "Germany")
> b) you have acquired the code from a source that is ISC compatible, for example code in the public domain or code that itself underlies the ISC license.
...or a similar permissive one like revised BSD or MIT-style. We might also like to mention that LGPL-Code is okay for libraries - CR had no problem with that either, after all.
I think the real issue is to get the artists to understand and agree with this. We don't want to have to remove something later because the artist is upset that somebody else modified his or her work and claims that they never agreed to that. We also have to discuss wether we need a really permissive license for gameplay content. The only real reason for the ISC instead of (for example) the GPL is that Redwolf Design might do another shareware game as they did with Clonk Endeavour. And as with CE, they could create new graphics.
I already mentioned to Newton we might need to use a different license for artistic content. I guess something from Creative Commons might be appropriate.
I think either CC-BY-SA or CC-BY would be appropiate. Opinions?
![[us]](/mwf/flags/us.png "United States")
Do we have an actual case of anyone not contributing because he wants to use CC instead of ICS?I think we should not mix licences unless we absolutely have to. Especially not with one of the communist copyleft licences!
I dunno, it says >Permission to use, copy, modify, and/or distribute this software for any...
software. I wonder if this is applicable for artwork?
For the attachment form---------------
Important!
When you upload contributions for OpenClonk, always specify a copyright message in the form of e.g ...
Copyright © 2009 Jon Doe
License: CC-BY
... in your post. If you don't hold the copyright of the uploaded contribution, state the original license and copyright message of the contribution in your post, instead. We ask you to license your contribution under the Creative Commons Attribution License, otherwise we might not be able to use it in OpenClonk. Read more here (insert here: link to the forum sticky/wiki)
Attention: If you do not specify any information about copyright or license, we assume that the contribution is 1. your work and 2. that you license it under the CC-BY license!
------------
This sets the standard for all uploaded contributions where the ppl are too lazy to state any license or copyright message to CC-BY but leaves the freedom to not put it under any license yet or put it under another license.
I think we'll all get tired very soon by those Copyright-statements, and half of the posters will forget them anyway. The wikipedia approach might be an interesting example to follow. Something like this?By uploading the attachment you agree that either you are the author of the work and release it under the CC-by license (for artwork) or ISC license (for code), or have mentioned the author and license in the message body. See our to be written FAQ entry for why.
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill
