'You like to paint - here is something you can work with, paint over, whatever.Metaphorically it is like taking an original 'Fresco' painting.It is about taking the WHY ? of consensus & translating that into a vessel of HOW ? that affords the widest concievable range for WHAT ?.* # 1 - # 3 are components of an inclusive OSS Development worth articulating for a better, clearer, grasp of both short-term & longer-term aspirations. #3 NEEDS to be THOROUGHLY defined & cataloged.1.) 'Lego' Modularization, externalizing as much as possible from the core engine & doing so to not only facilitate diversity of 'MODs' but also 'PORTABILITY'.Here are some key distinctions & possibly the basis of protocols:.That is the diff that makes the diff to longevity & progress through a process that is integral, inclusive & generative.The approach thru 'BerliOS' will be a boon for the whole Wz community - not just now but for years to come.Personally my vantage is to take the long-view, try not to lose sight of the forest just cause I'm so focused on a couple trees that I especially like.They also result in collective experience that feels positive & progressive OR frustrating & futile.

These are the differences in POV or Mind-sets that are directly manifest in Modus-Operandi that range from dysfunctional to functional.with all it's inherent pitfalls of turf & power. The BerliOS repository & apparatus will make it a whole lot easier to make distinctions & accomodate all foward progress without the need for a managed hierarchical team org.In OOS Dev Structure & Protocol that distinction is made & accomodated.Here's how I percieve the diffs: Heurisms *.Many have only known 'MOD' here because that is all that was possible till recently.1.7 More Kage on Code-base Functionality.1.1 Rman: The Diff That Makes A Diff in MOs.

Warzone 2100 source code