Well I know that B&B was incomplete, and I also seem to remember something about incompatibility with the current build at that time or something...or maybe the coding would interfere with other aspects of Aleph One? Not sure, but I think there was some reason other than it not being finished.
: Yeah, this is the thing that I'm really not understanding. Granted I'm not a
: programmer so maybe there's some part of the process I don't just grok,
: but can someone please explain how it is that we've got people who have
: written code for Aleph that does things that we want (Mark's enhancements
: ala Rubicon X, the B&B features, and so forth), and have submitted them to
: the main fork of the project long ago - so why do we not yet have a build
: of the main fork with these enhancements?
: Is there someone "in charge" of the main build who is blocking this
: progress, either deliberately or just because it takes some effort that
: they're not putting in? I understood open-source projects like this to be
: a fairly democratic thing. So why can't the same people who submitted this
: enhanced code also get a release of the main fork out to the public? Or
: alternatively, if the it's because the main fork developers are somehow in
: the way of this, why can't these (apparently more active) other developers
: just go about releasing their own fork of AO complete with all the updates
: that the main fork has released?
: Is there some sort of politics behind the Marathon Open Source scene that's
: keeping all these devs from getting along and just releasing what's been
: coded?
