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

Relicense VS:UtCS under GPLv3+ ? #34

Open
stephengtuggy opened this issue Sep 9, 2021 · 4 comments
Open

Relicense VS:UtCS under GPLv3+ ? #34

stephengtuggy opened this issue Sep 9, 2021 · 4 comments

Comments

@stephengtuggy
Copy link

See also vegastrike/Vega-Strike-Engine-Source#548

@stephengtuggy
Copy link
Author

I believe that the VS:UtCS assets are currently under GPLv2+, for the most part, with some exceptions e.g. for the music. Not sure how many of the text-format files actually list a copyleft notice at the top, though. We may need to add that in a bunch of places.

@klaussfreire
Copy link

Tracking all authors can take a while. For my part, I would have no problem relicensing under GPLv3+

Music, however, I think is mostly some form of CC. Licensing music in GPLv3 would require distributing sources, which we don't have.

@stephengtuggy
Copy link
Author

@klaussfreire Makes sense. So I guess we can leave the music under its current license(s), excluding them from any changes we make to other parts of the project.

@BenjamenMeyer
Copy link
Member

@stephengtuggy Artwork will likely fall into the same issue as music is my guess.

@klaussfreire I'm not saying we need to track the authors down; but as a first step we need to review to see if we do.

We should also make the licensing clearer using the different licenses as appropriate:

  • GPLv2+/v3+ should only be code
  • CC (or some form of it) should be for any artwork (images, music, etc)
  • FDL (https://www.gnu.org/licenses/fdl-1.3.en.html) should be for documentation if we don't want to use CC there too.

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

3 participants