Page History

...

• Taher went through a list of possible areas to start re-factoring. After some discussion it was decided that we will put together an initial batch of work to do that is publicly available so that people can assign themselves to a task. We need to ensure that people are comfortable picking up a task and assigning it so a mix of straightforward, easier tasks as well as harder more complex would be included.
  
  
• We would look to implement the framework changes in the trunk and 15.12. The changes would not be back ported to any of the live release branches. This means that anyone using the current releases would not be affected by the framework changes. (Jacopo suggested that because of the framework changes it might be a bit harder to upgrade so we could possibly consider extending the life of the release branches to compensate.)
  
  
• Jacopo mentioned that changing the framework code that is not exposed to the applications is fairly easy so this would be a good place to start.
  
  
• Jacopo also suggested that during the re-factoring process if people have performed a change but see many places where a similar change is needed, then it would be good to publish the template showing how the problem was fixed. This would help other people to fix problems in other areas by using the template and adjusting it.
  
  
• We briefly discussed the need for better test coverage and it was suggested that if people are not comfortable doing code changes then they can also help with improving the tests.

Collaboration Tools

The

...

Development mailing list, Jira and the Wiki were identified as the main tools to use for collaboration. The Skype group chat could also be used if required to help with clarifications

...

1. The Wiki will be used to store the Framework Re-Factor backlog tasks available. People can then sign up to a task that they will work on

...

1. 
   
   
2. Jira will be used to track the work. Once someone has signed up for a task a Jira will be created. We will try to create a working batch by limiting the number of Jira's open at a time (e.g a maximum of 10) and only move onto the next batch when the first batch is completed.
   
   
3. We will make use of Jira sprints to help us control and understand what is in progress. It will also help identify any blockages.