+1 for importing the codebase into 2 subdirectories to start with. However, if we want to merge the two into one, then let's make it a goal that we don't release anything until we've figured out how to cut-n-chop & mix-n-match to make that real. Its clearly not going to be easy and will take some serious effort and cooperation to make that real.
I too greatly prefer the idea of having one BPEL engine (properly layered ofcourse .. the part that does the core language vs. the part that does people-facing activities etc.) as there's little benefit in having multiple of those in ASF given it'll simply reduce the available developer resources. I'm glad to see the two seed organizations be so willing to cut-n-chop to make that real; it bodes really well for the success of the project! Sanjiva. On Thu, 2006-02-16 at 18:37 +0000, James Strachan wrote: > On 16 Feb 2006, at 16:41, Ismael Ghalimi wrote: > [snip] > > Our primary concern moving forward will be whether we start from one > > codebase, or try to merge two existing codebases. > > From a purely practical perspective, its probably easiest to start > off with the 2 codebases imported (when the IP & software grants are > all done) into separate modules then over time we can see how best to > merge things & share stuff, moving shared stuff maybe into separate > modules for easier reuse. Going from 2 codebases to 1 is gonna take a > while. Just like XMLBeans v JaxMe v Xerces or Struts v Tapestry v > Cocoon v Turbine; we don't have to mandate that everything be merged > into one single unified codebase up front - we can work at it > incrementally over time and see how much reuse we can get; it might > be parts remain diverged as there's not always one size fits all. > > James > ------- > http://radio.weblogs.com/0112098/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
