> Thanks for taking your time to answer my question. Let me clarify a > bit here. The plugin that I am going to modify will be released under > GPL license. There are two parts an application and the plugin. The > application will connect to these plugins. So we would be developing > the application from the scratch and the plugin would be an > improvement from the existing work which we are going to release in > GPL. >
How does your application talk to the plugin ? Is it over web service (or) some other protocol (or) some other way ? If the communication method is one of the standards (such as HTTP 1.1) then you should be okay with releasing source only for the modified plugin. But if the communication method is GPL licensed then, i am not sure, you need to dig into the license to see if your application is considered derived as per GPL. Also, there is a lot difference between GPLv2 and GPLv3. What license does the plugin come under ? GPLv2 is far more relaxed, even when it comes to contributing back to the community. > So just releasing the plugin in GPL would solve it rite? The > application codes can remain our company property? > Seems to be so but no one can say for sure without the details. -- 0 _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
