1
Could I get a definitave answer on this:
The FAQ states:
"If I create a module for XOOPS, do I have to release it as GPL?
The GPL has exceptions that allow you to use GPL software and write your own extensions without releasing your code as GPL (I won't go into what's a module or not which is covered under GPL).
What you can't do is take the XOOPS core, put your code into in and sell it as yours. The only way you can sell the XOOPS CMS is as a complete package keeping in tact all copywright and copyleft code, credits, names, etc. (as you can see, there is NO value here).
Now, by the nature of PHP and XOOPS being both modules, theoretically, you could sell just your module alone under whatever license you choose but, since your distributing source, it'll be hard to keep the cat in the bag so to speak again loosing the value proposition.
Now, what myself and others do is give all the software away and charge for install, custom dev and other services to make a profit since software is a commodity.
Don't get caught in some trap thinking you have a killer mod that everyone will pay for because all that will happen is some smart dev will recode/copy what you've created and give it away."
But then I read in the SourceForge Forums:
"XOOPS currently uses the GNU-General Public License. This means that (as many of you know as you've taught me this yourself) when a module shares the core processes to a degree of dependancy, the module automatically fall under the same license."
Which is it?
All modules must be GPL or they do not. I ask because there a a few modules that have "GPL with XYZcorp ammendments". Is this legal? I for one do not think so, but I need a definate answer from someone with a better understanding of GPL.
JMass
PS - The idea of a LGPL core and a GPL module collection is a great one. However I think the LGPL core should be minimal.