> included is a project proposal (in docbook) > > START OF VOTING: 2005-08-09 15:00 > END OF CALL: 2005-08-16 12:00 > > [_] +1 (YEA) > [_] +0 (ABSTAIN ) > [_] -1 (NAY), because : > [_] VETO, because:
Because of the lack of documentation, it is very hard for me, and other developers in my company working with MMBase, to fully grasp the life cycle of nodes and caches, and therefore to judge whether your proposal is a viable approach (are MMNodeEvent, MMRelationEvent and MMNodeEventListener required? What should they look like? etc.) As this project will affect the MMBase core, I think a more incremental approach is required, defining several stages of the project: 1 proper documentation of current node and cache life cycles and event model 2 analysis of problems caused by the current implementation 3 definition of a strategy/architecture resulting in a pluggable architecture solving the problems found 4 implementation Maybe you could cover stages 1 and 2 in a presentation, proposing your solution. Discussion may result in a strategy/architecture, after which a proper project proposal could be formulated which can be voted on. Kind regards, Wouter -- Wouter Huijnink Func. Internet Integration W http://www.func.nl T +31 30 2109750 F +31 30 2109751 _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
