The Mozilla Public License 1.1 (MPL 1.1) is an open source license established by Mozilla, created to balance the interests of the collaborative and commercial development worlds. It allows software distributors to combine and distribute code with other (proprietary) software, as long as the MPL-covered code remains accessible. Understanding whether MPL 1.1 can be used in a commercial application depends on several factors outlined under the terms of the license itself.

MPL 1.1 License Overview

MPL 1.1 governs the use, modification, and distribution of the covered code. Under this license, anyone is free to use and distribute the software or derivative works, whether modified or unmodified, as long as the terms of MPL are maintained. One critical aspect of MPL is that it is a "weak copyleft" license. Unlike strong copyleft licenses (such as the GPL), which require the entire software to be released under the same license, MPL only requires the files containing MPL-licensed code to remain under MPL.

Key Aspects of Using MPL 1.1 in Commercial Applications

1. Source Code Requirements

When you distribute MPL-covered software in an executable form, you must also make the source code of the MPL-covered parts available under the MPL. This doesn’t affect the proprietary files, which can be distributed under different, possibly non-open source terms.

2. File-Level Copyleft

The copyleft of the MPL applies on a file-by-file basis. This means that if a file is modified, the modified file must be released under the MPL. However, new files created in the program that do not contain any MPL-covered code can be licensed under a different license, including commercial ones.

3. Distribution of Derivative Works

If you modify MPL-covered code, you must distribute the entire source code of the modified files under MPL, whether or not you distribute the software commercially.

4. Compatibility with Other Licenses

It is essential to ensure that the use of MPL 1.1-compatible code does not conflict with the licensing requirements of any other code you intend to use or distribute in your app. While MPL is relatively flexible, it is not compatible with some strong copyleft licenses.

Technical Implementation Example

For example, if you are developing a mobile application and decide to use an MPL 1.1 licensed library for handling network communications, you need to observe MPL's conditions only for the parts of your application using this library. Suppose your application is structured into multiple modules, and only one module uses this MPL-covered library. In that case, you only need to disclose the source code for this particular module when you distribute your application, not the entire application.

Practical Considerations in Commercial Deployment

When using MPL 1.1 licensed components in your commercial software, it’s crucial to keep detailed track of which parts of your software use open-source code. This tracking helps in fulfilling the requirement of making the modified source code available when distributing the application.

Summary Table of MPL 1.1 Characteristics

Conclusion

In summary, yes, it is entirely possible to use the MPL 1.1 in a commercial application. However, it demands careful management of which components are MPL-covered and ensuring compliance with the source code distribution requirements for any changes to these components. It's often advisable to consult with a legal expert in open source licensing to ensure full compliance and strategically manage intellectual property issues in commercial product development.