public inbox for [email protected]
help / color / mirror / Atom feedFrom: Joshua D. Drake <[email protected]>
To: Marc G. Fournier <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: [Gforge-admins] Re: PgFoundry Move
Date: Mon, 16 Jan 2006 12:30:50 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<1137441491.3769.15.camel@swithin>
<[email protected]>
>> - unsupported (and in fact unknown) mailman version
>
> Wasn't Joshua planning on fixing that?
For the migration yes. I haven't touched the current machine as it is
production.
>
>> - missing features like SVN support
>
> SVN support is there, and last I heard on that, Joshua was reading
> through the docs on how to setup that ...
I did setup and install SVN but I did not getting it working "with"
gforge and as I stated in an email I would leave
that to someone more knowledgeable about gforge itself.
> That it has ... and the solution to that constantly seems to be "lets
> bring someone else new onto the admin team since they apparently have
> spare time" ... if JoshuaD has the spare time to set this up on one of
> his Linux boxes
Well first a good portion of this isn't "spare time". It is that I have
resources in the management and infrastructure area regardless of
myself. It is the same reason we
are about to host the search.
> (which isn't acceptable, the reason I agreed to move pgfoundry in the
> first place was that the box it moved to was running FreeBSD to match
> the rest of our *core* servers, including wwwmaster)
There is no reason except technical bias to keep it on FreeBSD and a lot
of reasons (including a larger support pool) to put it on Linux.
> , then how come, in almost 12 months, he hasn't had the time to do the
> same getting it up and running on a server that was bought
> specifically for that purpose? It isn't lack of access, since everyone
> involved with that side project has root access to do what is required
> ...
We are also talking about physical access.
>
> The problem isn't moving the vServer ... the problem is that JoshB
> wants to move the vServer *and* upgrade pgfoundry at the same time ...
> if it was a matter of just moving the vServer, that could have been
> done simply enough 12 months ago with a simple rsync, same as we did
> when we moved wwwmaster to another server ...
We aren't really talking about JoshB's efforts as much as trying to get
PgFoundry moved in general.
Sincerely,
Joshua D. Drake
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: PLphp, PLperl - http://www.commandprompt.com/
view thread (57+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: [Gforge-admins] Re: PgFoundry Move
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox