I had a nice conversation these days and I was pointed to persony.com as a reference of a well done Conferencing Solution … like *hey lets see how persony.com has done it*.
Actually looks quite nice indeed but I was curious how their screen sharing work and clicked on it. Et voila looks like they changed the buttons of the OpenMeetings Screen Sharing Client and used it.
Well I don’t mind at all but it would be nice if they could contributed something back instead of using it in their “number one get everything we make the next super generation” application and yes actually I do mind ggg
But lets compare them in depth
persony.com Screen Sharing:
and if you read through the usage of LGPL:
AFAIK, GPL implies that any application which modifies or even links to GPLed libraries will have to make that application GPLed too. Whereas, what LGPL states is that applications can link to LGPLed libraries and remain closed source, however, If they do modify the LGPLed library itself, they will have to show the modifications made to the library.
so from my point of view persony.com is forced to make the source code modification public.
the same is written on:
From my point of view this IS a LGPL violation. (this is my opinion ^^ do it yourself)
I am wondering what their other part is looking like if they say *I tightly integration into your invironment* they mean a Web-Service Gateway ggg