The "can NOT re-distribute" stipulation is not enforceable under CC0. There are no licenses accepted on OGA that prevent someone from redistributing the assets. I get why you would want that, but even in proprietary licenses it unintentionally makes using the assets extremely legally complicated. Would you be willing to forego that stipulation here? They're your assets and your choice how you want to share these, but in the meantime I have to mark these as having a licensing issue to protect your wishes.
I can't speak to youtube policy or their stance on various religions. However, I should caution you on the content you post here. Nothing you have said on OGA is against the rules, but it has gotten close.
OGA has no opinion on the politics of the Palestinian resistance movement, Islam, Judaism, or any other religion. However, the policies here do forbid discussion of politics and religion. Any religion, any politics. I have not addressed this thread earlier because the discussion of religion and politics have been (barely) within the bounds of discussing a game concerning those things, and not the discussion of those things themselves.
Promoting and discussing your game is fine, even one who's theme concerns religious and political concepts. Discussing the politics and religious biases of media platforms is getting dangerously close to violating the site's rules. As is the discussion of religion or politics not specifically in the context of game content. Even if it is friendly discussion and polite greetings.
Thank you for your understanding. Carry on. :) and please let me know if you have any questions.
I agree. I freaking hate how complicated licensing makes things.
Ok, I can get behind that interpretation of term 5. And I can respect the spirit of your desires for this asset.
My job is to make sure developers can use assets without worrying about violating licensing terms. If the terms are not clear, I haven't done my job. We can look into adding OFL to our list of licenses. In the meantime, the assets must be compatible with the licenses we accept. It looks like that's the case, but when the page says CC-BY, but the file says OFL, it tends to make developers worried. As long as it's clear people can use either license when they look at the file(s), then it should be fine. EDIT: you have made this adjustment already. :)
Since you want them to be able to quickly drop the package into their project without having to shuffle files around, what about having two zip files available here? one with the OFL, one with CC-BY? EDIT: Having both the CC-BY.txt and OFL.txt like you have now is fine, just wondering if you prefer two zip files with separate licenses?
Sorry for the huge wall of text, but you should know, one of the main reasons we don't already have OFL in our list of accepted licenses is because of the "no resale" stipulation. That doesn't mean we want others to profit off of your generosity. We don't accept licenses that forbid resale because it creates legal conflicts. For commercial projects especially, but free and open source projects as well. Developers will avoid anything with a "no resale" clause even when they have no intention of reselling that asset. This is because "resale" can attach to the game itself, even if the asset used by the game is free. Or if the game is free - and it is hosted on steam, itch, or any other game hosting platform with ads - that game generates revenue for the site via increased traffic and ad revenue. This could legally make the developer liable for "sales" based on assets that forbid sales. I know that is not what you're concerned about and not something you would ever go after someone for. I just want you to be aware that
1) We insist on assets here using one of the Free-Software-Foundation-approved licenses, and
2) All of those licenses allow people to try* resale of assets.
*That being said, it's generally pretty difficult for someone to successfully re-sell your free assets under CC-BY. They're required to credit you and link back to this page, so any "customer" of theirs would see that attribution, visit this page, and see it is available for free. Why would they bother paying someone when it's obviously free here? The license still allows them to try, though. :P
@Basto: Oh dear, you're right. Thank you for pointing that out.
However, the first revision is not shown by default, so I'm hoping that is acceptable? If this is still an issue, Technopeasant, let me know.
Nice! Would you be willing to include a copy of CC-BY in the zip file as well? or indicate in the LanaPixel_License.txt that users may choose either license? Otherwise it looks like the LanaPixel license is contradicting the CC-BY license.
EDIT: hmm... The 5th term of the SOFL may actually contradict the CC-BY license. If SOFL forbids this font being distributed under any other license, then it can't be distributed under CC-BY as well. Any thoughts?
No problem. :) I didn't mean to sound angry. I wasn't. That big wall of text was meant to explain, not chastise.
Those stipulations suggested by your friend are fairly common, but often either legally unenforceable or they make the assets unusable. Of course they're meant to promote freedom, but they unintentionally cause legal conflicts where any game that used them would be in violation even when the game is free and open source.
I can explain why if you would like to know, but these are all good, so I'll stop typing. Thanks for sharing these. Looking forward to seeing more of your work!
Pretty solid. Only a few with detectable repeating patterns.
What are these licensed as? I'm guessing they can't be any form of creative commons if the images are from "all over the internet"?
@ansimuz: EDIT: Thanks!
would you be willing to adjust the public-license.txt inside the .zip to match?Another great ansimuz set!
The "can NOT re-distribute" stipulation is not enforceable under CC0. There are no licenses accepted on OGA that prevent someone from redistributing the assets. I get why you would want that, but even in proprietary licenses it unintentionally makes using the assets extremely legally complicated. Would you be willing to forego that stipulation here? They're your assets and your choice how you want to share these, but in the meantime I have to mark these as having a licensing issue to protect your wishes.I can't speak to youtube policy or their stance on various religions. However, I should caution you on the content you post here. Nothing you have said on OGA is against the rules, but it has gotten close.
OGA has no opinion on the politics of the Palestinian resistance movement, Islam, Judaism, or any other religion. However, the policies here do forbid discussion of politics and religion. Any religion, any politics. I have not addressed this thread earlier because the discussion of religion and politics have been (barely) within the bounds of discussing a game concerning those things, and not the discussion of those things themselves.
Promoting and discussing your game is fine, even one who's theme concerns religious and political concepts. Discussing the politics and religious biases of media platforms is getting dangerously close to violating the site's rules. As is the discussion of religion or politics not specifically in the context of game content. Even if it is friendly discussion and polite greetings.
Thank you for your understanding. Carry on. :) and please let me know if you have any questions.
are there two different crossbow sheets? or is this just an update to the WIP version?
Good to know. Thanks again! :)
I agree. I freaking hate how complicated licensing makes things.
Ok, I can get behind that interpretation of term 5. And I can respect the spirit of your desires for this asset.
My job is to make sure developers can use assets without worrying about violating licensing terms. If the terms are not clear, I haven't done my job. We can look into adding OFL to our list of licenses.
In the meantime, the assets must be compatible with the licenses we accept. It looks like that's the case, but when the page says CC-BY, but the file says OFL, it tends to make developers worried.As long as it's clear people can use either license when they look at the file(s), then it should be fine. EDIT: you have made this adjustment already. :)Since you want them to be able to quickly drop the package into their project without having to shuffle files around, what about having two zip files available here? one with the OFL, one with CC-BY? EDIT: Having both the CC-BY.txt and OFL.txt like you have now is fine, just wondering if you prefer two zip files with separate licenses?
Sorry for the huge wall of text, but you should know, one of the main reasons we don't already have OFL in our list of accepted licenses is because of the "no resale" stipulation. That doesn't mean we want others to profit off of your generosity. We don't accept licenses that forbid resale because it creates legal conflicts. For commercial projects especially, but free and open source projects as well. Developers will avoid anything with a "no resale" clause even when they have no intention of reselling that asset. This is because "resale" can attach to the game itself, even if the asset used by the game is free. Or if the game is free - and it is hosted on steam, itch, or any other game hosting platform with ads - that game generates revenue for the site via increased traffic and ad revenue. This could legally make the developer liable for "sales" based on assets that forbid sales. I know that is not what you're concerned about and not something you would ever go after someone for. I just want you to be aware that
1) We insist on assets here using one of the Free-Software-Foundation-approved licenses, and
2) All of those licenses allow people to try* resale of assets.
*That being said, it's generally pretty difficult for someone to successfully re-sell your free assets under CC-BY. They're required to credit you and link back to this page, so any "customer" of theirs would see that attribution, visit this page, and see it is available for free. Why would they bother paying someone when it's obviously free here? The license still allows them to try, though. :P
@Basto: Oh dear, you're right. Thank you for pointing that out.
However, the first revision is not shown by default, so I'm hoping that is acceptable? If this is still an issue, Technopeasant, let me know.
Nice!
Would you be willing to include a copy of CC-BY in the zip file as well? or indicate in the LanaPixel_License.txt that users may choose either license? Otherwise it looks like the LanaPixel license is contradicting the CC-BY license.EDIT: hmm... The 5th term of the SOFL may actually contradict the CC-BY license. If SOFL forbids this font being distributed under any other license, then it can't be distributed under CC-BY as well. Any thoughts?EDIT2: Fixed, thanks! :)
No problem. :) I didn't mean to sound angry. I wasn't. That big wall of text was meant to explain, not chastise.
Those stipulations suggested by your friend are fairly common, but often either legally unenforceable or they make the assets unusable. Of course they're meant to promote freedom, but they unintentionally cause legal conflicts where any game that used them would be in violation even when the game is free and open source.
I can explain why if you would like to know, but these are all good, so I'll stop typing. Thanks for sharing these. Looking forward to seeing more of your work!
Pages