Alexander Mazuruk

sorry for late come-back. added home dir (scancode-toolkit cache defaults to this dir), set group id for opt, should be ready to merge

I think 3rd option is best - fetching is already a pipe and it would make scaling amount of workers easier based on amount of runs to process

How should policies by license expression work? Should they be defined in different manner in policies.yaml? Example: ``` license_expression_policies: - license_expr: bsd-simplified AND gpl-2.0 label: Restricted License compliance_alert: warning ```...

Sorry for not being clear: by 1:1 matching I meant https://github.com/nexB/license-expression/blob/master/src/license_expression/__init__.py#L213 Yet it would mean that for each CodeBaseResource.license_expression we would iterate through all expression policies to compare them... From...

@Atharex we're deploying scancode.io in k8s too! We used https://kompose.io/ to transform `docker-compose.yaml` to k8s definitions The definitions we have are currently a bit of a mess as its still...

our deployment- its not on par with typical helm charts yet- e.g. no quick ability to use own components rather than bitnami ones, etc but it works and should get...

@quepop I understand it as follows: the `APKBUILD` parser should currently live in `scancode-toolkit.packagedcode/alpine_build.py` - as it is the most logical place to have it right now without creating a...

> Hey, thanks for this! I'll review it as soon as I can. no worries > A quick comment though: I'd like to keep the branding. I know running it...

@deluan > Hey, I didn't forget about this, I'll look into that after the next release, due this weekend. no worries, this PR is not that important - just minor...