Gateway to NEW
We aim to:
-
Develop automated CI checks that assist the verification of copyright statements, license terms and source availability of packages.
-
Use these CI tests to peer-review new packages before they are submitted to the NEW queue, to reduce rejection rate and therefore speed up the processing.
We are in pilot phases. Improvements of the workflow are welcome. In the current workflow, the package mainainer's request (with self assessment) and reviews are in a single issue, but a multi-issue workflow was also considered and is not ruled out if it gains traction.
How to request a review
- The package maintainer adds the pipeline to its Salsa CI file.
- The package maintainer opens an issue that includes:
- Title "Review request: FOO" replacing FOO with the package name.
- A URL to the canonical Salsa git repository of the package.
- A URL to the pipeline running on the package.
How to make a review
- Each reviewer post their coments or assessment a the issue. The can use the default template checklist to guide their review.
- Each reviewer add a review label to the issue when they see no problems in the packages.
- Once two or reviews are thumbs are up, the maintainer closes their own issue.
Reference information:
- Debian Policy 2.3 β Copyright considerations
- Debian Policy 12.5 β Copyright information
- REJECT-FAQ
- https://ftp-master.debian.org/#rejections
About the team:
By default, all members of the debian
team have Maintainer access.
Link to team activity log.