57
I would like to clarify a point: there's nothing, im my mind, against what mithrandir stated. I'm personally the first one which got a bit afraid of being unable to mantain a package and to develop it... But, after starting, I found some people which I know consider as friends: they looked at the code, we exchanged feedback, we got this little (very useful to us, I believe) module working, we now give a call to the community to help, to share their ideas with us...
A call which could be view from 2 different points:
-on the one hand, we'd like people to help with their knowledge, improving this little project and any other collaborative project over there;
-on the other hand, we'd like to give back to the community what we firstly took from this community: the original module was not so far from working, but it appeared (and still appears) to be unmantained and I believe it would have been a pity to waste such a piece of code; moreover, how about the satisfaction of helping the mass of XOOPS users, non-programmers, which were asking for such a module and just wanted to enjoy it?
Perhaps I wrote to much, but I'd like to close by saying that I absolutely agree with kaotik when he says:
Quote:
The point (I would assume) was to bring XOOPS to the masses, and, if possible, have them directly colaborate on the development of Xoops, be it in the core or modules, independent from any PHP C0derz status, it's the effort that counts...
This is exactly the point.
Have all a good time!
Yours,
ft
P.S: i just finished updating all php files with a license note, credits, "last modified on.. by..." box, etc... I Updated this last one on the server. I hipe this helps to track changes