On Tue, 01 Feb 2011 18:25:24 +0200, anatoly techtonik <techtonik@gmail.com> wrote:
On Tue, Feb 1, 2011 at 9:45 AM, Georg Brandl <g.brandl@gmx.net> wrote:
It sure is more convenient to do patch review, but that's why we are working on Rietveld integration in the tracker.
Where is the code? What is the status? Where is the roadmap, i.e. how can people help? Why can't you use hosted Rietveld instance if there are troubles to setup server properly?
See http://wiki.python.org/moin/TrackerDevelopment for how to set up a test instance to hack on. The rietveld stuff is in http://svn.python.org/view/tracker/instances/python-dev/rietveld/. The problem with the rietveld setup is that the script that looks for patches and sets up review tickets has a problem where it consumes ever larger amounts of memory and doesn't finish its run. So the "roadmap" is to debug and fix that script. Martin hasn't had time to do it, and I haven't had time to learn enough about rietveld to try. Getting set up to test tracker patches is distinctly non-trivial, which is probably why very few people work on it. -- R. David Murray www.bitdance.com