Draft: scancode evaluation

This MR is WIP, but allows us to discuss some points.

assigned to @daissi

added 2 commits

• 69077e92 - Add results of scan
• 7a74968b - Add AT9949_scancode_evaluation.md

Compare with previous version

changed title from Draft: WIP to Draft: scancode evaluation

changed the description

added 1 commit

• bf116a7a - Add .gitlab-ci.yml

Compare with previous version

@wlozano here is the current status of scancode evaluation. Reports are generated in the gitlab-ci.

As a suggestion for the future probably it is better to this MR in our website. Most likely this document will reflect a plan so it fits very well under https://www.apertis.org/concepts/

Thank you very much for preparing this draft. Let me think a bit more about this to provide additional feedback. Also let's include @em since I am sure he will be happy to share some thoughts.

I am still thinking in which is the best way approach. So far, the options I see (brainstorming time):

• Keep using scan-copyrigths
• Use scancode by default and suggest drinking a coffee while waiting (or maybe some thousands of coffee)
• Use scancode only for target, but pipelines will be different (@em will complain and he is right)
• Keep using scan-copyright and use scancode for tricky files, like files with GPL or UNKNOWN or files with multiple licenses in target, but I am a bit scary about creating a Frankenstein

added 3 commits

• c705c245 - Add note about firefox-esr and texlive-extra which are not in target
• af1f626f - Add .gitignore
• 423c36de - Improve and move paragraph about the different approaches between scancode and scan-copyrights

Compare with previous version

added 1 commit

• 5c229b95 - Add ref to upstream comparison

Compare with previous version

added 2 commits

• b128b785 - Add info about hardware used for analysis
• 276cc3d7 - Add more results

Compare with previous version