LGPL waiver Source Code Requirement - Let's Chat About It! - Gizmox | the enterprise > HTML5 platform for native-quality user interfaces

.net html5 web/cloud/mobile app delivery

| Downloads | Solutions | Store | Contact us

Search Forum Home

Forum General Visual ... Let's Chat Abou... LGPL waiver Source Code Requirement

4/24/2012 8:52 PM

	victorlo
5 posts

Re: LGPL waiver Source Code Requirement

Thanks God, I find this one in FAQ:

Q: Do I always have to pay for OEM / SaaS license agreement if I commercially distribute my named application? click to expand

A: No, if the Visual WebGui product you use is licensed with LGPL license, you may embed VWG open source as you got it, leave Visual WebGui LGPL waiver on your UI, and comply with the rest of the LGPL terms. In this case you do not need to pay.

Is it means that if we shows LGPL Waiver in the Software Product developed by VWG Pro, we can commerially distribute the named application (> 5 organizations) and do not need to pay for the OEM/SaaS license agreement?

Best Regards,

Victor

4/26/2012 4:29 PM

	palli
14313 posts

Re: LGPL waiver Source Code Requirement

Hi Victor,

I apologize. Half way through writing my reply I lost the fact that you were talking about "LGPL Waiver Visible" at all times, and started assuming that you would be removing it if you distributed your application. Sorry for that.

Seems that you have found the correct FAQ for your case, and to further support it, the first post in this thread here is very informative for licensing models. I copy/paste the last section of that post, the part that applies to your distribution model. This section applies to a named application sold to more than 5 end user organizations either deployed or as SaaS:

Gizmox provides two distribution options for OEM named application or named application offered as SaaS:

LGPL Open Source Distribution Option
You may license your OEM named application or named application offered as SaaS, with an LGPL license for VWG combined code or library. This license requires a notice to your end user organization that the application contains LGPL open source VWG library or code and that VWG is the copyright owner. Also you are required to maintain the VWG LGPL Copyright UI waiver, as it presented on VWG UI (from version 3.1.1). You may remove it only with commercial distribution option license. If you choose the LGPL open source distribution option, you may deploy the combined application freely and there is no OEM / SaaS Royalties owed to Gizmox.

Click here to distribute as LGPL (Not mandatory)
Commercial Distribution Option
Pay lump sum OEM / SaaS license fee per named application for lifetime distribution rights and license your product to your end user organization, as you choose with no restrictions. With this license you may remove the LGPL VWG waiver, and you do not have to notify your end user organization that you had embedded VWG in your product. If you choose this commercial distribution option, you will have to pay a lump sum of $5000 per named application that entitles you a lifetime royalty free deployment of the specific named application.

Click here to Purchase

Hope this clarifies,

Palli

Páll Björnsson - Visual WebGui support team - Email: support@visualwebgui.com

5/15/2012 7:49 AM

	michael
56 posts

Re: LGPL waiver Source Code Requirement

I am responding to Palli's comment "Using GPL products would require you to distribute your code also as open source".

Isn't the GPL requirement to distribute 'your code' applicable only to changes made to the visualwebgui library code? For example if I modifed some aspect of vwg itself? GPL does not usually imply that you must distribute your application specific code to anyone, at least as I understand it. In any case, as you state, GPL is not really used with the current vwg.

http://www.gnu.org/licenses/gpl-faq.html#MereAggregation

What is the difference between an “aggregate” and other kinds of “modified versions”? (#MereAggregation)

An “aggregate” consists of a number of separate programs, distributed together on the same CD-ROM or other media. The GPL permits you to create and distribute an aggregate, even when the licenses of the other software are non-free or GPL-incompatible. The only condition is that you cannot release the aggregate under a license that prohibits users from exercising rights that each program's individual license would grant them.

Where's the line between two separate programs, and one program with two parts? This is a legal question, which ultimately judges will decide. We believe that a proper criterion depends both on the mechanism of communication (exec, pipes, rpc, function calls within a shared address space, etc.) and the semantics of the communication (what kinds of information are interchanged).

If the modules are included in the same executable file, they are definitely combined in one program. If modules are designed to run linked together in a shared address space, that almost surely means combining them into one program.

By contrast, pipes, sockets and command-line arguments are communication mechanisms normally used between two separate programs. So when they are used for communication, the modules normally are separate programs. But if the semantics of the communication are intimate enough, exchanging complex internal data structures, that too could be a basis to consider the two parts as combined into a larger program.

5/16/2012 5:56 PM

	palli
14313 posts

Re: LGPL waiver Source Code Requirement

Hi Michael,

Thanks for your comments.

This section even says it's a legal question how to interpret, so no wonder I have problems with it's interpretation. Another section which I think is relevant in this case is: http://www.gnu.org/licenses/gpl-faq.html#LinkingWithGPL

Anyways, we don't have to worry about GPL at the moment, as I understand it for now.

Palli

Páll Björnsson - Visual WebGui support team - Email: support@visualwebgui.com