Skip to main content
edited tags
Link
feetwet
  • 22.1k
  • 13
  • 87
  • 185
Bumped by Community user
Source Link

Does AGPL apply to products created by the software, or just the software?

I'm a 3D modeler by trade, and in the past I've used some software to create a base mesh for humanoid renders. I'm seeing now that, while it used to be AGPL and CC0, it's now entirely AGPL, and by some mechanism which I do not fully understand this seems to apply to products and meshes created with it.

That is, if I produce a model while using this software, I am required to release the model, and any software dependent on the model (say, a game or a web app), under the same license. This feels extraordinarily aggressive.

This is very strange to me. It feels like a paintbrush manufacturer demanding royalties on all paintings done with their brush. Additionally, when AGPL was created, it was apparently to close a gap in GPLv3 which allowed companies to alter software on a server and open it to the public via a web interface; which was phrased loosely enough to potentially apply to all products created by the program.

While I'm historically a big fan of GPL-created works and feel that they have done wonders for the whole of the software and multimedia community, this AGPL oddity is a total deal-breaker for the software-in-question. I'm no longer even entirely certain about my rights to my videos. What is the nature of this reach? Do I need to make my application AGPL simply because I used an AGPL-produced resource in it? And, perhaps most importantly, has this ever been enforced in a court of law, or could it be in the United States?