miki3421 opened a new pull request, #42:
URL: https://github.com/apache/openserverless-admin-api/pull/42

   ## Summary
   
   This is the first, preparatory step of the ASF convenience-binary licensing 
remediation for the Admin API image.
   
   - add an artifact-specific `LICENSE`, `NOTICE`, and Incubator `DISCLAIMER`;
   - add `THIRD-PARTY.csv`, derived from `uv.lock`;
   - add `WARN.txt` with unresolved licensing and reproducibility findings;
   - copy the files into the final image under 
`/usr/share/doc/apache-openserverless/`.
   
   ## Important status
   
   This PR is intentionally a draft. It does **not** claim that the resulting 
image is ready for an ASF release or fully ASF-compliant.
   
   Known blockers recorded in `WARN.txt` include:
   
   - `psycopg` and `psycopg-binary` declare LGPL-3.0 licensing, which is 
Category X under ASF policy;
   - the image resolves the Python environment from `pyproject.toml` rather 
than installing in frozen mode from `uv.lock`;
   - the inventory must still be reconciled against an SBOM generated from each 
final image digest;
   - dependency license texts and any required third-party notices must be 
completed after final-image analysis.
   
   Removal or replacement of Category X dependencies is handled separately and 
is outside this PR.
   
   ## Validation
   
   - verified all five legal files are present;
   - parsed `THIRD-PARTY.csv` and checked uniform columns;
   - verified the Dockerfile copies the files into the final stage;
   - ran `git diff --check` successfully.
   
   ## Follow-up before marking ready
   
   - remove or replace Category X dependencies;
   - rebuild every published architecture;
   - generate and review a digest-level SPDX or CycloneDX SBOM;
   - reconcile `LICENSE`, `NOTICE`, and the third-party inventory with the 
final filesystem;
   - include all required dependency license texts or in-package pointers.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to