From: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Satoshi Nagayasu <snaga(at)uptime(dot)jp>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_reorg in core? |
Date: | 2012-09-24 01:02:51 |
Message-ID: | CA+mi_8YiFosp7ueNOjRvNRz124Yqt4_Od3x4bzd6=eQE_HoToQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Sep 24, 2012 at 12:23 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> As proposed by Masahiko, a single organization grouping all the tools (one
> repository per tool) would be enough. Please note that github can also host
> documentation. Bug tracker would be tool-dedicated in this case.
From this PoV, pgFoundry allows your tool to be under
http://yourtool.projects.postgresql.org instead of under a more
generic namespace: I find it a nice and cozy place in the url space
where to put your project. If pgFoundry will be dismissed I hope at
least a hosting service for static pages will remain.
-- Daniele
From | Date | Subject | |
---|---|---|---|
Next Message | Karl O. Pinc | 2012-09-24 01:52:07 | Re: Suggestion for --truncate-tables to pg_restore |
Previous Message | Michael Paquier | 2012-09-23 23:23:58 | Re: pg_reorg in core? |