Make compliant with the REUSE specification

[Schneegans]

This makes CosmoScout VR compliant with the REUSE Specification of the Free Software Foundation Europe.

• It is now clear for each and every file
  • Who is the copyright holder?
  • What is the license for the file?
• There's a new CI job which enforces this.
• There's a new badge in the README to show the status.

This requires #298 to be merged first.

Some additional changes:

• The Vive controller model was removed due to the unclear licensing.
• Some moon textures have been removed due to unclear licenses.
• Some eslint files were removed as we are using clang-format to format the JavaScript files.

[coveralls]

Pull Request Test Coverage Report for Build 3184185550

• 0 of 1 (0.0%) changed or added relevant line in 1 file are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.0002%) to 3.011%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
plugins/csp-lod-bodies/src/PlanetShader.cpp	0	1	0.0%
<!--	Total:	0	1	0.0%	-->

Files with Coverage Reduction	New Missed Lines	%
plugins/csp-anchor-labels/src/AnchorLabel.cpp	1	0%
<!--	Total:	1		-->

Totals
Change from base Build 3180237718:	-0.0002%
Covered Lines:	491
Relevant Lines:	16306

---

💛 - Coveralls

[JonasGilg]

Is there a guideline for which file is licensed under which license? Because some config files are CC and others are MIT.

[Schneegans]

Is there a guideline for which file is licensed under which license? Because some config files are CC and others are MIT.

There should be no config files under CC-BY, however there are some under CC0.

There is no real guideline on when to choose which. However, there are two reasons due to which we may decide to publish a specific file under CC0 rather than MIT:

• The file is extremely simple. This is the case for our .gitignore file etc. These files do not meet a certain "threshold of originality" and are therefore not really copyrightable (see here).
• The file is very likely to be adapted by the user. For example, our scene configuration file will likely be the basis for a scene configuration file of a user. If we put it under the MIT, the user will always need to specify this which would b a pretty useless burden.

Therefore, I put very simple files and our configuration files (not the vista xml's, they actually contain complex logic) under the CC0.

[Schneegans]

Thank you for the review! Why do we want to have newlines in those files? They are auto-generated anyways (via reuse addheader --copyright="German Aerospace Center (DLR) <cosmoscout@dlr.de>" --license="CC0-1.0" <binary file>). I think it would be a bit cumbersome if we want to have those newlines everywhere...

[JonasGilg]

Thank you for the review! Why do we want to have newlines in those files? They are auto-generated anyways (via reuse addheader --copyright="German Aerospace Center (DLR) <cosmoscout@dlr.de>" --license="CC0-1.0" <binary file>). I think it would be a bit cumbersome if we want to have those newlines everywhere...

Ok, I think we can leave it then. GitHub suggested these changes, so I went with it.