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

Update LICENSE to reflect project reality #3338

Closed
licaon-kter opened this issue Oct 31, 2021 · 9 comments
Closed

Update LICENSE to reflect project reality #3338

licaon-kter opened this issue Oct 31, 2021 · 9 comments
Labels
duplicate This issue or pull request already exists

Comments

@licaon-kter
Copy link
Contributor

As pointed in several places (eg. #3290 (comment) ) the LICENSE file contradicts the actual license terms as stated in the Readme.

It would be good to have it clear that DevilutionX is not licensed as Free Software nor as Open Source.

Hopefully once the file is updated the Github info is updated too, so it does not say Unlicensed.

@AJenbo AJenbo added the duplicate This issue or pull request already exists label Oct 31, 2021
@AJenbo
Copy link
Member

AJenbo commented Oct 31, 2021

Duplicate of diasurgical/devilution#2208

@AJenbo AJenbo marked this as a duplicate of diasurgical/devilution#2208 Oct 31, 2021
@AJenbo AJenbo closed this as completed Oct 31, 2021
@licaon-kter
Copy link
Contributor Author

Oh, that's on a different repo, and locked, hence this one...

Anyway, is this on the TODO for 1.3.0?

@AJenbo
Copy link
Member

AJenbo commented Oct 31, 2021

We inherit this from upstream. I suggest joining the chat if you want to talk about things in locked issues.

@licaon-kter
Copy link
Contributor Author

licaon-kter commented Oct 31, 2021

I find it odd for FOSS projects to use proprietary closed source siloed communications systems that lock information away from (possible) contributors.

Or maybe I've missed the IRC or XMPP groups where project chat is ongoing?

@qndel
Copy link
Member

qndel commented Oct 31, 2021

@licaon-kter it's 2021, nobody is using irc/xmpp/whatever ;)
https://discord.gg/YQKCAYQ

@StephenCWills
Copy link
Member

I find it odd for FOSS projects to use proprietary closed source siloed communications systems that lock information away from (possible) contributors.

Or maybe I've missed the IRC or XMPP groups where project chat is ongoing?

I thought you didn't consider this a FOSS project so that standard shouldn't apply. Furthermore, many of our contributors are gamers, so Discord is a natural choice.

@maciek134
Copy link

I find it odd that you refuse to change the license which is clearly wrong and the readme that contradicts itself (you give up your right to restrict usage by putting something in public domain, so either the public domain part is invalid, or the commercial restriction).

CC-BY-NC would solve your "no commercial use" problem if you need a license text written by someone else.

@diasurgical diasurgical locked as spam and limited conversation to collaborators May 9, 2022
@AJenbo
Copy link
Member

AJenbo commented May 9, 2022

@maciek134 CC-BY-NC does not appear appropriate https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software

Please see previous comments for where to go if you have input on this subject.

@AJenbo
Copy link
Member

AJenbo commented Aug 27, 2022

This has now been resolved, see the following for details: diasurgical/devilution#2279

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

5 participants