Consider adding many CLAs

[pombredanne]

https://github.com/contributoragreements/ca-cla-chooser/tree/main/agreement_texts contains mainy CLAs variants, but I am not sure we should track them and if they are used.

Some may be like the FLA variants though https://github.com/search?q="Fiduciary+License+Agreement+2.0"&type=code&p=5

They have an impact on licensing, so this is TBD.

[DennisClark]

@pombredanne this surfaces a basic question about the role of a CLA in license reporting. SCTK detects licenses that apply to software so that when you use it you know what the license terms are, especially if you subsequently use that software in your own product, and it supports the reporting of licenses for attribution and SBOM purposes. So where does a CLA fit into this picture? Does one really need to report a CLA that applies to a software component that one is using? If yes, I don't understand the purpose of doing that.

[DennisClark]

I think that the CLA items listed in project ca-cla-chooser should be considered as templates rather than actual licenses or notices, since the point of the project is to help someone craft a CLA for their own purposes.

[armijnhemel]

I actually do get requests from clients about being able to detect CLAs. Of course, these are not licenses, but they are significant pieces of information.