Davanum Srinivas wrote: > Is this about competing podlings? or existing projects/new podlings?
The Competing Projects thread is a general umbrella of how the incubator should approach any two proposed podlings that overlap in scope, or a proposed podling that overlaps in scope with an existing podling/project. Niclas said it well, let the code speak for itself. It would add an extra burden on the incoming project; "Project Foo intersects the functionality of project Bar. We take a different design approach by using ... which will accomplish ...". (It's not necessary, and probably in poor taste to add "project Foo will trump project Bar by ...".) And the reviewers approving incubation would need to be comfortable that there is a technical reason for two implementations. If there is, great, let it incubate :) Healthy competition of code is always good. We shouldn't treat two of the competing code bases within the ASF any differently than one implementation at the ASF, and one outside at codehaus, sourceforge, or in the commercial sector. Let code speak for itself. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
