GNU GPL Plugins, Copyright & You GNU GPL, who are they? What are they? Quiz Multi-Choice Quiz: GNU GPL is: a. GNU GPL is the coolest band in the last decade. b. The sound made by a Large Beaked Yellow Breasted Flightless Bird found in the Amazon Rain forest along the Rio Negro. c. GNU's Not Unix General Public License” From their site: The GNU Project was launched in 1984 to develop the GNU system. The name “GNU” is a recursive acronym for “GNU's Not Unix!”. "GNU" is pronounced g'noo, as one syllable, like saying "grew" but replacing the r with n. What does “GPL” stand for? “GPL” stands for “General Public License”. The most widespread such license is the GNU General Public License, or GNU GPL for short. This can be further shortened to “GPL”, when it is understood that the GNU GPL is the one intended. How does it apply to plugins? Go to Buzztouch's FAQ's and you find this entry: "Can I sell an app I create at buzztouch.com? Sure. Download the source code, compile it, sell the heck out of it! The project source is licensed under a GNU, General Public License. The software is Open Source. As long as you follow the provisions outlined in the license text, you can do whatever you want with your project." What does that mean? Actually it means a lot. Does it mean the plugins are not copyrighted? No, they are by default, all software is automatically copyrighted. Buzztouch is released under the GNU GPL. Buzztouch has a copyright to the code found in the plugins. Does that mean I have to get permission to use the code to create a new plugin? No, you have permission, it's in the license. Does that mean I can't sell the plugin? No, you can sell the plugin anywhere you wish for any price you wish Does that mean I can't copyright the new plugin? No, by law the plugin is automatically copyrighted when you first publish the new plugin. It's copyrighted even if you don't use the © symbol. OK, so that means that I can copyright the plugin and no one can use it without my permission, right? No, the GNU GPL license used in the plugins says among other things: a. You will grant a GNU GPL license to anyone to reuse your code. So, if you use (modify) a plugin to create a new plugin you should/must grant a GNU GPL so others can modify and/or use the plugin. If you write the plugin from scratch you can copyright the plugin and not be required to grant the GNU GPL. OK, so that means that if someone use my plugin they don't have to pay me. Isn't that stealing. Isn't it wrong. Yes & No, Well maybe. Yes they can use it without paying. No it's not stealing, because when you used the existing plugin code you agreed that others can use your code. Fair is fair, correct? So, I could modify the plugin, create a new plugin and just never release it and then no one could use it. Yes, that's correct, but what would be the fun in that. When I create (modify) a new plugin should I leave the copyright untouched. This its a difficult question. a. If you're just making a few minor modifications, you should but you should note the modifications so users know whom to blame and seek support from. b. If you're making a totally different plugin you should copyright the plugin as your own, but give credit to the prior copyright holders. If you making just a few modifications don't pass the modified plugin as the original, since it's not. If your "just a few minor changes" plugin has flaws or bugs then the copyright holder of the original plugin could be blamed and you would be responsible. Whether they sue you or not, you'll be doing them wrong. For additional resources in understanding copyright law go to www.MySkylla.com and click on the copyright button. Fred

Great post! I'll add a bit to this as we near the Plugin Market announcement. When you use the Plugin Creator tool, the standard license text that comes with source code delivered with the plugin is GNU, the same license text that we use on all our work at buzztouch. However, this does not mean you have to leave this license text. Because we're adding it by default does not mean you have to use it. However, if you plan to use the Plugin Market to sell or share any plugins you create, you can expect this to be the required license. We've gone round and round on this for awhile but have decided that if you're going to use the buzztouch.com market to distribute your software, you'll be expected to release it under the GNU license. The logic behind this decision is obvious. Because buzztouch delivers project packages to app owners in plain text, and because plugin packages are very commonly "hacked up" or modified, it's logical that there would not be any confusing issues around the license. Imagine how much support would be necessary if a user used a plugin that was "not allowed to be modified." Ugh. This doesn't mean you have to use the buzztouch Plugin Market and it doesn't mean that anything you create will suddenly become free to all to use. It simply means that if you CHOOSE to sell or share you plugin we will require you to release it under the GNU license so everyone understands the process. Lastly: Before you release a plugin in the Plugin Market you'll be asked to read and understand and agree to an buzztouch Developer Agreement drafted by us. It wil be simple, transparent, easy to understand agreement and shouldn't be too intimidating. Miles shorts of the Apple Developer Agreement!

:-)

Great Post! @David www.jimmyscafe.com dinner still on me when you make it to Saint Louis...

great explanation thanks fred and david

great post!

Very nice!!! Best Regards, Danny

@MAGIC_MAN: Dont' be surprised if I surprise you. I'm SO taking you up on this at some point ;-)