Skip to main content

User login

What is OpenID?
  • Log in using OpenID
  • Cancel OpenID login
  • Create new account
  • Request new password
Register
  • Home
  • Browse
    • 2D Art
    • 3D Art
    • Concept Art
    • Textures
    • Music
    • Sound Effects
    • Documents
    • Featured Tutorials
  • Submit Art
  • Collect
    • My Collections
    • Art Collections
  • Forums
  • FAQ
  • Leaderboards
    • All Time
      • Total Points
      • Comments
      • Favorites (All)
      • Favorites (2D)
      • Favorites (3D)
      • Favorites (Concept Art)
      • Favorites (Music)
      • Favorites (Sound)
      • Favorites (Textures)
    • Weekly
      • Total Points
      • Comments
      • Favorites (All)
      • Favorites (2D)
      • Favorites (3D)
      • Favorites (Concept Art)
      • Favorites (Music)
      • Favorites (Sound)
      • Favorites (Textures)
  • ❤ Donate
Game Design

Licensing Question

ImpossibleRealms
Wednesday, January 4, 2017 - 16:54
ImpossibleRealms's picture

I figured I'd post this in the Game Design section, as it applies to both programming and art, and I'm not sure which section it would go into. I've been curious for a while as to what a GPL license means for artwork. For coding, I believe a GPL license means that all new code must be licensed under GPL or another compatible license (i.e. something more permissive such as BSD or even public domain), but when using source code that is licensed under GPL, what does this mean for artwork? Must the artwork also be licensed under GPL, or does the GPL license only apply to the code? If the latter, does this mean that the artwork could be under a completely proprietary license? I mostly ask just because I'm curious as to the relation between the two, as I actually haven't seen very much discussion on this.

  • Log in or register to post comments
MedicineStorm
joined 12 years 8 months ago
Wednesday, January 4, 2017 - 21:33
MedicineStorm's picture

"...I actually haven't seen very much discussion on this."

...Really? I think there's been a lot of discussion on this. Nothing was ever truly concluded on the topic, though. Here are some stuff on GPL as it relates to art: 

http://opengameart.org/content/faq#q-ccgplcompat 

"...the Free Software Foundation has clarified that the game code and game media are separate entities and do not need to be released under the same license, provided those licenses allow you to copy and redistribute the work for both commercial and non-commercial purposes..."

 

http://www.gnu.org/philosophy/free-system-distribution-guidelines.html

"Non-functional Data

Data that has an aesthetic purpose, rather than a functional one, may be included in a free system distribution as long as its license gives you permission to copy and redistribute, both for commercial and non-commercial purposes. For example, there are some game engines that have been released under the GNU GPL, and have accompanying game information "world map, game graphics, and so on" released under such a verbatim distribution license. This kind of data can be part of a free system distribution."

 

http://opengameart.org/forumtopic/source-required-for-art-licensed-under...

"...The reason the GPL is a license option at all is because there were several major projects that, at the time of OGA's creation, required their art to be licensed under the GPL (Wesnoth comes to mind, although I believe there were others), and because of the existence of legacy works from back when the GPL was the only game in town as far as licenses with a "share-alike" requirement..."

 

There is a bunch of threads in the forum talking about GPL as it relates to art, but they are usually more like blurbs mixed into a larger (and less related) licensing discussion, so it's a bit hard to wade through it all. Capbros has written a lot on the topic and he definitely understands GPL better than I do. Maybe he'll see this and give his assessment. 

TL;DR: My overly simplified summary of the issue is:

  • GPL is not the recommended license for art, but there are legacy reasons for maintaining it as an art license.
  • GPL'd art doesn't neccessarily mean the code must be GPL as well. Art and code in a single project may be licensed separately as independent "collections". However, each project is subject to unique circumstances. Consult your lawyer if swelling persists longer than 4 hours.
  • If you're submitting GPL artwork, it is preferable (and polite) that a highly-editable format of the art be included along with a more finialized form. E.g. include a photoshop PSD file (or gimp XCF file) along with a PNG or JPG image of artwork, so other users may modify the image easily. Whether or not this is required in order to be compliant with the GPL is unlikely/debatable, but still a good idea.

Hope that helps some :)

--Medicine Storm

 

  • Log in or register to post comments
withthelove
joined 11 years 4 months ago
Thursday, January 5, 2017 - 05:21
withthelove's picture

'. For coding, I believe a GPL license means that all new code must be licensed under GPL or another compatible license (i.e. something more permissive such as BSD or even public domain), 

absolutely not.  Derivatives of GPL code must be released as GPL period.   There's no provision for releasing derivatives under 'compatible' licenses.  Otherwise you could trivially flip something from GPL to CC0 and then to a private/closed source license.

As for art, MedicineStorm pretty much summed it up as far as my research has taken me.   To be honest, I can say I've studied what GPL means for artwork some but I wouldn't really say I understand it much.   My general take is that the license wasn't written for artwork and therefore shouldn't be used for it (this is the reason for the CC folks getting started).  But people do release art under GPL and the FSF does seem to have an idea that the license can work for art, so clearly there's more for me to learn on the topic.

https://withthelove.itch.io/

  • Log in or register to post comments
ImpossibleRealms
joined 12 years 5 months ago
Thursday, January 5, 2017 - 07:20
ImpossibleRealms's picture

Alright, thanks for the info. It's actually kinda funny you mentioned CC0 specifically, since I'm personally a pretty big fan of the public domain (and I tend to prefer to release things I won't be using anymore to the public domain, or occasionally something only marginally more restrictive like CC-BY), and admittedly it's a shame that I wouldn't be able to release any new code under the license if I contributed to a GPL codebase, but I suppose it's understandable given the goals of GNU and the GPL.

I am glad that I could potentially release artwork contributed to a GPL project under CC0, as that was my primary concern if I were to do so. If I submitted such artwork here, would I have to dual-license under GPL, or would leaving the artwork as CC0 be sufficient?

  • Log in or register to post comments
MedicineStorm
joined 12 years 8 months ago
Thursday, January 5, 2017 - 07:23
MedicineStorm's picture

CC0 would be sufficient... wait. The artwork being submitted is from a GPL project? If the artwork is already GPL and you don't have authority to change the license (you're not the artist) then it should stay GPL.

--Medicine Storm

 

  • Log in or register to post comments
ImpossibleRealms
joined 12 years 5 months ago
Thursday, January 5, 2017 - 07:30
ImpossibleRealms's picture

No, there is no artwork (yet), I was specifically asking for if I were to make artwork to be used for a GPL project. Would my ownership of said art as the person who made it allow me to release that art under CC0?

  • Log in or register to post comments
MedicineStorm
joined 12 years 8 months ago
Thursday, January 5, 2017 - 07:34
MedicineStorm's picture

Ah. Yes. As the author of such artwork, you are free to release the artwork under any number of licenses you want. GPL over there, CC0 over here.

CC0 would be sufficient to cover all future bases. People coming here can use your CC0 art in a GPL project, a CC-BY-SA project, or a closed source commercial project. :)

--Medicine Storm

 

  • Log in or register to post comments