Page History

...

• Some of the classes have been extended from external libraries into the Core APs
• Some of the files are too long
• Different levels of abstractions are mixed together
• Poor test coverage, lack of Test Driven Development
• Implicit (hidden) dependencies

Planning and Approach

The re-factor covers the whole OFBiz code base so we need a simple approach that makes it easy for people to pick up, re-factor and improve an area. This means that we probably wont be able to run it as a traditional linear project. Instead we will look to highlight areas of work where the community can help.

...

• Identify a list of 5 possible key re-factoring areas
• Ask the Community for volunteers to help re-factor in these 5 selected areas
• As one area is completed, top up the list of 5 with another area
• Use of JIRA for tracking work (e.g open a master issue for each area identified and include individual sub-tasks)

Reasoning

• A short list of 5 is good number to highlight the key areas
• A  list will help focus the community

People Available to Help

Jacques, Taher, Nicolas, Julien, Gil, Sharan,  Hotwax team??

• Include ideas for design philosophy (note from Taher)
• need to document our design philosophy for others to consider when writing code. I don't mean just formatting conventions but also things like writing to interfaces, TDD, design rules specific to OFBiz, and so on.
• Use of JIRA for tracking work - can use subtasks linked to one overall task ? Open a master issue with macro sub-task, linked to wiki for each conception detai

...