This is a read-only archive. Find the latest Linux articles, documentation, and answers at the new!

Re: Forty-Two

Posted by: ToothlessRebel on February 04, 2006 11:34 PM
Oh, but it IS his project. The thing is that he took HIS project and once it got to a certain point released it to the public. Not in th etypical release, however, no, He choose to release his project in such a way that not only could you use it for free, but you could also modify it. Granted, there was one stipulation, and a small one at that, if you released your modification you had to grant the public the same right as you had, you had to allow the free use and modification of your project.

Ahh, but there's the stickler! The instant you modify HIS project it becomes YOUR project. Down the road the first developer may decide to incorporate your modifications into his project. That's fine, because you grant that right through licenses like the ones discussed here, and hey, you've got some pretty cool ideas.

Now, what we have is two projects. Both have been modified to be very similar, but they are still seperate projects. The fact that I choose to excercise my right to use your ideas in my project does not make my project yours, in any way shape or form. It doesn't even make that portion of my project "yours", as you have given the freedom for me to build on it, and to make it my project.

So long as "LT" is heading the developement of this software it is HIS project and HIS call as to what is right or wrong for it. FORKING, although my project is the ancestor of yours, it is still my own.


Return to Torvalds versus GPLv3 DRM restrictions