Quote:> The GPL is pretty much bullshit. It is a very poorly drafted, vague
> document that is more of a political statement than a recipe on how to
> handle distribution of software.
> Obvious example: you are not required to distribute source of a part of
the
> work, if that part is "...normally distributed (in either source or binary
> form) with the major components (compiler, kernel, and so on) of the
> operating system...".
> Is the windowing system a major part of the operating system? Is libc? Is
> Internet explorer a major part of windows?
> Who knows? The GPL is poorly drafted, so it's not specified. You have to
go
> by opinion. Are you willing to be sued on that opinion? Then you have to
be
> conservative. Then you don't link. Then your reinvent the wheel. Because
> the GPL makes you do it.
Indeed, you make a good point, Roberto. Much of GPL is clear and
unambiguous, but there are potential pools of quicksand. There's also
section 10: "If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author to
ask for permission." It would appear that if I gain permission from the
original author to sell a version of program x, that section 10 implies that
I can sell program x regardless of all the contributions of others, who may
not want their code included in the sale of program x.
On the other hand, overspecification can be a disaster for a contract. If
you try to specify every possible condition under which the contract holds,
then every other condition may be considered not to hold.
This was part of what the article in Business Week talked about. As I
recall, the GNU folks indicated that they had found some violators, but also
said that they had been able to convince them to change their ways without
going to court.
Red Hat's annual report carries this warning, under "Risks Related to Legal
Uncertainty":
We could be prevented from selling or developing our products if the GNU
General Public License and similar licenses under which our products are
developed and licensed are not enforceable. ... We know of no circumstance
under which these licenses have been challenged or interpreted in court.
Accordingly, it is possible that a court would hold these licenses to be
unenforceable in the event that someone were to file a claim asserting
proprietary rights in a program developed and distributed under them. Any
ruling by a court that these licenses are not enforceable, or that
Linux-based operating systems, or significant portions of them, may not be
liberally copied, modified or distributed, would have the effect of
preventing us from selling or developing our products.
Their point seems clear, and it's the same thing Business Week was saying:
until it's been through the courts, nobody really knows for sure.
Any attorneys out there who'd like to offer a free (as in beer, naturally)
opinion?
-- Mike --