>From what I understood a plugin cannot be licensed under the Apache License if it uses API calls of a GPL licensed product.
The trademark issue might be another hurdle to tackle but first we are concerned about licensing the code. So my question might be misunderstood, the question is really "Can we license the code and release under the Apache License" not about the name of the plugin or how we are using the 3th party product names in our project. Sebastian 2012/8/15 Daniel Shahaf <[email protected]>: > [email protected] wrote on Wed, Aug 15, 2012 at 10:45:36 +0200: >> Dear Legal Team, >> >> our podling "Apache OpenMeetings" maintains a number of plugins to >> integrate OpenMeetings into several LMS and CMS and other 3th party >> products. >> >> The questions is if we can release those plugins at the ASF as >> "apache-openmeetings-plugin_xyz". >> >> All plugins have in common: They call API methods of the system they >> integrate as well as the system they are integrated into calls methods >> in the plugin and expects the plugin to have a certain structure. > > This may depend on the other system's trademarks policy? eg for ASF > products, we place less requirements on the code-level symbol names and > more requirements on the user-facing product name; ask trademarks@ > (private list) for details. -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
