Re: Cutting the Gborg throat - Mailing list pgsql-general

From Dave Cramer
Subject Re: Cutting the Gborg throat
Date
Msg-id 4FC62F39-68E0-4581-9A4C-6DDFF15AB045@fastcrypt.com
Whole thread Raw
In response to Re: Cutting the Gborg throat  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Cutting the Gborg throat  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-general
On 27-Aug-06, at 11:47 PM, Joshua D. Drake wrote:

> Greg Sabino Mullane wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>> I have been looking at the migration of Gborg lately. It looks
>>> like the
>>> only two active projects on that site are Slony, and pljava.
>>> Libpqxx has
>>> recently moved to their own Trac site.
>> There are definitely more than that.
>
> ? like? I am not saying you are wrong, but I didn't see much.
How about jdbc ?
>
>>> 1. We set a read only date of 12/31/06
>>> 2. We set a shut down date of 03/31/07
>> I don't have a problem per se with shutting down gborg, but there
>> are some
>> questions to answer/problems to resolve first:
>> 1) Have the project maintainers been sent an email yet? (as promised
>> multiple times)?
>
> Well that is kind of the point of this whole thread. To solidify
> this now and get it done (including communication with maintainers)
Speaking as a maintainer I have not been contacted.
>
>> 3) Is there a migration guide or documentation somewhere?
>
> I think you missed my point. There is no migration, except the
> important of the mbox files and moving of the cvs repo. All tickets
> etc... are the responsibility of the project.
>
>> 3) Is the pgfoundry machine stable and finished being moved/
>> upgraded/etc.?
>
> To my knowledge it has never moved but it is current stable.
>
>> 4) Are we changing the subdomain or not? Speaking on my own
>> behalf, this
>> is important because if I port a project, hard-coded documentation
>> URLs
>> need to be changed as well.
>
> I don't know what you mean?
>
>> 5) Is subversion available? This is not a must, but a strong "nice
>> to have"
>> and having it would be a good indication that a) someone is
>> actively working
>> on the site, and b) someone is willing to help pgfoundry move forward
>> in the future.
>
> This is actually part of a thread I started on Gforge-admins. It
> will be available, it just isn't yet.
>
>
> Joshua D. Drake
>
>
>
>> - --
>> Greg Sabino Mullane greg@turnstep.com
>> PGP Key: 0x14964AC8 200608272100
>> http://biglumber.com/x/web?
>> pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
>> -----BEGIN PGP SIGNATURE-----
>> iD8DBQFE8kAbvJuQZxSWSsgRAhl5AKC9miWUAETzwdfZ/oL0R+c2PQDNvgCfd6hg
>> 8iqkEakHQCDlGjtrz7uRdCI=
>> =KeJ0
>> -----END PGP SIGNATURE-----
>> ---------------------------(end of
>> broadcast)---------------------------
>> TIP 3: Have you checked our extensive FAQ?
>>                http://www.postgresql.org/docs/faq
>
>
> --
>
>    === The PostgreSQL Company: Command Prompt, Inc. ===
> Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
>    Providing the most comprehensive  PostgreSQL solutions since 1997
>              http://www.commandprompt.com/
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>


pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Atomicity?
Next
From: CSN
Date:
Subject: database files are incompatible with server, after computer restart