Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This page needs to be reviewed

Frequently Asked Questions

This is the OpenMRS, Ltd ("OpenMRS") OpenMRS License FAQ. It aims to answer the most common questions people have about using and distributing code under MPL 2.0 + Disclaimer.

If you see any errors in this FAQ, or have suggestions for further questions, please contact OpenMRS at openmrs@openmrs.org. Note that these answers do not represent our license. The explanations are not legal advice. If you need to know exactly what the OpenMRS license requires, you need to read and understand the license itself; if you need legal advice, you need to talk to a lawyer.

I want to distribute complete and unchanged binary packages of the Original Code provided by OpenMRS. What do I have to do?

Nothing.

The binary form of the Original Code provided by OpenMRS already meet the requirements of section 3.2. You may distribute and use it under the terms of MPL 2.0.

If you are offering a warranty, however, you must make clear that it is offered by you alone (Section 3.5). OpenMRS offers no warranties on the Original Code or any other code we make available.

I want to distribute OpenMRS (or other MPL 2.0-covered code) that I have compiled myself but not changed. What do I have to do?

You must:

  • add a conspicuous notice stating where to find the exact source to the binary you are distributing (Section 3.2)
  • if your documentation has a section dealing with licensing or the recipient's rights to the code, put a copy of the MPL 2.0 + Disclaimer in it. (Section 3.5)

You may distribute any binaries you create under a license of your choosing, as long as it doesn't interfere with the recipients' right to the source under the MPL 2.0 (Section 3.2).

I want to distribute a modified version of OpenMRS (or other MPL 2.0-covered code). What do I have to do?

You must

  • add a conspicuous notice stating where to find the exact source to the binary you are distributing. (Section 3.2).
  • if your documentation has a section dealing with licensing or the recipient's rights to the code, put a copy of the MPL 2.0 + Disclaimer in it. (Section 3.5)

In addition, there are several obligations relating to your Modifications. You must

  • have the right to distribute your Modifications (Section 3.1)
  • add a correctly-completed license header to any new files which are Modifications (Section 3.4)
  • make your Modifications available in source code form, under MPL 2.0 (Section 3.1)
  • document what your Modifications are (Section 3.3)
  • include a statement that your code is derived from the particular piece of MPL 2.0 code you started with (e.g., the Original Code), and a list of the names of the Initial Developers of that code (Section 3.3).

How "viral" is the MPL 2.0? If I use MPL 2.0-covered code in my proprietary application, will I have to give all the source code away?

MPL 2.0 is not as "viral" as the LGPL or the GPL forms of public licenses. To determine the level, you must focus on the definition of a "Modification" in MPL 2.0 (Section 1.10).

What is a Modification? Any changes to MPL 2.0-covered files, or new files into which MPL 2.0-covered code has been copied, are Modifications and so fall under MPL 2.0. New files containing only your code are not Modifications, and are not covered by MPL 2.0.

Files which fall under MPL 2.0 because they are or because they contain Modifications must be made available as detailed in MPL 2.0.

How are OpenMRS Modules affected by the OpenMRS License?

MPL 2.0 + Disclaimer covers the core OpenMRS code and is used for all of the OpenMRS community-supported and distributed modules, but modules are not required to be licensed under MPL 2.0.  In fact, modules do not have to be open source.  You are free to create a closed-source module and distribute it under any license you wish.  Module authors who are uncertain of how to license their module are encouraged to make their modules open source and, unless they have some reason to use a different license, use the same licensing as OpenMRS, but this is not a requirement for modules.

Who has the right to publish new versions of MPL 2.0 (Section 10.1)?

Only Mozilla may publish revised and/or new versions of MPL 2.0 from time to time. Each version will be given a distinguishing version number.

  • No labels