Cool! I can help explain the licensing:
The Spine Runtimes licensing terms are defined by the Spine Runtimes License Agreement.
The first paragraph is for those who have licensed Spine. Their usage of the Spine Runtimes is covered by the terms in the Spine Editor License Agreement, Section 2.
The second paragraph is for those who have not licensed Spine and likely applies to your PR. It allows the Spine Runtimes to be integrated into any software, as long as the Spine Runtimes License Agreement applies to that software.
Game toolkits, OSS, and other software that want to include the Spine Runtimes often don't want the Spine Runtimes License Agreement applied to their entire software. To avoid that, you could make the part that contains the Spine Runtimes an optional component. The Spine Runtimes License Agreement only applies to that component. Users who include that component either:
-
license Spine and have the Spine Editor License Agreement apply to their derivative works, or
-
don't license Spine and have the Spine Runtimes License Agreement apply to their derivative works.
Most OSS projects go that route. Alternatively, you could show the Spine Runtimes License Agreement and have the user agree to the terms before enabling features that cause the Spine Runtimes to be included in derivative works. For example, GameMaker does this.
Legalese like this is never fun to deal with, sorry. We put enormous effort into our Spine Runtimes and the intent of this is that the Spine Runtimes be used by those who have licensed Spine.
