62
I can understand, this might be difficult to handle, but to my mind, the core developers MUST take care of some default modules as well.
The core itself is isolated and useless without modules. It may be fantastically designed and programmed but if 'nobody' uses it, it is a waste of time and effort.
I would like to emphasize that XOOPS needs both sides - good programmers AND users. Since there are too many other CMS on the market, I don't think XOOPS can afford to concentrate only on a sophisticated core and don't care about the applications. And I am not very convinced with the way it is now, where there are hundreds of modules. Some well maintained, some maintained sometimes and dozens just existing since XOOPS 1 and spread across (at least) ten different sites/repositories.