ASF spec licensing issues

[Shane Wright]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

Couldn't see anything about that on the virtualdub web site, but found this on 
usenet (and dammit there has to be a tidier way of doing a link like 
this...):

http://groups.google.com/groups?q=asf+license+terms&hl=en&lr=lang_en&ie=UTF-8&safe=off&selm=392EBCB6.2BB2%40cco.caltech.edu&rnum=6

It seems they were indeed pretty heavy on him - even without using the 
specification (which, even now, doesn't have any references to any patents in 
it.  Well, it says MS 'may' have patents on it; but doesnt say specifically 
on what or whether there actually are any...).

Cheers

Shane


On Saturday 20 July 2002 9:34 pm, Michael Matz wrote:
> Hi,
>
> On Sat, 20 Jul 2002, Cristian Tibirna wrote:
> > No matter how _you_ read it, no matter how honestly well intentioned
> > you are, to me it is pretty clear that the license tries to deny
> > possibility of developing an open source asf software based on their
> > published spec.
>
> Exactly.  In the past they did so with virtualdub.  It's author somewhen
> removed ASF reading support on M$' request (they were not suing him, but
> he feared he would be, so he stayed on the safe side).  Somehow M$ has a
> funny position on a _spec_.  I mean that they don't give away software,
> sure, but don't allowing people to implement a spec is absurd crap.
>
>
> Ciao,
> Michael.

- -- 
Shane
http://www.shanewright.co.uk/
Public key: http://www.shanewright.co.uk/files/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9Oc/E5DXg6dCMBrQRAmBoAKC9ZzVjD2p/zkWf/JJ/mmHB1rVRmgCgg5uJ
hYazM2Dp3f0SkUsL2HvuDBY=
=optJ
-----END PGP SIGNATURE-----