ChucK (not to be confused with ChuckK, sorry!) is licensed under the GPL. I am not sure how this squares with the STK stuff. The ChucK site appears to be hosted at Princeton, not at SourceForge.

Regards,
Mike

-----Original Message-----
>From: Michael Gogins 
>Sent: Jul 28, 2007 11:21 AM
>To: Developer discussions 
>Subject: Re: [Cs-dev] questions on licensing issues
>
>Technically those distributions should probably be removed. But I don't think anything will happen if we leave them be. What we have been doing was widely advertised, including conference presentations and magazine articles, and nobody complained.
>
>As far as music created from that software is concerned, there is no problem whatsoever with your music copyright. Your music copyright automatically comes from you having merely created a work of music. Software licenses and copyrights usually have nothing to do with music copyright, and in the case of Csound and its component software, they definitely do not restrict your music copyright in any way. Of course, I am not a lawyer, but that is my best understanding.
>
>I think you personally will be just fine if you make all the music you like with CsoundVST, vst4cs, and the STK C++ opcodes.
>
>Thanks for mentioning ChuckK, I will take a look at its license.
>
>Regards,
>Mike
>
>
>
>-----Original Message-----
>>From: rasputin 
>>Sent: Jul 27, 2007 6:20 PM
>>To: csound-devel@lists.sourceforge.net
>>Subject: Re: [Cs-dev] questions on licensing issues
>>
>>
>>Dear Michael:
>>
>>Sorry to be so far behind the power curve, and probably my questions would
>>be 
>>answered if I read all the past threads, so perhaps you can point me at a 
>>summary of these issues.
>>
>>My inference is that components of the csound distribution, such as
>>CsoundVST,
>>contain code which traces back to commercial and/or copyrighted software
>>e.g. Steinberg's VST SDK). Thus new works which incorporate them perforce 
>>can't be completely freely distributable. 
>>
>>I wonder if pre-5.0d csound distributions which may contain some of these
>>defectively licensed components and do not comply with the SF licensing
>>guidelines 
>>will have to be removed from the repository. 
>>
>>Further, if I've written works using (e.g.) CsoundVST, are those works in
>>violation of licensing rules since they were created with defectively
>>licensed software?
>>
>>I've already done pieces with Chuck using STK opcodes; which are as part of
>>its 
>>standard release.
>>
>>Cheers,
>>
>>...r...
>>
>>
>>Michael Gogins wrote:
>>> 
>>> Thanks to discussions some weeks past, I have been motivated to make the 
>>> following changes in Csound CVS:
>>> 
>>> -- The CsoundVST plugin, vst4cs, and the STK C++ opcodes are not included 
>>> with the standard Windows installer, which I intend to be the one that
>>> goes 
>>> up on SourceForge. This should bring the Windows installers into line with 
>>> the SourceForge licensing guidelines.
>>> 
>>> -- The algorithmic composition classes formerly in the CsoundVST Python 
>>> extension module have now been moved into a new CVS directory and a new 
>>> Python extension module, CsoundAC (for "Csound Algorithmic Composition", 
>>> obviously). Scripts that used to import CsoundVST and create instances of 
>>> CsoundVST classes should work exactly as they did before, if "import 
>>> CsoundVST" is changed to "import CsoundAC" and creators such as 
>>> "myLindenmayer = CsoundVST.Lindenmayer" are changed to use CsoundAC, e.g. 
>>> "myLindenmayer = CsoundAC.Lindenmayer."
>>> 
>>> -- The CsoundVST plugin, vst4cs, and the STK C++ opcodes not only remain
>>> in 
>>> Csound CVS and SConstruct, but there are new NSIS installer scripts, 
>>> csoundd-complete.nsi and csoundf-complete.nsi, which will build Windows 
>>> installers containing these plugins.
>>> 
>>> -- The Python scripts in the examples directory have been changed to use 
>>> CsoundAC instead of CsoundVST.
>>> 
>>> Because CsoundAC has nothing to do with the Steinberg VST SDK or any other 
>>> non-open-source software, it is completely open source, and can and should 
>>> now be included in the Debian package.
>>> 
>>> At this time, no changes in "A Csound Tutorial" appear to be necessary.
>>> 
>>> There are still a few loose ends for me to tidy up, and we must make sure 
>>> that the builds continue to work on the non-Windows platforms. I can check 
>>> on Linux, but somebody else will need to check on OS X.
>>> 
>>> Thanks to everyone who participated in the discussion.
>>> 
>>> Regards,
>>> Mike
>>> 
>>> 
>>> -------------------------------------------------------------------------
>>> This SF.net email is sponsored by: Splunk Inc.
>>> Still grepping through log files to find problems?  Stop.
>>> Now Search log events and configuration files using AJAX and a browser.
>>> Download your FREE copy of Splunk now >>  http://get.splunk.com/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> 
>>> 
>>
>>-- 
>>View this message in context: http://www.nabble.com/CsoundVST-and-CsoundAC-tf4139527.html#a11837657
>>Sent from the Csound - Dev mailing list archive at Nabble.com.
>>
>>
>>-------------------------------------------------------------------------
>>This SF.net email is sponsored by: Splunk Inc.
>>Still grepping through log files to find problems?  Stop.
>>Now Search log events and configuration files using AJAX and a browser.
>>Download your FREE copy of Splunk now >>  http://get.splunk.com/
>>_______________________________________________
>>Csound-devel mailing list
>>Csound-devel@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc.
>Still grepping through log files to find problems?  Stop.
>Now Search log events and configuration files using AJAX and a browser.
>Download your FREE copy of Splunk now >>  http://get.splunk.com/
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel




-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net