JMorris,
It upsets me to see how badly things have "progressed" (and I use that term loosely) in the last few days and the consequences it brings -- you stepping down, Hervet leaving (if only temporary, etc.). It also saddens me to see the topics that are posted on the front page of XOOPS every time I visit the site lately. It does not give new users, potential new users, or existing users a "a warm fuzzy". I have to say the term "pis$ing contest" comes to mind, nothing to do with you, the developers, moderators, or users.
It is discouraging to say the least when users are told to have patience...we've been told to have patience for over a year for the new site. We are not criticizing about the time that it takes, the anticipation of a new site being released is enough to give everyone "the willies". The criticism is that users are not informed of the "behind the scenes", again, nothing against you, the developers, moderators, or users.
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.
It is with great regret that I've had to move client sites and encourage new clients to move to other CMS applications, ones that are actively (visibly) developed, ones that are actively (visibly) supported, and MOST IMPORTANTLY, ones that do not have criticism, resignations, and turmoil posted on the front page. Good grief, I had two clients today email me about the status of XOOPS because they visit this site often!
The last few weeks have brought about MANY changes to XOOPS and the repercussions are scary, including Skalpa falling ill, losing you as a Moderator, losing McNaz and now possibly Hervet. This small community can NOT afford to alienate those who contribute time, skills and effort.
While we are glad to know Skalpa is recovering and returning to XOOPS code, there are those wondering why, if he can email you, why he can't write a small post to this community. Personally, it doesn't affect me in the least, I'm a designer not a developer. But there's still many unanswered questions amongst the users.
It doesn't matter whether I believe in XOOPS or not, it matters how I can provide the best solution for my clients in a timely fashion without worrying about the turmoil that is currently in Xoops. I love Xoops, the community (for the most part) and being an active contributor, but when the front page looks like a replica of the National Enquirer, it's time to decide what matters most.
I have spoken with Hervet and passed on my feelings about him leaving Xoops. No, I won't post my conversation here because it's a private conversation between him and myself. The bottom line is that WE ALL need to bond together and bring XOOPS back to the forefront of CMS applications. Skalpa alone can not do it, it requires the effort of all users of Xoops.
To trspice:
Quote:
please weed out the useless modules and set some strict guidelines for module production and a beta team (just some members) to test them before publishing.
I think 'bad' modules are a contribution to Xoops' bad name today because when someone (myself included) has a problem with a module the curses go to XOOPS and not the module writer.
Again, this should be coming with the new site. There are no "bad modules", there are modules that are outdated, but at one time they did work and still work, depending on the XOOPS version you are using. Researching the comments will help weed out the "outdated" modules until the new site becomes available. I have not seen (and can not see) a developer releasing a bad module. All modules are a generous contribution from the developer and when it's stated that it's Alpha, Beta, or for a different version, should be evaluated as such.
Yes, long live Xoops, let's just get the ball rolling
