Hello, The buster development cycle is open. I'm personally interested in working on changes that are directly related to the issue mentioned in the Subject. I'm sure many people will have a problem changing their package for the better while at the same time introducing a policy violation. I thus consider this issue a blocker for my work. (Not to mention I already maintain a package violating this part of policy and everyone seems to be in agreement it's the right thing to do. See merged bug report for history.)
Can we please get the original issues in this bug report resolved soon so we can actually get the risky changes done during the early phase of the Buster cycle? I don't see any pros of leaving policy in its current state related to this issue. As I've argued elsewhere, if it's hard to come to a conclusion about the perfect replacement I would suggest just removing the harmful parts as an intermediate step. Is there anything left to resolve before actually editing policy that I might look into helping out with? Regards, Andreas Henriksson
