1The files in, and generated output documents from this Vulkan-Docs 2project are under a mix of copyright and license statements. Refer to 3the individual files for specific information. As a general 4guideline: 5 6* The Vulkan Specification asciidoc sources, as well as other documentation 7 which we expect people may wish to regenerate and distributed in other 8 formats - such as the reference pages generated from the Specification 9 source - are under a Creative Commons Attribution 4.0 license. 10** The specification sources have only recently (as of June 2017) been 11 placed under this license. We will now be able to accept pull requests on 12 Github, but there is a related Contribution License Agreement which 13 people proposing PRs to the Vulkan-Docs repository must execute as part 14 of opening the PR. 15* Generated output documents, including the official Vulkan Specification 16 PDF and HTML documents, are under a proprietary Khronos license. See 17 https://www.khronos.org/registry/speccopyright.html . Only Specification 18 documents posted in the Vulkan Registry are official. 19* The Vulkan headers, spec build tools, and spec and registry configuration 20 files are, for the most part, under the Apache 2 license. Some older files 21 are under BSD-like licenses which may eventually be updated to Apache 2 as 22 we have time. 23* There may be some configuration files customized from material shipped 24 with the asciidoc and dblatex distributions. Such files continue under 25 their original copyrights. 26* Some generated, transient files produced during the course of building 27 the specification, headers, or other targets may not have copyrights. 28 These are typically very short asciidoc fragments describing parts of 29 the Vulkan API, and are incorporated by reference into specification 30 or reference page builds. 31* If something is missing a copyright statement and that poses an 32 *actual problem* for whatever you're doing, file an issue on GitHub 33 and we'll eventually correct it in some fashion. 34 35Working with the different Khronos member company IP lawyers to make 36license changes is a very slow process constrained by the Khronos Member 37Agreement and IP Policy as well as by individual company concerns about 38their IP. Do not expect rapid changes in anything having to to with 39copyrights and licensing. 40