> For what I know of Imbrium - which is not much - it is a rather cool thing. I only pitty that we > don't see much of it flow back into MMBase itself. I think that while developing such a thing and > integrating it in MMBase you must stumble into lots of bugs and short-comings in MMBase itself, > isn't it?
It is a cool thing and the reason that you don't see anything flowing back (yet) is that we have currently closed down its release 1.x building stage and will focus in the upcoming months on integrating the latest stable release of MMBase into Imbrium. Allthough we encountered some bugs, the list here is not that long and we will make sure that fixes will be routed back to MMBase. Of course that's also in our own interest. We don't like fixing bugs twice ;-) Regarding short-comings we do have a list of items here (of which a number has not been addressed yet). Again, when integration with the latetst MMBase release starts, we will see which elements are suitable for release to the community. Have a look at the Sourceforge location of Imbrium, where you can find a release plan for Imbrium 2.0 with all major updates to its current level of features. If you see interesting things there, drop me a mail and we can discuss how we can integrate these things back into MMBase. We have not yet had time to report on the progress of 2.0 to the Sourceforge environment. If you're interested, drop me mail and I'll give you an update. > > How are you dealing with this? Is MMBase source code branched? > We try to avoid that and so far we succeeded. Any changes we need in MMBase, we implement in separate packages, renaming then nl.imbrium.whatever . By configuring the Imbrium, we can "overrule" default MMBase behavior and avoid forking the base code of MMBase. The same approach is applied to Jetspeed (the portal component of Imbrium), which is also not forked. This doesn't mean that we will not run into problems when integrating the next MMBase release (and the next Jetspeed for that matter). Obviously when overriden behavior doesn't work with the new codebase, we'll have to address that, however "surgery" is then quite overseeable. Rogier
