These are not licenses, but are license-like from a detection point of view and are an important part of the constitution of a FOSS project.
Some example are AboutCode's own CoC, Eclipse's https://www.eclipse.org/org/documents/Community_Code_of_Conduct.php and many more.
Eventually the high level approach could be either treat these as license texts and rules either:
- part of the general license detection flow
- in a separate index and flow just for CoCs
If treated as licenses, they would need to come out as a separate section like for mere license clues, and tagged as CoCs
See also for CLAs:
Designing a single approach for CoCs and CLAs make sense.
We could extend these to API and SaaS ToS at a later stage.
These are not licenses, but are license-like from a detection point of view and are an important part of the constitution of a FOSS project.
Some example are AboutCode's own CoC, Eclipse's https://www.eclipse.org/org/documents/Community_Code_of_Conduct.php and many more.
Eventually the high level approach could be either treat these as license texts and rules either:
If treated as licenses, they would need to come out as a separate section like for mere license clues, and tagged as CoCs
See also for CLAs:
Designing a single approach for CoCs and CLAs make sense.
We could extend these to API and SaaS ToS at a later stage.