Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <49B0117B.8040901@pearsoncmg.com>
Date: Thu, 05 Mar 2009 09:52:59 -0800
From: Chris Darroch <chrisd@pearsoncmg.com>
Organization: Pearson CMG/CTG
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.1.19) Gecko/20081226 SeaMonkey/1.1.14
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: [summary] accept mod_fcgid codebase into httpd project
References: <496ABECF.9060202@rowe-clan.net> <4976322A.8030505@rowe-clan.net>
 <4978CD2D.4000600@pearsoncmg.com> <49792A45.1060904@rowe-clan.net>
 <497E2BBB.6050200@pearsoncmg.com> <497F47F0.9010808@pearsoncmg.com>
 <ED4D3138-6573-455C-BB62-6DE21DFE3ADA@gbiv.com>
 <499C7A05.8040605@pearsoncmg.com>
In-Reply-To: <499C7A05.8040605@pearsoncmg.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Chris Darroch wrote:

> Roy T. Fielding wrote:
>
>> Yes, that is what I prefer as well.  All paperwork is done, so please
>> let us know when you have an export.  I (or one of the other svnadmins)
>> will have to massage it a bit to prefix the sourceforge ids, so just
>> point us to the dump file when you have it ready.
> 
>    It should be in people.apache.org:/home/chrisd/donations/mod_fcgid now.
> 
>    I used the default "full" cvs2svn conversion; if you want one with just
> the trunk and without the small number of CVS tags in the mod_fcgid
> repository, let me know.  There weren't any branches or anything too
> complex in the SF repository.

   Sorry not to follow up on this for a while; been busy with other
stuff.  Is there anything else I can help with here?  I'd be happy to
tackle munging IDs if someone can provide a quick tutorial on what's
needed.

   I should probably also ask about setting up mailing lists,
a Bugzilla entry, and getting Web site mojo for mod_fcgid.  It would
be good to have stuff up and running so we can let people on the old
SourceForge mailing lists know about the adoption, among other things.

   Once the code's in SVN I figured I'd try to do the following:

- apply license changes
- create legacy 2.x branch
- apply whitespace changes to match httpd standard
- begin applying functional patches

   Thoughts?

Chris.

-- 
GPG Key ID: 366A375B
GPG Key Fingerprint: 485E 5041 17E1 E2BB C263  E4DE C8E3 FA36 366A 375B