1,623
edits
Support/TikiWikiUpgrade: Difference between revisions
no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
=Our three options= | |||
=Upgrade= | ==Upgrade== | ||
Upgrade to the latest stable version of TikiWiki and upstream future patches to ensure that we can continue to upgrade on each major TikiWiki release with minimal headache. | Upgrade to the latest stable version of TikiWiki and upstream future patches to ensure that we can continue to upgrade on each major TikiWiki release with minimal headache. | ||
| Line 19: | Line 19: | ||
* TikiWiki and SUMO often has quite different priorities. TikiWiki wants to create the equivalent of a CMS "operating system" -- a solution that can do pretty much anything. Our focus is to produce a high quality solution designed to fit our needs. | * TikiWiki and SUMO often has quite different priorities. TikiWiki wants to create the equivalent of a CMS "operating system" -- a solution that can do pretty much anything. Our focus is to produce a high quality solution designed to fit our needs. | ||
=Fork= | ==Fork== | ||
Fork and leave TikiWiki behind altogether and develop our own solution independently of TikiWiki. | Fork and leave TikiWiki behind altogether and develop our own solution independently of TikiWiki. | ||
| Line 33: | Line 33: | ||
* We could hardly call ourselves good open source citizens since we wouldn't give any of our fixes or feature additions back unless someone took our code and upstreamed it themselves | * We could hardly call ourselves good open source citizens since we wouldn't give any of our fixes or feature additions back unless someone took our code and upstreamed it themselves | ||
=Port= | ==Port== | ||
Port SUMO to a different platform. | Port SUMO to a different platform. | ||
| Line 50: | Line 50: | ||
* Not clear how much of a benefit this would be in the end -- depends heavily on the platform chosen | * Not clear how much of a benefit this would be in the end -- depends heavily on the platform chosen | ||
* Would likely have tons of regressions and broken use cases we didn't consider | * Would likely have tons of regressions and broken use cases we didn't consider | ||
=What's needed to make a decision= | |||
* Meeting with James/Laura/David/Marc/Paul for James to share some new architecture concerns and get to know each others' perspectives more -- Sept 2nd | |||
* Table of technical comparison between different CMS platforms (James) | |||
* Meeting with James/Laura/David/Marc/Paul/LPH so LPH can provide some initial responses on the feasibility of our architectural ideas | |||
* Completed work on [https://wiki.mozilla.org/Support/TikiUpstreamTriage SUMO bug triage] to get a clear picture of resources needed to upgrade (David/Laura/Marc) | |||
* Response to our [http://dev.tikiwiki.org/Architecture+Suggestions+From+Mozilla architecture concerns] (LPH/Marc) -- due Sept 9th | |||