Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-Id: <6.0.3.0.2.20040715232640.020bbce8@mail.charter.net>
Date: Thu, 15 Jul 2004 23:36:40 -0400
To: dev@httpd.apache.org
From: Greg Marr <gregm@alum.wpi.edu>
Subject: Re: Move apache-1.3 to Subversion
In-Reply-To: <6.1.2.0.2.20040715214708.03111ae8@pop3.rowe-clan.net>
References: <200405241852.i4OIq9P21751@devsys.jaguNET.com>
 <1086559573.2454.25.camel@localhost.localdomain>
 <40C3E441.4020805@modperlcookbook.org>
 <0BE454CC-B83A-11D8-ADE0-000393B4C1D8@red-bean.com>
 <40C4716F.8090007@wstoddard.com>
 <878yezh212.fsf@gemini.sunstarsys.com>
 <6.1.2.0.2.20040715214708.03111ae8@pop3.rowe-clan.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 10:50 PM 7/15/2004, William A. Rowe, Jr. wrote:
>I agree, here, with Joe.  Wondering if it's an appropriate 
>alternative.
>
>I'm facing similar, with a subproject entering incubation, and I'd 
>like to know our decision here, before I go and create a subproject 
>structure under /httpd/ that turns out to be wonky.
>
>is /trunk/httpd/ an appropriate solution?  This bit me, trying to 
>check out some /incubation/ stuff.

Everything I've seen on source control strategies recommends stuff 
like:
/httpd/trunk/
/httpd/branches/
etc.

This seems to make the most sense to me from an organizational 
standpoint, especially once you start adding other top level projects.

As an example:

/apr/trunk/
/apr-util/trunk/
/httpd/trunk/

makes a heck of a lot more sense than

/trunk/httpd/
/trunk/apr/
/trunk/apr-util/

since the logical grouping is by project, then by whether it's the 
trunk or a branch, and then by the name of the branch.

Someone that doesn't know the organization of the source may make 
this mistake once, if it's not well documented, or if they don't read 
the docs first.  After that, they'll probably never make that mistake 
again.  With the other direction, you'll constantly have to deal with 
the illogical organization.