View Single Post
aflegg's Avatar
Posts: 1,463 | Thanked: 81 times | Joined on Oct 2005 @ UK
#7
Originally Posted by rtaranu View Post
Well since the code is in python, it's already "open-source". And I was planing on licensing it as such, but right now I was more interested in making it work properly than to figure out how to work these licenses.

I'll take a look one of these days, and probably host the code on code.google.com and take care of the license also.
That kind of attitude's all too prevalent, I'm afraid. If you're not complying with the wording of the GPL - under which gnuite has given you permission to copy his code - you're guilty of copyright infringement.

If you're only interested in making it work properly, don't release it: then you've no obligations under the GPL. If you release it, you've got obligations in exchange for getting the headstart of gnuite's code.

Sorting it out "one of these days" isn't enough, because your unclear code could be copied and pasted into another project before you sort out the licencing on your project. Thus causing problems for both gnuite and the third project.

If a relatively close knit community can't get these things right, is it any wonder there're all the companies ripping off GPL software because they think it's free?
__________________
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
Now known as
Jaffa