Copyright headers in translator source code about spirv-llvm-translator HOT 5 OPEN

@outofcontrol do we have any Khronos guidelines for this?

from spirv-llvm-translator.

Moving to Apache 2.0 would be inline with Khronos' other repositories. @oddhack might be able to confirm if there are certain files which would not fall within Apache 2.0. This would also resolve any issues with applying a CLA to this repository.

from spirv-llvm-translator.

Do we have any copyright header template for the files or is it to be decided per repository?

from spirv-llvm-translator.

For Apache 2.0 we would use the following header:

;
; Copyright (c) YYYY The Khronos Group Inc.
;
; 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
;
; http://www.apache.org/licenses/LICENSE-2.0
;
; 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.
;

Additional trademarks and license would be included after the license.

edited: Fixed incorrect comment tag. oops.

from spirv-llvm-translator.

What we're encouraging all the WGs to do going forward is like Vulkan and OpenXR - Apache 2.0 on code-like things (code, scripts, Makefiles) and CC-BY 4.0 on documentation-like things (spec sources, document processing macros, etc.). Ratified Specifications produced by the WG in output formats (PDF, HTML) and published by us are normally placed under the proprietary Khronos specification license.

In specific cases where LGPL compatibility is required, we have added an "Exception Clause" to the Apache license. This happens very rarely; see xml/vk.xml in the Vulkan-Docs repository for an example.

Re #63. be aware that changing the copyright on something that has a copyright holder other than Khronos requires getting their affirmative consent to the change. What we've done for spec changes is ask members to assign copyright to Khronos under the current IP agreements; the only Vulkan documents that keep a vendor copyright are vendor extension specifications, and they still must be under the same Apache / CC-BY regimen as the Khronos-copyrighted files.

If you need more clarification on this, please copy me and Neil Trevett in email.

from spirv-llvm-translator.