chore: Add REUSE compliance and AI block

[KhronosWebservices]

• add reuse compliance to the repository
• add an AI Contributing block to the CONTRIBUTING doc
• add an Open Source Apache 2.0 CLA to cover in-bound contributions.

This repository CONTRIBUTING.adoc originally listed only CC-BY-SA-4.0. However, the repository also has Apache-2.0, CC-BY-4.0 and BSD-3-Clause.

As there are typically a lot of questions around the use of wildcards in REUSE.toml, here is a little background:

The wildcard has been put in place solely because REUSE was introduced without first updating every file. A strict configuration would have blocked any commit touching a non-compliant file, which probably would not make the maintainers very happy. The wildcard gives us a compliant baseline while headers are added at the maintainers' pace.

REUSE annotations are not just for exceptions. The REUSE spec fully supports REUSE.toml as the primary mechanism for declaring copyright and licensing. File headers are recommended, not required.

1. Wildcards can be removed once file headers are in place across the repository.
2. Updating headers is the correct thing to do. However, the wildcard is a valid way to use REUSE.toml.
3. Once the wildcard is removed, missing licences will trigger lint failures.

[SaschaWillems]

Looks good to me.

I do have one question though: This has Apache-2.0 as license. But that folder also contains the tutorial source, which is base on the original tutorial code that afaik is CC-BY SA.

Or does the REUSE only apply to files that contain a copyright header?

[KhronosWebservices]

Yes, I did miss that in the Overview. I am thinking that not all files in /en should be copyright both Alexander Overvoorde and Khronos Group?

[KhronosWebservices]

Or does the REUSE only apply to files that contain a copyright header?

REUSE applies to all files included in the path statement under [[annotations]]. Using a wildcard /en/** would apply to all files in /en. Ideally we would want each file to have their own SDPX Copyright and License, but that is a big undertaking. REUSE.toml is a valid work around until each file can be updated.