Skip to content
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.

GPL Licensing Violation #10

Open
NostalgiaRunner opened this issue Jun 30, 2020 · 2 comments
Open

GPL Licensing Violation #10

NostalgiaRunner opened this issue Jun 30, 2020 · 2 comments

Comments

@NostalgiaRunner
Copy link

Hello,

It has come to my attention that this project is licensed as MIT, when in-fact it cannot be licensed as such. This repository contains excellent work done researching this format further. However this project claims it is based off of node-flp. Node-flp is licensed as GPL as node-flp is based off of PyDAW, which is GPL. And to take it even further, PyDAW was based off of LMMS' work on the FLP import filter. Both LMMS and that filter are licensed as GPL. Basically what I'm trying to say is that this is GPL code all the way up until this repository. Any codebases that are using GPL code must abide by the GPL terms. Thus using GPL code to the extent that it has been in this project, has contaminated this codebase. This codebase should now be licensed as GPL. GPL also prohibits re-licensing, and that's what has been done here by having an MIT license.

This is just a heads-up for the maintainers of the project and for anyone else who plans on using this code. I wish I had payed closer attention, before using code from this repo in my project. Shame on me I guess.

But to the maintainers, thank you for your contributions. And I do not wish for there to be any hard feelings.

@cpdt
Copy link
Member

cpdt commented Jun 30, 2020

Hey, thanks for bringing this to my attention - this is completely on me for not being thorough and checking this stuff when I first released this.

I'm not sure what the best course of action is on this, but in the meantime I've changed the license in the repo to GPL3. Hopefully this doesn't cause you too much hassles, although I know with how annoying GPL can be that might be too much to hope for...

@djh0ffman I dun goofed up. Does this affect your usage in Wavesabre?

@NostalgiaRunner
Copy link
Author

No worries. Thank you for changing it! C# is not my main language, but I'll let you know if I document any new event types or find any other ways to contribute back upstream. Take care.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants