Re: embedded emc and GPL

["Markus Meyer" <meyer-at-mesw.de>]

Hi Pete,

I'm afraid I didn't really understand what your original question was, but
as far as the GPL is concerned, I see two "problems" with using it:

1. Since the GPL includes a copyright claim, it's not that easy to change
license from public domain to GPL. Furthermore, GPL places some restrictions
on code (re-)use, and IMHO that would not comply with the original public
domain style.

2. The big "problem" with the GPL is, that it limits commercial use by
explicitely stating, that a software derived from a GPLed software must be
GPLed, too. GPL-enthusiasts take that "derived work" term very seriously, it
holds, even if the amount of GPL code used is very small compared to the
size of the "derived" program. So, consider, EMC would be GPL. If you only
take a few lines from the original code (f.e. the G-Code interpreter) and
build it into your own software, you had to make your whole software GPL,
too. One may find that good or bad (Personally, I find this policy just as
extreme as software patents, in a certain sense). But I'm sure that this
would scare many potential EMC users and resellers.


Best regards


Markus



> -----Ursprüngliche Nachricht-----
> Von: emc-at-nist.gov [emc-at-nist.gov]Im Auftrag von Pete Cook
> Gesendet: Montag, 4. März 2002 19:36
> An: Multiple recipients of list
> Betreff: Re: embedded emc and GPL
>
>
>
> Okay - Where is the problem - the code that NIST was involved is not
> copyrightable because of American tax dollars at work (play? ) in the
> development of the program. Does the GPL prohibit public domain?
> The source
> code is available and well as the programs - for free - which
> would seem to
> meet the spirit and intent of the GPL. Or is there some pressing
> legal hooha
> that someone is trying to exploit to the harm of all others involved?
>
> WHat's the problem???
>