/!\ The infrastructure commitee made a recommendation on Oct 3rd, 2006. See python-dev posting for more (selected: Jira & Roundup).

Four trackers were set up by the deadline of August 7 2006; see below for the list. A committee of four people is now looking at the submitted trackers, and will recommend one for use as the new Python bug tracker. The committee will make its recommendation in the fall, perhaps in October.

Once a tracker has been selected, a new installation will be set up and the SourceForge bug data will be converted once more. That conversion may be more carefully done than the conversion for the demo trackers.

Participating Trackers

Tracker wiki page

Test Tracker URL

Contact Person (name & email)


Alec Thomas


Stefan Seefeld


Jonathan Nolen


James Henstridge

/!\ No new trackers are being accepted for consideration. /!\

To learn what the committee liked about various trackers participating, see GoodTrackerFeatures (to be edited by committee members only!).

The Announcement

The Python Software Foundation's Infrastructure committee has been charged with finding a new tracker system to be used by the Python development team as a replacement for SourceForge. The development team is currently unhappy with SF for several reasons which include:

For these reasons and others, we are requesting the Python community help us find a new tracker to use. We are asking for test trackers to be set up to allow us to test them to see which tracker we want to move the Python development team to. This is in order to allow the Infrastructure committee to evaluate the various trackers to see which one meets our tracker needs the best.

Because we are not sure exactly what are requirements for a tracker are we do not have a comprehensive requirements document. But we do have a short list of bare minimum needs:

If there is a tracker you wish to propose for Python development team use, these are the steps you must follow:

We will accept new trackers for up to a maximum of two months starting 2006-06-05 (and thus will end 2006-08-07). If trackers cease to be suggested, we will close acceptance one month after the last tracker proposed (this means the maximum timeframe for all of this is three months which ends 2006-09-04). This allows us to not have this process carry on for three months if there is no need for it to thanks to people getting trackers up quickly.

For those that are working to provide a test tracker, please subscribe to the various wiki pages that are maintained by the Infrastructure committee. We will use these wiki pages as the primary way to communicate with all tracker maintainers.

If you have any questions, feel free to email infrastructure at .

- Brett Cannon


OriginalCallForTrackers (last edited 2010-04-29 12:45:41 by PaulBoddie)

Unable to edit the page? See the FrontPage for instructions.