Rietveld integration status (Was: MSI: Remove dependency from win32com.client module (issue4080047))
On Tue, Feb 1, 2011 at 9:45 AM, Georg Brandl <g.brandl@gmx.net> wrote:
A mailing list works only if you have a small group of core developers who can independently organize the incoming mails using local tools, such as the read/unread marking of the email client. For a larger group this doesn't work (how do you assign a patch to someone using a mailing list?).
If you can filter patches by module (and it can be done automatically), then you won't need to assign patches. People can subscribe to interested parts and participate independently.
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? -- anatoly t.
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
Am 01.02.2011 17:25, schrieb anatoly techtonik:
On Tue, Feb 1, 2011 at 9:45 AM, Georg Brandl <g.brandl@gmx.net> wrote:
A mailing list works only if you have a small group of core developers who can independently organize the incoming mails using local tools, such as the read/unread marking of the email client. For a larger group this doesn't work (how do you assign a patch to someone using a mailing list?).
If you can filter patches by module (and it can be done automatically), then you won't need to assign patches. People can subscribe to interested parts and participate independently.
That's not true. Assignment isn't meant to make searching issues easier, it's meant for the developers to help them collect and work on their tasks. Georg
participants (3)
-
anatoly techtonik -
Georg Brandl -
R. David Murray