Quote:
I don't!
It should say Genius in stead of Evil!
You may maybe not feel like it, right now, but you are.
It is not because your last addition (ERM class) of the XOOPS core was rolled back, that you're evil.
It is inherent on the XOOPS develop model.
XOOPS developments advances in two ways:
-1- by implementation of most wanted things.
-2- by implementation of interesting technologies by visionary developers.
In the latter case the community is mostly taken by surprise.
These novelties are in general not announced or explained and even if it were, maybe somebody could see the use, but very few could understand the reach of the addition. And this means not only to the targeted functionallity or future use, but also to the performance of the XOOPS system in terms of server use or user expierience.
When changements are too impacting, they change the very nature of the XOOPS system.
But now I'm too far on the philosofic part, let's come back to the surprise. It can be good and everyone is applauding or if the community feels it is not right or good enough, then the changement is refused.
This is all what organic growth is about.
The whole history of XOOPS is like that. Even the more promising V2.2.x version, which looked once the leading branch, died off by a revivement of the 2.0.x branch, which lives now further in 2.3.x and soon in 2.4.x
And that is what I mean on the inherence of the develop model. You can walk on the safe site under (1) or try to shape the future with (2) on the peril that the community will not follow.
How can this risk be minimized without minimizing the possibilities at the same time? I don't know.
As said it is very difficult to discuss these directions. If discussion is even possible, because sometimes I get the 'ivory tower' feeling.
But it is the way it is and both sides, developers and community, has to face the consequences.
Maybe this should be the start of a new topic, because I'm way out off topic by now.
