Page History

...

We currently have cases where some external products should not have been implemented to form part of release but can be made available if users want to integrate them into an OFBiz release.

Draft Proposals

These proposals are to be raised for on the mailing lists for community discussion and feedback

...

. They will only be implemented if the community consensus is recevied/

1. Proposal: Tidy up OFBiz

...

1. Technical Framework or "kernel"

...

2. Proposal: Define and implement a process to manage the

...

1. code that has been cleaned out

   1. eg to a sandbox location so could be used by users who want to pick it up and use
      
      

2. Proposal: Tidy or Clean up

...

1. OFBiz Business Framework

   1.  (e.g. ensure business processes have a use case to describe the process and that can be used for validation)
      
      
2. OFBiz in application documentation - have been using docbook but two other proposals mentioned
   1. Idea 1: Use SVNPUB: This is committer controlled but may be able to switch to setup a business user expert with write access. This means that the "mini subject matter experts" could easier maintain their specific areas.
   2. Idea 2: Wikipedia style documentation where a page linked within the OFBiz application page (e.g. using the '?') will link to the wiki. This is more open and non committer controlled. Means more people can contribute
3. External dependencies refactoring
4. Build a Roadmap / High level plan that will be used to show details of releases and how they are supported, details of work in development, updates planned. Need to look at tools available eg. JIRA has options to do planning and roadmap, also look for Roadmap and planning info on the Wiki as may be able to collate
5. Ensure business success stories are documented (as this is valuable info for potential users). Ask users  to add their stories and also get them to list the applications used / implemented. Existing policy is that there should be no direct links from OFBiz website main pages so need to use the wiki. Investigate whether integraters are willing to share their client links and stories.
6. Marketing OFBiz - prepare an end user demo that can be based on roles (e.g accountant, HR manager, Order Clerk, Warehouse Manager etc). Link to user stories that can have a script or supporting documentation (e.g currently on main page there are no instructions about how to login to the demo just in case you are thrown out. Also default user if flexadmin which doesnt have all the permissions for all applications).
7. Common Core Marketing Material - Put together some standard OFBiz marketing information that all integrators / users have access to. Integrators can then adapt it to suit their needs if required. Information could be white papers around supported industries etc. Need to define what tool could be used to prepare the material as it needs to be accessible to a common audience. This is important as everyone will need to be able to edit it!
8. Maintenance - eg. Tomcat etc. Need to keep a watching brief on external products that are directly used by OFBiz
9. Establish a group of  "mini subject matter experts" both business and technical (i.e. dont have to be both but can be). Identify contributors and knowledge. Can refer to these people regarding their specific area
10. Work on a strategy to encourage more business users
11. Look at the testing strategy - unit testing in isolation is not enough. We need to ensure there is an full end to end test flow
12. OFBiz branding and trademarks - need to review the process and contact sites that may be infringing this
    
    

Actions

...