Comment 1 for bug 479331

I discussed this with Graham, and we identified two problems:

1. Making it possible to appoint everybody (except teams you don't administer) may lead to an unpleasant suprise for a supervisor who isn't aware of the consequesnces of his new role: lots of bug mail.
2. The current permission check for structural subscriptions in StructuralSubscriptionTargetMixin._userCanAlterSubscription() already has a special case when the subscription target is an IDistributionSourcePackage, where more people are allowed to subscribe somebody else. Adding another special case, in this case for the new subscriber getting the "new hat" of a bug supervisor would make the code even more convoluted.

Especially issue 1 needs a bit more discussion. Our idea is to implement a process, where a person/team is first proposed to become the bug supervisor, and where the proposed person/team can then explicitly accept or decline this role.

This is a bit outside of the scope of fixing an OOPS, so we'll leave the permissions as they are right now. To fix this bug, I'll only catch the exception lthat leads to the OOPS and show the user a polite error message.