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

Change license into GPLv3 #162

Closed
3 tasks done
Wohlstand opened this issue Jul 19, 2021 · 3 comments
Closed
3 tasks done

Change license into GPLv3 #162

Wohlstand opened this issue Jul 19, 2021 · 3 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@Wohlstand
Copy link
Owner

Wohlstand commented Jul 19, 2021

As we (Me, @ds-sloth, and @KevinW1998) have been discussed together with Nomagno#8284 at the Discord server, I need to apply the GPLv3 license to all main project files (keep the MIT license at libraries and various generic shared modules).

Nomagno#8284
After successfully verifying all current contributions made over the last year are (Surprisingly, hopefully I can change that once I make something worth including) only yours, and that indeed all code has been completely rewritten from the Redigit code thus eliminating all theoretical VERY MINOR restrictions, I'd like to politeky request a license switch to GPL or otherwise copyleft be considered, to avoid what I see as a curse that hunts all BSD licensed-based Mario fangame engines that makes them end up monetized by a third party closed source fork
TheXTech is probably now in a position where it'll be shined a relatively big spotlight, and without copyleft licensing being in place I'm worried any new features make it just ever that more susceptible to the collective malice seen previously in the game-cloning third parties that roam the internet

That means TheXTech is being used as the engine for the "Super Mario Bors. X" Mario fan game, should not be allowed to be used with closed-source proprietary projects. The MIT license is fine for the Moondust Engine runtime as it's directly targeted to develop brand-new games from the scratch, even its WIP.

  • Replace the main license file with GPLv3
  • Patch all main project headers to identify them as GPLv3-licensed
  • Apply ReadMe changes Not so needed, it doesn't mention the license
  • Apply the license change at the Wiki
@Wohlstand Wohlstand added the documentation Improvements or additions to documentation label Jul 19, 2021
@Wohlstand Wohlstand added this to the Version 1.3.5.2 milestone Jul 19, 2021
@Wohlstand Wohlstand self-assigned this Jul 19, 2021
Wohlstand added a commit that referenced this issue Jul 24, 2021
@Wohlstand
Copy link
Owner Author

Mainstream branches have been updated, the license file has been changed with GPLv3, and all main Moondust Wiki pages (except Chinese, German, and Spanish translations) have been updated to mention the license change since 1.3.5.2.

@LoveBodhi
Copy link
Contributor

Chinese also updated

@M0REKZ
Copy link
Contributor

M0REKZ commented Jul 25, 2021

A, I'm going to see that in spanish

@Wohlstand Wohlstand added this to To do in Wohlstand's works via automation Aug 14, 2021
@Wohlstand Wohlstand moved this from To do to Done in Wohlstand's works Aug 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Development

No branches or pull requests

3 participants