[PD-dev] License restriction of CNMAT OSC code

[Hans-Christoph Steiner]

So I actually looked through those files and all the ones that I looked  
at had the newer free license:

/*
Written by Adrian Freed, The Center for New Music and Audio  
Technologies,
University of California, Berkeley.  Copyright (c)  
1992,93,94,95,96,97,98,99,2000,01,02,03,04
The Regents of the University of California (Regents).

Permission to use, copy, modify, distribute, and distribute modified  
versions
of this software and its documentation without fee and without a signed
licensing agreement, is hereby granted, provided that the above  
copyright
notice, this paragraph and the following two paragraphs appear in all  
copies,
modifications, and distributions.
*/

Now its just a matter of someone merging in that code into what's in  
the CVS.

.hc

On Monday, Apr 12, 2004, at 03:24 America/New_York, Frank Barknecht  
wrote:

> Hallo,
>
> I'm one of the maintainers of the Pure Data CVS at Sourceforge
> (pure-data.sf.net). The repository also includes an OSC external for
> Pd which is based on the CNMAT example code in:
> http://cnmat.cnmat.berkeley.edu/OpenSoundControl/src/ although an
> older version.
>
> Recently it was brought to our attention, that much of the the code on
> the CNMAT OSC site - contrary to the text on the OSC homepage - is
> *not* distributed under an open source license, but instead restricts
> use to "educational, research, and not-for-profit purposes". Any other
> use, for example distribution of the source code on Linux distribution
> CDs or whatever, is prohibited by the OSC code license.
>
> Now, as the OSC code doesn't come with a README including the license,
> but instead requires users to read the source code to find out about
> the "non-free"-ness and the usage restrictions, we made the mistake of
> including the OSC for Pd code in the Sourceforge CVS.  (Mistake,
> because Sourceforge requires an open source license for hosted
> projects.)
>
> As OSC is a very useful protocol (who am I telling this) we would
> still like to maintain a somehow Max-compatible set of OSC externals
> for Pd. But the license of the upstream code now forces us to either
> a) reimplement the protocol as real open source externals, probably
> using Steve's GPL'd liblo or b) wait for a change of the upstream
> code's license, which would of course spare us a lot of work.
>
> Now my question is: Will the OSC code in above URL get an open source
> compatible license in the forseeable future?
>
> Thank you for your help.
>
> Ciao
> --  
>  Frank Barknecht                               _ ______footils.org__
>
> _______________________________________________
> PD-dev mailing list
> PD-dev at iem.at
> http://iem.at/cgi-bin/mailman/listinfo/pd-dev
>

________________________________________________________________________ 
____

Man has survived hitherto because he was too ignorant to know how to  
realize his wishes.
Now that he can realize them, he must either change them, or perish.
		                                     -William Carlos Williams

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 3039 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20040412/7d61e5b1/attachment.bin>