If we were to revive a code review process, it would be much less resource intense. We'd set up a proper tool for voting and the code management. Please see: Quality Team - How to reduce the workload
There is stub of this in Tiki: https://profiles.tiki.org/Software_Project#Hooks_for_version_control
The information below is kept for posterity.
The Quality Team aims to (especially in the stable branch) to share experience and minimize the risk of introducing regression bugs or bad coding practices.
- 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