Design Principles - mavenea/mavencrm GitHub Wiki

why a fork?

  1. Inactivity of VTENext dev team. They are no where to be seen!
  2. Source code is released in non open source process cycle. Source code is released like a commercial application.
  3. The codebase is outdated, uses legacy libs, require refresh, re-design and refactoring.
  4. The foundation of VTENext is sound specially the BPMN engine, relatively easy to use, however, the product is not using modern technologies, has drifted from the original VTiger fork and did not merge upstream changes.
  5. The current VTENext client-base / deployments seem to be around a particular region only , and heavily Italian-based.
  6. A modern end-to-end solution integrating other services such as content personalisation, data analytics, nodejs with VTENext as a module is a viable ERP & CRM solution option.

guiding principles

  1. Stay current with upstream as much as possible.