X-Original-To: pgsql-www-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id E1F129FB1FB; Sun, 17 Sep 2006 10:17:10 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 06847-07; Sun, 17 Sep 2006 10:17:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from mx-2.sollentuna.net (mx-2.sollentuna.net [195.84.163.199]) by postgresql.org (Postfix) with ESMTP id 8087E9FB1EF; Sun, 17 Sep 2006 10:17:01 -0300 (ADT) Received: from ALGOL.sollentuna.se (janus.sollentuna.se [62.65.68.67]) by mx-2.sollentuna.net (Postfix) with ESMTP id 91505F40BD; Sun, 17 Sep 2006 15:16:58 +0200 (CEST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: Re: Still waiting on pmt.postgresql.org Date: Sun, 17 Sep 2006 15:17:07 +0200 Message-ID: <6BCB9D8A16AC4241919521715F4D8BCEA0FBB8@algol.sollentuna.se> In-Reply-To: <484A728B-9585-4903-B731-562114EDBE04@ehpg.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [pgsql-www] Still waiting on pmt.postgresql.org Thread-Index: AcbZtica/zALbgsbTHi2kxwFH1DBTAApTyBw From: "Magnus Hagander" To: "Gavin M. Roy" , "Joshua D. Drake" Cc: "Marc G. Fournier" , "PostgreSQL WWW" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.177 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, SPF_PASS X-Spam-Level: X-Archive-Number: 200609/138 X-Sequence-Number: 10716 > Configuring and getting this bad boy working is on my todo=20 > list today after the funds related stuff. Do we want to=20 > htaccess it from the get-go, requiring a login to get on the=20 > trac?=20 Yes. Since we intend to put internal documentation on it. > I'll install trac- admin which will give a basic=20 > ability to admin it to everyone who should have access. I'm=20 > thinking of upgrading it to the .10 beta =20 > release. Do we want custom fields for the tickets? At the very =20 > least we should probably add a URL field for reporting=20 > specific issues. Remember that (at least for now) it's only intended for internal stuff. If this is something that can easily be added later, let's just get the stock version up and we can take it from there - we'll know more once we've been using it for a while. //Magnus