I just want to update you with a few words about the Gateway to NEW
project. (https://salsa.debian.org/newgateway-team)
Our goal is to have an infrastructure and tools to host pre-upload peer-review of the debian/copyright file of source packages before
they are sent to the NEW queue, in the hope of making them perfect and reduce the rejection rate, thus accelerating the processing.
Hi Charles,
On Sat Apr 5, 2025 at 5:59 PM CEST, Charles Plessy wrote:
I just want to update you with a few words about the Gateway to NEW
project. (https://salsa.debian.org/newgateway-team)
Our goal is to have an infrastructure and tools to host pre-upload
peer-review of the debian/copyright file of source packages before
they are sent to the NEW queue, in the hope of making them perfect and
reduce the rejection rate, thus accelerating the processing.
I'm sorry, but I don't understand. Why should I do copyright reviews in
the Gateway to NEW team, instead of joining the NEW team itself?
(Ignoring the fact that joining the NEW team is a more involved process)
As I understand it, doing copyright reviews outside of the NEW team
would not speed up processing, as they would have to re-review
everything anyway. The only thing this would help with is reduce
rejection rate, but in my experience rejects are quite rare.
I'm sorry, but I don't understand. Why should I do copyright reviews
in the Gateway to NEW team, instead of joining the NEW team itself?
Hi all,
I just want to update you with a few words about the Gateway to NEW
project. (https://salsa.debian.org/newgateway-team)
Our goal is to have an infrastructure and tools to host pre-upload peer-review of the debian/copyright file of source packages before they
are sent to the NEW queue, in the hope of making them perfect and reduce
the rejection rate, thus accelerating the processing.
At the moment there are rudimentary Salsa CI pipelines that aim at
providing a web-browsable view of the package contents that are relevant
for copyright checks (https://salsa.debian.org/newgateway-team), and
another repository hosting a checklist and hosting the reviews in its
issue tracker (https://salsa.debian.org/newgateway-team/reviews/-/blob/main/.gitlab/issue_templates/Default.md).
We explored two possible workflows, one where one issue contains all the review, and one with one issue per review. The first one, simpler, is gaining traction, but we are only three, so, the door is surely not
closed for other ways of operating in the future.
I would be delighted if more people would join, as much on the review
side as on the pipeline development side. There is a lot to do, but we
can change Debian together!
At the moment there are rudimentary Salsa CI pipelines that aim at
providing a web-browsable view of the package contents that are relevant
for copyright checks (https://salsa.debian.org/newgateway-team), and
another repository hosting a checklist and hosting the reviews in its
issue tracker (https://salsa.debian.org/newgateway-team/reviews/-/blob/main/.gitlab/issue_templates/Default.md).
Do you plan to integrate this into the existing salsa-ci-team/pipeline?
Would you be able to provide me a link to an example of this
web-browseable view? I might be able to provide some feedback.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 486 |
Nodes: | 16 (1 / 15) |
Uptime: | 148:22:12 |
Calls: | 9,659 |
Calls today: | 1 |
Files: | 13,708 |
Messages: | 6,168,027 |