> @paelzer are there other cases of shared packages? There is history in server/openstack, server/maas, server/kernel, ... and it always was bad and eventually cleared to be one. I'd strongly suggest you go for "one owner" and "one strong supporter" or whatever you want to call it :-)
> Who is responsible for owning and integrating dbus-run-session? That needs to be solved by the owning team and their supporting team. To fully enable and promote it that needs to be done (or needs a replacement) according to the former discussions. > Which team will own security issues if they come up in the future? (e.g., in > cases similar to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2067613 ) Per http://reqorts.qa.ubuntu.com/m-r-package-team-mapping.html you can see your section there. http://reqorts.qa.ubuntu.com/m-r-package-team-mapping.html#ubuntu-security So "ubuntu-security" would be what you subscribe if security ends up being the owning team. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015538 Title: [MIR] dbus-broker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-broker/+bug/2015538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
