Hello to all of you,
Flectra has been out for about 1 year and has made many improvements over the community version, open source, of Odoo 11.
Flectra keeps benefits from patches, so stability and security, by regularly backporting patches from Odoo version 11… This is in my opinion an excellent thing but it will stop in the fall of 2020.
In fact, I think it is relevant to start the discussion on the after, and a possible version 2 of Flectra. What strategy could and should be adopted?
I see three possible ways. I will try to describe them, then I will give my own opinion:
Follow your own path
Flectra could decide, for its future major version, to follow its own innovations. It is the way of independence, it is the way Odoo has chosen for its software.
This is a way to maximize compatibility with existing modules and ecosystem can lead to great technical expertise.
Taking the best of open source
This way would make it possible to delegate low-level research and development costs to the communities in question, ensure a real and interesting technical evolution and it would be possible to update the use of common libraries with other open source ERPs such as ERPNext or Tryton.
However, this is an ambitious path, as it would break all existing modules, both internally and in the community. It would indeed be necessary to write solutions allowing a complete interoperability and therefore ensure that current modules made for Flectra 1 will still work. this represents an important and complex work.
Odoo 13 fork
The last way I think about would be to redo what had been done for Flectra 1, i.e. start from a recent version of Odoo (to fork). It would be to wait for the release of the version 13, in October 2019 theoretically, and to base on it to build Flectra 2. We would only take ** the low level** technical part, de facto delegated to Odoo S A and could benefit from about 2 years of patches recoverable on it.
Choosing version 13 would allow Flectra to allow 1 year to prepare version 2 before version 1 support is no longer provided through Odoo 11. The idea of taking only the core would make it possible to keep the modules as they are and to modify only the technical elements impacted by Odoo version 13, thus limiting the difficulty of operating the existing modules on these new foundations. This would also allow the community to allow up to 1 year to adapt its modules for version 2 of Flectra.
The concern of this approach lies mainly in the dependence on Odoo S A and the critique that can be addressed regarding the strategic and technical choices made (and in particular the fact of choosing to develop your own solutions).
In my humble opinion:
- The first solution would be a bad idea. Flectra does not have the financial or community capacity to ensure such a burden, either now or in the long term;
- This second track would have my technical preference, because I consider it more relevant and logical, more open to other communities and allowing for a stronger independence. However, I fear that the complexity required to continue to operate the existing modules will lead to an effort that I don’t know if Flectra or the community would want to take over…
- The last proposal is the most pragmatic. Since the Odoo base is relatively stable, migration efforts for two major versions should remain moderated. It would allow Flecra to focus on the overall reliability of the current modules and their evolution for another year before working on the next version.
I welcome the point of view of all those who will read this topic, because I think that the strategy must be discussed and decided quickly in order to allow everyone to anticipate what a version 2 of Flectra will be, to contribute to its success.