Re: Thoughs on V2 development

From: David Abrahams (gclbb-jamboost_at_[hidden])
Date: 2003-09-29 09:09:10

Vladimir Prus <ghost_at_[hidden]> writes:

> The problem is that the situation is like a deadlock. I can try to refactor as 
> I implement feature, which I actually do. Another alternative would be to 
> stop implementing features, and refactor to get a better architecture. Why 
> not? Because I have some reservations
>
> - No features/user-level improvements for a next milestone is just
> not good
>
> - I am not sure that archiecture improvement will have noticable effect on 
> involvement of other persons
>
> - Even if I start refactoring, I might well refactor parts that *I* consider 
> messy, and in a way that *I* consider right. Which might end up even more 
> confusing for other people.
>
> So, I did not have much motivation for a global refactorings. And
> because of that nobody dares to write significant patches. Deadlock?
>
> I don't know how to resolve this. I can try to raise priority of
> refactorings, and there are some things that I wanted to improve for
> some time. But that also requires that other interested parties
> review my refactorings or suggest places to improve or help with
> this process. Without that, I might return to the current mode of
> operation.
>
> And, Dave, you say that "a few people I know who are actually
> motivated to make significant contributions". Can you tell who are
> they? My impression is that nobody has enough time. Some pretty
> simple and good ideas, like separating the build system in 4 layers,
> were never implemented, for example.

I don't want to speak for others, but I think Ali, Rene, and I all
wanted to have a greater impact on the project than we've been able
to. People have time partially in proportion to how much of a
difference they perceive their work will make. The 4-layer split was
going to be done by Ali after I put the infrastructure in place, but I
think (I shouldn't speak for him, but I have a pretty good idea that)
he decided the other BBv2 issues were too daunting to make it worth
the investment. He had limited time to get his build system going at
work, and basically had to make the tough choice to return to using
'make' because he knew he could get the job done. Similarly I have
more time to work on BBv1 these days because I see positive results
relatively quickly when I do that (not that I'm spending much time on
it -- it's already working pretty well for me).

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com