Luca Boccassi <bl...@debian.org> writes: > Snarks aside, allowing merge requests to be open on Salsa in _addition_ > to attachments to the BTS, as the vast majority of other packages > already do, doesn't take away anything from you, but would add quite a > lot for the rest of us, who find ourselves very limited and very much > barrier-ized by clunky, old and painful email-based processes.
Merge requests are useful when the goal is to be able to merge the merge request as-is at the end of some code review process. My guess is that this happens about 20% of the time with Policy. The other 80% of the time I tweak wording or phrasing or formatting when applying the change, and also add an upgrading-checklist entry and other bookkeeping that I don't want to have to explain to everyone proposing new wording. Policy is not a program and we're not taking source code changes. The goal of the discussion is to converge on the semantics of what we are going to say, which often requires multi-paragraph discussions where the normal tools of email such as quoting are more useful. I find trying to have an email-style discussion in Salsa to be annoying and tedious. It also fragments the record, whereas having it in the bug means I can, at any time, load the entire bug into Gnus and re-read the discussion of how we arrived at the decision in the same tool that I use for reading all other Debian discussions. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
