Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

License clarification #7

Open
Leseratte10 opened this issue Apr 23, 2022 · 2 comments
Open

License clarification #7

Leseratte10 opened this issue Apr 23, 2022 · 2 comments

Comments

@Leseratte10
Copy link

Leseratte10 commented Apr 23, 2022

I remember a couple years ago Riivolution was closed-source and only available as binaries. Great to see that the source code is now available in a public repository for people to look at.

WiiBrew's Riivolution page lists Riivolution as "Freeware". Does that still apply, meaning, the source code in this repository is purely to look at, and there's no actual open-source license that the code is published under? I didn't see a LICENSE file, nor a mention in the README or in the source code files.

Would it be possible to publish Riivolution under an Open-Source license like the GPL?
Or, if that's not possible and Riivolution is intended to still be Freeware, just with source code available to look at, could a LICENSE file be added to this repository regardless which clarifies that Riivolution is not under any open-source license?

@AerialX
Copy link
Owner

AerialX commented Apr 23, 2022

Sorry, this is a bit unclear because (re)licensing would require some sort of sign-off by tueidj. It's currently effectively provided as-is with copyright held by the original authors. That should be clarified somewhere!

My personal stance is that I'm happy to accept fixes or other contributions and might eventually make a new release down the line if one is warranted. Until an open-source license is selected, it might be a good idea to require assignment of copyright for PRs to allow for such a license change in the future.

@Leseratte10
Copy link
Author

Assignment of copyright might be a bit extreme, but maybe something could be added that all new contributions / PRs to the project are under a license like MIT, or 2-clause BSD. These licenses are fairly open, so MIT or 2-BSD code could be used in GPL code as well, should Riivolution be distributed under the GPL2 or GPL3 in the future.

Do you have contact information like an email address of tueidj? When I google that name I can find a defunct website and a bunch of accounts that haven't been used in a long time. A project without any license is really not ideal, so it would be great if tueidj could be contacted to agree to a proper license ...

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

No branches or pull requests

2 participants