Closed caryoscelus closed 7 years ago
@caryoscelus we should probably discuss how to license graphics, music, video, and other assets.
Some files will remain MIT - others will be AGPLv3+.
Or rather, they'll be double-licensed, i guess.
As for assets, i would go with CC-BY-SA unless there are any reasons to do otherwise.
Or rather, they'll be double-licensed, i guess.
I'll leave that detail to you, I didn't know this was an advantageous thing to do.
CC-BY-SA
Great idea! Can you take care of doing that properly as well?
I'll leave that detail to you, I didn't know this was an advantageous thing to do.
From purely legal point of view, it might be not (though i think it is: we don't really need to put the whole file under mit, it's just that we place header there for convenience), but at the very least it will convey our intention.
Can you take care of doing that properly as well?
Sure!
A little history for posterity:
This code began life as an extension of an example using TypeScript, Phaser, and Webpack. https://github.com/geowarin/phaser-webpack
That repository is licensed under MIT - and significant portions of this repo still mirror the structure of that one, although all the included dependencies were updated to modern versions, and the total LOC is at least 10x higher now.
We'd like to place the additional work (new files) in this repository under the AGPL to prevent other people from doing something with this code without releasing the source. So, we're going to put license information into each file. Some files will remain MIT - others will be AGPLv3+.