Hence, my question: what do we include in the Core?
Allowing a whole range of escaper code opens the door to other specific
solutions and means that the MMBase Core becomes less what it is
supposed to be (or at least how I envision it, which may ofcourse be
totally wrong).
I feel more for a 'utilities' or 'examples' application, where these
tools could have a place.
But I also know others don't and like to add as much as possible to the
core to make it more useful.
What are other people's opinion on this?
I think the core should be a mean and clean CMS engine. It should be
easy to extend the engine with functionality (such as the mentioned
sitestat utility).
IMO this should be done with
plugins/applications/modules/components/utilities/whatever which are
coupled to a specific MMBase core version. Development of these modules
should be separate from core development, and having its own releases.
Preferably in a development environment like sourceforge (e.g.
mmforge.mmbase.org) with its own bugtracking, featurerequestlist,
downloads and community. Have a look at Mambo (a CMS,
http://www.mamboserver.com) and MamboForge (the repository bases on
sf.net: http://mamboforge.net/)
Just my 2cts.
Regards, Zoran
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
