...
- Identify a list of approximately 10 key re-factoring areas (5 easier, 5 more difficult)
- Ask the Community for volunteers to help re-factor in these selected areas
- Tick off each area as it is completed
- Use of JIRA for tracking work (e.g open a master issue for each area identified and include individual sub-tasks)
Use of JIRA to organise sprints if required
- Use the trunk as the main code source for the framework re-factor
Reasoning
- A short to-do list of is good number to highlight the key areas
- A list will help focus the community on what needs to be done
- As one area is finished we can easily move to another
- Over time the initial re-factoring will make further re-factoring easier
Current List of Re-factoring Focus Areas
...
If you are interested in working (or are in the process of working) on any of these areas then please add your name in the column below.
AREA | REASON FOR RE-FACTOR | STATUS | WHO IS WORKING ON IT? | JIRA MASTER ISSUE LINK | COMMENTS | |
---|---|---|---|---|---|---|
1 | EntitySaxReader | EntitySaxReader implements javolution interfaces and looks hideous | ||||
2 | HtmlFormRenderer | HtmlFormRenderer is 3000 lines of code and the interfaces it implements are also huge | ||||
3 | XmlFormRenderer | XmlFormRenderer does not implement more than half of the methods | ||||
4 | Dependencies on Deprecated Classes / Constructors | Lots of dependencies on deprecated classes / constructors (e.g. HtmlScreenRenderer, FoScreenRenderer) | ||||
5 | Start.java | This has some problems which I'm trying to tackle in JIRA: OFBIZ-6783 | In Progress | Taher Alkhateeb | OFBIZ-6783 |
Other ways to help
If our top 5 areas seem a little too much for you to take on then you can help in other areas too, and a little bit of work quickly adds up. Below are some other ideas for helping remove clutter and help clean up the code base.
...
helping us with this re-factor effort then please take a look at the list of tasks that we'd like to focus on in our Current Re-Factor To Do List