2
Celso:
The "call to arms" launched by Herko to discuss ideas for the roadmap about the core features of XOOPS was done with a pertinent aclaration from the very start: it's one thing to open the table to discussions, and to sum up a lot of ideas and suggestions as to the course XOOPS will take, and another to set up the road map.
The first is a thread in the general forum, it's a way for all of us to participate in the brainstorm and to contribute new insights about what's needed. The second one is a definition made by the core developers using perhaps the suggestions made in the thread, but ultimately based on their own decisions.
We'd all like XOOPS to be our silver bullet when it comes to managing a site's content. We do know it's already better than most systems, but are also painfully aware of its shortcomings. What I can tell you is the core developers, headed by onokazu, are quite aware of everything we've put in the table. There've been several long discussions in the core team private site and in online chats about many of the issues discussed here, and some of the more crucial aspects are being taken care as I write this.
We all know that if the devs tried to please everyone, we'd have the next version in 5 years. So it won't have all the bells and whistles, but it'll be a strong step in the right direction and it will certainly please most xoopsters.
For some, the core team's been moving too slowly. For us, honest, it's been a hectic rhythm since Herko started shaking things up. There's a great deal of work behind curtains, and I've personally seen some of the good things ahead.
So, to sum up, what's for real in XOOPS 2.1? It's not for me to say, since I'm in, ahem, another department, but please be patient, and you can be sure it'll be a good leap ahead and the beginning of a carefully planned route towards a more powerful and creative Xoops.
Cheers.