[PD] Can you close source of Pd patches (for commercial development)?

[Pagano, Patrick]

But we'll be missing out on awesome front ends we can pay for N stuff!

Patrick Pagano B.S, M.F.A
Interactive Media & Education
+1352.226.2016
https://patrickrpagano.wordpress.com/


On May 11, 2016, at 1:09 AM, Jonathan Wilkes via Pd-list <pd-list at mail.iem.at<mailto:pd-list at mail.iem.at>> wrote:

> No--INAL, either, but program inputs are not subject to GPL.

Is there an example of proprietary software that ships with a GPL'd plug-in?

You may be technically right.  But in the context of a question about whether some person or business
can come along and "hijack our stuff", the practical answer is very likely to be "no".  And as someone
who's spent too much time reading the code for some of that stuff, I'd also add, "Good luck".

-Jonathan


On Wednesday, May 11, 2016 12:33 AM, Charles Z Henry <czhenry at gmail.com<mailto:czhenry at gmail.com>> wrote:


On May 10, 2016 9:39 AM, "Roman Haefeli" <reduzent<mailto:reduzent at gmail.com>@<mailto:reduzent at gmail.com>gmail.com<mailto:reduzent at gmail.com>> wrote:
>
> On Sat, 2016-05-07 at 16:13 +0000, Jonathan Wilkes via Pd-list wrote:
> > Hi Matti,
> > Pd Vanilla has a 3-clause BSD license.  This license allows you
> > to use the code in proprietary software and distribute binaries
> > without
> > also distributing the corresponding source code.
> >
> >
> > It also allows you to make changes/improvements to the code without
> > sharing them back with the community.
> >
> >
> > As for external libraries-- it depends on how they are licensed.  Some
> > are
> > licensed GPL, which doesn't allow you to do what you're asking.
>
> I'm just curious: If I implemented a way to close-source Pure Data
> patches, would I violate the GPL if I ship:
>
>  * Pd as a binary
>  * the GPL'd externals as binary with their source code and License
>  * my closed-source patch
>
No--INAL, either, but program inputs are not subject to GPL.  Distributing software that links with GPL licensed libraries requires that the free/open software requirements of GPL are met for each program or library linked with.  So, all that's additionally required is to distribute Pd's source code or provide a link to the code.
If you had to modify Pd in the process so it reads encrypted patches, you'd give away the method of encryption in the code and make the keys easier to find.
So then, one also has to find a decent method of obfuscating the inputs without linking with or modifying Pd.  An additional binary that reads an encrypted patch translates it into a readable format but doesn't link with Pd.  It can also be distributed without source code.  But, then there's an intermediate form of the patch when it's run that can be read and so it is not a foolproof method of hiding anything.
Modified versions of Pd without the GPL can be distributed without providing source code.  So one could add a method of reading an encrypted patch.

_______________________________________________
Pd-list at lists.iem.at<mailto:Pd-list at lists.iem.at> mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list


_______________________________________________
Pd-list at lists.iem.at<mailto:Pd-list at lists.iem.at> mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20160511/7eae6e59/attachment-0001.html>