Current Strategy of bring.out: "Odoo" Open-Source "Behind Closed Doors"
Bosnian version of this article / Bosanska verzija članka
In February 2025, we published our work on Bosnian localization, before the Bosnian Odoo conference. After our experiences at that conference, we decided to continue our work “behind closed doors”. We noticed that none of the conference attendees were interested in our concept. We realized that “pushing” others was the wrong approach. We also assessed that licenses and licensing rights are not something we can rely on in Bosnia in case of abuse.
Over the past 3 years, we have spent approximately 1500 developer-hours on Bosnian “Odoo” localization projects, which means the cost side of the project to date is approximately 75,000 EUR.
However, the end of this year shows signs that the effort was not in vain. Our solutions have been recognized as credible within one large “Odoo” project, while our “old” clients have accepted “Odoo” as a platform on which a new generation of business solutions can be built.
As I just said, we develop projects behind closed doors, but all clients receive Odoo modules of Bosnian localization under standard open-source license (AGPL-3).
What does this mean in practice?
It means our clients, if they are not satisfied with our services, can continue development with other contractors. The only prerequisite is that the appropriate license is respected. In the case of AGPL-3 license, every new change must be published publicly. Also, they have the right to publish the existing source code publicly.
Is this allowed from the standpoint of the AGPL-3 license?
Yes, it is legal as long as we hold the copyright in its entirety, or all copyright holders make an agreement that development takes place privately.
Do we lose anything with this development approach?
As I explained above, this development approach currently protects us from the stated risks. However, our position is that we lose a lot because we do not share development with other “Odoo” development teams. “It takes two to tango”. For this project, to be an open-source project in every sense, it takes more than “bring.out”.
Until when open-source “behind closed doors”?
We see this strategy as a temporary solution. Possible future scenarios are:
- Create a healthy open-source ecosystem in Bosnia and Herzegovina or, even better, in the region.
- Create a pool of companies that would organize internal development similar to how we defined it with our clients (open-source licenses, private development)
- Achieve clear market recognition, based on which we could count on being the right partner for “Odoo” Bosnian localization
Support for Odoo EE
Our development is based on the “Odoo” open-source platform. When we are the main contractor, we offer exclusively solutions based on “open-source” modules1. The only exception can be highly specialized software modules2. However, everything that basic functions (such as Bosnian localization) are delivered exclusively under open-source license.
Example
We are currently working on a project based on the Odoo EE platform. Our localization modules will be delivered under the AGPL-3 license.
Claude, what do you think about this?
I asked Claude what he thinks about this. Interesting thoughts. A lot is obviously fabricated, but the concept is worth considering.
References
Ernad Husremović bring.out doo Sarajevo hernad@bring.out.ba