Re: Is this better for tomsrtbt?

2001-04-22 Thread Eric Jacobs
Tom Oehser [EMAIL PROTECTED] What I don't like is other people just copying the *actual binary* without giving any credit or acknoledgement that *they* don't want to bother to compile it *themselves*. As long as they mention where they got it, I'm fine with it. So, in the case

RE: namespace protection compatible with the OSD?

2001-04-19 Thread Eric Jacobs
"Lawrence E. Rosen" [EMAIL PROTECTED] I was trying to point out that you CAN'T ALLOW someone to use your name -- e.g., ALL uses, even friendly ones, are misuses -- because it is YOUR trademark and not theirs. If you allow a third party who creates a derivative work to market that

Re: namespace protection compatible with the OSD?

2001-04-18 Thread Eric Jacobs
Brian Behlendorf [EMAIL PROTECTED] I'm saying two things: if you create a derivative work from my code, then the license says if you change the behavior of the functions or macros, etc., defined in my .h, that you must call it something else. However, if you keep the same interface (keep

Re: Subscription/Service Fees - OSD Intent

2001-03-28 Thread Eric Jacobs
Ian Lance Taylor [EMAIL PROTECTED]: ) It may certainly be possible to have a [requirement that derivative works ) be licensed under the GPL] for Open Source software. I am not denying ) that. However, until such a time as the [requirement that derivative ) works be licensed under

Re: Subscription/Service Fees

2001-03-27 Thread Eric Jacobs
"Karsten M. Self" [EMAIL PROTECTED]: I wasn't thinking of any form of copying restriction, only having it clearly stated in the license that if you continue to use the software you are required to pay $x to xyz inc. Nope. Violates #7: "The rights attached to the program must apply

Re: What is Copyleft?

2001-02-22 Thread Eric Jacobs
"Ryan S. Dancey" [EMAIL PROTECTED] When you make a function call in compile-time linked code, you are creating a derivative work, because the function code itself will be compiled into the Program and inextricably combined with your code. When the two are separated by a run-time

Re: Converting/Splitting Code - Open to Closed

2001-02-12 Thread Eric Jacobs
Brian DeSpain [EMAIL PROTECTED] Yes - but the previous versions licensed under the GPL remain GPLd and development can continue on the code. Can you explain why this is the case? In reality, the code would most likely *fork,* leaving one strand open and the other proprietary.

Re: IPL as a burden

2001-01-17 Thread Eric Jacobs
[EMAIL PROTECTED]: I believe OSD section 7 may cover that: 7. Distribution of License. The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties. =2E..in which

RE: AFPL vs. GPL-like licenses?

2001-01-15 Thread Eric Jacobs
"Lionello Lunesu" [EMAIL PROTECTED]: It reminds of something I did in my childhood (I must have been 12 years old or so). Somebody gave me a collection of comics that he knew I liked. I read most but when I got tired of them I try to sell them in a yard sale. Then my brother pointed out

Re: Qt/Embedded

2000-11-17 Thread Eric Jacobs
On Fri, 17 Nov 2000, David Johnson wrote: On Friday 17 November 2000 01:20 am, [EMAIL PROTECTED] wrote: The idea is that, if a program is a work, and if (as the courts have held, in Mai v. Peak) a program in memory meets the fixed and tangible requirements of copyright law, and is