Thanks James for the update.
Quote:
It is discouraging to say the least when users are told to have patience.
It is, but unfortunately that is something which needs to be endured.
As you no doubt saw the recent post which was started by me, resulted in James stepping down and Herv leaving (not my fault but....), for this I apologise that was in no way my intention, however these things were on the horizon, and the time bomb was ticking on that one.
Since this I've spoken to James, David Bender and others, and have had some insight into the works going on behind the scenes, and be rest assured work is being done, and improvements are coming.
There are still things the community can do to keep us all moving, this includes end user support, developing themes and modules, reporting bugs, following the SVN and submitting code fixes/improvements.
I'm not saying that I agree with what has happened and is happening, but at least I now understand a little more.
I still love xoops, despite my concerns.
Quote:
The criticism is that users are not informed of the "behind the scenes"
This is what James is doing, with this post, he is informing you, although rather vague, I'm pretty sure there will be more to follow.
Quote:
The XOOPS community does not require a timetable until the next release, but a roadmap is desired and it gives comfort to know that XOOPS is proceeding forward.
To my understanding, a road map is on the horizon also.
I do agree it is rather disheartening to keep seeing this, we've lost some good developers, hopefully we'll recruit more, and some of those older ones will come back when they see XOOPS progress.
Basemen:
Quote:
read these numerous complaint threads that crop up nearly every day, or threads like Herve's or James' where people have "resigned" or "quit".
Mine wasn't a complaint thread, more a suggestion thread and an offer of help and support, or at least I'd like to see it that way.
Carnuke:
Quote:
You make this new version of XOOPS that is supposedly coming, to sound like a quick fix that will solve all the moans and groans that we suffer.
It's not a quick fix, more like a bridge if you wish, to being the two branches, 2.2 and 2.0.16 together, making a clear path forward for 2.3, also making it easier to support, and develop for, and of course then upgrade.
Quote:
Xoops is in an leadership and management crisis.
I couldn't agree more with this, and I feel the major contributor of that, is lack of and bad communication, its something thats hoepfully being addressed finally?
James:
Quote:
Sigh... I guess words of encouragement and hope are wasted here.
No there not, bare in mind not everyone reading this post will reply, not everyone will log in, and not everyone has read this yet.
Quote:
And quite frankly, I'm ready to join them in their silence.
Rise above it, James.
Quote:
I would personally advise 2.0.16 - but the next version *may* (as I don't know yet ) provide some of the things that 2.2 has, that 2.0.16 doesnt...
From my understanding of whats happening, the merge should bring some of the benefits of 2.2 and possibly a few more too, which could make 2.2 look antique (:wink:).
As for which benefits, I'm uncertain as of yet.
Now come on guys and gals, we asked for an update, we have one, it's not a fix, there is a long way to go, but hopefully this will be the start of better communications.
