1,107
edits
| Line 32: | Line 32: | ||
= Option 2: Redevelop SUMO platform = | = Option 2: Redevelop SUMO platform = | ||
The outcome of the option matrix we developed in Q3 2009 ([[https://spreadsheets.google.com/ccc?key=0Ao5KB_TZOvbVdDgtSEdRNnNyeDBvWUtJOUZYZnU0Rnc&hl=en]]) was that none of the other existing platforms look significantly better than TikiWiki. | In Q3 2009 we discussed three options: Upgrade, Fork, or Port (see [[https://wiki.mozilla.org/Support/TikiWikiUpgrade]]). | ||
Having done the upgrade, there is really no point in forking the code as any changes we make are trivial to upstream. The outcome of the option matrix we developed in Q3 2009 ([[https://spreadsheets.google.com/ccc?key=0Ao5KB_TZOvbVdDgtSEdRNnNyeDBvWUtJOUZYZnU0Rnc&hl=en]]) was that none of the other existing platforms look significantly better than TikiWiki. That means that this option represents reimplementing the platform from scratch. | |||
When considering this option we should remember the pros and cons of porting to a new platform that [https://wiki.mozilla.org/Support/TikiWikiUpgrade#Port we analyzed previously]. | When considering this option we should remember the pros and cons of porting to a new platform that [https://wiki.mozilla.org/Support/TikiWikiUpgrade#Port we analyzed previously]. | ||
In addition, while developer morale and retention is a reason for moving away from TikiWiki, having the previous six months' work discarded quickly will likely not improve morale. Having committed previously to the upgrade path, the consequences of now moving away from that path must be considered. | In addition, while developer morale and retention is a current reason for moving away from TikiWiki, having the previous six months' work discarded quickly will likely not improve morale. Having committed previously to the upgrade path, the consequences of now moving away from that path must be considered. | ||
edits