Re: Bug#296369: ITP: spin -- Powerfull model checking and softwareverification tool
Glenn Maynard wrote:
On Wed, Feb 23, 2005 at 04:08:40PM +0100, Eike Dehling wrote:
See http://cm.bell-labs.com/cm/cs/what/spin/spin_license.html for the
whole license, it is quite lengthy therefor i won't quote it here
comletely. The precious discussion about the license starts at
conclude that the license is basically not free.
I'm interpreting this as that it is possible to include spin in the
non-free section, concerning the license issue. Any comments?
Since they force people to go through a click-wrap page, it seems like
they'd expect you, upon redistributing it, to do the same. However, I
can't find any such requirement in the license. That's strange--the
license is obviously an EULA, and if they think that it's useful to
have people click-wrap, it doesn't make sense to allow further distribution
"LUCENT, at its sole discretion, may from time to time publish a revised
and/or new version of this Agreement (each such revised or new version
shall carry a distinguishing version number) which shall govern all copies
of Licensed Software downloaded after the posting of such revised or new
version of this Agreement."
which seems to say that the license may change or terminate at Lucent's
whim at any time. This means that whoever is distributing this must be
on constant license watch, in order to update the license or pull the
software from the archive if the license changes or is revoked. Is it
really a good idea to distribute such a time-bomb?
Why would a term that only comes into play for software downloaded AFTER the change be a concern to software downloaded & redistributed before the change? Is this any different than Foo Inc. licencing App A v 1.0 under the GPL and releasing App A v1.1 under a clone of a CA EULA and stopping their distribution of App A v1.0?