From Project JEDI Wiki
If you have any comments or questions about licensing, please let us know.
 MPL License
The JEDI Libraries are licensed under the Mozilla Public License ("MPL") version 1.1.
Mozilla is the Open Source initiative formulated by Netscape for the next generation of their web browsers. Netscape states "We believe this license satisfies the Debian Free Software Guidelines which provide a commonly accepted definition of 'free software', much like other free software licenses such as GPL or BSD."
JEDI's implementation of the MPL allows developers to use its code in their applications ("Larger Work") regardless of whether the intended distribution will be in the public domain or as commercial applications, as long as the licence conditions are met. For a more detailed explanation, an annotated version of the MPL is available.
 License FAQ
For additional information, please also check the official FAQ from Mozilla.
 Author perspective
Q Do I retain copyright once I publish source under the MPL?
Q Can I release the code under a different (possibly commercial type) license?
Q In two years Acme, Inc. comes with a great new license, which I would love to use. Am I always bound to MPL for my released code?
Q I've contributed code to JEDI under MPL, but now I've changed my mind and don't want this code to be OpenSource.
Q I think, JEDI could benefit from having cryptographic functions. I would like to donate some (DES, Tripple DES etc.), which are covered by patent rights (RSA, for example)? How should I do it?
 User perspective
Q Can I use the MPL code in commercial software? If yes, am I obligated to credit the author?
Q Must I release the source code of used components?
Q Must I publish my apps under MPL if I used MPL licensed code (the viral aspect)
Q If a bug in MPL licensed code renders my clients machine unbootable, who can I hold responsible for that?
Q Must I publish modifications to MPL licensed code?
Q Must I publish code based on MPL licensed code under MPL?
Q If I subclass the MPL code, do I still have to publish the new code? After all I didn't modify the code at all!
Q I am proposing a modification to a JEDI-VCL component, which has a dual license (MPL and GPL). This new file also needs to include a new class. Should the source files for the new class be put in JEDI-VCL using MPL with GPL dual-license or can it be put in another location and use only the MPL?
 Case study
I am considering using an XML parser that has being covered by the MPL v1.1 (or alternatively the GPL) in a commercial product. I will simply use the DLL libraries without modification, including the necessary header files in my own code. When I distribute (sell) my own product I would, of course, need to distribute the DLL libraries as well. My questions are:
Q Am I correct in assuming that simply including unmodified header files and linking with a library covered by the MPL does not place any legal restrictions or obligations on my commercial product and its source code?
Q Am I obligated to distribute the (unmodified) source code that produced the libraries with which I link?
Q Am I obligated to make my use of the particular libraries known to users of my product?
Q We are using JEDI Libraries in our products. We did not modify the source codes in any way. Can some one please tell me if we need to add a Copyright statement in our product's license text and if so, which text is required?