Re: [Pywikipedia-l] [Pywikipedia-svn] SVN: [7591]trunk/pywikipedia/wikipedia.py

... The only way to ensure stability IMHO is to introduce a strict review process, where a changeset has to be reviewed by a qualified developer other than the submitter before making it into the main development branch. It appears to slow down the process at first, because it introduces a delay in the commit workflow, but in the end code quality significantly improves, and this reduces maintenance costs. Being now used to the Mercurial community, where each patch is sent to the dev- mailing list before being pulled by the relevant maintainer, I would love to see those practices here. If the community was interested to do the switch, I would be willing to spend a significant part of my time to review patches, and/or give assistance in Mercurial usage. I think that a few developers in the past got tired of pywikipedia, specifically because of our development process. I would love to improve that aspect of our project.