Linux Foundation license scan identifies a number of problems which need to be resolved before any releasing.  This wiki page describes the best practices for resolving these identified issues.

...

Files identified by scan to be under a copy left license shall be removed or replaced by alternatives under open source friendly licenses, or developed by O-RAN SC.  If the use of such "copyleft-ed" files is not avoidable, the PTL needs to request for ToC approval for exception.  In such request the PTL shall describe how such files are used and why the use of such files does not compromise the integrity of the O-RAN SC licenses.  

Weak

...

copy left

In general, we cannot have files under "weak copy left" licenses such as LGPL in our repos.  

...

For files under these non O-RAN SC licenses that are originated from external sources, the use need to be reported to and approved by the ToC.  Such files shall  If possible, such files should be placed under a directory clearly indicating its external originality, such as "external", "thirdparty", "vendor", etc. 

The PTL will need to describe the use of these files to the ToC for approval, including how they are used in the project, their original location, and where they are placed under the O-RAN SC repo.  The license uses under this category are tracked here:  License Attribution Records

No license

Code files must need to contain license claim at the beginning.  This is to protect files from being copied and used individually.  The standard text for O-RAN SC licenses can be found here:

The only exception is for files downstream-ed from external sources.  If the original file does not carry any license claim, we do not need to add a claim.  However, 1. we need to make sure they are not from projects under copyleft licenses, and 2. such files need to be placed under a directory clearly indicating its external originality, such as "external", "thirdparty", "vendor", etc.  

In addition, the PTL need to report the use of these files to the ToC for approval, including how they are used in the project, their original location and license, and where they are placed under the O-RAN SC repo Licensing Text.

False positives

If an identified issue is believed to be incorrect, an exception must be filed to the ToC to clarify the use and why owner believes that the report is incorrect.

Files/file types that should be excluded from having license claim header

Need ToC Approval:

.gitattributes
.gitignore
.gitmodules
.gitreview
.readthedocs.yaml
INFO.yaml
favicon.ico
*.png
*.gif
*.jpg
*.json

...