|
@@ -4,9 +4,13 @@ This GitHub project hosts the Spine Runtimes which are needed to use [Spine](htt
|
|
|
|
|
|
## Licensing
|
|
|
|
|
|
-The Spine Runtimes may only be used for personal or internal use, typically to evaluate Spine before purchasing. If you would like to incorporate the Spine Runtimes into your applications, distribute software containing the Spine Runtimes, or modify the Spine Runtimes, then you will need a valid [Spine license](https://esotericsoftware.com/spine-purchase). Please see the [Spine Runtimes Software License](http://esotericsoftware.com/git/spine-runtimes/blob/LICENSE) for detailed information.
|
|
|
+You are welcome to evaluate the Spine Runtimes and the examples we provide in this repository free of charge.
|
|
|
|
|
|
-The Spine Runtimes are developed with the intent to be used with data exported from Spine. By licensing Spine, `Section 2` of the [Spine Software License](https://esotericsoftware.com/files/license.txt) grants the right to create and distribute derivative works of the Spine Runtimes. A Spine license is needed to distribute any software containing the Spine Runtimes, even if you are not using the Spine editor.
|
|
|
+You can integrate the Spine Runtimes into your software free of charge, but users of your software must have their own [Spine license](https://esotericsoftware.com/spine-purchase). Please make your users aware of this requirement! This option is often chosen by those making development tools, such as an SDK, game toolkit, or software library.
|
|
|
+
|
|
|
+In order to distribute your software containing the Spine Runtimes to others that don't have a Spine license, you need a [Spine license](https://esotericsoftware.com/spine-purchase) at the time of integration. Then you can distribute your software containing the Spine Runtimes however you like, provided others don't modify it or use it to create new software. If others want to do that, they'll need their own Spine license.
|
|
|
+
|
|
|
+For the official legal terms governing the Spine Runtimes, please read the [Spine Runtimes License Agreement](http://esotericsoftware.com/spine-runtimes-license) and Section 2 of the [Spine Editor License Agreement](http://esotericsoftware.com/spine-editor-license#s2).
|
|
|
|
|
|
## Documentation
|
|
|
|
|
@@ -14,7 +18,7 @@ See the [Spine Runtimes Guide](http://esotericsoftware.com/spine-runtimes-guide)
|
|
|
|
|
|
## Bugs, enhancements, and tasks
|
|
|
|
|
|
-Review our backlog of bugs, enhancements, and tasks in the [spine-runtimes](https://github.com/EsotericSoftware/spine-runtimes/issues) and [spine-editor](https://github.com/EsotericSoftware/spine-editor/issues) issue trackers.The [spine-runtimes waffle](https://waffle.io/EsotericSoftware/spine-runtimes) and [spine-editor waffle](https://waffle.io/EsotericSoftware/spine-editor) provide a more convenient view of the same issue tracker information.
|
|
|
+Review our backlog of bugs, enhancements, and tasks in the [spine-runtimes](https://github.com/EsotericSoftware/spine-runtimes/issues) and [spine-editor](https://github.com/EsotericSoftware/spine-editor/issues) issue trackers. Our [roadmap](http://esotericsoftware.com/spine-roadmap) provides a more convenient view of the same issue tracker information.
|
|
|
|
|
|
## Versioning
|
|
|
|
|
@@ -24,6 +28,6 @@ It is highly suggested to [freeze](http://esotericsoftware.com/spine-settings#Ve
|
|
|
|
|
|
## Contributing
|
|
|
|
|
|
-In order to merge your contributions, we need a signed [contributor license agreement (CLA)](http://esotericsoftware.com/files/cla.txt) from you. You can send a copy of the CLA to [email protected].
|
|
|
+In order to merge your contributions, we need a signed [contributor license agreement (CLA)](http://esotericsoftware.com/licenses/cla.txt) from you. You can send a copy of the CLA to [email protected].
|
|
|
|
|
|
When possible, it is best to base your contributions on the current beta branch (`X.X-beta`). Please be sure to follow the style and formatting you find in the respective runtime code to which you are contributing.
|