Development of Creative Commons licenses

[Arne Babenhauserheide <arne_bab AT web.de>]

Am Mittwoch, 7. Mai 2014, 18:41:34 schrieb Anthony:
> What specifically are the problems with applying the GPL to graphical art?

You have to provide the sources you actually use for editing. In my case 
these are gimp-files which can easily require 30 MiB of diskspace for a 300 
KiB image file.

You can’t just upload a low-res version to your website, if you actually use 
the high-res version to do changes: You have to provide the high-res version.

Where do you upload non-released versions? How many artists add a “how to get 
the sources”-section to their sites? Would you add a source-link to a 
postcard?

> How will these problems be solved by someone who wants to incorporate
> CC-BY-SA graphical art in a GPL work?

If you have a GPL-project you already have all the required infrastructure in 
place.

> Versioned dependencies, build systems, asset-repositories....do these apply
> to graphical art?

Jepp: Old versions of the images in your version tracking system (for smaller 
ones) or in your public source-releases and a versioned build system which 
references the actual images you used, or in the case of scribus a 
text-format design-file with that information.

Since you will do a source-release anyway, you only need to add the high-res 
images to that.

I for example keep most images, fonts and so forth in version tracking¹ 
except for the few where I actually use the huge gimp-files or photo-raws. 
Those huge files are released in the releases-folder² and the date in version 
tracking shows which file was used.

¹: http://bitbucket.org/ArneBab/1w6
²: http://1w6.org/releases

If you have a project which requires the GPL, you already use tools which 
distinguish clearly between source and product.

Best wishes,
Arne
-- 
1w6 sie zu achten,
sie alle zu finden,
in Spiele zu leiten
und sacht zu verbinden.
→ http://1w6.org