Hi All,
> At 6:50 PM -0500 on 3/18/00, Mark Rauterkus wrote:
>
>>And we might run into further
>>problems in other fronts as we do the human interface and want it to be part
>>of the suite offered by MetaCard. The co-mingling of GPL and PROPRIETARY
>>licenses is something that needs full ADVANCE awareness, and it isn't yet a
>>bridge that we've scouted and accounted for just yet.
From: "DeRobertis" <[EMAIL PROTECTED]>
> We deliver Scott his UI under any licence he wants. Just because we
> licence something under the GPL to someone, does not mean we can't
> licence it to someone else under another licence.
Yes. Very good. Thanks.
Silly me for not seeing this. :/
I call this concept the "DUAL LICENSE" where the original authors can
re-release their original content in different packages, much like a book
author has one publisher for the book's rights in hard-back books and
another for softback.
BTW, makes a strong case here where we as a group need to have an "entity"
of some type so we can be holders and defenders of something -- even if it
is only a copyright. But that is another issue.
> And it'd be pretty hard for Scott not to include source code for the
> home stack we give him, so he'd be complying with the GPL anyway.
Well, not really as for the last part. Scott (MC) wouldn't be complying with
the GPL, but it wouldn't be his burden to comply with. So, no harm.
The non-compliance seems to be, and please correct me if I'm wrong, the
dynamic linking element restriction that is in hold with the GPL. This is
one of those "hair-splitting" questions, IMHO -- because of my ignorance
today. I should try to get it better understood. So I ask and ramble on.....
Isn't it the case that the GPL (????) does NOT allow for the mingling of
GPLed code with CLOSED & PROPRIETARY code. Its a no-no for OPEN & Not-OPEN
source in the same package. --- Then it goes to the idea of if the HOME
STACK would be the same package of the overall distribution of MC.
There has been general talk I've seen in the past for other programs
instances of the GPL where there is something foreign to me about "LINKING"
and "DYNAMIC-Linking." User does the links is okay. Right? Libraries and
such come into play too, right?
So, I'm looking for clarification I guess on the nature of the relationship
between the "HOME STACK" that would be release as GPLed and the rest of the
MC distribution.
Hand holding welcomed, I guess.
Mark Rauterkus
[EMAIL PROTECTED]
