supriya-project/supriya

License

nikolay-ulyanov opened this issue · 6 comments

nikolay-ulyanov commented

Could you clarify, please, your work currently has MIT license, but SuperCollider has GPL license, which is more restrictive, so I have a couple of questions:

josephine-wolf-oberholtzer commented

How is it derivative?

josephine-wolf-oberholtzer commented

The sc3 library, as I understand it, was explicitly created as a translation or sclang into Python. Supriya was not created with that intention.

nikolay-ulyanov commented

I mean, I'm not a lawyer, and maybe your project is not derivative of SuperCollider; but your project depends on SuperCollider, right? And from what I find in Google, this probably means, that your library also should use GPL license, but again, I'm not a lawyer and just trying to understand this stuff.

josephine-wolf-oberholtzer commented

I guess it depends on what "depends" means. I don't think interacting with scsynth's OSC API counts.

josephine-wolf-oberholtzer commented

If anything maaaybe supriya should have a license like sonic-pi's (https://github.com/sonic-pi-net/sonic-pi/blob/dev/LICENSE.md) which is MIT except for a couple files here and there. I would be done for that, but it's not high on my priorities to write.

Alternatively I would just remove the one cython file that knows about SC's source, leaving my MIT code intact.