Subject: Re: GPL and proprietary licensing.
From: Bernard Lang <>
Date: Fri, 31 Mar 2006 17:55:09 +0200

The problem of assigning copyright to anyone is that he controls the

And the same occurs when you allows distribution under a yet unknown

I personally consider that the DRM restrictions in the GPL v3 are a
betrayal of trust.  As far as I am concerned, it is not even a free
software licence as it stands.


* Mark Wielaard <>, le 31-03-06, a écrit:
> On Thu, 2006-03-30 at 16:15 -0400, Taran Rampersad wrote:
> > Personally, I don't see this as a fault of the GPL but rather a fault of 
> > copyright assignment when people are irked by such things. Something 
> > similar happened with MEPIS last year that irritated the contributing 
> > community, where they thought that the work they did would be GPL'd but 
> > was not. My contention is that developers should be aware of who owns 
> > the copyright when they contribute, and if they aren't comfortable with 
> > who owns the copyright itself, they should not contribute or personally 
> > GPL their contributions. For example, Drupal modules are done in a very 
> > similar manner. I see no fault in the GPL itself; rather, I see a fault 
> > in the issue of people perceiving a copyright license as a copyright 
> > itself.
> > 
> > Thoughts?
> It can be beneficial to have all copyright owned by one trusted entity.
> Either to make clear that all contributions/copyrights are tracked, for
> enforcing the GPL or for future changes to the distribution terms that
> might benefit the larger community. But as you say people should always
> think of the consequences of doing that. If the goal is having one
> guardian of the work that acts in the interest of the whole community
> then it is a good idea to actually get that in writing when you do the
> copyright assignment. If you assign copyright to the Free Software
> Foundation for example you enter into a contract that commits the FSF to
> always publish any of your contributed works or derivatives of it under
> free terms. You might want to ask for an example
> contract and suggest other foundations/companies to adopt such an
> approach to copyright assignment. Getting an assignment contract back
> makes it clear what the rights and obligations of the party receiving
> the assignment are. That will prevent some nasty surprises to the
> contributors.
> Cheers,
> Mark
> -- 
> Escape the Java Trap with GNU Classpath!
> Join the community at

             Le brevet logiciel menace votre entreprise
               Software patents threaten your company
    Soutenez la Majorité Économique - Support the Economic Majority
                     ,_  /\o    \o/    Tel  +33 1 3963 5644  ^^^^^^^^^^^^^^^^^  Fax  +33 1 3963 5469
            INRIA / B.P. 105 / 78153 Le Chesnay CEDEX / France
         Je n'exprime que mon opinion - I express only my opinion