19
First, I'd like to thank everybody for the support you're showing. It's really warmimg me up after having felt so bad during two days. I want to promise you again we'll do our best to go in the right direction, and ensure everybody is recognized, whatever his contribution is.
Quote:
skalpa, I am glad to make my contribution, as always.
Although I don't think it necessary for the "new" developers to take some tasks right now, but I am ready there.
Thanks a lot. I don't think we should assign tasks either, it's not the point. It's first about giving you CVS access so you can apply the bug fixes you made or have by yourself, without having to wait for us. This is how we all started. You'll also become a privilieged collaborator who we trust, and can ask about some of the problems we encounter.
Quote:
I don't think beating mambo is what we are aiming for, rather we're just wanting to realise XOOPS to its maximum potential
That means beating up mambo m8
LOL
More seriously, mambo is certainly not what we're aiming at. For sure, having good designers and prices would be nice, but IMO mambo is reproducing what XOOPS did a few years ago. In some time, they'll get a big monster that makes nice things but is a pain to maintain and debug. I'm more interested by things like Typo3 (except for the fact it is over-complex and cannot be easily understood by normal humans, which is the opposite of what we're trying), or ezPublish (Xoops and ez will soon be the 2 only PHP CMS I know of that generate their own classes, except I've pushed this quite further than them and have been building several features of our system on this idea).
skalpa.>
PS: I only have the "features list" to finish before the Xoopshere roadmap is ready (I though it would be necessary to detail this part more, after reading a few recent comments here. So it may not be coming tonight, but it's a matter of days too).