Support/PlatformEngineering: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 13: Line 13:


= Evaluation =
= Evaluation =
In Q2 2010 we will develop our first releases based on top of TikiWiki 5.1.  This will enable us to evaluate the success of our upgrade.
During the upstreaming process, we have developed some concern about the viability of building on top of Tiki 5.1.  We will hence re-evaluate our options once the upstreaming is finished, before we actively port our production instance.  


During the first two release cycles we will gather data relating to the following objective and subjective indicators.  In mid-May stakeholders will meet to make a decision about the future development path for SUMO.  This decision should be influenced by objective factors but will need to take into account developer skillsets and internal culture.
We had originally intended porting our production instance to 5.1, running through a couple of release cycles, and then evaluating.  However, we can reduce time to evaluate and possible investment by performing this evaluation earlier.  Finishing upstreaming gets us to the point of having paid our ethical debt to TikiWiki by giving back our changes and improvements to the community, so this was important to complete.


The evaluation criteria are as follows:
The evaluation criteria are as follows:
* Is the new codebase easier to understand and develop further than the old one?  That is, is it easier/more enjoyable for our webdevs to do their jobs?   
* TikiWiki 5.1 Codebase: This can be evaluated by looking at the code and running tests against tiki-trunk.mozilla.com.
* Can we get more done in a release cycle?   
** Is the new codebase easier to understand and develop further than the old one?  That is, will it be easier/more enjoyable for our webdevs to do their jobs?   
* Is the new codebase more robust?
** Will we be able to get more done in a release cycle?   
* Is the new codebase at least as performant as the old one?
** Is the new codebase more robust?
* Is the new codebase actively good on each of these criteria, as opposed to just better than before?
** Is the new codebase at least as performant as the old one?
** Is the new codebase actively good on each of these criteria, as opposed to just better than before?


The recommendation to undertake at least two release cycles before performing a formal evaluation is in conflict with the desire to move forward as quickly as possible with the eventual decision path, however it is important to make a good decision here, which cannot be done objectively with only a single cycle.  The first new release after the upgrade will be testing a new development process.  Doing anything for the first time will be slower.
* Our implementation
** How would we implement our build process in order to keep our TikiWiki up to date?
** How will we separate out our local changes that are not going to be upstreamed to TikiWiki?
** What is the scope of these local changes? 
** What is the complexity and time required to create and maintain a local codebase consisting of templates, modules, and overridden files?
** How would this affect the deployment process and our desire to move towards continuous integration?
** What new local code do we need to write or rewrite in order to run Tiki 5.1?


= Option 1: continue with Tiki =
= Option 1: continue with Tiki =
1,107

edits

Navigation menu