On Thu, 24 Oct 2002, Justin Erenkrantz wrote:
> --On Thursday, October 24, 2002 9:28 PM +0100 Stephen Colebourne > <[EMAIL PROTECTED]> wrote: > > > 2) One sub-project for each component ignoring language (eg. > > commons.apache.org/collections). But then what happens if that > > component is implemented in two languages? > > IMHO, it would then be up to the component to create divisions > internally based on language. > > That is: > > commons/httpclient > > could initiallty start out with the codebase from apr-serf. If the > httpclient from Jakarta wants to come over, then the serf committers > and the httpclient committers can duke it out. But, the httpclient > is their collective place to play. It's their responsibility to sort > out the code divisions. (I would probably suggest > commons/httpclient/serf, commons/httpclient/java, but I don't really > care to think about it until it happens.) This seems bad. Each component will have to tackle the same cross-language problems over and over again. We'll end up with an enourmous mess of a system in which crossing from one component to another will involve learning a new setup/system. It seems all your doing is turning the current system of components being organised for a language but with no sharing of functionality into a system in which components are ordered by functionality but with no sharing of language. Even worse, each component will immediately become a fiefdom. The first to the commons.apache.org/xxx/java will give it a definite java feel. the first to commons.apache.org/xxx/c will not. Another thing is raised by the serf/httpclient thing. How will they be named. In this example we're merging APR-Serf and Jakarta-HttpClient. Your suggestion of: commons.apache.org/httpclient/serf ............................./java seems unbalanced. To be pure flamebait, serf should rename to C or httpclient should not be the top level name etc :) To be less flamebait, this naming problem will happen as well. The first project in will name the category and then the following projects will hesitate to join. However there's no reason to say that components will be split on language. Take regexp. It's gonna have to fit at least 2 Java implementations in. If these are just allowed to float, you're going to have an anarchy of a mess on your hands. Hen
