On Tue, Jul 2, 2013 at 11:37 PM, Vaughan Johnson <vaughan@audacityteam.org> wrote:

On 7/1/2013 11:46 PM, Gale Andrews wrote:
> | From Vaughan Johnson <vaughan@audacityteam.org>
> | Mon, 01 Jul 2013 16:01:37 -0700
> | Subject: [Audacity-quality] Removal of author names from effect dialogs
>> On 7/1/2013 1:48 PM, Richard Ash wrote:
>>> On Sun, 30 Jun 2013 17:23:11 +0100
>>> gale@audacityteam.org wrote:
>>>> Peter's pointed out that the SC4 and Hard Limiter still have author
>>>> names (and licence information).
>>> They are external plug-ins (note we don't have their source in the
>>> Audacity SVN to my knowledge), so you need to be very careful about
>>> removing attribution and license information from them. It could well
>>> be a license violation (it would be for BSD for instance).
>> Absolutely. We'd been explicit in this thread that that we can't
>> legitimately remove credit and license from 3rd-party software. The
>> whole point was to clean up *our* stuff.
> OK, but we do ship these two.  Apart from the hack we would be
> otherwise compliant I think (though Steve Harris is in "About
> Audacity" and Marcus Andersson who wrote Hard Limiter isn't).

Okay, so you're saying the hack puts us out of compliance. We shouldn't
do it.

Steve's there because he supplied the whole library and helped me figure
out the Windows port. And without the hack, both get credit for their

> We already link to the original http://plugin.org.uk/ in
> win\LADSPA_plugins-win\readme_LADSPA_plugins-win.txt.

Yes. Point?

None, now we've agreed that and additionally crediting Magnus in "About" is not strictly sufficient if we hacked the plug-ins.

We ought to ship a non-distorting limiter. I think we could probably replace Hard Limiter in the near future even if it was felt we needed to still offer it as a separate download or needed to redo the Windows LADPSPA installer as a zip (so you could easily install what you wanted from it). 

From Steve's comments we need to keep SC4 for now, but ultimately that will drop out of the shipped plug-ins too.

Then all we need to do is review how to credit if we ever start shipping large numbers of new plug-ins or modules that are not "by us".