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

[Not A Bug] Question about the License and Legal Section in the Readme #2208

Closed
pairofdocs opened this issue Mar 3, 2021 · 5 comments
Closed

Comments

@pairofdocs
Copy link

pairofdocs commented Mar 3, 2021

Hello,

I was interested in this project, was looking around and noticed a conflict in the 'legal' docs.
This is not a big issue for me I think that the most recent doc, the README, has more weight than the LICENSE file.
Maybe this can be improved/ clarified.

https://github.com/diasurgical/devilution/blob/master/LICENSE#L3-L5
from 2018 Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software ... for any purpose, commercial or non-commercial...

vs

https://github.com/diasurgical/devilution/blob/master/README.md#L120
https://github.com/diasurgical/devilution/blob/master/README.md#legal
from 2020 The source code in this repository is for non-commerical use only. If you use the source code you may not charge others for access to it or any derivative work thereof.

Mentioning users who edited these lines (referencing git blame) @galaxyhaxz @AJenbo

P.S. Thank you for your work on devilution 🔥

@galaxyhaxz
Copy link
Member

I originally released the project under no license (a.k.a Un-license) because I wasn't sure how to license the code. We later had clarification and decided to specify the code should not be used for commercial purposes since it is based on Blizzard's original code. More specifically devilution is a preservation of the original code under the interoperability clause, so technically it's being provided purely for academic/research purposes.

@pairofdocs
Copy link
Author

Gotcha.
Should the License file be updated so that the message is consistent with the Readme?

@AJenbo
Copy link
Member

AJenbo commented Mar 4, 2021

yes

@TheEvilSkeleton
Copy link

Any update?

@AJenbo
Copy link
Member

AJenbo commented Aug 26, 2022

This issue has now been resolved, thank you for the patience.

@AJenbo AJenbo closed this as completed Aug 26, 2022
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

4 participants