Fwd: Free Software and Cincom Smalltalk Non-Commercial

> From: James Robertson <[hidden email]>
> Date: 8 avril 2006 22:50:23 HAEC
> To: stéphane ducasse <[hidden email]>
> Subject: Re: Free Software and Cincom Smalltalk Non-Commercial
>
> Generally speaking, yes.  There are two caveats:
>
> 1) If you are making money off what you ship, it's commercial and  
> needs a license
> 2) If an end user might have to buy a license if they themselves  
> make money off of it.
>
> At 04:21 PM 4/8/2006, you wrote:
>> James
>>
>> if I want to write the next generation limeWire in VW for example,
>> can I ship an executable?
>>
>>
>> You mentioned in another email:
>>
>>> Within the terms of the license, sure
>>>
>>> At 02:05 PM 4/4/2006, you wrote:
>>>
>>>> James:
>>>>
>>>> One may want to distribute something for free but that does not
>>>> necessarily mean that one may want the source code exposed or at
>>>> least
>>>> blatantly exposed. So is it okay to all or any of:
>>>>
>>>> 1. Launch one's app at startup instead of the VW Launcher
>>>> 2. Hide the source code to at least one's code.
>>>> 3. Plead ignorance and just do what one things reasonable.
>>
>> How does it fit with the point 2. I'm confused.
>>
>>>> 2) The end users use the software in Cincom Smalltalk non-  
>>>> commercial, in
>>>> the context of the development environment (i.e., not in a sealed
>>>> runtime)
>>
>>
>> Stef
>>
>>
>> On 4 avr. 06, at 20:04, James Robertson wrote:
>>
>>> For personal use, sure.  For widespread distribution, the terms of
>>> the NC license apply.  Meaning, the resulting sealed app can't be
>>> used for commercial purposes.
>>>
>>> Yes, BottomFeeder potentially violates that :)
>>>
>>>
>>>
>>> At 02:03 PM 4/4/2006, you wrote:
>>>> If I read it properly, the point #2 implies that one can't make
>>>> runtime-packaged freeware apps with VisualWorks Non-Commercial?
>>>>
>>>> Cheers!
>>>>
>>>> -Boris
>>>>
>>>> --
>>>> +1.604.689.0322
>>>> DeepCove Labs Ltd.
>>>> 4th floor 595 Howe Street
>>>> Vancouver, Canada V6C 2T5
>>>>
>>>> [hidden email]
>>>>
>>>> CONFIDENTIALITY NOTICE
>>>>
>>>> This email is intended only for the persons named in the message
>>>> header. Unless otherwise indicated, it contains information that is
>>>> private and confidential. If you have received it in error, please
>>>> notify the sender and delete the entire message including any
>>>> attachments.
>>>>
>>>> Thank you.
>>>>
>>>> -----Original Message-----
>>>> From: James Robertson [mailto:[hidden email]]
>>>> Sent: Tuesday, April 04, 2006 10:56 AM
>>>> To: [hidden email]
>>>> Subject: Free Software and Cincom Smalltalk Non-Commercial
>>>>
>>>> We've gotten a few questions about the use of Cincom Smalltalk for
>>>> free
>>>> software distribution.  In light of that, here's the policy we  
>>>> have:
>>>>
>>>> If you have downloaded Cincom Smalltalk non-commercial, then:
>>>>
>>>> -- You are already under the non-commercial or academic license,
>>>> so any
>>>> software you want to distribute also falls under that license
>>>>
>>>> -- The end users of software you give away under the non-  
>>>> commercial or
>>>> academic license need not pay anything, either to you or Cincom,
>>>> so long as
>>>> two things hold:
>>>>
>>>> 1) No money changes hands (if it does, it becomes a commercial
>>>> transaction
>>>> rather than an NC/Academic transaction)
>>>>
>>>> 2) The end users use the software in Cincom Smalltalk non-  
>>>> commercial, in
>>>> the context of the development environment (i.e., not in a sealed
>>>> runtime)
>>>>
>>>> Under those criteria, you can distribute free software written in
>>>> Cincom
>>>> Smalltalk Non-Commercial
>>>>
>>>>
>>>> <Talk Small and Carry a Big Class Library>
>>>> James Robertson, Product Manager, Cincom Smalltalk
>>>> http://www.cincomsmalltalk.com/blog/blogView
>>>>
>>>
>>> <Talk Small and Carry a Big Class Library>
>>> James Robertson, Product Manager, Cincom Smalltalk
>>> http://www.cincomsmalltalk.com/blog/blogView
>
> <Talk Small and Carry a Big Class Library>
> James Robertson, Product Manager, Cincom Smalltalk
> http://www.cincomsmalltalk.com/blog/blogView
>