We could probably automate at least the calendar setting by sending an ics file with a reminder after 21 days when opening ITS bug (or another service that queries udd and generate these mails). We could also send an email reminder when 21 days are over. This would ease the burden on people filing ITS bugs.Personally, my main challenge is having to focus on the same issue twice, with a minimum delay of 21 days in between. For example, I encountered an ITS bug that had been lingering in the BTS for over a year. The waiting period is entirely reasonable under our current understanding of package ownership, as it allows the maintainer sufficient time to respond. Shortening this waiting time might have limited impact, as the person initiating the salvaging process still needs to set a calendar reminder. I’m unsure how to improve this aspect within the ITS process.