8
For those monitoring this thread, there is now a new project at dev.xoops.org called XoopsDBase.
I will manage the project, but obviously it will move forward with help from others.
As it gets clear on the design strategy, I intend to produce a design document, that doesn't mean people can't hack and prototype and learn from independent work, but in the long run a module like this needs to have some advance thought. Such as making it as Object-Oriented as possible, anticipating features in advance and building a lot of flexibility into the design up front. learning from the lessons of the other more experience module builder and hopefully the Core Dev Team.
I'm looking forward to working with anyone who willing to create an 'exemplar' XOOPS module, my wish is that the design document becomes the 'documentation' so the documentation is there at each step of the way.
My experience is that this requires a bit of patience and willingness to co-create software, not that I intend to make this a design heavy process upfront, but using more of an extreme programming approach. Even rapid development needs some guiding design.
krayc
