Hello All,
Since I work on the bootstrap theme in OFBiz, I have many thoughtful,
carefully read the ofbiz community exchanges and spoke with some members
of the OFBiz community.
Today I am convinced that the OFBiz project is a framework that is not
intended to be an ERP. Its OOTB user interface is a nightmare and is not
really user oriented.
Several topics that seem to have no link together, seems to be linked
around the same idea.
The first topic is about functionality of OFBiz.
On one hand, there is the OFBiz framework. It contains a user interface
to show the possibility of OFBiz, but must be changed during
integration. It also includes functional oriented features. These
features split the community between those who want to keep them in the
project and those who wish to exclude them.
On the other hand, there are new initiatives,abandoned projects, old or
having no longer contributors (project manager, POS, etc.) who need
support, visibility, even if they are not added to the OFBiz project.
A first approach was discussed with GIT. It can allow everyone to share
their work more easily with branch feature. Which is good but not the
best in my opinion.
Another topic that is important to me is the functional part of OFBiz.
Sharan explained me about its willingness to invest energy to make the
software more functional, and if it's possible to have a version with
ERP oriented for small businesses with minimal features but easy to use.
Like growERP or TerCompta offer. Using OFBiz framework but simplify the
UI to allow the software to be used intuitively without modifications.
These initiatives come up against the model of OFBiz project. Who has
still not decided whether it is an ERP, in which case it needs to adjust
its UI or an automation of enterprise processes framework, which
involves getting rid of unnecessary features dedicated to ERP.
There are several solutions that could help to make better the model of
OFBiz and satisfy the entire community.
The first solution would be to limit the “OFBiz framewok” project
framework for automation enterprise processes and to have another “OFBiz
ERP” project which would use the framework as a basis, and which would
provide a user-friendly UI and dedicated tools to ERP.
The second option is to find a way to cut the project in extensions.
This solution would have the opportunity to clean the framework and have
features as micro projects and therefore no longer a monolithic software.
I see a lot of debate about adding new functionality that allow to
improve development, compile, manage sources, merge with another
framework, but the debate on the division of project extensions seems
not to interest. It seems to me extremely important to facilitate
development and therefore, ultimately, the visibility of the project in
the developers community.
At Nomaka, we initiated an effort starting from the first solution. We
took OFBiz framework, deleted all the themes and created a new one. Then
we redesigned the interface to match a basic ERP.
We started with actor UI. Disabled existing screens and created new ones
more functional and user-friendly.
I find it a pity to work alone in my corner without being able to easily
share my work, without taking advantage of the OFBiz community knowledge
to guide me onthe right way.
I wonder if we could work on this axis and balance the rigidity
necessary to have a stable project and flexibility that allow to include
non-committer contributions ...
What do you think ?
Julien.
