I'm getting on a plane to Sweden shortly and will be out of touch, so I have to give you this all at once
I think we need to focus on modules for a while. The core development (which has been excellent by the way) has run a long way ahead of the modules. Also, 1.4 will break compatibility with legacy XOOPS modules. We NEED to have a set of 1.3+ compatible modules available that will:
a) Cover the essential functionality that most people require from a CMS (as a minimum).
b) Be carried forward into the future, ie. be maintained and have an ongoing development path.
The compatibility breakage will narrow down the number of available modules for some time. This is not necessarily a bad thing, as a lot of the old XOOPS modules are not being maintained and are way overdue for retirement. Back to lean and mean.Proposal
I also suggest that the accumulated $$$ and advertising revenue could be invested in further development of the system. This could include:
1. Commissioning PAID development of essential modules for the community’s benefit, where there is not an existing candidate available, or paying people to update existing modules to 1.3 spec.
2. Maybe award of a ‘best module’ or ‘best contribution’ prize or ‘bounties’ periodically for getting particular jobs done, which may accumulate if there are no satisfactory developments etc, which could be announced through the email newsletter etc.
Obviously there would need to be a discussion about what module functionality is essential, where are the gaps and who will do what, but I don't think it would be too hard to come up with a process.
[Please note that since I am suggesting this, I will not participate in paid development schemes, in order to avoid any conflict of interest].