Page History

...

1. Based on his experience he thought that trying to make OFBiz an "out of the box" solution that could work for everyone will be too hard and that in future we should focus on using these tools to build good business solutions
2. He also saw it as important that the applications that are there need to include contextual help and integrated testing tools across the complete global process.
3. He thinks that we need to bring more business users into the project and that there are not many active business users on the current mailing lists. OFBiz is a business product so we should have a mix of business and technical users across the community.

Original Project Vision:

Jacopo mentioned that the original vision of the OFBiz was to have an application development framework with with  a data model and some core skeleton applications with CRUD services that would be customised per implementation. Over the years because of contributions from the community these 'skeleton' applications have become more and more complete.A User Interface was added and an effective 'out of the box' e-commerce solution.

Currently we believe that we have the situation where OFBiz as an integrated ERP can only be used "out of the box" for specific cases.

Project Strategies

Sharan talked about the different strategies that projects generally have in place that she wanted to investigate for the project.

...

• Curently the mailing lists, website and wiki are the main communication tools. Jacopo as PMC chair prepares project reports to the ASF on a regular basis.
• We want to encourage more business users into the community so need to tailor the website and wiki.
• We have found that meeting in person at events such as Apachecon have been really good in building community as well as communication links. What other

Risk Management - Not sure there is anything currently in place

• Risk Management strategies are used to identify, assess and react to any risks to the project. Risks can cover a range of areas.
• Currently OFBiz has a range of external dependencies that need to be maintained. Do we have someone allocated to keep a 'watching brief' for any retiring of a release that we are using, finding out about any new releases that we may have to implement at a future date
• Does anyone assess the impact of not implementing a specific change or process for the project?
• What is the project attitude to risk? (Does the project want to keep everything low risk because we need to be able to manage and conform to the Apache release process?)

Issue Management - currently managed by JIRA

...