Andr� wrote: "I believe we should rethink our reluctance against introducing new builders with new applications/code/modules or whatever for MMBase. In the future more and more additions to MMBase will be accompanied by builders and data to be able to use them. It is an argument often heard when someone introduces a new addition to MMBase "This can't make it to the core cause it also introduces new builders".
Why should we not introduce cloud context security as the default security for the 1.8 release? We could adopt the strategy, like changes to api's, that with every major release there can be changes in the default builders." Andr�, is it not possible to devise install options, so that variations can be applied by the target developer? In this instance, builders would be a suitable way of introducing options. Downloading extensions to mmbase seperately is prohibitive in the mind of a new developer. It also means that "mmbase" is the sum of all of it's parts, not just a core with added options. It also means that testing mmbase would include all of the applications installed as well. regards Emile _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
