Code Review aims to (especially in the stable branch) to share experience and minimize the risk of introducing regression bugs or bad coding practices.
Although there is currently no formal code review process for commits, it is currently being done by the Developers on an ongoing basis through the monitoring of the SVN mailing list. A formal code review process has been implemented before but only for commits in the LTS branches, in the form of a Quality Team. This was abandoned when the amount of overhead became unsustainable. There has been talk about getting some kind of code review process up again, but details are uncertain - in order to have a process that works smoothly and does not depend on too small a group of developers. The plan is to wait till after we've switched to GIT from SVN as that would address a number of issues we faced before including merging issues between the various SVN branches. GIT is also a much better tool via "pull requests" to implement a more distributed code review process. See Distributed revision control.
- Maintain code.tiki.org (might not be needed anymore if we are on GIT and using something like GITHUB, to be investigated.
- Release LTS versions
- Clean up content and move it to proper site according to Where.
- Implement Reduction of workload strategies
More details: dev:Quality Team