The feedback from the community day survey was that people wanted to have a bit more organisation for the next community day so I'd like to use this page to put down some ideas.
Project Vision and Direction - What do we want to achieve?
Tidy up OFBiz into the following 4 distinct streams.
1 .OFBiz Kernel
Structure: It contains one common component that only contains all the entity definitions (the whole data model) that are currently defined in the various applications; it will also include CRUD or basic and very global/generic services; no user interfaces.
Purpose: To be used with the "OFBiz framework" by users interested in building from scratch user interfaces based on the OFBiz data model and crud services
2. OFBiz Framework
Structure: It includes only the framework components, the tools, hot-deploy and runtime folders;only a few entities are defined (the ones declared by the framework components, of course); no applications, no specialpurpose; the only user interface available ootb is WebTools
Purpose: It provides a framework to build ERP-like applications from scratch; typically a developer will start by running the "ant create-component" task and will then declare the entities, services and screens in the custom component
3. OFBiz Applications
Structure: It contains all the existing applications (except the component delivered as "OFBiz Kernel") with their special services and user interfaces
Purpose: To be used by users interested to running a mostly-ready out of the box solution; to be used with the "OFBiz Framework" and "OFBiz Kernel"
4. OFBiz Special Purpose
Structure: It contains all the existing specialpurpose components with their special services and user interfaces
Purpose: To be used by users interested in specific integrations/solutions solution; to be used with the "OFBiz Framework" and (maybe) "OFBiz Kernel"; the user could use a subset of the specialpurpose components
Potential Community Day Tasks
- Applications Componets Tidy up (as described above)
- Move all Application Services and Data Model into one catchall component as per diagram - Roadmap Diagrams - In Progress and Draft Applications Roadmap
- Some discussions have already taken place and there appears to be some strong benefits for the re-organisation (NOTE: Need to ensure that we have achieved consensus for this work to be done)
OFBiz Website - What do we want to achieve ?
- Definition of requirements and constraints
- Identification of team (graphics, web development, content, flow)
- Planning and re-design
OFBiz Online Help
- Disable Content Manager rendering of online help
- Enable Webhelp
- Create one docbook 'book' per application
OFBiz End User and Wiki Documentation - What do we want to achieve?
- Review and consolidation of existing information
- What can be moved to the wiki and then organised?