Licensing of generated files

[JanHoefelmeyer]

Looking at e.g. https://github.com/csaf-poc/csaf_distribution/blob/main/csaf/generate_cvss_enums.go, this will generate another file using the MIT License. Should generated files also use the Apache2.0 License and should this be changed as a part of https://github.com/csaf-poc/csaf_distribution/issues/532, or should this be left as-is?

[bernhardreiter]

There are two generates files in the code base:

• https://github.com/csaf-poc/csaf_distribution/blob/main/csaf/cvss20enums.go
• https://github.com/csaf-poc/csaf_distribution/blob/main/csaf/cvss3enums.go with both, a lot of the content comes from the input files, e.g.
• https://github.com/csaf-poc/csaf_distribution/blob/main/csaf/schema/cvss-v2.0.json

but the input file comes with a different license. The one function copied over into the output comes from Intevation, but the source file is not and has a different license.

It seems a good solution to not create a full header.

[bernhardreiter]

Added label service+dev as this is part of the licensing change.

[s-l-teichmann]

@JanHoefelmeyer I explained the expected go generate behavior to @bernhardreiter I will adjust the generator to stamp the right license in generated files.