More people will choose MMBase if the core is mean and lean and a broad range of addons are available (as described in eg. the CMS Container proposal). If the developer community doesn't start growing fast, combined with the availability of useful addons, my guess is that it is too late.

Things like this make me very reluctant committing code in MMBase. You could call me a 'junior committor' compared to most others (i am a committor since a year or two, i can't recall if there have been other new memebers since me). And it seams that every time i commit something it results in discussion.

The point at hand has nothing to do with what you committed. It is just an example of current practices.

btw: discussion is a Good Thing :)

In this discussion architecture should be the dogma. We need architecture, we need vision, we need The Big Plan. After that we can discuss the simple utility classes.

What happended to our vision? What Pierre forces us to think about is the roadmap/vision/whatever, one of my 'stokpaardje'. So what hapened to that discussion?

Perhaps it's a good idea to point to that discussion (is the roadmap online?) in order to expand on it instead of repeating ourselves.

I agree with Michiel: i was just following current practice and was trying to make life less difficult.

As I said: consistency over correctness is a Good Thing too.

Regards, Zoran
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers

Reply via email to