Seaside License

Seaside is licensed under the MIT License. Does this mean I can develop an application with VW and Seaside, sell it to a customer, install it at their site, and not have to release my application source? The wording is to 'permit persons to whom the Software is furnised to...'. It looks like I have the option to permit... is this correct? My goal is to protect my application code. Will the MIT license allow for this?

Any comments would ge appreciated,
Glenn

Glenn Swanlund wrote:
> Seaside is licensed under the MIT License. Does this mean I can develop an
> application with VW and Seaside, sell it to a customer, install it at their
> site, and not have to release my application source?
If you have a commercial license for VW: yes you can do exactly that.


Aside:

I am surprised at how many people ask this question over and over again.
The MIT license is only a handful of paragraphs, it mentions nowhere
that you should share anything but still people ask...
Is this the fallout of Microsoft FUD re open source software? Suddenly
every open source license is perceived as viral?


I feel a bit disillusioned in that I thought that the MIT/BSD licenses
were actually readable (understandable!) by Smalltalk programmers
because they are so short and simple. I guess I was wrong but I also
guess an even simpler license is not possible to construe. So what can I
do when I want to slap an MIT license onto code I release? Add an extra
disclaimer that this license is not viral? That would make its text 25%
or so longer without adding anything significant (in the legal sense).
What to do in order to not be affected by this viral stigma?



R
-