new skin im making

[KingArgyle]

Maybe this article will help clear things up:

http://www.sitepoint.com/article/public-...-explained

My interpretation if the only part of your program that is using GPL related items are the images, then the only thing you have to keep as GPL are the images. Your code that you wrote to process and display the images are yours. The same goes for a Company that would use Linux for their operating system, and they develop their own programs. Just because they are using Linux as the operating system doesn't mean they have to GPL their proprietary program they wrote. They can't charge for the Linux operating system, but they can charge for the program they create to run on linux.

In your case, reven, I would apply the same situation. You include in your readme where the images came from and who they are copyrighted by, and that if the images are changed then those changes have to be made available as a GPL (on the images only), but your program doesn't have to be GPLed and your source code doesn't have to be released. Since you didn't modify the images, but just used them, then you are safe from having to release your source code, and your app doesn't have to be GPLed.

[jquinlan]

Reven, just release it with the default blue skin to keep it safe, and if someone uses a GPL image and changes the skin your plugin uses then you can not be held responsable. If so, this example could cause GB-PVR to be held responsable for the loading of GPL images when the Sub never included them.

The skin should be considered separate because the plugin does not require it to function, its a user selectable option and the author can not be held responsable what they select or make. The images and XML code are the components that make up the skin so those would fall under the GPL license.