Seems smart to me. No learning curve for developers at NewCo cause they
use it already...we can learn it quick, and the developers all know ib so
should be able to fix marion pretty efficiently and quickly and make it
widely available for ib developers who may or may not be able to afford to
put down $$$ on a code manager.

On Wed, 26 Jan 2000, Doug Chamberlin wrote:

> From: Doug Chamberlin <dchamberlin@...>
>
> At 1/26/2000 12:32 AM (Wednesday), David Schnepper wrote:
> >As for the main task at hand -- that kinda depends on the where the
> >bottleneck is for getting 6.0 out the door. If it's going to be
> >mainly NewCo folk pushing it out, then continuing to use marion may be
> >the best (short-term) strategy. Changing tools is always a short-term
> >disruption. (Though, of course, changing to a better tool could
> >shorten cycles -- "Sharpen the saw").
>
> I see the main task at hand as more long term. I'm thinking about what the
> investment over the next few years should be for the long term health of
> the product, now that it is open source. That is, how should NewCo and the
> volunteer community invest their efforts over the next year or two?
> Focussing on the development and maintenance of the core Interbase product
> seems wise. Focusing on the development and maintenance of marion, to add
> say branching support, seems foolish if there are perfectly capable
> alternatives available.
>
> Short term decisions about how to get 6.0 out the door are a different
> matter altogether. Expediency would be more valuable here, especially if
> NewCo will be doing 99% of the work.
>
>
> --------------------------- ONElist Sponsor ----------------------------
>
> FREE ADVICE FROM REAL PEOPLE! Xpertsite has thousands of experts who
> are willing to answer your questions for FREE. Go to Xpertsite today
> and put your mind to rest.
> <a href=" http://clickme.onelist.com/ad/XpersiteCPC ">Click Here</a>
>
> ------------------------------------------------------------------------
>
> Community email addresses:
> Post message: IBDI@onelist.com
> Subscribe: IBDI-subscribe@onelist.com
> Unsubscribe: IBDI-unsubscribe@onelist.com
> List owner: IBDI-owner@onelist.com
>
> Shortcut URL to this page:
> http://www.onelist.com/community/IBDI
>