Page 1 of 1

How should I handle the Community/GPL aspects for very client specific modules?

Posted: Sun Apr 26, 2009 9:46 am
by devolver
Hi!

I've written a module that handles a very specific case of having members companies that associates a number of member users. This is a integration with FEU where my modules create "member" information and lets FEU handle member users. The very specific nature of the module makes me reluctant to commit it to any community but I really want to contribute.

How does the community handle this?

Re: How should I handle the Community/GPL aspects for very client specific modules?

Posted: Sun Apr 26, 2009 2:46 pm
by calguy1000
From time to time, we all write 'custom software' for a client... something that meets their specific needs... and we don't always put these up on the forge (why should we, they're really only useful to that one client).

Because CMS Made Simple is licensed under the GPL, those modules are derivative works, and therefore are still licensed under the GPL.    We're just not distributing the software.

However, if somebody was to ask for that software (and this is where I'm not sure about things)... I think you would be required to send them a copy of it.

Re: How should I handle the Community/GPL aspects for very client specific modules?

Posted: Mon Apr 27, 2009 5:14 pm
by devolver
That is what I have read into the GPL license as well.