By tonyp001 on

I've been doing some work for a client developing a fairly complex module. The original plan was to have their Drupal site hosted on my server, but now they want to host it on their server instead. I don't really care about the hosting, but I'm a little concerned about them taking the source code of the module I wrote. Is it ok to obfuscate/encrypt my module? Does it violate the GPL license agreement? Has anyone done this before?
Thanks for your advice.

⋅ Categories: Drupal 6.x

Comments

mradcliffe’s picture

mradcliffe
he/him
Primary language English
commented

Drupal derivatives must be GPL (Read the Licensing FAQ from 6 on).

From #8: "The GPL requires that if you make a derivative work of Drupal and distribute it to someone else, you must provide that person with the source code under the terms of the GPL so that they may modify and redistribute it under the terms of the GPL as well."

So, no obfuscation as stated in #6.

You shouldn't need to obfuscate your modules. You're providing a service, not a product to your client, and hopefully you have clear terms of payment for your services.

tonyp001’s picture

tonyp001 commented

Now I know.