From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: "Bort, Paul" <pbort@tmwsystems.com>, pgsql-www@postgresql.org,
	pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Collaboration Tool Proposal
Date: Fri, 27 Feb 2004 11:05:02 -0800
User-Agent: KMail/1.5.4
References: <735D404BD9E7EB44B9CDFC27FC88809B01C4D526@mail2.tmwsystems.com>
In-Reply-To: <735D404BD9E7EB44B9CDFC27FC88809B01C4D526@mail2.tmwsystems.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402271105.02335.josh@agliodbs.com>

Paul,

> Your main concern about RT isn't true, at least here at my office. I
> installed RT, with no prior experience with any OSS tracker, back in
> October, and it worked on PostgreSQL the first time. (PostgreSQL support was
> one of the main reasons I chose it to track issues on my
> PostgreSQL/Perl-based webapp.) I made this point in an earlier post in this
> thread. There is no conversion effort needed with RT 3.0.6, it just works on
> PostgreSQL. 

My apologies, then!   I was operating off of the statements of others, and the 
fact that the only RT impelementations I've used were running on MySQL.   So, 
questions:

1) can you compare/contrast RT vs. BZ vs. Simplified bug-tracking, like 
GForge?

2) What help, if any, would we be able to get in supporting RT from the RT 
community?

-- 
-Josh Berkus
 Aglio Database Solutions
 San Francisco