[Python-Dev] [Pydotorg] Do we need both Trac and Roundup? (original) (raw)
Brett Cannon brett at python.org
Sun Jan 6 23:02:12 CET 2008
- Previous message: [Python-Dev] Do we need both Trac and Roundup?
- Next message: [Python-Dev] [Pydotorg] Do we need both Trac and Roundup?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Jan 6, 2008 8:57 AM, <skip at pobox.com> wrote:
A ticket I opened on Roundup about a website issue some time ago was closed today. It was related to a different topic, but in the discussion I wrote: Is there some reason at this point that we need to maintain two separate trackers? A ton of work went into making our Roundup instance what the key players wanted. Why not use it to track website issues as well? With them separate you have two communities of maintainers and triage folks who are mostly disjoint. I assume there would be some trac-to-roundup conversion necessary. Perhaps something like that already exists. Do people think it would be worthwhile to merge the Trac tracker content (the issue tracker that holds tickets related to the python.org website) into the Roundup tracker (the issue tracker that holds tickets related to Python the language)? While they are nominally distinct activities, it seems to me that we must waste some precious resources (mostly people) maintaining two mostly disjoint trackers. There is also some functionality overlap, mostly in the documentation area.
Yes, we should consolidate. But first we need more manpower to manage the tracker as it is now. Some time this month I will be sending out an announcement asking for more volunteers to help maintain the tracker. If we can get enough people to come forward to also help out we can include moving the web site tracker over as well.
-Brett
- Previous message: [Python-Dev] Do we need both Trac and Roundup?
- Next message: [Python-Dev] [Pydotorg] Do we need both Trac and Roundup?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]