Revision 6 as of 2006-06-06 05:23:36

Clear message

About

Python Software Foundation's Infrastructure commitee has put out a call for trackers in order to evaluate alternatives to [http://sourceforge.net/tracker/?group_id=5470 SourceForge] for use by the Python development team. A copy of the original request can be found at the bottom of this wiki page containing details of what we are asking of the community.

For Those Participating

For those wishing to participate, please add yourself to the table below after reading the original request for trackers.

Tracker wiki page

Tracker URL

Contact Person (name & email)

XXX <wiki page>

XXX <URL>

XXX <contact name>

XXX <contact email>

TracTracker

http://python-trac.swapoff.org||Alec Thomas

alec@swapoff.org

To find out what the committee is finding they like about various trackers participating, please monitor GoodTrackerFeatures (to be edited by committee members only!). For those providing a test tracker, please subscribe to that wiki page so that you can see what the committee discovers they like about trackers, allowing you to change your tracker accordingly.


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.

As the committee evaluates trackers we will add information about what we like and dislike to the http://wiki.python.org/moin/GoodTrackerFeatures wiki page so that various trackers and change their setttings and notify us of such changes. This prevents penalizing trackers that are set up quickly (which could be taken as a sign of ease of maintenance) compared to trackers that are set up later but possibly more tailored to what the Infrastructure committee discovers they want from a tracker.

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

- Brett Cannon


CategoryTracker

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