My concern is that the proposed path is one where there's little convergence in the near term and where the single incubating project releases multiple files on their own schedules. That's fine, but that's not one project.
What's the point of being one project if there's no viable plan to make the code marry? I of course know the task is complex and indeed was quite surprised when everyone was willing to say "merge 'em all" but there's no point at all in pretending we're merging if the task is indeed too complex. Sanjiva. On Fri, 2006-02-17 at 12:43 +0000, Rob Davies wrote: > Would it not be more expedient to have Ode as an umbrella project - > but the goal would to be to try and find commonality between all the > projects and see it's possible to merge? > It's a complex problem - no doubt (not because the individual code > bases are complex - but they are completely different) - but we have > a proposal, if it's accepted in its current form, we can as a > community can start working with the code and assessing points of > integration - to see how feasible it would be. If we all decide at > that point it's not practicable to have one project - but need to > have two or three - can't we make that decision later ? I don't know > how the incubator is meant to work (still finding my feet) - but I > would have thought the incubator would be able to work this way. > > cheers, > > Rob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
