It would be great if you clarify your questions a bit more. As I understood, your project license in apache and you are using some plugins licensed under apache and GPL; you are also using some 3rd party components. Eventually, you wanted to release all under Apache License; how you can comply with all licenses? Was that your question?
--------- Aahit Gaba On Tue, Aug 28, 2012 at 5:10 PM, [email protected] < [email protected]> wrote: > Hi folks, > > this really seems to be a tough nut to crack. I guess lack of time > makes it difficult to answer this request. > However we would be happy if you could share your opinions about it. > > Thanks > Sebastian > > 2012/8/23 [email protected] <[email protected]>: > > Dear Legal team, > > > > I am confident we can find a solution no matter what the result will be. > > I would be happy to hear your thoughts on this! > > > > Thanks! > > Sebastian > > > > 2012/8/21 [email protected] <[email protected]>: > >> Dear Legal Team, > >> > >> is there anything else I can do to help you or any questions that > >> should be clarified upfront? > >> > >> Thanks! > >> Sebastian > >> > >> 2012/8/17 [email protected] <[email protected]>: > >>> @Legals-Team I am sorry for the last cross posting user, maybe CC'ing > >>> private list is better. > >>> > >>> Is there anything else you would like to know? > >>> From my point of view all GPL licensed product can be treated equal as > >>> they all provide the same functionality, using almost the same API > >>> calls to integrate OpenMeetings into the 3th party system. > >>> > >>> It is always the same process: > >>> 1) Verify, and read user role in the 3th party system > >>> 2) Trigger API calls to OpenMeetings to create/update/delete > conference room > >>> 3) Create session hash/token to enter conference room or recording > >>> > >>> But if you feel like each of the 3th party systems must be treated > >>> separated I can also try to prepare some graphics for each system > >>> separated that show the interaction in more details. > >>> > >>> Thanks! > >>> Sebastian > >>> > >>> 2012/8/16 German Grekhov <[email protected]>: > >>>> Teambox guys simplified so much the way of integration with their > service. > >>>> So, now there is not Javascript, but only REST calls are used in the > plugin. > >>>> > >>>> German. > >>>> > >>>> > >>>> > >>>> > >>>> 2012/8/16 Maxim Solodovnik <[email protected]> > >>>>> > >>>>> OK > >>>>> There should be Teambox "client" plugin, since AFAIK to integrate > into > >>>>> Teambox JavaScript is required. > >>>>> > >>>>> @German can you clarify it? > >>>>> > >>>>> On Thu, Aug 16, 2012 at 1:00 AM, [email protected] < > >>>>> [email protected]> wrote: > >>>>> > >>>>> > I can only see PHP files involved in the integration: > >>>>> > > >>>>> > > >>>>> > > http://svn.apache.org/repos/asf/incubator/openmeetings/trunk/plugins/teambox/ > >>>>> > > >>>>> > Sebastian > >>>>> > > >>>>> > 2012/8/15 Maxim Solodovnik <[email protected]>: > >>>>> > > I believe Teambox plugin is Javascript based also ... (but I > might be > >>>>> > wrong) > >>>>> > > > >>>>> > > > >>>>> > > On Thu, Aug 16, 2012 at 12:30 AM, [email protected] > >>>>> > > <[email protected]> wrote: > >>>>> > >> > >>>>> > >> Yes all mentioned plugins are in PHP except Zimbra plugin, > which is > >>>>> > >> pure JavaScript. > >>>>> > >> > >>>>> > >> Sebastian > >>>>> > >> > >>>>> > >> 2012/8/15 Maxim Solodovnik <[email protected]>: > >>>>> > >> > Almost all plugins are written in PHP, couple are JavaScript. > >>>>> > >> > > >>>>> > >> > > >>>>> > >> > On Thu, Aug 16, 2012 at 12:14 AM, Daniel Shahaf < > >>>>> > [email protected]> > >>>>> > >> > wrote: > >>>>> > >> >> > >>>>> > >> >> [email protected] wrote on Wed, Aug 15, 2012 at 14:32:27 > >>>>> > >> >> +0200: > >>>>> > >> >> > From what I understood a plugin cannot be licensed under > the > >>>>> > >> >> > Apache > >>>>> > >> >> > License if it uses API calls of a GPL licensed product. > >>>>> > >> >> > > >>>>> > >> >> > >>>>> > >> >> That's a generalisation and answering it as stated is a > whole new > >>>>> > >> >> can > >>>>> > >> >> of > >>>>> > >> >> worms. > >>>>> > >> >> > >>>>> > >> >> It might be useful to mention what languages the plugins > will be > >>>>> > >> >> written > >>>>> > >> >> in. > >>>>> > >> > > >>>>> > >> > > >>>>> > >> > > >>>>> > >> > > >>>>> > >> > -- > >>>>> > >> > WBR > >>>>> > >> > Maxim aka solomax > >>>>> > >> > >>>>> > >> > >>>>> > >> > >>>>> > >> -- > >>>>> > >> Sebastian Wagner > >>>>> > >> https://twitter.com/#!/dead_lock > >>>>> > >> http://www.webbase-design.de > >>>>> > >> http://www.wagner-sebastian.com > >>>>> > >> [email protected] > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > -- > >>>>> > > WBR > >>>>> > > Maxim aka solomax > >>>>> > > >>>>> > > >>>>> > > >>>>> > -- > >>>>> > Sebastian Wagner > >>>>> > https://twitter.com/#!/dead_lock > >>>>> > http://www.webbase-design.de > >>>>> > http://www.wagner-sebastian.com > >>>>> > [email protected] > >>>>> > > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> WBR > >>>>> Maxim aka solomax > >>>> > >>>> > >>> > >>> > >>> > >>> -- > >>> Sebastian Wagner > >>> https://twitter.com/#!/dead_lock > >>> http://www.webbase-design.de > >>> http://www.wagner-sebastian.com > >>> [email protected] > >> > >> > >> > >> -- > >> Sebastian Wagner > >> https://twitter.com/#!/dead_lock > >> http://www.webbase-design.de > >> http://www.wagner-sebastian.com > >> [email protected] > > > > > > > > -- > > Sebastian Wagner > > https://twitter.com/#!/dead_lock > > http://www.webbase-design.de > > http://www.wagner-sebastian.com > > [email protected] > > > > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
