David Strauss skrev:
Thomas Barregren wrote:
To avoid this sort of GPL Hell, we have very specific terms on which we work with clients:
(1) The client owns the work we do specifically for them.
(2) The client licenses .module files and their dependencies back to us under the GPL, version 2, and all future versions as published by the FSF.
The terms of (2) mean their internal staff can contribute to the project, but the final working modules are licensed back to us in a GPL-clean way that allows us to return the work to the community.
The other way around works as well. You can keep the intellectual property rights yourself and license the software under GPL to your customer.
Doing it that way requires that the client transfer ownership of even their own employees' work on the project back to us. That's a lot harder to convince a client to do considering that they're paying you to do the work.
The other way around approach is easy to use if you can isolate a module on which only your guys/gals work on. If the project team is a mix of your and your customers employees, I think your approach (which I never had though of - thank you) is better. Regards, Thomas