Quote:
xguide wrote:
Quote:So far, we haven't seen much that's worth a lot...
Me too. No developers, new core, no documentation. Sorry, if machine translation hurts you. I was not my intention to wound your ego or blame your efforts.
If you haven't seen anything in the XOOPS community that is worth a lot, you just haven't been looking. This isn't machine translation, because machine translation follows basic logic. Only broken machine translation keeps repeating the same points over and over again. And where my ego came into this is beyond all logic. Please reread this thread carefully.
Quote:
My young son start to use XOOPS with friends for a personal project at school and ask me to help.
Smart kid!
![](https://xoops.org/uploads/smil3dbd4d6422f04.gif)
Quote:
I thought there was mature people managing this project. But your words let me understand it is not a place to old man like me.
Now *that* is childish. Now the maturity of the whole project management is assessed by you. And all by inventing new vague points, insinuations and false accusations. That's what I call immature, but this comment probably falls on deaf ears.
Quote:
I am genuinely glad you are.
Quote:
No developer contact me for security question.
How would they know that they needed to contact you? I have several support questions, feature requests and general usage questions. Can I contact you about those as well? How can we contact you? You might just prove a very valuable resource to everyone. And free of charge too, if I read your previous posts correctly
![](https://xoops.org/uploads/smil3dbd4d6422f04.gif)
Quote:
Do not worry. You can think it is stable if you compare to situation 2 years ago. But last time you say it was secure, Mr. Gijoe post with your account (find on the XOOPS forums).
Thank you for bringing this up, because this illustrates my point beautifully. The bug was demonstrated and fixed. All by the community. The bug wasn't reported before and was closed as soon as the developers knew what the bug was. And that is how it works, so if you know of any security vulnerabilities, please let the developers know.
And security vulnerabilities are a fact of life for any and all cms products, open and closed source. The bug and hole free script has yet to be written. So don't act like XOOPS is insecure. It's very stable and secure by any measure. We do not guarantee 100% security, nor does any other CMS out there. And XOOPS has a very good track record. So use facts and behave like a true member of the community. Or not, but then you lose the right to b*tch about it.
Quote:
Why you think developers of php and MySQL still release new versions? You understand technologies evolves and software evolution is a reason for XOOPS security problems.
Aha! So what you're saying here is that XOOPS is safe, but that the underlying software may not be, which in effect may cause XOOPS powered sites to be insecure. Well, nobody can know which holes will appear in the future based on not yet released updates from these developers. That's just another fact of life, nothing that singles out XOOPS as being insecure. In fact... quite the opposite.
Quote:
Xoops is good for people without skills or time to learn to build simple and small site. But it is important developers think of new code for future.
I agree with this statement, but probably for different reasons. XOOPS is simple to master, flexible to expand and easy to maintain. Does that mean XOOPS is perfect? No. Does it mean XOOPS is finished? No. Does it mean XOOPS is dead? No.
New ideas will need new code. New demands will require new code. New code requires new testing and new feedback. This requires new participation from the community.
In conclusion:
is XOOPS dead: NO!
Is XOOPS insecure: NO! (not more so then most other CMS's, better then some -all *known* security holes are patched)
Is XOOPS stable: YES!
Is XOOPS management ego driven and only out for money: NO!
Is XOOPS core development dead: NO! it's eh.. resting*
This concludes this essay. I have put all your worries to rest, based on arguments. Lack of proof does the rest. And I am not even part of the XOOPS management
![](https://xoops.org/uploads/smil3dbd4d6422f04.gif)
Herko