Difference between revisions of "Licensing"

(Make abbreviations consistent with Debian)
m (Note about spaces in file names)
Line 172: Line 172:
  CC-BY-SA 4.0 license.</nowiki>
  CC-BY-SA 4.0 license.</nowiki>
{{Popup-warning|content=If you need to document a file with a space in the file path, replace the space with a question mark.}}
Note that current and previous licenses are noted, as are current and previous copyrights and authors.
Note that current and previous licenses are noted, as are current and previous copyrights and authors.

Revision as of 19:44, 14 October 2017

Licensing is not the most exciting topic, but if you wish to contribute, you will absolutely need to read it.


SuperTuxKart is included in many Linux distributions with strict license requirements (e.g. Debian). We cannot accept tracks/karts/textures/etc. with unclear licensing terms as this could result in SuperTuxKart being removed from their repositories, or, worse, getting sued.

Furthermore, we are hosted (freely, I might add) by SourceForge and TuxFamily, which require that all hosted materials be released under open licenses; therefore posting materials with improper licenses would violate our terms of hosting and be rude to the kind people who provide this hosting.

STK Code

The source code of SuperTuxKart is released under GPL v3.0 (we updated all files to use this version by making use of the "or (at your option) any later version" clause of the GPL).

Considerations to always keep in mind

Here's the information you should write down about any artwork you make (don't forget to include the same information about any other artwork you integrate into your work) or someone else's artwork that you share. Artwork includes textures, concept art, tracks, karts, 3D models, and any other artistic work. Note that while it's OK to license a track as a whole under a single license, you must still credit the authors of individual components.

  • Author's name (legal name and pseudonym, if possible)
  • Year of publication (copyright year—if possible)
  • License(s) under which the work is published
  • URL of where you found the artwork (It's a good idea to save the page on the Internet Archive too, in case it goes offline.)
  • If you made a modified version and upgrade the license version, still note down the original license.

If you fail to provide the necessary information, your work will be included neither in core SuperTuxKart nor add-ons!

If you reuse a texture from another STK track, still note down the information above in case the texture is later removed from core STK.

Also be sure that you have the right to actually release the art work under the license you chose. Some (usually commercial) software might restrict what you are allowed to do with anything created with that software. If the software includes bundled sound or image samples, be sure to follow the publisher's licensing requirements if you integrate the samples into your work.

Brands, corporations etc

Trademarked logo and brands aren't allowed in SuperTuxKart. Instead if you want to add a company or a corporation you can use fictional ones from our universe.

Which licenses?

Acceptable Licenses

Consult the table below to choose an acceptable license. All compatibility between licenses is one-way unless specified otherwise.

Name Abbreviation Summary Compatibility
Acceptable Licenses
Creative Commons Attribution-ShareAlike 4.0 International CC-BY-SA 4.0 Ensures that you receive credit for your work and that your work (and derivative works) remain freely available under the same license. Note that the 3.0 version of this license is less internationally consistent in application and is not as compatible. Creative Commons licenses prior to version 3.0 are not acceptable. This is our recommended license. Works licensed under the CC-BY-SA 4.0 (only 4.0, not 3.0) may be integrated into GPLv3 works. (But not GPLv3+ unless Creative Commons is specified as a proxy.) Works licensed under any version of the CC-BY can be integrated into CC-BY-SA works. Works licensed under the CC-BY-SA 1.0 cannot be integrated into CC-BY-SA 4.0 works. CC-BY-SA 4.0 works may be integrated into other CC-BY-SA 4.0 works. Public domain works can be integrated into any works under the CC-BY-SA 4.0. Works under the CC-BY-SA 2.0 or later may be able to be integrated into CC-BY-SA 4.0 works (see § Licenses requiring modification).
Creative Commons Attribution 4.0 International CC-BY 4.0 More permissive than the CC-BY-SA in that it allows reuse under a different (potentially non-free) license. Note that older versions of this license are less internationally consistent in application. Public domain works can be integrated into works under the CC-BY 4.0. Works under any prior version of the CC-BY license can be integrated into CC-BY 4.0 works. Works under the CC-BY 4.0 can be integrated into other works under the CC-BY 4.0.
Artistic License version 2 Artistic The Artistic License version 2 is a permissive license allowing licensees some freedom to modify the original work without license restrictions, provided they avoid confusion with the original. (Note: I find the wording of both versions a bit confusing, however both versions are acceptable to Debian. The Free Software Foundation however finds the Artistic License version 1 to be non-free due to lack of clarity.) Works based on those under the Artistic License version 2 can be released under the GPL. Other licenses may also be OK—decide on a case-by-case basis.
X11 License/Expat License/"MIT License" X11 or Expat A very permissive license that requires only that a copyright notice be included in derivative works or copies. You can even re-license works under equivalent or more restrictive licenses. The only difference between X11 and Expat is that X11 includes a clause disallowing use of the company name in promotion. Works licensed under the X11 License may be integrated into works under the CC-BY-SA 4.0, CC-BY 4.0, GPLv3, ALv2, MPLv2, and potentially others.
BSD Licenses (4-Clause, 3-Clause, 2-Clause (NetBSD version), 2-Clause (FreeBSD version)) BSD-4 (Four-clause version), BSD-3 (Three-clause/Revised/Modified version), BSD-2 (Two-clause/FreeBSD version), BSD-simplified (NetBSD version) The BSD licenses are a group of very permissive licenses. They are listed in order of most to least restrictive in the "abbreviation" column to the left. All BSD licenses include an attribution (copyright notice) requirement and a disclaimer of liability. Additionally, the BSD-4 and BSD-3 include a restriction on the use of the author's name in promotion of modified versions of the product. (Note: the latter requirement still implicitly applies under the BSD-2 and BSD-simplified since this is considered a right in most countries that cannot be taken away without explicit forfeiture.) The BSD-4 includes a controversial clause requiring attribution in advertisements and is not recommended. The BSD-2 includes a statement that the views expressed in the software or documentation are the author's and not the organization's. The BSD-simplified does not include the latter statement. Works under all BSD licenses EXCEPT the BSD-4 may be integrated into GPL works and probably many others, provided you remember to note down what license the original was under. (This is a requirement for all derivative works.)
Creative Commons Zero CC0 or public-domain Not a true license but rather a statement of release into the public domain. This means that anyone can use your work for any purpose without any type of attribution to you. CC0 works can be integrated into any other type of work, however we ask that you still record your source to dissuade false copyright infringement claims. Because the CC0 is a declaration of forfeiture of copyright, you cannot integrate copyrighted work into your art and release it under the CC0.
Mozilla Public License version 2 MPL 2.0 The MPLv2 is unique in that it requires modifications to be released under the MPLv2, but unmodified versions may be incorporated into "larger works" as long as they remain as individual files. Of course, this makes little sense for artistic works, where multiple works could be stored in the same file but still be able to be separated. Only of particular note is that MPLv2 works can be integrated into differently-licensed works, provided that the MPLv2 works remain under the MPLv2 despite the "larger work" being distributed under a different license. However this is not really applicable for artistic works as e.g. including an MPLv2-licensed 3D model in a GPL-licensed track doesn't constitute a larger work since the two objects remain separable, unlike a compiled program.
Apache License version 2 Apache 2.0 The ALv2 is a very permissive license much like the BSD-2. The important thing is that it protects users from patent traps. Of particular note is that ALv2 is compatible with GPLv3, but not other versions. Other licenses may also be OK—decide on a case-by-case basis.
GNU General Public License version 3 GPL 3.0 (GPL 3.0+ if "or later version" clause is used) The GPL is a strong copyleft license, similar in many ways to the CC-BY-SA. GPL-licensed works can only rarely be integrated into non-GPL works.
GNU Lesser General Public License version 3 LGPL 3.0 (LGPL 3.0+ if "or later version" clause is used) Much like the GPL 3.0, except allows linking with proprietary libraries. Doesn't make sense for artistic works. ????

Licenses requiring modification before inclusion

These licenses are unacceptable for works submitted to SuperTuxKart, but if you make a significant change to a work of art under one of these licenses (for instance crop it and make it repeatable to build a texture), then you are allowed to release your modified version of the image under a later version the same license. What constitutes a significant modification is open for lawyers to debate upon but as long as your modified version does not look like a copy of the original we won't be picky.

  • Creative Commons Attribution 2.0
  • Creative Commons Attribution 2.5
  • Creative Commons Attribution-ShareAlike 2.0
  • Creative Commons Attribution-ShareAlike 2.5

Unacceptable Licenses

Do not attempt to submit modified or unmodified versions of works under these licenses:

  • GNU Free Documentation License (all versions)
  • Creative Commons Sampling 1.0
  • Creative Commons Sampling Plus 1.0
  • Any Creative Commons licenses version 1.0
  • Any Creative Commons licenses with the no derivatives (ND) clause
  • Any Creative Commons licenses with the non-commercial (NC) clause
  • Free Art License (Licence Art Libre)—due to confusion with the translation from French
  • CGTextures License
  • Image*After Terms
  • Mayang License
  • TextureArchive Terms
  • "Creative Commons" without a full name including the version number (because Creative Commons is an organization, not a license.)
  • "I-asked-the-guy-and-he-said-I-could-use-it." This is not a license, and even if you have it in writing it doesn't tell you what legal restrictions apply. Ask for an explicit statement, or ask the person to copy and sign/re-post the one below:

I, <name here>, agree to release my artistic work, <name of work here>, under the terms of the <name of license here>.

For other licenses, we need to check on a case-by-case basis. The Debian Wiki provides more details on other licenses along with GNU's page about licenses.

Documenting Licenses

Note: If you've made a library node or texture to be included in SuperTuxKart main, just provide the information required above to whoever is in charge of including your artwork and the licensing information will be added for you.

So, you've dutifully gathered all the information needed that's listed above. Now what? For any add-on kart, track, or arena, you will need to include this information in an organized way in a file called licenses.txt in the same folder as the exported kart or track's files.

The preferred way to document the licenses for your kart/track/arena/etc. in licenses.txt is to follow the Debian Machine-Readable Copyright File Format. This ensures a standardized way to keep track of licenses and makes it easy to look up the license of your work should a controversy ever arise. Here is an example of what your licenses.txt might look like for an add-on kart:

Note that current and previous licenses are noted, as are current and previous copyrights and authors.

Where to find files

Looking for properly licensed material?

The following websites offer only public domain material, that is always OK to use :

The following websites provide resources under a variety of mixed licenses; you may find a lot of good material there but verify the license on a case by case basis :