We use cookies to give you a better user experience and service.

By using our website, you agree to their use. Click on the "read more" link provided below, if you want more information about cookies and how to delete them.

Read more

Openbravo ERP

Openbravo Legal (ERP)

 

Openbravo® ERP is distributed under the Openbravo Public License (OBPL), a free software license based on the Mozilla Public License (MPL). At Openbravo, we want to let both open source and commercial developers use the Openbravo ERP core. We have therefore chosen the MPL as the basis for our license because it makes the ERP code available for extension, customization and integration with proprietary software and gives intermediate distributors and integrators the freedom to choose their licensing model. On the other hand, it keeps the source code for the core package freely available for the open source community to build upon, providing access, copying, modification and free distribution rights.

MPL is recognized and accepted by the Open Source community and it is suitable for software that includes other open source technologies licensed under various non-copyleft licenses such as Apache Software License or LGP.

More specific issues regarding licensing may be found in the following "Legal FAQs" for Openbravo ERP. If you have any additional doubts or wish to enquire about particular licensing issues please contact our Legal Department at legal@openbravo.com.

 

Legal FAQs for Openbravo ERP

 

How are the core components of the Openbravo ERP software licensed?


The Openbravo ERP Software Core Code is licensed under the Openbravo Public License (OBPL), a variation of the Mozilla Public License 1.1 (MPL). The Openbravo MVC Framework, part of Openbravo ERP, is licensed under the Apache Software License 2.0.

How does the OBPL differ from MPL?

The OBPL has been derived from the MPL by substituting references to the Openbravo Software for that of the Mozilla Foundation.

The OBPL also includes a branding clause, whereby anyone redistributing the code, in original or modified form, must maintain the Openbravo logo and link on start-up or login screens and on the user interface. For more details, please read Exhibit B of the license. While this may seem an additional obligation on developers, we do not believe it places an undue burden on them.

 

Why did Openbravo choose a variation of the MPL?


There are several reasons. First and foremost, we wanted a form of copyleft or reciprocal license so that derivative works of Openbravo are published under the same open source license. In this way, the Openbravo Community receives the benefit of any extensions and innovations added within the Openbravo ERP Software by third parties. On the other hand, we do not want to discourage Openbravo ERP users from adding their own proprietary value-additions to the Openbravo ERP Software, because of worries that they must publish those additions in open source. MPL does require that derivative works be published in open source, but separable extensions (i.e., those included in new files) are permitted to be distributed under another (open or closed) license.


An annotated version of the MPL, with comments on how it works, is posted on the Mozilla site: http://www.mozilla.org/MPL/MPL-1.1-annotated.html.

 

When must derivative works of Openbravo ERP be published as open source under the OBPL?


The OBPL permits anyone freely to make copies and derivative works and to distribute them, on condition that anyone who distributes derivative works must publish the source code. This requires a few helping comments, though please read the full text of the OBPL for the applicable license terms.

A distribution is interpreted generally as providing a copy, by any physical or electronic means, to a third party. Under the OBPL, users within a licensee's company or organization are not generally considered third parties. We consider that if our software or any changes to it are only distributed on an organization's internal network (intranet), source code does not need to be disclosed.

However, we also interpret the OBPL to require source code to be disclosed and the software distributed under the OBPL if Openbravo's client or server software is made available to third parties, such as would be the case with independent software vendors, value-added resellers, hosted service providers and ASPs, appliance manufacturers, or alternative support channels. This is because the Openbravo ERP user interface (UI) is itself software - the Openbravo client it is written in Javascript. Under standard operation, Openbravo client software is automatically distributed to users' browsers when users first connect, and software updates are automatically distributed that way as well. Because the Openbravo client software is distributed to users' web browsers, original source code and any changes to Openbravo ERP (regardless where made) must be published in open source if your Openbravo ERP deployment has "external" or third party users, for example under an ASP model. In addition, you must ensure that any recipients of a derivative work of Openbravo ERP client software are also bound by the terms of the Openbravo Public License.

 

How can I incorporate Openbravo ERP in a proprietary software offering?


First of all, Openbravo ERP can be integrated in a software solution distributed under a commercial or proprietary license to clients, under the terms of the OBPL. However the original core code files and any changes to them ("derivative works") must be redistributed under the OBPL, along with their source code. If you don't want to distribute the source code of these changes, Openbravo offers alternative commercial licensing terms, particularly for independent software vendors, and value-added resellers.

 

Does Openbravo comply with standard attribution "etiquette"?


We at Openbravo believe strongly in code attribution. Not only do we believe that original developers and contributors have moral rights to be recognized as authors of the software, but also we believe that developers - both intermediaries and end-users - must have the means to know the history of the software components they are using. Therefore all original attribution notices in the source code must be kept, and developers' modifications must be highlighted by adding new attribution notices (e.g. including change logs) for the derivative works they produce.

In addition, we believe it is important to both us and users for these to know where the ERP software they are using comes from, and for this reason we include an obligation to maintain our "Powered by Openbravo" logo on the GUI and on log-in screens, and links to our webpage. While this may place an additional obligation on developers, we do not believe this is an undue burden, nor breaches the guidelines of the Open Source Definition.

 

Do I need to consider any special trademark conditions regarding Openbravo ERP?


Openbravo® is a registered trademark in Spain and several other countries. Our trademarks are important to us, to distinguish our product and maintain the quality and reputation of our business. Trademarks must be strictly enforced, in order to preserve their validity and value, and protect users in the market. Accordingly, use of our Trademarks, including the Openbravo name and logo, is subject to our Trademark policy indicating what you can do with them and when you need permission to use them. Please read this document, together with our license, carefully if you are redistributing Openbravo ERP, in binary or source code form. Generally speaking,

Do not use our trademarks in a way that states or suggests that Openbravo sponsors, endorses, or is otherwise affiliated with your project or product, including text on your webpage or in your product documentation, without our consent (license).
While referential use of our trademarks (such as in a product review or website link) does not need our consent, however you should follow the policy guidelines as to how to mention "Openbravo".
Please include text stating the product "includes Openbravo software" on any packaging or other physical means of distributing the Openbravo ERP software.

Please read "Trademark Guidelines" and "Trademark Policy" documents for more details.

 

How may I contribute to the development of Openbravo ERP?


Contributions can be made in two ways:

1) Under the Openbravo or Apache license, as a modification of the code. This will not necessarily be included in the source tree.

2) On the other hand, if we do want to include a contribution into our source tree, we need to be sure that we can use it under our current free software license, other alternative licenses that may be requested now or in the future, or commercial terms. Accordingly we would request contributors of significant code to be incorporated into the core product to make it available to us under the standard contributor's agreement, giving us freedom to use the code and maintaining your rights to exploit it.

A copy of the Openbravo Contribution Agreement can be found here.