Do we need both Trac and Roundup?
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. Skip
skip@pobox.com wrote:
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.
I think it would be a great idea. As I try to get back up on a new, "privacy=paranoid" machine, I went to mention that somewhere in the logging in process, there should be an indication of how much your box must be opened up before you can "log on," at least in the screen you get to when you log on. However, each time I went to enter such a note, I needed to "log on." I just gave up. -Scott David Daniels Scott.Daniels@Acm.Org
On Jan 6, 2008 8:57 AM, <skip@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
skip@pobox.com wrote:
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.
It would be great to merge into Roundup. The Trac instance is ancient and I've not had the time to try to upgrade it, which would indeed now be a waste of effort. When Roundup is ready, please let me know and I can at least make a pass through the pydotorg tickets to close those that aren't worth moving over to Roundup. There are quite a few stale and questionable items. In fact, it wouldn't be the end of the world to discard almost all of them, but still worth a review. - Stephan
participants (4)
-
Brett Cannon -
Scott David Daniels -
skip＠pobox.com -
Stephan Deibel