Review of GPL code requirements text

[Florian Weimer]

* Alison Bogle:

> "Tracking GPL licensed code can be tricky, especially when components
> are modified during the development process, or when they are combined
> with proprietary code. According to the terms of the GPL, the
> proprietary code can become a "derived work" of the GPL code. In that
> case, the intermingled code must be released under GPL. 

In effect, this is not far from the truth.  Incorporating GPL code may
require to license the combined work under the GPL as well.  This is
especially true if you stick to the letter of the GPLv2 which has got
a severely restricted, but rarely enforced "mere aggregation" clause
when it comes to embedded devices.

> If GPL code is modified in order to make improvements, all GPL sources
> used must be published so that others can rebuild the GPL code.

The obligation to publish sources is independent of the question
whether they have been modified.

> At the same time, they can then take the modifications and can use
> them in other GPL software, essentially stripping the product of its
> proprietary advantages."

Well, yeah, that's the point of the GPL, isn't it?