@@ -7,10 +7,10 @@ Top Issues
771. Primary license detection, top issue.
88~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
99
10- There is too much cruft in detected licenses, and we know too much without being
10+ There is too much cruft in detected licenses. We know too much without being
1111to distinguish the forest from the trees. Therefore reporting the primary
12- license detection is important: when we get SC results, we can often
13- get 30 license on a single a package and that's a problem.
12+ license detection is important: when we get Scan results, we can often
13+ get 30 license for a single a package and that's a problem.
1414It would make the logic of selection the primary license visible
1515
1616Is this for SCIO or SCTK? Likely a bit a both.
@@ -19,8 +19,8 @@ Is this for SCIO or SCTK? Likely a bit a both.
19192. Package files.
2020~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2121
22- Reporting the set of package files for each package instance is important as
23- it allows to naturally group these together in one unit.
22+ Reporting the set of package files for each package instance is important because
23+ it allows for natural grouping of these in one unit.
2424
2525
26263. Go to two-level reporting of detections to provide more effective detections
@@ -34,12 +34,12 @@ it allows to naturally group these together in one unit.
3434
3535*License *:
3636
37- - many detections in a file at different location , could be merged in a single reported license
37+ - many detections in a file at different locations , could be merged into a single reported license
3838- same for primary licenses
3939
4040*Copyright *:
4141
42- - Copyrights and authors detection, which are tracked at the line level
42+ - Copyright and author detection, which are tracked at the line level
4343- Holder would be for many copyright detections
4444
4545
@@ -60,50 +60,47 @@ Roadmap
6060 package-type/ecosystem conventions.
6161- SCIO: add primary license field in DiscoveredPackage models and feed it with
6262 the data from packages
63- - SCIO: Do we track secondary? or is this just aggregated data on the fly.
63+ - SCIO: Do we track secondary? or is this just data aggregated on the fly.
6464- SCIO: Refine primary license based on license in "key files"
6565
6666
67672. Primary copyright detection for packages
6868~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
6969
70- - this is likely closely tied to the primary license detection and should focus
70+ - This is closely tied to the primary license detection and should focus
7171 on package manifests and key files. And on package first
7272
7373
74-
75743. Package files
7675~~~~~~~~~~~~~~~~~~~~~~~~~
7776
7877- SCTK: See https://github.com/nexB/scancode-toolkit/projects/10
79- - work on the model
80- - work on updating the package code focus in npm, pypi, maven, go.
78+ - Work on the model
79+ - Work on updating the package code focus in npm, pypi, maven, go.
8180- SCIO: adopt the two levels manifests/package instances
8281
8382
84-
85- 4. Go to two-level reporting of detections for licenses
83+ 4. Go to two-level reporting for license detections
8684~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
8785
88- - add top level reference licenses section in the JSON output
89- - report detections at the file level, one per matched rule
90- - multiple detections for one or more license expressions in a file, eventually
86+ - Add top level reference licenses section in the JSON output
87+ - Report detections at the file level, one per matched rule
88+ - Report multiple detections for one or more license expressions in a file, eventually
9189 grouping multiple detection in a single expression in a file
9290
9391
94- 5. Go to two-level reporting of detections for holders
92+ 5. Go to two-level reporting for copyright holder detections
9593~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
9694
9795- Reported detections of Copyrights and authors detection, tracked at the line level in a file
9896- Holder would be for many copyright detections
9997
10098
101-
102996. License detection quality improvements
103100~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
104101
105- - Finish and merge unknown license detection (this depends on having 4. Go to two-level reporting of detections for licenses done )
106- - Update scancode-analyze to the new two-level reporting of license detections
102+ - Finish and merge unknown license detection (this depends on completion of 4. Go to two-level reporting of detections for license )
103+ - Update scancode-analyze to the new two-level reporting of license detections
107104- Revamp how common list of suprrious licenses are detected (this is a bug)
108105- Use important key phrases for license detection https://github.com/nexB/scancode-toolkit/issues/2637
109106
0 commit comments