I am concerned about the use of the libertine-team as the designated subscriber for this because of the granularity of this team; it appears to currently be a reasonably-sized team, but it also seems this is a one-off project team which I could imagine would have its membership reduced later as the project matures and engineering resources are allocated elsewhere.
It's certainly appropriate for the libertine-team to follow the bugs for this project, but with a bug subscriber we also want to be able to answer the question, "organizationally, who is responsible for problems in this package long term if we need to escalate?" For that it is usually better to use a smaller number of teams that have a fairly stable mapping to the Canonical org chart, which I'm not sure is true for this team. This is an existing problem with many of the client stack packages in main, so I don't consider this a blocker for libertine right now (and it's quite urgent that we get libertine into main to unblock image builds). Will add libertine-team to our list of known teams for now, but I think we want to revisit this later as part of a review of the client stack ownership generally. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588050 Title: [MIR] libertine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1588050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
