Support/PlatformEngineering: Difference between revisions
< Support
Jump to navigation
Jump to search
(Created page with '= Overview = We need to come up with a plan for engineering a sustainable platform for SUMO. The goals are: * Develop the Tiki platform into a codebase that can continue to gro…') |
|||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
We need to come up with a plan for engineering a sustainable platform for SUMO. The goals are: | We need to come up with a plan for engineering a sustainable platform for SUMO. The goals are: | ||
* | * Evaluate the updated Tiki platform for suitability as a codebase that can continue to grow and improve with SUMO and with other projects using it for support | ||
* Improve code platform quality to | * Improve code platform quality to | ||
** Increase robustness and performance | ** Increase robustness and performance | ||
Revision as of 16:08, 20 January 2010
Overview
We need to come up with a plan for engineering a sustainable platform for SUMO. The goals are:
- Evaluate the updated Tiki platform for suitability as a codebase that can continue to grow and improve with SUMO and with other projects using it for support
- Improve code platform quality to
- Increase robustness and performance
- Increase developer happiness
- Reduce time to implement new features
Refactoring
We need to identify which parts of Tiki we plan to rewrite or refactor. The criteria for choosing these are as follows:
- Existing poor code quality and/or fragility
- Impact of refactoring: choose areas that will have the biggest impact for users and developers
- Ease of refactoring: While this would never be the only criteria, there is certainly value in choosing low hanging fruit