THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 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
- 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.
- 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:
...
- Currently there doesnt seem to be a roadmap or high level project plan in place
- Work is being done on a task by task basis that is triggered by a reported issue or maintenance request (e.g. Tomcat upgrade etc)
- An overall plan will help with communications to the community, give the project future direction and also give focus to work efforts
- The planning could be broken down into the key areas (e.g. applications, maintenance/housekeeping, release planning, security, etc)
- We would need to investigate the Roadmap and.or Agile functionality that exists as perhaps it could be used to help manage the project
Communication:
- 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 strategies are used to identify, assess and react to any risks that impact the project. Risks can cover a range of areas including doing or not doing something. I think we need a strategy in place to deal with things that will impact the project. We need to identify them, assess them (because not all of them may cause a problems - some could be positive!), and then decide on how to react to them (this could something as simple as defining when to include it in a release or deciding that for the moment implementing something will cause more problems that it will solve).
- 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
- All project issues are managed in JIRA
- Users need to create a profile and can report an issue or submit a patch
- Committers assign themselves to an issue and then follow it through to resolution (normally this is either fixing the issues themselves or applying a submitted patch)
- Reports and statistics are available
Task Management - currently managed by JIRA (Need to loo
...