Hi, > What I'm really missing here is the global picture of how this (= uses > of Salsa beyond just using a Git repository) fits in Debian workflow_s_. > Just saying "you can check open MRs from the command line with `salsa > merge_requests` if you don't like checking the Salsa project page." is > not very useful. > > There are developers who maintain a small number of large packages, > and developers who maintain a large number of small packages. > There are developers who prefer push-based notifications using email > (and then use their mailbox as a To-Do list), and developers who > prefer dashboard services[1] to get a new overview of what they need to > look at. > > [1] Mostly https://qa.debian.org/developer.php, > https://udd.debian.org/dmd/ (both per-maintainer/team) and > https://tracker.debian.org/ (mainly per-package) those days.
I put screenshots of those yesterday at https://wiki2025.debian.org/wiki/Salsa The tracker improvement is being worked on at https://salsa.debian.org/qa/distro-tracker/-/issues/85. Thanks for participating in it and for all your work on UDD. > All this is reasonable and meets real needs. As you care about better > integration of Salsa in Debian workflows, I think that you should review > what is the current integration level, and how it can be improved. I have and will continue to improve tooling here and there. In parallel to improving tools, we also need to remind people that this avenue of contributions exists and should not be ignored to maintain a culture where merge requests matter and should not be dismissed as a nuisance "wasting developers' time." as some put in this thread.
