We'd probably release with a notice that says something like-
Quote:
What license is SLAGE released under?
Slage has not yet had an official release. When Slage is released, it will probably be released under the GPL, with an exception. The exception states that Handlers developed in the game do not need to have their code released.
Doesn't the GPL mean I need to release my game code? My game will never sell if I do that!
We are not requiring that you release the code to your game. Games are typically written in XML and Handlers. The XML code for your game is a dataformat, and does not need to be made public. Handlers, which are how you script actions, are specifically exempted from being required.
So.. What code would I ever release?
The /only/ code you would ever release is code changing the SLAGE engine. If you change the internal engine, so that it renders fanter, or if you change a scaling feature, or add the ability to play new sound files, you will need to release the code to THOSE FEATURES only.
You will never be expected to release your entire gamecode.
I still hate the GPL, and won't use any software released under it.
Contact us, and we may be able to offer you a release using commercial terms instead of the GPL depending on your needs and budget.
|
Would that meet your needs? We're actively thinking this over right now. One problem is that technically, if you wanted to, you could probably screw us over by writing engine code in a handler
But we're trying to be accomating to commercial interests, while still asking that we get any improvements made to the Engine codebase.
The more I think about it, the more I think the MPL is the right solution.
The MPL lets you combine the code with non-licensed code as part of a larger work, such as your game.
It asks that you post your modifications to the original source, but doesn't make you post your whole game.
Advice welcomed.
-Colin
