X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 4CDA9D1B904; Fri, 27 Feb 2004 18:50:05 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 74716-08; Fri, 27 Feb 2004 14:49:46 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id C531AD1CCCD; Fri, 27 Feb 2004 14:49:44 -0400 (AST) Received: from [63.195.55.98] (HELO 192.168.1.29) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 4502620; Fri, 27 Feb 2004 10:50:53 -0800 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: pgsql-www@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Collaboration Tool Proposal Date: Fri, 27 Feb 2004 10:48:57 -0800 User-Agent: KMail/1.5.4 References: <200402260912.54001.josh@agliodbs.com> <17173.1077862747@sss.pgh.pa.us> <200402262311.14871.josh@agliodbs.com> In-Reply-To: <200402262311.14871.josh@agliodbs.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402271048.57042.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/223 X-Sequence-Number: 3788 Folks: ALTERNATIVE BUG TRACKERS: Jira: Core did look at and consider (and debate) Jira. Atlassian are enthusiastic PostgreSQL supporters and offered to host Jira for us. However, Jira is not OSS and for various reasons it would be difficult to host a Jira installation at Hub.org. We're very reluctant to endorse any non-OSS, externally hosted solution becuase of the distinct possibility that the company will have a change of management and drop us. There is also a significant political issue; by adopting a non-OSS piece of infrastructure, we are effectively saying that OSS software isn't good enough, in the eyes of many members of the public. RT: I've been using RT for OSCON, and am not wowed by it. Of course, I can say the same of BZ and GForge-Tracker. From my perspective, it's neither better nor worse than the other solutions, although the interaction with e-mail is nice. More importantly, *we* would have to do the port to PostgreSQL. This is pretty much prohibitive; how long have we been working on an update to the main site, Techdocs, and/or Advocacy? If we pick a solution which is not ready *right now* I fear that we will still be having this discussion in late 2005. I also don't see any good reason, politically, to adopt a tool by a community who are not at all enthusiastic about Postgres -- when there a those available that are. Both of the above alternatives have 2 major issues: 1) They are each bug trackers and bug trackers only. They do not deal with community or code management at all. I would tend to prefer an integrated solution where one is available. 2) For whatever reason, most of our volunteer web crew seem to be PHP developers. We haven't attracted many Perl or Java programmers to helping with the site. This may be a chicken-and-egg thing, but unless there are several untapped Perl Hackers/Java programmers waiting to jump in and do integration work for RT, Jira, or whatever, any non-PHP solution automatically carries a detraction. -- -Josh Berkus Aglio Database Solutions San Francisco