Etusivu Tutki Apua
Kirjaudu sisään
Godot
/
godot-docs
peilaus alkaen https://github.com/godotengine/godot-docs.git
2
0
Fork 0
Tiedostot Ongelmat 0 Wiki
Puu: 91897778b2
Haarat Tagit
godot-docs
/
tutorials
/
legal
/
complying_with_licenses.rst

complying_with_licenses.rst 5.7 KB
Historia Raaka

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106 
  1. .. _doc_complying_with_licenses:
    2. 

  2. 

  3. Complying with Licenses
    4. 

  4. =======================
    5. 

  5. 

  6. What are licenses?
    7. 

  7. ------------------
    8. 

  8. 

  9. Godot is created and distributed under the `MIT License <https://opensource.org/licenses/MIT>`_. It doesn't have a sole owner either, as every contributor that submits code to the project does it under this same license and keeps ownership of the contribution.
    10. 

  10. 

  11. The license is the legal requirement for you (or your company) to use and distribute the software (and derivative projects, including games made with it). Your game or project can have a different license, but it still needs to comply with the original one.
    12. 

  12. 

  13. 

  14. Requirements
    15. 

  15. ------------
    16. 

  16. 

  17. In the case of the MIT license, the only requirement is to include the license text somewhere in your game or derivative project.
    18. 

  18. 

  19. This text reads as follows:
    20. 

  20. 

  21. 

  22. 	Godot Engine
    23. 

  23. 

  24. 	Copyright (c) 2007-2019 Juan Linietsky, Ariel Manzur.
    25. 

  25. 	Copyright (c) 2014-2019 Godot Engine contributors.
    26. 

  26. 

  27. 	Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal	in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
    28. 

  28. 

  29. 	The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
    30. 

  30. 

  31. 	THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
    32. 

  32. 

  33. 

  34. Inclusion
    35. 

  35. ---------
    36. 

  36. 

  37. The license does not specify how it has to be included, so anything is valid as long as it can be displayed under some condition. These are the most common approaches (only need to implement one of them, not all).
    38. 

  38. 

  39. Credits screen
    40. 

  40. ^^^^^^^^^^^^^^
    41. 

  41. 

  42. Include the above license text somewhere in the credits screen. It can be at the bottom after showing the rest of the credits. Most large studios use this approach with open source licenses.
    43. 

  43. 

  44. Licenses screen
    45. 

  45. ^^^^^^^^^^^^^^^
    46. 

  46. 

  47. Some games have a special menu (often in the settings) to display licenses.
    48. 

  48. 

  49. Output log
    50. 

  50. ^^^^^^^^^^
    51. 

  51. 

  52. Just printing the licensing text using a :ref:`print() <class_@GDScript_method_print>` function may be enough on platforms where a global output log is readable (as an example, mobile devices).
    53. 

  53. 

  54. Accompanying file
    55. 

  55. ^^^^^^^^^^^^^^^^^
    56. 

  56. 

  57. If the game is distributed on desktop operating systems, a file containing the license can be added to the software that is installed to the user PC.
    58. 

  58. 

  59. Printed manual
    60. 

  60. ^^^^^^^^^^^^^^
    61. 

  61. 

  62. If the game includes printed manuals, license text can be included there.
    63. 

  63. 

  64. Third Party licenses
    65. 

  65. --------------------
    66. 

  66. 

  67. Godot itself contains software written by `third parties <https://github.com/godotengine/godot/blob/master/COPYRIGHT.txt>`_. Most of it does not require license inclusion, but some do. Make sure to do it if you are using them. Here is a list of which ones require it:
    68. 

  68. 

  69. FreeType
    70. 

  70. ^^^^^^^^
    71. 

  71. 

  72. Godot uses `FreeType <https://www.freetype.org/>`_ to render fonts. Its license requires attribution, so the following text must be included together with the Godot license:
    73. 

  73. 

  74. 

  75. 	Portions of this software are copyright © <year> The FreeType Project (www.freetype.org).  All rights reserved.
    76. 

  76. 

  77. 

  78. ENet
    79. 

  79. ^^^^
    80. 

  80. 

  81. If the project being created is a multiplayer game using the `ENet <http://enet.bespin.org/>`_ driver, ENet has similar licensing terms as Godot
    82. 

  82. 

  83. 

  84. 	Copyright (c) 2002-2016 Lee Salzman
    85. 

  85. 

  86. 	Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
    87. 

  87. 

  88. 	The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
    89. 

  89. 

  90. 	THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
    91. 

  91. 

  92. MBedTLS
    93. 

  93. ^^^^^^^
    94. 

  94. 

  95. If the project is done with Godot 3.1 or above and it utilizes SSL (usually through HTTP requests), the `MBedTLS <https://tls.mbed.org>`_ Apache license needs to be complied by including the following text:
    96. 

  96. 

  97. 

  98. 	MBedTLS is Copyright (C) 2013-2019 ARM
    99. 

  99. 

  100. 	Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
    101. 

  101. 

  102. 	http://www.apache.org/licenses/LICENSE-2.0
    103. 

  103. 

  104. 	Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
    105. 

  105. 

  106. Keep in mind that Godot 2.x and 3.0 use `OpenSSL <https://www.openssl.org>`_ instead.
    107.