What is the ideal one for ?

For example if I create a python script that generates imagery in one form or another and I want to both be able to share that code for others to improve, modify or whatnot and also to be able to sell prints of the outputs, what license would one choose for the script?

Would need to know more, but what the software produces is not covered by the license, at least not if you use regular known FLOSS licenses. Say you GPL your software source code, nothing prevents you to sell what is generated with it (and nothing prevents others to do so as well). But maybe you mean something else?

@kurbitur I tend to like permissive licenses like MIT/BSD:

More recently, I've become fond of putting stuff in the public domain and/or using the unlicense. The philosophy vibes with me:

Generated images/content should be placed under a different license. Creative commons 0 (CC0) is the most permissive (essentially public domain):

Thank you!
So if I understand correctly I could license the script under BSD-2 but the output of the script under CC0?

@kurbitur regular GPL would work fine if you want the code to be share-alike. The terms of reciprocity don't apply to applications of the software (creative or otherwise). That's why people can sell works made in GNU IMP etc.

@kurbitur Do you want to limit what people can do with the output of the code or who can use it for what?

@KnowPresent I mean it would be nice to have some clause so people can't just take my code, start printing the outcomes and profiting without any input (Would anyone do that?). But at the same time that could probably impose all sort of annoying restrictions and the whole notion of me being the only one to be able to profit can come off weird.

@kurbitur If you can accept that somebody somewhere (Jeff Koons perhaps?) might make a ton of money putting your stuff on overpriced handbags, then just go with a AGPL/GPL-3 or similar share-alike license. Those kinds of clauses usually don't work or hold up legally.

@KnowPresent Yeah that was what I thought. @paul also mentioned I could license the output under a different license but I think if Jeff Koons wants to make a ton of money off it somewhere then a license is probably not going to stop him. I mean there is a bunch of cases of Zara and Urban Outfitters stealing art from small artists and selling it as their own and that is not even open source art.

I think there was a case a bit similar, but forgot the details, where Alexei Shulgin was accused to sell video art sculptures that were using parts of the GPLed effect tv filters from Kentaro Fukuchi. Maybe @h220 remembers? Another relevant situation was Scott Draves' electric sheep, GPL and all, but he was also able to generate and I think sell or exhibit hi-res versions, maybe using a modified version. But basically your options are: 1. Make your own non-free license that restricts some usage, 2. Only publish part of the software under GPL and don't release a module that could facilitate the production of what you think is financially valuable, 3. Keep the latest version private, only publish it when you have exhausted it or are bored with it (this strategy was used by some Pd devs who were also making some living from performing with their software). Anyway, regardless of how you proceed, if it's worth appropriating/monetising, it will be appropriated/monetised (see the whole ML based so-called AI art that sold for gazillions petrodollars, forgot the name of the collective involved but it involves quite intense discussion on this matter and the use of GPL in art, by artists, making use of other artists tools, making use of other people ML frameworks, and lots of feels, many many feels).

@kurbitur BSD, MIT, or X11. Or Apache if you really like long licenses that resolve to mostly the same rights. You can do it with GPL & an exemption waiver of the output like Linux uses, but it's a legal grey area.

@kurbitur You could have your art program under GPL and still sell whatever artwork is produced by it. The license only applies to the code, not the data which it produces (in this case images).

I've written a couple of programs like that: Paintatron and Hypercollage.

Sign in to participate in the conversation

Welcome to, an instance for discussions around cultural freedom, experimental, new media art, net and computational culture, and things like that.