Template imports built from branches are owned by VCS imports.

[Henning Eggers]

Translation template import - ogmrip in OGMRip trunk
----
Hello VCS imports,

On 2010-06-13 20:50z (3 minutes ago), you uploaded a translation
template for ogmrip in OGMRip trunk in Launchpad.

The template has now been imported successfully.

Thank you,

The Launchpad team
----

^ we get many of these nowadays, how do we turn it off? VCS import admins are not interested, and the user wanting the import probably is interested but not being told.

[Henning Eggers (henninge)]

The question is: who should own the queue entries (be the uploader)? It is vcs-imports atm because it owns any imported branch. Since vcs-imports is a celebrity, we could check for it and select somebody else instead, like the project maintainer.

[Jeroen T. Vermeulen (jtv)]

For imports from a mirrored branch, I think nobody should be notified at all. The project's owners can use the import queue UI to monitor and diagnose. They are not getting email notifications now, and I haven't heard anyone ask for them. In the future I'm sure we'll want a unified why-does-this-not-work UI covering the process end-to-end.

Experience shows (as does this bug) that people mind getting an unexpected stream of notifications. I wouldn't direct this stream of notifications at currently unsuspecting users just for the sake of them having to go somewhere.

This also begs the question of what to do with notifications of imports triggered by _hosted_ branches. For the pottery case, if every commit to a branch triggers a template rebuild, import success notifications are likely to be very annoying. Failure notifications can be useful, but possibly a nuisance if each and every branch change triggers them. And again there is also UI for diagnosing problems.

The non-pottery case is different. That's where a user commits a change to a template or a translation file, and gets a notification about its import. I think that will often be appreciated, and as long as the branch is hosted, we know exactly where to send the email.

[Jeroen T. Vermeulen (jtv)]

Actually, I now see that project owners do get notified of translation imports directly from mirrored branches (though not in the case of pottery imports). So that's fine as it is.

The notifications going to vcs-imports are only for templates that the build farm generates from mirrored branches. Those uploads are done in the name of the branch owner. We can simply suppress notifications to vcs-imports, and should consider suppressing uploads from the build farm by making them owned by a similar, "notification-deaf" celebrity.

[Jeroen T. Vermeulen (jtv)]

Fix will be on staging in db-stable r9797.

[Launchpad QA Bot (lpqabot)]

Fixed in stable r11568 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/11568>.