Bug Supervisors are not notified when the project is not shared

[Curtis Hovey]

The Bug Supervisor role exists to get notifications about private (proprietary) bugs. Setting a team in that role does not share user-data and proprietary information with them. When sharing is released, the bug supervisor role just gives the team elevated permissions to triage and nominate bugs.

The role currently acts are a an implicit structural subscription for notification, and is used to create create a real subscription when the bug is made proprietary. This rule does not agree with sharing rules because the bug supervisor can be an inclusive team. Lp cannot subscribe an inclusive team to a private bug. Projects cannot share with inclusive teams.

But many projects, and specifically Canonical, configured the bug supervisor role to ensure an exclusive team is notified and has access to private bugs. Should Lp offer to share proprietary and user-data with the bug supervisor if it is an exclusive team? Should Lp warn that inclusive teams will in the bug supervisor role will not be notified? Should Lp offer to create a structural subscription for the team?

[Curtis Hovey (sinzui)]

This is the query that shows which bug supervisors need APGs and structural subscriptions.

-- Under the old rules the default person to get private bug mail
-- is the maintainer. The maintainer may set the bug supervisor to
-- himself (a no-op) or to a team that he belongs to.
-- Under the new rules, the maintainer gets full access by default,
-- but the bug supervisor gets no access because the role exists
-- to deletegate bug triage, so the team can be inclusice.
-- We only want to share USERDATA with exclusive bug supervisor teams
-- for active projects that use Lp Bugs.
-- these team need a structural subscription for with a USERDATA filter.
select p.name, bs.name
from product p
    join person bs on p.bug_supervisor = bs.id
where
    p.active is true
    and p.official_malone is true
    and bs.teamowner is not null
    and bs.subscriptionpolicy in (1, 3)
    and p.owner != p.bug_supervisor
    -- and p.driver = p.bug_supervisor
order by bs.name
;
-- (758 rows) on staging.
-- common practive is to set the driver team as the bug supervisor to
-- ensure the people who plan releases can see the bgus.
-- (378 drivers get proper access which includes all Canonical projects)