See introductory video for GSoC here: https://www.aboutcode.org/news/2022-03-30-aboutcode-for-gsoc2022.html and https://github.com/nexB/aboutcode/wiki/GSOC-2022 . Weekly meeting on Monday's at 16:00 UTC on Jitsi. See details and URL at https://github.com/nexB/aboutcode/wiki/MeetingMinutes -- Interested in contributing? See https://aboutcode.readthedocs.io/en/latest/contributing.html - If you need support specifically for ScanCode ask in https://gitter.im/aboutcode-org/scancode
@JonoYang@pombredanne could you elaborate more on next steps? I'm not really sure what "being able to install custom licenses using wheels" means/how the scancode plugin binaries example works. Is it that the licenses would be packaged like the plugins and I'd have to add code that unpacks that, installs the license into a directory, and then adds it to the license cache too?
The previous week, I developed templates for the project with the help of @tdruez.
I would also like to contribute
Dear Team, Hope you are doing well! One query regarding copyright notices, Is there any possibility of listing the copyright notices as per scanned packages (currently its listing as file by file)? kindly confirm
@Raghavendrakamatagi-eng I'm working on a output plugin that generates a NOTICE file per packages, not sure if it's what you need
@aspacca yes, i am looking into the report per packages. kindly let me know once its ready to use
GSoC update on the workbench: Implemented FileTree & path selection (updates are synced across all components on path change)
weekly GSoC update: implemented functionality to use installed external license plugins in license detection
GSoC update: add deps validator add test for osv validator
@catalinstratu:matrix.org Hey :)
@catalinstratu:matrix.org welcome back! re: creating a project for inspecting Go binaries... yes! I will create it later today
go-inspector has a nice ring to it, do you linke the name?