11
Mithrandir is right. Since the modules are considered part of the whole application (since they will not function without the core which is released under the GPL), they are automatically GPL, or similarly licenced. This means that you have the right to the source code, if you get a legally obtained copy. Also, you have the right to edit and redistribute the code. Even when you have paid for the module in the first place. To prove this point, show me a place where you have to pay for the code of a GPL-ed application (NOT services like packaging, documentation, etc.). There aren't any, simply because of the GPL. This doesn't mean you can't get paid to develop, write, create, design or customise a module or site powered by XOOPS, all it means is that you can't limit the use of the code other then what the GPL states.
This has actually been submitted to an attorney and checked.
As for the idea about the credits page, most modules have this in the code itself (the credits). It is our intention to add a credits page to each module admin, as well as to the XOOPS core. Adding it to the page source can be a good idea, but it may not be the best. (it would require the addition of a smarty variable to the theme.html, which is assigned by each and every module). Then again, I don't know a better way to do this (although it is very hidden).
Herko