Closed JanHoefelmeyer closed 7 months ago
I'm not sure if the MIT license is the correct one for the machine generated code (see this commit). Isn't the code generated from the schemas in csaf/schema/cvss-v2.0.json
and csaf/schema/cvss-v3.0.json
? As those have a "custom" license I would expect that we have to use that license. But I think @bernhardreiter can bring light into the dark.
If we use the MIT license for the machine generated code the files csaf/cvss20enums.go
and csaf/cvss3enums.go
also will have to be licensed under MIT.
How to license generated code was indeed also a question I had and an action I'd defer for now, see https://github.com/csaf-poc/csaf_distribution/issues/534. The commit you linked is actually not a change, it's undoing the change of a prior commit.
Changes all original files currently licensed under MIT to Apache. Contributes towards https://github.com/csaf-poc/csaf_distribution/issues/532