In response to comment #8, you said that "Until [the owning team issue] is resolved, I believe it doesn't make sense for other people to do the work to process this application." However, having an owning team is only a requirement for the actual promotion. From https://github.com/canonical/ubuntu-mir/blob/main/README.md:
RULE: - All packages must have a designated "owning" team, regardless of
RULE: complexity, which is set as a package bug contact. This is not a
RULE: requirement for the MIR team ACK, but for the package to be promoted
RULE: by an archive admin. Still, it is strongly suggested to subscribe,
RULE: as the owning team will get a preview of the to-be-expected incoming
RULE: bugs later on.
In response to comment #8, you said that "Until [the owning team issue] is resolved, I believe it doesn't make sense for other people to do the work to process this application." However, having an owning team is only a requirement for the actual promotion. From https:/ /github. com/canonical/ ubuntu- mir/blob/ main/README. md:
RULE: - All packages must have a designated "owning" team, regardless of
RULE: complexity, which is set as a package bug contact. This is not a
RULE: requirement for the MIR team ACK, but for the package to be promoted
RULE: by an archive admin. Still, it is strongly suggested to subscribe,
RULE: as the owning team will get a preview of the to-be-expected incoming
RULE: bugs later on.
Therefore, I am reopening this bug.