4 ms·
I would interpret this for this scenario as "If you make (reasonably original) graphics for a theme, you do not need to release the graphics as GPLv2 if you rel
by strictfp 15y ago
I would interpret this for this scenario as "If you make (reasonably original) graphics for a theme, you do not need to release the graphics as GPLv2 if you release the graphics standalone. If you, however, release the graphics as a part of the theme, you need to put the graphics under GPLv2 aswell".
The mail quoted at http://wordpress.org/news/2009/07/themes-are-gpl-too/ http://wordpress.org/news/2009/07/themes-are-gpl-too/ classified the images and css as standalone works. They then concluded that the standalone works did not fall under GPL2. But the excerpt in the parent seems to state that these actually must be GPLv2:ed if bundled with the derivative work, no?
So my interpretation is that the disclaimer is in conflict with the licence, since the licence actually requires you to GPLv2 standalone work when bundling with derivative.
(IANAL)
- pmjordan 15y agoYeah, I don't know; Linux distributions bundle GPL software with non-GPL software. That doesn't make the non-GPL parts suddenly fall under GPL. In practice you're probably fine if you offer the GPL parts for free separately as well. Certainly, if the copyright holders of the original work openly state they don't consider third-party images and CSS to be included in the license, then I think they would have a hard time arguing the opposite in court.