After I've added my own code to models.py, views.py and other files generated by django, can I protect them using the GPL? Or is there a clash given there is code in there that has been auto generated by django which is not licensed under GPL?
views:
178answers:
4
+4
A:
Code that is generated by a tool is not covered by the same license, and can therefore be put under any license you want. This is why you can use GCC to compile code, but the result can be licensed any way you chose, not only under the GPL.
Augustus
2009-07-22 10:47:27
+3
A:
GPL only touches the actual program that is licensed under it. If you were to modify django and redistribute your changes, you would have to respect the GPL. You should check djangos licensing details or FAQ to be absolutely sure, but usually the output of such a tool is not covered by the license. So you can probably do whatever you want with those files.
Another example: When using GIMP to produce an image, the image is not covered by the GPL. But mofifying GIMP (e.g to support vector graphics) and passing that on to friends would mean your code is under GPL, too.
galaktor
2009-07-22 10:54:40
+2
A:
Since Django uses a BSD license for its code, you could even take the code of Django itself and relicense it any way you want. That's what Microsoft and Apple are doing with code taken from *BSD operation systems. As long as you comply with the simple conditions of the Django license, you are fine.