|
Size: 5623
Comment:
|
← Revision 43 as of 2009-09-17 11:55:58 ⇥
Size: 1026
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Can I change it? |
|
| Line 5: | Line 3: |
| 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. | Python Software Foundation's Infrastructure commitee put out a call for trackers (bug/request/issue/ticket trackers) in June 2006 in order to evaluate alternatives to [[http://sourceforge.net/tracker/?group_id=5470|SourceForge]] for use by the Python development team. A copy of that request can be found at OriginalCallForTrackers. |
| Line 7: | Line 5: |
| Jira was the first choice of the committee. A lot of people complained about using a closed-source and hosted bug tracker, so a call was posted for volunteers to help administer a Roundup installation. Enough volunteers came forward, so work is now proceeding on improving the conversion to Roundup. |
|
| Line 8: | Line 8: |
| = For Those Participating = | The Roundup bug tracker that serves http://bugs.python.org/ is actually hosted at http://psf.upfronthosting.co.za/roundup/tracker/ |
| Line 10: | Line 10: |
| For those wishing to participate, please add yourself to the table below after reading the original request for trackers. || '''Tracker wiki page''' || '''Test 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|| ||Roundup||XXX||Stefan Seefeld||seefeld@sympatico.ca|| || JiraTracker || http://jira.python.atlassian.com || Jonathan Nolen || jonathan@atlassian.com || || Scarab || http://www.solitone.org/scarab-demo/issues || Tigris.org || XXX || 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. = Key Wiki Pages = * GoodTrackerFeatures * WorkingWithSourceForgeData |
Bugs found in the living installation of Roundup for Python bugs are reported to '''meta-tracker''' -- is at http://psf.upfronthosting.co.za/roundup/meta/ Please report problems with the bug tracker there. |
| Line 28: | Line 14: |
= 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: * Bad interface Most obvious example is the "Check to Upload" button * Lack of reliability SF has been known to go down during the day unexpectedly and stay down for hours * Lack of workflow controls For instance, you cannot delete a category once created 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: * Can import SF data http://effbot.org/zone/sandbox-sourceforge.htm contains instructions on how to access the data dump and work with the support tools (graciously developed by Fredrik Lundh) * Can export data To prevent the need to develop our own tools to get our data out of the next tracker, there must be a way to get a dump of the data (formatted or raw) that includes *all* information * Has an email interface To facilitate participation in tracker item discussions, an email interface is required to lower the barrier to add comments, files, etc. If there is a tracker you wish to propose for Python development team use, these are the steps you must follow: * Install a test tracker If you do not have the server resources needed, you may contact the Infrastructure committee at infrastructure at python.org, but our resources are limited by both machine and manpower, so *please* do what you can to use your own servers; we do not expect you to provide hosting for the final installation of the tracker for use by python-dev, though, if your tracker is chosen * Import the SF data dump http://effbot.org/zone/sandbox-sourceforge.htm * Make the Infrastructure committee members administrators of the tracker A list of the committee members can be found at http://wiki.python.org/moin/PythonSoftwareFoundationCommittees#infrastructure-committee-ic * Add your tracker to the wiki page at http://wiki.python.org/moin/CallForTrackers This includes specifying the contact information for a *single* lead person to contact for any questions about the tracker; this is to keep communication simple and prevent us from having competing installations of the same tracker software * Email the Infrastructure committee that your test tracker is up and ready to be viewed 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 tgdrggrgo email infrastructure at python.org . - Brett Cannon Chairman, Python Software Foundation Infrastructure committee ---- |
About
Python Software Foundation's Infrastructure commitee put out a call for trackers (bug/request/issue/ticket trackers) in June 2006 in order to evaluate alternatives to SourceForge for use by the Python development team. A copy of that request can be found at OriginalCallForTrackers.
Jira was the first choice of the committee. A lot of people complained about using a closed-source and hosted bug tracker, so a call was posted for volunteers to help administer a Roundup installation. Enough volunteers came forward, so work is now proceeding on improving the conversion to Roundup.
The Roundup bug tracker that serves http://bugs.python.org/ is actually hosted at http://psf.upfronthosting.co.za/roundup/tracker/
Bugs found in the living installation of Roundup for Python bugs are reported to meta-tracker -- is at http://psf.upfronthosting.co.za/roundup/meta/ Please report problems with the bug tracker there.