> I have noticed though that under the GPL licence terms, editing the sprites is not allowed.
Huh? Are you mixing up GPL and CC-*-ND?
> Also I'd like to say that those 2 licences are confusing.
From the FAQ:
You must follow only one of the licenses. However, when you re-distribute/edit, you are encouraged to include/use all of the licenses, so the license spectrum (and thus sum of people/projects who can use the art) doesn't shrink.
> If you use CC-BY-SA art with other works, the resulting work must be CC-BY-SA.
I think the main question is whether including art into a game means creating a 'Collection' or an 'Adaption' (see CC-BY-SA 3.0 legal code 1.a and 1.b). IMHO game data (= art and configuration) is a 'Collection', in which case the CC-BY-SA agreement does not force you to make the whole 'Collection' CC-BY-SA.
> Games are a weird corner case.
I fully agree on this one. ;-)
> If a screenshot contains a CC-BY-SA work mixed with other works, the entire screenshot must be released CC-BY-SA.
This one is indeed a weird case. The result would probably be that, if a user takes such a screenshot, he wouldn't be able to release it at all, because he would either be breaking CC-BY-SA or the propietary license which covers the rest of the art.
> But the code license is not affected either way.
This. Taking into consideration that the code would still remain propietary, it probably wouldn't hurt a closed-source game to release all of its art under CC-BY-SA.
I'm not a lawyer, so don't take this as legal advice (you should probably contact a real lawyer instead), but that's how I understand CC-BY-SA:
It's generaly perfectly fine to encorporate CC-BY-SA content into a closed source project (and you don't need to make all of your art or even the entire project CC-BY-SA), provided you give credit in a appropiate manner and make all modifications ('Adaptions' in the CC-BY-SA legal code) to the original content available under CC-BY-SA. There are however restrictions:
You may not offer or impose any terms on the Work that restrict the terms of this License or the ability of the recipient of the Work to exercise the rights granted to that recipient under the terms of the License.
[ ...]
When You Distribute or Publicly Perform the Work, You may not impose any effective technological measures on the Work that restrict the ability of a recipient of the Work from You to exercise the rights granted to that recipient under the terms of the License.
The first one may be incompatible with the App Store's Terms and Conditions (I didn't dig into these terms, so that's just an assumption) and the second one is clearly incompatible with any form of DRM. It might be possible to solve these incompatibilites by publishing the CC-BY-SA content and any Adaption of this content on your projects website, but again, I'm not a lawyer, so this might or might not be true.
EDIT: When I started my response, Clint did not have responded yet.
There is some documentation at https://github.com/clintbellanger/flare/wiki . However, it is far from being complete and partly obsolete; I think Clint has plans to create detailed tutorials sometime in the future, but I don't know when this will happen. In the meantime, it's probably the best to take a look at the existing Flare mods ( https://github.com/clintbellanger/flare/tree/master/mods ) to get an idea of how Flare works.
Since you would probably have to compress the files anyway, couldn't you just submit them packed into archives?
But if you really need to upload every single file separately, Bart will probably agree to allow uploading of BVH files. (It's only a simple Drupal configuration task afaik.)
Hi, here is a proposal for the logo. The png contains the actual logo, while the gif explains the idea behind the logo. I wasn't able to attach the svg source file, but I'll upload it to OGA if you are happy with the logo.
That's the copyright header for the license itself -- you may not change the GPL.
> I have noticed though that under the GPL licence terms, editing the sprites is not allowed.
Huh? Are you mixing up GPL and CC-*-ND?
> Also I'd like to say that those 2 licences are confusing.
From the FAQ:
> If you use CC-BY-SA art with other works, the resulting work must be CC-BY-SA.
I think the main question is whether including art into a game means creating a 'Collection' or an 'Adaption' (see CC-BY-SA 3.0 legal code 1.a and 1.b). IMHO game data (= art and configuration) is a 'Collection', in which case the CC-BY-SA agreement does not force you to make the whole 'Collection' CC-BY-SA.
> Games are a weird corner case.
I fully agree on this one. ;-)
> If a screenshot contains a CC-BY-SA work mixed with other works, the entire screenshot must be released CC-BY-SA.
This one is indeed a weird case. The result would probably be that, if a user takes such a screenshot, he wouldn't be able to release it at all, because he would either be breaking CC-BY-SA or the propietary license which covers the rest of the art.
> But the code license is not affected either way.
This. Taking into consideration that the code would still remain propietary, it probably wouldn't hurt a closed-source game to release all of its art under CC-BY-SA.
@proteinbeer:
I'm not a lawyer, so don't take this as legal advice (you should probably contact a real lawyer instead), but that's how I understand CC-BY-SA:
It's generaly perfectly fine to encorporate CC-BY-SA content into a closed source project (and you don't need to make all of your art or even the entire project CC-BY-SA), provided you give credit in a appropiate manner and make all modifications ('Adaptions' in the CC-BY-SA legal code) to the original content available under CC-BY-SA. There are however restrictions:
The first one may be incompatible with the App Store's Terms and Conditions (I didn't dig into these terms, so that's just an assumption) and the second one is clearly incompatible with any form of DRM. It might be possible to solve these incompatibilites by publishing the CC-BY-SA content and any Adaption of this content on your projects website, but again, I'm not a lawyer, so this might or might not be true.
EDIT: When I started my response, Clint did not have responded yet.
This is just great - you should defitinitly continue doing such experiments :)
@Anonymous:
There is some documentation at https://github.com/clintbellanger/flare/wiki . However, it is far from being complete and partly obsolete; I think Clint has plans to create detailed tutorials sometime in the future, but I don't know when this will happen. In the meantime, it's probably the best to take a look at the existing Flare mods ( https://github.com/clintbellanger/flare/tree/master/mods ) to get an idea of how Flare works.
Hey, nice style :) .
Since you would probably have to compress the files anyway, couldn't you just submit them packed into archives?
But if you really need to upload every single file separately, Bart will probably agree to allow uploading of BVH files. (It's only a simple Drupal configuration task afaik.)
I've changed your license to CC-BY-SA, because you can't downgrade stuff from CC-BY-SA to CC-BY.
Hi, here is a proposal for the logo. The png contains the actual logo, while the gif explains the idea behind the logo. I wasn't able to attach the svg source file, but I'll upload it to OGA if you are happy with the logo.
Pages